- sr-users - kamailio.org

RTC DevRoom at FOSDEM 2025
by Daniel-Constantin Mierla 21 Nov '24

21 Nov '24

Hello, FOSDEM'25 will host again a RTC DevRoom during the afternoon of February 1, 2025 (Saturday) -- more details and the call for presentation can be read at: - https://lists.fosdem.org/pipermail/fosdem/2024q4/003584.html I am not sure if I can participate (chances are more towards no, than to yes), but if anyone considers to go to the event, it will be good to submit a proposal to cover a bit Kamailio as well (it doesn't have to be entirely about Kamailio). Note that FOSDEM imposes a strict deadline this time for submissions (Dec 1, 2024), thus is no much time left. Should anyone in these groups plans to submit a proposal, let us know, so the others have an idea about it. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

1 0

TM-Module, ignoring
by Christian Berger 19 Nov '24

19 Nov '24

Hi, we would like to replicate a SIP-message ("REGISTER" in our case) to a set of nodes for further asynchronous processing. The message is already processed on the local Kamailio. We thought about using the tm-module in conjunction with the dispatcher module so we can reliably forward the message. This seems to work, however we get a new problem: Kamailio forwards the response it gets from those nodes. When we drop the response in the reply_route, it gets dropped before TM can see it. When we drop the response in the on_reply_route, it still will be forwarded. (adding or removing a header here works, however) $du is set to $null. Is there any clean way to suppress that response being forwarded back to the original requester? Best regards Christian Berger -- Christian Berger - berger(a)sipgate.de Telefon: +49 (0)211-63 55 55-0 Telefax: +49 (0)211-63 55 55-22 sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.co.uk

2 2

Not able to use SRTP - from client to proxy
by Sajid Khan 18 Nov '24

18 Nov '24

