July 2025 - sr-dev - kamailio.org

[kamailio/kamailio] tls_tracker: added module for tls encriptions key export (PR #4339)
by sergey-safarov 02 Nov '25

02 Nov '25

#### 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 - [ ] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description Added TLS encryption keys export into the database. Later keys can be searched and saved to a file. Key search can be done by timestamp, connection IP addresses, and port numbers. For key search, used kamcmd utility. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4339 -- Commit Summary -- * tls_tracker: added module for tls encriptions key export -- File Changes -- A src/modules/tls_tracker/Makefile (75) A src/modules/tls_tracker/README (1) A src/modules/tls_tracker/api.c (33) A src/modules/tls_tracker/api.h (40) A src/modules/tls_tracker/doc/Makefile (4) A src/modules/tls_tracker/doc/tls_tracker.xml (117) A src/modules/tls_tracker/tls_tracker_mod.c (1126) A src/modules/tls_tracker/tls_tracker_mod.h (25) A src/modules/tls_tracker/tls_tracker_rpc.c (478) A src/modules/tls_tracker/tls_tracker_rpc.h (8) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4339.patch https://github.com/kamailio/kamailio/pull/4339.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4339 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4339(a)github.com>

4 11

[kamailio/kamailio] tls: Create one shared context and reuse it. (PR #3972)
by Xenofon Karamanos 24 Oct '25

24 Oct '25

#### 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 #3823 #### Description  This PR aims to implement what was discussed in [mailing list](https://lists.kamailio.org/mailman3/hyperkitty/list/sr-dev@lists.kama… regarding some `tls.reload` and increasing memory usage. It adds a new parameter `enable_shared_ctx` in `tls` module that if set to 0, preserves the old behavior and if set to 1 (other than 0 tbh), it creates a single SSL context that is being shared. This have the effect of using way less memory when initialized as well, but also minimizes (can't say it fixes the problem) the `tls.reload` memory increase. I have also added a small markdown (comparison.md) file, where some comparisons where made between enabled/disabled shared context and with/without CA file (where the initial problem was occurring by the reporter). Feedback would be necessary to verify whether this patch, acts as expected and kamailio works as intented. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3972 -- Commit Summary -- * tls: Add parameter for shared contexts * tls: Comparison for enable_shared_ctx -- File Changes -- A comparison.md (15) M src/modules/tls/tls_domain.c (172) M src/modules/tls/tls_mod.c (11) M src/modules/tls/tls_mod.h (1) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3972.patch https://github.com/kamailio/kamailio/pull/3972.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3972 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3972(a)github.com>

4 17

[kamailio/kamailio] wrong transport selected (Issue #4344)
by anfedoro 17 Oct '25

17 Oct '25

anfedoro created an issue (kamailio/kamailio#4344) 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> [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 -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4344 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4344(a)github.com>

3 3

[kamailio/kamailio] Handling Duplicate Values in secfilter Module's kamcmd Commands (Issue #4091)
by AsedMorteza 16 Oct '25

16 Oct '25

**Description** The `secfilter` module in `kamcmd` currently allows duplicate entries when adding values to certain lists (e.g., blacklists, whitelists). This can lead to unexpected behavior and potential inconsistencies. Could you clarify the reason behind accepting duplicate values? Recently, I submitted a pull request to add delete commands to the `secfilter` module #4089. When a user, for example, executes: `kamcmd secfilter.del_bl user 1005` I iterate through the entire list to ensure all occurrences of `1005` are removed, as I realized duplicates might exist. This is inefficient and could be avoided by preventing duplicates in the first place. **Proposed Solutions** 1. **Prevent Duplicates in Existing `add` Commands:** * I can modify existing `add` commands to directly prevent the addition of duplicate values. This would simplify future operations and improve performance. 2. **Introduce New `add_unique` Commands:** * I can maintain the current `add` commands for backward compatibility. * I can introduce new `add_unique` commands (e.g., `secfilter.add_bl_unique`) that explicitly reject duplicate entries. **Recommendation** I recommend implementing the first solution (preventing duplicates in existing `add` commands) as it provides the most straightforward and efficient approach. **Further Considerations** * Consider adding a check for duplicates during the `add` operation and returning an appropriate error message if a duplicate is encountered. * Document the behavior of duplicate values in the `secfilter` module's documentation. **I would appreciate your feedback and guidance on the best course of action.** -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4091 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4091(a)github.com>

7 18

[kamailio/kamailio] tm: allow pending forked REGISTER auths being handled the same way as… (PR #4304)
by ovoshlook 08 Oct '25

08 Oct '25

… forked INVITEs auths #### Pre-Submission Checklist - [*] Commit message has the format required by CONTRIBUTING guide - [*] Commits are split per component (core, individual modules, libs, utils, ...) - [*] Each component has a single commit (if not, squash them into one commit) - [*] No commits to README files for modules (changes must be done to docbook files #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [*] 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 - [ *] Tested changes locally - [ ]* Related to issue #[4266](https://github.com/kamailio/kamailio/issues/4266) #### Description If a Negative reply for forked REGISTER comes after the first 200 response, it won't be ignored by Kamailio and will be processed the same way as replies processed for the INVITEs You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4304 -- Commit Summary -- * tm: allow pending forked REGISTER auths being handled the same way as forked INVITEs auths -- File Changes -- M src/modules/tm/t_reply.c (15) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4304.patch https://github.com/kamailio/kamailio/pull/4304.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4304 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4304(a)github.com>

6 27

[kamailio/kamailio] Dispatcher: ds_is_from_list() only checks first record when doing DNS lookup (Issue #4338)
by Anton Olofsson 26 Sep '25

26 Sep '25

olofssonanton created an issue (kamailio/kamailio#4338) Here in `ds_is_addr_from_set`, `he->h_addr_list` may contain more than one address, but only the first address (as seen by the third argument, `addr_no`) is stored and later used for comparison. https://github.com/kamailio/kamailio/blob/91472b8d1015ace7c40c052a19913d384… https://github.com/kamailio/kamailio/blob/91472b8d1015ace7c40c052a19913d384… If a request is from any other address than the first in the resolved `hostent` address list, `ds_is_from_list` will give a false negative. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4338 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4338(a)github.com>

3 3

[kamailio/kamailio] KEMI app_python3 crash (Issue #4314)
by Denys Pozniak 24 Sep '25

24 Sep '25

denyspozniak created an issue (kamailio/kamailio#4314) ### Description The code below causes Kamailio to crash when sending a simple OPTIONS request. I agree that this is not the most proper way to call the sl function, but it's probably worth paying attention to this issue. #### Reproduction ```import sys import KSR as KSR def mod_init(): return kamailio() class kamailio: def __init__(self): KSR.info('== kamailio init ==\n') def child_init(self, rank): return 0 def ksr_request_route(self, msg): KSR.x.modf("sl_send_reply", "200", "OK"); return 1 ``` #### Debugging Data [(gdb) bt full.txt](https://github.com/user-attachments/files/21149798/gdb.bt.full.tx… [(gdb) info locals.txt](https://github.com/user-attachments/files/21149836/gdb.info.loc… ``` (gdb) list 154 in sl_funcs.c ``` #### Log Messages ``` Program received signal SIGSEGV, Segmentation fault. sl_reply_helper (msg=msg@entry=0x7ffff6fada80, code=200, reason=reason@entry=0x7ffff75d2070 "OK", tag=tag@entry=0x0) at sl_funcs.c:159 159 sl_funcs.c: No such file or directory. ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 6.1.0-dev1 (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 9.4.0 ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4314 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4314(a)github.com>

4 5

[kamailio/kamailio] fedora: changed bin file location (Issue #4341)
by sergey-safarov 24 Sep '25

24 Sep '25

sergey-safarov created an issue (kamailio/kamailio#4341) ### Description In modern dist `/usr/sbin` is symlinked to `/usr/bin`. Probably this needs some discussion. More info at https://fedoraproject.org/wiki/Changes/Unify_bin_and_sbin -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4341 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4341(a)github.com>

3 3

[kamailio/kamailio] Dialog: Timeout/dlg_bye randomly doesn't send BYE message (Issue #4169)
by Mercury109 23 Sep '25

23 Sep '25

Mercury109 created an issue (kamailio/kamailio#4169) ### Description I loop through the active dialogs in a timer functions and based on some conditions, a dialog may be ended by setting a short timeout or using the dlg_bye function. **Sometimes** when a dialog times out or the dlg_bye("all") function is used, the BYE is not being sent in both directions, only towards the caller. There's a warning: send_bye(): dlg [25641:71143] with callid XXXXXXXXX already in deleted state, BYE not sent. I noticed this check was added in the commit below: https://github.com/kamailio/kamailio/commit/d411c6ea4358e6d9dd367349e877ed5… Is there a race condition between marking the dialog as terminated and sending the BYE? Not sending a BYE towards the callee when it should is much worse than sending an unnecessary BYE as it causes billing issues. If this can't be resolved to be 100% reliable, it's safer to remove this check all together. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.7.6 (x86_64/linux)) ``` * **Operating System**: Debian GNU/Linux 12 (bookworm) -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4169 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4169(a)github.com>

4 7

[kamailio/kamailio] db_cluster module marking mysql connection down on "Illegal mix of collations" failure (Issue #4332)
by Ben Kaufman 14 Sep '25

14 Sep '25

whosgonna created an issue (kamailio/kamailio#4332)  ### Description We received a INVITE with non-ascii characters in the authentication username. The character set and collation of the subscriber table is `latin1` and `latin1_swedish_ci`. This generated the following failure (DB connection names are `primary` and `secondary`): ``` 3(9) ERROR: db_mysql [km_dbase.c:127]: db_mysql_submit_query(): driver error on query: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8mb4_general_ci,COERCIBLE) for operation '=' (1267) 3(9) ERROR: <core> [lib/srdb1/db_query.c:158]: db_do_query_internal(): error while submitting query 3(9) WARNING: db_cluster [dbcl_api.c:513]: db_cluster_query(): serial operation - failure on cluster [db] (9/0) [primary] 3(9) ERROR: db_mysql [km_dbase.c:127]: db_mysql_submit_query(): driver error on query: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8mb4_general_ci,COERCIBLE) for operation '=' (1267) 3(9) ERROR: <core> [lib/srdb1/db_query.c:158]: db_do_query_internal(): error while submitting query 3(9) WARNING: db_cluster [dbcl_api.c:513]: db_cluster_query(): serial operation - failure on cluster [db] (8/0) [secondary] 3(9) ERROR: db_cluster [dbcl_api.c:513]: db_cluster_query(): no successful read on cluster [db] 3(9) ERROR: auth_db [authorize.c:180]: get_ha1(): failed to query database 3(9) ERROR: [DIGEST_AUTH 60e4abd540674d4aa8961d380411585e(a)0.0.0.0 INVITE-124524] Generic failure in authentication. Send '503 Server Error' and exit. ``` While using the limited character set in the database (and it's associated collation) is questionable, and I don't expect the query to succeed, the issue is that this single query failure is causing the connections to be disabled in the db_cluster. ### Troubleshooting #### Reproduction I haven't tried to reproduce this, but I would assume it's easy to do. I can probably mock it up in docker fairly quickly. As a safety measure, I'll be validating the field with `is_alphanum()` #### Log Messages (as in description) #### SIP Traffic The `Username` in the `Proxy-Authorization` header as "\uFEFF1011". As hex it's: ``` 22 ef bb bf 31 30 31 31 22 ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 6.0.1 (aarch64/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-NOSMP, 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 on 18:45:18 Mar 14 2025 with gcc 14.2.0 ``` * **Operating System**:  Container: ``` NAME="Alpine Linux" ID=alpine VERSION_ID=3.21.2 PRETTY_NAME="Alpine Linux v3.21" HOME_URL="https://alpinelinux.org/" BUG_REPORT_URL="https://gitlab.alpinelinux.org/alpine/aports/-/issues" ``` Host: ``` NAME="Amazon Linux" VERSION="2023" ID="amzn" ID_LIKE="fedora" VERSION_ID="2023" PLATFORM_ID="platform:al2023" PRETTY_NAME="Amazon Linux 2023" ANSI_COLOR="0;33" CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2023" HOME_URL="https://aws.amazon.com/linux/" BUG_REPORT_URL="https://github.com/amazonlinux/amazon-linux-2023" ``` Kernel (`uname -a)`: ``` Linux use2apocor01.n.fl.gg 6.1.56-82.125.amzn2023.aarch64 #1 SMP Tue Oct 10 17:03:29 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4332 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4332(a)github.com>

3 3