- Joined
- May 22, 2017
- Messages
- 4
- Reaction score
- 1
Hi,
Just wondering if anyone else has experienced issues with the T54W ringer volume after the 96.86.0.23 firmware update?
The firmware update coincided with updating the system to the latest V16 SP level.
The issue seems to be only affecting those with headsets (Sennheiser). This particular client also uses hotdesking.
A user will adjust the ringer volume on the phone down to low or sometimes silent, and when the next call rings on the phone. the ringer volume has been reset back to the same position it was before the user adjusted it.
The end result is a loud ringer (multiplied by 5-6 phones) and a noisy office. This client also shares space with other businesses and the noise can be disruptive.
I had been using a custom template for the phones, and have changed back to using the default T54W in troubleshooting, unfortunately to no effect.
So far I've been able to set the template to push the ringer through the headset (when connected) as a workaround, but am hoping to determine the cause of the issue.
I thinking it is down to the new Yealink firmware version, as the comparing the old 3CX template to new doesn't show many differences.
Thanks in advance,
Tim
Just wondering if anyone else has experienced issues with the T54W ringer volume after the 96.86.0.23 firmware update?
The firmware update coincided with updating the system to the latest V16 SP level.
The issue seems to be only affecting those with headsets (Sennheiser). This particular client also uses hotdesking.
A user will adjust the ringer volume on the phone down to low or sometimes silent, and when the next call rings on the phone. the ringer volume has been reset back to the same position it was before the user adjusted it.
The end result is a loud ringer (multiplied by 5-6 phones) and a noisy office. This client also shares space with other businesses and the noise can be disruptive.
I had been using a custom template for the phones, and have changed back to using the default T54W in troubleshooting, unfortunately to no effect.
So far I've been able to set the template to push the ringer through the headset (when connected) as a workaround, but am hoping to determine the cause of the issue.
I thinking it is down to the new Yealink firmware version, as the comparing the old 3CX template to new doesn't show many differences.
Thanks in advance,
Tim