sr-users August 2025

sr-users@lists.kamailio.org

38 participants
31 discussions

Kamailio - SIPDUMP doesn't capture the IP header information (ECN)
by ilyass.ghijjou＠gmail.com 11 Aug '25

11 Aug '25

I am using Kamailio as a proxy between a public and private network (tls and udp), i was wondering if there is a way to capture SIP messages along with their IP header metadata using SIPDUMP in Kamailio. For example, I would like to see the real DSCP value, which is set to zero by default (by SIPDUMP i guess). When i run a tcpdump i can see that the dscp is set to 0xb8 but in in the sipdump capture is set to 0x00

4 4

secfilter secf_check_country($gip2(src=>cc)) always replies null
by Samuel Moya Tinoco 11 Aug '25

11 Aug '25

Good morning everyone, Im trying to configure secfilter module to harden our kamailio. After configuring geoip2 module and checking that using function geoip2_match("$si", "src") it shows the country properly. I've configured secfilter module, and I think it's also working because kamailio service starts and with kamcmd secfilter.print I can see the entries from the DDBB. But when I call the function secf_check_country($gip2(src=>cc)) it always replies with <null> (I saw it in this variable $avp(secfilter)). I've also tried to use $? Variable and it shows "1", in the module documentation I saw that 1 means "the value is not found". But when I use kamcmd secfilter.print I can see the country in the output and it's spelled exactly the same that in $gip2(src=>cc) I don't know if there's something I'm missing. Any help would be appreciated. Thanks in advance This is the code I'm executing if (geoip2_match("$si", "src")) { secf_check_country($gip2(src=>cc)); xlog("L_ALERT", "La respuesta de de secfilter es $avp(secfilter)"); xlog("L_ALERT", "$?"); if ($avp(secfilter) == 2) { return; } xlog("L_ALERT", "$rm from $si blocked because Country '$gip2(src=>cc)' is blacklisted"); exit; } And this is what appears in the logs 2025-08-07T09:42:54.876178+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1} *** cfgtrace:dbg_cfg_trace(): request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1061 a=16 n=if 2025-08-07T09:42:54.876219+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1} *** cfgtrace:dbg_cfg_trace(): request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1049 a=26 n=geoip2_match 2025-08-07T09:42:54.876252+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1} *** cfgtrace:dbg_cfg_trace(): request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1051 a=32 n=secf_check_country 2025-08-07T09:42:54.876291+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1} *** cfgtrace:dbg_cfg_trace(): request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1052 a=26 n=xlog 2025-08-07T09:42:54.876473+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: ALERT: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1} <script>: La respuesta de de secfilter es <null> 2025-08-07T09:42:54.876513+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1} *** cfgtrace:dbg_cfg_trace(): request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1053 a=26 n=xlog 2025-08-07T09:42:54.876556+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: ALERT: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1} <script>: 1 2025-08-07T09:42:54.876587+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1} *** cfgtrace:dbg_cfg_trace(): request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1058 a=16 n=if 2025-08-07T09:42:54.876619+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1} *** cfgtrace:dbg_cfg_trace(): request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1058 a=26 n=xlog 2025-08-07T09:42:54.876651+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: ALERT: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1} <script>: OPTIONS from 91.228.91.69 blocked because Country 'ES' is blacklisted 2025-08-07T09:42:54.876682+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1} *** cfgtrace:dbg_cfg_trace(): request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1059 a=2 n=exit The output of kamcmd secfilter.print country root@PRE-KAMAILIO:/etc/kamailio# kamcmd secfilter.print country Country ======= [+] Blacklisted ----------- [+] Whitelisted ----------- 0001 -> ES Samuel Moya Tinoco Departamento de Sistemas y Redes Móvil: (+34) 606985997 smoya(a)vivelibre.es<mailto:smoya@vivelibre.es> ViveLibre C/ La Orotava 4 28660 Boadilla del Monte Madrid www.vivelibre.es<http://www.vivelibre.es/> [cid:image001.png@01DC0780.5D6264D0] Soluciones inteligentes para la autonomía personal "Tanto este mensaje como todos los posibles documentos adjuntos al mismo son confidenciales y están dirigidos exclusivamente a los destinatarios de los mismos. Por favor, si Usted no es uno de dichos destinatarios, notifíquenos este hecho y elimine el mensaje de su sistema. Queda prohibida la copia, difusión o revelación de su contenido a terceros sin el previo consentimiento por escrito de VIVELIBRE AUTONOMÍA PERSONAL S.L.U. (VIVELIBRE). En caso contrario, vulnerará la legislación vigente. De conformidad con lo establecido en el Reglamento (UE) 2016/679, General de Protección de Datos, le informamos de que sus datos son objeto de tratamiento por VIVELIBRE, en calidad de Responsable del Tratamiento. VIVELIBRE tratará sus datos con la finalidad de mantener la relación contractual, gestionar su solicitud, así como remitirle comunicaciones de carácter comercial relacionadas con su ámbito de actividad y los servicios prestados. Si desea ejercitar sus derechos de acceso, rectificación, supresión, limitación, oposición o portabilidad, puede dirigirse a la dirección postal Calle de la Orotava 4, 28660, Boadilla del Monte, (Madrid) o a la dirección de correo electrónico protecciondedatos(a)vivelibre.es. Para obtener más información sobre cómo tratamos sus datos, consulta nuestra Política de Privacidad en Política de Privacidad - Vivelibre."

4 11

kamailio.org is down?
by Jurijs Ivolga 11 Aug '25

11 Aug '25

Hi, Is it me or kamailio.org is down? Jurijs

5 4

Re: problems using kamailio
by Peter walber 08 Aug '25

08 Aug '25

