May 2024 - sr-users - kamailio.org

VoLTE/IMS third party registration issues
by ruben.iniguez＠vodafone.com 23 May '24

23 May '24

Checking Kamailio in a VoLTE environment we are finding issues to make it work. First issues arise when getting AS to extract the required info from third party registration, primarily IMPUs. Third party registration is sent to AS with IMPI in To header, preventing the AS from extracting the IMPU from the most obvious place, the To header, according to 3GPP 24.229: "Notification of Application Servers about registration status [...] the To header field, which shall contain a non-barred public user identity belonging to the service profile of the processed Filter Criteria. It may be either a public user identity as contained in the REGISTER request received from the UE or one of the implicitly registered public user identities in the service profile, as configured by the operator;" On the other hand, the third party registration can only embed in its body either the original request or the original response but not both (notice mutually exclusive "else if" statements in third_party_reg.c). Both are needed to extract Feature-Caps (from original request) and IMPUs (for instance from P-Associated-URI in original response). Therefore to extract that info the AS should subscribe to the reg info in S-CSCF, but such SUBSCRIBE is rejected with 403. From Registrar IMS SCSCF documenation it looks like this is not supported: "This function checks to see that a SUBSCRIBE request is authorised to subscribe to the particular identity. Only 3 entities can subscribe: The user agent to its own state The P-CSCF specified in the path header for that user Application Server (AS) not yet implemented" Therefore question to the community is how these limitations are overcome in existing VoLTE deployments with Kamailio? Any advice?

1 0

Kamailio IPSec module
by H Yavari 23 May '24

23 May '24

Hi all, I was reviewing the `ims_ipsec_pcscf` code and noticed that this module creates a pool of sockets using different ports (ipsec_max_connections). I'm unclear on the necessity of this approach. Can't we simply create one server listener and one client listener to handle all UE connections? If this is feasible, is there still a need to create the pool at startup? I'm curious if this is due to an architectural limitation or if the IPSec module can be modified to replace the current implementation with a more efficient one. Thank you for your insights. Best regards,Hossein

3 5

S-CSCF SiFC support
by ruben.iniguez＠vodafone.com 22 May '24

22 May '24

Hello In the context of an IMS deployment, does anybody know if Shared iFC mechanism is supported in Kamailio? I don't see configuration options for it, and just wanted to confirm if only regular iFCs (residing on HSS) are supported. Thank you

1 0

Assistance Required for VoNR Setup with Version 5.8.1
by venkateshcoff＠gmail.com 22 May '24

22 May '24

Hi, I am trying to set up VoNR with version 5.8.1, but I cannot find the configuration information and documentation anywhere. Has anyone tested a VoNR call? Thanks.

1 0

usrloc: keepalives not being sent to UDP endpoints for a very long time
by luke＠primevox.net 21 May '24

21 May '24

We've noticed an issue with UDP endpoints and the usrloc module not sending keepalive packets to them for a long time. Eventually, usrloc will begin doing it, but sometimes it's anywhere between 10 minutes and multiple hours before the endpoint starts receiving an OPTIONS packet. TCP and TLS endpoints do not have this issue - they being receiving OPTIONS after registration + ka_timeout elapsed. Has anyone else seen this? It can be very easily seen with a pcap on a device registering via UDP.

1 0

A question about Db_flatstore Module in Kamailio
by فرزانه سلطان زاده 20 May '24

20 May '24

Hi, Hope to find you well, I have a question about the 'db_flatstore' module in Kamailio. Here's my script for log rotation: for f in acc_cdrs_*.log; do mv -- "$f" "${f%.log}.temp" done docker exec -it pcscf kamcmd flatstore.k_rotate rm *.temp I want to know if the kamcmd command is blocking and the files can be removed after that or if I should wait for it to be done before removing the renamed files. Regards, Farzaneh

3 2

Kamailio multidomain IMS
by Valentin Christoph 20 May '24

20 May '24

Dear IMS enthusiasts :-) Has anyone experience with Kamailio IMS (CSCF) setups, where users with different domain names can be registered at one and the same S-CSCF? Is this feasible at all? I mean one IMS for users <user>@ims1.example.com, <user>@ims2.example.com, <user>@ims3.example.com,........ in one and the same S-CSCF, I-CSCF, P-CSCF. Thanks, Christoph

