sr-users November 2025

sr-users@lists.kamailio.org

22 participants
26 discussions

Unable to start Kamailio with TLS configuration
by Chandramouli P 21 Nov '25

21 Nov '25

Hello, Please find my server environment below: Operating System: RockyLinux 8.x and RHEL 8.x Kamailio version: 6.0.2 IP address: 10.122.0.4 I have generated SSL certificates using OpenSSL. After configuring Kamailio, I am unable to start Kamailio. Please find the steps that I used to generate certificates along with configuration at the below link: *https://pastebin.com/Veu8z9Pr <https://pastebin.com/Veu8z9Pr>* Any help would be appreciated and thanks in advance. Best Regards, Chandramouli.

3 11

How to access all branches in the failure_route
by 13715209697＠139.com 20 Nov '25

20 Nov '25

Hi team How to access all branches in the failure_route? ··· SIP/2.0 480 Temporarily Unavailable Via: SIP/2.0/UDP 220.231.180.131:12290;branch=z9hG4bK7699.12bab93a2131301bddba965165d7b8a4.0 Via: SIP/2.0/UDP 192.168.99.203:5090;received=192.168.99.203;rport=5090;branch=z9hG4bKeS4Hy8evHZa4N To: <sip:1001@192.168.99.203:12290>;tag=a8016513 From: <sip:9196@192.168.99.203:12290>;tag=rQSg2p11ptytp Call-ID: d25b05e3-3fb6-123f-0ba6-000c29943390 ··· failure_route[MANAGE_FAILURE] { xlog("$sel(via[1].branch) + $T_branch_idx\n"); } The obtained value is z9hG4bKeS4Hy8evHZa4N, which is the branch generated by UAC. But I also want to obtain the branch automatically generated by Kamailio. How can I do this? Thanks!

2 4

error while parsing credentials
by David Cunningham 20 Nov '25

20 Nov '25

Hello, We have one particular device which won't authenticate with Kamailio, and are looking for any insight into why. When Kamailio receives the REGISTER it logs: Nov 17 17:50:37 sip /sbin/kamailio[2293367]: ERROR: {1 2 REGISTER mrXSmu5Gh} <core> [core/parser/digest/digest.c:323]: find_credentials(): error while parsing credentials Nov 17 17:50:37 sip /sbin/kamailio[2293367]: ERROR: {1 2 REGISTER mrXSmu5Gh} auth [api.c:73]: pre_auth(): Error while looking for credentials A redacted copy of the REGISTER is below. I note two unusual things: - On the Authorization header it says "[truncated]Authorization". - It includes a "cnonce" (client nonce) in the Authorization data, which is unusual compared to our other SIP devices. Thanks in advance! Session Initiation Protocol (REGISTER) Request-Line: REGISTER sip:sip.example.com:5060 SIP/2.0 Message Header To: "C25" <sip:123456789@sip.example.com> SIP to display info: "C25" SIP to address: sip:123456789@sip.example.com SIP to address User Part: 123456789 SIP to address Host Part: sip.example.com From: "C25" <sip:123456789@sip.example.com>;tag=mmVG392Qv SIP from display info: "C25" SIP from address: sip:123456789@sip.example.com SIP from tag: mmVG392Qv Contact: <sip:123456789@11.22.221.114:65477;transport=udp> Contact URI: sip:123456789@11.22.221.114:65477;transport=udp Via: SIP/2.0/UDP 11.22.221.114:65477;branch=z9hG4bK.X0v8d63yc CSeq: 2 REGISTER Call-ID: iYC5fcJqy [Generated Call-ID: iYC5fcJqy] Max-Forwards: 70 Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, NOTIFY User-Agent: Rogue sip 7.1.11 (stm32mp15-ya157c-v2) linux Expires: 3600 [truncated]Authorization: Digest realm="sip.example.com", nonce="aRvGYGkbxTQrS5pTzBoahdefo1xCqskN", algorithm=MD5, username="123456789", uri="sip:sip.example.com:5060", response="ab717ce439c666e9b5651d0dc74dff9a", cnonce="MzrTCxYCoCPxZ Authentication Scheme: Digest Realm: "sip.example.com" Nonce Value: "aRvGYGkbxTQrS5pTzBoahdefo1xCqskN" Algorithm: MD5 Username: "123456789" Authentication URI: "sip:sip.example.com:5060" Digest Authentication Response: "ab717ce439c666e9b5651d0dc74dff9a" CNonce Value: "MzrTCxYCoCPxZ91a" Nonce Count: 00000001 QOP: Content-Length: 0 -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

3 4

Re: sr-users Digest, Vol 246, Issue 20
by Seke Kazuru 19 Nov '25

19 Nov '25

1 0

Re: sr-users Digest, Vol 246, Issue 19
by Seke Kazuru 19 Nov '25

19 Nov '25

1 0

jwt module not found for debian 5.8?
by David Villasmil 17 Nov '25

17 Nov '25

