Inbound rules - Redirecting to main number

[Informma]

Hi all,

I have and SIP trunk configured with some DIDs.
All DIDs are configureds to internal extensions, but some DIDs are working fine (when I call, it goes to the correct extension) and some DIDs are not (when I call, it goes to the main number).
For example, when I call DID xxxx6819, it goes to the main number (1000) and not the the extension 1013.

• 3CX Version, e.g. Professional Annual 18.0.3.450
• Is the 3CX Server Hosted and where? Google

Can someone help me?

 

[Saqqara]

3cx can match the incoming ddi number, so is using main number routing

check the activity log, and see what number is being presented to 3cx

adjust your ddi rule, on the info you see in the activity log.

you can use * in the ddi rule , I.e. *87654321 will match 0987654321

 

[Informma]

3cx can match the incoming ddi number, so is using main number routing

check the activity log, and see what number is being presented to 3cx

adjust your ddi rule, on the info you see in the activity log.

you can use * in the ddi rule , I.e. *87654321 will match 0987654321

Hello Saqqara,

Tks for your answer.

In the activity log I can't find the number is being presented to 3CX as you can see below.
Where can I find it, do you know?

I believe you are right and probably the problem is in the number presented to 3CX.

Tks

04/03/2022 1:38:21 PM - [CM503003]: Call(C:2): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5063

04/03/2022 1:38:06 PM - [CM503003]: Call(C:2): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

04/03/2022 1:31:52 PM - [CM503003]: Call(C:1): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

04/03/2022 1:31:52 PM - [CM503003]: Call(C:1): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

04/03/2022 1:31:51 PM - [CM503003]: Call(C:1): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

04/03/2022 1:31:50 PM - [CM503003]: Call(C:1): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

04/03/2022 1:31:49 PM - [CM503003]: Call(C:1): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

04/03/2022 1:31:48 PM - [CM503003]: Call(C:1): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

04/03/2022 1:31:44 PM - [CM503003]: Call(C:1): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

04/03/2022 1:24:32 PM - STUN discovery of public IP is disabled

 

[leejor]

If you have not yet done so, you may have to set the Activity Logging level to Verbose, to see the details.

 

[Informma]

If you have not yet done so, you may have to set the Activity Logging level to Verbose, to see the details.

Thank you all for helping me.

With detailed activity log I can see the sip provider is sending wrong did.

 

[ChrisC_3CX]

Glad to see you identified the issue.

If that DID is unique to your PBX you could potentially add it to the SIP Trunks configuration and use it to get the desired routing until the SIP Provider sorts it out. Keep both the wrong and correct DID along with their Inbound Rules and just delete the wrong DIDs once the SIP Provider sorts it out.