(04-08-2015 07:23 AM)SixFive7 Wrote: [ -> ]Dear Yealink,
We are also running multiple setups with a T46G + BT40 + Voyager Legend. All firmware is up to date:
T46G: 28.73.0.50
Voyager Legend: 106
Still we find problems.
Most users only have a few calls an hour and experience no problems except for the need to re-pair every few days.
Some users however are part of our callcenter team. They experience heavy loads where the phone practically never stops ringing on multiple lines. In this scenario all headsets fail within the hour in one of three ways:
1>
Sometimes the customers suddenly hear a loud static forcing them to call back.
2>
Sometimes the headsets stop receiving or sending audio, forcing the user to disable and re-enable the headset.
3>
But mostly the headset goes into what we call ghost mode. In this mode the headset can be enabled (green light) on the phone, but the voyager legend does not report the connection. Also, if we go into the menu, we can see the pairing has disappeared. Putting the headset into pairing mode and trying to re-pair will not succeed until the phone is power cycled. On occasion we even need to hard-reset the phone. Luckily we have a provisioning server.
Plantronics is not taking blame and is refusing to RMA their headsets. In their defense, the headsets work flawlessly on other phones and bluetooth is supposed to be generic. Also we have used them on other phones for years without incident.
The problem seems related to the bluetooth stack of the T46G. Our experience has been that on all the v72 versions the BT40 was not recognized half of the time. When it was, many attempts were required to even get a device paired. Many different beta versions in the v72 series we tried resulted in better support for recognition of the BT40 adapter, but were riddled with other bugs and performance problems. Now that the v73 version is released we were hoping our problems would disappear as one ought to think enough development time had passed. However, except for a more stable recognition of the BT40 adapter, none of our problems with the Voyager Legend have been resolved. As a result we are on the brink of going for another solution and leave the T46G phones for a lengthy RMA procedure.
Yealink, when can we expect the problems around the BT40 adapter to be resolved? Or, if never, the compatibility matrix to be updated?
Your sincerely,
A somewhat frustrated customer
Yep Im now running 28.80.0.95 and Im still having problem 1> on both Sennheiser MB Pro and Jabra Evolve 65 headsets.
This is really starting to annoy me. Any updates Yealink?
Mike
(08-23-2016 12:55 PM)ipcsolutions Wrote: [ -> ] (04-08-2015 07:23 AM)SixFive7 Wrote: [ -> ]Dear Yealink,
We are also running multiple setups with a T46G + BT40 + Voyager Legend. All firmware is up to date:
T46G: 28.73.0.50
Voyager Legend: 106
Still we find problems.
Most users only have a few calls an hour and experience no problems except for the need to re-pair every few days.
Some users however are part of our callcenter team. They experience heavy loads where the phone practically never stops ringing on multiple lines. In this scenario all headsets fail within the hour in one of three ways:
1>
Sometimes the customers suddenly hear a loud static forcing them to call back.
2>
Sometimes the headsets stop receiving or sending audio, forcing the user to disable and re-enable the headset.
3>
But mostly the headset goes into what we call ghost mode. In this mode the headset can be enabled (green light) on the phone, but the voyager legend does not report the connection. Also, if we go into the menu, we can see the pairing has disappeared. Putting the headset into pairing mode and trying to re-pair will not succeed until the phone is power cycled. On occasion we even need to hard-reset the phone. Luckily we have a provisioning server.
Plantronics is not taking blame and is refusing to RMA their headsets. In their defense, the headsets work flawlessly on other phones and bluetooth is supposed to be generic. Also we have used them on other phones for years without incident.
The problem seems related to the bluetooth stack of the T46G. Our experience has been that on all the v72 versions the BT40 was not recognized half of the time. When it was, many attempts were required to even get a device paired. Many different beta versions in the v72 series we tried resulted in better support for recognition of the BT40 adapter, but were riddled with other bugs and performance problems. Now that the v73 version is released we were hoping our problems would disappear as one ought to think enough development time had passed. However, except for a more stable recognition of the BT40 adapter, none of our problems with the Voyager Legend have been resolved. As a result we are on the brink of going for another solution and leave the T46G phones for a lengthy RMA procedure.
Yealink, when can we expect the problems around the BT40 adapter to be resolved? Or, if never, the compatibility matrix to be updated?
Your sincerely,
A somewhat frustrated customer
Yep Im now running 28.80.0.95 and Im still having problem 1> on both Sennheiser MB Pro and Jabra Evolve 65 headsets.
This is really starting to annoy me. Any updates Yealink?
Mike
We had the same problem you describe. Particularly number 1. We were using Plantronics Legend CS. The battery died in this one so we switched to the standard Plantronics Legend and it has worked perfectly since. (3-4 months now)
(08-23-2016 01:28 PM)waynecollins Wrote: [ -> ] (08-23-2016 12:55 PM)ipcsolutions Wrote: [ -> ] (04-08-2015 07:23 AM)SixFive7 Wrote: [ -> ]Dear Yealink,
We are also running multiple setups with a T46G + BT40 + Voyager Legend. All firmware is up to date:
T46G: 28.73.0.50
Voyager Legend: 106
Still we find problems.
Most users only have a few calls an hour and experience no problems except for the need to re-pair every few days.
Some users however are part of our callcenter team. They experience heavy loads where the phone practically never stops ringing on multiple lines. In this scenario all headsets fail within the hour in one of three ways:
1>
Sometimes the customers suddenly hear a loud static forcing them to call back.
2>
Sometimes the headsets stop receiving or sending audio, forcing the user to disable and re-enable the headset.
3>
But mostly the headset goes into what we call ghost mode. In this mode the headset can be enabled (green light) on the phone, but the voyager legend does not report the connection. Also, if we go into the menu, we can see the pairing has disappeared. Putting the headset into pairing mode and trying to re-pair will not succeed until the phone is power cycled. On occasion we even need to hard-reset the phone. Luckily we have a provisioning server.
Plantronics is not taking blame and is refusing to RMA their headsets. In their defense, the headsets work flawlessly on other phones and bluetooth is supposed to be generic. Also we have used them on other phones for years without incident.
The problem seems related to the bluetooth stack of the T46G. Our experience has been that on all the v72 versions the BT40 was not recognized half of the time. When it was, many attempts were required to even get a device paired. Many different beta versions in the v72 series we tried resulted in better support for recognition of the BT40 adapter, but were riddled with other bugs and performance problems. Now that the v73 version is released we were hoping our problems would disappear as one ought to think enough development time had passed. However, except for a more stable recognition of the BT40 adapter, none of our problems with the Voyager Legend have been resolved. As a result we are on the brink of going for another solution and leave the T46G phones for a lengthy RMA procedure.
Yealink, when can we expect the problems around the BT40 adapter to be resolved? Or, if never, the compatibility matrix to be updated?
Your sincerely,
A somewhat frustrated customer
Yep Im now running 28.80.0.95 and Im still having problem 1> on both Sennheiser MB Pro and Jabra Evolve 65 headsets.
This is really starting to annoy me. Any updates Yealink?
Mike
We had the same problem you describe. Particularly number 1. We were using Plantronics Legend CS. The battery died in this one so we switched to the standard Plantronics Legend and it has worked perfectly since. (3-4 months now)
Yes thanks although the Jabra Evolve 65 lasted about 2 months. Unfortunately in ear headsets are out of the question for most of my customers. I would like to know what causes this problem though and what we can do about it?
Thanks
Mike
Was a resolution ever found for this?
I am having the same type of issue (#3) on T46 with a Jabra Style BT headset. It works for a day and then will not connect. Phones have to be rebooted for them to recognize the headsets again.
I am currently running version 28.73.193.50. The phones were running version 28.80.193.130 with the same issue. It is doing it on multiple phones using the same type of headset.
Phone = T46 28.73.193.50
Headset= Jabra Style
Any input would be appreciated! Customer is getting very frustrated with this.
Thanks,
Tim
Add me to this list too. We have about 80 x T46G running firmware 28.80.0.125. We had to completely stop using our Plantronics Voyager headsets. I was spending all day long re-pairing them to try and get rid of the static issue. They work well for a while, then all the sudden all the other person hears is loud solid static. We have tried several other models of Bluetooth headsets with the same end result. I'd really like a fix for this...
I have stopped using Bluetooth now and just use DECT wireless headsets like the Sennheiser D10 Phone.
It would be nice if they fixed it though.
Thanks Mike
Hi All,
regarding the loud static and lose connective, we now have some optimization on our new firmware V81, such as enhance the connectivity of BT40 and the headset. the latest V81 version will release this week, you can make a testing with them.
We are also having this issue with plantronics voyager headsets. There is a loud static sound on the receiving end and sometimes they just cant hear us. I have had a ticket in with Yealink for a few weeks. I've sent them all of the info and traces they've asked for and haven't got an answer back yet. I hope this gets fixed soon. I have other customers to deploy these to but I'm waiting for a fix.
