Solved Outbound Rules

[jpatel]

For the longest time one of our PBXs didn't have an issue, but recently when the users redial a number from their call history starting with +, the call doesn't go past the PBX. Outbound rules haven't changed and we have other PBXs with similar configs and rules (sip trunk, outbound, inbound etc) and don't have this issue including our own PBX. Only recent change is switching from AWS LightSail to Hosted by 3CX.

So if a user has call from a +1 234 567 8910 and redials it, the logging says no outbound rule found, but I clearly have one and even put it to the top. Again same rules exist for my other PBXs and no issue, but this one just started doing this.

No In/Outbound rules exist in SIP trunk, or CallerID rules (nor on other PBXs).
Rule in question is set to strip a digit if + is prefix.




3CX Version: Standard Annual 18.0.2.314
Server: Debian
Is the 3CX Server Hosted and where? 3CX Hosted
IP Phone Make/Model/Firmware version: Yealink T41S version 66.86.05
Provisioning Method: SBC
Trunk Provider: Flowroute
Has the Firewall Checker passed: YES
Are custom Phone Templates being used: NO

 

[Saqqara]

Check the e164 settings under settings

 

[VasilisV_3CX]

Hi @jpatel,

Do you by chance have E164 processing enabled? Try and disabling it, applying and then try it again.

In the E164 settings untick the options: Remove if same Area Code & Remove if same Country before unticking the option Process E164 Numbers.

 

[jpatel]

Thanks fellas. That was the issue. Somehow changed to Ukraine. Changed it back to US. Thanks for your help, cheers!

 

[VasilisV_3CX]

Hi @jpatel,

Great to hear. Note that you can check the new Audit log on v18 systems which will tell you who made the change and when:



You can type E164 into the search field.

If you need anything else, feel free to open a new thread!