sr-users

sr-users@lists.kamailio.org

35 participants
37509 discussions

PRACK Retransmission and 408 Timeout Issue in Kamailio
by 高秉寬 26 Feb '25

26 Feb '25

Dear Kamailio Developers, I am using Kamailio as a SIP server to facilitate a phone call, but I am encountering an issue where the call cannot be established due to Kamailio sending a 408 Request Timeout to the caller. Issue Details: - A (Caller) sends an initial INVITE to Kamailio, which then forwards it to B (Callee). The INVITE contains the following Supported header: Supported: timer,100rel,replaces,precondition,from-change,histinfo,tdialog I suspect the *precondition* option may be relevant to the issue. - *B* responds with a *183 Session Progress* message, which includes: Require: 100rel,precondition Kamailio correctly forwards this response to *A.* - *A* then sends a *PRACK* request to Kamailio. However, this request contains: Require: sec-agree Supported: timer Notably, *precondition* is absent from both the *Require* and *Supported* headers. - Kamailio forwards this *PRACK* to *B*, and *B* responds with *200 OK*, including: Supported: 100rel,from-change,tdialog - However, Kamailio does not seem to acknowledge *B's 200 OK* and instead *keeps retransmitting the PRACK* to *B*. B responds with *200 OK* again, but the cycle repeats. - After three retransmissions of *PRACK*, Kamailio eventually sends *408 Request Timeout* to *A*, leading *A* to send a *CANCEL* request. Device Used: - *Caller (A):* Asus ROG Phone 5 - *Callee (B):* Asus ROG Phone 6 Both are commercially available mobile phones. Possible Cause: According to *3GPP TS 24.229, Subclause 5.1.3.1*, If the received response with an SDP body includes a Require header with > the "precondition" option-tag, the originating UE shall include a Require > header with the "precondition" option-tag in responses with an SDP body to > subsequent requests that include an SDP body and include the "precondition" > option-tag in either the Supported or Require header field received > in-dialog. In this case: - The *183 Session Progress* from *B* contains Require: *precondition*. - The subsequent *PRACK* from *A* does not include *precondition* in either *Require* or *Supported*. Could this mismatch be the reason Kamailio keeps retransmitting *PRACK* and ignoring *B's 200 OK*? Or could there be another factor causing Kamailio to behave this way? If additional details are needed, please let me know. Best regards, Ping Kuan Kao

3 4

Issue with registrations
by Anthony Ford 26 Feb '25

26 Feb '25

Hi Version = 5.6.0-dev0 We are seeking help to resolve an issue with registering devices to 3CX (All 3CX servers, have tried 8 different ones) . all the auth info including passwords etc are identical on the 3cx servers. We use Kamailio to register mobile sim cards to 3rd party sip servers i.e. 3CX. We send the normal Username, server addresses and auth details but are experiencing failures with 3CX rejecting the registration and return Proxy Auth failure 407. We have noticed in the pcaps from both sides that the expire value is changing from 180 as an example to 0. As an example In the uac reg_dump the values are : l_uuid: +447529135850<tel:+447529135850> l_username: +447529135850<tel:+447529135850> l_domain: sbc-mt.asim.apalo.io<http://sbc-mt.asim.apalo.io/>;transport=udp r_username: 1001 r_domain: egte.3cx.uk<http://egte.3cx.uk/> realm: <null string> auth_username: FdlHDC1IvA auth_password: extracted auth_ha1: none auth_proxy: sip:egte.3cx.uk:5060 expires: 60 flags: 0 diff_expires: -1738853736 timer_expires: 0 reg_init: 1738850836 reg_delay: 0 contact_addr: k01.asim.apalo.io<http://k01.asim.apalo.io/>;transport=tcp socket: <null string> [cid:image001.png@01DB86AB.2701F190] [cid:image002.png@01DB86AB.2701F190] [cid:image003.png@01DB86AB.2701F190] Looking forward to hearing from you. Many thanks Tony Ford

3 3

REG_MAR_REPLY never get executed
by stinktohighheaven＠gmail.com 26 Feb '25

