[SR-Users] Re: RFC: uptime metric for xhttp_prom module

2024-04-05 Thread Ovidiu Sas via sr-users
For now, I pushed the new uptime statistic to follow the naming convention that was in place: https://www.kamailio.org/docs/modules/devel/modules/xhttp_prom.html#xhttp_prom.p.xhttp_prom_uptime_stat We could implement the following naming convention: # This is the modparam for stats_stats.get_stati

[SR-Users] Handling 422 Message (was: Re: dlg_vars of existing dialog not set after loose_route())

2024-04-05 Thread Benoît Panizzon via sr-users
Hi After more intensive testing, I narrowed the issue down. CPE A => Kamailio+dialog => CPE B CPE A is sending an INVITE with a session timer too smal for CPE B. CPE B replies with 422. This causes the dialog module to trigger the 'call failed' event and attempt to delete the dialog data. CPA

[SR-Users] dlg_vars of existing dialog not set after loose_route()

2024-04-05 Thread Benoît Panizzon via sr-users
Hi Gang I have a strange issue after upgrading to 5.7 I use dlg_vars to keep some information until the end of the call to write them in a CDR. One of those variables records the timestamp of the first invite to determine how long it took from the invite to the 'connection established' if at all

[SR-Users] Re: RFC: uptime metric for xhttp_prom module

2024-04-05 Thread Ben Kaufman via sr-users
I've only ever used "all" as well, and never tried anything else until writing this response yesterday. I think separate param names is fine. -Original Message- From: Ovidiu Sas Sent: Thursday, April 4, 2024 6:58 PM To: Ben Kaufman Cc: Kamailio (SER) - Users Mailing List ; Henning We

[SR-Users] Re: Kamailio Visions 2030 for Appalachia

2024-04-05 Thread Ben Kaufman via sr-users
The release was from April 1st – April Fool’s day. ;) Regards, Kaufman From: Alexandru Covalschi via sr-users Sent: Thursday, April 4, 2024 11:38 PM To: Kamailio (SER) - Users Mailing List Cc: Tom Lynn ; Alexandru Covalschi <568...@gmail.com> Subject: [SR-Users] Re: Kamailio Visions 2030 for A

[SR-Users] Re: low performance with no apparent reason

2024-04-05 Thread Sergio Charrua via sr-users
Thanks Henning! I followed your tip, and indeed got 2.500 CPS now :) ... more than enough for the project! Cheers! *Sérgio Charrua* On Fri, Apr 5, 2024 at 12:37 PM Henning Westerholt wrote: > Hello, > > > > you should be able to decrease the private memory substantially, as this > is per pr

[SR-Users] Re: low performance with no apparent reason

2024-04-05 Thread Henning Westerholt via sr-users
Hello, you should be able to decrease the private memory substantially, as this is per process. This much is never needed. On the other hand, you should probably increase the shared memory if you are having a lot of transactions going on, TLS etc.. This is per server, so you can configure more.

[SR-Users] Re: low performance with no apparent reason

2024-04-05 Thread Sergio Charrua via sr-users
Thank you all for helping! I wasn't expecting such a large number of replies! I ended up partially solving the issue with a different approach. Modifying the size of the UDP Buffer did not reveal any improvement. However, modifying the memory management did improve a lot: from 330 CPS to 1800 CPS

[SR-Users] Statistics for all generated

2024-04-05 Thread Alfredo Román Domínguez via sr-users
I am using Kamailio versions 5.5.7 and 5.8.0 as a stateful proxy (with tm module) and I want to have metrics for all the SIP messages received and sent. I am using the statistics module for counting messages. I have in configuration file the following routes to capture events and count them: onsen