sr-users December 2024

sr-users@lists.kamailio.org

27 participants
34 discussions

[print_dset(): no r-uri or branches] when working with async worker
by elhar.mohamed＠gmail.com 18 Dec '24

18 Dec '24

Hello, I'm getting this warning WARNING: <core> [core/dset.c:690]: print_dset(): no r-uri or branches when working with async worker. here is below the code used: request_route { if (is_method("INVITE")) { append_to_reply("Contact: <sip:+1234;myparam=test@$si:$sp>\r\n"); send_reply("302", "Moved Temporarily"); exit; } } Can you please help?

2 2

Multiple Branches and 3xx Status Codes
by Christian Berger 17 Dec '24

17 Dec '24

Hi, we have the following situation: Multiple UAs are subscribed to the proxy and get INVITEd via parallel forking. Now one of the UAs sends us a 302 status, we would like to handle this like a failure. So we'd like to CANCEL all the other branches, and forward the 302 status to the original INVITE. We have tried t_reply("302", "$T(reply_reason)") in the response, which almost solves this, however we cannot pass the required headers form the 302 response in it. BTW, could there have been a change in the default behavior of Kamailio? We think it used to "just work" in the past. Thank you very much Christian Berger -- Christian Berger - berger(a)sipgate.de Telefon: +49 (0)211-63 55 55-0 Telefax: +49 (0)211-63 55 55-22 sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.co.uk

3 3

Development for v6.0.x is frozen
by Daniel-Constantin Mierla 17 Dec '24

17 Dec '24

Hello, the formal notification that the development for the next major version 6.0.0 is now frozen. The focus has to be on testing the master branch. Also, the master branch should not get commits with new features till the branch 6.0 is created, expected to happen in 2-4 weeks, a matter of how testing goes on. Meanwhile, the commits with new features in the C code can be pushed to personal branches, new pull requests can still be done, but they will be merged after branching 6.0. Can still be done commits with documentation improvements, enhancements to related tools (e.g., kamctl, kamcmd), merging exiting pull requests at this moment, exporting missing KEMI functions and completing the functionality of the new modules added for 6.0. Once the branch 6.0 is created, new features can be pushed again to master branch as usual. From that moment, the v6.0.0 should be out very soon, time used for further testing but also preparing the release of packages. If someone is not sure if a commit brings a new feature, just make a pull request and it can be discussed there on github portal or via sr-dev mailing list. A summary of what is new in upcoming 6.0 is going to be built at: * https://www.kamailio.org/wikidocs/features/new-in-6.0.x/ Upgrade guidelines will be collected at: * https://www.kamailio.org/wikidocs/install/upgrade/5.8.x-to-6.0.0/ Everyone is more than welcome to contribute to the above wiki pages, especially to the upgrade guidelines, to help everyone else during the migration process from v5.8.x to 6.0.x. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

1 0

Freezing development for 6.0.x series
by Daniel-Constantin Mierla 16 Dec '24

16 Dec '24

Hello, I propose to aim freezing the development for 6.0.x series at the end of the 16th of December 2024 (Monday). New features that one wants to get in this release series have to be pushed to git repository or pull requests made for them. Afterwards usually follows a 4-6 weeks of testing till the first release 6.0.0. Unfreezing will happen earlier, after the first weeks of testing when the 6.0 branch will be created. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

1 1

ims_diameter_server: $diameter_response PV is null in the event_route[diameter:response]
by Grotti, Daniel 15 Dec '24

15 Dec '24

