Remote Phones Registration Failed

[HalcyonDays992]

I have 3CX deployed to my google cloud account with remote phones at 3 separate locations. I'm using Yealink T21P-E2 handsets all updated to the recommended firmware. The problem I'm having is that in one of the locations, when I provision a phone it will provision, get the 3cx phonebook, but fail to register.

• I have unticked the "Disallow use of extension outside the LAN (Remote extensions using Direct SIP or STUN will be blocked)" option.
• I can successfully provision and register the phones on another network
• If I change the transport mode to TCP from UDP, the phones will successfully register but there is no audio on the calls to other extensions. (oddly external calls and calls to my android soft phone work fine)
• I have two other phones working on that network and all settings on the phone and on the 3CX management console are identical with the exception of username and password.
• The network subnet is different than my other networks (192.168.88.xxx)
• The network's outside IP address is not blacklisted.

Any thoughts are very much appreciated.

 

[Saqqara]

Have you configured different SIP port and RTP ports as per info here - https://www.3cx.com/community/threa...etgear-nighthawk-x4s-d7800.54620/#post-225296. As you have multiply stun phones on the same network you probably need to setup port forwarding

Have you tried provisioning the phone using RPS Server, enter the settings into management console, factory default the phone

 

[HalcyonDays992]

Thanks Saqqara!

Incrementing the SIP and RTP ports did the trick for registration.

For the no audio between extensions I had to enable "PBX delivers audio" I'm setting up a Raspberry Pi SBC for each site now.