Solved YeaLink and WTI Failover

[DCB]

I have a remote YeaLink W60B at a site with a WTI internet failover (locations internet is not stable). Every time the ISP has an issue and the WTI flips over to cellular, the W60B goes offline from the cloud-hosted 3CX. If I reboot the WTI, then W60B registers.

Likewise, when the ISP does come back online, I have to reboot the WTI again so the W60B will re-register back through the hardline.
The LAN IP address of the W60B is not changing, only the WAN IP address.

I'm thinking this is more of an issue with the W60B than 3CX, but wanted to see if anyone here had any thoughts as to why a change in the WAN IP would make the phone unable to see 3CX.

 

[JohnS_3CX]

Hi @DCB

I also think it's probably the device having trouble with this, but it may not necessarily be its fault entirely.

You can go deep and analyze the traffic from the W60 to the WTI, and then from the WTI to the PBX to see who may be responsible, but I can suggest a potentially better solution to try out and tell us if it improves the situation.

Install a 3CX SBC at the client site (on a PC/VM/or even Raspberry Pi) and factory reset the W60. Configure it again as SBC mode using our guide. Ensure you also have the latest firmware that the guide point to.

Hopefully now when the internet link swaps back and forth you are no longer relying on the device + STUN protocol to play nice with the WTI. The SBC should be able to re-establish it's connection with your PBX within a few seconds of the failover, and the W60 will be none the wiser of what just happened.

 

[DCB]

Hello. Just an update to this thread. I put SBC on a Raspberry PI and had it installed. We've tested a couple of times by forcing a fail-over. This morning, the was a brief ISP outage (about 10 minutes) but the SBC appears to mitigate the failover issue.
Good solution. Thank you!

 

[JohnS_3CX]

Happy to hear