Module: kamailio
Branch: 5.2
Commit: fdd8bd3cce007e6256be5373d84413ffdeff802e
URL: https://github.com/kamailio/kamailio/commit/fdd8bd3cce007e6256be5373d84413f…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2019-12-19T17:43:48+01:00
dispatcher: small style fix in ds_probing_mode docs
(cherry picked from commit faccbb1cf62bfb625d0bcc9d1a52727dcdd962ff)
---
Modified: src/modules/dispatcher/doc/dispatcher_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/fdd8bd3cce007e6256be5373d84413f…
Patch: https://github.com/kamailio/kamailio/commit/fdd8bd3cce007e6256be5373d84413f…
---
diff --git a/src/modules/dispatcher/doc/dispatcher_admin.xml b/src/modules/dispatcher/doc/dispatcher_admin.xml
index bcfa4a95c9..ed8b1808ad 100644
--- a/src/modules/dispatcher/doc/dispatcher_admin.xml
+++ b/src/modules/dispatcher/doc/dispatcher_admin.xml
@@ -644,8 +644,8 @@ modparam("dispatcher", "force_dst", 1)
but you can skip some servers with flag 4 in destination list file, for example.</para>
</listitem>
<listitem>
- <para>Value 2: if set to 2, only gateways in inactive state with
- probing mode set are tested.</para>
+ <para>Value 2: if set to 2, only gateways in INACTIVE state with
+ PROBING mode set are tested.</para>
</listitem>
<listitem>
<para>Value 3: If set to 3, any gateway with state PROBING is continually probed
Module: kamailio
Branch: 5.1
Commit: 45f6263470bc6866352d450a606d094a45bcbb70
URL: https://github.com/kamailio/kamailio/commit/45f6263470bc6866352d450a606d094…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2019-12-19T17:42:44+01:00
dispatcher: small style fix in ds_probing_mode docs
(cherry picked from commit faccbb1cf62bfb625d0bcc9d1a52727dcdd962ff)
---
Modified: src/modules/dispatcher/doc/dispatcher_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/45f6263470bc6866352d450a606d094…
Patch: https://github.com/kamailio/kamailio/commit/45f6263470bc6866352d450a606d094…
---
diff --git a/src/modules/dispatcher/doc/dispatcher_admin.xml b/src/modules/dispatcher/doc/dispatcher_admin.xml
index c62385279c..2b486ad090 100644
--- a/src/modules/dispatcher/doc/dispatcher_admin.xml
+++ b/src/modules/dispatcher/doc/dispatcher_admin.xml
@@ -681,8 +681,8 @@ modparam("dispatcher", "force_dst", 1)
set to TRYING state.</para>
</listitem>
<listitem>
- <para>Value 2: if set to 2, only gateways in inactive state with
- probing mode set are tested.</para>
+ <para>Value 2: if set to 2, only gateways in INACTIVE state with
+ PROBING mode set are tested.</para>
</listitem>
<listitem>
<para>Value 3: If set to 3, any gateway with state PROBING is continually probed
I observed inconsistent behaviour in the dispatcher module. In some modes either the code needs to be fixed or the documentation adapted. As it is a widely used module, some feedback about this would be appreciated.
1) ds_probing_mode 0
This mode don't work together with a ds_inactive_threshold > 1 and gateway set to "IP". It will set a gateway to IX after the first successful ping. Therefore gateways will not be activated automatically. In mode "TP" it works and sets the gateway to "AX".
My suggestion would be to fix this in the code, that it behaves as mode 1 and 3: count to the ds_inactive_threshold and then set to "AX".
2) ds_probing_mode 2
According to the docs this should like this: “only gateways in inactive state with probing mode set are tested”. I understood it that it means gateways with mode "IP".
But according to my tests it also probes gateways in "TP" or "AP" probing state and changes this both to AX. Either the documentation or the module behaviour should be fixed.
The same issue mentioned above (ds_probing_mode 0 together with ds_inactive_threshold > 1) is also present. I also would suggest to fix it in the code here as well.
root@sip:/etc/kamailio# kamcmd core.version
kamailio 5.4.0-dev1 (x86_64/linux) 8ee711
--
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/issues/2100
Module: kamailio
Branch: master
Commit: faccbb1cf62bfb625d0bcc9d1a52727dcdd962ff
URL: https://github.com/kamailio/kamailio/commit/faccbb1cf62bfb625d0bcc9d1a52727…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2019-12-19T17:35:58+01:00
dispatcher: small style fix in ds_probing_mode docs
---
Modified: src/modules/dispatcher/doc/dispatcher_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/faccbb1cf62bfb625d0bcc9d1a52727…
Patch: https://github.com/kamailio/kamailio/commit/faccbb1cf62bfb625d0bcc9d1a52727…
---
diff --git a/src/modules/dispatcher/doc/dispatcher_admin.xml b/src/modules/dispatcher/doc/dispatcher_admin.xml
index 4c9430a630..36bf343a0d 100644
--- a/src/modules/dispatcher/doc/dispatcher_admin.xml
+++ b/src/modules/dispatcher/doc/dispatcher_admin.xml
@@ -651,8 +651,8 @@ modparam("dispatcher", "force_dst", 1)
but you can skip some servers with flag 4 in destination list file, for example.</para>
</listitem>
<listitem>
- <para>Value 2: if set to 2, only gateways in inactive state with
- probing mode set are tested.</para>
+ <para>Value 2: if set to 2, only gateways in INACTIVE state with
+ PROBING mode set are tested.</para>
</listitem>
<listitem>
<para>Value 3: If set to 3, any gateway with state PROBING is continually probed
Module: kamailio
Branch: master
Commit: cb8b582f478d80e80d0dff492e0e376427182d91
URL: https://github.com/kamailio/kamailio/commit/cb8b582f478d80e80d0dff492e0e376…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2019-12-19T11:01:22+01:00
modules: readme files regenerated - ims_ipsec_pcscf ... [skip ci]
---
Modified: src/modules/ims_ipsec_pcscf/README
---
Diff: https://github.com/kamailio/kamailio/commit/cb8b582f478d80e80d0dff492e0e376…
Patch: https://github.com/kamailio/kamailio/commit/cb8b582f478d80e80d0dff492e0e376…
---
diff --git a/src/modules/ims_ipsec_pcscf/README b/src/modules/ims_ipsec_pcscf/README
index 32bb2d6000..fb95bae68b 100644
--- a/src/modules/ims_ipsec_pcscf/README
+++ b/src/modules/ims_ipsec_pcscf/README
@@ -54,7 +54,7 @@ Tsvetomir Dimitrov
4. Functions
4.1. ipsec_create(domain)
- 4.2. ipsec_forward(domain)
+ 4.2. ipsec_forward(domain, flags)
4.3. ipsec_destroy(domain)
List of Examples
@@ -93,7 +93,7 @@ Chapter 1. Admin Guide
4. Functions
4.1. ipsec_create(domain)
- 4.2. ipsec_forward(domain)
+ 4.2. ipsec_forward(domain, flags)
4.3. ipsec_destroy(domain)
1. Overview
@@ -222,7 +222,7 @@ modparam("ims_ipsec_pcscf", "ipsec_spi_id_range", 1000)
4. Functions
4.1. ipsec_create(domain)
- 4.2. ipsec_forward(domain)
+ 4.2. ipsec_forward(domain, flags)
4.3. ipsec_destroy(domain)
4.1. ipsec_create(domain)
@@ -241,7 +241,7 @@ modparam("ims_ipsec_pcscf", "ipsec_spi_id_range", 1000)
ipsec_create("location");
...
-4.2. ipsec_forward(domain)
+4.2. ipsec_forward(domain, flags)
The function processes redirects outgoing message via the IPSec tunnel
initiated with ipsec_create().
@@ -249,10 +249,15 @@ ipsec_create("location");
Meaning of the parameters is as follows:
* domain - Logical domain within the registrar. If a database is used
then this must be name of the table which stores the contacts.
+ flags - Set send force socket for request messages. If 1 - set
+ force socket for request messages. Useful for ipsec and TCP. This
+ is an optional parameter, default value - 0.
Example 1.9. ipsec_forward
...
ipsec_forward("location");
+# or
+ipsec_forward("location", "1");
...
4.3. ipsec_destroy(domain)