Solved Switched ISP - Stun Server Could Not Be Reached

[usat]

We are currently migrating from our cable internet provider to a fiber provider. We have a new static IP with the new provider, and the connection works fine with our LAN. I followed instructions found within the forum stating to set the 3CX server to dynamic IP, restart services and then wait for DNS to update. I changed the network settings to dynamic, restarted the 3CX server completely and waited for the DNS change. The 3CX server constantly stated it was "detecting" the IP on the status page, and after 9hrs, the DNS never updated for our FQDN to the new IP. Additionally, the server was constantly popping up errors stating that the STUN server could not be reached.

To my knowledge, the STUN servers have never been used with this install. I see that stun, stun2, and stun3 are all set to port 5060. Is this the correct port? If not, what would the correct port be? At this time, I have reverted back to our cable internet provider so that our remote users can have access to 3CX, so any assistance would be greatly appreciated.

 

[Saqqara]

Do you have a firewall , have you changed the outbound rules to reflect the new ISP link ?

I have checked a few servers, all the stun servers are set to port 3478

You could try, using static IP and changing the static public IP to see if this works.

 

[usat]

This has been resolved. I'm not sure why our install had port 5060 for the stun servers, but switching it to 3478 absolutely corrected the issue. Thanks Saqqara for the help!

 

[cobaltit]

Someone must have misread something and changed it. STUN for the 3CX instance has always used 3478. But STUN for the endpoints uses 3CX as the STUN server on port 5060.

 

[YiannisH_3CX]

Glad to see the issue has been resolved