[Kamailio-Users] LCR Private Memory

[Stagg Shelton]

I'm using the lcr module in the 1.4.4 source tar.gz.  I have just  
gotten kamailio to successfully start by increasing the shared memory  
using the command parameter -m 1024.  I had initially thought about  
using carrierroute instead of LCR just because we currently use use  
carrierroute to send specific customers out to specific upstream  
carriers.  I was concerned that carrierroute wasn't designed to handle  
such a large number of routes, and had found other posts in this  
mailling list where people had stated using LCR with 300,000+ routes  
with no issues.

I also am following the changes in the 1.5 branch and notice that LCR  
now uses fetch_rows like carrierroute does.  I have considered  
upgrading directly from 1.3.3 to 1.5.1, but am cautious as I do not  
want to bring anything disruptive into a very stable production  
environment, so I fell back to 1.4.4 thinking that the code has had  
more time to mature, and have many issues resolved.

Stagg

On Apr 30, 2009, at 10:44 AM, Henning Westerholt wrote:

> On Donnerstag, 30. April 2009, Stagg Shelton wrote:
> > I should also note that I also changed this line in the lcr_mod.c to
> > account for the amount of rows that I have in the lcr database  
> table.
> >
> > Original
> > #define MAX_NO_OF_LCRS 256
> >
> > Changed to
> > #define MAX_NO_OF_LCRS 32000
>
> Hi Stagg,
>
> do you use a "old" version of the lcr module, e.g. the one of  
> version 1.3 or 1.4? AFAIK this is not optimized for such a large  
> number of routing rules, i'd suggest that you use the one from 1.5  
> instead, or carrierroute.
>
> Cheers,
>
> Henning