Hello guys, trying to install the jwt module on debian 11, but it's not found. I'm using kamailio's debian repos: deb http://deb.kamailio.org/kamailio58 bullseye main deb-src http://deb.kamailio.org/kamailio58 bullseye main my kamailio version is 5.8: # kamailio -V version: kamailio 5.8.3 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_SEND_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: unknown compiled with gcc 10.2.1 the search doesn't return kamailio-jwt-modules # apt-cache search kamailio kamailio - very fast, dynamic and configurable SIP server kamailio-dbg - very fast and configurable SIP server [debug symbols] kamailio-erlang-modules - Erlang modules for the Kamailio SIP server kamailio-extra-modules - Extra modules for the Kamailio SIP Server kamailio-geoip-modules - The geoip module for the Kamailio SIP Server kamailio-geoip2-modules - The geoip2 module for the Kamailio SIP Server kamailio-kazoo-modules - kazoo modules for the Kamailio SIP server kamailio-ldap-modules - LDAP modules for the Kamailio SIP server kamailio-lua-modules - The app_lua module for Kamailio Lua support kamailio-lwsc-modules - Libwebsockets module for the Kamailio SIP server kamailio-microhttpd-modules - Microhttpd module for the Kamailio SIP server kamailio-mono-modules - The app_mono module for the Kamailio SIP server kamailio-nth - Kamailio SIP server - package for "nice to have" utilities kamailio-outbound-modules - SIP Outbound module for the Kamailio SIP server kamailio-python-modules - The app_python module for the Kamailio SIP server kamailio-python3-modules - The app_python3 module for the Kamailio SIP server kamailio-ruby-modules - The app_ruby module for Kamailio Ruby support kamailio-secsipid-modules - contains the secsipid module kamailio-tls-wolfssl-modules - TLS support for the Kamailio SIP server (authentication, transport) kamailio-autheph-modules - authentication using ephemeral credentials for the Kamailio SIP server kamailio-berkeley-bin - Berkeley database module for Kamailio - helper program kamailio-berkeley-modules - Berkeley database module for the Kamailio SIP server kamailio-cnxcc-modules - cnxcc modules for the Kamailio SIP server kamailio-cpl-modules - CPL module (CPL interpreter engine) for the Kamailio SIP server kamailio-ims-modules - IMS module for the Kamailio SIP server kamailio-json-modules - Json parser and Json-RPC modules for the Kamailio SIP server kamailio-memcached-modules - interface to the memcached server, for the Kamailio SIP server kamailio-mongodb-modules - mongodb modules for the Kamailio SIP server kamailio-mqtt-modules - MQTT modules for the Kamailio SIP Server kamailio-mysql-modules - MySQL database connectivity module for Kamailio kamailio-perl-modules - Perl extensions and database driver for the Kamailio SIP server kamailio-phonenum-modules - phonenum modules for the Kamailio SIP server kamailio-postgres-modules - PostgreSQL database connectivity module for the Kamailio SIP server kamailio-presence-modules - SIP presence modules for Kamailio kamailio-rabbitmq-modules - RabbitMQ and AMQP integration modules for the Kamailio SIP server kamailio-radius-modules - RADIUS modules for the Kamailio SIP server kamailio-redis-modules - Redis database connectivity module for the Kamailio SIP server kamailio-sctp-modules - SCTP SIP transport module for the Kamailio SIP server kamailio-snmpstats-modules - SNMP AgentX subagent module for the Kamailio SIP server kamailio-sqlite-modules - SQLite database connectivity module for the Kamailio SIP server kamailio-systemd-modules - systemd logging modules for the Kamailio SIP server kamailio-tls-modules - TLS support for the Kamailio SIP server (authentication, transport) kamailio-unixodbc-modules - unixODBC database connectivity module for the Kamailio SIP server kamailio-utils-modules - Utility functions for the Kamailio SIP server kamailio-websocket-modules - WebSocket module for the Kamailio SIP server kamailio-xml-modules - XML based extensions for Kamailio's Management Interface kamailio-xmpp-modules - XMPP gateway module for the Kamailio SIP server kamcli - Kamailio Command Line Interface Control Tool Am I missing something? Thanks! David Villasmil email: david.villasmil.work(a)gmail.com

2 2

Delete register when websocket closes
by Samuel Moya Tinoco 17 Nov '25

17 Nov '25

Hi everyone, I'm using my kamailio to register extensions and route calls to different asterisks. With the configuration that we have right now if we close the websocket used for the register of an extension the contact still persist in kamailio until it expires. Is there any parameter or module to delete a contact when we close a websocket? Thanks in advance 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@01DC579E.71C9C490] 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."

2 1

pdt.list
by simon.halder＠eckoh.com 14 Nov '25

14 Nov '25

I have kamailio version 5.6.0 , when I run kamcmd pdt.list I get "error: 500 - Internal error printing records" . I have checked all the entries in the pdt database table for invalid/incorrect characters but looks fine. Any ideas anyone ?

3 2

Proxy-Require: privacy error "420 Bad Proxy Require Extension"
by David Costa 13 Nov '25

13 Nov '25

Hello, When my kamailio 5.8.2 receives an INVITE with header "Proxy-Require: privacy" it replies "420 Bad Proxy Require Extension" with "Unsupported: privacy", but we are treating privacy on our code. Is the default behavior for sanity Proxy-Require validations rejecting calls with "420 Bad Proxy Require Extension" ? If default behavior for sanity Proxy-Require validations is rejecting calls with "420 Bad Proxy Require Extension" , I can use "modparam("sanity", "proxy_require", "privacy")". Or based on https://lists.kamailio.org/pipermail/sr-users/2015-August/089636.html the best approach to solve this is subtract 512 from proxy_require to kamailio default sanity value 3047 using modparam("sanity", "default_checks", 2535)? Thanks, David Costa

2 1

Incorrect routing of PRACK with TOPOS_htalbe
by 13910937632＠163.com 10 Nov '25

10 Nov '25

In Kamailio 6.0.3, Kamailio is incorrectly routing the PRACK. PRACK skipped the proxy indicated by the record_route header in message 183 and was sent directly to the callee indicated by the contact. The PRACK is handled correctly when TOPOS_redis

1 0

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