sr-users

sr-users@lists.kamailio.org

9 participants
37525 discussions

Running Kamailio 6.0.x with rtpengine 10.5.x.x
by Sebastian Damm 03 Jul '25

03 Jul '25

Hi, I'm in the process of updating Kamailio from 5.8.x to 6.0.x, and in my last tests I noticed these error messages in rtpengine log: WARNING: [3B4A4512-7DA7-439F-97B7-78021488407B]: [core] Unknown dictionary key encountered: 'sip-message-type' We run rtpengine still with version 10.5.x.x (currently 10.5.6.3), and the update of rtpengine is a bit blocked (mainly because of the removal of iptables support requiring more changes for nftables in the background). I tracked down the changes both in rtpengine and kamailio repository, and with rtpengine 12.x it probably would work, but I'm not there yet. In this combination, does rtpengine still do what it should do? I did not notice any problems, but before our customers do, I thought I'd rather ask. Thanks for any advice, Sebastian

1 0

[Help] Websocket synchronization between two nodes
by xiongyiyang＠shuidi-inc.com 03 Jul '25

03 Jul '25

When I use dmq synchronization, I find that websocket cannot synchronize between two nodes. What should I do?

1 0

kamailio module development setup
by mohsen khashei 03 Jul '25

03 Jul '25

Hi everyone. I want to start development of an kamailio module. and I am wondering is the any tutorial about that and also what ide or other setup the other people use for this. sorry for begginer question and thanks for attention.

2 1

[microhttpd] POST request with body can't get return message
by mm e 02 Jul '25

02 Jul '25

version: kamailio 6.1.0-dev1 (x86_64/linux) 75b73d loadmodule "microhttpd.so" modparam("microhttpd", "listen_addr", "0.0.0.0") modparam("microhttpd", "listen_port", 8364) event_route[microhttpd:request] { mhttpd_reply("200", "OK", "",""); } When using "curl -X POST http://127.0.0.1:8364", a response can be obtained. When using "curl -d '{"test":"2", "test2":"1"}' -H "Content-Type: application/json" -X POST http://127.0.0.1:8364" to pass json data, the kamailio process will be blocked.

2 5

KamailioProxy: Should kamailio do handshake or asterisk?
by Fernando Lopes 01 Jul '25

01 Jul '25

Hello everyone, I have Kamailio set up as a proxy between external clients and an Asterisk server. When traffic comes in over WSS, should Kamailio handle the TLS handshake, or should it be passed through to Asterisk? Thank you.

4 3

I encountered a problem when using dmq and dmq_usrloc. When I used the save function to save to the location table in the database, the socket field was sometimes empty, which caused problems with my call.
by xiongyiyang＠shuidi-inc.com 01 Jul '25

01 Jul '25

My dmq configuration： loadmodule "dmq_usrloc.so" modparam("dmq_usrloc", "enable", 1) modparam("dmq_usrloc", "sync", 1) modparam("dmq_usrloc", "usrloc_domain", "location_shuidi_online_agent") modparam("dmq_usrloc", "batch_size", 1000) modparam("dialog", "enable_dmq", 1) loadmodule "dmq.so" # ----- dmq params ----- modparam("dmq", "server_address", DMQ_SIP_URL) modparam("dmq", "server_socket", DMQ_UDP_URL) #!ifexp POD_NAME == "kamailio-cti-xyy-0" modparam("dmq", "notification_address", "sip:kamailio-cti-xyy-1.kamailio-cti-xyy-headless.devops.svc.bedin.bj3:5062") #!endif #!ifexp POD_NAME == "kamailio-cti-xyy-1" modparam("dmq", "notification_address", "sip:kamailio-cti-xyy-0.kamailio-cti-xyy-headless.devops.svc.bedin.bj3:5062") #!endif modparam("dmq", "multi_notify", 1) modparam("dmq", "num_workers", 4) modparam("dmq", "ping_interval", 15) Report an error： NATMANAGE cline: c=IN IP4 10.21.24.151 1(11) WARNING: <core> [core/msg_translator.c:2904]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found 1(11) ERROR: <core> [core/msg_translator.c:2044]: build_req_buf_from_sip_req(): could not create Via header 1(11) ERROR: tm [t_fwd.c:482]: prepare_new_uac(): could not build request 1(11) ERROR: tm [t_fwd.c:1759]: t_forward_nonack(): failure to add branches 1(11) ERROR: sl [sl_funcs.c:415]: sl_reply_error(): stateless error reply used: Message processing error (2/SL) I think the reason is that the socket field in the location database is copied to another kamailio node and then updated to the database, causing it to be overwritten and empty. A part of location database table： user_agent socket methods SIP.js/0.21.2 5023 SIP.js/0.21.1 5023 SIP.js/0.21.2 5023 SIP.js/0.21.1 5023 SIP.js/0.21.2 5023 please help ！！！ I really don't know how to prevent the socket field from being overwritten.

