Yealink Forums
BLF lighting wrong button on sidecar? Anyone experienced this? - Printable Version

+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: T4x Series (/forumdisplay.php?fid=31)
+--- Thread: BLF lighting wrong button on sidecar? Anyone experienced this? (/showthread.php?tid=42936)



BLF lighting wrong button on sidecar? Anyone experienced this? - tima - 07-08-2019 02:32 PM

Having an interesting issue where T46G's running 28.81.0.110 having random issues where a user sends a call via sidecar to another user but the incorrect BLF lights. I see the notify for the correct user but the button below it lights up. Example: expansion module button 12 is extension 1125 but when sending a call to button 12 via a press extension 1125 rings but the BLF monitor for button 15 lights up (extension 1129)

I can see from pcaps the notify being the correct extension but the incorrect button lights. Unplugging the side car and reconnecting it seems to "fix" the issue.

Exporting the entire config from the phones shows the BLF set correctly (this is from the exported settings > Export CFG Configuration File > all settings

expansion_module.1.key.12.type = 16
expansion_module.1.key.12.value = 1125
expansion_module.1.key.12.line = 1
expansion_module.1.key.12.label = Michele

expansion_module.1.key.15.value = 1129
expansion_module.1.key.15.line = 1
expansion_module.1.key.15.label = Mtg Rm


PCAP done locally at the phone shows the correct notify being sent:


Anyone experienced this?


RE: BLF lighting wrong button on sidecar? Anyone experienced this? - Brenda_Yealink - 07-16-2019 09:48 AM

(07-08-2019 02:32 PM)tima Wrote:  Dear Customer´╝î
This is Brenda from Yealink Technical Support team.

For this issue, please upgrade the phone to the latest version from the link below.
https://drive.google.com/open?id=1p7ghSkKo4XZqp1-1WYzbdKr-tgFArv0b

If it happens again, please try to reproduce the issue and offer us trace files for further analysis as below:
a. Level 6 syslog
b. PCAP trace
c. Config.bin
You can get the guide from this link to see how to export the issue data(trace files):
http://support.yealink.com/faq/faqInfo?id=707

(For the consideration of your privacy, you can email the trace files to me at: Brenda@yealink.com.)

If you have any other question, please click the link below to create a ticket, we will assign a FAE to follow up.
ticket.yealink.com


Best Regards,
Brenda