Solved-Outbound rules not working

[eric.anderson@trailheadma]

Hello, I have a situation where I must be missing something, but can't figure it out. I'm currently running Version 15.5.15502

I'm trying to set up OB rules so that if a client requested not to be called again for whatever reason 3CX will just automatically disconnect the call if someone tries to call them again. Simple enough, right? However, my OB rules are not working.

Under the OB rules I'm testing it out with my own number first.

I add 4 separate outbound rules for my number trying to figure out which format I should use initially, however even with all of them implemented I can still make a call out to my number.

Here's the OB rules I currently have setup:

1. Just my number alone (e.g. xxxyyyzzzz)
2. '1' then my number (e.g. 1xxxyyyzzzz)
3. '+1' then my number (e.g. +1xxxyyyzzzz)
4. '*' then my number (e.g. *xxxyyyzzzz)

Even with all 4 of these rules in place. I can still call my number.

Here's what I've tried so far on all 4 of these OB rules:
I put down BLOCK CALLS for everything under 'Make outbound calls on'. I can still call my number.
I add the department I'm a group of. I can still call my number.
I add all the departments we have including the one I'm attached to. I can still call my number.
I add the specific extension I'm calling from. I can still call my number.
I add all the departments and the extension I'm calling from. I can still call my number.
Please note, with doing all of these changes I press the 'ok' button on 3CX each time I make a change. I've also restarted the 3CX client every time I make a change, just in case a change wasn't coming through. I can still call my number.

All the forum posts I've come across about this issue in particular have literally said add an OB rule and it should be good. So I'm thinking I must be missing something in this setup. Any insight on this issue is appreciated.

 

[eric.anderson@trailheadma]

I did some fiddling around with it. I literally had to move my 1st rule (e.g. xxxyyyzzzz) to take precedence by moving it above the other OB rules I already had in place. Leaving this up in case anyone else comes across the same issue

 

[leejor]

The rules are (and always have been), read by 3CX from top to bottom. So...if you want a single number to route somewhere other than the "general" catch-all rule, it must be above that rule

 

[AWS2P]

you don't need to create an outbound rule for each extension, this is not an issue, OB rules needs to be sorted logically to be executed, otherwise they won't be

 

[leejor]

If you cannot figure out why outbound calls are still working, when trying to block them, then use the 3CX Activity log. it will show you which rule was matched and the call is following.

 

[eric.anderson@trailheadma]

Thanks everyone for your help. And leejor that's exactly what I did next. I looked at the logs for a few of my calls and noticed the outbound rule it was being attached to.