sr-dev April 2026

sr-dev@lists.kamailio.org

18 participants
288 discussions

[kamailio/kamailio] Allow customizing the contact user in uac reg requests (Issue #4653)
by Flavio Grossi 14 May '26

14 May '26

flaviogrossi created an issue (kamailio/kamailio#4653) ### Description Currently the uac module uses the value of the `l_uuid` variable as the user part in the contact header for the REGISTER request. Some providers, especially when registering trunks, requires the user part to be the registration username though, and, while it is possible to do it using the config, it may get cumbersome and error prone to remap the contact back in the reply. ### Expected behavior To be able to customize the contact in the register #### Actual observed behavior The register hardcodes the `l_uuid` value in the register, see [here](https://github.com/kamailio/kamailio/blob/d9a05f9781d2d9cddf485e938ea… This causes the registration to never be in the registered status when it is queried via the reg_dump rpc, unless the contact is rewritten via config both in the request (to make the SIP provider happy) and in the reply (to replace it back to use the uuid so that the check [here](https://github.com/kamailio/kamailio/blob/d9a05f9781d2d9cddf485e938ea… matches). ### Possible Solutions I'm currently testing a patch which: - adds an optional new field `contact_user` which, if present, is used in the contact user part instead of the uuid; - adds to the outgoing REGISTER the contact parameter `line=<l_uuid>` (only when `contact_user` is configured, returns an error if `contact_addr` already contains a line parameter to avoid it to be silently overwritten) - the REGISTER reply match is extended to check the uuid in the line parameter instead of the user part (only if `contact_user` is configured) to select the correct binding. This means that if the new parameter is configured, the contact will be in the form `sip:<contact_user>@<contact_addr>;line=<l_uuid>`. If not, the usual `sip:<l_uuid>@<contact_addr>` is sent. This should allow the new feature while also being retro compatible. Do you think this is correct? Any feedback? If it is, i can send a PR for review. ### Additional Information This applies to the latest develop version of kamailio and is OS independent -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4653 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4653(a)github.com>

3 4

[kamailio/kamailio] core: add support for pre-processor undefines (PR #4713)
by Tyler Moore 12 May '26

12 May '26

#### Pre-Submission Checklist - [ x ] Commit message has the format required by CONTRIBUTING guide - [ x ] Commits are split per component (core, individual modules, libs, utils, ...) - [ x ] Each component has a single commit (if not, squash them into one commit) - [ x ] Code is formatted with `clang-format` using the config file `.clang-format` from source code folder - [ x ] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [ x ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist: - [ ] PR should be backported to stable branches - [ x ] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description Adds support for undefining pre-processor IDs. New directives: - `#!undefine <ID>` - `#!tryundefine <ID>` Useful for testing scenarios or local override configs. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4713 -- Commit Summary -- * core: add support for pre-processor undefines -- File Changes -- M src/core/cfg.lex (116) M src/core/ppcfg.h (8) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4713.patchhttps://github.com/kama… -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4713 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4713(a)github.com>

3 3

[kamailio/kamailio] Draft: Allow customizing the contact user in uac reg requests #4653 (PR #4679)
by Flavio Grossi 12 May '26

12 May '26

#### Pre-Submission Checklist    - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [x] Tested changes locally - [x] Related to issue #4653 #### Description  This is the proposed pull request for issue #4653 Marked as draft because: - still seeking for suggestions if this is the correct way to do it - the PR still misses the database migration related code and documentation changes, which i will add if the general idea of the PR is accepted - i am not an expert in kamailio internals currently the uac module uses the value of the l_uuid variable as the user part in the contact header for the REGISTER request. this change allows to customize the contact user part by providing an optional new field contact_user which, if present, used in the contact user part instead of the uuid. it also adds to the outgoing REGISTER the contact parameter line=<l_uuid> (only when contact_user is configured, returns an error if contact_addr already contains a line parameter to avoid it to be silently overwritten) the REGISTER reply match is extended to check the uuid in the line parameter instead of the user part (only if contact_user is configured) to select the correct binding. Open points: - [ ] Documentation changes missing - [ ] Db changes missing - [ ] should uac_reg_lookup() also be fixed to lookup by the line parameter? You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4679?email_source=notifications&a… -- Commit Summary -- * Allow customizing the contact user in uac reg requests #4653 -- File Changes -- M src/lib/srdb1/schema/entities.xml (1) M src/lib/srdb1/schema/uacreg.xml (10) M src/modules/uac/uac_reg.c (191) M src/modules/uac/uac_reg.h (3) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4679.patch?email_source=notificat… -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4679 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4679(a)github.com>

2 2

[kamailio/kamailio] dmqueue: add peer-up and peer-down event_routes (PR #4661)
by Gustavo Almeida 11 May '26

11 May '26

#### Description This PR introduces `event_routes` that will trigger when `dmq peers` go up and down during the time. Really useful to detect problems between `peers` and allows addition of prometheus metrics for example, to add automatic visibility. #### Pre-Submission Checklist    - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [x] PR should be backported to stable branches - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Tests Tested locally simulating crashes and startups to evaluate the trigger of routes. Couldn't found any problems or strange cases, on ping intervals the status validation, gives the correct output. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4661 -- Commit Summary -- * dmqueue: add peer up and down event routes -- File Changes -- M src/modules/dmq/dmq.c (68) M src/modules/dmq/dmq.h (3) M src/modules/dmq/dmqnode.c (30) M src/modules/dmq/dmqnode.h (2) M src/modules/dmq/doc/dmq_admin.xml (79) M src/modules/dmq/notification_peer.c (22) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4661.patchhttps://github.com/kama… -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4661 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4661(a)github.com>

4 38

[kamailio/kamailio] Add dmq_peer_id modparams (PR #4706)
by Stefan Mititelu 11 May '26

11 May '26

#### Pre-Submission Checklist    - [X] Commit message has the format required by CONTRIBUTING guide - [X] Commits are split per component (core, individual modules, libs, utils, ...) - [X] Each component has a single commit (if not, squash them into one commit) - [X] Code is formatted with `clang-format` using the config file `.clang-format` from source code folder - [X] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [X] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [X] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  Add new dmq_peer_id modparams for modules that use DMQ. Useful when one wants to add new kamailio node in existing DMQ cluster, but not sync with (some) old kamailio node peers. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4706 -- Commit Summary -- * htable: add new modparam dmq_peer_id * dialog: add new modparam dmq_peer_id * rtpengine: add new modparam dmq_peer_id * presence: add new modparam dmq_peer_id * dmq_usrloc: add new modparam dmq_peer_id * dmq: update reply message when peer id not found -- File Changes -- M src/modules/dialog/dialog.c (2) M src/modules/dialog/dlg_dmq.c (7) M src/modules/dialog/doc/dialog_admin.xml (21) M src/modules/dmq/message.c (2) M src/modules/dmq_usrloc/dmq_usrloc.c (2) M src/modules/dmq_usrloc/doc/dmq_usrloc_admin.xml (21) M src/modules/dmq_usrloc/usrloc_sync.c (7) M src/modules/htable/doc/htable_admin.xml (21) M src/modules/htable/ht_dmq.c (7) M src/modules/htable/htable.c (2) M src/modules/presence/doc/presence_admin.xml (22) M src/modules/presence/presence.c (2) M src/modules/presence/presence_dmq.c (8) M src/modules/rtpengine/doc/rtpengine_admin.xml (22) M src/modules/rtpengine/rtpengine.c (2) M src/modules/rtpengine/rtpengine_dmq.c (8) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4706.patchhttps://github.com/kama… -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4706 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4706(a)github.com>

3 2

[kamailio/kamailio] Sanity (PR #4704)
by Xenofon Karamanos 11 May '26

11 May '26

#### Pre-Submission Checklist    - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] Code is formatted with `clang-format` using the config file `.clang-format` from source code folder - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [x] PR should be backported to stable branches - [x] Tested changes locally - [] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  Add RFC3261 compliance to Route headers by checking lr paramater You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4704?email_source=notifications&a… -- Commit Summary -- * sanity: Add lr check for Route Headers * sanity: docs: Update RFC3261 check -- File Changes -- M src/modules/sanity/doc/sanity_admin.xml (2) M src/modules/sanity/sanity.c (34) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4704.patch?email_source=notificat… -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4704 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4704(a)github.com>

2 4

[kamailio/kamailio] Phonenum (PR #4703)
by Xenofon Karamanos 11 May '26

11 May '26

#### Pre-Submission Checklist    - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] Code is formatted with `clang-format` using the config file `.clang-format` from source code folder - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  Add RFC3261 compliance for Route header by checking lr parameter You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4703?email_source=notifications&a… -- Commit Summary -- * phonenum: add support for short-number validation mode * phonenum: docs: add documentation for shortcode parameter * phonenum: tests: add unit tests for short code and normal number validation -- File Changes -- M src/modules/phonenum/cphonenumber.cpp (17) M src/modules/phonenum/cphonenumber.h (2) M src/modules/phonenum/doc/phonenum_admin.xml (28) M src/modules/phonenum/phonenum_mod.c (4) A test/unit/62.cfg (83) A test/unit/62.sh (64) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4703.patch?email_source=notificat… -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4703 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4703(a)github.com>

2 3

[kamailio/kamailio] memory leak if subst_body is used (Issue #4707)
by Riccardo-78 11 May '26

11 May '26

Riccardo-78 created an issue (kamailio/kamailio#4707) ### Description When using subst_body, the memory allocated for compiling the regular expression is never freed, resulting in a memory leak. Subst_body definition: ``` {"subst_body", (cmd_function)subst_body_f, 1, fixup_substre, 0, ANY_ROUTE}, ``` Memory is allocated in function fixup_substre: ``` se = subst_parser(&subst); ``` In subst_body_f (which calls subst_body_helper_f) subst_run runs regexec for matching but `se` is never freed with subst_expr_free(se); ### Troubleshooting #### Reproduction Use subst_body from textops in kamailio.cfg, after some calls RSS usage is increased. #### Debugging Data ``` (paste your debugging data here) ``` #### Log Messages ``` (paste your log messages here) ``` #### SIP Traffic ``` (paste your sip traffic here) ``` ### Possible Solutions Add subst_expr_free(se) to subst_body_f before returning. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.8.6 (x86_64/linux) fb71db 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: fb71db compiled on 19:26:27 Mar 29 2025 with gcc 8.5.0 ``` * **Operating System**: ``` Linux lihost 4.18.0-513.11.1.el8_9.x86_64 #1 SMP Wed Jan 17 02:00:40 EST 2024 x86_64 x86_64 x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4707 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4707(a)github.com>

2 5

[kamailio/kamailio] UAC authentication fails when receiving multiple Proxy-Authenticate headers (SHA-256 and MD5) from WhatsApp (Issue #4698)
by sznoname 06 May '26

06 May '26

sznoname created an issue (kamailio/kamailio#4698) When integrating Kamailio (v5.8.2) with WhatsApp/Meta SIP services, the WhatsApp server returns a 407 Proxy Authentication Required response containing two Proxy-Authenticate headers with different algorithms (SHA-256 and MD5): ``` Proxy-Authenticate: Digest realm="wa.meta.vc",nonce="47cdac2830f7539b",opaque="7a2b178b2328d18b",algorithm=SHA-256,qop="auth" Proxy-Authenticate: Digest realm="wa.meta.vc",nonce="729eeee06334d43b",opaque="1a8057db2558c27a",algorithm=MD5,qop="auth" ``` Currently, Kamailio seems to have issues processing the SHA-256 algorithm in this context, or it fails to correctly fall back to the MD5 header when SHA-256 is encountered first. This results in an authentication failure, preventing the SIP trunk from establishing a connection with WhatsApp. Observed Behavior Kamailio’s authentication logic (specifically within the uac module’s header parsing) does not skip the unsupported SHA-256 header to pick the MD5 one, or it fails to parse the response correctly when multiple headers are present. Temporary Workaround/Patch I have implemented a temporary fix by modifying the get_authenticate_hdr() function to filter out headers containing algorithm=SHA. This forces Kamailio to select the MD5-based authentication header. Modified Code: ``` for(hdr = rpl->headers; hdr; hdr = hdr->next) { if(rpl_code == WWW_AUTH_CODE && hdr->type == HDR_WWW_AUTHENTICATE_T && !strstr(hdr->name.s, "algorithm=SHA")) return hdr; if(rpl_code == PROXY_AUTH_CODE && hdr->type == HDR_PROXY_AUTHENTICATE_T && !strstr(hdr->name.s, "algorithm=SHA")) return hdr; } ``` Analysis of the Patch - Logic: During the header iteration, we added a !strstr(hdr->name.s, "algorithm=SHA") check. This bypasses any header using SHA-256 and allows the logic to fall back to the MD5 header. - Use Case: This successfully resolves the interoperability issue with WhatsApp’s 407 response for Kamailio 5.8.2. - Limitations: This is a hotfix. It does not implement actual SHA-256 support but simply ensures compatibility by forcing MD5 when both are present. Environment - Kamailio Version: 5.8.2 - Module: uac -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4698 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4698(a)github.com>

3 6

[kamailio/kamailio] ims_diameter_server: don't leak on diameter_request() (PR #4570)
by Victor Seva 05 May '26

05 May '26

2 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev April 2026