I keep getting the following message in the log- STUN failed to resolve external IP using server 80.239.235.209.
I have tried using three different STUN servers and get the same results with each one.
Hi, if you need STUN then it may be worth checking the firewall settings to ensure that the required ports are opened to the internet, this would usually be UDP port 3478
UDP 3478 is open onthe firewall and routed to the 3CX computer. I don't think I do need STUN, I've set "Which IP to use in 'Contact' field for registration:" to Specified IP with my external static IP but, I still get the messages.
If you have a full cone NAT or what I call one-to-one NAT where you have a public ip tied to a private ip and it is only for that host STUN will not work. I just got back from a class and this was what I found out. STUN was designed for the dynamic ip user and not the static world. To solve my problem I told the system what my external ip was and that fixed any issues with external users. If you have one-to-one NAT you can ignore the STUN error in the logs on the server. It will be handy though on the handset like the Linksys WIP300 I was using from a Hotel in Atlanta during the class. Hope this helps.
If you can please send us a support file ("generate support info" from the 'support' page) to our support mail address with a full description of the tests carried out we would be able to follow through the negotiation and see what might be the issue.
Also new registrations take over old ones so it should not be a re-registration process issue.
Also to dyntech as mbs pointed out, you need to allow outbound STUN traffic from the PBX server.