2 1

q_malloc.c:520 WARNINGs
by Joel Serrano 20 May '24

20 May '24

Hi, Does anyone know what this WARNING means or how to fix it? 2024-03-09T00:39:15.406674-05:00 csbc03 csbc[33024]: WARNING: {1 1 INVITE CALL-ID} <core> [core/mem/q_malloc.c:520]: qm_free(): WARNING: free(0) called from dialplan: dp_db.c: pcre2_free(206) 2024-03-09T00:39:15.406823-05:00 csbc03 csbc[33024]: WARNING: {1 1 INVITE CALL-ID} <core> [core/mem/q_malloc.c:520]: qm_free(): WARNING: free(0) called from dialplan: dp_db.c: pcre2_free(206) 2024-03-09T00:39:15.406973-05:00 csbc03 csbc[33024]: WARNING: {1 1 INVITE CALL-ID} <core> [core/mem/q_malloc.c:520]: qm_free(): WARNING: free(0) called from dialplan: dp_db.c: pcre2_free(206) 2024-03-09T00:39:15.407089-05:00 csbc03 csbc[33024]: WARNING: {1 1 INVITE CALL-ID} <core> [core/mem/q_malloc.c:520]: qm_free(): WARNING: free(0) called from dialplan: dp_db.c: pcre2_free(206) 2024-03-09T00:39:15.407178-05:00 csbc03 csbc[33024]: WARNING: {1 1 INVITE CALL-ID} <core> [core/mem/q_malloc.c:520]: qm_free(): WARNING: free(0) called from dialplan: dp_db.c: pcre2_free(206) 2024-03-09T00:39:15.407278-05:00 csbc03 csbc[33024]: WARNING: {1 1 INVITE CALL-ID} <core> [core/mem/q_malloc.c:520]: qm_free(): WARNING: free(0) called from dialplan: dp_db.c: pcre2_free(206) 2024-03-09T00:39:15.407375-05:00 csbc03 csbc[33024]: WARNING: {1 1 INVITE CALL-ID} <core> [core/mem/q_malloc.c:520]: qm_free(): WARNING: free(0) called from dialplan: dp_db.c: pcre2_free(206) It happens after running dp_translate(). These are my settings: debug=L_DBG debug=L_NOTICE memdbg=L_INFO memlog=L_INFO corelog=L_ERR mem_summary=12 log_stderror=no log_facility=LOG_LOCAL0 log_name="csbc" log_prefix="{$mt $hdr(CSeq) $ci} " mem_join=1 Any ideas? Thanks, Joel.

2 5

tm.t_uac_wait ACK does not have Max-Forwards header
by Juha Heinanen 20 May '24

20 May '24

Kamailio sends INVITE by tm.t_uac_wait RPC command: INVITE sip:test-0x55e7f1f78e70@192.168.187.215:5022 SIP/2.0 Via: SIP/2.0/UDP 192.168.187.215;branch=z9hG4bK6cf1.f1d087d6000000000000000000000000.0 To: <sip:test@test.tutpro.com> From: <sip:click2dial@test.tutpro.com>;tag=2dd3d4389fe3d66c5cb97dc370ab7d7b-9c5a2a58 CSeq: 1 INVITE Call-ID: 6649e78355ac2(a)test.tutpro.com Content-Length: 131 User-Agent: OpenSIPg SIP Proxy (5.9.0-0b01 (x86_64/linux)) Max-Forwards: 10 Contact: <sip:click2dial@192.168.187.215:5060> Content-Type: application/sdp .. sdp omitted UAS accepts the INVITE: SIP/2.0 200 Answering Via: SIP/2.0/UDP 192.168.187.215;branch=z9hG4bK6cf1.f1d087d6000000000000000000000000.0 To: <sip:test@test.tutpro.com>;tag=a3302e2a0898de3e From: <sip:click2dial@test.tutpro.com>;tag=2dd3d4389fe3d66c5cb97dc370ab7d7b-9c5a2a58 CSeq: 1 INVITE Call-ID: 6649e78355ac2(a)test.tutpro.com Server: baresip v3.12.0 (x86_64/Linux) Contact: <sip:test-0x55e7f1f78e70@192.168.187.215:5022> Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,NOTIFY,SUBSCRIBE,INFO,MESSAGE,UPDATE,REFER Supported: gruu,replaces,norefersub Content-Type: application/sdp Content-Length: 239 .. sdp omitted After receiving the response, Kamailio automatically sends ACK: ACK sip:test-0x55e7f1f78e70@192.168.187.215:5022 SIP/2.0 Via: SIP/2.0/UDP 192.168.187.215;branch=z9hG4bK6cf1.f1d087d6000000000000000000000000.0 From: <sip:click2dial@test.tutpro.com>;tag=2dd3d4389fe3d66c5cb97dc370ab7d7b-9c5a2a58 Call-ID: 6649e78355ac2(a)test.tutpro.com To: <sip:test@test.tutpro.com>;tag=a3302e2a0898de3e CSeq: 1 ACK User-Agent: OpenSIPg SIP Proxy (5.9.0-0b01 (x86_64/linux)) Content-Length: 0 The problem is that Max-Forwards header is missing from the ACK. Should I have something in config file to add it or is this a bug? -- Juha

