Solved Inbound rule doesn't work

[Wookie]

Hello

I'm using a DID to create an inbound rule for a conference.
For example : 0123456789 is used to call the conference extension 7000.

When calling this number, the operator extension is ringing instead of conference one.
I searched and I can't find any redirection for this number.

I tried to use another external number for this extension and it worked.

Do you have any idea about this strange problem please ?

Thanks

 

[SweetAction]

Likely the inbound rule isn't being used because the number isn't matching. You will have to check the logs to see what number is presented when calling in. Oftentimes people do the last 6 of a number on the rule, prefixed with a *, like *123456 because their provider only sends 7 digits, or 10 digits, or with a + or without, etc.

 

[eddv123]

Is this 01234 number the default DDI on your SIP trunk ? if it is I would first check the routing of this number on the trunk itself as it may have an adverse effect on the DDI.

 

[JohnS_3CX]

Hi @Wookie

is 0123456789 entered into your list of trunk DIDs? Sounds like you are receiving a call and the system interprets it as under catch-all because it has not matched to any rules.

Is it entered in the same way the provider sends the call in the invite when calling it externally?

 

[Wookie]

Well, the trunk number isn't the same and the number format in the rule is *123456789, like the others

 

[JohnS_3CX]

Did you add the number in this field?

 

[Wookie]

Sorry, I didn't see your message.
Yes I did, as usual

 

[JohnS_3CX]

It's quite likely that when the call arrives in the trunk it does not match your rule for some reason.

Are you perhaps reformatting the incoming call in a way that "breaks" your incoming rule?

 

[leejor]

Check the 3CX Activity Log. It will show the incoming DID number, and why it routes where it does. No point in wasting time guessing. Compare the log of the non-working number, with one that does work.

 

[Wookie]

Hi all

The problem was from the trunk SIP provider.
The presentation of the number was not activated. So, 3CX didn't "recognize" it and the inbound rule wasn't applied.

Thank you all for your help

 

[JohnS_3CX]

Glad to hear it was resolved @Wookie