Solved Multiple DIDs on SIP trunk routing

[wildmanmatt]

Hi,

I have 5 DIDs on the same sip trunk and I need to route calls coming in differently for each DID. I've setup ring groups and incoming routing rules but it doesn't seem to make any difference, each incoming number just follows the same route which is the default setup on the sip trunk.

For some reason, the 3cx system doesn't seem to be seeing the different incoming DIDs and routing them as setup.

It's probably that I haven't identified them properly or in the format sent by the trunk. But I've tried different formats... With the leading 0, without, with the country code in place of the leading zero and none seem to make a difference.

Which log should I be looking in to see the exact data sent by the sip trunk?

Or is there anything else I might be missing?

Thanks,

 

[leejor]

I suspect the issue is that the numbers in your DID rules don't match the DID numbers being sent, exactly. The call will then take the default route. This is quite a common problem. Use the * wildcard, to replace all but the last 5 digits of the DID number, in the rules.
You can confirm what number is being sent if you use the 3CX Activity Log, which may have to be set to Verbose, to see all the details.

 

[YiannisH_3CX]

If you are not using a 3CX supported provider your issue might also be that you are reading the called number from the wrong SIP header. You can adjust that from the inbound parameters of the trunk once you identified where the called number is sent.
To be fair 99% of the times its in the To:UserPart but its worth checking if you are having issues.

 

[wildmanmatt]

Thanks for the replies. The provider hadn't setup the sip trunk to send the DDIs correctly. After sending them the logs, they sorted it out.

 

[YiannisH_3CX]

Glad to see you got this sorted