sr-dev March 2026

sr-dev@lists.kamailio.org

35 participants
467 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] 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] ims_diameter_server: don't leak on diameter_request() (PR #4570)
by Victor Seva 05 May '26

05 May '26

2 3

[kamailio/kamailio] app_lua: packaging many times with different lua library versions (Issue #4578)
by Daniel-Constantin Mierla 04 May '26

04 May '26

miconda created an issue (kamailio/kamailio#4578) At least Debian/Ubuntu ship many versions of lua and liblua, like 5.1, 5.2, 5.3 and 5.4. So far the package including app_lua compiled with liblua5.1, @linuxmaniac plans to switch to a newer version, but I am thinking that maybe we can ship app_lua many times, to offer a variant linked with each lualib version. The app_lua module can be compiled with any of those available in Debian/Ubuntu. Therefore I am starting this issue more like a discussion to see what can be done. Maybe @xkaraman can comment if cmake could cover easier such needs. We can provide the internal module name as a compile option (i.e., `-DMOD_NAME='"app_lua"'` or `-DMOD_NAME='"app_lua52"'`), then the output object file should have similar name (e.g., `app_lua.so` or `app_lua52.so`). I see a combination of two input values, the name of the module and the library version to compile with. I would say, linking with the latest stable library version should result in the `app_lua.so`, the other variants should be with version number (e.g., `app_lua52.so`). The question is also if @linuxmaniac (and the other packagers) could leverage such mechanism, to compile a module many times and package the results in different packages, because they have different library requirements/dependencies. There is a similar case with `tls` and `tlsa`, which is done a bit awkward, by including tls files completely inside tlsa files. I won't go the same path, the need for tlsa was required by the instability of latest libssl at that moment. Here, if we cannot find a flexible and easy enough solution, we should probably just go with linking against latest stable liblua. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4578 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4578(a)github.com>

6 15

[kamailio/kamailio] P-CSCF crashes with SIGSEGV in REGISTER_reply/ipsec_create path during IMS registration (Issue #4670)
by kongjun586999 04 May '26

04 May '26

kongjun586999 created an issue (kamailio/kamailio#4670)  ### Description Kamailio P-CSCF crashes with SIGSEGV while processing a REGISTER reply during IMS registration. Based on the logs, the crash happens in the REGISTER_reply path after a 401 response is matched to an active transaction. The routing script enters ipsec_create, then ims_ipsec_pcscf reports that the SIP reply has no Contact header and reconstructs the AOR from Via. After that, IPSec cleanup functions report netlink errors, and ims_usrloc_pcscf finds a pcontact in memory with reg_state[unknown]. Immediately after this, the worker process exits with signal 11 (SIGSEGV). From the logs, this issue appears to be triggered by abnormal state handling in the REGISTER reply processing path involving transaction state, IPSec handling, and pcontact lookup.  ### Troubleshooting Deployment mode: Docker Role: Kamailio as IMS P-CSCF No core dump was available #### Observed log sequence 1.A previous REGISTER transaction shows abnormal reply state (408 / 500 visible in logs) 2.A subsequent 401 reply matches an active transaction 3.The script enters ipsec_create 4.ims_ipsec_pcscf reports no Contact header and builds AOR from Via 5.IPSec cleanup reports netlink errors 6.ims_usrloc_pcscf finds a pcontact with reg_state[unknown] 7.Kamailio worker crashes with SIGSEGV #### Reproduction The issue can be reproduced by sending high-rate IMS registration traffic for the same UE, repeatedly triggering: 1.initial registration 2.re-registration 3.de-registration in rapid succession. In my test, the same UE identity is used continuously, and these REGISTER / re-REGISTER / de-REGISTER procedures are sent at high speed so that different registration-related transactions overlap closely in time. Under this condition, Kamailio P-CSCF eventually crashes in the REGISTER_reply processing path with SIGSEGV.  #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` 92(133) DEBUG: {2 100000901 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER_reply} ims_usrloc_pcscf [udomain.c:578]: get_pcontact_from_cache(): continuing to match on received details 92(133) DEBUG: {2 100000901 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER_reply} ims_usrloc_pcscf [udomain.c:541]: get_pcontact_from_cache(): comparing contact with aorhash [2715556337], aor [sip:505030000000005@192.168.55.147:40579] 92(133) DEBUG: {2 100000901 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER_reply} ims_usrloc_pcscf [udomain.c:543]: get_pcontact_from_cache(): contact host [192.168.55.147:40579] 92(133) DEBUG: {2 100000901 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER_reply} ims_usrloc_pcscf [udomain.c:545]: get_pcontact_from_cache(): contact received [1:192.168.55.147:40579] 92(133) DEBUG: {2 100000901 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER_reply} ims_usrloc_pcscf [udomain.c:553]: get_pcontact_from_cache(): matched a record by aorhash: 2715556337 92(133) DEBUG: {2 100000901 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER_reply} ims_usrloc_pcscf [udomain.c:578]: get_pcontact_from_cache(): continuing to match on received details 92(133) DEBUG: {2 100000901 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER_reply} ims_usrloc_pcscf [udomain.c:606]: get_pcontact_from_cache(): found contact with URI [sip:505030000000005@192.168.55.147:40579] 92(133) DEBUG: {2 100000901 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER_reply} ims_usrloc_pcscf [udomain.c:706]: get_pcontact_from_cache(): contact found in memory, reg_state[unknown] 99(140) CRITICAL: <core> [core/pass_fd.c:284]: receive_fd(): EOF on 52 0(7) ALERT: <core> [main.c:824]: handle_sigs(): child process 43 exited by a signal 11 0(7) ALERT: <core> [main.c:828]: handle_sigs(): core was generated 0(7) INFO: <core> [main.c:851]: handle_sigs(): terminating due to SIGCHLD 5(46) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 13(54) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 1(42) INFO: {1 100014610 REGISTER 00000000000000000000(a)192.168.55.147 DEFAULT_ROUTE} <core> [main.c:907]: sig_usr(): signal 15 received 19(60) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 17(58) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 18(59) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 6(47) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 3(44) INFO: {1 100014612 REGISTER 00000000000000000000(a)192.168.55.147 DEFAULT_ROUTE} <core> [main.c:907]: sig_usr(): signal 15 received 4(45) INFO: {1 100014611 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER} <core> [main.c:907]: sig_usr(): signal 15 received 31(72) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 38(79) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 20(61) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 21(62) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 39(80) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 23(64) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 35(76) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 16(57) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 14(55) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 8(49) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 11(52) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 33(74) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 15(56) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 36(77) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 40(81) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 42(83) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 27(68) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 41(82) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 29(70) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 10(51) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 45(86) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 46(87) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 44(85) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 52(93) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 50(91) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 56(97) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 37(78) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 24(65) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 47(88) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 30(71) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 26(67) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 51(92) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 49(90) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 28(69) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 12(53) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 43(84) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 54(95) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 32(73) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 55(96) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 25(66) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 66(107) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 48(89) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 7(48) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 53(94) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 22(63) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 9(50) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 60(101) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 59(100) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 61(102) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 64(105) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 57(98) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 63(104) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 62(103) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 68(109) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 69(110) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 70(111) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 65(106) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 71(112) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 58(99) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 72(113) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 73(114) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 34(75) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 77(118) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 78(119) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 79(120) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 75(116) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 81(122) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 82(123) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 80(121) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 86(127) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 85(126) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 84(125) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 83(124) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 67(108) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 88(129) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 90(131) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 91(132) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 89(130) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 99(140) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 94(135) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 96(137) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 93(134) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 97(138) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 95(136) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 87(128) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 92(133) INFO: {2 100000901 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER_reply} <core> [main.c:907]: sig_usr(): signal 15 received 74(115) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 98(139) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 76(117) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 0(7) ERROR: ims_ipsec_pcscf [ipsec.c:654]: clean_sa(): Error sending delete SAs command via netlink socket: No data available 0(7) WARNING: ims_ipsec_pcscf [cmd.c:1424]: ipsec_cleanall(): Error cleaning IPSec Security associations during startup. 0(7) ERROR: ims_ipsec_pcscf [ipsec.c:703]: clean_policy(): Error sending delete policies command via netlink socket: No data available 0(7) WARNING: ims_ipsec_pcscf [cmd.c:1428]: ipsec_cleanall(): Error cleaning IPSec Policies during startup. 0(7) CRITICAL: <core> [main.c:734]: sig_alarm_abort(): shutdown timeout triggered, dying.../kamailio_init.sh: line 45: 7 Aborted (core dumped) /mnt/pcscf/${COMPONENT_NAME}_init.sh ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 6.1.1 (x86_64/linux) 01f496 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, DBG_QM_MALLOC, DBG_F_MALLOC, DBG_TLSF_MALLOC, 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: 01f496 compiled on 15:06:49 Mar 23 2026 with gcc 11.4.0 ``` * **Operating System**:  ``` Distributor ID: Ubuntu Description: Ubuntu 22.04.5 LTS Release: 22.04 Codename: jammy ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4670 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4670(a)github.com>

2 8

[kamailio/kamailio] P-CSCF crash in ims_registrar_pcscf during concurrent REGISTER and de-REGISTER (Issue #4671)
by kongjun586999 04 May '26

04 May '26

kongjun586999 created an issue (kamailio/kamailio#4671)  ### Description Under high-rate concurrent registration activity for the same UE, Kamailio P-CSCF may crash while processing IMS REGISTER requests. Based on the observed logs, the failure happens in the ims_registrar_pcscf path, where sec_agree.c:parse_sec_agree() first reports abnormal warnings, and shortly afterwards a child process exits with signal 11 and a core dump is generated. The issue appears when REGISTER and de-REGISTER style requests for the same contact are processed concurrently. In this situation, one execution path is still handling security-agreement related state, while another path is updating or expiring the same pending registration state. This may lead to inconsistent internal state and eventually a crash.  ### Troubleshooting Deployment mode: Docker Role: Kamailio as IMS P-CSCF No core dump was available #### Observed log sequence 1.Multiple REGISTER requests for the same UE/contact are processed concurrently by P-CSCF. 2.ims_registrar_pcscf reports warnings from sec_agree.c:parse_sec_agree(), including: qm_free(): WARNING: free(0) called from ims_registrar_pcscf: sec_agree.c: parse_sec_agree(...) 4.The affected requests continue into: request_route=[REGISTER] pcscf_save_pending save_pending() 5.At least some requests are processed as regular registration updates with a non-zero expiry value. 6.Another concurrent request for the same contact is processed with expiry 0, corresponding to a de-registration/unregister-style update. 7.A Kamailio child process then exits with signal 11, and a core dump is generated. #### Reproduction The issue can be reproduced by sending high-rate concurrent REGISTER traffic for the same UE against P-CSCF, including both: repeated REGISTER / re-REGISTER requests for the same contact concurrent de-REGISTER style requests for the same contact, using expiry 0 In my setup, reproduction was performed in a Docker-based deployment by rapidly and repeatedly issuing registration, re-registration, and de-registration for the same UE so that these requests overlap in processing on the P-CSCF side.  #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` 3(44) NOTICE: {1 100003144 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER} <script>: Received IP and Port: (172.22.0.21:5060) 3(44) ERROR: {1 100003144 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER} *** cfgtrace:dbg_cfg_trace(): request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=12 a=25 n=xnotice 3(44) NOTICE: {1 100003144 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER} <script>: Contact header: <sip:505030000000005@192.168.55.147:40318>;+g.3gpp.accesstype="cellular2";audio;+g.3gpp.smsip;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";+sip.instance="<urn:gsma:imei:86196306-254962-0>" 3(44) ERROR: {1 100003144 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER} *** cfgtrace:dbg_cfg_trace(): request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=15 a=63 n=assign 3(44) DEBUG: {1 100003144 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER} textops [txt_var.c:87]: tr_txt_eval_re(): no match for subst expression 3(44) ERROR: {1 100003144 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER} *** cfgtrace:dbg_cfg_trace(): request_route=[] c=[] l=0 a=12 n=seturi 3(44) ERROR: {1 100003144 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER} *** cfgtrace:dbg_cfg_trace(): request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=22 a=16 n=if 3(44) ERROR: {1 100003144 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER} *** cfgtrace:dbg_cfg_trace(): request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=17 a=25 n=is_present_hf 3(44) ERROR: {1 100003144 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER} *** cfgtrace:dbg_cfg_trace(): request_route=[REGISTER] c=[/etc/kamailio_pcscf/route/register.cfg] l=18 a=25 n=pcscf_save_pending 3(44) DEBUG: {1 100003144 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER} ims_registrar_pcscf [save.c:386]: save_pending(): Save pending contact with AOR [sip:505030000000005@192.168.55.147:40318], proto 1, port 40318 3(44) DEBUG: {1 100003144 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER} ims_registrar_pcscf [save.c:388]: save_pending(): contact requesting to expire in 0 seconds 99(140) CRITICAL: <core> [core/pass_fd.c:284]: receive_fd(): EOF on 52 0(7) ALERT: <core> [main.c:824]: handle_sigs(): child process 43 exited by a signal 11 0(7) ALERT: <core> [main.c:828]: handle_sigs(): core was generated 0(7) INFO: <core> [main.c:851]: handle_sigs(): terminating due to SIGCHLD 4(45) INFO: {1 100003142 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER} <core> [main.c:907]: sig_usr(): signal 15 received 8(49) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 12(53) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 11(52) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 1(42) INFO: {1 100003143 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER} <core> [main.c:907]: sig_usr(): signal 15 received 15(56) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 17(58) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 23(64) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 18(59) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 16(57) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 19(60) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 7(48) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 3(44) INFO: {1 100003144 REGISTER 00000000000000000000(a)192.168.55.147 REGISTER} <core> [main.c:907]: sig_usr(): signal 15 received 10(51) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 9(50) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 13(54) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 6(47) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 5(46) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 26(67) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 29(70) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 30(71) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 31(72) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 33(74) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 32(73) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 34(75) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 36(77) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 35(76) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 21(62) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 37(78) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 14(55) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 38(79) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 22(63) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 40(81) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 27(68) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 20(61) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 41(82) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 39(80) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 43(84) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 44(85) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 45(86) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 42(83) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 50(91) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 25(66) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 24(65) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 28(69) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 48(89) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 47(88) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 52(93) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 46(87) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 49(90) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 58(99) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 91(132) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 67(108) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 96(137) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 66(107) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 92(133) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 73(114) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 64(105) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 57(98) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 87(128) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 98(139) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 81(122) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 83(124) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 53(94) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 71(112) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 75(116) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 90(131) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 76(117) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 54(95) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 77(118) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 65(106) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 80(121) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 99(140) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 59(100) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 60(101) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 61(102) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 85(126) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 63(104) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 88(129) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 51(92) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 93(134) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 84(125) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 74(115) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 94(135) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 79(120) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 55(96) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 89(130) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 56(97) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 97(138) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 95(136) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 82(123) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 72(113) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 68(109) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 69(110) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 70(111) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 78(119) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 86(127) INFO: <core> [main.c:907]: sig_usr(): signal 15 received 62(103) INFO: <core> [main.c:907]: sig_usr(): signal 15 received ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 6.1.1 (x86_64/linux) 01f496 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, DBG_QM_MALLOC, DBG_F_MALLOC, DBG_TLSF_MALLOC, 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: 01f496 ``` * **Operating System**:  ``` Distributor ID: Ubuntu Description: Ubuntu 22.04.5 LTS Release: 22.04 Codename: jammy ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4671 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4671(a)github.com>

2 6

[kamailio/kamailio] Issue with usrloc 'handle_lost_tcp' and dmq_usrloc 'usrloc_delete' (Issue #3479)
by alternatenetwork 02 May '26

02 May '26

### Description When a TLS connection is closed and handle_lost_tcp=1 the entry is deleted for usrloc. This deletion is not synced via DMQ even though usrloc_delete=1. There is also an issue on the same server if a re-registration happens right after before the timeout was supposed to expire then $var(sv_res) = 2 even though the usrloc table is empty. So it seems like the way handle_lost_tcp deletes is not deleting fully in registrar. usrloc db_mode is 0 ### Troubleshooting #### Reproduction Setup 2 servers with DMQ and close the TCP connection. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.6.1 (x86_64/linux) d8f98b flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: d8f98b compiled on 19:05:04 Aug 16 2022 with gcc 8.3.0 ``` * **Operating System**:  ``` Debian 10 ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3479 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3479(a)github.com>

3 6

[kamailio/kamailio] Issue Regex module (Issue #4660)
by itpanda2024 01 May '26

01 May '26

itpanda2024 created an issue (kamailio/kamailio#4660)  ### Description We config : loadmodule "regex.so" modparam("regex", "file", "/usr/local/etc/kamailio/regex") modparam("regex", "max_groups", 15) modparam("regex", "group_max_size", 256) modparam("regex", "pcre_caseless", 1) modparam("regex", "pcre_multiline", 1) modparam("regex", "pcre_dotall", 1) modparam("regex", "pcre_extended", 1) And check regex: if(pcre_match_group("$fU", "6")){ $sht(cache_src_num=>$dlg_var(uuid))="84"+$fU; } else if(pcre_match_group("$fU", "5")){ $sht(cache_src_num=>$dlg_var(uuid))=$fU; } else if(pcre_match_group("$fU", "4")){ $xavp(db_src_number=>$dlg_var(uuid))=$fU; $xavp(db_tmp_src_number=>$dlg_var(uuid))=$(xavp(db_src_number=>$dlg_var(uuid)){s.substr,1,0}); $sht(cache_src_num=>$dlg_var(uuid))="84"+$xavp(db_tmp_src_number=>$dlg_var(uuid)); }else if(pcre_match_group("$fU", "7")) { $sht(cache_src_num=>$dlg_var(uuid))=$fU; } And regex file : ### 0 prefix [4] ^0[35789]\d{8}$ ^020[3-9]\d{7}$ ^021\d{8}$ ^022[01256789]\d{7}$ ^023[2-9]\d{7}$ ^024\d{8}$ ^025[12456789]\d{7}$ ^026[01239]\d{7}$ ^028\d{8}$ ^029[01234679]\d{7}$ ^099\d{7}$ ^059\d{7}$ ^0169\d{8}$ ### 84 prefix [5] ^84[35789]\d{8}$ ^8420[3-9]\d{7}$ ^8421\d{8}$ ^8422[01256789]\d{7}$ ^8423[2-9]\d{7}$ ^8424\d{8}$ ^8425[12456789]\d{7}$ ^8426[01239]\d{7}$ ^8428\d{8}$ ^8429[01234679]\d{7}$ ^84169\d{8}$ ### none prefix [6] ^[35789]\d{8}$ ^20[3-9]\d{7}$ ^21\d{8}$ ^22[01256789]\d{7}$ ^23[2-9]\d{7}$ ^24\d{8}$ ^25[12456789]\d{7}$ ^26[01239]\d{7}$ ^28\d{8}$ ^29[01234679]\d{7}$ ^169\d{8}$ ## 1900 1800 [7] ^1900\d+$ ^1800\d+$ ### virtual number 84169xx [8] ^84169\d{8}$ The system start from 8h30 AM to 18h30 PM work well with regex module. But 19h00 PM have issue no memory for regex  ### Troubleshooting #### Reproduction  #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` (paste your log messages here) ``` Mar 25 19:06:44 SIP-SV01 kamailio[1439001]: 384(1439001) ERROR: {1 112666410 INVITE b44b6d93-388e-4341-bd49-0fc2d16ee62e} <core> [core/mem/q_malloc.c:463]: qm_malloc(): qm_malloc(0x7f43455c4000, 20480) called from regex: regex_mod.c: pcre2_malloc(168), module: regex; Free fragment not found! Mar 25 19:06:44 SIP-SV01 kamailio[1439001]: 384(1439001) ERROR: {1 112666410 INVITE b44b6d93-388e-4341-bd49-0fc2d16ee62e} regex [regex_mod.c:706]: ki_pcre_match_group(): matching error:'no more memory' failed[-48 #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` version: kamailio 5.8.6 (x86_64/linux) 1daebf 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: 1daebf compiled on 13:56:24 Dec 31 2025 with gcc 14.3.1 ``` (paste your output here) ``` * **Operating System**: OS : Oracle linux 10  ``` (paste your output here) ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4660 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4660(a)github.com>

3 3

[kamailio/kamailio] DB_cluster issue (Issue #4467)
by itpanda2024 01 May '26

01 May '26

itpanda2024 created an issue (kamailio/kamailio#4467)  ### Description  ### Troubleshooting #### Reproduction  #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` (paste your log messages here) ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` (paste your output here) ``` * **Operating System**:  ``` (paste your output here) ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4467 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4467(a)github.com>

4 13

[kamailio/kamailio] remove makefiles (PR #4588)
by Xenofon Karamanos 01 May '26

01 May '26

#### 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 in `doc/` subfolder, the README file is autogenerated) #### 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 #XXXX (replace XXXX with an open issue number) #### Description  You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4588 -- Commit Summary -- * src: make: Remove src/ Makefiles including lib/modules * doc: make: Remove of Makefiles * misc: make: Remove Makefiles * test: make: Remove Makefiles * utils: make: Remove Makefiles -- File Changes -- D doc/docbook/Makefile (204) D doc/docbook/Makefile.module (4) D doc/tutorials/cfg_list/Makefile (352) D doc/tutorials/cfg_list/docbook/Makefile (15) D doc/tutorials/counter_list/Makefile (348) D doc/tutorials/counter_list/docbook/Makefile (15) D doc/tutorials/presence/Makefile (4) D doc/tutorials/rpc/Makefile (4) D doc/tutorials/rpc_list/Makefile (431) D doc/tutorials/rpc_list/docbook/Makefile (15) D doc/tutorials/select_list/Makefile (353) D doc/tutorials/select_list/docbook/Makefile (15) D doc/tutorials/ser_radius/Makefile (4) D doc/tutorials/serdev/Makefile (4) D doc/tutorials/serfaq/Makefile (4) D doc/tutorials/serhowto/Makefile (4) D doc/tutorials/seruser/Makefile (4) D doc/tutorials/sip/Makefile (4) D misc/extra/vim/Makefile (12) D misc/tools/pike_top/Makefile (10) D misc/tools/protoshoot/Makefile (30) D src/Makefile (1124) D src/Makefile.cfg (17) D src/Makefile.defs (2221) D src/Makefile.dirs (19) D src/Makefile.groups (549) D src/Makefile.libs (162) D src/Makefile.modules (293) D src/Makefile.radius (55) D src/Makefile.rules (296) D src/Makefile.shared (50) D src/Makefile.sources (30) D src/Makefile.targets (41) D src/Makefile.utils (153) D src/lib/Makefile (36) D src/lib/Makefile.defs (126) D src/lib/Makefile.nonser (32) D src/lib/doc/Makefile (4) D src/lib/ims/Makefile (15) D src/lib/srdb1/Makefile (9) D src/lib/srdb1/schema/Makefile (339) D src/lib/srdb2/Makefile (9) D src/lib/srdb2/schema/Makefile (97) D src/lib/trie/Makefile (9) D src/modules/acc/Makefile (11) D src/modules/acc/doc/Makefile (4) D src/modules/acc_diameter/Makefile (11) D src/modules/acc_diameter/doc/Makefile (4) D src/modules/acc_json/Makefile (25) D src/modules/acc_json/doc/Makefile (4) D src/modules/acc_radius/Makefile (13) D src/modules/acc_radius/doc/Makefile (4) D src/modules/alias_db/Makefile (13) D src/modules/alias_db/doc/Makefile (4) D src/modules/app_jsdt/Makefile (11) D src/modules/app_jsdt/doc/Makefile (4) D src/modules/app_lua/Makefile (89) D src/modules/app_lua/doc/Makefile (4) D src/modules/app_perl/Makefile (72) D src/modules/app_perl/doc/Makefile (4) D src/modules/app_python/Makefile (40) D src/modules/app_python/doc/Makefile (4) D src/modules/app_python3/Makefile (39) D src/modules/app_python3/doc/Makefile (4) D src/modules/app_python3s/Makefile (39) D src/modules/app_python3s/doc/Makefile (4) D src/modules/app_ruby/Makefile (39) D src/modules/app_ruby/doc/Makefile (4) D src/modules/app_ruby_proc/Makefile (39) D src/modules/app_ruby_proc/doc/Makefile (4) D src/modules/async/Makefile (9) D src/modules/async/doc/Makefile (4) D src/modules/auth/Makefile (17) D src/modules/auth/doc/Makefile (4) D src/modules/auth_arnacon/Makefile (32) D src/modules/auth_arnacon/doc/Makefile (6) D src/modules/auth_db/Makefile (12) D src/modules/auth_db/doc/Makefile (4) D src/modules/auth_diameter/Makefile (13) D src/modules/auth_diameter/doc/Makefile (4) D src/modules/auth_ephemeral/Makefile (43) D src/modules/auth_ephemeral/doc/Makefile (4) D src/modules/auth_radius/Makefile (28) D src/modules/auth_radius/doc/Makefile (4) D src/modules/auth_web3/Makefile (31) D src/modules/auth_web3/doc/Makefile (4) D src/modules/auth_xkeys/Makefile (9) D src/modules/auth_xkeys/doc/Makefile (4) D src/modules/avp/Makefile (12) D src/modules/avp/doc/Makefile (4) D src/modules/avpops/Makefile (12) D src/modules/avpops/doc/Makefile (4) D src/modules/benchmark/Makefile (18) D src/modules/benchmark/doc/Makefile (4) D src/modules/blst/Makefile (9) D src/modules/blst/doc/Makefile (4) D src/modules/call_control/Makefile (13) D src/modules/call_control/doc/Makefile (4) D src/modules/call_obj/Makefile (8) D src/modules/call_obj/doc/Makefile (4) D src/modules/carrierroute/Makefile (11) D src/modules/carrierroute/doc/Makefile (4) D src/modules/cdp/Makefile (34) D src/modules/cdp/doc/Makefile (4) D src/modules/cdp_avp/Makefile (7) D src/modules/cdp_avp/doc/Makefile (4) D src/modules/cfg_db/Makefile (11) D src/modules/cfg_db/doc/Makefile (4) D src/modules/cfg_rpc/Makefile (10) D src/modules/cfg_rpc/doc/Makefile (4) D src/modules/cfgt/Makefile (11) D src/modules/cfgt/doc/Makefile (4) D src/modules/cfgutils/Makefile (13) D src/modules/cfgutils/doc/Makefile (4) D src/modules/cnxcc/Makefile (50) D src/modules/cnxcc/doc/Makefile (4) D src/modules/corex/Makefile (9) D src/modules/corex/doc/Makefile (4) D src/modules/counters/Makefile (10) D src/modules/counters/doc/Makefile (4) D src/modules/cplc/Makefile (27) D src/modules/cplc/doc/Makefile (4) D src/modules/crypto/Makefile (35) D src/modules/crypto/doc/Makefile (4) D src/modules/ctl/Makefile (16) D src/modules/ctl/doc/Makefile (4) D src/modules/db2_ldap/Makefile (18) D src/modules/db2_ldap/doc/Makefile (4) D src/modules/db2_ops/Makefile (13) D src/modules/db2_ops/doc/Makefile (4) D src/modules/db_cluster/Makefile (10) D src/modules/db_cluster/doc/Makefile (4) D src/modules/db_flatstore/Makefile (9) D src/modules/db_flatstore/doc/Makefile (4) D src/modules/db_flatstore/km_doc/Makefile (4) D src/modules/db_mongodb/Makefile (28) D src/modules/db_mongodb/doc/Makefile (4) D src/modules/db_mysql/Makefile (69) D src/modules/db_mysql/doc/Makefile (4) D src/modules/db_oracle/Makefile (22) D src/modules/db_oracle/doc/Makefile (4) D src/modules/db_postgres/Makefile (55) D src/modules/db_postgres/doc/Makefile (4) D src/modules/db_redis/Makefile (81) D src/modules/db_redis/doc/Makefile (4) D src/modules/db_sqlite/Makefile (25) D src/modules/db_sqlite/doc/Makefile (4) D src/modules/db_text/Makefile (25) D src/modules/db_text/doc/Makefile (4) D src/modules/db_unixodbc/Makefile (27) D src/modules/db_unixodbc/doc/Makefile (4) D src/modules/debugger/Makefile (9) D src/modules/debugger/doc/Makefile (4) D src/modules/dialog/Makefile (9) D src/modules/dialog/doc/Makefile (4) D src/modules/dialplan/Makefile (22) D src/modules/dialplan/doc/Makefile (4) D src/modules/dispatcher/Makefile (14) D src/modules/dispatcher/doc/Makefile (4) D src/modules/diversion/Makefile (12) D src/modules/diversion/doc/Makefile (4) D src/modules/dlgs/Makefile (9) D src/modules/dlgs/doc/Makefile (4) D src/modules/dmq/Makefile (12) D src/modules/dmq/doc/Makefile (4) D src/modules/dmq_usrloc/Makefile (5) D src/modules/dmq_usrloc/doc/Makefile (4) D src/modules/dnssec/Makefile (16) D src/modules/dnssec/doc/Makefile (3) D src/modules/domain/Makefile (12) D src/modules/domain/doc/Makefile (4) D src/modules/domainpolicy/Makefile (12) D src/modules/domainpolicy/doc/Makefile (4) D src/modules/drouting/Makefile (9) D src/modules/drouting/doc/Makefile (4) D src/modules/enum/Makefile (12) D src/modules/enum/doc/Makefile (4) D src/modules/erlang/Makefile (26) D src/modules/erlang/doc/Makefile (4) D src/modules/evapi/Makefile (31) D src/modules/evapi/doc/Makefile (4) D src/modules/evrexec/Makefile (12) D src/modules/evrexec/doc/Makefile (4) D src/modules/exec/Makefile (12) D src/modules/exec/doc/Makefile (4) D src/modules/file_out/Makefile (8) D src/modules/file_out/doc/Makefile (4) D src/modules/gcrypt/Makefile (26) D src/modules/gcrypt/doc/Makefile (4) D src/modules/geoip/Makefile (9) D src/modules/geoip/doc/Makefile (4) D src/modules/geoip2/Makefile (10) D src/modules/geoip2/doc/Makefile (4) D src/modules/group/Makefile (12) D src/modules/group/doc/Makefile (4) D src/modules/gzcompress/Makefile (23) D src/modules/gzcompress/doc/Makefile (4) D src/modules/h350/Makefile (14) D src/modules/h350/doc/Makefile (4) D src/modules/htable/Makefile (12) D src/modules/htable/doc/Makefile (4) D src/modules/http_async_client/Makefile (44) D src/modules/http_async_client/doc/Makefile (4) D src/modules/http_client/Makefile (28) D src/modules/http_client/doc/Makefile (4) D src/modules/imc/Makefile (12) D src/modules/imc/doc/Makefile (4) D src/modules/ims_auth/Makefile (34) D src/modules/ims_auth/doc/Makefile (4) D src/modules/ims_charging/Makefile (16) D src/modules/ims_charging/doc/Makefile (4) D src/modules/ims_dialog/Makefile (9) D src/modules/ims_dialog/doc/Makefile (4) D src/modules/ims_diameter_server/Makefile (16) D src/modules/ims_diameter_server/doc/Makefile (4) D src/modules/ims_icscf/Makefile (29) D src/modules/ims_icscf/doc/Makefile (4) D src/modules/ims_ipsec_pcscf/Makefile (31) D src/modules/ims_ipsec_pcscf/doc/Makefile (4) D src/modules/ims_isc/Makefile (29) D src/modules/ims_isc/doc/Makefile (4) D src/modules/ims_ocs/Makefile (16) D src/modules/ims_ocs/doc/Makefile (4) D src/modules/ims_qos/Makefile (16) D src/modules/ims_qos/doc/Makefile (4) D src/modules/ims_qos_npn/Makefile (16) D src/modules/ims_qos_npn/doc/Makefile (4) D src/modules/ims_registrar_pcscf/Makefile (35) D src/modules/ims_registrar_pcscf/doc/Makefile (4) D src/modules/ims_registrar_scscf/Makefile (35) D src/modules/ims_registrar_scscf/doc/Makefile (4) D src/modules/ims_usrloc_pcscf/Makefile (11) D src/modules/ims_usrloc_pcscf/doc/Makefile (4) D src/modules/ims_usrloc_scscf/Makefile (11) D src/modules/ims_usrloc_scscf/doc/Makefile (4) D src/modules/influxdbc/Makefile (9) D src/modules/influxdbc/doc/Makefile (4) D src/modules/ipops/Makefile (13) D src/modules/ipops/doc/Makefile (4) D src/modules/jansson/Makefile (27) D src/modules/jansson/doc/Makefile (4) D src/modules/janssonrpcc/Makefile (24) D src/modules/janssonrpcc/doc/Makefile (4) D src/modules/janssonrpcc/unit_tests/Makefile (11) D src/modules/json/Makefile (33) D src/modules/json/doc/Makefile (4) D src/modules/jsonrpcc/Makefile (35) D src/modules/jsonrpcc/doc/Makefile (4) D src/modules/jsonrpcs/Makefile (11) D src/modules/jsonrpcs/doc/Makefile (4) D src/modules/jwt/Makefile (25) D src/modules/jwt/doc/Makefile (4) D src/modules/kafka/Makefile (23) D src/modules/kafka/doc/Makefile (4) D src/modules/kazoo/Makefile (39) D src/modules/kazoo/doc/Makefile (4) D src/modules/keepalive/Makefile (13) D src/modules/keepalive/doc/Makefile (4) D src/modules/kemix/Makefile (9) D src/modules/kemix/doc/Makefile (4) D src/modules/kex/Makefile (12) D src/modules/kex/doc/Makefile (4) D src/modules/lcr/Makefile (26) D src/modules/lcr/doc/Makefile (4) D src/modules/ldap/Makefile (24) D src/modules/ldap/doc/Makefile (4) D src/modules/log_custom/Makefile (8) D src/modules/log_custom/doc/Makefile (4) D src/modules/log_systemd/Makefile (23) D src/modules/log_systemd/doc/Makefile (4) D src/modules/lost/Makefile (43) D src/modules/lost/doc/Makefile (4) D src/modules/lrkproxy/Makefile (14) D src/modules/lrkproxy/doc/Makefile (4) D src/modules/lwsc/Makefile (25) D src/modules/lwsc/doc/Makefile (4) D src/modules/mangler/Makefile (12) D src/modules/mangler/doc/Makefile (4) D src/modules/math/Makefile (9) D src/modules/math/doc/Makefile (4) D src/modules/matrix/Makefile (8) D src/modules/matrix/doc/Makefile (4) D src/modules/maxfwd/Makefile (12) D src/modules/maxfwd/doc/Makefile (4) D src/modules/mediaproxy/Makefile (13) D src/modules/mediaproxy/doc/Makefile (4) D src/modules/memcached/Makefile (21) D src/modules/memcached/doc/Makefile (4) D src/modules/microhttpd/Makefile (23) D src/modules/microhttpd/doc/Makefile (4) D src/modules/misc_radius/Makefile (10) D src/modules/misc_radius/doc/Makefile (4) D src/modules/misctest/Makefile (12) D src/modules/misctest/doc/Makefile (4) D src/modules/mohqueue/Makefile (12) D src/modules/mohqueue/doc/Makefile (4) D src/modules/mqtt/Makefile (42) D src/modules/mqtt/doc/Makefile (4) D src/modules/mqueue/Makefile (9) D src/modules/mqueue/doc/Makefile (4) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4588.patch https://github.com/kamailio/kamailio/pull/4588.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4588 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4588(a)github.com>

6 24

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev March 2026