Hello, good idea. i will try to set it up outside of docker. using the config Files from the docker Container from Florian h05. I will install the latest releases of kamailio and rtpengine from the command live apt-get install. thanks for Support regards peter Gesendet mit der Telekom Mail App --- Original-Nachricht --- Von: Richard Robson via sr-users Betreff: [SR-Users] Re: problems using kamailio Datum: 08. August 2025, 16:54 An: sr-users(a)lists.kamailio.org Cc: Richard Robson the Github link you originally posted with does have a basic websockets, tls and stp engine script in it https://github.com/florian-h05/webrtc-sip-gw/blob/main/config/kamailio/kama… maybe try without Docker and get things running in an environment that you can change easily. you can then get access to all the ports and traffic you need without extra docker configuration. I use a docker environment for testing, which uses sipp to emulate traffic and it spits out a set of logs and pcaps in needed, but again that a set of proffestional level tools, I use just to confirm the scripts sun as expected. each test needs to be configured and reads the lastest script I provide. also I need to setup myslq in the docker to provide the requied configs for the modules being used, dialplan, drouting, dispatcher, etc. try running kamailio on 1 vm and rtpengine on another, then setup the network for the VMs. have your endpoints connect o the VMs LAN. check the traffic is working before hand, via Pings and telnet. once your platform is stable, then try and get the different elements working. tls can be a pain to get working initally, make sure you have valid certs etc. then get RTPengine working and then the websockets. I'm afraid Its going to be difficult to aid you further without doing it all for you. Like Henning said, Its a steep learning curve and can be pretty daunting. Think of Kamailio as a framework not an end solution. You need to build the end solution from the framework provided. Again think of the github repo as a starting point for your solution. Once you get the desired outcome from your testing, you could probably dockerize that with the egress and ingress ports open to your local LAN. Hope you get your solution working. Richard On 08/08/2025 08:49, Peter Walber via sr-users wrote: Hi, I can imagine that the problems come from the configuration within the docker container. IP address and ports are somehow automatically defined and I'm not sure if these paramerts are correct. And I can not enter the routing scripts for HOMER intergration in the docker container. Therefore , I want to install and run kamailio with rtpengine directly outside a docker container on my debian vm. But I'm pretty much confused by the default kamailio configuration file with all the parameters, directives and loadmodules. Can somebody send me a basic configuration file for kamailio with websockets, TLS Support and rtpengine. Thanks and regards Peter Am 07.08.25 um 19:24 schrieb Richard Robson via sr-users: Hi, You could run up a Homer server and send the traffic to there from Kamailio with the sipcapture module. It should give you the ingress and egress packets unencrypted from the script. Hope that helps Richard On 07/08/2025 17:35, peter walber via sr-users wrote: Hello, I can use wireshark to capture and filter packets now. But the payload ist encrypted and I don't know how to decrypt the app-data. I can observe a lot of packets which are trevelling from the SIP Client to the webrtc-sip-gw. But can not decrypt the payload. I have opened the network console of google chrom. I can see that the client starts the SIP request using JsSIP **72 is my doorbird **73 is my openhab SIP Client --------------------------------------------------------- INVITE sip:**72@speedport.ip SIP/2.0 Via: SIP/2.0/WSS r64og133ol2n.invalid;branch=z9hG4bK2639027 Max-Forwards: 69 To: <sip:**72@speedport.ip> From: <sip:**73@speedport.ip>;tag=0l5gn2o04p Call-ID: k57isvj3jnib42sone96 CSeq: 6684 INVITE Contact: <sip:gpmhi027@r64og133ol2n.invalid;transport=ws;ob> Content-Type: application/sdp Allow: INVITE,ACK,CANCEL,BYE,UPDATE,MESSAGE,OPTIONS,REFER,INFO,NOTIFY Supported: ice,replaces,outbound User-Agent: JsSIP 3.10.1 Content-Length: 1705 v=0 o=- 8248900579316048806 2 IN IP4 127.0.0.1 s=- t=0 0 a=group:BUNDLE 0 a=extmap-allow-mixed a=msid-semantic: WMS c8e94492-8d01-4aa1-9023-497510a9054b m=audio 43416 UDP/TLS/RTP/SAVPF 111 63 9 0 8 13 110 126 c=IN IP4 192.168.2.151 a=rtcp:9 IN IP4 0.0.0.0 a=candidate:1715666646 1 udp 2122260223 192.168.2.151 43416 typ host generation 0 network-id 1 a=candidate:2923572520 1 udp 2122194687 172.17.0.1 34664 typ host generation 0 network-id 2 a=candidate:2565352002 1 tcp 1518280447 192.168.2.151 9 typ host tcptype active generation 0 network-id 1 a=candidate:1357445564 1 tcp 1518214911 172.17.0.1 9 typ host tcptype active generation 0 network-id 2 a=ice-ufrag:vZWG a=ice-pwd:NWYzQwxQ4nP4FdcL6XpCl66/ a=ice-options:trickle a=fingerprint:sha-256 80:22:F4:1E:B4:94:EF:F8:44:FA:E9:CA:72:DA:75:F3:99:1F:10:8D:B4:11:B3:65:3D:F9:44:67:28:31:CB:E5 a=setup:actpass a=mid:0 a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level a=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time a=extmap:3 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01 a=extmap:4 urn:ietf:params:rtp-hdrext:sdes:mid a=sendrecv a=msid:c8e94492-8d01-4aa1-9023-497510a9054b 8cd550e3-9b06-4e06-af55-f31b5392bafd a=rtcp-mux a=rtcp-rsize a=rtpmap:111 opus/48000/2 a=rtcp-fb:111 transport-cc a=fmtp:111 minptime=10;useinbandfec=1 a=rtpmap:63 red/48000/2 a=fmtp:63 111/111 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:13 CN/8000 a=rtpmap:110 telephone-event/48000 a=rtpmap:126 telephone-event/8000 a=ssrc:1295466586 cname:7i+lr9FQ7qgsLxhh a=ssrc:1295466586 msid:c8e94492-8d01-4aa1-9023-497510a9054b 8cd550e3-9b06-4e06-af55-f31b5392bafd --------------------------------------------- But I also see the obviously kamilio responding with timeout ------------------------------------------------------------------------------------------ SIP/2.0 408 Request Timeout Via: SIP/2.0/WSS r64og133ol2n.invalid;branch=z9hG4bK2315704;rport=58076;received=192.168.2.151 To: <sip:**73@speedport.ip>;tag=5532e97d005227a861814c798ae9fc63-c1c00000 From: <sip:**73@speedport.ip>;tag=kfjl6vah0u Call-ID: p928jbnb7d2spbvdgoepjt CSeq: 1 REGISTER Server: kamailio (5.6.3 (x86_64/linux)) Content-Length: 0 -------------------------------------------------------------------- does it help to analyse ? Regards Peter Am 07.08.25 um 14:07 schrieb Henning Westerholt via sr-users: @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face {font-family:Aptos;}p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:12.0pt; font-family:"Aptos",sans-serif;}a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;}span.EmailStyle19 {mso-style-type:personal-reply; font-family:"Aptos",sans-serif; color:windowtext;}.MsoChpDefault {mso-style-type:export-only; font-size:10.0pt; mso-ligatures:none;}div.WordSection1 {page:WordSection1;} Hello, have a look e.g. with tcpdump and wireshark what exactly happens. Maybe the connection is closed from one party. Sometimes TCP keep-alive or SIP REGISTER time intervals needs to be adapted to keep a connection open, e.g. in NAT scenarios. Cheers, Henning From: Peter Walber via sr-users <sr-users(a)lists.kamailio.org> Sent: Donnerstag, 7. August 2025 09:56 To: sr-users(a)lists.kamailio.org Cc: Peter Walber <peter.walber(a)t-online.de> Subject: [SR-Users] problems using kamailio Hello, I try to use kamailio as webrtc-sip-gateway between my openhab smart home system and my doorbird doorbell with phone and camera. I try to use the product of "https://github.com/florian-h05/webrtc-sip-gw". Which integrates kamailio together with rtpengine to the gateway. I want to use openhab as SIP Client and have a Telekom Speedport Smart 4 Router on the other side. The webrtc-sip-gw from florian-h05 shall be the software between Openhab and the speedport smart 4. On the speedport smart router the SIP Server is enabled and configured. I can sucessfully call with zoiper extern phone numbers. The doorbird als is configured correctly. I can call the doorbird with my zioper softphone using the SIP interface of the doorbird. The runtime system is a docker container on debian 12. I want to call the doorbird by SIP from my openhab SIP client. I can initiate the call, but it doesn't establish Here is the log from the docker container. --------------------------------------------------------------------------------------------------- 2025-08-07T07:46:57.384687165Z 9(52) INFO: <script>: HTTP Request Received 2025-08-07T07:46:57.391479050Z 9(52) INFO: <script>: START: REGISTER from sip:**73@speedport.ip (IP:192.168.2.185:39510) 2025-08-07T07:46:57.391516534Z 9(52) INFO: <script>: Current Contact header: <sip:v0fds0hl@fe8ojuo7pnkl.invalid;transport=ws>;+sip.ice;reg-id=1;+sip.instance="<urn:uuid:243e461d-f0cb-4c09-9a63-f57c9bba8d6b>";expires=600 2025-08-07T07:46:57.391526535Z 9(52) INFO: <script>: Setting new Contact header: <sip:**73@192.168.2.209:5060> 2025-08-07T07:47:00.195739350Z 9(52) INFO: <script>: START: INVITE from sip:**73@speedport.ip (IP:192.168.2.185:39510) 2025-08-07T07:47:00.195800424Z 9(52) INFO: <script>: Current Contact header: <sip:v0fds0hl@fe8ojuo7pnkl.invalid;transport=ws;ob> 2025-08-07T07:47:00.195811886Z 9(52) INFO: <script>: Setting new Contact header: <sip:v0fds0hl@fe8ojuo7pnkl.invalid;transport=ws;ob;alias=192.168.2.185~39510~6;alias=192.168.2.185~39510~6> 2025-08-07T07:47:00.196163528Z 9(52) INFO: <script>: MANAGE_BRANCH: New branch [0] to sip:**72@speedport.ip 2025-08-07T07:47:00.196181228Z 9(52) INFO: <script>: NATMANAGE branch_id:0 ruri: sip:**72@speedport.ip, method:INVITE, status:<null>, extra_id: z9hG4bK44082210, rtpengine_manage: replace-origin replace-session-connection via-branch=extra rtcp-mux-demux SDES-off ICE=remove RTP/AVP 2025-08-07T07:47:00.196608235Z INFO: [penvq8f06ehafutk9ivf]: [control] Received command 'offer' from 127.0.0.1:50790 2025-08-07T07:47:00.196625247Z NOTICE: [penvq8f06ehafutk9ivf]: [core] Creating new call 2025-08-07T07:47:00.198519843Z INFO: [penvq8f06ehafutk9ivf]: [control] Replying to 'offer' from 127.0.0.1:50790 (elapsed time 0.001979 sec) 2025-08-07T07:47:01.927528447Z 9(52) INFO: <script>: START: CANCEL from sip:**73@speedport.ip (IP:192.168.2.185:39510) 2025-08-07T07:47:01.927577111Z 9(52) INFO: <script>: Current Contact header: <null> 2025-08-07T07:47:01.927586439Z 9(52) INFO: <script>: Setting new Contact header: <null> 2025-08-07T07:47:09.169489716Z 7(50) INFO: <script>: WebSocket connection from 192.168.2.185:39510 has closed 2025-08-07T07:47:27.355185671Z 2(45) WARNING: tm [../../core/forward.h:203]: msg_send_buffer(): TCP/TLS connection for WebSocket could not be found 2025-08-07T07:47:27.914769340Z 9(52) INFO: <script>: HTTP Request Received 2025-08-07T07:47:27.951608347Z 9(52) INFO: <script>: START: REGISTER from sip:**73@speedport.ip (IP:192.168.2.185:44816) 2025-08-07T07:47:27.951663073Z 9(52) INFO: <script>: Current Contact header: <sip:lebth4eq@fe8ojuo7pnkl.invalid;transport=ws>;+sip.ice;reg-id=1;+sip.instance="<urn:uuid:39eac0ca-0aea-4526-a5c7-0516bc8a2d71>";expires=600 2025-08-07T07:47:27.951915520Z 9(52) INFO: <script>: Setting new Contact header: <sip:**73@192.168.2.209:5060> 2025-08-07T07:47:30.168546446Z 2(45) INFO: <script>: BRANCH FAILED: z9hG4bK4408221 + 0INFO: [penvq8f06ehafutk9ivf]: [control] Received command 'delete' from 127.0.0.1:36296 2025-08-07T07:47:30.168587880Z INFO: [penvq8f06ehafutk9ivf]: [core] Deleting call branch '' (via-branch 'z9hG4bK44082210') 2025-08-07T07:47:30.168597011Z INFO: [penvq8f06ehafutk9ivf]: [core] Call branch '' (via-branch 'z9hG4bK44082210') deleted, no more branches remaining 2025-08-07T07:47:30.168605215Z INFO: [penvq8f06ehafutk9ivf]: [core] Deleting entire call 2025-08-07T07:47:30.168612883Z INFO: [penvq8f06ehafutk9ivf]: [core] Final packet stats: 2025-08-07T07:47:30.168620604Z INFO: [penvq8f06ehafutk9ivf]: [core] --- Tag 'utenlull77', created 0:30 ago for branch '' 2025-08-07T07:47:30.168628359Z INFO: [penvq8f06ehafutk9ivf]: [core] --- subscribed to '' 2025-08-07T07:47:30.168636445Z INFO: [penvq8f06ehafutk9ivf]: [core] --- subscription for '' 2025-08-07T07:47:30.168645446Z INFO: [penvq8f06ehafutk9ivf]: [core] ------ Media #1 (audio over UDP/TLS/RTP/SAVPF) using unknown codec 2025-08-07T07:47:30.168653691Z INFO: [penvq8f06ehafutk9ivf]: [core] --------- Port 192.168.2.209:23484 <> 192.168.2.185:60650, SSRC 0, 0 p, 0 b, 0 e, 30 ts 2025-08-07T07:47:30.168661939Z INFO: [penvq8f06ehafutk9ivf]: [core] --- Tag '', created 0:30 ago for branch 'z9hG4bK44082210' 2025-08-07T07:47:30.168669844Z INFO: [penvq8f06ehafutk9ivf]: [core] --- subscribed to 'utenlull77' 2025-08-07T07:47:30.168677713Z INFO: [penvq8f06ehafutk9ivf]: [core] --- subscription for 'utenlull77' 2025-08-07T07:47:30.168685661Z INFO: [penvq8f06ehafutk9ivf]: [core] ------ Media #1 (audio over RTP/AVP) using unknown codec 2025-08-07T07:47:30.168693705Z INFO: [penvq8f06ehafutk9ivf]: [core] --------- Port 192.168.2.209:23472 <> :0 , SSRC 0, 0 p, 0 b, 0 e, 30 ts 2025-08-07T07:47:30.168718608Z INFO: [penvq8f06ehafutk9ivf]: [core] --------- Port 192.168.2.209:23473 <> :0 (RTCP), SSRC 0, 0 p, 0 b, 0 e, 30 ts 2025-08-07T07:47:30.168728065Z INFO: [penvq8f06ehafutk9ivf]: [control] Replying to 'delete' from 127.0.0.1:36296 (elapsed time 0.000505 sec) 2025-08-07T07:47:30.169042099Z 2(45) INFO: <script>: Failure: <null> 2(45) WARNING: tm [../../core/forward.h:203]: msg_send_buffer(): TCP/TLS connection for WebSocket could not be found 2025-08-07T07:47:30.265075785Z 9(52) INFO: <script>: START: INVITE from sip:**73@speedport.ip (IP:192.168.2.185:44816) 2025-08-07T07:47:30.265125134Z 9(52) INFO: <script>: Current Contact header: <sip:lebth4eq@fe8ojuo7pnkl.invalid;transport=ws;ob> 2025-08-07T07:47:30.265135557Z 9(52) INFO: <script>: Setting new Contact header: <sip:lebth4eq@fe8ojuo7pnkl.invalid;transport=ws;ob;alias=192.168.2.185~44816~6;alias=192.168.2.185~44816~6> 2025-08-07T07:47:30.265484502Z 9(52) INFO: <script>: MANAGE_BRANCH: New branch [0] to sip:**72@speedport.ip 2025-08-07T07:47:30.265664116Z 9(52) INFO: <script>: NATMANAGE branch_id:0 ruri: sip:**72@speedport.ip, method:INVITE, status:<null>, extra_id: z9hG4bK16860370, rtpengine_manage: replace-origin replace-session-connection via-branch=extra rtcp-mux-demux SDES-off ICE=remove RTP/AVP 2025-08-07T07:47:30.265819591Z INFO: [412n0o8dedgair81t70p]: [control] Received command 'offer' from 127.0.0.1:50790 2025-08-07T07:47:30.265979425Z NOTICE: [412n0o8dedgair81t70p]: [core] Creating new call 2025-08-07T07:47:30.267497852Z INFO: [412n0o8dedgair81t70p]: [control] Replying to 'offer' from 127.0.0.1:50790 (elapsed time 0.001599 sec) 2025-08-07T07:47:30.469565385Z 9(52) INFO: <script>: START: CANCEL from sip:**73@speedport.ip (IP:192.168.2.185:44816) 2025-08-07T07:47:30.469629711Z 9(52) INFO: <script>: Current Contact header: <null> 2025-08-07T07:47:30.469645116Z 9(52) INFO: <script>: Setting new Contact header: <null> 2025-08-07T07:47:41.207672567Z 7(50) INFO: <script>: WebSocket connection from 192.168.2.185:44816 has closed 2025-08-07T07:47:57.917754216Z 2(45) WARNING: tm [../../core/forward.h:203]: msg_send_buffer(): TCP/TLS connection for WebSocket could not be found 2025-08-07T07:48:00.230412646Z 2(45) INFO: <script>: BRANCH FAILED: z9hG4bK1686037 + 0INFO: [412n0o8dedgair81t70p]: [control] Received command 'delete' from 127.0.0.1:36296 2025-08-07T07:48:00.230457143Z INFO: [412n0o8dedgair81t70p]: [core] Deleting call branch '' (via-branch 'z9hG4bK16860370') 2025-08-07T07:48:00.230466718Z INFO: [412n0o8dedgair81t70p]: [core] Call branch '' (via-branch 'z9hG4bK16860370') deleted, no more branches remaining 2025-08-07T07:48:00.230475640Z INFO: [412n0o8dedgair81t70p]: [core] Deleting entire call 2025-08-07T07:48:00.230483968Z INFO: [412n0o8dedgair81t70p]: [core] Final packet stats: 2025-08-07T07:48:00.230491909Z INFO: [412n0o8dedgair81t70p]: [core] --- Tag 'hc7h5imu96', created 0:30 ago for branch '' 2025-08-07T07:48:00.230518917Z INFO: [412n0o8dedgair81t70p]: [core] --- subscribed to '' 2025-08-07T07:48:00.230528302Z INFO: [412n0o8dedgair81t70p]: [core] --- subscription for '' 2025-08-07T07:48:00.230537387Z INFO: [412n0o8dedgair81t70p]: [core] ------ Media #1 (audio over UDP/TLS/RTP/SAVPF) using unknown codec 2025-08-07T07:48:00.230545867Z INFO: [412n0o8dedgair81t70p]: [core] --------- Port 192.168.2.209:23400 <> 192.168.2.185:46431, SSRC 0, 0 p, 0 b, 0 e, 30 ts 2025-08-07T07:48:00.230554949Z INFO: [412n0o8dedgair81t70p]: [core] --- Tag '', created 0:30 ago for branch 'z9hG4bK16860370' 2025-08-07T07:48:00.230563124Z INFO: [412n0o8dedgair81t70p]: [core] --- subscribed to 'hc7h5imu96' 2025-08-07T07:48:00.230570851Z INFO: [412n0o8dedgair81t70p]: [core] --- subscription for 'hc7h5imu96' 2025-08-07T07:48:00.230578827Z INFO: [412n0o8dedgair81t70p]: [core] ------ Media #1 (audio over RTP/AVP) using unknown codec 2025-08-07T07:48:00.230587091Z INFO: [412n0o8dedgair81t70p]: [core] --------- Port 192.168.2.209:23494 <> :0 , SSRC 0, 0 p, 0 b, 0 e, 30 ts 2025-08-07T07:48:00.230595631Z INFO: [412n0o8dedgair81t70p]: [core] --------- Port 192.168.2.209:23495 <> :0 (RTCP), SSRC 0, 0 p, 0 b, 0 e, 30 ts 2025-08-07T07:48:00.230603868Z INFO: [412n0o8dedgair81t70p]: [control] Replying to 'delete' from 127.0.0.1:36296 (elapsed time 0.000253 sec) 2025-08-07T07:48:00.230753116Z 2(45) INFO: <script>: Failure: <null> 2(45) WARNING: tm [../../core/forward.h:203]: msg_send_buffer(): TCP/TLS connection for WebSocket could not be found --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- especially the bold lines confuse me. Why is the TCP/TLS closed and can not be found ? Could that be the problem ? Thanks for some help and best regards Peter __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users(a)lists.kamailio.org To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users(a)lists.kamailio.org To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users(a)lists.kamailio.org To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users(a)lists.kamailio.org To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender!

