sr-users September 2023

sr-users@lists.kamailio.org

52 participants
59 discussions

by Benoît Panizzon

Hi Team I'm still hunting dialog errors which cause my dialog counters to divert and stick around, basically exploding in my face now and then. I suppose they are DMQ related (maybe packet loss, maybe retransmissions, maybe generic overloading of the virtualized kamailio instances) causing issues with inserting dialog timers on the peer etc. So for the moment I'm running only one instance, no DMQ peer. What I still occasionally see are messages: INVITE]dialog [dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 3 for dlg 0x7ff906294be8 [2482:872] with clid 'A8459C74@7f33ff47' and tags '7f33ff47+1+7d820120+89494caf' '3904288054-1882699775' I found an ancient post, confirming this to be an open bug in Kamailio 1.4 and race condition between the 200 OK reply to an INVITE and the ACK confirming the 200 OK. Someone attempted to backport a fix for opensips to kamailio. Indeed, I see this message occur occasionally after managing the 200 OK reply and routing the ACK. Does anyone know, if this is still a open bug with Kamailio 5.5? Or what else could be the cause of this message? -- 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 ______________________________________________________

10 months, 1 week

Floating Point in variables and arithmetic

by Barry Flanagan

Hi I need to take in a priority (from 0 to 100, 0 being highest prio) and convert this into a Q value between 0 and 1.0 My idea was to simply do: q_value = 1 - ($var(priority)/100) However, it seems Kamailio only deals in integers in the config. A Previous post suggested using xavp vars, but this ends up the same result. Apart from doing a pseudo SQL query "SELECT 1 - (20/100)" is there any way within the config I can do such maths? Thanks -- -Barry Flanagan

10 months, 1 week

uac_auth() in KEMI Python - Drop 401 sent to caller

by Marrold

Hi all, I'm attempting to use the uac module in KEMI (Python) to authenticate outbound requests. When the downstream replies with a 401 the proxy correctly re-sends the request with a Authorization header, but the 401 is also relayed to the caller. As far as I can tell I've converted the example to KEMI correctly, but no matter what I try the 401 is still sent to the caller. Any ideas? The config I'm using is below - The avps are set when the request is sent so aren't visible here. Thanks def ksr_failure_manage(self, msg): if self.ksr_route_natmanage(msg)==-255 : return 1 if KSR.tm.t_is_canceled()>0 : return 1 if KSR.tm.t_check_status("401|407") >0 : KSR.info(f"Got a 40X, should attempt authentication") if KSR.uac.uac_auth()>0: KSR.tm.t_relay() KSR.info (f"Dropping further replies") KSR.set_drop() exit() return 1

10 months, 1 week

Handle the DNS SRV to manage failover

by Massimo Dal Sasso

I need to manage failover in the connection between SCSCF and AS. I need to understand how it is possible to configure Kamailio to handle the DNS SRV to manage failover for UAS transaction like REGISTER. I see that it works for UAC transaction like INVITE, but I am not able to configure Kamailio to work for UAS transaction. Thanks, Massimo ________________________________ Massimo Dal Sasso SW Developer massimo.dalsasso(a)ext.athonet.com [Athonet logo]<https://www.athonet.com/> the mobile core that works for you Athonet Italy Via Cà del Luogo 6/8 36050 Bolzano Vicentino Vicenza-Italy +39 0444 750045 This email and any attachments are confidential and intended solely for the use of the intended recipient. If you are not the named addressee, please be aware that you shall not distribute, copy, use or disclose this email. If you have received this email by error, please notify us immediately and delete this email from your system. Email transmission cannot be guaranteed to be secured or error-free or not to contain viruses. Athonet S.r.l. processes any personal data exchanged in email correspondence in accordance with EU Reg. 679/2016 (GDPR) - you may find here the privacy policy with information on such processing and your rights. Any views or opinions presented in this email are solely those of the sender and do not necessarily represent those of Athonet S.r.l.

10 months, 1 week

Creating CDRs for Missed and failed calls

by Marrold

Hi all, I'm using the acc module along with postgres to generate CDRs. For connected calls the CDRs are created as expected, but in the scenario where a lookup() fails and Kamailio sends a stateless 404 there's no CDR logged. I'm setting the FLT_ACCMISSED and FLT_ACCFAILED flags in the initial request route, but perhaps I have a misunderstanding of how these work? Thanks Matthew

10 months, 1 week

How to validate re-invites without challenging them?

by Benoit Panizzon

Hi List At the moment, we challenge every invite (and re-invite) to make sure the customer is authenticated. Now we have one kind of PBX, which never does not authenticate when we challenge a Re-Invite. According to the vendor of that PBX's RFC interpretation, answering a challenge to a re-invite is optional. If that is ignored by the PBX, then the existing established dialog shall not end. Unfortunately this causes the session timer to run out. I am therefore wondering, if there is a safe way not to challenge re-invites. A Re-Invite contains a To-Tag. So I could bypass authentication on presence of a to-Tag. But then, how do I prevent a customer to just set a spoofed To-Tag to circumvent authentication? Is there a feasible way? 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 ______________________________________________________

10 months, 1 week

DBTEXT + TOPOS

by James Lipski

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

10 months, 1 week

Using maxload in dispatcher list

by Calvin E.

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

10 months, 1 week

SIP Registartion Sharing between two kamailio

by Lewis Hutchinson

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.

10 months, 1 week

SIP Registartion Sharing between two kamailio using AWS NLB having issue.

by pra.savaliya1987＠gmail.com

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.

10 months, 1 week

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 September 2023