Im using the module RTPengine. im having issues when ever i try to do a call using SRTP im using microsip i have checked the SDP everything ok. But when ever i place the call it gets rejected. if i disable SRTP then the calls work if (!rtpengine_offer("replace-origin replace-session-connection ICE=force RTP/SAVP RTP/AVP")) { I only need to encrypt client -> proxy from proxy -> asterisk should be plain rtp i hope someone can help me out thank you. The log in rtpengine shows this [1731055305.417896] ERR: [2a721ebf2c73414ab8e739d7bde912f9//1 port 14124]: [srtp] SRTP output wanted, but no crypto suite was negotiated

4 4

Kamailio 5.5.7 crash
by Mitesh Thakkar 18 Nov '24

18 Nov '24

Hi, I have recently migrated from Kamailio 5.2.5 to Kamailio 5.5.7. After a migration, the Kamailio crashed. Also, there were a lot of errors and warnings. Can someone help me to understand why this happened and what could be the solution? Logs (upside down): 18(397) INFO: <core> [main.c:859]: sig_usr(): signal 15 received 2(381) INFO: <core> [main.c:859]: sig_usr(): signal 15 received 30(409) INFO: <core> [main.c:859]: sig_usr(): signal 15 received 8(387) INFO: <core> [main.c:859]: sig_usr(): signal 15 received 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/tcp_read.c:1863]: handle_io(): io_watch_del failed for 0x7f526aa7f458 id 0 fd -1, state -1, flags 0, main fd 0, refcnt 0 ([]:0 -> []:0) 35(414) WARNING: <core> [core/tcp_read.c:1840]: handle_io(): F_TCPCONN connection marked as bad: 0x7f526aa7f458 id 0 fd -1 refcnt 0 ([]:0 -> []:0) 35(414) CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd -1, not in [0, 2) OS: Ubuntu 22.04.5 LTS \n \l # kamailio --version version: kamailio 5.5.7 (x86_64/linux) 272fdd flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, 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: 272fdd compiled on 14:21:35 Oct 21 2024 with gcc 11.4.0 # dpkg -l |grep openssl ii openssl 3.0.2-0ubuntu1.18 amd64 Secure Sockets Layer toolkit - cryptographic utility Regards, Miteshkumar Thakkar

2 1

Pua PUBLISH method over xmlrpc/jsonrpc
by dries＠degendt.com 18 Nov '24

18 Nov '24

Hi all I've installed a (pretty old) presence_dfks module that allows setting the presence using the following command: kamctl fifo pua_publish sip:1000@10.10.99.254 3600 as-feature-event application/x-as-feature-event+xml . . . "<?xml version='1.0' encoding='ISO-8859-1'?><ForwardingEvent><device><notKnown/></device><forwardingType>forwardImmediate</forwardingType><forwardStatus>true</forwardStatus><forwardTo>1234</forwardTo></ForwardingEvent>" The "pua_mi" module was however removed in Kamailio and jsonrpcs/xmlrpcs are supposed to be an alternative. I've tried both the following calls, but neither does recognize the pua_publish/pua.publish as a valid method. Attempt with jsonrpc: curl -H "Content-Type: application/json" -X POST -d '{"jsonrpc": "2.0", "method": "pua.publish", "params": [""], "id":1}' https://sbctest.tel.redacted.xx:5061/RPC/ ERROR: jsonrpcs [jsonrpcs_mod.c:1422]: ki_jsonrpcs_dispatch(): method callback not found [pua.publish] Attempt with xmlrpc: curl -H "Content-Type: text/xml" -X POST -d '<?xml version="1.0" ?><methodCall><methodName>pua_publish</methodName><params><param><value><string>sip:jh@sbctest.tel.redacted.xx</string></value></param><param><value><string>7776000</string></value></param><param><value><string>as-feature-event</string></value></param><param><value><string>application/as-feature-event</string></value></param><param><value><string>.</string></value></param><param><value><string>a.1481534683.13958.6.7</string></value></param><param><value><string>sip:127.0.0.1:5080;transport=tcp</string></value></param><param><value><string>P-Flags: 0</string></value></param><param><value><string>Messages-Waiting: yesMessage-Account: sip:jh@sbctest.tel.redacted.xxVoice-Message: 2/0 (0/0)</string></value></param></params></methodCall>' https://sbctest.tel.redacted.xx:5061/RPC/ <?xml version="1.0"?> <methodResponse> <fault> <value> <struct> <member> <name>faultCode</name> <value><int>500</int></value> </member> <member> <name>faultString</name> <value><string>Method Not Found</string></value> </member> </struct> </value> </fault> Anyone who had some luck in this matter? Best regards, Dries

3 6

SIP NOTIFY over TLS fails
by dries＠degendt.com 15 Nov '24

15 Nov '24

Hi all I've installed a custom presence_dkfs module (https://github.com/tombeard/presence_dfks) in an effort to make our Grandstream devices (connected over TLS) display a server set callforward using Broadsoft's Device Feature Key Sync. The module was installed succesfully, but it appears that the NOTIFY upon SUBSCRIBE cannot be sent over TLS. This part seems to use the default presence module however so I'm taking my chances here to ask for some advice. I have already disabled verify_certificate in tls.cfg. The "dst addr: 193.19x.x.x:0" does seem to have an incorrect port as I should expect 5061? INFO: {1 600000 SUBSCRIBE 319937814-5062-3(a)BHC.DA.GB.CD} presence [notify.c:1744]: send_notify_request(): NOTIFY sip:544460@sbctest.tel.redacted.xx via sip:544460@172.30.61.23:5062;transport=tls on behalf of sip:544460@sbctest.tel.redacted.xx for event as-feature-event : 319937814-5062-3(a)BHC.DA.GB.CD ERROR: tls [tls_server.c:1312]: tls_h_read_f(): protocol level error ERROR: tls [tls_util.h:50]: tls_err_ret(): TLS connect:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure (sni: unknown) ERROR: tls [tls_server.c:1316]: tls_h_read_f(): src addr: 172.30.61.23:5062 ERROR: tls [tls_server.c:1319]: tls_h_read_f(): dst addr: 193.19x.x.x:0 ERROR: <core> [core/tcp_read.c:1526]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f6d55b4b360 r: 0x7f6d55b4b488 (-1) Your advice is most appreciated! Cheers, Dries

4 7

dlq_req_within() usage for 3pcc-style reinvite media setup
by Alex Balashov 14 Nov '24

14 Nov '24

Hi, I am trying to use dlg_req_within() for a 3pcc-style call setup, to set up media via a reinvite: 1. Store original SDP offer from caller in $dlg_var()s; 2. Later, after e2e ACK is processed for initial INVITE transaction, send reinvite to callee using dlg_req_within(). I call rtpengine_offer() and feed it the original SDP offer (via read_sdp_pv modparam), and take the RTPEngine-transformed SDP and feed that to dlg_req_within(): dlg_req_within("callee", "INVITE", "application/sdp", "$var(sdp_from_rtpengine)"); 3. I have found that event_route[tm:local-response] does not allow me to capture the 200 OK / SDP answer to this reinvite; it is internally absorbed. However, it is possible to arm an onreply_route in event_route[tm:local-request], to receive the 200 OK: event_route[tm:local-request] { if(method == "INVITE" && has_body("application/sdp")) t_on_reply("REINVITE_REPLY"); } 4. My intent is for this reinvite reply handler to set off a reinvite to the caller side: onreply_route[REINVITE_REPLY] { if(method == "INVITE" && has_body("application/sdp") && t_check_status("200")) { ... $var(rtpengine_use_this_sdp) = $rb; rtpengine_answer("..."); dlg_req_within("caller", "INVITE", "application/sdp", "$var(sdp_from_rtpengine)"); } This ensures proper relay symmetry. Otherwise, the caller will continue to send RTP to the previous upstream endpoint of the call, prior to any reinvite. However, dlg_req_within() doesn't work in this later context, even though the documentation says it can be used from ANY_ROUTE. Kamailio doesn't complain, there is no error. It just doesn't initiate a reinvite to the caller. I considered the possibility that this may be because the calling scope is that of a pending reinvite transaction to the callee, but there is no obvious way to defer that into the future. If I send it to an async task worker, the transaction scope required for dlg_req_within() to know which dialog it's operating on will be lost. Any ideas appreciated, and thank you in advance! -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

2 2

KEMI / Python Issues
by Daniel W. Graham 14 Nov '24

14 Nov '24

Experimenting with KEMI for the first time, I ran into a few issues and hoping someone has feedback. kamailio 5.8.3 In the following python example, 'if ksr.is_method("ACK"):' should never be reached. Below is debug. if not ksr.siputils.has_totag(): ksr.info("has to tag") sys.exit() if ksr.is_method("ACK"): if ksr.tm.t_check_trans(): ksr.relay() sys.exit) else: sys.exit() ksr.sl.send_reply(404, "Not here") sys,exit() ..... DEBUG: app_python3s [apy3s_kemi.c:365]: sr_apy_kemi_exec_func_ex(): execution of method: siputils.has_totag DEBUG: siputils [checks.c:122]: has_totag(): no totag DEBUG: app_python3s [apy3s_kemi.c:368]: sr_apy_kemi_exec_func_ex(): execution of method: is_method DEBUG: app_python3s [apy3s_kemi.c:389]: sr_apy_kemi_exec_func_ex(): number of arguments: 1 DEBUG: app_python3s [apy3s_kemi.c:365]: sr_apy_kemi_exec_func_ex(): execution of method: sl.send_reply DEBUG: app_python3s [apy3s_kemi.c:389]: sr_apy_kemi_exec_func_ex(): number of arguments: 2 DEBUG: sl [sl.c:306]: send_reply(): reply in stateless mode (sl) ..... Second, here are a couple errors I have seen a few times but havent been able to identify the underlying issue, mainly hoping for more context on the meaning of 'execution of route type 1 with no name returned -1'. ERROR: app_python3s [apy3s_kemi.c:146]: apy3s_exec_func(): error exception occurred DEBUG: app_python3s [apy3s_kemi.c:230]: sr_kemi_config_engine_python(): execution of route type 1 with no name returned -1 Any input is appreciated. * dan

2 7

WG: [External] RE: Question regarding error message "failed to add new socket to the fd list"
by Floimair Florian 14 Nov '24

14 Nov '24

Thank you Henning! Here are the configured limits for Kamailio Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 8388608 unlimited bytes Max core file size unlimited unlimited bytes Max resident set unlimited unlimited bytes Max processes 31543 31543 processes Max open files 16384 16384 files Max locked memory unlimited unlimited bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 31543 31543 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us This is what I know so far: There seems to be a problem with siptrace module (going via TCP to a heplify-server on another host), but I’m not sure if this is a coincidence or the cause of the problems. I see quite a bit of these before the actual problem arises: Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322822]: ERROR: <core> [core/tcp_main.c:630]: _wbufq_add(): (591 bytes): write queue full or timeout (32498, total 43196, last write 0 s ago) Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322822]: ERROR: siptrace [../../core/forward.h:261]: msg_send_buffer(): tcp_send failed Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322822]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322829]: ERROR: <core> [core/tcp_main.c:4023]: handle_ser_child(): received CON_ERROR for 0x7fe054f8ae10 (id 727321), refcnt 2, flags 0x3096 At some point then all things go south and the log is flooded with these messages Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322829]: CRITICAL: <core> [core/io_wait.h:596]: io_watch_del(): invalid fd 2244, not in [0, 482) Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322829]: ERROR: <core> [core/tcp_main.c:4677]: handle_tcpconn_ev(): io_watch_del(3) failed: for 0x7fe054f8ae10, fd 2244 And then ultimately the above combined with the initially mentioned Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322829]: CRITICAL: <core> [core/tcp_main.c:4264]: handle_ser_child(): failed to add new socket to the fd list And occasionally also something like this Nov 4 07:54:01 kamailio-prod-westeurope-2 /usr/sbin/kamailio[322829]: ERROR: <core> [core/io_wait.h:373]: io_watch_add(): trying to overwrite entry 2247 watched for 5 in the hash 0x5621dc404ee0 (fd:-601539712, type:22049, data:0x5621dc23c004) with (2247, 2, 0x7fe04f85c2a0) In total these add up to roughly 3600 lines per second (!!) in the log, so it is quickly flooded with these. Florian FLOIMAIR Software Development - Symphony Cloud Services (1568) Von: Henning Westerholt <hw(a)gilawa.com> Datum: Montag, 11. November 2024 um 19:52 An: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Cc: Floimair Florian <f.floimair(a)commend.com> Betreff: [External] RE: Question regarding error message "failed to add new socket to the fd list" CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hello Florian, Any other error messages before that error happens, e.g. something about the memory. Otherwise, it could be indeed a ulimit issue. First step would be to check the actual configured limits for the kamailio user. Cheers, Henning From: Floimair Florian via sr-users <sr-users(a)lists.kamailio.org> Sent: Montag, 11. November 2024 17:45 To: sr-users(a)lists.kamailio.org Cc: Floimair Florian <f.floimair(a)commend.com> Subject: [SR-Users] Question regarding error message "failed to add new socket to the fd list" Hi! We have recently had issues with one of our Production Kamailios. When those happened, the log was filled with the following message: CRITICAL: <core> [core/tcp_main.c:4528]: handle_new_connect(): failed to add new socket to the fd list Now I wonder what the best approach is to prevent this. We are using TCP/TLS only and I think this might be related to the file ulimit, but I am not sure about that. Shared memory is set to 512MB Can you give me a hint on what to look for? Thank you very much! P.S.: Sorry, I accidentally replied to a previous post of a different topic before which is totally unrelated (I think I should stop working for today 😉) FLORIAN FLOIMAIR Software Development - Symphony Cloud Services Commend International GmbH Saalachstrasse 51 5020 Salzburg, Austria [signature_2072127332] commend.com LG Salzburg / FN 178618z

