Solved Unable to Add Yealink T54W as Local Phone

[JeremyUSEZER]

Hi All, I am actually new to 3cx and trying to work through things as I go, recently i onboarded a few Yealink (T54W) phones for a client and set them up as local phone but the registration kept failing, even when I switched to a different network if kept failing, but adding the phones as SBS (router Phones) works without any issues.

I tried upgrading the firmware, Resetting the device and trying to configure different Yealink T54W phones but it was all the same.
Our system is Azure Hosted, the client has phones connected from Melbourne (AUS) and Sydney (AUS), the Melbourne site also has the same phones, and they work fine as local phones, only the Sydney site has this issue.

I am unable to figure out where the problem is as the same issue happens even when I try it from a hotspot network as opposed to the site network.

I have some trace logs I can share if that would help narrow the issue, I would really appreciate any guidance on this issue.

Regards
Jeremy

 

[richiewhite]

Do you have an SBC on site in addition to these phones, or are you adding them as local phones connecting directly over the internet to the Azure hosted 3CX system, assuming you don't have any VPN or other private link to Azure?

Per https://www.3cx.com/sip-phones/yealink-t5-series/
Router Phone - A Router Phone or an SBC is required to bundle all SIP traffic over a single TCP port and direct the signalling to the IP Phones. At least one Router Phone is required if your 3CX System is in the cloud or its remote phone connected to an on premise system.

Local phones are designed to connect to a 3CX system on the same local network, or via an SBC/Router Phone on the network. It seems you've gotten lucky with your Melbourne site if they're working! The Local Phone template doesn't set up any NAT traversal, so you're probably seeing traffic not being returned to the device.

Is there a reason you don't want to set them up as router phones? Ideally you'd be doing that rather than trying to mess around with working out why they don't work as local phones. I've myself not had any issues with running multiple router phones, but you could definitely get away with setting one as a router phone, and the others as local phones connected to the router phone.

 

[JeremyUSEZER]

Thank you for the response, and no there is no SBC setup on the site, i am adding the phone directly over the internet to the Azure hosted 3CX system.

I honestly (neither does the client) don't have any issues with keeping the phones as router phones, like i mentioned earlier I am very new to 3cx and was thinking that having it as local phones is the correct way, but I will keep it as it is if it will not cause any issues along the way.

I have also added each phone as it's own router phone, so it does not rely on another phone to be online.