Solved Correct DID is not being called

[DDSITSupport]

Hi all,
Can you please assist I've come across a bit of an issue with a new Azure built 3CX appliance.
We've recently setup a project to move the on-prem 3CX to cloud and I'm doing the migration but I'm coming across a rather difficult issue.
I have all the DID's setup but it doesn't matter which DID I call I can't get it to go to the correct queue. It always goes to the same "primary DID".
Below is our SIP:

This is the number that is always called when we try call any of the DID's for whatever reason,
Below is our DIDs (I've given a few just for an example):

We have a number of clients that we support each with their own DID to ring. So it's important we are able to segregate the calls properly.
Thanks

 

[PanagiotisL_3CX]

Hello @DDSITSupport

We've seen the reported issue occur when there is a mismatch between the configured DID's (in the PBX) and the format of the number sent from the provider to the PBX. For example if the provider sends the number in E164 and the DID is not, the call will be routed to the 'catch-all' destination. Assuming that this is the cause of the issue, we suggest changing the configuration of the DID's to e.g. *004912 which will match any format sent from the provider.

 

[DDSITSupport]

Hey PanagiotisL
So if I understand this correctly, we're saying that if the number in the PBX is set to (Area code)xxx004912 we should be looking at *(area code)xxx004912 or are we meant to ignore the area code since in my region we drop a 0 before a country code. Which means we would be looking at *xxx004912.


*********
UPDATE
*********

Thanks I've made some adjustments and it's the E164 indeed I had to remove the area code for it to work but it's definitely come through now and passing through to each DID properly.

Thank you kindly,

 

[PanagiotisL_3CX]

@DDSITSupport

You can try both with and without the area code. You can keep a fraction of the DID after the * (minimum of 6 digits).

 

[PanagiotisL_3CX]

*********
UPDATE
*********

Thanks I've made some adjustments and it's the E164 indeed I had to remove the area code for it to work but it's definitely come through now and passing through to each DID properly.

Thank you kindly,

That's great, glad that the issue is resolved.