Module: kamailio
Branch: 5.8
Commit: a7d4ce95b383dc26c547ef9ee07b05d51abc50f9
URL: https://github.com/kamailio/kamailio/commit/a7d4ce95b383dc26c547ef9ee07b05d…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2024-03-20T13:16:00+01:00
keepalive: small formatting updates and comments to the ka dest structure
(cherry picked from commit cee82c92b06a026b88fea654944f6146eb5cb4d8)
---
Modified: src/modules/keepalive/keepalive.h
---
Diff: https://github.com/kamailio/kamailio/commit/a7d4ce95b383dc26c547ef9ee07b05d…
Patch: https://github.com/kamailio/kamailio/commit/a7d4ce95b383dc26c547ef9ee07b05d…
---
diff --git a/src/modules/keepalive/keepalive.h b/src/modules/keepalive/keepalive.h
index d5a8fcb2197..5ca1ce3561d 100644
--- a/src/modules/keepalive/keepalive.h
+++ b/src/modules/keepalive/keepalive.h
@@ -69,13 +69,15 @@ typedef struct _ka_initial_dest
typedef struct _ka_dest
{
str uri;
- str owner; // name of destination "owner"
- // (module asking to monitor this destination
- str uuid; // Universal id for this record
+ str owner; /*!< Name of destination "owner" */
+ /*!< Module asking to monitor this destination */
+ str uuid; /*!< Universal id for this record */
int flags;
int state;
- time_t last_checked, last_up, last_down;
- int counter; // counts unreachable attempts
+ time_t last_checked;
+ time_t last_up; /*!< Time of last successful SIP reply */
+ time_t last_down; /*!< Time of last failure SIP reply */
+ int counter; /*!< Counts unreachable attempts */
ticks_t ping_interval; /*!< Actual interval between OPTIONS */
void *user_attr;
Module: kamailio
Branch: 5.8
Commit: 7df7508d7d2b7b9495dafab8b515a5721bd669ee
URL: https://github.com/kamailio/kamailio/commit/7df7508d7d2b7b9495dafab8b515a57…
Author: Dennis Yurasov <dennis-y(a)yandex-team.ru>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2024-03-20T13:14:16+01:00
dispatcher: refine documentation
- more clear documentation for the new ds_is_from_list flags
(cherry picked from commit 761e963c0f7d9bf1b66c1ef18a409756b919ae2c)
---
Modified: src/modules/dispatcher/doc/dispatcher_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/7df7508d7d2b7b9495dafab8b515a57…
Patch: https://github.com/kamailio/kamailio/commit/7df7508d7d2b7b9495dafab8b515a57…
---
diff --git a/src/modules/dispatcher/doc/dispatcher_admin.xml b/src/modules/dispatcher/doc/dispatcher_admin.xml
index 4708ca06c92..83ef06285a0 100644
--- a/src/modules/dispatcher/doc/dispatcher_admin.xml
+++ b/src/modules/dispatcher/doc/dispatcher_admin.xml
@@ -1805,9 +1805,12 @@ if(ds_list_exists("10")) {
If bit two is set, then protocol is ignored.
If bit three is set, then state must be active.
If bit four is set, then socket/sockname be matched.
- If bit five is set, then try to find the most complete
- "address/protocol/port/local socket" combination for all dispatcher targets. The parameter
- can be an integer or a variable holding an integer value.
+ If bit five is set, then try to find the most closest target from all
+ dispatcher targets with the mandatory ip and combination of local socket, protocol, port,
+ the weighted search result is combined from bit flags of matched components:
+ ip - 1, port - 2, protocol - 4, local socket - 8,
+ the target with the maximum value of flags combination will be selected.
+ The parameter can be an integer or a variable holding an integer value.
It must be provided if the uri parameter is provided.
</para>
</listitem>
This started happening with 5.8.0. I was to update our project with Docker image from 5.7.1 to 5.8.0
```
kamailio[594]: ERROR: acc [acc_extra.c:169]: parse_acc_extra(): parse failed in <callid=$dlg(callid);src_user=$(dlg(from_uri){uri.user});dst_user=$(dlg(to_uri){uri.user});xxx_channel_id=$dlg_var(xxx_channel_id);t_error=$dlg_var(to_original_user);src_original_user=$dlg_var(from_original_user);dst_original_user=$dlg_var(to_original_user)id);src_user=$(dlg(from_uri){uri.user});dst_user=$(dlg(to_uri){uri.user});xxx_channel_id=$dlg_var(xxx_channel_id);t_error=$dlg_var(to_original_user);src_original_user=$dlg_var(from_original_user);dst_original_user=$dlg_var(to_original_user> around position 257
kamailio[594]: ERROR: acc [acc_extra.c:173]: parse_acc_extra(): error
kamailio[594]: ERROR: acc [acc_cdr.c:827]: set_cdr_extra(): failed to parse crd_extra param
kamailio[594]: ERROR: acc [acc_mod.c:528]: mod_init(): failed to set cdr extra 'callid=$dlg(callid);src_user=$(dlg(from_uri){uri.user});dst_user=$(dlg(to_uri){uri.user});xxx_channel_id=$dlg_var(xxx_channel_id);t_error=$dlg_var(to_original_user);src_original_user=$dlg_var(from_original_user);dst_original_user=$dlg_var(to_original_user)id);src_user=$(dlg(from_uri){uri.user});dst_user=$(dlg(to_uri){uri.user});xxx_channel_id=$dlg_var(xxx_channel_id);t_error=$dlg_var(to_original_user);src_original_user=$dlg_var(from_original_user);dst_original_user=$dlg_var(to_original_user'
kamailio[594]: ERROR: <core> [core/sr_module.c:1039]: init_mod(): Error while initializing module acc (/usr/lib/x86_64-linux-gnu/kamailio/modules/acc.so)
```
This is how it looks in cfg:
```
modparam("acc", "cdr_extra",
"callid=$dlg(callid);src_user=$(dlg(from_uri){uri.user});dst_user=$(dlg(to_uri){uri.user});"
"xxx_channel_id=$dlg_var(xxx_channel_id);t_error=$dlg_var(to_original_user);"
"src_original_user=$dlg_var(from_original_user);dst_original_user=$dlg_var(to_original_user)")
```
I have tested and it looks like it only happen if cdr_extra fields are bigger > 255 char.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3785
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3785(a)github.com>
Module: kamailio
Branch: master
Commit: cee82c92b06a026b88fea654944f6146eb5cb4d8
URL: https://github.com/kamailio/kamailio/commit/cee82c92b06a026b88fea654944f614…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2024-03-19T10:21:51+01:00
keepalive: small formatting updates and comments to the ka dest structure
---
Modified: src/modules/keepalive/keepalive.h
---
Diff: https://github.com/kamailio/kamailio/commit/cee82c92b06a026b88fea654944f614…
Patch: https://github.com/kamailio/kamailio/commit/cee82c92b06a026b88fea654944f614…
---
diff --git a/src/modules/keepalive/keepalive.h b/src/modules/keepalive/keepalive.h
index d5a8fcb2197..5ca1ce3561d 100644
--- a/src/modules/keepalive/keepalive.h
+++ b/src/modules/keepalive/keepalive.h
@@ -69,13 +69,15 @@ typedef struct _ka_initial_dest
typedef struct _ka_dest
{
str uri;
- str owner; // name of destination "owner"
- // (module asking to monitor this destination
- str uuid; // Universal id for this record
+ str owner; /*!< Name of destination "owner" */
+ /*!< Module asking to monitor this destination */
+ str uuid; /*!< Universal id for this record */
int flags;
int state;
- time_t last_checked, last_up, last_down;
- int counter; // counts unreachable attempts
+ time_t last_checked;
+ time_t last_up; /*!< Time of last successful SIP reply */
+ time_t last_down; /*!< Time of last failure SIP reply */
+ int counter; /*!< Counts unreachable attempts */
ticks_t ping_interval; /*!< Actual interval between OPTIONS */
void *user_attr;
AFAIK the commits from Herle Supreeth from its fork https://github.com/herlesupreeth/kamailio were migrated manually (not via PR) to upstream at the end of last year. While reviewing the migration I have found two discrepancies:
1. https://github.com/kamailio/kamailio/commit/8b9a2977e111d9adb8595d98ab59f8c… vs. https://github.com/kamailio/kamailio/commit/a6a3bd088368fbf65c283ae27e999d3…
```
herlesupreeth/kamailio (fork)
commit 8b9a2977e111d9adb8595d98ab59f8c8eb033120
Author: herlesupreeth <herlesupreeth(a)gmail.com>
Date: Mon Jun 7 14:01:54 2021 +0200
IPSec fixes
diff --git a/src/modules/ims_ipsec_pcscf/cmd.c b/src/modules/ims_ipsec_pcscf/cmd.c
index 8e0cabcb80..9de3cf7331 100644
--- a/src/modules/ims_ipsec_pcscf/cmd.c
+++ b/src/modules/ims_ipsec_pcscf/cmd.c
@@ -937,7 +939,14 @@ int ipsec_forward(struct sip_msg* m, udomain_t* d)
dst_port = s->port_us;
}
- int buf_len = snprintf(buf, sizeof(buf) - 1, "sip:%.*s:%d", ci.via_host.len, ci.via_host.s, dst_port);
+ int buf_len = 0;
+ if (dst_proto == PROTO_TCP) {
+ buf_len = snprintf(buf, sizeof(buf) - 1, "sip:%.*s:%d;transport=tcp", ci.via_host.len, ci.via_host.s, dst_port);
+ } else if (dst_proto == PROTO_TLS) {
+ buf_len = snprintf(buf, sizeof(buf) - 1, "sip:%.*s:%d;transport=tls", ci.via_host.len, ci.via_host.s, dst_port);
+ } else {
+ buf_len = snprintf(buf, sizeof(buf) - 1, "sip:%.*s:%d", ci.via_host.len, ci.via_host.s, dst_port);
+ }
if((m->dst_uri.s = pkg_malloc(buf_len + 1)) == NULL) {
LM_ERR("Error allocating memory for dst_uri\n");
```
vs.
```
kamailio/kamailio (upstream)
commit a6a3bd088368fbf65c283ae27e999d315db0844b
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Wed Jun 1 18:11:22 2022 +0200
ims_ipsec_pcscf: new option for ipsec_forward() to set trasport for tcp dst uri
diff --git a/src/modules/ims_ipsec_pcscf/cmd.c b/src/modules/ims_ipsec_pcscf/cmd.c
index 5aa208d334..6f6c15e21b 100644
--- a/src/modules/ims_ipsec_pcscf/cmd.c
+++ b/src/modules/ims_ipsec_pcscf/cmd.c
@@ -947,8 +949,14 @@ int ipsec_forward(struct sip_msg *m, udomain_t *d, int _cflags)
if(!(_cflags & IPSEC_NODSTURI_RESET)) {
char buf[1024];
- int buf_len = snprintf(buf, sizeof(buf) - 1, "sip:%.*s:%d", ci.via_host.len,
- ci.via_host.s, dst_port);
+ int buf_len;
+ if((_cflags & IPSEC_SETDSTURI_FULL) && (dst_proto == PROTO_TCP)) {
+ buf_len = snprintf(buf, sizeof(buf) - 1, "sip:%.*s:%d;transport=tcp",
+ ci.via_host.len, ci.via_host.s, dst_port);
+ } else {
+ buf_len = snprintf(buf, sizeof(buf) - 1, "sip:%.*s:%d", ci.via_host.len,
+ ci.via_host.s, dst_port);
+ }
if((m->dst_uri.s = pkg_malloc(buf_len + 1)) == NULL) {
LM_ERR("Error allocating memory for dst_uri\n");
```
To me it seems the handling of the case `dst_proto == PROTO_TLS` is missing upstream.
2. The commit https://github.com/kamailio/kamailio/commit/bfb0a17f3998d26991b4da7a8e83b8c… seems to be absent in upstream.
(From my point of view all the other commits are migrated fine, thanks for the good work!)
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3772
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3772(a)github.com>
<!-- 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 -->
- [ ] 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 -->
Carrier id 0 might be a valid carrier number(e.g. for Germany D000-D999 are valid). Return negative carrier id in case of failures.
If all ok, I'd like to backport this to 5.8, 5.7 and 5.6
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3775
-- Commit Summary --
* pdb: Return negative carrierid for failures
-- File Changes --
M src/modules/pdb/pdb.c (14)
M utils/pdbt/pdb_server.c (2)
M utils/pdbt/pdb_server_backend.c (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3775.patchhttps://github.com/kamailio/kamailio/pull/3775.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3775
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3775(a)github.com>
<!-- 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 -->
- [ ] PR should be backported to stable branches
- [ ] Tested changes locally
- [x] Related to issue #3772
#### Description
<!-- Describe your changes in detail -->
This patch was initially done by Herle Supreeth in his fork but isn't present upstream yet: https://github.com/kamailio/kamailio/commit/8b9a2977e111d9adb8595d98ab59f8c…
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3780
-- Commit Summary --
* ims_ipsec_pcscf: TLS support in ipsec_forward() improved
-- File Changes --
M src/modules/ims_ipsec_pcscf/cmd.c (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3780.patchhttps://github.com/kamailio/kamailio/pull/3780.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3780
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3780(a)github.com>
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for feature requests.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio…
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-dev.lists.kamailio.o…
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If you submit a feature request (or enhancement) add the description of what you would like to be added.
If there is no content to be filled in a section, the entire section can be removed.
Note that a feature request may be closed automatically after about 2 months
if there is no interest from developers or community users to implement it, being
considered expired. In such case can be reopened by writing a comment that includes
the token `/notexpired`. About two weeks before considered expired, the item is
marked with the label `stale`, trying to notify the submitter and everyone else
that might be interested in it. To remove the label `stale`, write a comment that
includes the token `/notstale`. Also, any comment postpone the `expire` timeline,
being considered that there is interest in the proposed feature request.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
We recently deployed successfully Kamailio with TLS certificates. Now we would like to use let's encrypt certificate which expire after 3 months. Means we need to renew certificate approximatively every 2 months. But while reading docs, in [known limitations](https://kamailio.org/docs/modules/devel/modules/tls.html#tls.k… it says :
> TLS specific config reloading is not safe, so for now better don't use it, especially under heavy traffic.
We struggle to understand if this behaviour is risky and not recommended under heavy traffic for certificate renewal. The doc has been added initially by @poandrei 18 years ago in Feb 21 2007 (see [commit](https://github.com/kamailio/kamailio/commit/32e4977cdb9c1c9ca24c140…)
While digging we came across few discussions Kamailio user groups which are saying "the opposite" (kind of):
- [Comments by a co-founder of Kamailio ](https://www.mail-archive.com/sr-users@lists.kamailio.org/msg16014.html)stating that the old connections shouldn’t be affected by reload.
- Comments by a Kamailio core developer stating that certificate reload is fine with the “reload” cmd ([link1](https://lists.kamailio.org/pipermail/sr-users/2022-February/114296.h…, [link2](https://github.com/kamailio/kamailio/issues/3305))
Plus in another section in docs:
- [By definition :](https://kamailio.org/docs/modules/devel/modules/tls.html#tls.r.tls.reload) (the) existing active TLS connections are not terminated and they continue to use the old certificates. The new configuration will be used for new connections.
So 18 years after, Is it safe to use `tls.reload` command in production and in heavy traffic for **TLS certificate renewal** ? Because it sounds scary and confusing.
So the documentation as it is, really needs clarifications to let users know which risk they're taking when running the `tls.reload` command.
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
### Expected behavior
The document should clearly documents risks, at least for certificate renewal.
#### Actual observed behavior
Docs and Kamailio user/dev groups are confusing.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3717
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3717(a)github.com>
#### Pre-Submission Checklist
- [ ] 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:
- [x] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #3592
#### Description
Building the WolfSSL module should be optional, even if it is on by default, builders should be able to choose to not need to install 4th party repositories.
See pr #3592 and specifically [this comment](https://github.com/kamailio/kamailio/pull/3592#issuecomment-198730…
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3781
-- Commit Summary --
* Allow builders to disable wolfssl module
-- File Changes --
M pkg/kamailio/obs/kamailio.spec (21)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3781.patchhttps://github.com/kamailio/kamailio/pull/3781.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3781
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3781(a)github.com>
Module: kamailio
Branch: master
Commit: e55d9f50be4adfc14ff9de45c77c23bd0f5e1981
URL: https://github.com/kamailio/kamailio/commit/e55d9f50be4adfc14ff9de45c77c23b…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2024-03-13T10:16:29+01:00
modules: readme files regenerated - dispatcher ... [skip ci]
---
Modified: src/modules/dispatcher/README
---
Diff: https://github.com/kamailio/kamailio/commit/e55d9f50be4adfc14ff9de45c77c23b…
Patch: https://github.com/kamailio/kamailio/commit/e55d9f50be4adfc14ff9de45c77c23b…
---
diff --git a/src/modules/dispatcher/README b/src/modules/dispatcher/README
index 17885b6f77c..209d77f4c87 100644
--- a/src/modules/dispatcher/README
+++ b/src/modules/dispatcher/README
@@ -1491,10 +1491,14 @@ if(ds_list_exists("10")) {
set, then port is ignored. If bit two is set, then protocol is
ignored. If bit three is set, then state must be active. If bit
four is set, then socket/sockname be matched. If bit five is set,
- then try to find the most complete "address/protocol/port/local
- socket" combination for all dispatcher targets. The parameter can
- be an integer or a variable holding an integer value. It must be
- provided if the uri parameter is provided.
+ then try to find the most closest target from all dispatcher
+ targets with the mandatory ip and combination of local socket,
+ protocol, port, the weighted search result is combined from bit
+ flags of matched components: ip - 1, port - 2, protocol - 4, local
+ socket - 8, the target with the maximum value of flags combination
+ will be selected. The parameter can be an integer or a variable
+ holding an integer value. It must be provided if the uri parameter
+ is provided.
* uri (optional) - if parameter is empty or missing, the matching is
done against source IP, port and protocol. Otherwise the value has
to be a valid SIP URI, used to match against addresses in the
- more clear documentation for the new ds_is_from_list flags
<!-- 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 -->
- [ ] PR should be backported to stable branches
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3783
-- Commit Summary --
* dispatcher: refine documentation
-- File Changes --
M src/modules/dispatcher/doc/dispatcher_admin.xml (9)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3783.patchhttps://github.com/kamailio/kamailio/pull/3783.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3783
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3783(a)github.com>
Module: kamailio
Branch: master
Commit: 761e963c0f7d9bf1b66c1ef18a409756b919ae2c
URL: https://github.com/kamailio/kamailio/commit/761e963c0f7d9bf1b66c1ef18a40975…
Author: Dennis Yurasov <dennis-y(a)yandex-team.ru>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2024-03-13T10:08:05+01:00
dispatcher: refine documentation
- more clear documentation for the new ds_is_from_list flags
---
Modified: src/modules/dispatcher/doc/dispatcher_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/761e963c0f7d9bf1b66c1ef18a40975…
Patch: https://github.com/kamailio/kamailio/commit/761e963c0f7d9bf1b66c1ef18a40975…
---
diff --git a/src/modules/dispatcher/doc/dispatcher_admin.xml b/src/modules/dispatcher/doc/dispatcher_admin.xml
index 4708ca06c92..83ef06285a0 100644
--- a/src/modules/dispatcher/doc/dispatcher_admin.xml
+++ b/src/modules/dispatcher/doc/dispatcher_admin.xml
@@ -1805,9 +1805,12 @@ if(ds_list_exists("10")) {
If bit two is set, then protocol is ignored.
If bit three is set, then state must be active.
If bit four is set, then socket/sockname be matched.
- If bit five is set, then try to find the most complete
- "address/protocol/port/local socket" combination for all dispatcher targets. The parameter
- can be an integer or a variable holding an integer value.
+ If bit five is set, then try to find the most closest target from all
+ dispatcher targets with the mandatory ip and combination of local socket, protocol, port,
+ the weighted search result is combined from bit flags of matched components:
+ ip - 1, port - 2, protocol - 4, local socket - 8,
+ the target with the maximum value of flags combination will be selected.
+ The parameter can be an integer or a variable holding an integer value.
It must be provided if the uri parameter is provided.
</para>
</listitem>