sr-users June 2025

sr-users@lists.kamailio.org

10 participants
6 discussions

adding codecs to rtpengine
by Jeff Brower 03 Jun '25

03 Jun '25

Hi all, Is there a documented procedure for adding codecs to rtpengine ? As I understand it so far, we would adapt rtpengine encoder and decoder interfaces to the voplib API (documented at https://github.com/signalogic/SigSRF_SDK/blob/master/codecs_readme.md), allowing use of voplib shared object libs. I've been searching (e.g. adding codecs to rtpengine site:kamailio.org) but have not found a step-by-step procedure yet. Thanks for any advice / guidance. -Jeff

3 2

event_route[xhttp:request] is not executed
by Володимир Іванець 03 Jun '25

03 Jun '25

Hello! I'm doing some testing with http requests but got stuck at the beginning. event_route[xhttp:request] does not seem to be executed. I'm getting the following in the log with the most basic configuration. Am I missing something? Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 13(9161) DEBUG: <core> [core/ip_addr.c:577]: print_ip(): tcpconn_new: new tcp connection: 127.0.0.1 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 13(9161) DEBUG: <core> [core/tcp_main.c:1238]: tcpconn_new(): on port 46328, type 2, socket 23 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 13(9161) DEBUG: <core> [core/tcp_main.c:1630]: tcpconn_add(): hashes: 1391:1425:2615, 2 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 13(9161) DEBUG: <core> [core/io_wait.h:367]: io_watch_add(): processing io_watch_add(0xb22d80, 23, 2, 0x7f7a63877f30) - fd_no=17 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 13(9161) DEBUG: <core> [core/io_wait.h:598]: io_watch_del(): DBG: io_watch_del (0xb22d80, 23, -1, 0x0) fd_no=18 called Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 13(9161) DEBUG: <core> [core/tcp_main.c:4671]: handle_tcpconn_ev(): sending to child, events 1 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 13(9161) DEBUG: <core> [core/tcp_main.c:4335]: send2child(): selected tcp worker idx:1 proc:10 pid:9158 for activity on [tcp:127.0.0.1:8089], 0x7f7a63877f30 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 10(9158) DEBUG: <core> [core/tcp_read.c:1782]: handle_io(): received n=8 con=0x7f7a63877f30, fd=6 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 10(9158) DEBUG: <core> [core/tcp_read.c:627]: tcp_read_headers(): no clen, p=A Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 10(9158) ERROR: <core> [core/tcp_read.c:1555]: tcp_read_req(): bad request, state=7, error=4 buf: Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: GET /TEST HTTP/1.1 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: Host: 127.0.0.1:8089 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: User-Agent: curl/7.43.0 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: Accept: */* Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: parsed: Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: GET /TEST HTTP/1.1 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: Host: 127.0.0.1:8089 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: User-Agent: curl/7.43.0 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: Accept: */* Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 10(9158) DEBUG: <core> [core/tcp_read.c:1562]: tcp_read_req(): received from: port 46328 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 10(9158) DEBUG: <core> [core/ip_addr.c:577]: print_ip(): received from: ip127.0.0.1 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 10(9158) DEBUG: <core> [core/tcp_read.c:1704]: release_tcpconn(): releasing con 0x7f7a63877f30, state -2, fd=6, id=2 ([127.0.0.1]:46328 -> [127.0.0.1]:8089) Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 10(9158) DEBUG: <core> [core/tcp_read.c:1705]: release_tcpconn(): extra_data (nil) Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 13(9161) DEBUG: <core> [core/tcp_main.c:3745]: handle_tcp_child(): reader response= 7f7a63877f30, -2 from 1 Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 13(9161) DEBUG: <core> [core/tcp_main.c:3668]: tcp_emit_closed_event(): TCP closed event creation triggered (reason: 0) Jun 3 20:50:35 kamailio-dev-2 kamailio[9148]: 13(9161) DEBUG: <core> [core/tcp_main.c:3676]: tcp_emit_closed_event(): no callback registering for handling TCP closed event #!KAMAILIO children = 4 tcp_children = 4 debug=3 log_stderror=yes memdbg=5 memlog=5 fork=yes #!substdef "!LOCAL_UDP!udp:127.0.0.1:5060!g" #!substdef "!LOCAL_HTTP!tcp:127.0.0.1:8089!g" listen=LOCAL_UDP listen=LOCAL_HTTP loadmodule "xlog.so" loadmodule "pv.so" loadmodule "ctl.so" loadmodule "sl.so" loadmodule "xhttp.so" event_route[xhttp:request] { xhttp_reply("200", "OK", "text/html", "<html><body>OK - [$si:$sp]</body></html>"); } Thank you very much!

2 1

Kamailio Dispatcher for Docker Asterisk
by Fernando Lopes 03 Jun '25

03 Jun '25

Hello everyone, I have Kamailio running on port 5060, and I'm running Asterisk inside a Docker container. I'm trying to connect to Asterisk via port 5061. Could someone please advise what I should add to my dispatcher list? Currently, I have the dispatcher.list entry: 1 sip:10.0.0.5:5061;transport=tcp 0 Here’s the network info for my Kamailio host (eth0 interface): inet 10.0.0.4/24 brd 10.0.0.255 scope global eth0 And here are the relevant port mappings from Docker: 5038/tcp -> 0.0.0.0:5038 5060/tcp -> 0.0.0.0:5061 5060/udp -> 0.0.0.0:5061 ... My main question: Is the dispatcher entry sip:10.0.0.5:5061;transport=tcp correct if Asterisk is listening on port 5061 in the container? Do I need to adjust anything on the Kamailio side or change the dispatcher entry format? Thanks in advance for any help!

3 5

Small Question
by Fernando Lopes 03 Jun '25

03 Jun '25

Hello Everyone, I have a cloud vm with public ip: 135.2xx.1xx.1xx:5060 and locally 10.0.0.4 When I receive a SIP message the invite looks like this, it gets stuck here. SIP Invite: 2025/06/03 16:24:58.249284 192.76.120.10:5060 -> 10.0.0.4:5060 INVITE sip:+35122xxxxxxxx@135.2xx.1xx.1xx:5060 SIP/2.0 Record-Route: <sip:192.76.120.10;r2=on;lr;ftag=765jrrKarBe3F> Record-Route: <sip:10.255.0.1;r2=on;lr;ftag=765jrrKarBe3F> Via: SIP/2.0/UDP 192.76.120.10;branch=z9hG4bKbb37.28332dbc5901e729308403cd5e049713.0 v:SIP/2.0/UDP 10.239.44.224:6000;received=10.239.44.224;rport=6000;branch=z9hG4bKD4UtjN52Qrm9D Max-Forwards:55 f:"+3519xx78xx1x"<sip:+3519xx78xx1x@sip.telnyx.com>;tag=765jrrKarBe3F t:<sip:+35122xxxxxxxx@135.2xx.1xx.1xx:5060> i:c64314db-75b9-4029-8147-be3f3d77da2a CSeq:99930157 INVITE m:<sip:mod_sofia@10.239.44.224:6000> Allow:INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,INFO,UPDATE,REFER,NOTIFY k:timer,path u:talk,hold,conference,refer Privacy:none c:application/sdp Content-Disposition:session l:205 P-Asserted-Identity:"+3519xx78xx1x"<sip:+3519xx78xx1x@sip.telnyx.eu;verstat=No-TN-Validation> v=0 o=Telnyx 1748940128 1748940129 IN IP4 50.114.150.25 s=Telnyx c=IN IP4 50.114.150.25 t=0 0 m=audio 27770 RTP/AVP 9 a=rtpmap:9 G722/8000 a=sendrecv a=rtcp:27771 IN IP4 50.114.150.25 a=ptime:20 Kamailio Code: #!define DS_LIST "/etc/kamailio/dispatcher.list" #!define LISTEN_UDP_PUBLIC udp:135.2xx.1xx.1xx:5060 #!define LISTEN_UDP_PRIVATE udp:10.0.0.4:5060 #!define LISTEN_TCP_PUBLIC tcp:135.2xx.1xx.1xx:5060 #!define LISTEN_TCP_PRIVATE tcp:10.0.0.4:5060 #!define EXTERNAL_IP "10.0.0.4" #!define KUBERNETES_NETWORK "172.19." #!define FLAG_TELNYX_CALL 12 #set module path mpath = "/usr/lib/x86_64-linux-gnu/kamailio/modules" ####### Global Parameters ######### #mhomed=1 # doesn't work with virtual IPs #!ifdef WITH_DEBUG debug=4 #!else debug=2 #!endif log_stderror=no memdbg=5 memlog=5 #log_facility=LOG_LOCAL6 log_facility=LOG_LOCAL0 fork=yes children=4 auto_aliases=no #listen=LISTEN_UDP_PUBLIC listen=LISTEN_UDP_PRIVATE listen=LISTEN_TCP_PRIVATE ####### FLAGS ###### #!define FLAG_FROM_ASTERISK 10 #!define FLAG_FROM_PEER 11 sip_warning=no

1 0

Kamailio as Proxy only
by disa_369＠msn.com 03 Jun '25

03 Jun '25

Hello to everyone. I deployed Kamailio on Debian system. Install was successfull. I have not much experience Kamailio and i dont know what need to run Kamailio as Proxy. I have the task to use Kamailio as proxy between Avaya PBX and Videoconference System. Outgoing calls only from Avaya PBX -------> Kamailio ----> Video System. We dont need Kamailio subscribers\peers, Just to forward a call from avaya to Video system by ip. Video system has IVR number 3000, all we need to dial number 3000@ip_of_video_system. I got questions. 1. Do we need install maria_db for that? 2. Do we need create subscriber\peer on Kamailio? 3. Do we need add modules for that? And main question what to add in kamailio.cfg is? Thx!!!!!!!!!

2 2

Disable IPSec in Kamailio PCSCF
by Navjyoty Singh 02 Jun '25

02 Jun '25

Hi, I'm working on a custom IMS deployment using the pcscf module in Kamailio. For our setup, we do not want Kamailio to handle IPsec or generate Security-Server headers in 401/407 responses. Is there a clean way to disable IPsec functionality entirely in the pcscf module? Specifically, I would like to: Prevent the module from requiring IPsec setup during UE registration Avoid any modification of SIP messages related to IPsec (e.g., removing Security-Verify, Security-Client, or Security-Server headers) Use only TLS or UDP without IPsec involvement Has anyone achieved this via configuration or by disabling specific features? Any guidance or examples would be greatly appreciated. *Regards,Navjyoty*

1 0

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 June 2025