PIONEERS Yealink T46G phone

[Chris Sweeney]

$154 at Telephony Depot once you log in.

He was asking about the T48 not the T46

 

[wardmundy]

 

[wintek]

http://www.telephonydepot.com/Catalog/Yealink-Phones/Yealink-SIP-T48G

Log in and its $198.00 still in pre-order

http://www.voipdw.com/Yealink-SIP-T48G-p/sip-t48g.htm

Log in and its $192.00 shows in stock but not sure if Authorized reseller.

 

[jeff.h]

I see $193.40 at Telephony Depot right now.

Still pre-order but my account manager said they will be in stock by the end of the month. I can't wait to get one along with the bluetooth dongle. Anyone have experience with it on another phone?

 

[wintek]

Just got the T48G. Now I see what all the fuss was about on the T46G. It's looking good

 

[Spaceleeb]

Thanks wintek! Saved me some nice $$$ thanks!

Got my T48G's this week - they are awesome. One or two firmware quirks with DSS Keys, but I've reported them to Yealink and they are usually great about fixing them.

My only other Yealink gripe is the Headset button functionality... I'd like it to work like the Speakerphone button. From an idle state, you press the speakerphone button and it picks up a line. Press it again and it hangs up/releases the line and turns the speaker off.

The Headset button doesn't behave like that... It would be nice to be able to press it and have it pick up a line and press it again to hang-up.

 

[TheMole]

Hi all. i've been following this thread for a while. Is it possible to have the background image of the T46G/T48G be the output of a dynamic javascript webpage?

 

[DaveDog]

Hi all. i've been following this thread for a while. Is it possible to have the background image of the T46G/T48G be the output of a dynamic javascript webpage?

As far as I know, the answer at this point is no.

 

[nicknomo]

Hi, I've ordered some more of the T46G's, and it looks like I'm going to deploy a healthy number of them, but I've been hitting a wall trying to integrate some asterisk features into this phone's buttons.

I'm looking to make a direct transfer to VM button to use in conjunction with BLF keys. For instance, our operator would just hit the corresponding DSS key, than a BLF button on the operator panel (ext40 addon) and it would transfer directly to the voicemail of that extension. I know the operator could manually hit ##*<extension>, but I'm trying to prevent users from having to memorize feature codes and even extension numbers when possible (especially for an operator with 80 extension BLFs).

I've racked my brain on this for a few hours, and I'm looking for some fresh perspective. It looks like the phone doesn't have a basic way of implementing such a simple feature, but I'm hoping someone has some sort of workaround..

 

[wardmundy]

nicknomo: Just to be sure I understand what you're looking for...

Do you want users to be able to hit a button and transfer the caller to VM while the phone is ringing or after it is initially answered??

 

[nicknomo]

nicknomo: Just to be sure I understand what you're looking for...

Do you want users to be able to hit a button and transfer the caller to VM while the phone is ringing or after it is initially answered??

Hi Ward,

I'd like to be able to transfer the call after it is answered, directly to the voicemail of an extension that is chosen by the BLF. I asked Yealink support about this, and they didn't have any suggestions.

Basically, this is for an operator using an operator panel. The people we hire to sit at the operator extension don't always stay with the company long, and many may not know the extensions by heart. To assist them, they have a panel full of BLF's showing the names of other employees. If someone calls in from the outside asking for "Bob", and the receptionist knows the call isn't important (usually solicitors), she will transfer directly to Bob's voicemail. Right now, the receptionist has to hit: Transfer * <extension number> . I'd like to simplify this by hitting a DSS key for the transfer then the BLF for Bob, and have it go directly to his VM.

I tried making a DSS key of type "transfer", with value "*", but that immediately tries to transfer and doesn't wait for me to hit the BLF. I then tried to make a DSS key of type "DTMF", with value of "##*"... but when I hit the BLF after it sends the DTMF tone, it just dials the BLF's extension on another line.

I don't think the phone's DSS keys are really designed to do what I'm thinking, but I was hoping there was a clever workaround.

 

[DaveDog]

Hi Ward,

I'd like to be able to transfer the call after it is answered, directly to the voicemail of an extension that is chosen by the BLF. I asked Yealink support about this, and they didn't have any suggestions.

Basically, this is for an operator using an operator panel. The people we hire to sit at the operator extension don't always stay with the company long, and many may not know the extensions by heart. To assist them, they have a panel full of BLF's showing the names of other employees. If someone calls in from the outside asking for "Bob", and the receptionist knows the call isn't important (usually solicitors), she will transfer directly to Bob's voicemail. Right now, the receptionist has to hit: Transfer * <extension number> . I'd like to simplify this by hitting a DSS key for the transfer then the BLF for Bob, and have it go directly to his VM.

I tried making a DSS key of type "transfer", with value "*", but that immediately tries to transfer and doesn't wait for me to hit the BLF. I then tried to make a DSS key of type "DTMF", with value of "##*"... but when I hit the BLF after it sends the DTMF tone, it just dials the BLF's extension on another line.

I don't think the phone's DSS keys are really designed to do what I'm thinking, but I was hoping there was a clever workaround.

I spent some time looking for a solution to this also, eventually gave up. Hope to see a solution sometime on this.

 

[ou812]

when you say a panel full of blf's how many do you mean. if there are say 15 can you setup the second page on the panel and buttons with transfer *XXX and line them up so they are in same locations as blf's on previous page.

gary.

 

[nicknomo]

when you say a panel full of blf's how many do you mean. if there are say 15 can you setup the second page on the panel and buttons with transfer *XXX and line them up so they are in same locations as blf's on previous page.