2 1

Tell topos to create 'duplicate' route header from rr header with same ip
by Benoit Panizzon 14 Nov '24

14 Nov '24

Hi Gang I'm having another go with a dedicated kamailio running topos to replace a B2BUA SBC. I came across this situation: Server Topology: Kamaiolio SBC (topos) <=> Kamailio Registrar <=> Kamailio Router (DLG + CDRS) Core IP Address 10.0.0.1 Registrar IP 10.0.0.2 Two different CPE are registered on Registrar via SBC One CPE is calling the other CPE So the path the call is taking is: CPE A => SBC => Registrar => Core => Registrar => SBC => CPE B Invite A => B goes through, no issue. 180 Ringing, required 100rel B => A requires the route to be recorded therefore contains 3 record route statements: Record Route: <sip:10.0.0.2;lr> Record Route: <sip:10.0.0.1;lr> Record Route: <sip:10.0.0.2;lr> To ensure answer will get route back to the registrar => core => registrar and then the contact pointing to the SBC with topos to restore the last hop. Ringing B => A works as expected and is answered by A with PRACK. topos would now need set Route: in this PRACK message, according to the received Record Route Header. Unfortunately I fear Topos 'removes' the routes with duplicate host ip. I only get: Route: <sip:10.0.0.2> Route: <sip:10.0.0.1> Causing the Core not to be able to route the PRACK back to the registrar. To test, which line is being dropped, I added an mark to each one and determined the 3rd Record Router is being dropped by topos, probably considered a duplicate. I found no setting of the 'do not perform record route header dupe detection'. Interestingly, when I look at the database field topos_d.b_rr all three entries are present in the correct order. Has anyone come over the same issue and found a solution? Maybe related to: https://github.com/kamailio/kamailio/issues/3778 ? 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 0

