[SR-Users] Kamailio LCR module memory concern

[Ali Taher]

The case mentioned is exactly our case where we deal with class 4,  wholesale carriers with many vendors; just as explained in the provided short duration dialer video where we are using Kamailio lcr as redirect server. Hence, what can we do in order to afford such Huge number of rules?
 How did your customer handle 137 million using kamailio lcr?

Thanks for your cooperation,
Ali
Sent from my iPhone

> On Jun 10, 2015, at 7:55 PM, Alex Balashov <abalashov at evaristesys.com> wrote:
> 
>> On 06/10/2015 12:52 PM, Juha Heinanen wrote:
>> 
>> i wonder how it is possible to have so many distinct e.164 prefixes for
>> transit unless you need to deal with individual subscriber numbers.
> 
> It's quite possible for folks who run dialler traffic[1], at least in the US. The reasons are:
> 
> - Most rate centres in the US are subject to number pooling, which allocates numbers in blocks of 1000 using 7-digit prefixes. This yields a stupefyingly large number of prefixes just for domestic USA routing.
> 
> - Wholesale ITSPs, particularly ones specialising in short-duration traffic, typically utilise a large number of vendors, since many of them will fail the call due to race-to-the-bottom LCR. We once had a customer with 135 million routes from around 30 different vendors.
> 
> -- Alex
> 
> [1] Incidentally, the subject of my recent Kamailio World talk!
> 
> https://www.youtube.com/watch?v=u30Fyp3QanE
> 
> -- 
> Alex Balashov | Principal | Evariste Systems LLC
> 303 Perimeter Center North, Suite 300
> Atlanta, GA 30346
> United States
> 
> Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
> 
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users