Solved Trunk not registering after public IP change

[Joao Custodio]

Hi,

We have 3CX working with T4COM for several year, today we moved to a different ISP and our public IP also changed, I managed to get everything up and running except for the T4COM trunk.
We're getting the following error message every 3 min and external calls wont work

SIP Server/Call Manager ID: 12293
Registration at T4COM has failed. Destination (sip:185.49.43.148:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.

Any ideas would be appreciated

Best regards,

 

[AWS2P]

What is you 3cx licence type ? STD? PRO? ENT?
if public IP change and you are on STD or PRO then you need to wait for DNS propagation for FQDN to answer on new IP. It takes few hours.

Is your trunk IP based, if so then ask your SIP Provider to change for your new IP

 

[Joao Custodio]

Thanks for the quick answer, my license is PRO and I've read it may take up to 6h

guess I'll have to wait...

 

[Joao Custodio]

Update...

Got fixed after contacting T4COM