Activity log: [CM306002]: There is no valid STUN server specified! External IP can not be resolved.

[Cjay]

Curious to know if anyone else is seeing this message repeated over & over in their activity log?

Possibly I'm misunderstanding the meaning of this message: "There is no valid STUN server specified! External IP can not be resolved", however if I am running a dynamic public IP and:

1. The system does in fact correctly resolve the external IP (resolves & displays correctly in management system)
2. I can capture valid STUN transactions on Wireshark being sent at the interval specified
3. The system is working fine

then to my way of thinking the error message is possibly incorrect?

I'm seeing this behaviour on 2 systems, both running v16.0.4.493 on local machines: One is Windows 10 Pro based, the other Debian. Both systems passed firewall test. The Windows box has STUN set for every 600 seconds and throws the error message every 30 mins, the Debian system is set for STUN every 1200 seconds and throws the message every 40 minutes. The Debian is a totally fresh install. The only other STUN related message in the activity log that shows is:


[blanked IP is that of stun3.3cx.com]
In this case the message is correct. The STUN servers in a default fresh install are stun-eu.3cx.com, stun2.3cx.com & stun3.3cx.com and stun3 resolves to the same IP as stun-eu.3cx.com




Any thoughts/comments on the above most welcome!

 

[JohnS_3CX]

Hi @Cjay

Do you have the following status on your IP that says "detecting" or does it show your correct public IP?

 

[Cjay]

It shows the correct public IP (after initially detecting on startup).