1 0

Unsubscribe request form mailing list
by Pooja Yadav 08 Aug '25

08 Aug '25

Hi, As i am not working on kamailio currently. I need to unsubscribe from the mailing list. Please unsubscribe me from this list. Thanks, Pooja On Fri, 8 Aug 2025 at 15:15, <sr-users-request(a)lists.kamailio.org> wrote: > Send sr-users mailing list submissions to > sr-users(a)lists.kamailio.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > sr-users-request(a)lists.kamailio.org > > You can reach the person managing the list at > sr-users-owner(a)lists.kamailio.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sr-users digest..." > > Today's Topics: > > 1. Re: secfilter secf_check_country($gip2(src=>cc)) always replies null > (Samuel Moya Tinoco) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 8 Aug 2025 09:39:10 +0000 > From: Samuel Moya Tinoco <smoya(a)vivelibre.es> > Subject: [SR-Users] Re: secfilter secf_check_country($gip2(src=>cc)) > always replies null > To: Henning Westerholt <hw(a)gilawa.com>, "Kamailio (SER) - Users > Mailing List" <sr-users(a)lists.kamailio.org> > Message-ID: <GV1PR10MB5866E562B5E6C656E9F00B55D72FA(a)GV1PR10MB5866.EURP > RD10.PROD.OUTLOOK.COM> > Content-Type: multipart/related; boundary="_004_GV1PR10MB5866E5 > 62B5E6C656E9F00B55D72FAGV1PR10MB5866EURP_"; > type="multipart/alternative" > > Hello again Henning, > > Thank you for your reply. > I've try to use secf_check_country("$gip2(src=>cc)" but it's still the > same. We'll update to a newer version and try again > > Thank you again for your help > > Samuel Moya Tinoco > Departamento de Sistemas y Redes > Móvil: (+34) 606985997 > smoya(a)vivelibre.es<mailto:smoya@vivelibre.es> > > ViveLibre > C/ La Orotava 4 > 28660 Boadilla del Monte > Madrid > www.vivelibre.es<http://www.vivelibre.es/> > > [cid:image001.png@01DC0859.0D93E4E0] > > Soluciones inteligentes > para la autonomía personal > > > > De: Henning Westerholt <hw(a)gilawa.com> > Enviado el: viernes, 8 de agosto de 2025 9:30 > Para: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> > CC: Samuel Moya Tinoco <smoya(a)vivelibre.es> > Asunto: RE: secfilter secf_check_country($gip2(src=>cc)) always replies > null > > Hello, > > the documentation seems to have indeed some issues, the $avp(secfilter) > seems to be not available. It should be probably fixed in the docs. > > Regarding your issue, I can only say that we had a similar issue with > Kamailio 5.6.x on our customers, which apparently was solved with an update > to a newer version. One minor thing, the docs that the command need a > string value, so try secf_check_country("$gip2(src=>cc)"). > > Cheers, > > Henning > > From: Samuel Moya Tinoco <smoya(a)vivelibre.es<mailto:smoya@vivelibre.es>> > Sent: Freitag, 8. August 2025 08:57 > To: Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>>; Kamailio > (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto: > sr-users(a)lists.kamailio.org>> > Subject: RE: secfilter secf_check_country($gip2(src=>cc)) always replies > null > > Hello henning, > > Thank you for your reply. > I'm using kamailio 5.6.3, when I call $gip2(src=>cc) it shows the origin > country from the IP. I've test it with several countries and it works well. > The problem is when I call secf_check_country($gip2(src=>cc)) that it > replies with null. > > I've tried to insert into kamailio DDBB secfilter table exactly the output > of $gip2(src=>cc), and I can see that it appear when using "kamcmd > secfilter.print country" but it seems that the function cannot match it. > Also I've tried to insert into the secfilter table all the spelling > combinations of the country (both letter uppercase, both lowercase, one > uppercase one lowercase, between quotes, etc), and the command "kamcmd > secfilter.print country" shows all of them whitelisted but the function > still replies with a null > > I'm not sure if there's anything I'm doing wrong or what should I try next. > Thank you again for your help > > Samuel Moya Tinoco > Departamento de Sistemas y Redes > Móvil: (+34) 606985997 > smoya(a)vivelibre.es<mailto:smoya@vivelibre.es> > > ViveLibre > C/ La Orotava 4 > 28660 Boadilla del Monte > Madrid > www.vivelibre.es< > https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fwww.vivelibre.es%2f&c=E,… > > > > [cid:image001.png@01DC0859.0D93E4E0] > > Soluciones inteligentes > para la autonomía personal > > > > De: Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>> > Enviado el: jueves, 7 de agosto de 2025 13:22 > Para: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org > <mailto:sr-users@lists.kamailio.org>> > CC: Samuel Moya Tinoco <smoya(a)vivelibre.es<mailto:smoya@vivelibre.es>> > Asunto: RE: secfilter secf_check_country($gip2(src=>cc)) always replies > null > > Hello, > > some years ago, we had a similar issue with geoip with one of our > customers. It was not working anymore after a reload. But your problem > looks a bit more like it's in secfilter module. > > Which version of Kamailio you are using? Does it work when you call $gip2 > PV manually? > > Cheers, > > Henning > > From: Samuel Moya Tinoco via sr-users <sr-users(a)lists.kamailio.org<mailto: > sr-users(a)lists.kamailio.org>> > Sent: Donnerstag, 7. August 2025 10:08 > To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org > <mailto:sr-users@lists.kamailio.org>> > Cc: Samuel Moya Tinoco <smoya(a)vivelibre.es<mailto:smoya@vivelibre.es>> > Subject: [SR-Users] secfilter secf_check_country($gip2(src=>cc)) always > replies null > > Good morning everyone, > > Im trying to configure secfilter module to harden our kamailio. > After configuring geoip2 module and checking that using function > geoip2_match("$si", "src") it shows the country properly. I've configured > secfilter module, and I think it's also working because kamailio service > starts and with kamcmd secfilter.print I can see the entries from the DDBB. > But when I call the function secf_check_country($gip2(src=>cc)) it always > replies with <null> (I saw it in this variable $avp(secfilter)). I've also > tried to use $? Variable and it shows "1", in the module documentation I > saw that 1 means "the value is not found". But when I use kamcmd > secfilter.print I can see the country in the output and it's spelled > exactly the same that in $gip2(src=>cc) > > I don't know if there's something I'm missing. Any help would be > appreciated. > Thanks in advance > > This is the code I'm executing > if (geoip2_match("$si", "src")) { > secf_check_country($gip2(src=>cc)); > xlog("L_ALERT", "La respuesta de de secfilter es > $avp(secfilter)"); > xlog("L_ALERT", "$?"); > if ($avp(secfilter) == 2) { > return; > } > xlog("L_ALERT", "$rm from $si blocked because Country > '$gip2(src=>cc)' is blacklisted"); > exit; > } > And this is what appears in the logs > 2025-08-07T09:42:54.876178+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: > exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1<mailto: > fabe0744-1fca28e3-83050f4(a)127.0.0.1>} *** cfgtrace:dbg_cfg_trace(): > request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1061 a=16 n=if > 2025-08-07T09:42:54.876219+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: > exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1<mailto: > fabe0744-1fca28e3-83050f4(a)127.0.0.1>} *** cfgtrace:dbg_cfg_trace(): > request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1049 a=26 > n=geoip2_match > 2025-08-07T09:42:54.876252+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: > exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1<mailto: > fabe0744-1fca28e3-83050f4(a)127.0.0.1>} *** cfgtrace:dbg_cfg_trace(): > request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1051 a=32 > n=secf_check_country > 2025-08-07T09:42:54.876291+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: > exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1<mailto: > fabe0744-1fca28e3-83050f4(a)127.0.0.1>} *** cfgtrace:dbg_cfg_trace(): > request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1052 a=26 n=xlog > 2025-08-07T09:42:54.876473+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: > ALERT: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1<mailto: > fabe0744-1fca28e3-83050f4(a)127.0.0.1>} <script>: La respuesta de de > secfilter es <null> > 2025-08-07T09:42:54.876513+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: > exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1<mailto: > fabe0744-1fca28e3-83050f4(a)127.0.0.1>} *** cfgtrace:dbg_cfg_trace(): > request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1053 a=26 n=xlog > 2025-08-07T09:42:54.876556+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: > ALERT: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1<mailto: > fabe0744-1fca28e3-83050f4(a)127.0.0.1>} <script>: 1 > 2025-08-07T09:42:54.876587+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: > exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1<mailto: > fabe0744-1fca28e3-83050f4(a)127.0.0.1>} *** cfgtrace:dbg_cfg_trace(): > request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1058 a=16 n=if > 2025-08-07T09:42:54.876619+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: > exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1<mailto: > fabe0744-1fca28e3-83050f4(a)127.0.0.1>} *** cfgtrace:dbg_cfg_trace(): > request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1058 a=26 n=xlog > 2025-08-07T09:42:54.876651+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: > ALERT: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1<mailto: > fabe0744-1fca28e3-83050f4(a)127.0.0.1>} <script>: OPTIONS from 91.228.91.69 > blocked because Country 'ES' is blacklisted > 2025-08-07T09:42:54.876682+02:00 PRE-KAMAILIO /usr/sbin/kamailio[1393]: > exec: {1 1 OPTIONS fabe0744-1fca28e3-83050f4(a)127.0.0.1<mailto: > fabe0744-1fca28e3-83050f4(a)127.0.0.1>} *** cfgtrace:dbg_cfg_trace(): > request_route=[GEOIP] c=[/etc/kamailio/kamailio.cfg] l=1059 a=2 n=exit > > The output of kamcmd secfilter.print country > root@PRE-KAMAILIO:/etc/kamailio# kamcmd secfilter.print country > > Country > ======= > [+] Blacklisted > ----------- > > [+] Whitelisted > ----------- > 0001 -> ES > > > Samuel Moya Tinoco > Departamento de Sistemas y Redes > Móvil: (+34) 606985997 > smoya(a)vivelibre.es<mailto:smoya@vivelibre.es> > > ViveLibre > C/ La Orotava 4 > 28660 Boadilla del Monte > Madrid > www.vivelibre.es< > https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fwww.vivelibre.es%2f&c=E,… > > > > [cid:image001.png@01DC0859.0D93E4E0] > > Soluciones inteligentes > para la autonomía personal > > > > "Tanto este mensaje como todos los posibles documentos adjuntos al mismo > son confidenciales y están dirigidos exclusivamente a los destinatarios de > los mismos. Por favor, si Usted no es uno de dichos destinatarios, > notifíquenos este hecho y elimine el mensaje de su sistema. Queda prohibida > la copia, difusión o revelación de su contenido a terceros sin el previo > consentimiento por escrito de VIVELIBRE AUTONOMÍA PERSONAL S.L.U. > (VIVELIBRE). En caso contrario, vulnerará la legislación vigente. De > conformidad con lo establecido en el Reglamento (UE) 2016/679, General de > Protección de Datos, le informamos de que sus datos son objeto de > tratamiento por VIVELIBRE, en calidad de Responsable del Tratamiento. > VIVELIBRE tratará sus datos con la finalidad de mantener la relación > contractual, gestionar su solicitud, así como remitirle comunicaciones de > carácter comercial relacionadas con su ámbito de actividad y los servicios > prestados. Si desea ejercitar sus derechos de acceso, rectificación, > supresión, limitación, oposición o portabilidad, puede dirigirse a la > dirección postal Calle de la Orotava 4, 28660, Boadilla del Monte, (Madrid) > o a la dirección de correo electrónico protecciondedatos(a)vivelibre.es > <mailto:protecciondedatos@vivelibre.es>. Para obtener más información > sobre cómo tratamos sus datos, consulta nuestra Política de Privacidad en > Política de Privacidad - Vivelibre." > "Tanto este mensaje como todos los posibles documentos adjuntos al mismo > son confidenciales y están dirigidos exclusivamente a los destinatarios de > los mismos. Por favor, si Usted no es uno de dichos destinatarios, > notifíquenos este hecho y elimine el mensaje de su sistema. Queda prohibida > la copia, difusión o revelación de su contenido a terceros sin el previo > consentimiento por escrito de VIVELIBRE AUTONOMÍA PERSONAL S.L.U. > (VIVELIBRE). En caso contrario, vulnerará la legislación vigente. De > conformidad con lo establecido en el Reglamento (UE) 2016/679, General de > Protección de Datos, le informamos de que sus datos son objeto de > tratamiento por VIVELIBRE, en calidad de Responsable del Tratamiento. > VIVELIBRE tratará sus datos con la finalidad de mantener la relación > contractual, gestionar su solicitud, así como remitirle comunicaciones de > carácter comercial relacionadas con su ámbito de actividad y los servicios > prestados. Si desea ejercitar sus derechos de acceso, rectificación, > supresión, limitación, oposición o portabilidad, puede dirigirse a la > dirección postal Calle de la Orotava 4, 28660, Boadilla del Monte, (Madrid) > o a la dirección de correo electrónico protecciondedatos(a)vivelibre.es > <mailto:protecciondedatos@vivelibre.es>. Para obtener más información > sobre cómo tratamos sus datos, consulta nuestra Política de Privacidad en > Política de Privacidad - Vivelibre." > "Tanto este mensaje como todos los posibles documentos adjuntos al mismo > son confidenciales y están dirigidos exclusivamente a los destinatarios de > los mismos. Por favor, si Usted no es uno de dichos destinatarios, > notifíquenos este hecho y elimine el mensaje de su sistema. Queda prohibida > la copia, difusión o revelación de su contenido a terceros sin el previo > consentimiento por escrito de VIVELIBRE AUTONOMÍA PERSONAL S.L.U. > (VIVELIBRE). En caso contrario, vulnerará la legislación vigente. De > conformidad con lo establecido en el Reglamento (UE) 2016/679, General de > Protección de Datos, le informamos de que sus datos son objeto de > tratamiento por VIVELIBRE, en calidad de Responsable del Tratamiento. > VIVELIBRE tratará sus datos con la finalidad de mantener la relación > contractual, gestionar su solicitud, así como remitirle comunicaciones de > carácter comercial relacionadas con su ámbito de actividad y los servicios > prestados. Si desea ejercitar sus derechos de acceso, rectificación, > supresión, limitación, oposición o portabilidad, puede dirigirse a la > dirección postal Calle de la Orotava 4, 28660, Boadilla del Monte, (Madrid) > o a la dirección de correo electrónico protecciondedatos(a)vivelibre.es. > Para obtener más información sobre cómo tratamos sus datos, consulta > nuestra Política de Privacidad en Política de Privacidad - Vivelibre." >