Kamailio Developers Meeting, Nov 19-20, 2024, in Dusseldorf
by Daniel-Constantin Mierla 14 Nov '24

14 Nov '24

Hello, Kamailio SIP Server project is organizing another meeting of its developers and community members during November 19-20, 2024 (Tue-Wed), hosted again by sipgate.de in Dusseldorf, Germany. The event is intended to facilitate the interaction between Kamailio developers and contributors in order to offer a convenient environment for working together on several topics of high interest for the project, including writing code for Kamailio and its tools, improving documentation, or discuss about future development. Everyone from the community is welcome to join, developer or user interested in helping the project. Please note we have a limited capacity of seats in the meeting room, the main policy for accepting participants being first come first server. Also, very important to be aware that this is not an event to learn how to use Kamailio. More details about the event, the venue, how to register, are available at: * https://www.kamailio.org/w/developers-meeting/ Looking forward to those two intensive hacking Kamailio days in Dusseldorf! Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

2 4

Kamailio v5.8.4 Released
by Daniel-Constantin Mierla 12 Nov '24

12 Nov '24

Hello, Kamailio SIP Server v5.8.4 stable release is out. This is a maintenance release of the latest stable branch, 5.8, that includes fixes since the release of v5.8.3. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.8.x. Deployments running previous v5.8.x versions are strongly recommended to be upgraded to v5.8.4. For more details about version 5.8.4 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2024/11/kamailio-v5-8-4-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

1 0

Releasing v5.8.4
by Daniel-Constantin Mierla 12 Nov '24

12 Nov '24

Hello, I am considering to release Kamailio v5.8.4 (out of branch 5.8) sometime next week, most likely on Tuesday, Nov 12, 2024. If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

6 10

fail2ban complains about Kamailio syslog messages
by Juha Heinanen 12 Nov '24

