Thanks Juha I populated the lcr tables by hand. This is how they look now, I have 2 lcr_ids [1 and 2], each instance has its own gw. And each instance has its own prefix to match for [4444 and 5555]. The idea is that a call comes in with R-URI 444413051234567, it should match the lcr_id= 200, then it should go out using gw 192.168.169.200 etc
mysql> select * from lcr_gw; +----+--------+------------+-----------------+-------------------+------+--------+------------+-----------+-------+------+-------+---------+ | id | lcr_id | gw_name | ip_addr | hostname | port | params | uri_scheme | transport | strip | tag | flags | defunct | +----+--------+------------+-----------------+-------------------+------+--------+------------+-----------+-------+------+-------+---------+ | 1 | 200 | switchvox | 192.168.169.200 | pbx1.mydomain.com | 5060 | none | 1 | 1 | 0 | | 0 | 0 | | 2 | 201 | switchvox2 | 192.168.169.201 | pbx1.mydomain.net | 5060 | none | 1 | 1 | 0 | | 0 | 0 | +----+--------+------------+-----------------+-------------------+------+--------+------------+-----------+-------+------+-------+---------+ mysql> select * from lcr_rule; +----+--------+--------+----------+---------+---------+ | id | lcr_id | prefix | from_uri | stopper | enabled | +----+--------+--------+----------+---------+---------+ | 1 | 200 | 4444 | | 0 | 1 | | 2 | 201 | 5555 | | 0 | 1 | +----+--------+--------+----------+---------+---------+ mysql> select * from lcr_rule_target; +----+--------+---------+-------+----------+--------+ | id | lcr_id | rule_id | gw_id | priority | weight | +----+--------+---------+-------+----------+--------+ | 1 | 200 | 1 | 1 | 5 | 1 | | 2 | 201 | 2 | 2 | 5 | 1 | +----+--------+---------+-------+----------+--------+
Then I tried the sercmd commands to reload and dump and I do not see the contents o the screen. Is this how is supposed to work now?.
with debug level set to 3 I do this "/usr/local/kamailio-3.1/sbin/sercmd lcr.dump_rules" and see these lines on the syslog:
Jun 28 11:53:57 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [../../io_wait.h:390]: DBG: io_watch_add(0x2b772e494660, 12, 3, 0x9679e8), fd_no=1 Jun 28 11:53:57 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [io_listener.c:452]: handle_stream read: new connection (1) on /tmp/ser_ctl Jun 28 11:53:57 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [io_listener.c:505]: handle_stream read: eof on /tmp/ser_ctl Jun 28 11:53:57 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [../../io_wait.h:617]: DBG: io_watch_del (0x2b772e494660, 12, -1, 0x10) fd_no=2 called
if I do this: "/usr/local/kamailio-3.1/sbin/sercmd lcr.reload" I see these:
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [../../io_wait.h:390]: DBG: io_watch_add(0x2b772e494660, 12, 3, 0x9679e8), fd_no=1 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [io_listener.c:452]: handle_stream read: new connection (1) on /tmp/ser_ctl Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db.c:294]: connection 0x951b78 found in pool Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:118]: allocate 48 bytes for result set at 0x952728 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:68]: 5 columns returned from the query Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:155]: allocate 40 bytes for result names at 0x9527b8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:165]: allocate 20 bytes for result types at 0x952610 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[0] at 0x9528b8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x9528b8)[0]=[id] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[1] at 0x952928 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952928)[1]=[prefix] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[2] at 0x951a98 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x951a98)[2]=[from_uri] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[3] at 0x951b08 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x951b08)[3]=[stopper] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[4] at 0x952998 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952998)[4]=[enabled] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_dbase.c:326]: no rows returned from the query Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: lcr [lcr_mod.c:985]: loading, cycle 0 with <0> rows Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:81]: freeing 5 columns Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[0] at 0x9528b8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[1] at 0x952928 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[2] at 0x951a98 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[3] at 0x951b08 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[4] at 0x952998 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:94]: freeing result names at 0x9527b8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:99]: freeing result types at 0x952610 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:136]: freeing result set at 0x952728 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:118]: allocate 48 bytes for result set at 0x952728 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:68]: 12 columns returned from the query Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:155]: allocate 96 bytes for result names at 0x951ef8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:165]: allocate 48 bytes for result types at 0x951c38 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[0] at 0x951b08 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x951b08)[0]=[gw_name] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[1] at 0x951a98 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x951a98)[1]=[ip_addr] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[2] at 0x952928 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952928)[2]=[port] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[3] at 0x9528b8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x9528b8)[3]=[uri_scheme] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[4] at 0x952610 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952610)[4]=[transport] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[5] at 0x952998 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952998)[5]=[params] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[6] at 0x9527b8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x9527b8)[6]=[hostname] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[7] at 0x951fb8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x951fb8)[7]=[strip] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[8] at 0x952028 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952028)[8]=[tag] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[9] at 0x952098 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952098)[9]=[flags] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[10] at 0x952108 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952108)[10]=[defunct] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[11] at 0x951288 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x951288)[11]=[id] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:169]: no rows returned from the query Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:81]: freeing 12 columns Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[0] at 0x951b08 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[1] at 0x951a98 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[2] at 0x952928 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[3] at 0x9528b8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[4] at 0x952610 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[5] at 0x952998 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[6] at 0x9527b8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[7] at 0x951fb8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[8] at 0x952028 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[9] at 0x952098 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[10] at 0x952108 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[11] at 0x951288 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:94]: freeing result names at 0x951ef8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:99]: freeing result types at 0x951c38 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:136]: freeing result set at 0x952728 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:118]: allocate 48 bytes for result set at 0x952728 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:68]: 4 columns returned from the query Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:155]: allocate 32 bytes for result names at 0x952998 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:165]: allocate 16 bytes for result types at 0x951288 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[0] at 0x952098 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952098)[0]=[rule_id] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[1] at 0x952028 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952028)[1]=[gw_id] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[2] at 0x951fb8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x951fb8)[2]=[priority] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[3] at 0x9528b8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x9528b8)[3]=[weight] Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_dbase.c:326]: no rows returned from the query Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: lcr [lcr_mod.c:1344]: loading, cycle 0 with <0> rows Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:81]: freeing 4 columns Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[0] at 0x952098 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[1] at 0x952028 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[2] at 0x951fb8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[3] at 0x9528b8 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:94]: freeing result names at 0x952998 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:99]: freeing result types at 0x951288 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:136]: freeing result set at 0x952728 Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_pool.c:97]: connection still kept in the pool Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [io_listener.c:505]: handle_stream read: eof on /tmp/ser_ctl Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [../../io_wait.h:617]: DBG: io_watch_del (0x2b772e494660, 12, -1, 0x10) fd_no=2 called
I am trying to port our setup from kamailio 1.4.3 to 3.1.4 and I see
huge differences on the LCR module.
there is a script somewhere (read wiki) that upgrades the tables.
I have these main questions:
1- does lcr_id replaces the grp_id?
not really. lcr_ids denote independent lcr instances.
2- what happened to the fifo commands to add gws etc:
fifo commands to manipulate lcr tables are not supported by me.
-- juha
From: fborot@hotmail.com To: sr-users@lists.sip-router.org Subject: Questions about LCR module Date: Mon, 27 Jun 2011 17:23:05 -0400
I am trying to port our setup from kamailio 1.4.3 to 3.1.4 and I see huge differences on the LCR module. I have these main questions:
1- does lcr_id replaces the grp_id? 2- what happened to the fifo commands to add gws etc:
lcr addgw <gw_name> <ip> <port> <scheme> <transport> <grp_id> <flags> <tag> <strip> ............... add a gateway with flags, tag and strip ............ ................(flags, tag, and strip are optional arguments) ..... lcr rmgw <gw_name> .......................................................... ............... delete a gateway lcr addroute <prefix> <from> <grp_id> <prio> ................................. .............. add a route ( use '' to match anything in <from> ) lcr rmroute <prefix> <from> <grp_id> <prio> ................................. .............. delete a route
3- it looks like the kamctl fifo lcr reload can not be used anymore, instead I found that there is a sercmd command that can be used to "show" and "reload" only the lcr tables
What would be the best way to use this module on this version?
Any help/hint would be greatly appreciated. thank you
fborot
Thanks Juha I populated the lcr tables by hand. This is how they look now, I have 2 lcr_ids [1 and 2], each instance has its own gw. And each instance has its own prefix to match for [4444 and 5555]. The idea is that a call comes in with R-URI 444413051234567, it should match the lcr_id= 200, then it should go out using gw 192.168.169.200 etc
mysql> select * from lcr_gw; +----+--------+------------+-----------------+-------------------+------+--------+------------+-----------+-------+------+-------+---------+ | id | lcr_id | gw_name | ip_addr | hostname | port | params | uri_scheme | transport | strip | tag | flags | defunct | +----+--------+------------+-----------------+-------------------+------+--------+------------+-----------+-------+------+-------+---------+ | 1 | 200 | switchvox | 192.168.169.200 | pbx1.mydomain.com | 5060 | none | 1 | 1 | 0 | | 0 | 0 | | 2 | 201 | switchvox2 | 192.168.169.201 | pbx1.mydomain.net | 5060 | none | 1 | 1 | 0 | | 0 | 0 | +----+--------+------------+-----------------+-------------------+------+--------+------------+-----------+-------+------+-------+---------+ mysql> select * from lcr_rule; +----+--------+--------+----------+---------+---------+ | id | lcr_id | prefix | from_uri | stopper | enabled | +----+--------+--------+----------+---------+---------+ | 1 | 200 | 4444 | | 0 | 1 | | 2 | 201 | 5555 | | 0 | 1 | +----+--------+--------+----------+---------+---------+ mysql> select * from lcr_rule_target; +----+--------+---------+-------+----------+--------+ | id | lcr_id | rule_id | gw_id | priority | weight | +----+--------+---------+-------+----------+--------+ | 1 | 200 | 1 | 1 | 5 | 1 | | 2 | 201 | 2 | 2 | 5 | 1 | +----+--------+---------+-------+----------+--------+
Then I tried the sercmd commands to reload and dump and I do not see the contents o the screen. Is this how is supposed to work now?. How do I know that the new values are being loaded into memory w/o restarting kamailio?
I am trying to port our setup from kamailio 1.4.3 to 3.1.4 and I see
huge differences on the LCR module.
there is a script somewhere (read wiki) that upgrades the tables.
I have these main questions:
1- does lcr_id replaces the grp_id?
not really. lcr_ids denote independent lcr instances.
2- what happened to the fifo commands to add gws etc:
fifo commands to manipulate lcr tables are not supported by me.
-- juha
From: fborot@hotmail.com To: sr-users@lists.sip-router.org Subject: Questions about LCR module Date: Mon, 27 Jun 2011 17:23:05 -0400
I am trying to port our setup from kamailio 1.4.3 to 3.1.4 and I see huge differences on the LCR module. I have these main questions:
1- does lcr_id replaces the grp_id? 2- what happened to the fifo commands to add gws etc:
lcr addgw <gw_name> <ip> <port> <scheme> <transport> <grp_id> <flags> <tag> <strip> ............... add a gateway with flags, tag and strip ............ ................(flags, tag, and strip are optional arguments) ..... lcr rmgw <gw_name> .......................................................... ............... delete a gateway lcr addroute <prefix> <from> <grp_id> <prio> ................................. .............. add a route ( use '' to match anything in <from> ) lcr rmroute <prefix> <from> <grp_id> <prio> ................................. .............. delete a route
3- it looks like the kamctl fifo lcr reload can not be used anymore, instead I found that there is a sercmd command that can be used to "show" and "reload" only the lcr tables
What would be the best way to use this module on this version?
Any help/hint would be greatly appreciated. thank you
fborot
Fabian Borot writes:
Then I tried the sercmd commands to reload and dump and I do not see the contents o the screen. Is this how is supposed to work now?. How do I know that the new values are being loaded into memory w/o restarting kamailio?
lcr.reload load the tables to memory and does not print anything. lcr.dump_[gws|rules] prints what is in memory.
perhaps you didn't set lcr_count. please read whole README carefully.
-- juha
lcr.reload load the tables to memory and does not print anything. lcr.dump_[gws|rules] prints what is in memory.
perhaps you didn't set lcr_count. please read whole README carefully.
-- juha
you are right, I guess I did not have the module well configured
From: fborot@hotmail.com To: sr-users@lists.sip-router.org Subject: RE: Questions about LCR module Date: Tue, 28 Jun 2011 16:48:49 -0400
Thanks Juha I populated the lcr tables by hand. This is how they look now, I have 2 lcr_ids [1 and 2], each instance has its own gw. And each instance has its own prefix to match for [4444 and 5555]. The idea is that a call comes in with R-URI 444413051234567, it should match the lcr_id= 200, then it should go out using gw 192.168.169.200 etc
mysql> select * from lcr_gw; +----+--------+------------+-----------------+-------------------+------+--------+------------+-----------+-------+------+-------+---------+ | id | lcr_id | gw_name | ip_addr | hostname | port | params | uri_scheme | transport | strip | tag | flags | defunct | +----+--------+------------+-----------------+-------------------+------+--------+------------+-----------+-------+------+-------+---------+ | 1 | 200 | switchvox | 192.168.169.200 | pbx1.mydomain.com | 5060 | none | 1 | 1 | 0 | | 0 | 0 | | 2 | 201 | switchvox2 | 192.168.169.201 | pbx1.mydomain.net | 5060 | none | 1 | 1 | 0 | | 0 | 0 | +----+--------+------------+-----------------+-------------------+------+--------+------------+-----------+-------+------+-------+---------+ mysql> select * from lcr_rule; +----+--------+--------+----------+---------+---------+ | id | lcr_id | prefix | from_uri | stopper | enabled | +----+--------+--------+----------+---------+---------+ | 1 | 200 | 4444 | | 0 | 1 | | 2 | 201 | 5555 | | 0 | 1 | +----+--------+--------+----------+---------+---------+ mysql> select * from lcr_rule_target; +----+--------+---------+-------+----------+--------+ | id | lcr_id | rule_id | gw_id | priority | weight | +----+--------+---------+-------+----------+--------+ | 1 | 200 | 1 | 1 | 5 | 1 | | 2 | 201 | 2 | 2 | 5 | 1 | +----+--------+---------+-------+----------+--------+
Then I tried the sercmd commands to reload and dump and I do not see the contents o the screen. Is this how is supposed to work now?. How do I know that the new values are being loaded into memory w/o restarting kamailio?
I am trying to port our setup from kamailio 1.4.3 to 3.1.4 and I see
huge differences on the LCR module.
there is a script somewhere (read wiki) that upgrades the tables.
I have these main questions:
1- does lcr_id replaces the grp_id?
not really. lcr_ids denote independent lcr instances.
2- what happened to the fifo commands to add gws etc:
fifo commands to manipulate lcr tables are not supported by me.
-- juha
From: fborot@hotmail.com To: sr-users@lists.sip-router.org Subject: Questions about LCR module Date: Mon, 27 Jun 2011 17:23:05 -0400
I am trying to port our setup from kamailio 1.4.3 to 3.1.4 and I see huge differences on the LCR module. I have these main questions:
1- does lcr_id replaces the grp_id? 2- what happened to the fifo commands to add gws etc:
lcr addgw <gw_name> <ip> <port> <scheme> <transport> <grp_id> <flags> <tag> <strip> ............... add a gateway with flags, tag and strip ............ ................(flags, tag, and strip are optional arguments) ..... lcr rmgw <gw_name> .......................................................... ............... delete a gateway lcr addroute <prefix> <from> <grp_id> <prio> ................................. .............. add a route ( use '' to match anything in <from> ) lcr rmroute <prefix> <from> <grp_id> <prio> ................................. .............. delete a route
3- it looks like the kamctl fifo lcr reload can not be used anymore, instead I found that there is a sercmd command that can be used to "show" and "reload" only the lcr tables
What would be the best way to use this module on this version?
Any help/hint would be greatly appreciated. thank you
fborot