SIP-T22P failing to register - Printable Version +- Yealink Forums (http://forum.yealink.com/forum) +-- Forum: IP Phone Series (/forumdisplay.php?fid=4) +--- Forum: Configuration (/forumdisplay.php?fid=24) +--- Thread: SIP-T22P failing to register (/showthread.php?tid=3995) |
SIP-T22P failing to register - carlyle - 06-24-2015 04:57 PM Firmware Version 7.70.23.10 Hardware Version 5.0.0.55 A number of T22P phones are failing to register one or more accounts that have previously been working. I thought a work around had been identified by using keep alive "notify" in the advanced options of Account, however phones that had been set to "notify" have lost the setting and reverted to disabled. This work around was attempted as nothing else we tried seemed to fix the issue. Phones experiencing this issue have had calls disconnect, unable to pick up or transfer, failing to have incoming calls ring. We only use Yealink T22P phones on the phone system. The phone lines are not SIP so some of the Firewall comments in other postings don't necessarily apply. Why would some of the phones have lost the keep alive setting ? I have to be careful about the firmware applied as the phone system updates include a Yealink firmware that they have tested. RE: SIP-T22P failing to register - James_Yealink - 06-24-2015 07:09 PM Hi, Do you use autoprovision in your environment? If you don't reset or upgrade phone, it may be changed by autoprovision. Is there a value in Server URL filed under autoprovision interface? Regards, James RE: SIP-T22P failing to register - carlyle - 06-24-2015 11:03 PM (06-24-2015 07:09 PM)Yealink_James Wrote: Hi, Thanks for the response. There is a valid address in the "provisioning server" section of Upgrade \ Advanced. This entry is on all phones but the problem has only appeared on a selection of them. RE: SIP-T22P failing to register - James_Yealink - 06-25-2015 09:50 AM Maybe these phones have their own mac.cfg file in the server. May I know who set up the autoprovision server? Can you check the configuration file in the server. Regards, James |