12 Nov '24

When Kamailio message parser produces this kind of syslog message: 024-11-11T21:16:40.757364+02:00 box /usr/bin/sip-proxy[181398]: ERROR: <core> [core/parser/msg_parser.c:791]: parse_msg(): ERROR: parse_msg: message=<#026#003#001#006\340#001> fail2ban complains: Consider setting logencoding to appropriate encoding for this jail. Continuing to process line ignoring invalid characters: b'2024-11-11T21:06:15.347318+02:00 box /usr/bin/sip-proxy[181398]: ERROR: <core> [core/parser/msg_parser.c:791]: parse_msg(): ERROR: parse_msg: message=<#026#003#001#006\xc0#001>\n': 1 Time(s) Error decoding line from '/var/log/syslog' with 'UTF-8'.: 1 Time(s) Unable to retrieve Watch object associated to <_RawEvent cookie=0 mask=0x2 name='' wd=13 >: 3 Time(s) Would it be possible to somehow ensure that Kamailio syslog messages only contain valid UTF-8 characters? -- Juha

1 0

Last line of onreply_route (drops reply)
by James Browne 11 Nov '24

11 Nov '24

Hi all I noticed, in my config, that if the last line of the reply_route is a function that does not succeed, then the SIP response is not relayed and kamailio throws an error. I've searched documentation to indicate why this might be, but I can't find anything, so this looks to me like a bug. I use 5.8.1 for testing. Here's a sample config that shows what goes wrong. #################### #!KAMAILIO listen=udp:203.0.113.57:5060 debug=1 loadmodule "textops" request_route{exit;} reply_route{remove_hf_re("^X-Custom");} #################### Here's a sample SIP message that works. When I send this to udp:203.0.113.57:5060, kamailio relays it. #################### SIP/2.0 200 Testing Via: SIP/2.0/UDP 203.0.113.57:5060;branch=z9hG4bK-d8754z Via: SIP/2.0/UDP 198.18.0.157:5060;branch=z9hG4bK-d8754z T: <sip:c@s>;tag=676fbf45 F: <sip:c@s>;tag=676fbf45 X-Custom: lkjdfl i: testing-XXX CSeq: 1 INFO l: 0 #################### If I then remove the X-Custom header field from the SIP reply and try again, the message does not get relayed and I see this in the log. 5(1356) WARNING: <core> [core/receive.c:605]: receive_msg(): error while trying onreply script If I put a log command after the remove_hf_re(), then the message gets relayed. It looks like the reply_route always fails if the last function is not successful. Is this normal or is it a bug? James

3 5

Question regarding error message "failed to add new socket to the fd list"
by Floimair Florian 11 Nov '24

11 Nov '24

Hi! We have recently had issues with one of our Production Kamailios. When those happened, the log was filled with the following message: CRITICAL: <core> [core/tcp_main.c:4528]: handle_new_connect(): failed to add new socket to the fd list Now I wonder what the best approach is to prevent this. We are using TCP/TLS only and I think this might be related to the file ulimit, but I am not sure about that. Shared memory is set to 512MB Can you give me a hint on what to look for? Thank you very much! P.S.: Sorry, I accidentally replied to a previous post of a different topic before which is totally unrelated (I think I should stop working for today 😉) FLORIAN FLOIMAIR Software Development - Symphony Cloud Services Commend International GmbH Saalachstrasse 51 5020 Salzburg, Austria [signature_2072127332] commend.com LG Salzburg / FN 178618z

2 1

apt-key deprecation
by tom＠tomlynn.com 11 Nov '24

11 Nov '24

When I look at the debian repositories maintained by the project, there are instructions to import the public key of the repository for apt using this command: wget -O http://deb.kamailio.org/kamailiodebkey.gpg | sudo apt-key add - which results in: Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). gpg: no valid OpenPGP data found. Is there an alternate method that can be posted in the repository that will get better results? Thank you, TL

5 5

Unable to get body in multipart body
by Anthony Blandin 08 Nov '24

08 Nov '24

