Hi
I am looking at modifying the topoh module to support having multiple outside IP addresses.
To do this I am looking for a way to store an IP address per SIP message for later use. Is there a standard way of doing this or will I have to add a data structure to the module for this?
Tor
Module: kamailio
Branch: 5.6
Commit: b04f84ea826a4c97cf7ba1804f29833aecc50fd3
URL: https://github.com/kamailio/kamailio/commit/b04f84ea826a4c97cf7ba1804f29833…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2022-08-16T12:16:46+02:00
modules: readme files regenerated - modules ... [skip ci]
---
Modified: src/modules/nathelper/README
Modified: src/modules/siputils/README
Modified: src/modules/uac_redirect/README
Modified: src/modules/xhttp/README
---
Diff: https://github.com/kamailio/kamailio/commit/b04f84ea826a4c97cf7ba1804f29833…
Patch: https://github.com/kamailio/kamailio/commit/b04f84ea826a4c97cf7ba1804f29833…
---
diff --git a/src/modules/nathelper/README b/src/modules/nathelper/README
index 0b5abfb614c..e091d2018fc 100644
--- a/src/modules/nathelper/README
+++ b/src/modules/nathelper/README
@@ -731,9 +731,11 @@ if(is_rfc1918("$rd")) {
5.9. set_contact_alias([trim])
Adds an “;alias=ip~port~transport” parameter to the contact URI
- containing the received ip, port, and transport protocol. The new
- contact URI is immediately visible to other modules in the way the
- fix_nated_contact() does it.
+ containing the received ip, port, and transport protocol. The update of
+ contact URI is signaled to a few other modules in the way the
+ fix_nated_contact() does it by using the internal flags. The new value
+ is not visible to pseudo-variables and it does not change the SIP
+ message buffer.
Meaning of parameters:
* trim - by default, set_contact_alias() will not detect and trim an
diff --git a/src/modules/siputils/README b/src/modules/siputils/README
index adc29cbd24f..51b9e42adc0 100644
--- a/src/modules/siputils/README
+++ b/src/modules/siputils/README
@@ -1002,7 +1002,7 @@ if (is_supported("outbound")) { ... }
...
if(is_first_hop()) { ... }
...
-if(is_first_hop_mode("1")) { ... }
+if(is_first_hop("1")) { ... }
...
4.34. sip_p_charging_vector(flags)
diff --git a/src/modules/uac_redirect/README b/src/modules/uac_redirect/README
index 812755bc5d1..c016467df94 100644
--- a/src/modules/uac_redirect/README
+++ b/src/modules/uac_redirect/README
@@ -205,10 +205,12 @@ modparam("uac_redirect","accept_filter",".*(a)siphub\.net")
4.4. acc_function (string)
Specifies the accounting function to be used. Just by defining this
- parameter, the accounting support will not be enabled. Accounting may
- only be enabled via two parameters set_accept_filter() scripting
+ parameter, the accounting is not done automatically, it has to be
+ requested via parameters of set_accept_filter() or other scripting
function.
+ Set it to empty string in order to disable binding to acc module.
+
Its values may be:
* acc_log_request
* acc_db_request
@@ -224,10 +226,7 @@ modparam("uac_redirect","acc_function","acc_db_request")
4.5. acc_db_table (string)
Specifies the accounting table to be used if DB accounting was chosen
- (acc_function was set to “acc_db_request”). Just by defining this
- parameter, the accounting support will not be enabled. Accounting may
- only be enabled via two parameters set_accept_filter() scripting
- function.
+ (acc_function was set to “acc_db_request” or “acc_request”).
The default value is “acc”.
diff --git a/src/modules/xhttp/README b/src/modules/xhttp/README
index 781ac413927..9a59c839aa1 100644
--- a/src/modules/xhttp/README
+++ b/src/modules/xhttp/README
@@ -131,11 +131,15 @@ Chapter 1. Admin Guide
3.2. Kamailio Core Settings
- SIP requires a Content-Length header for TCP transport. But most HTTP
- clients do not set the content length for normal GET requests.
- Therefore, the core must be configured to allow incoming requests
- without content length header:
- * tcp_accept_no_cl=yes
+ Related core settings:
+ * tcp_accept_no_cl=yes - SIP requires the Content-Length header for
+ TCP transport. But most HTTP clients do not set the content length
+ for normal GET requests. Therefore, the core must be configured to
+ allow incoming requests without content length header.
+ * http_reply_parse=yes - various Kamailio modules may parse what it
+ is sent out (e.g., for replication, topology management). In such
+ case errors are printed if the outgoing message is not SIP and this
+ parameter is not set.
3.3. External Libraries or Applications
Module: kamailio
Branch: 5.6
Commit: e07c2288053a21f5fc758f359a60ffaceb687f35
URL: https://github.com/kamailio/kamailio/commit/e07c2288053a21f5fc758f359a60ffa…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2022-08-16T12:00:47+02:00
xhttp: docs - listed http_reply_parse core setting
(cherry picked from commit 36b0da00b9fc08be9e855d5dd4cc878b6e3c88bf)
---
Modified: src/modules/xhttp/doc/xhttp_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/e07c2288053a21f5fc758f359a60ffa…
Patch: https://github.com/kamailio/kamailio/commit/e07c2288053a21f5fc758f359a60ffa…
---
diff --git a/src/modules/xhttp/doc/xhttp_admin.xml b/src/modules/xhttp/doc/xhttp_admin.xml
index 507283b90f4..f0e6d3fdeb8 100644
--- a/src/modules/xhttp/doc/xhttp_admin.xml
+++ b/src/modules/xhttp/doc/xhttp_admin.xml
@@ -85,13 +85,23 @@
<section>
<title>&kamailio; Core Settings</title>
<para>
- SIP requires a Content-Length header for TCP transport. But most HTTP clients do not
- set the content length for normal GET requests. Therefore, the core must be configured
- to allow incoming requests without content length header:
+ Related core settings:
<itemizedlist>
<listitem>
<para>
- <emphasis>tcp_accept_no_cl=yes</emphasis>
+ <emphasis>tcp_accept_no_cl=yes</emphasis> - SIP requires the
+ Content-Length header for TCP transport. But most HTTP clients
+ do not set the content length for normal GET requests. Therefore,
+ the core must be configured to allow incoming requests without
+ content length header.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>http_reply_parse=yes</emphasis> - various Kamailio
+ modules may parse what it is sent out (e.g., for replication,
+ topology management). In such case errors are printed if the
+ outgoing message is not SIP and this parameter is not set.
</para>
</listitem>
</itemizedlist>