DID not routing to the correct extension?

[Song]

Hi,

I have assigned a DID for a extension. But everytime I called the DID it just go to the auto attendant. Anyone know what is causing this? Why its not going straight to the extension? I see the incoming route for DID is pointing to extension 123. But calls are still being coming into the auto attedant. Am I missing anything? I think something global is causing this . Where do I check?

thank you

 

[AWS2P]

Have you set an inbound rule? if so can you share a screen copy (hide partially sensitives infos)

This could be a good start too
https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[Song]

Have you set an inbound rule? if so can you share a screen copy (hide partially sensitives infos)

This could be a good start too
https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Yes, inbound rule is setup. please see attached.. Any log or debug and see why it is going into the auto attendant? instead of the extension?

 

[AWS2P]

most probably your rule is not applied because your number is not in same format your sip provider send it. so rule found no matching.
To avoid this problem modify your rule and don't set complete DID number but for example only the last 5 or 6 digits
IF your number is 10 digit ie. 0102030405 , in inbound rule set *030405, try this.

To see some more details set your log in verbose

 

[Song]

still not working. I don't know why. I add CID rule in the inbound rule and added *2221 as that is the last 4 digit of the number you told me and route it to extension 128. But still getting the auto attendant. So strange. . I know it must be something simple.

 

[Saqqara]

you need to setup did rules , not cid - https://www.3cx.com/docs/manual/inbound-did-call-routing/

Check activity log, to see what number is being presented to 3cx and adjust your inbound rule to suit

 

[Song]

I already have my inbound rule setup already with the DID. ok I turned on the activites log and turn on verbose. For some reason it the PATTON Analog Device 4323 FXO gateway is not passing the DID. instead i look closely it is passing the FXO number. So for the DID i dial it uses 000014. Which is for FXO14. So I added the 000014 DID into the DID and added it to the user and it worked!! Wonder why it is not passing the DID instead passing the FXO port. Maybe that is how it work with the PATTON Smart Analog device?

thank you!!

 

[leejor]

It seems that as a default, the 3CX template creates pseudo numbers in the gateway, that are then sent as the DIDs. Your alternative is to modify the template to include the real numbers, or do as you have already, create DID rules to match the numbers the gateway is sending.
https://www.3cx.com/community/threads/grandstream-gxw-4104-breaks-all-inbound-calls.70998/

 

[eddv123]

You customised your own template if I recall so it could likely be an error with this.

You can find out more about what the Patton is doing yourself (unless you want to contact Patton Support who will assist) by running the following command set on the CLI of the unit:

enable
debug call‐router
debug call‐control
debug fxo
debug ccfxo
debug context sip‐gateway signaling detail 5
debug context sip‐gateway transport detail 5
debug context sip‐gateway error

As per: https://www.patton.com/support/kb_art.asp?art=446&p=128

FYI there is no model Patton 4323 - you mean Patton 4324 ?

I have also attached a diagram of how the layout of a standard FXO Patton should look (obviously yours would be x 24 on the FXO interfaces and ports).