Solved Issue with second DID with Telnyx Sip Trunk

[andrewm30]

Currently on latest version of 3cx.

I have a Telnyx sip trunk. Main DID(original number) - 0330 - rings the ring group without issue.

Adding a second DID under the sip trunk, and pointing it to the same ring group, or creating another, and pointing it to that one - does not work. It fast rings indefinitely.

The only way I've gotten this to work - is by adding another Telnyx sip trunk to 3cx, with the second DID - then it functions normally.

Has anyone else experienced this or know what the resolution is? I've reached out to Telnyx, and they don't seem to know why it wouldn't work with a single Telnyx trunk and wanted me to reach out to 3cx.

 

[YiannisH_3CX]

Hello @andrewm30

Please note that Telnyx sends incoming numbers in the E164 format (e.g +13012345678) so add your DIDs in the same format to avoid call routing issues.

 

[andrewm30]

Thanks for the reply Yiannis, I have it set that way on both DIDs

 

[andrewm30]

Just to clarify - it was already set to that standard, so thats not the issue - its somethign with 3cx with Telnyx sip trunks - I have zero issues with Freepbx.,

 

[leejor]

Does the 3CX Activity Log show why the calls are not working. There may be some clues in there. Look for the difference between a working, and non-working call.

 

[andrewm30]

So I looked at the activity log - nothing there when the call comes in with it set on the same Telnyx Trunk.

Something Interesting: I moved it to another clients 3cx with a Telnyx trunk, and it works without creating another trunk.

Seems like its actually an issue with the 3cx install on this Box.

 

[andrewm30]

Additionally, it looks like some of the changes I've made - such as removing a name from someone extension - is still showing up as that persons name in the call log - even after restarting the machine/services.

I may reinstall.

 

[leejor]

So I looked at the activity log - nothing there when the call comes in with it set on the same Telnyx Trunk.

That would seem to indicate that the call never reaches 3CX. i would enlist he help of your provider and see if they can tell you what happens to that call.

Additionally, it looks like some of the changes I've made - such as removing a name from someone extension - is still showing up as that persons name in the call log - even after restarting the machine/services.

So...if that person calls your extension, their name is still showing on the caller ID? Was it ever put into the setting on the set.

 

[andrewm30]

I fixed the name issue on the extension - when it was provisioned it added to the phone - when I redid the extension - it never removed the name.

On to the other issue with the DID...

I turned on Medium verbose and I'm able to see the call hitting 3cx now.

07/24/2018 6:02:22 PM - [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:

Thats what I'm getting when I try to call the second DID in the list under the trunk.

Here is the odd thing, I have added the number I'm trying to call, to another 3cx system(obviously different public IP)..Identical setup. The other difference is the auth on the trunk - the DID's are different. but thats to be expected. They are different offices.

This is why adding a second trunk fixes the issue on the problematic 3cx install.

It literally makes no sense - they are IDENTICALLY setup in both telnyx, and on 3cx.

I have reached out to their support about this issue. The auth methods are setup the same for both connections on Telnyx. Settings Identical on trunks on both 3cx system.

I'm not sure where the problem lies. I've tried multiple DIDs too, to rule out a problematic issue - but its obvious its somethign with the authentication - either from 3cx to telnyx or vice versa.

 

[andrewm30]

I fixed it:

I reset the inbound DID parameters on the trunk and it fixed it.

I may of had them wrong on the initial setup - I'm not sure - but additional DID's are now working

Sorry for all the posts

Thanks

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution