sr-users November 2023

sr-users@lists.kamailio.org

47 participants
56 discussions

Re: RADIUS - Can't use extra attributes
by Duarte Rocha 24 Nov '23

24 Nov '23

Hello Daniel, Thanks for the reply. The extra dictionary is already included otherwise an error is thrown and Kamailio doesn't start. However, i realized my mistake now and you were right. I was checking for the extra attributes in a tcpdump and on radius server and i didn't had the dictionary configured on both of them. The extra attributes are in the packet but weren't being listed. One more question. Kamailio doesn't have a way to do a totally custom RADIUS access-request packet right? (Sorry if this opens another thread. I usually just hit reply on the mailing list and let Outlook create the e-mail, but it usually creates another thread and i'm not sure why). Thanks again. Cheers, Duarte

1 0

Re: RADIUS - Can't use extra attributes
by Duarte Rocha 24 Nov '23

24 Nov '23

1 0

Max-Forwards header missing in OPTIONS keep-alive messages
by Christian Schnell 24 Nov '23

24 Nov '23

Hello, in RFC 3261 (sec. 8.1.1.6) it states about the Max-Forwards header field: > A UAC MUST insert a Max-Forwards header field into each request it originates with a value that SHOULD be 70. > > Source: https://datatracker.ietf.org/doc/html/rfc3261#section-8.1.1.6 When Kamailio sends its OPTIONS keep-alive requests (from the nathelper module I believe), Max-Forwards is missing: > OPTIONS sip:alice@example.com:61266 SIP/2.0 > Via: SIP/2.0/UDP aa.bb.cc.dd:5060;branch=z9hG4bK5124450 > From: sip:pinger@sip.example.com;tag=uloc-6550aa14-7456-2461-6390f173-5fdb4667 > To: sip:alice@example.com:61266 > Call-ID: aba25282-2ca72be1-9d1fd53(a)aa.bb.cc.dd > CSeq: 1 OPTIONS > Content-Length: 0 The user agent library I'm using (libre from baresip) rejects these requests with a "400 Bad Request" response, I looked at the sources and it denies these requests because of the missing Max-Forwards header. Of course this suffices for the keep-alive logic because all that's needed is any traffic in both directions to keep both (potential) NATs open. However you might agree that it does look a bit confusing at first, and the RFC is clear about that. So it's not a bug, but is this behavior intended? Thanks, also thanks for all the great work that has been put into Kamailio. Christian

3 3

error sending message to heplify server.
by masoud96＠mail.ru 24 Nov '23

24 Nov '23

Hello, I have an error when sending a message to the heplify server: Nov 23 15:09:59 sip1-life3 kamailio[1045006]: CRITICAL: {2 1395 INVITE ad25bc92-16a8-4be6-a29f-a4e4ee3a2c0c} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045006]: ERROR: {2 1395 INVITE ad25bc92-16a8-4be6-a29f-a4e4ee3a2c0c} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044995]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549fc5f0, len: 445, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044995]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044995]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f2154948b18, len: 1511, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044994]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044995]: ERROR: {2 28117 BYE 65297c88-0834-44ce-a4da-cfd7012c2b85} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f2154979898, len: 485, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044995]: CRITICAL: {2 28117 BYE 65297c88-0834-44ce-a4da-cfd7012c2b85} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044995]: ERROR: {2 28117 BYE 65297c88-0834-44ce-a4da-cfd7012c2b85} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549d9c50, len: 532, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044994]: CRITICAL: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549d9c80, len: 560, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044994]: CRITICAL: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549d9c40, len: 529, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044994]: CRITICAL: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044996]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f215494b6a8, len: 823, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044996]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044996]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1045015]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549fc5a0, len: 507, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1045015]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045015]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044996]: ERROR: {2 16492 INVITE sOPq2dosBQcFpqitxVMlyLxFiuWNLZyk} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549fc158, len: 1037, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044996]: CRITICAL: {2 16492 INVITE sOPq2dosBQcFpqitxVMlyLxFiuWNLZyk} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044996]: ERROR: {2 16492 INVITE sOPq2dosBQcFpqitxVMlyLxFiuWNLZyk} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f2154978c18, len: 506, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1045009]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1045195]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f2154948e00, len: 567, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1045195]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045195]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: {2 6972 INVITE 8f4b30bb-01fa-462d-ab66-8b30c0f7b78e} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f2154948fe8, len: 488, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1045009]: CRITICAL: {2 6972 INVITE 8f4b30bb-01fa-462d-ab66-8b30c0f7b78e} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: {2 6972 INVITE 8f4b30bb-01fa-462d-ab66-8b30c0f7b78e} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549fc158, len: 542, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1045009]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message version: kamailio 5.7.2 (x86_64/linux) 95629c flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 95629c compiled on 14:30:56 Nov 20 2023 with gcc 10.2.1

2 1

Hump presence mwi htable
by David VILLAUME 24 Nov '23

24 Nov '23