26 Feb '25

Using Kamailio v5.3, based on the example for scscf found here: https://github.com/kamailio/kamailio/blob/master/misc/examples/ims/scscf/ka… after calling ims_www_challenge("REG_MAR_REPLY", "$var(realm)", "$var(alg)"); the control never goes to REG_MAR_REPLY route block, but it goes to the start of the requet_route block. here is the kamailio.cfg script: request_route { ....... /* Handle Registrations */ if (is_method("REGISTER")) { route(REGISTER); exit; } ...... } /** * Handling of REGISTER requests */ route[REGISTER] { ...... #!ifdef WITH_AUTH if (!ims_www_authenticate("$var(realm)")) { #!else if ($var(alg) == "3GPP-Digest" && !ims_www_authenticate("$var(realm)")) { #!endif if ($? == -2) { send_reply("403", "Authentication Failed"); exit; } else if ($? == -3) { send_reply("400", "Bad Request"); exit; } else if ($? == -9) { xdbg("Authentication re-sync requested\n"); ims_www_resync_auth("REGISTER_RESYNC_REPLY", "$var(realm)"); exit; } else { /* user has not been authenticated. Lets send a challenge via 401 Unauthorized */ xdbg("About to challenge! auth_ims\n"); ims_www_challenge("REG_MAR_REPLY", "$var(realm)", "$var(alg)"); exit; } } else { xdbg("Auth succeeded\n"); /* We need to check if this user is registered or not */ if (!impu_registered("location")) { save("PRE_REGISTER_SAR_REPLY", "location"); exit; } else { isc_match_filter_reg("1", "location"); save("REGISTER_SAR_REPLY", "location"); exit; } } } } /** * Handling of REGISTER MAR replies */ route[REG_MAR_REPLY] { xlog("L_DBG","maa_return code is $avp(s:maa_return_code)\n"); /* this is async so to know status we have to check the reply avp */ switch ($avp(s:maa_return_code)) { case 1: /* success */ xdbg("MAR success - 401/407 response sent from module\n"); break; case -1: /* failure */ xerr("MAR failure - error response sent from module\n"); break; case -2: /* error */ xerr("MAR error - sending error response now\n"); send_reply("503", "MAR failed"); break; default: xerr("Unknown return code from MAR, value is [$avp(s:maa_return_code)]\n"); send_reply("503", "Unknown response code from MAR"); break; } exit; } and here's the log: 12(18) ERROR: *** cfgtrace:request_route=[REGISTER] c=[/usr/local/etc/kamailio/kamailio.cfg] l=757 a=27 n=ims_www_challenge 12(18) DEBUG: ims_auth [authorize.c:293]: challenge(): Looking for route block [REG_MAR_REPLY] 12(18) INFO: ims_auth [cxdx_mar.c:79]: create_return_code(): created AVP successfully : [maa_return_code] - [-2] 12(18) DEBUG: ims_auth [authorize.c:317]: challenge(): Need to challenge for realm [ims.mnc071.mcc432.3gppnetwork.org] 12(18) DEBUG: ims_auth [authorize.c:324]: challenge(): Checking if REGISTER is authorized for realm [ims.mnc071.mcc432.3gppnetwork.org]... 12(18) DEBUG: ims_auth [authorize.c:1449]: get_auth_userdata(): Searching auth_userdata for IMPU sip:432710000010044@ims.mnc071.mcc432.3gppnetwork.org (Hash 425) 12(18) DEBUG: ims_auth [authorize.c:460]: challenge(): Suspending SIP TM transaction 12(18) DEBUG: ims_auth [authorize.c:1529]: multimedia_auth_request(): Sending MAR 12(18) DEBUG: ims_auth [cxdx_mar.c:574]: cxdx_send_mar(): Successfully sent async diameter 70(76) INFO: ims_auth [cxdx_avp.c:137]: cxdx_get_avp(): cxdx_get_experimental_result_code: Failed finding avp (avp_code = 297, vendor_id = 0) 70(76) DEBUG: ims_auth [authorize.c:1303]: new_auth_vector(): new auth-vector with ck [d2deb48b5b3b614ba9112396e3c036fe] with status 0 70(76) DEBUG: ims_auth [authorize.c:1560]: pack_challenge(): setting QOP str used is [, qop="auth"] 70(76) DEBUG: ims_auth [authorize.c:1562]: pack_challenge(): QOP str used is [, qop="auth"] 70(76) DEBUG: ims_auth [authorize.c:1449]: get_auth_userdata(): Searching auth_userdata for IMPU sip:432710000010044@ims.mnc071.mcc432.3gppnetwork.org (Hash 425) 70(76) DEBUG: ims_auth [authorize.c:1458]: get_auth_userdata(): Found auth_userdata 70(76) DEBUG: ims_auth [authorize.c:1682]: add_auth_vector(): Adding auth_vector (status 1) for IMPU sip:432710000010044@ims.mnc071.mcc432.3gppnetwork.org / IMPI 432710000010044(a)ims.mnc071.mcc432.3gppnetwork.org (Hash 425) 70(76) DEBUG: ims_auth [cxdx_mar.c:486]: async_cdp_callback(): DBG:UAR Async CDP callback: ... Done resuming transaction 70(76) INFO: ims_auth [cxdx_mar.c:79]: create_return_code(): created AVP successfully : [maa_return_code] - [1] 70(76) ERROR: tm [t_suspend.c:197]: t_continue_helper(): active transaction not found 70(76) DEBUG: ims_auth [cxdx_mar.c:87]: free_saved_transaction_data(): Freeing saved transaction data: async 11(17) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=380 a=5 n=route

