v20 Update 7 Outbound rules not working

yogasensai

Free User
Joined
Feb 16, 2023
Messages
21
Reaction score
3
After updating V20 to Update 7 my outbound rules stopped working correctly.

I have 3 rules that say if there is a certain prefix then strip it and call from Outbound caller ID. These rules are working correctly but another 3 rules that use Calls from extension(s) then use Outbound caller ID without striping any digits stopped calling all together.

I could no longer edit my trunks so I deleted them and remade them and now I can get the outbound calls from extension will make a call but they will not use the caller id as set in the outbound rule. This has been working for many years without issue until update 7.

If i change the priority of the rule then only the first rule will work and no other rules work after the first priority.

So many people complaining about bugs since update 7.
 
Can you send us a screenshot of your outbound rules? Why could you not edit your trunks? Also what do you mean by not working? Are you seeing an error in the activity log?
 
I think I have same problem also, I didn't used couple rules before but I have latest version and have same problem.

view the thread : https://www.3cx.com/community/threads/multitenant-mode-and-couple-outbound-rules.135413/post-648033
It doesn't look like the same problem. It looks like you are getting 403 Forbidden errors from your provider. If the calls are leaving 3CX and you are getting an error then your outbound rules work.
Generally for MCM you want to allow calls out based on group. Make sure your extensions and trunk are on the correct group and that's it.
If you have doubts as to who is sending the error then run a pcap and check the SIP messages. This should give you more details.
 
  • Like
Reactions: KyriacosS_3CX
Ok i got it all working again. Took me a day and a half of playing around with all settings.

Here's what I did to get Calls from extension(s) working again in my outbound rules:

1: Deleted the trunks and re-added them. This fixed the problem of when I clicked edit it would just link back to #/people. It also fixed the problem of when we tried to dial out it would just terminate the call. However its still ignoring the Outbound caller ID.

2: To fix the outbound caller id in the rule problem I set: Calls to numbers with a length of = 1-10. Adding this length stopped it from interferring with my other rule that uses 11 digits. And deleted:
Calls from Departments Select which Department(s) can use this outbound rule. We only use one department so this isn't a big problem for us. Maybe there is deeper settings in the department that can be fixed but i couldn't find any.

My day job is a software engineer so I guess some major background core changes were made in update 7 which interferred with all these settings.
 
I am having a similar issue. 3CX seems to be ignoring outbound rules from extensions and departments when used together.
I have duplicate outbound rules for different extensions within a department. The effected extensions are not listed in the duplicate rule, and the rule on top is being processed for the entire department even when the extensions are not included in the rule.
 
Outbound rules match
A call coming in that is either in the named Department or a listed Extension

- if a rule with a Department exists, it will match ALL of that Department + any Extensions from other departments added to that filed - Not Only the Extensions in the list as long as they are in that Department.
 
Outbound rules match
A call coming in that is either in the named Department or a listed Extension

- if a rule with a Department exists, it will match ALL of that Department + any Extensions from other departments added to that filed - Not Only the Extensions in the list as long as they are in that Department.
So like I said it ignores the rule and processes based on the department. What is the point then? If I want to have different outbound caller ID for select users in a department, why wouldn't I be able to use the calls from extension AND department? Rule processing needs to be revamped, you have all the data needed to make the appropriate logic, but for some reason we just want to process rules how we want to and ignore parameters . So now I have to create a separate department for these users so the rule is process correctly. It doesn't have to be like this.
 
You can just enter their extensions, leave department empty.
 

Members Online Now

Forum statistics

Threads
111,832
Messages
589,286
Members
164,662
Latest member
DejanMDS