Hello, I want to get a body for content-type "application/isup" but I have the following error: 4(16) DEBUG: textops [textops.c:3394]: ki_get_body_part_helper(): found content type application/isup 4(16) ERROR: textops [textops.c:3397]: ki_get_body_part_helper(): no CRLF found after content type Here is the INVITE sent: INVITE sip:+883390000010022@[remote_ip]:[remote_port];user=phone SIP/2.0 From: <sip:+883390000010007@[local_ip];user=phone>;tag=[call_number] To: <sip:+883390000010022@[remote_ip];user=phone> Max-Forwards: 70 Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch] Route: <sip:[local_ip]:[local_port];transport=udp;lr> Record-Route: <sip:[local_ip]:[local_port];transport=udp;lr> Call-ID: [call_id] CSeq: 1 INVITE P-Asserted-Identity: <sip:+883390000010007@[local_ip]:[local_port];user=phone> Accept: application/sdp,application/isup,multipart/mixed Allow: INVITE,ACK,CANCEL,BYE,OPTIONS,INFO,PRACK,UPDATE P-Charging-Vector: icid-value=IBCF-1-161460836711652742337;icid-generated-at=BC00.QX00.ORANGE-MSS.FR;orig-ioi=ORANGE-MSS.FR Supported: 100rel Content-Type: multipart/mixed;boundary=unique-boundary-1 MIME-Version: 1.0 Contact: <sip:[local_ip]:[local_port];transport=udp> Content-Length:[len] --unique-boundary-1 Content-Type: application/sdp v=0 o=user1 53655765 2353687637 IN IP[local_ip_type] [local_ip] s=- c=IN IP[local_ip_type] [local_ip] t=0 0 a=sendrecv m=audio [media_port] RTP/AVP 8 96 b=RR:0 b=RS:0 a=rtpmap:8 PCMA/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 a=ptime:20 a=maxptime:40 --unique-boundary-1 Content-Type: application/isup;version=spirou;base=itu-t92+ Content-Disposition: signal;handling=required \x01\x11\x20\x01\x0a\x00\x02\x0c\x0a\x04\x10\x88\x33\x09\x00\x00\x01\x20\xf2\x0a\x0a\x84\x13\x88\x33\x09\x00\x00\x01\x00\x07\x1d\x03\x80\x90\xa3\x3f\x07\x83\x97\x26\x87\x41\x00\x00\x39\x04\x34\xc0\x3f\xc0\x00 --unique-boundary-1-- CRLF is well added at the end of Content-Type header, is anybody could help me to solve this issue? Regards, Anthony

1 0

[db_unixodbc] how to specify the database with unixodbc？
by 17603019528＠163.com 08 Nov '24

08 Nov '24

Hi Dear Community, I want to use db_unixodbc to connect to the dm8 database. Although I use Opensips, I found that this module db_unixodbc, Kamailio and Opensips are the same. My question is how to specify the database with kamailio？ I add "Database = sbc" into odbc.ini, But nothing happened。 ###### cat /usr/local/etc/odbc.ini [DM8] Description = ODBC DRIVER FOR DM8 Driver = DM8 ODBC DRIVER SERVER = 172.16.7.131 TCP_PORT = 5230 odbcinst -j unixODBC 2.3.12 DRIVERS............: /usr/local/etc/odbcinst.ini SYSTEM DATA SOURCES: /usr/local/etc/odbc.ini FILE DATA SOURCES..: /usr/local/etc/ODBCDataSources USER DATA SOURCES..: /root/.odbc.ini SQLULEN Size.......: 8 SQLLEN Size........: 8 SQLSETPOSIROW Size.: 8 ####### #################### modparam("usrloc", "db_url", "unixodbc://opensips:opensips#$@172.16.7.131:5230/dm8") #################### DBG:db_unixodbc:db_unixodbc_new_connection: opening connection: unixodbc://xxxx:xxxx@172.16.7.131/dm8 Nov 7 17:05:21 [145] DBG:db_unixodbc:db_unixodbc_new_connection: connection succeeded with reply <DSN=dm8;SERVER=172.16.7.131;UID=opensips;PWD=opensips#$;TCP_PORT=5230;> DBG:core:db_do_init: connection 0xfffd5bbbaf08 inserted in pool as 0xfffd5bbbb0e0 Nov 7 17:05:21 [145] ERROR:db_unixodbc:db_unixodbc_submit_query: rv=-1. Query= select table_version from version where table_name='dialog' Nov 7 17:05:21 [145] ERROR:db_unixodbc:db_unixodbc_extract_error: unixodbc:SQLExecDirect=42S02:1:-2106:Error in line: 1 ####################

2 1

Draining TCP/TLS SIP sessions from Kamailio and media sessions from RTPEngine
by Evgenii Buchnev 07 Nov '24

07 Nov '24

Hi Dear Community, Would appreciate your input into where to look further to explore my options and would be good to learn your experience with the following. There are many active-active kamailio nodes behind tcp load balancer. On the same VM with each Kamailio there is an instance of RTPEngine to manage Media/Transcoding/Etc for that Kamailio. This scales UP easily - new nodes just added behind tcp load balancer. To be able to scale down and/or update node configuration - I'd like to be able to drain sessions/calls properly and pass any active calls from current Kamailio and RTPEngine to other nodes. DMQ is not yet in place, although it's planned. What would be proper ways of migrating RTP sessions to other RTPEngines? Caveats? Also wonder how properly a tcp/tls based SIP session can be passed to another Kamailio? Thank you in advance for your input. Evgenii Buchnev

3 2

Roadmap to v6.0.0 - the next major release
by Daniel-Constantin Mierla 07 Nov '24

07 Nov '24