1 0

Webrtc connection failure on multiple kamailio server setup
by er.maharaja＠gmail.com 07 Aug '25

07 Aug '25

Hi all, I am running 2 kamailio instances in kubernetes (daemonsets). kamailio act as webrtc server. all my webrtc clients are registered into kamailio. registration stored in location table (usrloc). Issue: 1. Webrtc client registers to kamailio instance-1 2. I am trying to make outbound call and it was initated from kamailio-2 3. kamailio-2 looks up into location table in DB and finds the user 4. However, when it tries to send the call over websocket's tcp, it fails with the following message 4(197) WARNING: {1 102703821 INVITE 0396e8d0-edae-123e-738c-325f60cc5a45} <core> [core/msg_translator.c:3036]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found Logically this is correct as the instance doesn't aware of the connection (kamcmd ws.dump does show the connection on kamailio-2 but it is seen in kamailio-1) I need help to share this connection details between the instances so that any kamailio instance can make outbound call regardless of where it was registered. Thank you for your help in advance. Maharaja

3 7

RTPEngine and branch_route
by David Tek 07 Aug '25

07 Aug '25

Hello, Using Kamailio 6.0.2. I'm running a registrar that can fork incoming calls to two or more registered users. Some users are WebRTC and others are not, so RTPEngine needs to handle them differently. In the branch route, I call: rtpengine_manage("via-branch=auto replace-origin"); However, the via-branch passed to RTPEngine doesn't match the branch ID of the actual INVITEs sent out. When one branch answers, the others get a CANCEL, but the CANCEL/200 OK sent to RTPEngine includes a different via-branch than the one used for the original INVITE. This causes media handling issues. I saw that the docs suggest using $T_branch(name) or AVPs to set the correct branch name, but $T_branch(name) seems deprecated or removed. In previous setups, branching was done on a separate instance, so identifying the right branch was easier. Now that it's local, I’m unsure how to arm rtpengine_manage() with the correct via-branch. *TL;DR:* When doing local forking, how can I set the correct via-branch value for each leg in rtpengine_manage()? Thanks, David

