sr-users

sr-users@lists.kamailio.org

37 participants
37511 discussions

DBTEXT + TOPOS
by James Lipski 19 Sep '23

19 Sep '23

Hello, I'm doing an experiment with the DB_TEXT module. I have the topos module enabled; however it doesn't seem to function properly with db_text. Going over my syslog I see the following, and not quite understanding why it's failing to insert the row; I was hoping someone can point me in the right direction. This is a fresh install/ fresh DB. Thank you. Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[5] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[6] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[6] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[7] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[7] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:200]: dbt_load_file(): column[8] is INT! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[9] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[9] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:239]: dbt_load_file(): column[9] NULL flag set! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[10] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[10] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[11] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[11] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:239]: dbt_load_file(): column[11] NULL flag set! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[12] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[12] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:239]: dbt_load_file(): column[12] NULL flag set! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[13] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[13] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:239]: dbt_load_file(): column[13] NULL flag set! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[14] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[14] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[15] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[15] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[16] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[16] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[17] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[17] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[18] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[18] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[19] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[19] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[20] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[20] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[21] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[21] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[22] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[22] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[23] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[23] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[24] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[24] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[25] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[25] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:119]: db_new_result(): allocate 56 bytes for result set at 0x7fd70c7f4c40 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:156]: db_allocate_columns(): allocate 160 bytes for result names at 0x7fd70cacabf8 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:167]: db_allocate_columns(): allocate 80 bytes for result types at 0x7fd70c7f4ce0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[0] at 0x7fd70cacad00 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[1] at 0x7fd70cacad78 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[2] at 0x7fd70cacadf0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[3] at 0x7fd70cacae68 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[4] at 0x7fd70cacaee0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[5] at 0x7fd70cacaf58 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[6] at 0x7fd70cacafd0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[7] at 0x7fd70cacb048 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[8] at 0x7fd70cacb0c0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[9] at 0x7fd70cacb138 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[10] at 0x7fd70cacb1b0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[11] at 0x7fd70cacb228 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[12] at 0x7fd70cacb2a0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[13] at 0x7fd70cacb318 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[14] at 0x7fd70c7c2368 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[15] at 0x7fd70c7c23e0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[16] at 0x7fd70c7c2458 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[17] at 0x7fd70c7c24d0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[18] at 0x7fd70c7c2548 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[19] at 0x7fd70c7c25c0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:1244]: tps_db_load_branch(): no stored record for <z9hG4bK22d5.7fedda308f2b91b2c0c83021c6adfaec.0> Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:79]: db_free_columns(): freeing 20 columns Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[0] at 0x7fd70cacad00 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[1] at 0x7fd70cacad78 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[2] at 0x7fd70cacadf0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[3] at 0x7fd70cacae68 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[4] at 0x7fd70cacaee0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[5] at 0x7fd70cacaf58 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[6] at 0x7fd70cacafd0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[7] at 0x7fd70cacb048 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[8] at 0x7fd70cacb0c0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[9] at 0x7fd70cacb138 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[10] at 0x7fd70cacb1b0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[11] at 0x7fd70cacb228 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[12] at 0x7fd70cacb2a0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[13] at 0x7fd70cacb318 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[14] at 0x7fd70c7c2368 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[15] at 0x7fd70c7c23e0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[16] at 0x7fd70c7c2458 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[17] at 0x7fd70c7c24d0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[18] at 0x7fd70c7c2548 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[19] at 0x7fd70c7c25c0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:96]: db_free_columns(): freeing result names at 0x7fd70cacabf8 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:101]: db_free_columns(): freeing result types at 0x7fd70c7f4ce0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:138]: db_free_result(): freeing result set at 0x7fd70c7f4c40 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [core/utils/sruid.c:214]: sruid_nextx(): new sruid is [tpsh-6508d6d9-14577b-1] (1 / 22) Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:451]: tps_storage_fill_contact(): td->bs <sip:leg_a@host1.sip-example.com;ccr=btpsh-6508d6d9-14577b-1> Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:454]: tps_storage_fill_contact(): td->as <sip:leg_b@host1.sip-example.com;ccr=atpsh-6508d6d9-14577b-1> Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:552]: tps_storage_link_msg(): downstream: yes - acontact: [sip:133@172.16.1.169:33880;line=g2l0pi9q;alias=72.255.5255.255~33880~1] - bcontact: [] Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_lib.c:285]: dbt_db_get_table(): cache or mtime succeeded for [topos_t] Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: ERROR: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_tb.c:468]: dbt_table_check_row(): null value not allowed - field 2 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: ERROR: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_base.c:525]: dbt_insert(): cannot insert the new row!! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: ERROR: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:1004]: tps_db_insert_branch(): failed to store message Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: ERROR: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:615]: tps_storage_record(): failed to store