Hello, about 8 months since the last major release v5.8.x, therefore it is the time to plan a bit the next steps for getting v6.0.0 out. The Kamailio Developers Meeting is schedule in Dusseldorf, Germany during November 19-20, 2024, where we expect to push out a consistent number of updates. Then maybe we can wait for another 2 weeks or so to settle down/finish those updates. After that, if no other new features are planned by developers in short term, we can enter the testing phase, so the new major version can be released during the second part of January 2025 or first part of February 2025. Therefore, if you have new features under development that might require more than 1-1.5 months from now, and you want to get them in v6.0.0, let us know to plan properly. Other time lines suggestions to get to v6.0.0 are also welcome! Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

2 1

Kamailio 5.5.7 alias not added to ACK
by Mitesh Thakkar 06 Nov '24

06 Nov '24

Hi, I was using kamailio 5.2.5. I have recently upgraded to kamailio 5.5.7. After upgrade, the alias is stop being add to the ACK of reinvite from upstream. Before upgrade, it was working fine. I’ll appreciate any help on this. Thank you. Regards, Miteshkumar Thakkar

1 0

SNMP setup
by Sergio Charrua 05 Nov '24

05 Nov '24

Hi all! I am having difficulties setting up SNMP, and mostly to figure out if what I have setup is correctly configured. This is what I have on Kamailio (5.8.2), which is set as stateless and as a redirect server (simply put, it receives INVITE from SBC, gets a route from routing services, modifies Contact header, and replies to SBC with 300 Multi Choice with new contact header): loadmodule "db_mysql.so" loadmodule "db_cluster.so" loadmodule "http_client.so" loadmodule "jsonrpcs.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "sl.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "textops.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "jansson.so" loadmodule "snmpstats.so" loadmodule "file_out.so" loadmodule "ctl.so" loadmodule "permissions.so" loadmodule "xhttp.so" loadmodule "xhttp_rpc.so" # ---- SNMP Stats params ---- modparam("snmpstats", "sipEntityType", "proxyServer") modparam("snmpstats", "sipEntityType", "redirectServer") modparam("snmpstats", "sipEntityType", "other") modparam("snmpstats", "snmpgetPath", "/usr/bin/") modparam("snmpstats", "MsgQueueMinorThreshold", 1) modparam("snmpstats", "MsgQueueMajorThreshold", 1) modparam("snmpstats", "dlg_minor_threshold", 1) modparam("snmpstats", "dlg_major_threshold", 1) modparam("snmpstats", "snmpCommunity", "kamailio") I have set the *_minor_threshold values to bear minimum. Should I add anything else? The logs show the following messages: DEBUG: <core> [core/mem/q_malloc.c:402]: qm_malloc(): qm_malloc(0x7f03af1ff010, 60) called from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) DEBUG: <core> [core/mem/q_malloc.c:449]: qm_malloc(): qm_malloc(0x7f03af1ff010, 64) returns address 0x7f03af3bcc50 frag. 0x7f03af3bcc10 (size=64) on 1 -th hit DEBUG: <core> [core/mem/q_malloc.c:402]: qm_malloc(): qm_malloc(0x7f03af1ff010, 20) called from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) DEBUG: <core> [core/mem/q_malloc.c:449]: qm_malloc(): qm_malloc(0x7f03af1ff010, 32) returns address 0x7f03af3bcd00 frag. 0x7f03af3bccc0 (size=32) on 1 -th hit DEBUG: <core> [core/mem/q_malloc.c:515]: qm_free(): qm_free(0x7f03af1ff010, 0x7f03af3bcc50), called from snmpstats: snmp_statistics.c: get_total_bytes_waiting(464) DEBUG: <core> [core/mem/q_malloc.c:562]: qm_free(): freeing frag. 0x7f03af3bcc10 alloc'ed from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) DEBUG: <core> [core/mem/q_malloc.c:515]: qm_free(): qm_free(0x7f03af1ff010, 0x7f03af3bcd00), called from snmpstats: snmp_statistics.c: get_total_bytes_waiting(471) DEBUG: <core> [core/mem/q_malloc.c:562]: qm_free(): freeing frag. 0x7f03af3bccc0 alloc'ed from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) DEBUG: <core> [core/mem/q_malloc.c:402]: qm_malloc(): qm_malloc(0x7f03af1ff010, 60) called from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) DEBUG: <core> [core/mem/q_malloc.c:449]: qm_malloc(): qm_malloc(0x7f03af1ff010, 64) returns address 0x7f03af3bcc50 frag. 0x7f03af3bcc10 (size=64) on 1 -th hit DEBUG: <core> [core/mem/q_malloc.c:402]: qm_malloc(): qm_malloc(0x7f03af1ff010, 20) called from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) DEBUG: <core> [core/mem/q_malloc.c:449]: qm_malloc(): qm_malloc(0x7f03af1ff010, 32) returns address 0x7f03af3bcd00 frag. 0x7f03af3bccc0 (size=32) on 1 -th hit DEBUG: <core> [core/mem/q_malloc.c:515]: qm_free(): qm_free(0x7f03af1ff010, 0x7f03af3bcc50), called from snmpstats: snmp_statistics.c: get_total_bytes_waiting(464) DEBUG: <core> [core/mem/q_malloc.c:562]: qm_free(): freeing frag. 0x7f03af3bcc10 alloc'ed from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) DEBUG: <core> [core/mem/q_malloc.c:515]: qm_free(): qm_free(0x7f03af1ff010, 0x7f03af3bcd00), called from snmpstats: snmp_statistics.c: get_total_bytes_waiting(471) DEBUG: <core> [core/mem/q_malloc.c:562]: qm_free(): freeing frag. 0x7f03af3bccc0 alloc'ed from snmpstats: snmp_statistics.c: get_socket_list_from_proto_and_family(185) INFO: snmpstats [utilities.c:116]: get_statistic(): failed to retrieve statistics for active_dialogs INFO: snmpstats [utilities.c:116]: get_statistic(): failed to retrieve statistics for active_dialogs The SNMP daemon is set as follows: - /etc/snmp]$ cat snmptrapd.conf # Example configuration file for snmptrapd # # No traps are handled by default, you must edit this file! # # authCommunity log,execute,net public # traphandle SNMPv2-MIB::coldStart /usr/bin/bin/my_great_script cold and on /etc/snmp/snmpd.conf: ############################################################################### # Further Information # # See the snmpd.conf manual page, and the output of "snmpd -H". agentaddress udp:161 rocommunity kamailio master agentx agentXSocket tcp:localhost:705 trap2sink 10.X.Y.Z netcool 162 When running tcpdump and listening on port 162, no traffic is captured....it seems to me that Kamailio is not sending anything to SNMP Any clue, anyone? What am I doing wrong? Atenciosamente / Kind Regards / Cordialement / Un saludo, *Sérgio Charrua*

