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

[Juha Heinanen]

Ricardo Martinez writes:

 > This keep happening even if change the priority value 2 for priority
 > value 5.  I even changed the priority 1 for priority 0 as follows : 
 > 
 > +-----+--------+----------+--------+----------+
 > 
 > | id  | prefix | from_uri | grp_id | priority |
 > 
 > +-----+--------+----------+--------+----------+
 > 
 > |  89 | 1351   |          |     51 |        0 | 
 > 
 > | 127 | 1351   |          |     43 |        1 | 
 > 
 > +-----+--------+----------+--------+----------+
 > 
 > But the LCR module keep using the "second" priority.
 > 
 > After doing some tests I've found two ways to use the "first" priority
 > for the prefix.  
 > 
 > 2.- Re-ordering the "id" column and using correlative values as
 > indicated in the next table : 
 > 
 > mysql> select * from lcr where prefix=0251 order by id;
 > 
 > +-----+--------+----------+--------+----------+
 > 
 > | id  | prefix | from_uri | grp_id | priority |
 > 
 > +-----+--------+----------+--------+----------+
 > 
 > | 127 | 1351   |          |     51 |        1 | 
 > 
 > | 128 | 1351   |          |     43 |        2 | 
 > 
 > +-----+--------+----------+--------+----------+

there is something wrong in above, because where clause is not matching
the output.

 > So, when the prefix are with "no correlatives" values in the "id" column
 > seems to be a problem to match the first priority.  But when the values
 > are correlative there is no problem.

are you saying that the problem goes away if you in the first table
change id 89 to id 127?

rather that printing your mysql tables, show what lcr dump mi commands
give.

-- juha