Solved Outbound rules +44 not working

[templeben]

Hi, my users are using the click to call feature and sometimes the numbers are +44xxxx etc.

I've created an outbound rule to detect calls starting with the number prefix +44, strip the first three digits and prepend with a 0 and use our normal sip trunk. Users get a "called number does not exist" and the dhasboard shows a warning saying:

There was no user or outbound rule found for the number +447917xxxxxxxx that Ext.268 dialed.

We have the same issue if a number is +44(0) .. but one thing at a time!! I'm sure this used to work on v.18

 

[TheodorosG_3CX]

Is there any Department restriction in your outbound rule?

 

[templeben]

I've not specified any department in the outbound rule.. I haven't done this for any of my rules.

 

[TheodorosG_3CX]

How is the outbound rule configured?

 

[templeben]

There was no user or outbound rule found for the number +447xxxxxxxx that Ext.268 dialed.

 

[templeben]

Just for testing, I've assigned the rule to the DEFAULT department, but it still doesn't apply.

 

[TheodorosG_3CX]

If you do not strip digits, does it proceed?

 

[templeben]

No .. still get the same message in the event log.

 

[TheodorosG_3CX]

Is this the only rule or in highest priority?

 

[templeben]

It's third down on the list. I have one rule for numbers starting with a 9 to strip the digit and use the trunk, then I have one rule for numbers 11 digits long to use the trunk, then the rule above.

 

[TheodorosG_3CX]

Set this to the top priority and check please.

 

[templeben]

Sorry ... now top of the list but same result.

 

[TheodorosG_3CX]

Since you have confirmed that this is correctly configured and still fail this might required to be checked further with logs.
You may create a support ticket so we can check further and advice.

 

[templeben]

Hmmm... if this is a bug do I get my support ticket refunded?!

 

[TheodorosG_3CX]

This is not a bug, but in order to identify the misconfiguration we will need to check the logs.
However if this is related with outbound rule you can create only one rule like below example to verify if this is the case:

 

[ENPNOC]

Hi,

Just curious if this has been resolved? I am getting exactly the same issue. We use a different SIP provider (Voiceflex) but I am not able to get the Outbound rule to work as I had hoped.

If we get incoming calls they are prefixed with +44, so when the call is returned we get an error "calls to this number do not exist". I have created the rule as suggested above, put it to the top of the list, tried specifying an extension for it to work from but still no joy, unfortunately.

Would be keen to find out if there is a fix.



I also tried amending the rule as TheororosG_3CX suggested, but that did not work either.

Cheers,

Jon

 

[templeben]

Hi, not resolved yet.I'm convinced its a software bug personally. Glad I'm not the only one having this issue!

I am going to pay for a support ticket because I need a fix, but I can see from the process involved that I need to crank my logging up to verbose first which I can't do during wokring hours.

 

[Evolute IT]

Hi, not resolved yet.I'm convinced its a software bug personally. Glad I'm not the only one having this issue!

I am going to pay for a support ticket because I need a fix, but I can see from the process involved that I need to crank my logging up to verbose first which I can't do during wokring hours.

If you go through a partner (like us), you don't have to pay for the ticket.

 

[Grace Liu]

Please check if the option(disable E164) will help you:

 

[TheodorosG_3CX]

As mentioned this is not a bug.
Checking the outbound rules will eliminate the issue or find where the problem is exactly.
Also E164 is another troubleshooting step however without logs we cannot say where exactly is the misconfiguration.
You need to contact your partner to check and advice.