3 3

Function sdp_get gets extra blank line (when MIME is used)
by James Browne 05 Nov '24

05 Nov '24

The sdp_get() function from sdpops returns an extra blank line sometimes, which looks like a bug to me. When I have an SDP that's in MIME, there's an extra newline at the end of the extracted SDP. Here's a sample config. I use 5.8.1 for testing. #################### #!KAMAILIO listen=udp:203.0.113.57:5060 debug=1 loadmodule "sdpops" loadmodule "pv" loadmodule "xlog" request_route{exit;} reply_route { sdp_get("$avp(sdp)"); xlog("L_NOTICE", "[$ci] The SDP is [$avp(sdp)].\n"); } #################### Here are two sample SIP-message bodies. #################### v=0 o=PCD 1730 1730 IN IP4 198.18.114.148 s=PCD c=IN IP4 198.18.114.148 t=0 0 m=audio 29426 RTP/AVP 0 a=rtpmap:0 PCMU/8000 #################### #################### --e61e7a6a-16a2-46c0-adbb-a41ba86d32a2 Content-Type: application/sdp Content-Length: 130 v=0 o=PCD 1730 1730 IN IP4 198.18.114.148 s=PCD c=IN IP4 198.18.114.148 t=0 0 m=audio 29426 RTP/AVP 0 a=rtpmap:0 PCMU/8000 --e61e7a6a-16a2-46c0-adbb-a41ba86d32a2-- #################### When the first body is received, the xlog correctly ends with this. m=audio 29426 RTP/AVP 0 a=rtpmap:0 PCMU/8000 ] with length 130 When the second body is received, the xlog incorrectly ends with this, which has an extra newline in it. m=audio 29426 RTP/AVP 0 a=rtpmap:0 PCMU/8000 ] with length 132 According to RFC2046, "The CRLF preceding the boundary delimiter line is conceptually attached to the boundary", but it looks like kamailio has a bug that incorrectly processes this. James

2 2

Simultaneous INVITE responses from multiple branches
by Anton Yabchinskiy 04 Nov '24

04 Nov '24

Hello, In our system we've encountered the following situation. There's a Kamailio proxy and a few REGISTER'ed devices behind the proxy. When there's an INVITE to these multiple devices, two of them simultaneously answer the call. Kamailio proxy accepts the first 200 OK from one of the devices and tries to CANCEL all other branches. But the second 200 OK device have already responded OK and doesn't acknowledge the CANCEL. So, there's now one established dialog with media, and another "established" one neither having media nor being correctly terminated. Looks like the similar scenario is described in section 3.1.2 of RFC 5407 (Example Call Flows of Race Conditions in the Session Initiation Protocol (SIP)). Is it possible to mitigate such scenarios in a Kamailio proxy? E.g., is it possible to send an additional BYE to these CANCEL'led branches? In current configuration, Kamailio proxy retrieves contacts with registrar:lookup() and does parallel forking with tm:t_relay().

2 2

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