provided by Star2Billing S.L.

Hi,

My A2B is 1.3.3 with Postgres.

I use LCR in my callplan and I have two ratecards. Both of them have the prefix for France - 0033 and one of them is 'cheaper'.
Also only one of them has the prefix 00336, which is France - Mobile and the other (cheaper) doesn't have this prefix.

The problem:
When customer calls 0033 all is OK. A2B chose the right (cheaper) route. But when customer calls 00336 A2B matches the 0033 prefix on the cheaper card instead of 00336 prefix on the other.

The CDR reports France as destination instead of France - Mobile. A2B charges customer for call to a wrong destination and the only one who is happy with that is the caller.
I lose money

I confirm that this is a fundamental bug in the 1.3 RateEngine.

More detail here:-

http://forum.asterisk2billing.org/viewtopic.php?p=16424

Joe

I'll take a closer look at this trac ticket, but from what i read there, the issue seems the other way around from what I report.
In my case the rate engine chose the shorter prefix with the lower cost from card A, but the longer prefix with higher cost from card B is the correct destination.

Added after 28 minutes:

I can confirm that the patch here http://www.asterisk2billing.org/cgi-bin ... ticket/209
does not fix this particular problem. It is a solution for exactly the opposite situation. I don't know why somebody would like to match the shorter prefix.
The longer the prefix the more specific. This way if one has a longer prefix only in one of the ratecards, although with a higher rate, rate engine should match the longer one.

My mistake. I deleted a ratecard and then forgot to assign it to the callplan again after I recreated it again.