Outbound rules

[choimarc]

Hello,

I have create a group with many extensions in it. I have created an outbound rule that uses this group to block access to using long distance number. I have discovered that if the long distance dialed is 19873130478 and that I have an extension that is 1304, it will use that outbound route because it seems to find 1304 in the number 19873130478. Is this a confirmed bug or is this normal ?

Is there a workaround ?

Thanks.

Marco

 

[pact]

Hi @choimarc

Are you able to provide a screenshot of your outbound rule configuration?

 

[craigreilly]

Sounds like outbound rules not set up properly.

 

[Marari]

Outbound rules match in a top-down way.
The first match (or partial match) that is found, executes that rule. Full stop.

So ...

If a rule exists higher up the list that defines "1304" as an extension, that rule will execute and it will not search for any better match.

 

[eddv123]

I would agree, outbound rule with this one. Although if it were my deployment I would run the Support info file and trace the call with the binary log viewer, it will tell you exactly what is going on:

https://www.3cx.com/docs/collecting-logs-for-3cx-support/
https://www.3cx.com/docs/3cx-log-viewer/

 

[YiannisH_3CX]

Hello @choimarc

I will also agree that this seems as an outbound rule issue however also make sure that the extension is not part of both Groups which will cause it to be able to dial out.

 

[choimarc]

Hello,

Here is some additionnal info:

I have created many inbound rules that takes calls from specific DIDs and transfers them to outside numbers. So in theory, there are no extension involved, no groups either. However, some out of them all used my long-distance blocking outbound rule that was configured with only a specific group as the criteria. That's where i noticed that the outbound number that it's trying to reach contains one of the extension that's in the group. I know it's not a mis-configured outbound rule issue because this rule is the only one before the last outbound rule that sends the call outside. If I move my blocking rule below my last one, all my inbound rules transfers work. If I move it back to it's place, only certain inbound rules will fall in that outbound rule (those that the outbound number contains a match with an extension in the blocking group).

I hope this makes it clearer.

Marco.

 

[choimarc]

Any other ideas with the new info ?

 

[choimarc]

This is the outbound rule. It is working now because I have added manually all the extensions. But when I used the group, and that a call coming in a specific DID that was directly fowarded to an outside number, it seem to use this rule. It should not because the call isn't originating from an extension nor a group. What I noticed though is that if one of the extension in the group is included in the outside number I'm dialing, it goes into this rule.

 

[NickD_3CX]

@choimarc
Thanks for bringing this up. We'll look into it.

 

[choimarc]

Were you able to reproduce the problem ?

 

[NickD_3CX]

Hey!

We did find some inconsistencies in the Outbound Rules behaviors that are similar to what you described. We do plan in addressing this for V16, but I can't say at the moment if it will make it into the first release of V16.