1 0

SIP messages examples
by Sergey Safarov 27 Jun '25

27 Jun '25

We are fixing the FreeSwitch issue with Contact headers containing ";" character in the user param. https://github.com/signalwire/freeswitch/issues/2824 Now required to test other use cases where the user part contains "&" / "$" / "," / "?" / "/" Could you provide some examples of SIP messages with these characters in the user part? Sergey

1 0

nghttp2
by mm e 27 Jun '25

27 Jun '25

loadmodule "nghttp2.so" modparam("nghttp2", "listen_addr", "0.0.0.0") modparam("nghttp2", "listen_port", "8363") event_route[nghttp2:request] { xinfo("request: $nghttp2(method) - url: $nghttp2(path) - data: [$nghttp2(data)]\n"); nghttp2_reply("200","OK"); } curl -H "Content-Type: application/json" -X POST -d '{"test":"data"}' "http://127.0.0.1:8363" curl: (56) Recv failure: Connection reset by peer When using curl request, the message "Recv failure" appears. What is wrong with the settings?

2 1

Dispatcher sets IP flag on servers even though SIP OPTIONS receive 200 OK
by Pablo Oliver 26 Jun '25

26 Jun '25

Hi there, I'm new to Kamailio, and maybe this is a silly question. I’ve set up Kamailio as a SIP proxy with two Asterisk servers acting as media services. This is my configuration for the dispatcher module: loadmodule "dispatcher.so" modparam("dispatcher", "db_url", DBURL) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "flags", 2) modparam("dispatcher", "ds_ping_interval", 20) modparam("dispatcher", "ds_ping_method", "OPTIONS") modparam("dispatcher", "ds_probing_threshold", 5) modparam("dispatcher", "ds_inactive_threshold", 5) modparam("dispatcher", "ds_ping_latency_stats", 1) modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_ping_reply_codes", "class=2;code=403;code=488;class=3") modparam("dispatcher", "ds_ping_from", SIPCALL) I can see the SIP OPTIONS requests going from Kamailio to Asterisk and receiving 200 OK responses. However, the dispatcher is still setting the IP (Inactive Probing) flag on the servers: kamcmd dispatcher.list { NRSETS: 1 RECORDS: { SET: { ID: 1 TARGETS: { DEST: { URI: sip:172.16.254.21:5060 FLAGS: IP PRIORITY: 0 LATENCY: { AVG: 0 STD: 0 EST: 0 MAX: 0 TIMEOUT: 183 } } DEST: { URI: sip:172.16.254.20:5060 FLAGS: IP PRIORITY: 0 LATENCY: { AVG: 0 STD: 0 EST: 0 MAX: 0 TIMEOUT: 183 } } } } } } So when I try to use ds_select_dst("1", "4"), it always fails. Did I miss something in my configuration? Thanks! Regards, Pablo.

3 6

Context of t_continue
by johannes.westhuis＠auerswald.de 25 Jun '25

25 Jun '25

Hi, we are using kamailio 5.8 with t_suspend to suspend calls until a push notification wakes up the phone. The phone will then send an NOTIFY with information, so that t_continue can be called. This works well, but currently we are facing issues with rtpengine, and looking at the logs, there is something suspicious: we are calling: t_continue("$sht(vtp=>id_index::$hdr(X-Resume))", "$sht(vtp=>id_label::$hdr(X-Resume))", "RESUME"); ... route[RESUME] { xdbgl("[RESUME] rm=$rm ru=$ru du=$du \n"); ... after the call to t_continue i can see the log mentioned above: Jun 24 16:20:52 proxy5 /usr/sbin/kamailio[2337]: DEBUG: {1 34558 NOTIFY sFsXwoWeDXHOzRHqVfA4E5KDT9U6qoov} <script>: 486:[RESUME] rm=INVITE ru=sip:<URI_REDACTED> I wondered why the log call still logs the context as the NOTIFY context and not the INVITE context, and if that might lead to issues? currently we get problems with rtpengine_manage when we try to call it in the route[RESUME] Jun 24 16:20:52 proxy5 /usr/sbin/kamailio[2337]: DEBUG: {1 34558 NOTIFY sFsXwoWeDXHOzRHqVfA4E5KDT9U6qoov} rtpengine [rtpengine.c:3198]: rtpp_function_call(): proxy reply: d7:warning38:Call-ID not found or tags didn't match6:result2:oke We are currently checking, if we can work around this issue, but i am hoping to getting a bit of insight from you. Best Regards JWes

4 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