STUN registration fails

[Aaron Shirk]

I have a client with an on premise 3CX server ( Pro version 16SC). System has been working great over the last several years. Over the last 2 weeks, I am having a strange issues, STUN provisioned phones will all fail to register at the same time once a week. The only solution i have found is to reset the phones to factory and re-provision. Never had this issue before. Firewall has not changed, 3CX server has not changed (running current release). I can't see anything in the logs to why. Using Yealink T46S phone with current 3CX firmware. This has happened once a week for the last two weeks. Any thoughts on where to look?

 

[ChrisC_3CX]

First thing I would recommend, is, if possible, switching from using STUN to using the 3CX SBC. It requires no firewall configuration on the remote site and also allows you to use PnP provisioning with IP Phones that support it. Plus, it uses the 3CX Tunnel to connect to the 3CX PBX which means you have an extra layer of security for that traffic.

 

[Aaron Shirk]

My apologies, I left off some need information. The site has about 20+ local phones all provisioned as local LAN. A few employees needed an additional phone for "remote working" at home. These are provisioned as STUN. I did not use a SBC because i thought a single phone on a remote network was what STUN was for. So there are about 6 folks with a phone at the office desk and one at their home. Hope this helps

 

[ChrisC_3CX]

In that case I can understand why you are using STUN, but make absolutely sure you have implemented the configuration mentioned in the guide I provided in my previous reply.