Yealink W52P base drops and reconnects individual handsets

Adalis · December 15, 2015, 8:21pm

Distro install on VM. FreePBX 13.0.30, 10.13.66-6, Asterisk 13.5.0, using pjsip and extensions. Yealink W52P is remote. “FreePBX Statistics” show phones up and down continuously. Log file shows the phones unreachable and then reachable. Calls can still be made and received while the phone is showing unreachable. Base station restarted, no change. Base returned to factory and reloaded, no change.

Help, please.

Log files:

2015-12-15 11:54:09] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Contact 5001/sip:[email protected]:15030 is now Unreachable. RTT: 0.000 msec
[2015-12-15 11:54:09] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Endpoint 5001 is now Unreachable
[2015-12-15 11:55:06] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Contact 5001/sip:[email protected]:15030 is now Reachable. RTT: 89.311 msec
[2015-12-15 11:55:06] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Endpoint 5001 is now Reachable
[2015-12-15 11:55:30] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Contact 5020/sip:[email protected]:15031 is now Unreachable. RTT: 0.000 msec
[2015-12-15 11:55:30] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Endpoint 5020 is now Unreachable
[2015-12-15 11:56:28] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Contact 5020/sip:[email protected]:15031 is now Reachable. RTT: 88.470 msec
[2015-12-15 11:56:28] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Endpoint 5020 is now Reachable
[2015-12-15 11:59:26] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Contact 4449/sip:[email protected]:15027 is now Unreachable. RTT: 0.000 msec
[2015-12-15 11:59:26] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Endpoint 4449 is now Unreachable
[2015-12-15 12:00:09] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Contact 5001/sip:[email protected]:15030 is now Unreachable. RTT: 0.000 msec
[2015-12-15 12:00:09] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Endpoint 5001 is now Unreachable
[2015-12-15 12:00:23] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Contact 4449/sip:[email protected]:15027 is now Reachable. RTT: 90.399 msec
[2015-12-15 12:00:23] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Endpoint 4449 is now Reachable
[2015-12-15 12:01:06] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Contact 5001/sip:[email protected]:15030 is now Reachable. RTT: 87.185 msec
[2015-12-15 12:01:06] VERBOSE[17280] res_pjsip/pjsip_configuration.c: Endpoint 5001 is now Reachable

Adalis · December 15, 2015, 8:26pm

Additional information: this is only occurring on this one base station that has three handsets and 5 active lines. All other local and remote phones are working fine. The FreePBX firewall is installed and configured and is getting green checkmark. Firmware on base is current. Base is connected through a SonicWALL NSA 240 persistent NAT is on everything else is off. Desk phone at same location has no issues.

Adalis · December 16, 2015, 12:16am

For those who are thinking this is a Yealink problem this base station has been on 12, worked great, was upgraded to 13, worked great, was installed on the newly cleanly loaded 13 and broke. Just saying.

reconwireless · December 16, 2015, 12:37am

What happens when you utilize a chan_sip extension?

Adalis · December 16, 2015, 7:10pm

It calms down, but then we lose the ability to use multiple devices on that extension. My extension has 5 devices tied into it. Since FreePBX isn’t supporting U&D and focusing on Extensions we will just let it log as it does. It doesn’t seem to affect the ability to call in or out. Most of our customers have multiple devices connected to their extension/DID. We have a medical device company who have 11 remote users that all have offices in multiple locations and all have the one extension. U&D worked great, jury is still out on Extensions.