3cx and yealink

[mrvdh]

Hi all,

I am trying to provision our first in office phone but am having trouble. This would be for a yealink T31G. I have followed the instructions on how to provision the phone through 3cx on site. The phone does provision, but then shows the "not registered" error on the home screen. We are hosting our 3cx on Amazon aws, not sure if there is anything that needs to be done through the aws side to allow for connection. Please let me know if any information is needed, any help is appreciated. Thanks.

 

[CentrexJ]

You should be using an SBC, or purchase an SBC capable phone. Connecting the phone direct to the PBX without an SBC/SBC Phone is unsupported.

 

[richiewhite]

Have you installed an SBC on site and configured the T31G to connect to it?

If you've added it using the Local LAN/VPN option, you're going to have a bad time as there's no NAT traversal enabled.

See Step 3 here: https://www.3cx.com/sip-phones/yealink-t3-series/, specifically the 3CX is in the cloud section. It's possible to set up a custom template to enable the device to connect to a remote/cloud system with STUN (NAT traversal) configured, but this is not supported by 3CX, and is really for cowboys who can handle their own support.

 

[mrvdh]

Thanks for the replies, I have not installed an SBC on site which is what I thought is the issue. I will need to get another phone type as it looks like the T31G is not on the list of covered yealink SBC phones. Question-can I get one SBC phone setup on site, and once that occurs, can the other phones (T31Gs) be added as a local LAN option and be provisioned/registered?

Thanks.

 

[richiewhite]

Yup, any of the router phones should be able to handle ~10 devices behind them, so you'd be all good. Instead of the Local LAN option when you're setting up a T31G, you should see the Connect via SBC/Router phone option isn't greyed out anymore once you've got one of these set up. The main thing is that the router phone/SBC needs to be on the same LAN as its dependent phones, or at least able to route to its local IP.

 

[mrvdh]

Hi there, so I have installed a yealink T53 which looks to be a router phone. I am still getting the account unregistered warning on the phone and "no service" on the LED screen. When I provisioned the phone through 3cx, it only gave me the option to connect directly which I chose. It has been provisioned and I was able to update the firmware of the phone to the recommended version 96.86.0.81. The last warning I am getting in the event logs in the following:

Trunk SBC 'Yealink T53 (1000)' (66.206.116.146/192.168.6.171) has changed status to Up I also did go in and change the transport option to TCP for the sip server 1 option. Any other thoughts as to why it is not registering the line?

 

[AnotherIT]

Depending on the number of phones, you maybe better off installing locally an sbc server https://www.3cx.com/docs/3cx-tunnel-session-border-controller/

As above router phones, can only handle 10 physical handsets

 

[mrvdh]

Well we are only connecting 5 phones through the router phone so not sure if we need to install the machine onto our local server. The 3cx pbx is being hosted on an aws instance. I am wondering if perhaps there is a setting that is missing in the yealink T53 that tunnels to the aws instance? I am not able to find through the yealink where it lists the ip address connection to the aws server through port 5090. Should this be listed somewhere so I can check that it is listed correctly on the yealink side? I will check our firewall as well to make sure port 5090 is open as I tried to ping the aws server IP address running the pbx from the yealink web portal and nothing was returned.

 

[mrvdh]

Ok, I have confirmed that by default all outgoing traffic is allowed but certain ports are restricted for incoming traffic. I am trying to explain to my contract IT person how 3cx may use port 5090 for a tunnel connection to aws, but he is not understanding. Is this correct that 3cx uses port 5090 to register the phone with the pbx hosted in the cloud?

 

[NicholasP_3CX]

Please make sure your phone is on the proper 3CX firmware to actually have the SBC functionality. The firmware should be upgraded before provisioning.

https://www.3cx.com/docs/phone-firmwares/

 

[fortech]

Footnote to thread, if you did not do so already, you may want to review this 3cx support doc,
https://www.3cx.com/docs/manual/firewall-router-configuration/#h.2b54zvy76urs

which discusses possible firewall port requirements to have 3cx functioning happily. <> with your on prem phone handsets.

ie, if your office location has a perimeter firewall that is blocking outbound traffic by default for example
you may need to have your firewall admin review the guide above, and open up some ports as permitted-outbound

note that many sites have more permissive "Allow any outbound..." and won't experience these problems
but if your firewall is 'more seriously locked down' then - some firewall admin intervention might be necessary

you may also want to do some basic sanity testing of your 3cx functionality, by using the 'good baseline test' of simply
- laptop inside the office, web browser > hit your 3cx instance
- use the web-based 3cx client with your EXT logged in thus
- test to make sure both outbound and inbound calling behaves as expected (ie, call to cellular phone and validate it works and sounds good; then call from cellphone to your 3cx DID>your EXT and make sure that too works as expected using the web3cxClient.
- once you have thoese tests done at very least you have a good easy solid baseline of "yes this should work" established.

hope this is maybe slightly helpful. Good luck with the debugging..

Tim