[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers.
You can see the details below.
https://www.yealink.com/ydmp-freetrial-2020
There are eight phone/console extensions on the local network and two phone/console extensions in another city which connect over the internet.
At least once a day, either of the two phones will receive notification packets of incoming calls and the console BLF LEDs will flash to indicate which extensions are ringing. When the call is answered, one of the LED's will continue to flash and the status icon on the LCD will still show the station as ringing. In this condition, the extension cannot be dialed by pressing the BLF button.
It us usually the extension that picked up the call. Sometimes, the extension will appear busy even though the call has ended. This only happens on the two remote extensions, never any of the local phones. I suspect this is partly caused by packet loss since we have a poor carrier system here and I have configured TCP on all extensions, as UDP is too unreliable over the public internet.
I tried calling the extensions in the hope that Asterisk would send out new status notifications to the extensions and cause the buttons to reset, but nothing seems to work and rebooting the phones is the only way to reset the LED's and the LCD display.
RE: EXP39 buttons fail to change status, phone requires reboot to fix
Hi Maerkis,
1. So only two remote phones can't change the BLF LED status? You connect one EXP39 on these two phones?
2. What about DSS key LED status on the phone DSS key, but not on EXP39? those 10 DSS keys also have this issue?
3.In this case, i am afraid we need logs on these two remote phones for analyzing.
Could you provide PCAP trace, syslog(level 6) and config.bin file to us, so we can analyze?
Before you export the syslog, please set log level as 6, and reboot the phone, then click Start,and reproduce the issue, then click Stop,and export the trace, syslog, config,bin to us.
(About where to export these files, please refer to attached screenshot.)
These three files are very important for us, hope you can kindly understand.
Thanks.
RE: EXP39 buttons fail to change status, phone requires reboot to fix
1. Only two of the phones are remote from the office, the others are on the same local lan as the PBX. Both of the remote extensions have one EXP39 each.
2. I'll try adding some extensions to the phone DSS keys and see what happens.
3. How long can the log capture run on the phones? It may be a day before I see the issue reproduced.
Also, what is a safe way to send the config to you?
(This post was last modified: 06-20-2013 07:49 PM by Benoiti.)
RE: EXP39 buttons fail to change status, phone requires reboot to fix
Hi you can send the trace,syslog, config.bin file to support@yealink.com
For example, if the issue happen about in afternoon, you can start the PCAP trace before afternoon.
Thanks.