2 1

Using maxload in dispatcher list
by Calvin E. 19 Sep '23

19 Sep '23

Should maxload work with all dispatcher algorithms? I'm trying to add a test node to dispatcher.list with maxload=1 and it is getting a lot more than one concurrent call. The test node is the last one in the list. 16 sip:10.x.x.43:5070 0 0 duid=duid01;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.44:5070 0 0 duid=duid02;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.47:5070 0 0 duid=duid03;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.48:5070 0 0 duid=duid04;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.56:5070 0 0 duid=duid05;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.57:5070 0 0 duid=duid06;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.58:5070 0 0 duid=duid07;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.x:5070 0 0 duid=duid08;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.104:5060 0 0 duid=duid09;user=+10007787878;sockname=floating-internal-ip;maxload=1

2 1

SIP Registartion Sharing between two kamailio
by Lewis Hutchinson 19 Sep '23

19 Sep '23

On the understanding that you have checked the INVITE to 802 and it looks OK but not getting there then I would probably start digging on the networking side of it. You have said no Firewalls however there may be Security Groups and VPC bits going on in AWS. It's hard to say as the level of detail is not in the ticket. Can 802 call 801? What happens if you log 802 into Kamailio 1 and 801 into Kamailio 2 and call either way. Lewis Mission Labs Limited is registered in England, company number 10040088. Trading Office: The Old Milk Depot, Bacup Rd, Rossendale, BB4 7FE. Registered office: The Scalpel, 18th Floor 52 Lime Street, London, EC3M 7AF. Email confidentiality notice: This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. Please consider the environment before you print this email.

1 0

SIP Registartion Sharing between two kamailio using AWS NLB having issue.
by pra.savaliya1987＠gmail.com 19 Sep '23

19 Sep '23

Hello All, I have two kamailio servers and shared the database between two kamailio. version: kamailio 5.5.6 (x86_64/linux) . I have used AWS network load balancer. domain pointed to AWS network load balancer IP address,AWS Network Load Balancer (NLB) to distribute incoming requests to kamailio servers. I have two users in same domain(dev.domain.com). 1. 801(a)dev.domain.com --> Registered on kamailio 1 2. 802(a)dev.domain.com --> Registered on kamailio 2 Two call invites have been received, one for extension 801 and another for extension 802. These call invites will reach kamailio Server 1. kamailio Lookup the users and send call invite to both the devices. 801 registered user will get a ring because it is registered from kamailio 1. but 802 will not get a ring because it's register from kamailio 2. I can able see kamailio send call invite to the both registered devices using sngrep. but it not reach to the 802 device. there i no firewalls so far. also i have took 802 Registered device IP phone logs but there is no Call Invite reach to the 802 device. I have also tried by using "dmq" and "dmq_usrloc" module but the same behavior. what could be the reason? It will be appreciable if anyone help to resolve the issue. Thank you in advance! Pratik Svaliya.

2 1

Increase MAX_BRANCHES_LIMIT
by Lars Jansson 18 Sep '23

18 Sep '23

Hi, I am building a configuration script where for some traffic flows parallel forking will be needed, and in this case I need to go beyond the default max limit of the max amount of branches. Apart from this specific case the traffic load that kamailio will need to handle is very low, let's say just one second here and there with up to 5 concurrent calls at most. This limit is as far as I understand set here: usr/local/src/kamailio-5.6/kamailio/src/core/config.h And the default limit is: #define MAX_BRANCHES_LIMIT 32 /*!< limit of maximum number of branches per transaction */ Here are the questions I have related to this: 1) If I increase the value of this constant in config.h, how high is it reasonable to set this value and still have a stable system? 2) If I increase MAX_BRANCHES_LIMIT beyond 32, are there also other parameters that needs to be changed for the system to be able to cope, and if so whichparameters? Regards, Lars

4 9

. Re: Multiple headers in http client request
by Lewis Hutchinson 18 Sep '23

18 Sep '23

