Hi all,
Currently running 3CX on Debian - version 15.5.15502.
This has been running successfully with no issues for the past 12 months.
We transitioned this internet to a new fibre service resulting in a new public IP.
There was no firewall change.
The only thing which was updated on the firewall was the new WAN IP details.
The 3CX PABX has not been successful in connecting to SIP trunk since. Keeps giving the following error.
Registration at "TRUNKNAME" has failed. Destination (sip:[email protected]:5060) is not reachable, DNS error resolving FQDN, or service is not available.
From looking at the packet captures on the firewall. The old WAN IP appears to still be showing when communicating to SIP server even though the SIP message headers in the packet show the new WAN IP
I did a bit of a search on the 3CX forums and they mentioned there is a particular way the WAN IP needs to be changed.
For eg:
Last link mentions the following:
...
"First thing to be aware of is that if you are using a 3CX Supported FQDN (which by your 3cx.fr you are) then your FQDN, Licence and Public IP are now bound together:
https://www.3cx.com/docs/fqdn-management-allocation/"
...
i can ping domain.3cx.com.au however and it shows the correct new IP.
I’ve also tried the suggestions in the above article about changing IP to dynamic IP. Then changing back to Static then waiting a long period. This will still not connect to trunk and packet capture continues to show old WAN IP.
Is there anything else within the 3CX PABX that needs updating regarding public IP's?
help appreciated
Currently running 3CX on Debian - version 15.5.15502.
This has been running successfully with no issues for the past 12 months.
We transitioned this internet to a new fibre service resulting in a new public IP.
There was no firewall change.
The only thing which was updated on the firewall was the new WAN IP details.
The 3CX PABX has not been successful in connecting to SIP trunk since. Keeps giving the following error.
Registration at "TRUNKNAME" has failed. Destination (sip:[email protected]:5060) is not reachable, DNS error resolving FQDN, or service is not available.
From looking at the packet captures on the firewall. The old WAN IP appears to still be showing when communicating to SIP server even though the SIP message headers in the packet show the new WAN IP
I did a bit of a search on the 3CX forums and they mentioned there is a particular way the WAN IP needs to be changed.
For eg:
- https://www.3cx.com/community/threads/change-wan-ip.60345/
- https://www.3cx.com/community/threads/change-public-ip.54252/
- https://www.3cx.com/community/threads/changing-public-ip.53806/
Last link mentions the following:
...
"First thing to be aware of is that if you are using a 3CX Supported FQDN (which by your 3cx.fr you are) then your FQDN, Licence and Public IP are now bound together:
https://www.3cx.com/docs/fqdn-management-allocation/"
...
i can ping domain.3cx.com.au however and it shows the correct new IP.
I’ve also tried the suggestions in the above article about changing IP to dynamic IP. Then changing back to Static then waiting a long period. This will still not connect to trunk and packet capture continues to show old WAN IP.
Is there anything else within the 3CX PABX that needs updating regarding public IP's?
help appreciated
