Stun Server Error

[hroberts65616]

I have a freshly built 3CX server using Debian. I looked at the Activity log, and it has hundred's of these messages in the log.



When I looked at the stun settings in 3cx I see this:


As this is a new setup, did these change? I can not locate anything in the forums of different stun server settings I should be using.

Thanks,

 

[YiannisH_3CX]

Hi @hroberts65616

Can you please provide more details about your installation? Which PBX version are you running? Did you install the PBX locally or is it a hosted installation?
Do you block any outbound traffic to your firewall? Run the firewall checker located on the Dashboard. Does it pass?

 

[Cjay]

@YiannisH_3CX, Just to confirm what @hroberts65616 is reporting, I commented on this issue back in March of this year.
I have 2 current installs both running behind (the same) dynamic IP address and therefore reliant on STUN. Both versions are local & running v16.0.6.655, one is on a Windows 10 platform & the other on a RPi4 (though previously was on a Debian VM but still with this issue). Both have passed firewall test (though for normal day to day operation I block most port 5060 incoming IP's except those I need). The activity logs are similarly full (either 2 or 3 times/hour) of:

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

The thing is that the External (Dynamic) IP is being resolved and shows correctly on the dashboard.
Both these systems function normally, but the activity logs are full of these spurious STUN error messages!
I believe the other error message is relatively harmless:

 There's another STUN server that resolves to the same IP: 54.37.20.144:3478/UNKNOWN_TRANSPORT fk=0 tgt=; ignored

and is because in the default stun list stun3.3cx.com resolves to the same IP as stun-eu.3cx.com? On my Windows based system I've eliminated this error by using a 3rd party STUN address.