[asterisk-users] Rate sheet "normalization"

[Markus]

Am 13.03.2012 01:24, schrieb Alex Balashov:
> On 03/12/2012 06:52 PM, Markus wrote:
>
>> Now, if the "49" route of the first provider is cheaper, my
>> system (a2billing) will still use the more expensive "4930" code
>> because it is more specific.
>
> There is a great deal of wisdom in this approach that you may wish to
> consider carefully before abandoning. It is especially true in Europe,
> and really, anywhere outside the North American environment, which it
> doesn't sound like you're in to begin with.

I understand what you're saying, but actually, I tried to keep the 
example really simple. In real life, the problem is that some of the 
rate sheets of some providers look like this - example:

Provider 1:

Brazil Mobile Tim, 55118, 0.0383

Provider 2:

Brazil Tim Mobile, 551181, 0.1785
Brazil Tim Mobile, 551182, 0.1785
Brazil Tim Mobile, 551183, 0.1785
Brazil Tim Mobile, 551184, 0.1785
etc.

Now, all calls would go via the more expensive Provider 2 due to the 
more specific codes, and the cheaper route via Provider 1 would not be 
used at all.

Basically the software I'm looking for knows all the real "base" codes 
throughout the world and will merge such unnecessary breakout codes like 
at Provider 2 to the "base" code. Or, it will understand that there is a 
cheaper route available for a valid base code and drop the more specific 
codes. And if the more specifics are cheaper, it should understand that 
as well.

Does such a thing exist?

Thanks!