This isn't a question specific to LCR module, but it could be an LCR or Carrierroute module issue.
Let's say you have to carriers...
Carrier Prefix Cost --------------------------- Carrier1 1650 0.3 Carrier2 165 0.2
When LCR or Carrierroute try to match a dialed number against a routing entry, they will try and match as much of the number as possible, which makes sense.
However, when you get routes from multiple carriers, they don't always bill on the same prefix boundaries. In my example above, LCR/Carierroute would match against Carrier1 for anything starting with 1650. HOWEVER, since 165 is also applicable (165 means 1650, 1651 and so on), and in this example cheaper, you should route 165 over Carrier 2.
What do people do in this case?
Doug
____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
On Mar 28, 2008, at 12:38 AM, Douglas Garstang wrote:
However, when you get routes from multiple carriers, they don't always bill on the same prefix boundaries. In my example above, LCR/ Carierroute would match against Carrier1 for anything starting with 1650. HOWEVER, since 165 is also applicable (165 means 1650, 1651 and so on), and in this example cheaper, you should route 165 over Carrier 2.
What do people do in this case?
It's called LCR for a reason, so I think minimizing cost should be priority 1. Once price has stopped being the differentiator other factors could be taken into account. Maybe price and other costs have to aggregated?
On Friday 28 March 2008, Douglas Garstang wrote:
Carrier Prefix Cost
Carrier1 1650 0.3 Carrier2 165 0.2
What do people do in this case?
Don't use the LCR module to compare, but do it by other means by selecting the longest matching prefix per carrier and then sort the list on price.
Store the list of associated uri's in the gw_uri_avp and use next_gw() to traverse them.
Alex.
-
Alex Hermann -
Andreas Sikkema -
Douglas Garstang -
jh＠tutpro.com