Solved DIDs routing to the wrong extensions

[SethTalley]

I have one Telnyx trunk with nine DIDs, xxx.xxx.xxx1 through .xxx9.

I have nine extensions, x101 through x109.

I have nine Inbound rules, xxx1 goes to x101, xxx2 goes to x102, etc, in and out of office. They are unnamed, and in numerical order

MMS to xxx1 go to ext. x101 etc.

MMS from x101 goes out on xxx1 etc.

Calls from x101 shows up with caller ID xxx1 etc.

I have no ring groups.

I have no call queues.

My only Digital Receptionist is the Out Of Office IVR

BUT

• With "Call Source Identification" and "Use both CSI and Caller Number/Name" checked, all calls coming in on xxx1-xxx9 go to Ext. x109.
• With "call Source Identification" checked and "Use both CSI/CNN" unchecked, all calls coming in on xxx1-xxx9 go to Ext. x109.
• With "Call Source identification" unchecked, all calls coming in on xxx1-xxx9 go to Ext. x101.

I'm sure I missed something simple and I would love it if someone clever could tell me what it is. That whole "Call Source Identification" thing was from the forums but that was as far as I got.

Thanks in advance!

 

[SethTalley]

Except it doesn't work that way - or at least, it doesn't work that way anymore, or at least it doesn't work that way anymore with 3CX hosted, or it doesn't work with the 3CX hosted/Telnyx combo. You have to:

1) Create the DID. Is it going to respond to wild cards?

2) Add it as a DID for the user.

3) The Inbound Rule appears.

None of that is editable - once the DID has been created, it can only be deleted.

I have a mix of "+1234567890" (which I know is not working correctly) and "23456789" (which are). I suspect I will have to delete all the +1 numbers and rebuild them with 234 numbers.

If I create the DID as "*xxxxxxxxx8" it sends it to the wrong extension again.

The only thing that works is

- Create the DID in 1234567890 format

- Add that DID to the User

- Inbound Rule is automatically generated.

 

[leejor]

You have to keep in mind....E164 is a number standard, and most people think of it as those phone numbers starting with a +. When a provider specifies that , it is usually referring to the numbers it wants to see from you.

Which is all well and good for numbers you are (dialing) sending to a provider. With a leading +, the provider knows that next digits are the country code, then the area code, office code, and line number. It really doesn't matter if it is local, or international, you give them the full number in any case.

When it comes to DID numbers, sent to you, it isn't quite as critical. For one thing, you already know what DIDs are going to be sent to you, and usually, you don't even require a country code. Most 3CX users could probably use *XXXXX to do a match on just the last few digits of the number.

So while there may be some providers that choose to send a leading + and the full number, as a DID, in the big scheme of things, it's not really needed, and many don't bother.

 

[YiannisH_3CX]

How should I configure my inbound rules and DIDs in such a way as to bomb-proof them? I can see this leading to a discussion between 3CX and Telnyx at which point whatever rules I rewrite today may break next week...

Glad to see you got it working. Telnyx will send the numbers to you in a specific format every time. That format is configurable from their customer portal. if its set up for E164 without the "+" then Its not likely to change unless you change it. So adding your DIDs in the "1XXXXXXXXXXX" formal is going to work for you.

Wildcards do work if configured correctly but you do not need them if you know the format the provider is using which you now do. So configure your DIDs to follow that format and you are done.

You can edit your DIDs from the sip trunk settings / DIDs tab and your inbound rules should auto update.