How to apply a fix to remove local prefix 0 in the called number.

[Marco pbx]

Hello!
We are calling from at least 50 countries for our work, and some numbers are saved in the CRM with a leading zero after the country code, for example:

0044 0 1313 414 000. When we try to call in this format, it fails because the correct number must be dialled as 0044 1313 414 000 when contacting the vendor.

I can fix this by adding an additional outbound route that catches 00440 and replaces it with 0044, but this solution is not practical for me.

I need to add 40-50 rules for each destination country, such as Germany 00490 being replaced with 0049, France, Spain, Turkey, etc. This would require many outbound rules.

How can I make this easier without creating numerous outbound rules?

E164 settings do not work for me because we do not have a single fixed trunk for calls. Instead, we use different trunks for different destinations: a German trunk for German numbers, a French trunk for French numbers, and so on. We are using over 20 trunks in total.

 

[fxbastler]

How can I make this easier without creating numerous outbound rules?

Take better care of your CRM. Use standards like E.123 or DIN 5008.

Everything else, including the pointless use of countless outgoing rules that sometimes overlap, are technical crutches.

I also keep seeing - even often from companies that build and maintain telephone systems - incorrect spellings,
like +49 (0) 30 888888. That cannot be dialed. It's simply wrong.

 

[leejor]

You may want to consider setting up E164 processing in 3CX.

Post in thread 'What does E164 Processing Actually Do?'

Apr 12, 2021

Select country: Pretty straight forward. Select the country you are in so the system knows your country code. For our examples lets use US as our country.

Remove if same country: When this option is selected and you try calling the same country using the E164 format the country code will be removed from the called number.
Example: Number dialed as +12345678910 will be converted to 2345678910.

International Dial Code: If you call a different country using the E164 format then the number will be converted and the international dial code will be added. If you are in the...

• YiannisH_3CX

• 

 

[KyriacosS_3CX]

Your best bet might be to export the phonebook in a CSV and clear all this out in a text editor and re-import. The system can handle brackets and dashes in the phone numbers, but 0 is a valid digit and stays.

Also unless the phonebook itself is fixed, CallerID matching will never work (properly - with match x digits you can match before the 0, but then some duplication across countries is more likely) for incoming calls.

 

[Marco pbx]

Hi @ieejor , it is not an E164 issue but with the national digit zero after country code.
I tried to figure out with outbound routes but i can not use one route to fix all destionation countries.
It is also very hard to fix the data since there are thousands of it and wrond data still comes in which is out of our control.

@fxbastler thanks for the information, you are correct, but i am still searching for a tricky way to remove these zeros after country code in the dialed number.

 

[fxbastler]

but i am still searching for a tricky way to remove these zeros after country code in the dialed number.

There isn't one.

Either there are tons of - probably overlapping - outgoing rules in 3CX, extensive reformatting of outgoing numbers in the 3CX SIP trunk, or putting all the rules into an SBC in front of 3CX. Either way, it won't get any easier.

Take better care of your CRM. Use standards like E.123 or DIN 5008.

nuff said