Module: kamailio
Branch: master
Commit: 120c47178475ad658a8a1846b6cd65b755cde2ac
URL: https://github.com/kamailio/kamailio/commit/120c47178475ad658a8a1846b6cd65b…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2021-02-06T16:16:24+01:00
modules: readme files regenerated - siptrace ... [skip ci]
---
Modified: src/modules/siptrace/README
---
Diff: https://github.com/kamailio/kamailio/commit/120c47178475ad658a8a1846b6cd65b…
Patch: https://github.com/kamailio/kamailio/commit/120c47178475ad658a8a1846b6cd65b…
---
diff --git a/src/modules/siptrace/README b/src/modules/siptrace/README
index 892c7946ee..59f677e899 100644
--- a/src/modules/siptrace/README
+++ b/src/modules/siptrace/README
@@ -526,7 +526,7 @@ modparam("siptrace", "trace_init_mode", 1)
* 0 - no automatic mirroring or storing of SIP traffic.
* 1 (1st bit set) - mirror the traffic to HEP server.
* 2 (2nd bit set) - store the traffic to database server.
- * 4 (3rd bit set) - mirro the traffic to the SIP URI specified by
+ * 4 (3rd bit set) - mirror the traffic to the SIP URI specified by
duplicate_uri.
The trace_on parameter still has to be set, allowing also to control
- the lost module uses http_client API functions and in the course of NG112
client certificates are used for authentication when querying LIS or ECRF,
the fix allows these to be read out via http_client module parameters.
<!-- 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 -->
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] 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
- [x] 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 -->
- [x] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
To use client certificates for authentication when sending HTTP requests via the http_client
API function `http_client_request`, the auth. specific module parameters (default values) are not
passed to curl. The fix allows these to be read out via http_client module parameters to
set proper curl config parameters. Maybe it's a new feature rather than a fix.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2612
-- Commit Summary --
* http_client: http_client_request to include default clientcert, clientkey,...
-- File Changes --
M src/modules/http_client/functions.c (12)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2612.patchhttps://github.com/kamailio/kamailio/pull/2612.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/2612
Dear all
since version 4.4 we are using this parameter to 1 to allow that ongoing
calls process their messages through a particular rtpengine when disabling
it manually from database.
But we see that enabling it also makes all the messages select the
rtpengine and attempt to send its own op command. This is causing an impact
in cases where the rtpengine crashes (luckily not so often).
We have been doing some tests, and with this change
diff --git a/src/modules/rtpengine/rtpengine.c
> b/src/modules/rtpengine/rtpengine.c
> index 20df725d2e..2f6130c62a 100644
> --- a/src/modules/rtpengine/rtpengine.c
> +++ b/src/modules/rtpengine/rtpengine.c
> @@ -3138,11 +3138,12 @@ select_rtpp_node(str callid, str viabranch, int
> do_test, struct rtpp_node **quer
> if (node->rn_recheck_ticks == RTPENGINE_MAX_RECHECK_TICKS)
> {
> LM_DBG("node=%.*s for calllen=%d callid=%.*s is
> disabled(permanent) (probably still UP)! Return it\n",
> node->rn_url.len, node->rn_url.s,
> callid.len, callid.len, callid.s);
> + return node;
> } else {
> LM_DBG("node=%.*s for calllen=%d callid=%.*s is
> disabled, either broke or timeout disabled! Return it\n",
> node->rn_url.len, node->rn_url.s,
> callid.len, callid.len, callid.s);
> }
> - return node;
> + /*return node;*/
> }
>
> return NULL;
it would make to only use allow_op for manually disabled rtpengine nodes,
and would make to not select the node and not try to send the rtpp command,
so we would not have almost any impact in kamailio like timeouts and
congestion, expect having messages not doing rtpengine in a call where
others did.
Do you think this change could make sense?
Is there any reason for being like it is now?
thanks a lot and regards
david
--
[image: Logo]
David Escartín Almudévar
VoIP/Switch Engineer
descartin(a)sonoc.io
*SONOC*
C/ Josefa Amar y Borbón, 10, 4ª · 50001 Zaragoza, España
Tlf: +34 917019888 · www.sonoc.io