Henry Fernandes writes:
Let’s say you have the following info in your LCR.
Prefix, Carrier/Route, Rate 1306, A, 1.5 1306343, A, 1.7 1306, B, 1.4
If you have phone number 13063431111, the LCR module matches it to the longest prefix (1306343) and routes the call to Carrier A. However, that is incorrect. It should match it to Carrier B which is the cheapest. Carrier B has provided a rate of 1.4 for all calls with prefix 1306.
why can't you add rule
1306343, B, 1.4
to solve the problem?
-- juha
You¹re right. The problem will be solved if you add that rule.
But we didn¹t want to add hundreds of thousands or millions of extra rules just to deal with this problem. We didn¹t consider that a good workaround.
In the end, we used sqlops to do our own LCR matching/routing. -H
On 2015-06-15, 8:55 AM, "Juha Heinanen" jh@tutpro.com wrote:
Henry Fernandes writes:
Let¹s say you have the following info in your LCR.
Prefix, Carrier/Route, Rate 1306, A, 1.5 1306343, A, 1.7 1306, B, 1.4
If you have phone number 13063431111, the LCR module matches it to the longest prefix (1306343) and routes the call to Carrier A. However, that is incorrect. It should match it to Carrier B which is the cheapest. Carrier B has provided a rate of 1.4 for all calls with prefix 1306.
why can't you add rule
1306343, B, 1.4
to solve the problem?
-- juha
-
Henry Fernandes -
Juha Heinanen