Solved Trouble setting up Telnyx SIP Trunk

[SOTASOTA]

I have gone through all the guides, and tried setting up Telnyx SIP trunks to my profile.
The trunks simply will not register.






Help please!

[Edited by Administrator]

 

[YiannisH_3CX]

Hello @SOTASOTA

First of all you should not post screenshots with your username and numbers on a public forum. You cannot register the trunk but someone else might manage it. I deleted the screenshots for your own safety.

Regarding your issue, please give us some more info about your setup so we can be in a better position to assist.
Start with these: https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Also are you sure your main trunk number is correct? It seems a bit long to be a valid number.

 

[SOTASOTA]

Oops! Thanks for the heads-up on what not to share.
I also thought the trunk number was very long, but that is what Telnyx shows in the SIP ID#.
There are no other identifying numbers. I have also reached out to Telnyx for help. I cannot imagine I am the only one with this issue. Makes no sense. I also setup this exact same SIP trunk in Yeastar's Cloud-PBX and it registered immediately. So, that is even more bewildering. Help!

 

[Evolute IT]

Oops! Thanks for the heads-up on what not to share.
I also thought the trunk number was very long, but that is what Telnyx shows in the SIP ID#.
There are no other identifying numbers. I have also reached out to Telnyx for help. I cannot imagine I am the only one with this issue. Makes no sense. I also setup this exact same SIP trunk in Yeastar's Cloud-PBX and it registered immediately. So, that is even more bewildering. Help!

Have you used the built-in Telnyx template and set it to register with your username/password Telnyx generated for your connection?

 

[SOTASOTA]

Yes, that is what I did. I selected US...Telnyx...and then put in the data required. Like I mentioned, I used the same template in the Yeastar Cloud-PBX and it worked the first time.

 

[Evolute IT]

I used the same template in the Yeastar Cloud-PBX and it worked the first time.

Don't compare 3CX and Yeastar. Not even close. Not same templates nor even SIP stack.

In your case, check that the credentials are right, that your firewall checker passes and see in the Event Log if you get any errors for the registration.

 

[YiannisH_3CX]

Did you by any chance enable the TLS option?

 

[SOTASOTA]

I tried setting TLS just now...no joy. So I set back to "Any".
Please let me know where the Firewall settings are. I cannot locate them.

 

[SOTASOTA]

I am on your Cloud platform.

 

[SOTASOTA]

Any more ideas? Surely this is easy to fix?

 

[YiannisH_3CX]

Please let me know where the Firewall settings are. I cannot locate them.

The firewall checker button is located on the Dashboard under the "PBX Status" column. Run it once to make sure everything is OK.

I am on your Cloud platform.

Are you using Hosted by 3CX?

Any more ideas? Surely this is easy to fix?

If you are using the 3CX template then yes it should be as easy as adding your username, password and trunk number and it should register. Check your credentials again and see it you get any errors in the activity log that might help us understand what the issue is.

 

[SOTASOTA]

Sorry, I simply cannot get this to work. Any other SIP trunk I add seems to register immediately.
The Firewall checker passes GREEN lights.
Not sure where I find the Activity Log?

 

[SOTASOTA]

I am on the hosted by 3CX system as I setup an account from the 3CX website.

 

[Evolute IT]

Sorry, I simply cannot get this to work. Any other SIP trunk I add seems to register immediately.
The Firewall checker passes GREEN lights.
Not sure where I find the Activity Log?

On the Dashboard, one of the big blue box.

I am on the hosted by 3CX system as I setup an account from the 3CX website.

If you wish, DM me and I can take a look. Otherwise, I think 3CX is supporting you in this case.

 

[SOTASOTA]

Wow, that big blue box right in front of me? Ha!
Here is the log entry:

Registration at Telnyx LLC has failed. Destination (sip:192.76.120.10:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.

and this error:

Registration at Telnyx LLC has failed. Destination (sip:sip.telnyx.com:5061;transport=TLS;lr;maddr=64.16.250.10) is not reachable, DNS error resolving FQDN, or service is not available.

 

[Evolute IT]

Wow, that big blue box right in front of me? Ha!
Here is the log entry:

Registration at Telnyx LLC has failed. Destination (sip:192.76.120.10:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.

and this error:

Registration at Telnyx LLC has failed. Destination (sip:sip.telnyx.com:5061;transport=TLS;lr;maddr=64.16.250.10) is not reachable, DNS error resolving FQDN, or service is not available.

Okay so two things:

1. That looks like a DNS error for some reason. Which is surprising.

2. Have you enabled TLS and uploaded the root cert for the trunk in the Options tab? By default it should use UDP/5060 and not TCP/5061 in TLS.

 

[SOTASOTA]

Hmmm, I selected "Any" for the Transport Protocol. I tried UDP and TCP. Not sure where I enable TLS and not sure where/how I upload the root cert?

 

[Evolute IT]

Hmmm, I selected "Any" for the Transport Protocol. I tried UDP and TCP. Not sure where I enable TLS and not sure where/how I upload the root cert?

If you set it as Any, it should use UDP.

The staff will need to check this out.

 

[SOTASOTA]

I am really surprised by this lack of immediate registration. I am sure I am not the only one trying Telnyx. Pity...
But thanks for trying to resolve this. I might jump away from 3CX now as I have to find a good and reliable solution.

 

[Evolute IT]

I am really surprised by this lack of immediate registration. I am sure I am not the only one trying Telnyx. Pity...
But thanks for trying to resolve this. I might jump away from 3CX now as I have to find a good and reliable solution.

This could be due to many many things and without having an insight into how things are configured, even on the Telnyx side, it's impossible to tell.

Specially, your getting DNS errors which would indicate an issue with the hosting provider network, not 3CX. You could simply move your instance to your own cloud, or, as I said earlier, I can simply take a look with you and see if we can figure it out. I'm curious too as it usually just works. We use Telnyx on MANY PBXs here.