Hello,
I am planning to release Kamailio v5.3.7 sometime next week, likely on
Monday or Tuesday, this being the usual prior notice for heads up to
identify issues not reported yet on bug tracker as well as the commits
you are aware of that were not backported yet.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Hi Alex,
yes, this is correct. This interface used also from other modules that needs to exercise UAC like functionality.
https://github.com/kamailio/kamailio/blob/master/src/modules/tm/uac.h
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com
-----Original Message-----
From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Alex Balashov
Sent: Friday, October 30, 2020 7:07 PM
To: sr-users(a)lists.kamailio.org
Subject: Re: [SR-Users] Confusion about TCP worker ports
Daniel,
Just to make sure I understood this:
On 10/30/20 4:34 AM, Daniel-Constantin Mierla wrote:
> confirming what Henning said that dispatcher is not using uac module,
> not to be any doubt about that. Actually, uac modules uses some of the
> TM-UAC functions as dispatcher module, but between dispatcher and uac
> module is no relation, no dependency. Sockets can be enforced in
> dispatcher via socket attribute (I think is also a modparam for a
> global need), however see next remarks about what can happen.
So, there's a common set of UAC request synthesis APIs which are actually exported by TM, but used by both dispatcher and the UAC module per se?
-- Alex
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Module: kamailio
Branch: 5.3
Commit: fec844e0f77bb96779c8380f40d8a842ec63a571
URL: https://github.com/kamailio/kamailio/commit/fec844e0f77bb96779c8380f40d8a84…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2020-10-30T15:01:35+01:00
modules: readme files regenerated - modules ... [skip ci]
---
Modified: src/modules/registrar/README
Modified: src/modules/textops/README
---
Diff: https://github.com/kamailio/kamailio/commit/fec844e0f77bb96779c8380f40d8a84…
Patch: https://github.com/kamailio/kamailio/commit/fec844e0f77bb96779c8380f40d8a84…
---
diff --git a/src/modules/registrar/README b/src/modules/registrar/README
index 2a611ef564..796832b3a4 100644
--- a/src/modules/registrar/README
+++ b/src/modules/registrar/README
@@ -896,8 +896,9 @@ request_route {
location records (in usrloc) depending on Contact and Expires header
fields in the REGISTER message. On success and when called from the
REQUEST_ROUTE, “200 OK” will be returned listing all contacts that are
- currently in the location database. On an error, an error message will
- be sent with a short description in reason phrase.
+ currently in the location database. As a side effect, also branch flags
+ are stored in usrloc. On an error, an error message will be sent with a
+ short description in reason phrase.
Meaning of the parameters is as follows:
* domain - Logical domain within the registrar. If a database is used
@@ -945,7 +946,8 @@ save("location", "0x00", "sip:test@kamailio.org");
no such contacts, -1 will be returned. If there are such contacts,
Request-URI will be overwritten with the contact that has the highest q
value and optionally the rest will be appended to the message
- (depending on append_branches parameter value).
+ (depending on append_branches parameter value). As a side effect, also
+ branch flags are restored from usrloc.
If the method_filtering option is enabled and request is initial
request without to-tag, the lookup function will return only the
diff --git a/src/modules/textops/README b/src/modules/textops/README
index 32ed2c4d36..aafe390638 100644
--- a/src/modules/textops/README
+++ b/src/modules/textops/README
@@ -721,10 +721,13 @@ if (has_body("multipart/mixed")) {
4.23. append_to_reply(txt)
- Append txt as header to the reply.
+ Append txt as header to the reply that is going to be generated by
+ Kamailio (e.g., via sl_send_reply(...)).
Meaning of the parameters is as follows:
- * txt - String which may contains pseudo-variables.
+ * txt - String which may contains pseudo-variables. Note that the
+ value has to be ended with "\r\n" (end of header characters
+ sequence).
This function can be used from REQUEST_ROUTE, BRANCH_ROUTE,
FAILURE_ROUTE, ERROR_ROUTE.
@@ -737,12 +740,14 @@ append_to_reply("Foo: $rm at $Ts\r\n");
4.24. append_hf(txt[, hdr])
- Appends 'txt' as header after first header field or after last 'hdr'
- header field.
+ Appends 'txt' as header at the end of the all headers, or after last
+ header named 'hdr' if the second parameter is provided.
Meaning of the parameters is as follows:
* txt - Header field to be appended. The value can contain
- pseudo-variables which will be replaced at run time.
+ pseudo-variables which will be replaced at run time. Note that the
+ value has to be ended with "\r\n" (end of header characters
+ sequence).
* hdr - Header name after which the 'txt' is appended.
This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE,
@@ -756,12 +761,14 @@ append_hf("From-username: $fU\r\n", "Call-ID");
4.25. insert_hf(txt[, hdr])
- Inserts 'txt' as header before the first header field or before first
- 'hdr' header field if 'hdr' is given.
+ Inserts 'txt' as header before the first header field, or before first
+ header named 'hdr'if the second parameter is provided.
Meaning of the parameters is as follows:
* txt - Header field to be inserted. The value can contain
- pseudo-variables which will be replaced at run time.
+ pseudo-variables which will be replaced at run time. Note that the
+ value has to be ended with "\r\n" (end of header characters
+ sequence).
* hdr - Header name before which the 'txt' is inserted.
This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE,
Module: kamailio
Branch: 5.3
Commit: dc582f3186e7a3fa6bce96ddb27240922da20201
URL: https://github.com/kamailio/kamailio/commit/dc582f3186e7a3fa6bce96ddb272409…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2020-10-30T14:47:25+01:00
textops: docs - some enhancements to basic header operations functions
(cherry picked from commit 374f0f05bdf27ddaf5d8652560738fbfb886c43c)
(cherry picked from commit 7cd88cf05f25a5a5883d936285ac51f82911e9af)
---
Modified: src/modules/textops/doc/textops_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/dc582f3186e7a3fa6bce96ddb272409…
Patch: https://github.com/kamailio/kamailio/commit/dc582f3186e7a3fa6bce96ddb272409…
---
diff --git a/src/modules/textops/doc/textops_admin.xml b/src/modules/textops/doc/textops_admin.xml
index fecaa059f2..9af8394a7c 100644
--- a/src/modules/textops/doc/textops_admin.xml
+++ b/src/modules/textops/doc/textops_admin.xml
@@ -872,13 +872,15 @@ if (has_body("multipart/mixed")) {
<function moreinfo="none">append_to_reply(txt)</function>
</title>
<para>
- Append txt as header to the reply.
+ Append txt as header to the reply that is going to be generated by
+ &kamailio; (e.g., via sl_send_reply(...)).
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
<listitem>
<para><emphasis>txt</emphasis> - String which may contains
- pseudo-variables.
+ pseudo-variables. Note that the value has to be ended with "\r\n"
+ (end of header characters sequence).
</para>
</listitem>
</itemizedlist>
@@ -902,15 +904,16 @@ append_to_reply("Foo: $rm at $Ts\r\n");
<function moreinfo="none">append_hf(txt[, hdr])</function>
</title>
<para>
- Appends 'txt' as header after first header field or after
- last 'hdr' header field.
+ Appends 'txt' as header at the end of the all headers, or after
+ last header named 'hdr' if the second parameter is provided.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
<listitem>
<para><emphasis>txt</emphasis> - Header field to be appended. The
value can contain pseudo-variables which will be replaced at run
- time.
+ time. Note that the value has to be ended with "\r\n" (end of header
+ characters sequence).
</para>
</listitem>
<listitem>
@@ -939,15 +942,16 @@ append_hf("From-username: $fU\r\n", "Call-ID");
<function moreinfo="none">insert_hf(txt[, hdr])</function>
</title>
<para>
- Inserts 'txt' as header before the first header field or before
- first 'hdr' header field if 'hdr' is given.
+ Inserts 'txt' as header before the first header field, or before
+ first header named 'hdr'if the second parameter is provided.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
<listitem>
<para><emphasis>txt</emphasis> - Header field to be inserted. The
value can contain pseudo-variables which will be replaced at run
- time.
+ time. Note that the value has to be ended with "\r\n" (end of header
+ characters sequence).
</para>
</listitem>
<listitem>