4 5

wrong transport selected
by Andrei Fedorov 06 Aug '25

06 Aug '25

Hello please advice what is wrong The scenario is following Client get registred with p-cscf using udp as transport and ipsec enabled Registration completed successfully. Client send reg event SUBSCRIBE, and get 200 back But it do not get any notification then. In p-cscf container I am observing NOTIFY coming from s-cscf and then something strange happen 52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: PCSCF: NOTIFY sip:172.22.0.1:55822;transport=udp (sip:9076543210@ims.mnc001.mcc001.3gppnetwork.org (172.22.0.20:6060) to sip:9076543210@ims.mnc001.mcc001.3gppnetwork.org, 0ed4dd8c-89a5-42ac-80cb-690891a400f1) 52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: Within DLG 52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: Within loose route 52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: PCSCF MO_indialog: Destination URI: <null> Request URI: sip:172.22.0.1:55822;transport=udp 52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: Source IP and Port: (172.22.0.20:6060) Route-URI: sip:mo@172.22.0.21:6101;lr=on;ftag=b7f568fe 52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: Received IP and Port: (172.22.0.21:6101) 52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: Next hop domain: (172.22.0.1) 52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: Contact header: <sip:scscf.ims.mnc001.mcc001.3gppnetwork.org:6060> 52(95) INFO: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} ims_ipsec_pcscf [cmd.c:1187]: ipsec_forward(): new destination URI: sip:172.22.0.1:55822 99(142) ERROR: <core> [core/tcp_main.c:4645]: handle_tcpconn_ev(): connect 172.22.0.1:55822 failed as you may see, request states transport=udp, Request URI: sip:172.22.0.1:55822;transport=udp while p-cscf then trying to use tcp?? 99(142) ERROR: [core/tcp_main.c:4645]: handle_tcpconn_ev(): connect 172.22.0.1:55822 failed what is wrong? Using tcp as a transport initially works well and NOTIFY is coming to the client. thanks in advance Andrei

