Yealink Forums

Full Version: T46G goes reboot during phone call
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Dear Support,

We have 1x MyPBX U500 + 100x T42G + 30x T46G in our university. We just finished installation of IP phones on users desk and started to remove old analog phones.
And then nightmare started...
It is already second week that every day I receive complains from number of IP phone users stating that their phones are accidentally went reboot during calls.
I noticed that all affected persons are T46G model owners (though it could be just coincidence).

Please advice what could be the reason of Yealink IP phones reboot, and how to eliminate this issue ?

Thank you
Here is the part of log from Asterisk PBX, for you interest:
[2014-07-29 12:44:15] WARNING[1814] chan_sip.c: Maximum retries exceeded on transmission 651044870@10.16.0.102 for seqno 2 (Critical Response) -- See doc/sip-retransmit.txt.
[2014-07-29 12:44:15] WARNING[1814] chan_sip.c: Hanging up call 651044870@10.16.0.102 - no reply to our critical packet (see doc/sip-retransmit.txt).
[2014-07-29 12:44:51] NOTICE[1814] chan_sip.c: Peer '2525' is now Reachable. (47ms / 2000ms) IP '10.16.0.102'
[2014-07-29 17:55:14] WARNING[1814] chan_sip.c: Maximum retries exceeded on transmission 1777351062@10.16.0.102 for seqno 2 (Critical Response) -- See doc/sip-retransmit.txt.
[2014-07-29 17:55:14] WARNING[1814] chan_sip.c: Hanging up call 1777351062@10.16.0.102 - no reply to our critical packet (see doc/sip-retransmit.txt).
[2014-07-29 18:01:33] NOTICE[1814] chan_sip.c: Peer '2525' is now Reachable. (23ms / 2000ms) IP '10.16.0.102'
Hi zonder,

Please try follow steps:
1.Did users plug in a standard power supply which is DC 5V/2A? if you use lower than the standard power supply, it will have reboot issue.
2.If they have alreay use a standard supply, how many T46 phones have this issue? And how often does this issue occur?
3. If this issue still exist, In order to do more troubleshootings, please supply syslog level 6, config.bin and pcap and send to support@yealink.com or support.usa@yealink.com.

How to Get the Correct Syslog, Config.bin and Trace

thanks in advance
Dear Support,

1. Yes, we use DC 5V/2A power adapters
2. As of today 8 of 30 T46G model users are reporting about phone's regular rebooting (near 3-6 reboots per day)
3. I collected syslog level 6 log and config.bin file and submitted them to support@yealink.com. It is not possible to get pcap log, since after phone reboots pcap log became cleared file I extracted is empty (24 byte long).

Please advise which version of T46G firmware you recommend to use with MyPBX U500 (the PBX we are using with T46G phones) ?

Currently all our T46G phones have firmware version 28.71.0.180.

28.72.0.1 and 28.72.0.25 versions have problem with auto-provision (extension is not being assigned after phone reboot)

Thank you
just to inform those who are interested. Reboot problem was solved by changing T46G version to 28.72.0.205 (the only v72 version which shows destination extension name)
Reference URL's