Solved V20 Update 10 issue - Dynamic Public IP issue

[CAOxford]

Hi, since the last night's update (Update 10) my 3CX is misbehaving when setup on Dynamic public IP (I have failover setup).
In the logs it seems to present the Local IP address to the SIP trunk instead of public IP.
If I setup Static public IP, works fine and it reports the public IP to the SIP trunk.

In the dashboard, the detection of the public IP.

 

[Alejandro_3CX]

Hi, If you are using a failover setup for high availability, you should be using a public static IP. Additionally, for both on-premise PBXs, please ensure that you have the split DNS and for the SIP Trunks under the options tab check they are using the default settings.



If your network uses a public dynamic IP instead, you must allow outbound traffic to the following domains:

• Discovery Service: Discover your Public IP ----> discoverv4.3cx.com, 443 (outbound, TCP, uninspected traffic)
• stun2.3cx.com
• stun3.3cx.com
• stun.3cx.com

Please review these settings on your end and let us know how it goes.

Have a good day!

 

[CAOxford]

Hi, Thanks for your quick reply. It is interesting. I did not find your suggested option but I removed the public IPs from the Public IP box and updated the stun servers form your recommended list and it seems to be working now. Why do you have different options?

 

[Alejandro_3CX]

Ok, the option Select which IP to use in 'Contact' (SIP) and 'Connection'(SDP) fields is available for generic sip trunks and other specific voip providers. Gamma has a template and when using it populates the field Public IP in SIP via Header with your static public IP.

About the different stun servers, these are used to detect the public IP used in the network, there are three for redundancy, if one does not respond or is undergoing maintenance, the pbx consults the next one.

 

[CAOxford]

Thanks. You can close this thread.