Registration at XXX has failed. Destination (sip:X.X.X.X:5060;transport=TCP;lr) is not reachable, DNS error resolving FQDN, or service is not

[jaraxle]

Hi everyone,

We just completed a migration from on prem to 3CX hosted cloud and we are having issues with our SIP Trunk. We are currently getting the error listed on the title. Any help would be appreciated.

Thanks!

 

[AndreasPo_3CX]

Hello @jaraxle

What SIP trunk provider are you using when seeing this message?
Is it listed in our supported providers list here? https://www.3cx.com/partners/sip-trunks/
If not, have you tried configuring a supported provider and do you still get the same issue?

 

[jaraxle]

Hi @AndreasPo_3CX,

Thanks for the reply. We had to revert back to on-prem because we could not get it working. We were assured by our Account Manager that our current SIP trunk provider would work and with that we gave the migration the green light. We are currently using Westman Communications for the SIP Trunks which is not listed in your supported providers list. We have not tried configuring it with a different SIP provider yet. Another layer of complexity to the setup is they have 14 DIDs that also need to be ported over if we switch to another SIP Provider.

The on-prem infrastructure is currently still on version 16, our client handsets are T29Gs which do not support auto provisioning in version 18 but we are replacing all the handsets to T46Us and have them ready, in fact we got them configured and provisioned on the hosted environment already. A couple of their T29Gs have already died, some are finicky and work half the time so we want them moved to the new handsets and hosted environment. Is there anyway to get our current SIP provider compatible/working with the hosted environment temporarily? The idea is to get this working with the current SIP provider to get the business up and running with functional phones and then move to a different supported SIP provider after as well as port the DIDs.

Thanks,

 

[cobaltit]

I'm just guessing but they may have a local device your 3CX was talking to directly, or the SIP server may only be reachable over their provided internet connection assuming they provide the internet and SIP. You can also go the other route and port your numbers first and then move to the cloud. Or you could move to the cloud with a new provider and just call forward your existing numbers to temporary numbers while you wait for the port if moving to the cloud is the urgency.