gary.

I've thought about that, but we do have a lot of BLF's on the operator panel. I am not sure that would be practical for us. Right now, I'm entering the 3 digit extension on the BLF panel's display and having them do transfer *, but its slower than I'd like. You tend to get a lot of flak when you deploy a brand new phone system and its slower to operate than the previous 40 year old legacy system... The operator is really where I have the most trouble, since they are overworked and underpaid as it is. Losing a few seconds on a call doesn't sound like much, but when you are churning out calls, it can add up and create a little bit of a bottleneck.

 

[Spaceleeb]

Yealink has been very responsive to my inquiries about the DSS Key (softkey) programming issue I was having on my new T48G's... After collecting my config file and log file, they have re-produced the issue on their end and presumably a fix will be coming. Basically, on the 3rd page of DSS Keys, a Line option was getting stuck to a particular setting and couldn't be cleared, etc. I also suggested to them that the DSS Keys work like they do on the Aastras... If you have blank page 2/3/4 of DSS keys (ie. not using them), then it should allow you use all 12 positions on page 1, and not permanently set the 12th position to say DSS Key and let users see blank page 2/3/4... just would confuse them. Also suggested being able to "lock" DSS Keys across screens. Ie. put line appearances on page 1 and lock them and then have them in the same positions across all the other pages.

The other commentary I gave them was around what I view as inconsistent UI/functionality around the Headset button. Basically, they consider the Headset button as a "mode" instead of as an "action" like the Speakerphone button is. When you press the speakerphone button, it picks up a line and gives you a dial-tone on the speaker. When you press it again, it hangs-up. However, when you press the Headset button, it just illuminates and then requires you to select a line on the softscreen. Likewise to hangup, you need to press a soft-key for end call. They acknowledge this is as designed. I've said it just feels inconsistent...

If you look at it as "the normal phone operating mode is the physical handset that you place to your ear", then both the Speakerphone and Headset buttons should work the same way - Speakerphone mode or Headset mode. But Speakerphone currently puts it on speaker and gets a dial-tone - or hangs up a call when pressed again, whereas Headset currently works as you describe, requiring you to press touchscreen/soft keys... From a UI standpoint, it's inconsistent.
Given how programmable these phones are, at least an option in the configuration in the settings to allow Headset to operate either as it does today or to operate like the Speakerphone button would seemingly satisfy all users in how they wish to use the phone!
Otherwise, great phone - very happy with it... Now if only they would bring greater configurability to their W52 DECT base/handsets....
Cheers

 

[nicknomo]

In case anyone is interested, I made a yealink app for picking up calls on hold. It does require some other system modifications though (AGI script and config edit). I have a post in the developers forum here:

http://pbxinaflash.com/community/index.php?threads/yealink-app-for-picking-up-calls-on-hold.14759/

Its still in beta right now, but I've used it without incident so far..

 

[paulhuynh]

I am to have reach out to yealink last year on dss key issues via their own forum on t38 they said they are working on it like a year ago but still no solution.

I would love to switch out all my aastra and start usnig yealink but that doesnt seem likely a lot of my users are very currently using aastra and so used to dds and tr-vm option

 

[krzykat]

You know ... these guys are using linux for their OS on these phones (GS and Yealink at least) ... and their main deal is to sell phones. I don't know why they don't open up their products (source) more and let the open market fix their problems and build a more robust solution, allowing them to SELL phones.

 

[pshaww]

I'm not seeing the search this thread tool... so forgive me if this was already asked. The park.php script works perfectly for our systems, except for one major flaw (for us at least). It displays all parked calls. We use ParkingPro from Schmooze and certain phones can only park or retrieve calls from a give parking lot. In looking at the code in this script, I can say that I for sure do not know how to easily change the script to retrieve parked calls in the context (created via the ParkingPro module from Schmooze) that that extension only has express permission to use.

I would be glad to give any information on the context or conf files you may need, but unfortunately it is for sure displaying parked calls. Just all parked calls across all parking lots - we have 5.


I have been working on a YealinkV70 (firmware v70, v71, v72) provisioner package for Yealink T2x, T3x, T4x, VP530 devices and have almost everything working. I will have this package ready to go and updated at github for Andrew Nagy to hopefully approve and pull into the main code as another brand package (Yealink V70). My only hold up here is I really wanted to have a visual parking functionality that is compatible with ParkingPro to show parked calls for an extension's given default parking lot. If this isn't easily doable in the next few days I will just not include this functionality and merge it in later at github.


UPDATE: I found that the separate parkinglot names appear in AMI when typing Action: parkedcalls. I then also found under extensions_additional.conf that there is a new context for each extension, referring to which lot to park calls. There may be a way to create an entry in the provisioner to create a PHP script for each extension called park_$mac.php, query that extension's parkinglot assigned and only show the information relevant to that specific parking lot. But the AMI commands / PHP scripting goes beyond my abilities. I can help with the provisioner side, but need some assistance to be able to provision something like this to be compatible with the Parking Pro module.



-Jon

 

[phoneguy]

Or you can go look at the Rest Apps that include a parking app with more features and full support for Park pro. Example of the userguide for Aastra 6739 and a Digium D70 here.

http://wiki.freepbx.org/display/FCM/Parking-Aastra+6739i
http://wiki.freepbx.org/pages/viewpage.action?pageId=23037179

The Parking App is fully aware of Park Pro and only shows you parked calls for the lot(s) you are allowed to see and only blinks red and displays the parking notification if a call is parked in a lot that you are allowed to monitor.