1 3

Segfault on startup when using TLS in kamailio 5.7.4
by stefanr＠wave.com 17 May '24

17 May '24

Hi there, We are encountering consistent segfaults after rebooting our Kamailio instance with incoming traffic, specifically when using Kamailio 5.7.4. We think this issue did not occur with version 5.7.2, so it seems to have been introduced in either 5.7.3 or 5.7.4. Due to team bandwidth constraints and the potential impact on production traffic, we don't want to spend time on trying to reproduce the issue. So we have decided to downgrade to 5.6.4, which we confirmed to be stable. (Probably 5.7.2 would be too - but we didn't try). Unfortunately, our logging was only set to WARNING level, and we did not capture a core dump, so we cannot provide additional details beyond the following logs: This was with tcp_reuse_ports=yes: 2024-05-17T15:42:55.582475541Z Listening on 2024-05-17T15:42:55.582512370Z [redacted] 2024-05-17T15:42:55.582538161Z tls: 10.X.X.X:5061 advertise Y.Y.Y:5061 2024-05-17T15:42:55.582543750Z Aliases: 2024-05-17T15:42:55.582549081Z tls: [redacted]:5061 2024-05-17T15:42:55.582574890Z 2024-05-17T15:42:55.587876630Z 0(1) WARNING: tls [tls_init.c:978]: tls_h_mod_init_f(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 18874368 and 9437184 bytes 2024-05-17T15:42:55.703927049Z 35(41) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 23 2024-05-17T15:42:55.703972029Z 0(1) ALERT: <core> [main.c:791]: handle_sigs(): child process 15 exited by a signal 11 2024-05-17T15:42:55.703978409Z 0(1) ALERT: <core> [main.c:795]: handle_sigs(): core was generated 2024-05-17T15:42:55.705049839Z 35(41) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 17 2024-05-17T15:42:55.705074209Z 35(41) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 21 2024-05-17T15:42:55.705081209Z 35(41) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 22 2024-05-17T15:42:55.705085879Z 35(41) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 20 2024-05-17T15:42:55.705090319Z 35(41) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 18 2024-05-17T15:42:55.705094649Z 35(41) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 19 2024-05-17T15:42:55.705098879Z 35(41) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 16 2024-05-17T15:42:55.705207399Z 35(41) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 15 2024-05-17T15:42:55.705459439Z 35(41) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 27 Without tcp_reuse_ports=yes, the segfault was always preceded by the following line if any existing TLS connections were stuck in TIME_WAIT: 2024-05-16T19:18:51.654447639Z 9(14) WARNING: {1 1 INVITE XXX(a)0.0.0.0} <core> [core/tcp_main.c:1301]: find_listening_sock_info(): binding to source address 10.X.X>X:5061 failed: Address already in use [98] 2024-05-16T19:18:51.746994728Z 0(1) ALERT: <core> [main.c:791]: handle_sigs(): child process 14 exited by a signal 11 When the server wasn't handling any traffic, the issue didn't occur even in 5.7.4. Does anyone have any insights or suggestions on how to address this issue? Kind regards Stefan

2 2