provided by Star2Billing S.L.

Hello to all. After the upgrade to 1.5 and then 1.6 I have problems with conflicting prefixes to local and long distance. Just an example is Mexico and a local code within the country with the prefix of 52. The difference is only the dialing prefix - 00 for long distance and 0 for the local code.
Adding zeros in the prefixes table doesn't work. Billing works correctly, but the wrong destination in CDR is very confusing for the customers.

Any advice is appreciated. Thanks!

Looks like this is not confusing to anybody else. Or maybe there is already information on this subject that I can't find?

I solved it. Was not an elegant solution. If I was the developer of this project, I would make this part work different.

How I did it:
I made new trunk that removes the 0 and adds 00359 - which is the country prefix.
Then created a ratecard and imported the same destinations only with 00359XX prefix. This caused a2b to import new prefixes in its prefixes table. Then I did an update on the database rows - replaced 00359 from the dialprefix field with just 0.