Country Blocking Feature wrongly reporting 001 as a blocked country

[XionicFire]

Hi,

Mexican telecom law states to dial from Mexico to the USA you need to dial 001 + (Area Code) + 7 digit number

The problem is 3CX detects 001 as an un allowed country, however there's no such country so there's no way to enable this, all countries are enabled.

We get this error:
Call from [XXXX] to [001305555XXXX] has been rejected by the 3CX Country Blocking Feature [001]. Reason: 001305555XXXX contains Prefix 001. Calls to 001 are not allowed by system.

Since there's no way to allow "Other custom" country codes, or disable the country blocking feature entirely, or force allow 001 in any way from the console were essentially screwed

Needless to say changing country dialing regulations is not an option.

As for our customer, a PBX system that cannot dial international calls is as good as useless to him.

Everything works perfect except for this feature which to this customer is basically make or break on the sale.

What can we do? Anyone know a workaround? there has to be a way to add this manually using console, maybe adding the code as a custom country manually somehow to the database or a command to run somewhere?

Any help would be appreciated.

Thank you.

 

[XionicFire]

Update:

I tried doing the E164 option to use + as a char, still same problem, if i tell it to strip + and add 00 instead i get the same error, ive also tried adding a static if it starts with 001 then route here route and nothing, also adding 9 before it and then striping it with no success, no matter what I try the system detects the 001 and blocks the call

There has to be a way to disable the country blocking system in its entirety, there's no way no one noticed an entire country (mexico) cannot dial to the US using 3CX, its too big a bug to miss.

Thanks in advance to anyone with any information regarding this.

 

[cobaltit]

So have you tried just dialing 1+ and not 001+? And to confirm you do have US calling allowed?

 

[XionicFire]

yes 1 works, 01 works, 001 does not work

 

[cobaltit]

So in reading the rules, it looks like 00 is an exit code, while the US country code is 1. It's not a country code of 001. So this is not a bug in 3CX, instead it's not a proper configuration of your system. For your outbound rule for international calls, just tell it to prepend 00 when sending it out the trunk. 3CX will see the correct country code and your telecom provider will process the call correctly.

 

[leejor]

3CX should be able to handle the user dialling 00 as, (I'm amusing) an international prefix, with the country code being 1, for North America. This in the same manner as dialling 0044+ for UK numbers, with 44 being recognized as a country code, to either allow or block, depending on the settings. they should not have to rely on the outbound rules adding the 00 before sending.
It sounds as if something else, is incorrectly defined.

 

[XionicFire]

So in reading the rules, it looks like 00 is an exit code, while the US country code is 1. It's not a country code of 001. So this is not a bug in 3CX, instead it's not a proper configuration of your system. For your outbound rule for international calls, just tell it to prepend 00 when sending it out the trunk. 3CX will see the correct country code and your telecom provider will process the call correctly.

Thanks for responding, will try to respond in line

If its a fault in my config im not seeing it, everything else works perfectly except anything that starts with 001, i can dial London no problem 0044 just 001 is blocked

As for your suggestion, yes but that would imply my users would have to dial to the USA the same way the USA dials to the USA, and since its not the way the country does its dialing its completely unfeasible, 150 people have their contacts in the form the country allows which is 00XX we cannot change this.

 

[XionicFire]

If its a fault in my config im not seeing it, everything else works perfectly except anything that starts with 001, i can dial London no problem 0044 just 001 is blocked

As for your suggestion, yes but that would imply my users would have to dial to the USA the same way the USA dials to the USA, and since its not the way the country does its dialing its completely unfeasible, 150 people have their contacts in the form the country allows which is 00XX we cannot change this.

Well that's the thing anything international other than 001 works just fine, just 001 fails, as i stated earlier 0044 to England works perfectly fine

It seems to be an issue with 3CX wrongly detecting 001 as a country, i would love to test this but seeing as there is no way to disable country blocking i cant.

I have a couple of lines here with an ATA adapter, others are direct trunks, same problem on both, yet physically connecting a phone to these lines and dialing 001 works perfectly, so its definitely something in 3CX

 

[cobaltit]

Hmm.. I honestly didn't think that far into it, just looked up what the Mexico telecom rules you mentioned said. But as @leejor said and you confirmed that other dial strings starting with 00 work. Can you confirm what version you are on?