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

2024-04-04 Thread Alexandru Covalschi via sr-users
Okay so is that some secret voip lore im missing on? What's the market value? пн, 1 апр. 2024 г. в 23:25, Tom Lynn via sr-users < sr-users@lists.kamailio.org>: > But is it organic? > > On Mon, Apr 1, 2024 at 11:59 AM Alex Balashov via sr-users < > sr-users@lists.kamailio.org> wrote: > >> For

[SR-Users] Re: TLS module doesn't support TLSV1

2024-04-04 Thread Richard Chan via sr-users
Check how libssl3 is configured in /etc/ssl/openssl.cnf. You may need: [system_default_sect] MinProtocol = TLSv1.0 CipherString = ALL@SECLEVEL=0 From: https://serverfault.com/questions/1143995/tls-1-0-broken-with-newer-debian-openssl Regards Richard

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

2024-04-04 Thread Ovidiu Sas via sr-users
Hi Ben, You made me discover that the xhttp_prom_stats modparam doesn't work the way I thought it would work :) I was always using all and I didn't check the scenario that you described. I was under the impression that xhttp_prom_stats is accepting a csv with all the stats to be collected. So

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

2024-04-04 Thread Ben Kaufman via sr-users
Is this a variable named "xhttp_prom_stats", or the modparam key "xhttp_prom_stats"? There's already two separate parameters, right: - xhttp_prom_stats - corresponds to the rpc stats.get_statistics, thus it's argument corresponds to that RPC call - xhttp_prom_pkg_stats - Corresponds to the rpc

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

2024-04-04 Thread Ovidiu Sas via sr-users
Hello Henning, I have nothing against using a single variable, except that it is confusing. It is not backward compatible. If you enable all vars, then all new stats will be enabled by default. In the current stable version, the names of the stats vars and stats groups are inherited from the

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

2024-04-04 Thread Henning Westerholt via sr-users
Hello Ovidiu, nothing against it from my side. I would recommend using the existing variable " xhttp_prom_stats" for activating/deactivation. Just think we should not introduce to many single purpose variables, especially for a value which is always available without any dependencies. Cheers,

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

2024-04-04 Thread Ovidiu Sas via sr-users
Hello all, The xhttp_module can export all stats under "stats.get_statistics" RPC command. I was thinking of adding an optional "uptime" stat that will return the kamailio server uptime (like the "core.uptime" RPC command). This will make it easier to add an uptime panel in grafana. The new stat

[SR-Users] Re: TLS module doesn't support TLSV1

2024-04-04 Thread Social Boh via sr-users
SIPTRACE module and SNGREP for TLS Capture: https://www.voztovoice.org/?q=node/3020 Spanish --- I'm SoCIaL, MayBe El 4/04/2024 a las 3:12 a. m., Omar Atef via sr-users escribió: Well, I've tried all versions lower than "TLSv1.2" and it didn't work just Kamailio running fine without

[SR-Users] Re: TLS module doesn't support TLSV1

2024-04-04 Thread Omar Atef via sr-users
Well, I've tried all versions lower than "TLSv1.2" and it didn't work just Kamailio running fine without activating TLS. Also I wonder if there's a way to bug TLS SIP messages throw Kamailio itself because as you know it doesn't appear in "sngrep". Thanks,