4 8

tm stats on prometheus
by Alexis Fidalgo 25 Feb '25

25 Feb '25

Hello all, i found that tm stats (kamcmd tm.stats) are not present in the response of xhttp_prom (prometheus), so in new configurations that we applied, we have no information/stats on reply codes. Is there a way to add this information to the xhttp_prom response? thanks in advance. regards

2 4

debug memory usage by AVP
by Sergey Safarov 25 Feb '25

25 Feb '25

In the "kamcmd mod.stats all shm" output i see to big value for "create_avp" metric Module: core { tcpconn_new(1205): 35104 counters_prefork_init(211): 61952 create_avp(178): 20737248 cfg_clone_str(132): 304 cfg_shmize(221): 1248 main_loop(1381): 16 Is possible to print AVP list and APV content without kamailio config change and restart?

1 0

Kamailio uses an ephemeral IP port instead of the port defined in $fs
by Leonid Fainshtein 24 Feb '25

24 Feb '25

Hi, I am using Kamailio v.5.8.4 on Ubuntu 24.04, kernel 6.8.0-51-generic In the configuration script I explicitly set $fs="udp:adrr:port". In normal situations, it works properly and I see that the UDP SIP requests are sent from the requested IP and port. Due to some reasons, free space on the server root filesystem was exhausted. I cleaned up the file system and everything looked good except the fact that Kamailio started to send messages from ephemeral IP ports instead of the port defined in $fs. Restart of Kamailio didn't solve the problem. But the server reboot fixed the issue. I don't understand how the lack of free disk space can cause such a problem and I'm afraid that there is another reason that I am missing. Has anybody seen such a problem? Best regards, Leonid

3 3

Outdated location information on deleted registrations
by Mathias Schneuwly 19 Feb '25

19 Feb '25

Hi I'm using Kamailio 5.8.4 and the python KEMI module. When I move the registration from one device to another, I can see for a while two entries with 'kamctl ul show' where the Expires parameter of the "old" registration is set to "deleted" and the "new" registration shows the seconds until the registration expires. "Address": "sips:200101@10.0.1.130:42323 ;transport=tls", "Expires": "deleted", -- "Address": "sips:200101@10.0.1.129:56374 ;transport=tls", "Expires": 3600, So far so good. When I try to fetch the actual registration address using "registrar.reg_fetch_contacts" or "registrar.lookup_xavp", I'm always getting the "old" deleted registration address instead of the new address as long as the deleted record is not removed. Feb 18 10:05:51 ttel /usr/sbin/kamailio[2356327]: WARNING: {1 511 INVITE 952600514-5060-52(a)BA.A.C.BCI} <core> [core/kemi.c:157]: sr_kemi_core_log(): reg_fetch_contacts: sips:200101@10.0.1.130:42323;transport=tls Feb 18 10:05:51 ttel /usr/sbin/kamailio[2356327]: WARNING: {1 511 INVITE 952600514-5060-52(a)BA.A.C.BCI} <core> [core/kemi.c:157]: sr_kemi_core_log(): lookup_xavp: aor=200101, uri=sips:200101@10.0.1.130:42323;transport=tls, socket=tls:10.0.1.1:5061, dsturi=None I also see that the database is only updated after the deleted entry is removed. Until then, the database still contains the old address. Btw, I'm using "modparam("usrloc", "db_mode", 2)", which would explain the delayed persisting into the database. 62|uloc-67b44aae-23f48e-2|200101||sips:200101@10.0.1.130:42323 ;transport=tls|||2460724.91858218|-1.0|482845299-5060-1(a)BA.A.B.BDA|2002|2460724.87691551|0|0|Grandstream GXV3350 1.0.3.52|tls:10.0.1.1:5061 |7135|<urn:uuid:00000000-0000-1000-8000-C074AD188038>|1|0|52|0|16 I'm asking myself whether the behavior is correct that "registrar.reg_fetch_contacts" and "registrar.lookup_xavp" are returning the deleted information instead of the "new" registration information? If yes, is there another way how I could get the "new" registration information? I'm not really interested in the old outdated information... Best regards Mathias

2 2

Info: maintenance work for kamailio.org server on Tuesday, Feb 18, 2025
by Daniel-Constantin Mierla 18 Feb '25

18 Feb '25

Hello, there is a planned mainenance work on the infrastructure for the server hosting kamailio.org services (among them: the main website, wiki, mailing lists) on next week, Tuesday, February 18, 2025, to start about 10:00am Berlin time (CET). Expect some intervals of unavailability, we hope they will be short and most of them not noticeable for the majority accessing these services during the day. Once the work is finished, an announcement will be sent out. The apt repository, github project and the matrix chat channels should not be affected, they can be accessed as usual and can be used a backup communication channels if anyone observes something that has to be addressed. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio Advanced Training, March 24-28, 2025 -- asipto.com Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com

1 2

Asterisk ConfBridge behind Kamailio+Rtpengine
by Rahul mm 18 Feb '25

18 Feb '25

Dear all, Thanks for the amazing product ! I’m trying my hands on a scenario involving Asterisk for video_sfu and a bunch of webrtc and sip clients. The condition is that every call must essentially be a conference call for the participants to add more dynamically. I front ended asterisk with Kamailio and RTPEngine for ssl offloading, load balancing, and registrations. So when one user is present in the conference (his invite SDP containing one audio and one video line) i get local video and MoH back, but when another user joins in and a re-invite is send from asterisk containing two video lines - one for the sendrecv and other for send only, rtpengine doesn’t process the sendonly video line - keeps it as is RTP/AVP instead of making it *UDP/TLS/RTP/SAVPF.* *Is there a way to achieve that? or I’m on the wrong path ?* BR, RM

1 0

Kamailio - asterisk registration issue & transparent proxy
by Enzo Damato 17 Feb '25

17 Feb '25

Hi. I'm working on setting up kamailio as a load balancer for some asterisk instances. I've build a configuration that is working for the most part, but I am encountering issues with calls from the asterisk instances to users who's registrations were processed through the kamailio instance. When these users register, asterisk saves thier AOR as the address of the kamailio instance, and then subsequently tires to send invites to kamailio, instead of to the UAC. Since kamailio just proxied the registration, without actually registering the user, it doesn't know what to do with the invite, and the call fails. I would like to configure kamailio to rewrite the sip requests so that all traffic appears to be coming from the end user, rather than from the kamailio instance, essentially making the proxy transparent. Is this possible? Thank you, Enzo Damato

4 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users