Yealink W60B fails to register after VPN breaks and reconnects

[Jim Shaflucas]

I have a 3CX installation with multiple sites connected via VPNs using Mikrotik routers.
For some reason, whenever one of the sites loses connectivity to the 3CX server (the VPN breaks and reconnects), the W60B phones fail to re-register. All the other phones come back online at the sites including the W56P DECT phones and T46S phones. It's just the W60B phones that have this problem. The only way to get them to re-register is to log into the web interface of the W60B and reboot it. Then it is good until the next "outage" which could be anything from a power failure or an internet disruption. I can recreate the issue if I restart the Mikrotik router at the sites that have W60Bs. This happens at all locations that have W60B phones. Firmware is updated to the latest and 3CX is running the latest version and service packs.

Anyone else having this issue?

-Jim

 

[cobaltit]

Just to make sure we're on the same page. So the W60B is the base station and the W60H are handsets. The W56P is a bundle of of a W56H handset with a different base than the W60B. But the W56H can work with either base (it's a mess). Trying to figure out if it's a problem with a specific model of the base or if it's with a specific handset template regardless of the base. It's probably going to be one of two things:

- Firmware or hardware issue causing the the SIP stack to crap out when registration fails
- Missing or really long re-register interval in the template.


I can tell you that I had something similar with the W60B base and W60H handsets on my UCaaS platform with firmware 77.81.0.20. Customer lost internet and a T41P at the site came up but the DECT phones didn't. Granted they didn't wait very long so they rebooted the base station before we could look at it.

 

[cobaltit]

So it's been a while since I've provided a DECT phone in 3CX since I don't usually handle it. I just provisioned 2 bogus handsets in 3CX to compare the W60B template and the W56P template. They look identical and they have a registration interval set to 120s so it seems it might be a problem with the base. I'll put it on my list of things to test when I find time in the office.

 

[Jim Shaflucas]

Thanks for your reply. So the bases are the W60B and the handsets are the W56H. The base is running the latest firmware 77.83.0.10. The handsets are running 61.83.0.10.

I do have several locations with the W52P/W56P bases with the W56H handsets that don't have this problem so I definitely think the issue is with the W60B bases.

 

[Marari]

@Jim Shaflucas

You might want to upgrade your base firmware. 77.83.0.20 is current on the 3CX page.

 

[Jim Shaflucas]

I never noticed that there was a specific 3CX section on Yealink's site. Thanks for the pro-tip. I will give that a shot!

 

[Marari]

I never noticed that there was a specific 3CX section on Yealink's site. Thanks for the pro-tip. I will give that a shot!

You're most welcome.

3CX firmware is here:

https://www.yealink.com/products_48.html

(This is Yealink's firmware page with a link to 3CX supported firmware)

 

[Jim Shaflucas]

Ok so upgrading the fw for the W60B however the issue still persists. Tested by the rebooting the router at the site where the W60B is located after fw update. After re-boot, W60B reg failed. Rebooting the W60B base got it back online again.

 

[Marari]

Ok so upgrading the fw for the W60B however the issue still persists. Tested by the rebooting the router at the site where the W60B is located after fw update. After re-boot, W60B reg failed. Rebooting the W60B base got it back online again.

Wish I could help you out further but I use a SBC for my connection to the cloud PBX.

 

[leejor]

Wireshark would tell you if a re-registration attempt is occurring when it should , and if so, is something else preventing that from being successful.

 

[complex1]

@Jim Shaflucas

Please replace and change the FQDN into the WAN IP-address of the PBX and try again.
Account > Register > AccountX > SIP Server 1 > Server Host

 

[gbrown100]

I am experiencing the same issue with these Bases. I have 3 of them on two different LAN's connecting using STUN to a cloud PBX. Same error, Register Failed. @complex1 Is this to test or have you got round the issue making this change?

 

[complex1]

Just for test purposes. To see if the base understand/can reach the FQDN after the router re-connect to the internet, thus have to reboot the base to re-register to the PBX.

 

[Jim Shaflucas]

I have it set as the IP address not FQDN in that field, and it's pointing to the PBX internal IP not external public since the base is connected to the PBX via a VPN.

 

[leejor]

I am experiencing the same issue with these Bases. I have 3 of them on two different LAN's connecting using STUN to a cloud PBX. Same error, Register Failed. @complex1 Is this to test or have you got round the issue making this change?

And what does the Activity Log show in error for the attempt....password, user name?

 

[Jim Shaflucas]

In our environment we are only using VPN not STUN at the remote sites.

 

[leejor]

Yeah sorry, I had read up only as far as the post from @gbrown100 and saw STUN mentioned.

I have yet to find a way to delete a post, only edit.

 

[complex1]

@Jim Shaflucas

Sorry I was answering the post from @gbrown100

I suppose you provisioned the W60B as FXS/DECT, not as an extension?

Please check in the base if “Server Expires” in AccountX is set to 120. (registration interval)

In worst case you have to wait 120 sec. after a VPN “outage” that the phone reconnect to the PBX.

 

[gbrown100]

@Jim Shaflucas

Sorry I was answering the post from @gbrown100

I suppose you provisioned the W60B as FXS/DECT, not as an extension?

Please check in the base if “Server Expires” in AccountX is set to 120. (registration interval)

In worst case you have to wait 120 sec. after a VPN “outage” that the phone reconnect to the PBX.

OK, so although I was not on site I could VPN in and access the Base Station's web interface. It showed not registered, making a change in the account (changed fqdn to IP) made it change to registering but nothing ever appeared in the activity monitor and when running a packet capture on the server it never showed that IP address trying to make any sort of registration. It would appear the base station is simply not making any attempt to register. Reboot the base and it immediately registers as normal.

I provisioned as FXS/DECT as per 3CX instructions. These are both behind either a Draytek Vigor 2860 or a Ubiquiti AmpliFi router so I can rule out the firewall (Amplifi has no outbound blocking). 2 out of three of them are as per 3cx template, the third I made a change in the web interface as I wanted each handset on that base to have a different 3cx extension and it wouldn't do that correctly if I used the 3CX interface...

 

[Jim Shaflucas]

So the reg interval is set to 120. Phone never re-connects after the interval. I tried updating the firmware to W60B-77.83.0.25.rom which was just released but having the same issue.
gbrown100...I am basically having the same symptoms. You can get into the base over the VPN but nothing will get it register unless you restart. I am going to run a wireshark as well so see what is going on with it.