2 2

Dispatcher failover to the next least loaded destination
by i.ribakov＠zaleos.net 05 Aug '25

05 Aug '25

Hi all, I'm wondering if it is currently supported to perform failover while respecting the call load distribution algorithm. What makes me doubt this is possible is the following wording in the documentation: > The rest of the destination list is taken in order of the entries in set - anyhow, until a re-route to next destination happens, the load on each address can change. From it it's not clear if ds_next_dst() will simplify use next entry from the AVP list or if it will attempt to intelligently choose next entry from the AVP list taking into the account updated call load of the remaining entries.

3 3

Unknown character set utf8mb4
by Igor Potjevlesch 05 Aug '25

05 Aug '25

Hello, We move to fresh version of Kamailio 6. We have a MySQL backend in an old version. We have many errors like this: ERROR: db_mysql [km_dbase.c:127]: db_mysql_submit_query(): driver error on query: Unknown character set: 'utf8mb4' (1115) ERROR: <core> [lib/srdb1/db_query.c:393]: db_do_update(): error while submitting query ERROR: dialog [dlg_db_handler.c:1000]: update_dialog_dbinfo_unsafe(): could not update database info ERROR: db_mysql [km_dbase.c:127]: db_mysql_submit_query(): driver error on query: Unknown character set: 'utf8mb4' (1115) ERROR: <core> [lib/srdb1/db_query.c:158]: db_do_query_internal(): error while submitting query ERROR: avpops [avpops_impl.c:328]: ops_dbload_avps(): db_load failed ERROR: db_mysql [km_dbase.c:127]: db_mysql_submit_query(): driver error on query: Unknown character set: 'utf8mb4' (1115) ERROR: <core> [lib/srdb1/db_query.c:158]: db_do_query_internal(): error while submitting query ERROR: avpops [avpops_impl.c:328]: ops_dbload_avps(): db_load failed It looks like the accounting module is not affected because we have writes in acc table. Registrar is affected because dump from location to location table is not working. Is there a way to make it work with older version of MySQL? Regards, Igor. -- Cet e-mail a été vérifié par le logiciel antivirus d'Avast. www.avast.com

2 5

2026

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