Remote clients “not registered” after Unifi router upgrade

MoboPro

SOHO User
Joined
Feb 3, 2025
Messages
4
Reaction score
0
I’ve been using a UniFi USG router and Could Key for years. We self host 3CX v20 with Bulk VS as our trunk provider and have had no issues. We have several Yealink phones on the local network and one remote user in the Philippines with the Windows Microsoft Store client (20.0.664.0).

Yesterday, I upgraded the USG router to a new UniFi Cloud Gateway Express. I setup all the former port forwarding rules exactly the same as they were (5001, 2195-2196, 9000-10999, 5090, & SIP on 5260). 3CX firewall check reports all OK.

All physical phones on the LAN, as well as my iOS client outside the LAN are working perfectly just as they were, however the remote worker in the Philippines with the 3CX Windows Client is showing as “not registered” and he can’t receive calls. I tried resetting his password. He is able to visit our instance at “https//ourdomain.3cx.us:5001” to change password and log in, but remains unregistered.

I setup a brand new user and tested from outside the network using the Chrome Webapp (clicked the bell to allow notifications). It’s the same story. I get the email invite, I set my password and login, I can navigate the 3CX interface, but I’m showing as “not registered” I'm able to make outgoing calls just fine, but can't receive.

Seems like I’m missing something simple here, but can’t figure out what. I drilled through all the UniFi settings but can’t see any differences between the old setup and the new one that would cause this. Seems weird that my iOS client works outside the network, seeming to indicate it's not excluding all external clients.

In the 3CX Activity Log is do see this message: “There is no valid STUN server specified! external IP cannot be resolved”, but not sure that's related

Again, just to clarify, everything was working yesterday and the only change was the router, although I can't identify any differences in the settings between old and new router.

Any ideas?

  • 3CX Version, Version 20.0 Update 4 (Build 487 Release)
  • Server OS, Debian
  • Is the 3CX Server Hosted and where? e.g. On-premises
  • IP Phone Make/Model/Firmware version, Windows Client (20.0.664.0), Chrome Client
  • Provisioning Method: Local
  • Trunk Provider or VoIP Gateway Make/Model, Bulk VS
  • Has the Firewall Checker passed: YES /
  • Are custom Phone Templates being used: N/A
 
We have tried reinstalling the Windows client and rebooting the computer, No change. I should also add that the IP is not black-listed.
 
Another update: the remote employee was able to try the mobile phone client and that does work. Unfortunately this is a call center type position, so they cannot use their mobile phone regularly. We still need to diagnose the root issue with the Windows client.
 
Update: I installed the Windows app on a spare machine here in the USA, and it is able to register just fine. So we have a Windows machine in the USA that can register, a smart phone in the Philippines that can register, and a Windows machine in the Philippines that can't register.
 
Was the smartphone on their same wireless/network or cellular data?

Is this a laptop they can take to another network to try?
 

Latest Posts

Forum statistics

Threads
111,962
Messages
589,996
Members
164,867
Latest member
swegner