Yealink Forums
T-42 BLF - Printable Version

+- Yealink Forums (
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: T4x Series (/forumdisplay.php?fid=31)
+--- Thread: T-42 BLF (/showthread.php?tid=32821)

T-42 BLF - mlenihan - 10-26-2016 02:40 AM

On 3CX V14. Our Yealink t42 phones with firmware lose BLF presence after a while. We have other extensions configured as BLF and they do not show if someone is on the phone (BLF buttons stay green).

We attempted to manually install firmware but it will not take (it goes through 'updating firmware' but stays on .110).

The only fix we have found so far is to reboot the phones. We cannot tell how long the reboot is good for before it stops working.

Has anyone seen this or have a fix for it?

RE: T-42 BLF - Lucia_Yealink - 10-26-2016 11:01 AM

Dear customer,

1. About the BLF presence problem, do you mean the BLF can work normally first but will lose presence after a while? When the status of the monitored extension changed, the BLF LED stay green all the time?

If the answer is yes, please share us more information below:
1) Please provide the level 6 syslog, config.bin and pace trace when you reproduce the issue.(if you can update the firmware to .130, then please use it to reproduce the issue.)
About how to get the three files, please refer to the FAQ below:
2) How often the issue will happen? Such as once a day?
3) How many phones you have in total? And how many of them have the issue? If there are phones that can work normally, please also provide the three files to make a comparison.

2. About the update firmware issue, do you mean you update the firmware via the web interface but failed ? If the answer is yes, please see the detail below:

1) Please check if you configure the firmware update to the .110 version in the auto provision file, if you configure like that, then after the phone update to the .130 version, it will do auto provision and update the firmware to .110 again. So please check if you have configure it in the auto provision file, if yes, please modify or delete the parameter(firmware.url=)
2) If is not because of the auto provision , please provide the level 6 syslog, config.bin and pace trace for us when you reproduce the issue to do trouble shooting.
Please note to use the Wireshark to get the pace and export the level 6 syslog to server.
3) How many of the phones have the update issue?

You can send the three files to Thank you for your information in advanced.

Any question, please let me know.

Best Regards,
Lucia Lu

RE: T-42 BLF - mlenihan - 10-27-2016 01:55 AM

Lucia. This was able to solve my problem. The phone was auto provisioning after a manual update to .130 and rolling back to .110. I removed .110 and the phone stayed at .130 after update. Thank you.