Hello,
If somebody is using Kamailio in a larger environment with TLS, this new technical analysis and performance report from haproxy could be interesting: https://www.haproxy.com/blog/state-of-ssl-stacks
The bottom-line - OpenSSL 3.0 will show serious performance regressions for larger TLS services with higher performance requirements. OpenSSL 3.1 and newer versions are a bit better, but still much slower in key operations. You should consider using the tls_wolfssl module or stay on OpenSSL 1.1.1. For the medium- to long-term we probably should observe how other OpenSSL libraries are developing and act accordingly for the tls modules.
The haproxy project recommends besides using wolfssl also the aws-lc library. The situation regarding OpenSSL 3.x seems to be not easily fixable, as these regressions are caused from internal design decisions.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com<https://gilawa.com/>
Module: kamailio
Branch: master
Commit: 57316690e96f8c458e9f83af7e102bfa816bf2cf
URL: https://github.com/kamailio/kamailio/commit/57316690e96f8c458e9f83af7e102bf…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2025-05-11T15:57:50+02:00
pv: docs for the new xavp/i rm all functions
---
Modified: src/modules/pv/doc/pv_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/57316690e96f8c458e9f83af7e102bf…
Patch: https://github.com/kamailio/kamailio/commit/57316690e96f8c458e9f83af7e102bf…
---
diff --git a/src/modules/pv/doc/pv_admin.xml b/src/modules/pv/doc/pv_admin.xml
index 6a06bb717de..0d962a81ca5 100644
--- a/src/modules/pv/doc/pv_admin.xml
+++ b/src/modules/pv/doc/pv_admin.xml
@@ -726,6 +726,29 @@ xavi_child_sets("WhatEver", "FoO", "Count: $var(n)");
...
xavp_rm("x");
# same result as: $xavp(x) = $null;
+...
+ </programlisting>
+ </example>
+ </section>
+ <section id="pv.f.xavp_rm_all">
+ <title>
+ <function moreinfo="none">xavp_rm_all(rname)</function>
+ </title>
+ <para>
+ Remove all the values of $xavp(rname).
+ </para>
+ <para>
+ The parameter has to be the name of XAVP in the root list.
+ It can be static or dynamic string (to include variables).
+ </para>
+ <para>
+ Function can be used from ANY ROUTE.
+ </para>
+ <example>
+ <title><function>xavp_rm_all</function> usage</title>
+ <programlisting format="linespecific">
+...
+xavp_rm_all("x");
...
</programlisting>
</example>
@@ -750,6 +773,29 @@ xavp_rm("x");
...
xavi_rm("WhatEver");
# same result as: $xavi(whatever) = $null;
+...
+ </programlisting>
+ </example>
+ </section>
+ <section id="pv.f.xavi_rm_all">
+ <title>
+ <function moreinfo="none">xavi_rm_all(rname)</function>
+ </title>
+ <para>
+ Remove all the values of $xavi(rname).
+ </para>
+ <para>
+ The parameter has to be the name of XAVI in the root list.
+ It can be static or dynamic string (to include variables).
+ </para>
+ <para>
+ Function can be used from ANY ROUTE.
+ </para>
+ <example>
+ <title><function>xavi_rm_all</function> usage</title>
+ <programlisting format="linespecific">
+...
+xavi_rm_all("WhatEver");
...
</programlisting>
</example>
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [*] Commit message has the format required by CONTRIBUTING guide
- [*] Commits are split per component (core, individual modules, libs, utils, ...)
- [*] Each component has a single commit (if not, squash them into one commit)
- [*] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [*] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [*] PR should be backported to stable branches
- [*] Tested changes locally
- [*] Related to issue #4232
#### Description
not all versions of rtpengine sends a key SSRC per stream. For those that do not the same information can be found in ingress SSRCs. Add logic to check for the SSRC value there if the SSRC key is not present.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4233
-- Commit Summary --
* rtpengine: improve compatibility of rtpengine per call leg stats parsing
-- File Changes --
M src/modules/rtpengine/rtpengine.c (19)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4233.patchhttps://github.com/kamailio/kamailio/pull/4233.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4233
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4233(a)github.com>