Hello, I'm running presence_mwi without database. I'm looking for a way to dump the presence htable content, is there any way to perform that ? Regards [https://storage.letsignit.com/6009878cd5039f000742d6a1/generated/effects_bf…] David VILLAUME Ingénieur Voix Tel : +33 156377321 david.villaume(a)sewan.fr 2 cité Paradis - 75010 PARIS www.sewan.fr<https://cloud.letsignit.com/collect/bc/649d2ea2264803323682b26f?p=qPDZoXyim…> [https://storage.letsignit.com/6009878cd5039f000742d6a1/generated/effects_78…]<https://cloud.letsignit.com/collect/bc/649d2ea2264803323682b26f?p=qPDZoXyim…> [https://storage.letsignit.com/6009878cd5039f000742d6a1/generated/effects_13…]<https://cloud.letsignit.com/collect/bc/649d2ea2264803323682b26f?p=qPDZoXyim…> [https://storage.letsignit.com/6009878cd5039f000742d6a1/generated/effects_24…]<https://cloud.letsignit.com/collect/bc/649d2ea2264803323682b26f?p=qPDZoXyim…>

2 1

RADIUS - Can't use extra attributes
by duarterocha91＠gmail.com 24 Nov '23

24 Nov '23

Hello all, I'm currently implementing a Kamailio with RADIUS. I want to send an Access-Request to my RADIUS server and in order to do that i'm using misc_radius module and radius_does_uri_exist() function without any arguments : "if (radius_does_uri_exist()) {" For my module configuration I have the following configurations : "modparam("misc_radius", "radius_config", "/etc/radcli/radiusclient.conf") modparam("misc_radius", "uri_extra", "Sip-Method=$rm")" From what i understand, with this config my access-request should contain the default attributes and Sip-Method Attribute but that is not happening. Only defaults attributes are included. I've tried to run Kamailio with "-ddd" flag for better debug and i only get this error : "1(176) DEBUG: misc_radius [functions.c:615]: radius_does_uri_user_host_exist(): failure". Is there any other configuration that i must do? Thanks for the help. Cheers, Duarte

2 1

Online devel meeting on matrix - 14:30 UTC, Dec 5, 2023
by Daniel-Constantin Mierla 24 Nov '23

24 Nov '23

Hello, we should consider an online devel meeting sometime soon to summarize what was done at (and still needs to be done after) devel meeting in Dusseldorf and plan a bit the targets for next major release (5.8 or 6.0)? If considered useful, I propose Dec 5 at 14:30UTC (15:30 Berlin/Paris/Madrid/Rome), but we can also look for other dates as well. Topics to be discussed can be added at: - https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings… Pull requests can be made by users without git access. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 1

sips to sip
by David Villasmil 24 Nov '23

24 Nov '23

Hello guys, I have this setup where one side is TLS and the other UDP. Normally this works fine, but we have this provider sending sips as the schema everywhere (from, to, rr, contacts), kamailio sends the same sips to the upstream usp freeswitch. My problem is when FS sends back a 200OK and kamailio forwards it back to the provider, the provider sends an ACK and kamailio can't match it with the dialog and doesn't know where to forward it. i think this is happening because FS when is sees SIPS is setting the contact port as 5081 instead of the usual 5080... Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

5 8

Dialog + DMQ: dlg_ontimeout() triggered on wrong node!
by Benoît Panizzon 23 Nov '23

23 Nov '23

Hello World! Kamailio 5.5 in use. I wonder, how I could prevent this issue. modparam("dialog", "send_bye", 1) modparam("dialog", "default_timeout", 21600) in the corresponding route: $dlg_ctx(timeout_route) = "DIALOG_TIMEOUT"; dlg_manage(); Dialog starts on Node01 and it's variables, status and timer are DMQ synced to Node02 As both nodes have the same information, I guess both arm the timeout trigger and sometimes the wrong node is more trigger friendly. If dlg_ontimeout() is triggered on Node02 then: * No Bye is send, as Node02 is not handling that Dialog. * Dialog is removed from Memory on Node02 and state synced back to Node01 * Dialog is removed from Memory on Node01 too, but NOT from database [*1] * Dialog CDR is never commited on Node01 * Call is never sent to timeout_route And subsequent in dialog messages on Node01 result in: dlg_onroute(): unable to find dialog Did I misconfigure something? Is there a way to make sure the timer is NOT triggered on the node not handling the dialogue? Shall I try by setting the default_timeout and then use a timeout_avp to set that timeout slightly lower AFTER the dialog has started? Or would this be synced to the other node too? I found out, session timer changes are not synced after an initial timer was synced, so you can not extend the session timer after setting a initial timeout. So maybe this is also true for dialog timeout? [*1] this also explains why upon restarting kamailio, the dialog suddenly is back and after timing out again, a CDR is then written with a way too long duration. -- 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 3

set_body() adding or replacing existing body?
by Benoit Panizzon 23 Nov '23

23 Nov '23

Hi I'm trying to change the lifetime timer on a KDMQ dialog message before handing it with dmq_handle_message(); if(has_body("application/json") && $fU == 'dialog') { if (jansson_get("lifetime", $rb, "$var(lifetime)")) { xlog("L_INFO", "$cfg(route): DIALOG JSON action: $var(action) state: $var(state) lifetime: $var(lifetime)\n"); $var(new_lifetime) = $var(lifetime) + 60; $var(newrb) = $rb; jansson_set("integer", "lifetime", $var(new_lifetime), "$var(newrb)"); xlog("L_INFO", "$cfg(route): DIALOG JSON NEW: $var(newrb)\n"); set_body("$var(newrb)","application/json"); msg_apply_changes(); } } dmq_handle_message(); exit; The JSON string looks good after that manipulation, it contains the updated lifetime. But dmq_handle_message() does not seem to get the body anymore. So I wonder what set_body() exactly does. Is it replacing the body or appending to it? Is there a way to crank up debug output in the dialog and/or dmq module? 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

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