3CX App stopping Yealinks registering

[hornetsoft]

I have an issue where the 3CX Windows App seems to be stopping a Yealink T40G from registering I reboot the deskphone and it comes back up.

When it occurs the 3CX Windows App is shown in the list of Phones and the T40G is not then I reboot and the App disappears from the Phones list and the T40G reappears.

It seems to be like I can only use one device ?

Pro version 16.0.910 hosted on OVH
Yealink T40G on latest FW

I have 15 other 3CX hosted and setup the same way with no issues.

Rich

 

[Saqqara]

How are the phones provisioned - sbc or stun

How many devices at the remote site ?

 

[hornetsoft]

Stun and about 20 handsets across two sites 50/50 some have handset windows app in CTi mode and the Android App just in case they leave their desk and go into a factory.

 

[Saqqara]

As you have configured the phones as stun, have you configured to the phones to 3CX requirements

1. Each phone requires different sip ports
2. Each phones requires different rtp audio ports
3. You need to give each phone a fixed ip address, and setup both forwarding on the firewall for the above ports.

More info here - https://www.3cx.com/community/threa...etgear-nighthawk-x4s-d7800.54620/#post-225296

 

[Saqqara]

As you have this amount of remote phones, you maybe better off installing SBC

 

[hornetsoft]

The 3cx is hosted on OVH where does the SBC reside please ?

 

[hornetsoft]

I have had a look at SBC and looks like I need to install a small windows app local to each site that talks back to the pbx then I point the phones at the SBC in each site. Then I change the provisioning in each extension to sbc instead ?

Rich

 

[JohnS_3CX]

Hi Rich,

That's correct. The SBC will help your phones talk to the PBX using the built in tunnel, and should solve NAT and Port related issues in general (which can potentially cause the problem you faced). The desktop app is not really related to your phone deregistering, I think that was just a coincidence.

You can install the SBC, and reprovision the one problematic T40G phone in SBC mode which should help you with the problem. Just make sure your PBX, templates and firmware are also updated to the latest 3CX provides before you go ahead.

I would recommend to run the SBC on a machine that is dedicated for this cause. You have the option to install it on Windows 10, Debian (using our provided ISO file) or even a Raspberry Pi 3B+. This machine will have to run at all times to keep the SBC online.

 

[hornetsoft]

I installed it on a server that does not do a lot in the network and reconfigured half the phones so far and our issues seem to have gone its simple to use did it on our inhouse 3CX first and was so simple to use will roll it out to others install now.

Regards Rich

 

[JohnS_3CX]

Hi Rich,

Glad to hear it's going well. Let us know in case you need any further assistance.

PS: If you have an in-house PBX (where the phones are local on the same network) then you do not need an SBC for this one. You mainly consider an SBC when the phones and the PBX are not on the same network (ie. like your OVH cloud PBX, or remote office that is not connected via VPN to the main office network for example)

 

[hornetsoft]

I wish I had looked into the SBC before its great takes a lot of hassle out of things.