Re: [Kamailio-Users] LCR problem with "id" column and match priorities

Juha. Can i change the lcr_has_size from the configuration file with the parameter?

modparam("lcr", "lcr_hash_size", 1024)

Another thing. Looking at the lcr_mod.c file there is a parameter called MAX_NO_OF_GWS defined as follows :

#define MAX_NO_OF_GWS 128

Can I increase this value too? Maybe 256 ?

Thanks, Ricardo.-

-----Mensaje original----- De: Juha Heinanen [mailto:jh@tutpro.com] Enviado el: jueves, 22 de octubre de 2009 12:41 Para: Ricardo Martinez CC: users@lists.kamailio.org Asunto: RE: [Kamailio-Users] LCR problem with "id" column and match priorities

Ricardo Martinez writes:

I was trying to replicate the problem with another prefix, and was

using

the "id's" 132 and 133, correlative, however the problem persists.

id numbers should not have anything to do with this, because nowhere in the module is id column used. the only thing that might matter is the order in which the records are returned from database.

Maybe I'm missing something in all this scenario. If I have more

than

130 routes in the lcr table do need to set something else? Maybe the lcr_hash_size??

if you have more than 128 routes, it would be advisable to increase the size of the lcr hash table. you can do that by changing the value of constant

#define DEF_LCR_HASH_SIZE 128

in lcr_mod.c

in your case, you could use 256 instead of 128.

-- juha