Hi Matteo I have used http_async_client and http_client in both Native & KEMI to good affect for handling SUBSCRIBE & NOTIFY flows however did have a few issues with formatting which took a bit of work to get right. Just to note, something you may want to test. Initially I set about my task using http client within Python (aiohttp and ayncio) and stepped in and out of it from various points in the logic depending on the config I was using at the time. Under load this proved to be a bottle neck and failed load testing. The best options under load were using http_async_client or http_client modules which offered significantly better performance. In the end we took a different approach of using Kafka Module as that had even better performance but that was a decision taken our side not through any fault of the http_async_client or http_client modules Lewis Mission Labs Limited is registered in England, company number 10040088. Trading Office: The Old Milk Depot, Bacup Rd, Rossendale, BB4 7FE. Registered office: The Scalpel, 18th Floor 52 Lime Street, London, EC3M 7AF. Email confidentiality notice: This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. Please consider the environment before you print this email.

1 0

Add Header to reply on failure_route
by Benoit Panizzon 18 Sep '23

18 Sep '23

Hi List I'm attempting to add a header to a reply message on failure. Situation: Registrar => Core => (dispatcher list) => Various IC I would like to know on the registrar, which of the dispatcher groups failed. What I attempted sofar: failure_route[DISPATCH_FAILURE] { append_to_reply("X-RR: (append reply) Final Dispatch Failure $avp(dispgroup):$avp(trunkname)\r\n"); append_hf("X-RR: (append hf) Final Dispatch Failure $avp(dispgroup):$avp(trunkname)\r\n"); $avp(rstatus) = t_get_status_code(); $avp(rtext) = $T_rpl($rr); $avp(rtext) = "REMOTE REPLY: " + $T_rpl($rr); t_send_reply("$avp(rstatus)", "$avp(rtext)"); } I only get status text is getting through to my reply. I would much prefer to add a header which I could then extract on the registrar. Am I missing something which could prevent addition of a header in a reply? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 1

Multiple headers in http client request
by Matteo Brancaleoni 17 Sep '23

17 Sep '23

Hello all :) I'm struggling to add two headers to an http client request, but cannot find a proper way to do it. The headers are Authorization and Content-Type. The first try is with http_client module, beside undocumented, is possible to add multiple headers separating them with "\r\n". What I see is the correct Authorization header, and two Content-Type headers, one with my content type the other with x-www-form-urlencoded, which no one sets ? Second try is with http_async_client which supports multiple headers, but since I'm calling it from an xhttp event route, there's no transaction and request cannot be suspended, so I cannot get results before sending out xhttp response... Any hint? br, Mat

2 3

Orphan Dialog Vars: Probable cause found!
by Benoît Panizzon 15 Sep '23

15 Sep '23

Hi List I wonder if some of the devs could look at the dialog code and maybe confirm my observation of this supposed Bug in Kamailio 5.6 Situation: Two Kamailio, dialog counters synced via DMQ and each node using a local DB as dialog backend. Goal is to count channel usage per customer. modparam("dialog", "db_mode", 1 ) modparam("dialog", "enable_dmq", 1) modparam("dialog", "h_id_start", -1) # Use server_id modparam("dialog", "h_id_step", 2) modparam("dialog", "profiles_with_value", "custcallcounter") If 'JohnDoe' is involved in a call, I do: set_dlg_profile("custcallcounter","JohnDoe"); To check how many calls are busy by JohnDoe I do: get_profile_size("custcallcounter","JohnDoe","$var(channel_use)"); Picture this situation: JohnDoe is initiating a first call via Node1: Node1 created the dialogue and variables, writes them to the database and replicates the dialog vars to Node2 => IN MEMORY Nothing about the running dialog is being written to the Database on Node2, but get_profile_size returns the count on Node2. So while the first call aka dialog is running via Node1, JohnDoe is initiating a second call, this time via Node2. Node2 creates the dialog and writes this to the database. Then the profile with Name 'JohnDoe' is INCREASED on Node2. This is when I suddenly find the dialog_vars on the Node2 database containing information about the dialog started on Node1. So I guess writing to a dialog counter triggers the dialog_vars being written to the Database. When JohnDoe is ending it's first call, then the dialog and dialog_vars are cleaned out of the database on Node1, but NOT on Node2 What I fear happens next: They dialog_vars remaining on the Database of Node 2 accumulate more and more, making the database slower. When a call happens to re use the same hash id and entry, things start going really badly. Could I be right? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

Set a License for Kamailio
by Ali Taher 15 Sep '23

15 Sep '23

Hello, Is it possible to put a kind of license for Kamailio, in a way that it works for 1 week for example, and after that it will not process new requests? Regards,

3 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users