Hi list, I'm using kamailio 5.8 and playing with the ims_diameter_server module, by sending an async diameter request and trying to catch the reponse. Following the documentation, I'm sending the request with: route[SEND_ACR] { route(PREPARE_ACR); diameter_request_async("3", "271", "$var(json_acr)"); } route[PREPARE_ACR] { # here I build the AVP list in JSON $var(json_acr) = "[{"avpCode":277,"vendorId":0,"Flags":64,"int32":0},{...},{...}]"; } event_route[diameter:response] { xlog("Reply to diameter request is: '$diameter_response'\n"); } The ACR request is successfully sent and the the server is replying with ACA. The list of AVP are properly parsed, but when I enter the event_route to print the response, I get the $diameter_response = 'null': 2024-12-11T10:52:39.192951872+00:00 stderr F 11(19) DEBUG: cdp [worker.c:374]: worker_process(): worker_process(): [2] got task Q(2/2) 2024-12-11T10:52:39.193026280+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP((nil) < 0x7ff827633810 >0x7ff8276338c0);code=263,flags=40; 2024-12-11T10:52:39.193026280+00:00 stderr F DataType=1;VendorID=0;DataLen=52; 2024-12-11T10:52:39.193026280+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP(0x7ff827633810 < 0x7ff8276338c0 >0x7ff827633970);code=268,flags=40; 2024-12-11T10:52:39.193026280+00:00 stderr F DataType=3;VendorID=0;DataLen=4; 2024-12-11T10:52:39.193026280+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP(0x7ff8276338c0 < 0x7ff827633970 >0x7ff827633a20);code=264,flags=40; 2024-12-11T10:52:39.193026280+00:00 stderr F DataType=1;VendorID=0;DataLen=37; 2024-12-11T10:52:39.193026280+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP(0x7ff827633970 < 0x7ff827633a20 >0x7ff8276340b0);code=296,flags=40; 2024-12-11T10:52:39.193026280+00:00 stderr F DataType=1;VendorID=0;DataLen=33; 2024-12-11T10:52:39.193124627+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP(0x7ff827633a20 < 0x7ff8276340b0 >0x7ff827634160);code=259,flags=40; 2024-12-11T10:52:39.193124627+00:00 stderr F DataType=0;VendorID=0;DataLen=4; 2024-12-11T10:52:39.193286132+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP(0x7ff8276340b0 < 0x7ff827634160 >0x7ff827634210);code=480,flags=40; 2024-12-11T10:52:39.193286132+00:00 stderr F DataType=0;VendorID=0;DataLen=4; 2024-12-11T10:52:39.193286132+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP(0x7ff827634160 < 0x7ff827634210 >0x7ff8276342c0);code=485,flags=40; 2024-12-11T10:52:39.193286132+00:00 stderr F DataType=0;VendorID=0;DataLen=4; 2024-12-11T10:52:39.193286132+00:00 stderr F 11(19) DEBUG: ims_diameter_server [avp_helper.c:60]: avp2json(): AVP(0x7ff827634210 < 0x7ff8276342c0 >(nil));code=85,flags=40; 2024-12-11T10:52:39.193286132+00:00 stderr F DataType=0;VendorID=0;DataLen=4; 2024-12-11T10:52:39.193612877+00:00 stderr F 11(19) INFO: <script>: [event_route]: Reply to diameter request is: '<null>' Is there something I miss to set/configure? Thanks, Daniel Daniel Grotti Development Team Leader, Private 5G daniel.grotti(a)hpe.com<mailto:daniel.grotti@hpe.com> Hewlett Packard Enterprise HPE.com [cid:803b85f7-01fe-4c9c-a069-74d14a9ea122]

3 9

How to remove rr param on a reply?
by Benoît Panizzon 13 Dec '24

13 Dec '24

Hi Is there a way to remove an param from the top most rr header? I add a rr param towards the B CPE to store some information which is sent back on the rr header of the reply from B. So far this is what is intended and I also get this param in subsequent route headers from messages created by B and as the route header are remove towards A, this works fine. Unfortunately, in a case of a reply, the parameter is passed to A which is then sending back the param in the route header which would make it somehow complicated to figure out which side sent that parameter. I'm only interested if sent from B. So I wonder, is there a way to delete a rr param on replies to make sure I don't get it back in the ACK to the reply? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 4

slot hongkong terbaik
by Womkevintanuwijaya＠gmail.com 13 Dec '24

13 Dec '24

<a href="https://slothongkong.pro/">slot hongkong</a> The best information from the world's largest number one blog!

1 0

registrar / usrloc / tm => 'load balanced' serial forking?
by Benoit Panizzon 13 Dec '24

13 Dec '24

Hi List With the dispatcher module, you can use different ways of load balanced and weighted serial or parallel forking. Is there a corresponding way to achieve load balanced serial forking to a destination set loaded from registered locations? Use case: Customer with a high availability set-up has two redundant PBX registered to the same AoR. Calls can not be sent in parallel as this would generate two concurrent calls to the end device but call should be distributed evenly between the two contacts registered with that AoR. Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 8

HTTP_CLIENT timeout
by Sergio Charrua 13 Dec '24

13 Dec '24

Hello all! For a STSH project, kamailio is making HTTP requests to a middleware (REST API) using HTTP_CLIENT module. I have set the parameter "timeout" to 2 second, but this increases PDD to too high levels, so I have set it to 1 second. Problem is that 1sec is also too high! The parameter only accepts integer values, so no way to set this to 0.5sec. I thought of having a way for kamailio to be aware that HTTP node #1 is down, so next request it will use HTTP node #2 instead. And once in a while, say, every 60 seconds, kamailio would check status of HTTP node #1 and, if OK, then it will switch back to HTTP node #1 and failover to node #2 when required. The HTTP_CLIENT, as far as I know, doesn't do that. So the question is: what would be the best approach to have this feature on Kamailio? i thought about using HTable and have a flag with value of the HTTP connection to use by default. At worst, only the 1st failover request would take 1 or 2 seconds to timeout....then the subsequent HTTP requests would use node #2. Any ideas? Atenciosamente / Kind Regards / Cordialement / Un saludo, *Sérgio Charrua*

4 5

How to inspect/dump a stacked xavp? / How to stack two xavp on each other?
by Benoit Panizzon 10 Dec '24

10 Dec '24

Hi List I'm trying to inspect the content of the $xavp(tm_contacts) to figure out how t_load_contacts exactly behaves when called multiple times. $var(k) = 0; while ($xavp(tm_contacts[$var(k)]) != $null) { $var(out) = "nothing"; xavp_params_implode("tm_contacts[$var(k)]", "$var(out)"); xlog("L_INFO", "$cfg(route): tm_contacts idx: $var(k) => $var(out)\n"); $var(k) = $var(k) + 1; } My stack contains multiple entries. Unfortunately I struggle to access the lower entries. xavp_params_implode("tm_contacts[$var(k)]", "$var(out)"); does nothing when $var(k) > 0 What is the best way to dump a complete xavp stack? I suspect t_load_contacts does flush the complete stack. Is there a way to stack an xavp on top of another one? Something like: xavp_rm("contact_stack"); # Initialize Stack lookup("location", "sip:alice@example.com"); t_load_contacts(0); $xavp(contact_stack) = $xavp(tm_contacts); lookup("location", "sip:bob@example.com"); t_load_contacts(0); $xavp(contact_stack) = $xavp(tm_contacts); # contact_stack now contains alice + bob lookup("location", "sip:carlie@example.com"); t_load_contacts(0); # $xavp(tm_contacts) now contains only charlie. $xavp(tm_contacts) = $xavp(contact_stack); # $xavp(tm_contacts) now contains only alice, bob + charlie. t_next_contacts(); # Push contacts to destination list creating branches. t_relay(); # Invite all contacts Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

6 10

2026

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 December 2024