Outbound rules to be selected by which Department you are in doesn't work.

[Steve Jones]

We were looking to use the Departments function within the outbound rules section to force certain CLI for certain users.

But it seems (under a test) that a new rule created even if you select a specific dept or even set which ext can use the rule.

Any user on the system can dial the prefix we are using as a test (so we know it's using that outbound rule)

Any idea why the Department setting is not barring people from for example the Default group which has in theory no access to that outbound rule?

 

[paulodagraca]

Hello @Steve Jones ,

Can you please check ALL the outbound rule from the top down, to see if there is any rule that will match what you dial out above the rule you have setup.

The 3CX will stop at the first rule that does have a match, and will NOT check for any 'better' match.

So if the rule outbound rule you think should be taken is lower in the list, it will never exeute.

If you can find it, place a screenshot here of the outbound rules and tell us what you try to dial out.

Paulo

 

[paulodagraca]

ALso, could it be the provider not supporting the outbound number?

Have you already got it working on any other extension, meaning dialing out with 'other' number than the default one?

If not than check provider / SIP trunk setup first.

Paulo

 

[SteveITS]

I seem to recall seeing a similar post online somewhere recently, actually.

I had a couple minutes so I tested it, and was unable to replicate this, on 20u6, with the "test" rule at the top of the list and the caller not in the selected department. Prefix 99 strip 2 would fail to call out, until I added the caller to the department.

The Medium verbosity setting will show the routing in the activity log. ("...Target endpoint for 99_______ is Out#:>>Rule{test}>>99...")

 

[leejor]

Any user on the system can dial the prefix we are using as a test (so we know it's using that outbound rule)

The 3CX Activity Log will also confirm which rule is being used, in the event there are other rules, that could allow the calls to go through.

 

[Steve Jones]

Here are the two screen shots, (just so you know the #### is where my mobile number is entered)
So in theory only me in the department "Steve Jones" should be able to dial 555 and which forces the system to dial my mobile.
But any user can dial 555

 

[KyriacosS_3CX]

In the Outbound rules some elements are OR and some are AND. Avoid using an extension and a Department limit at the same time.

Also here I would leave the length empty.

The below, with the right department, should be enough (I tested calling my mobile when dialing 555 and being in the Default dep, where other users not in it could not -
Set limits to 555 prefix and Department needed, nothing else.
Rule was placed first, but should work as second in your case.
stripping 3 digits and prepending my whole number):

 

[Steve Jones]

Thanks for the reply I did start with just department I only added Ext and call length to see if it wasn't strict enough.
Let me go back and try again

 

[Steve Jones]

Ok we have retested and it does work as expected after I change the initial dial to 600 not 555 turns out in previous testing stuff 555 was a short code to my mobile DOH!

 

[KyriacosS_3CX]

OK, thanks for confirming things are as they should be, since I really couldn't replicate that behaviour

 

[KyriacosS_3CX]

Also leaving a general comment - if you need to have some custom dial/shortcodes, avoid making them the same length as extensions, even if that number is free now, the system could assign something to it in the future.

 

[Steve Jones]

I take your point, about the length but that was only because we were testing on a live system, the final result was to prove we would alter the caller ID depending on the Department you are in, the final rule will be to dial any external number...we just used the short number to prove the call routing logic