Module: kamailio
Branch: master
Commit: 00b1aba770c26f75c31cf2a28e7ca425f18788dc
URL: https://github.com/kamailio/kamailio/commit/00b1aba770c26f75c31cf2a28e7ca42…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-01-25T12:42:36+01:00
tm: docs for reply_relay_mode parameter
---
Modified: src/modules/tm/doc/params.xml
---
Diff: https://github.com/kamailio/kamailio/commit/00b1aba770c26f75c31cf2a28e7ca42…
Patch: https://github.com/kamailio/kamailio/commit/00b1aba770c26f75c31cf2a28e7ca42…
---
diff --git a/src/modules/tm/doc/params.xml b/src/modules/tm/doc/params.xml
index 0c187375cc..3fdb0a7a49 100644
--- a/src/modules/tm/doc/params.xml
+++ b/src/modules/tm/doc/params.xml
@@ -1547,6 +1547,35 @@ modparam("tm", "rich_redirect", 3)
...
modparam("tm", "exec_time_check", 0)
...
+</programlisting>
+ </example>
+ </section>
+
+ <section id="tm.p.reply_relay_mode">
+ <title><varname>reply_relay_mode</varname> (int)</title>
+ <para>
+ If set to 1, a received 200ok response that was suspeneded is no
+ longer forwarded in the transactional context if another final
+ response was forward while 200ok was suspended. Forwarding the 200ok,
+ even it was received first, results in overwritting the transaction
+ response buffer that can impact matching of incoming ACKs.
+ </para>
+ <para>
+ Set it to 0 in order to disable this behaviour and attempt to forward
+ suspended 200ok in the transaction context. This was the behaviour
+ before the commit 18410da0.
+ </para>
+ <para>
+ <emphasis>
+ Default value is 1.
+ </emphasis>
+ </para>
+ <example>
+ <title>Set <varname>reply_relay_mode</varname> parameter</title>
+ <programlisting format="linespecific">
+...
+modparam("tm", "reply_relay_mode", 0)
+...
</programlisting>
</example>
</section>
<!-- 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
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [x ] 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 -- tested at 5.1.6
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
Problem:
Forwarding of 200 OK while sent 488 waits for ACK, destroys the UAS send buffer
Scenario:
During suspension of 200 OK by ims_qos module function Rx_AAR() at terminating PCSCF,
The PCRF sends an AA Answer with result code DIAMETER_TOO_BUSY (3004), which triggers
the PCSCF to send a 488 ‘Sorry no QoS available’ to the originating side (ims_dialog
module function dlg_terminate()).
Afterwards neither the 200 OK nor the ACK(488) is processed correctly by the PCSCF.
Solution:
The UAS send buffer should not be overwritten during processing of 200 OK,
because non-2xx is needed to associate the ACK message in a correct way.
200 OK must be forwarded statelessly.
Side-Effect (potentially breaks existing function):
Some callbacks cannot be called for the 200 OK, to avoid messing the stored 488.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2590
-- Commit Summary --
* tm: 200 OK not processed correctly by Proxy after final non-2xx
-- File Changes --
M src/modules/tm/t_reply.c (72)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2590.patchhttps://github.com/kamailio/kamailio/pull/2590.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/2590
Module: kamailio
Branch: master
Commit: 18410da04c7f7bbc9628820427fedb92cf893526
URL: https://github.com/kamailio/kamailio/commit/18410da04c7f7bbc9628820427fedb9…
Author: Theo <theodor.scherney(a)kapsch.net>
Committer: Theo <theodor.scherney(a)kapsch.net>
Date: 2020-12-17T14:32:39+01:00
tm: 200 OK not processed correctly by Proxy after final non-2xx
Description:
Problem:
Forwarding of 200 OK while sent 488 waits for ACK, destroys the UAS send buffer
Scenario:
During suspension of 200 OK by ims_qos module function Rx_AAR() at terminating PCSCF,
The PCRF sends an AA Answer with result code DIAMETER_TOO_BUSY (3004), which triggers
the PCSCF to send a 488 âSorry no QoS availableâ to the originating side (ims_dialog
module function dlg_terminate()).
Afterwards neither the 200 OK nor the ACK(488) is processed correctly by the PCSCF.
Solution:
The UAS send buffer should not be overwritten during processing of 200 OK,
because non-2xx is needed to associate the ACK message in a correct way.
200 OK must be forwarded statelessly.
Side-Effect (potentially breaks existing function):
Some callbacks cannot be called for the 200 OK, to avoid messing the stored 488.
---
Modified: src/modules/tm/t_reply.c
---
Diff: https://github.com/kamailio/kamailio/commit/18410da04c7f7bbc9628820427fedb9…
Patch: https://github.com/kamailio/kamailio/commit/18410da04c7f7bbc9628820427fedb9…
Module: kamailio
Branch: master
Commit: 12414972ad0c28ac50ece3c14f98134c3f06c522
URL: https://github.com/kamailio/kamailio/commit/12414972ad0c28ac50ece3c14f98134…
Author: Nicolas C <nchaigne(a)capgemini.fr>
Committer: Nicolas C <nchaigne(a)capgemini.fr>
Date: 2021-01-22T16:04:40+01:00
core: fix to xavp_rm_internal (#2604)
This fixes the following issue:
https://github.com/kamailio/kamailio/issues/2604
Description of the issue:
When called to remove a specific index from a given xavp, function xavp_rm_by_index removes the index (as expected) but also all others before it.
E.g :
If called with idx = 1, it removes indexes 0 and 1.
Likewise if invoked with idx = 2 => the first 3 elements are removed.
This bug is located in function xavp_rm_internal. An assignment was missing when looping over the xavp list.
Same for xavi_rm_internal.
---
Modified: src/core/xavp.c
---
Diff: https://github.com/kamailio/kamailio/commit/12414972ad0c28ac50ece3c14f98134…
Patch: https://github.com/kamailio/kamailio/commit/12414972ad0c28ac50ece3c14f98134…
---
diff --git a/src/core/xavp.c b/src/core/xavp.c
index de6da0c858..26e89a8df3 100644
--- a/src/core/xavp.c
+++ b/src/core/xavp.c
@@ -454,6 +454,8 @@ static int xavp_rm_internal(str *name, sr_xavp_t **head, int idx)
if(idx>=0)
return 1;
count++;
+ } else {
+ prv = foo;
}
n++;
} else {
@@ -1914,6 +1916,8 @@ static int xavi_rm_internal(str *name, sr_xavp_t **head, int idx)
if(idx>=0)
return 1;
count++;
+ } else {
+ prv = foo;
}
n++;
} else {
Hello,
It seems that the respective plugin is missing or can not be loaded. Can you do a ldd on the db_mysql module?
E.g. like this: ldd /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com<https://gilawa.com/>
From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Nicki Otte
Sent: Thursday, January 21, 2021 8:27 AM
To: sr-users(a)lists.kamailio.org
Subject: [SR-Users] Kamailio, debian and MySQL caching_sha2_password
Hi all
Have any of you experienced problems using MySQL(Not MariaDB) on a debian machine, with caching_sha2_password?
I am having some trouble:
Jan 21 08:13:41 MobileValue-Kamailio systemd[1]: Starting Kamailio (OpenSER) - the Open Source SIP Server...
Jan 21 08:13:42 MobileValue-Kamailio kamailio: INFO: <core> [core/tcp_main.c:4983]: init_tcp(): using epoll_lt as the io watch method (auto detected)
Jan 21 08:13:42 MobileValue-Kamailio kamailio[24260]: Listening on
Jan 21 08:13:42 MobileValue-Kamailio kamailio[24260]: udp: 185.31.176.39:5060
Jan 21 08:13:42 MobileValue-Kamailio kamailio[24260]: tcp: 185.31.176.39:80
Jan 21 08:13:42 MobileValue-Kamailio kamailio[24260]: Aliases:
Jan 21 08:13:42 MobileValue-Kamailio kamailio[24260]: tcp: voipgw01.evercall.dk:80
Jan 21 08:13:42 MobileValue-Kamailio kamailio[24260]: udp: voipgw01.evercall.dk:5060
Jan 21 08:13:42 MobileValue-Kamailio /usr/sbin/kamailio[24262]: INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded
Jan 21 08:13:42 MobileValue-Kamailio /usr/sbin/kamailio[24262]: INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available
Jan 21 08:13:42 MobileValue-Kamailio /usr/sbin/kamailio[24262]: ERROR: db_mysql [km_my_con.c:163]: db_mysql_new_connection(): driver error: Plugin caching_sha2_password could not be loaded: /usr/lib/x86_64-linux-gnu/mariadb19/plugin/caching_sha2_password.so: cannot open shared object file: No such file or directory
Jan 21 08:13:42 MobileValue-Kamailio /usr/sbin/kamailio[24262]: ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool
Jan 21 08:13:42 MobileValue-Kamailio /usr/sbin/kamailio[24262]: ERROR: dispatcher [dispatch.c:903]: ds_connect_db(): cannot initialize db connection
Jan 21 08:13:42 MobileValue-Kamailio /usr/sbin/kamailio[24262]: ERROR: dispatcher [dispatch.c:937]: ds_init_db(): unable to connect to the database
Jan 21 08:13:42 MobileValue-Kamailio /usr/sbin/kamailio[24262]: ERROR: dispatcher [dispatcher.c:404]: mod_init(): could not initiate a connect to the database
Jan 21 08:13:42 MobileValue-Kamailio /usr/sbin/kamailio[24262]: ERROR: <core> [core/sr_module.c:849]: init_mod(): Error while initializing module dispatcher (/usr/lib/x86_64-linux-gnu/kamailio/modules/dispatcher.so)
Jan 21 08:13:42 MobileValue-Kamailio /usr/sbin/kamailio[24262]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Jan 21 08:13:42 MobileValue-Kamailio systemd[1]: kamailio.service: Control process exited, code=exited, status=255/EXCEPTION
Jan 21 08:13:42 MobileValue-Kamailio systemd[1]: kamailio.service: Failed with result 'exit-code'.
Jan 21 08:13:42 MobileValue-Kamailio systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server.
I can get around the problem, by making the kamailio & kamailioro user use mysql_native_password instead.
But am i wrong to belieave that it should Work out of the box?
Here are the installed packages from APT:
kamailio/unknown,now 5.4.3+bpo10 amd64 [installed]
kamailio-json-modules/unknown,now 5.4.3+bpo10 amd64 [installed]
kamailio-mysql-modules/unknown,now 5.4.3+bpo10 amd64 [installed]
kamailio-outbound-modules/unknown,now 5.4.3+bpo10 amd64 [installed]
default-libmysqlclient-dev/stable,now 1.0.5 amd64 [installed]
default-libmysqld-dev/stable,now 1.0.5 amd64 [installed]
libmariadb-dev/stable,now 1:10.3.27-0+deb10u1 amd64 [installed,automatic]
libmariadb-dev-compat/stable,now 1:10.3.27-0+deb10u1 amd64 [installed,automatic]
mysql-apt-config/unknown,now 0.8.16-1 all [installed]
mysql-client/unknown,now 8.0.23-1debian10 amd64 [installed,automatic]
mysql-common/unknown,now 8.0.23-1debian10 amd64 [installed,automatic]
mysql-community-client/unknown,now 8.0.23-1debian10 amd64 [installed,automatic]
mysql-community-client-core/unknown,now 8.0.23-1debian10 amd64 [installed,automatic]
mysql-community-client-plugins/unknown,now 8.0.23-1debian10 amd64 [installed,automatic]
mysql-community-server/unknown,now 8.0.23-1debian10 amd64 [installed,automatic]
mysql-community-server-core/unknown,now 8.0.23-1debian10 amd64 [installed,automatic]
mysql-server/unknown,now 8.0.23-1debian10 amd64 [installed]
Thanks in advance
Nicki Bo Otte
Module: kamailio
Branch: master
Commit: 89eea7edb8832124dc325d8303b23ea5f36c88f4
URL: https://github.com/kamailio/kamailio/commit/89eea7edb8832124dc325d8303b23ea…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-01-20T08:54:21+01:00
tm: docs for rpc t_uac_wait_block
---
Modified: src/modules/tm/doc/rpc.xml
---
Diff: https://github.com/kamailio/kamailio/commit/89eea7edb8832124dc325d8303b23ea…
Patch: https://github.com/kamailio/kamailio/commit/89eea7edb8832124dc325d8303b23ea…
---
diff --git a/src/modules/tm/doc/rpc.xml b/src/modules/tm/doc/rpc.xml
index 3304b390d4..18eeccd97c 100644
--- a/src/modules/tm/doc/rpc.xml
+++ b/src/modules/tm/doc/rpc.xml
@@ -65,8 +65,20 @@
<function moreinfo="none">tm.t_uac_wait</function>
</title>
<para>
- Similar to tm.t_uac_start, but waits for the SIP response and tries to
- provide its details via RPC response.
+ Similar to tm.t_uac_start, but waits asynchronously for the SIP response
+ and tries to provide its details via RPC response.
+ </para>
+ </section>
+
+ <section id="tm.rpc.t_uac_wait">
+ <title>
+ <function moreinfo="none">tm.t_uac_wait</function>
+ </title>
+ <para>
+ Similar to tm.t_uac_start, but blocks waiting for the SIP response and
+ returns the SIP reply code and reason text via RPC response. It waits
+ up to 80 seconds, if no reply is received, it returns a RPC fault 500
+ code. While waiting, the RPC process cannot handle other RPC commands.
</para>
</section>
Also added a function called by the three "*_serialize_fields" to reduce code duplication.
The interface is not modified.
#### Type Of Change
- [x] New feature (non-breaking change which adds new functionality)
#### Checklist:
- [x] Tested changes locally
#### Description
Small pull request that adds a function "xavu_serialize_fields" (with same interface as "xavp_serialize_fields" and "xavi_serialize_fields"), and an internal helper function to reduce code duplication.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2603
-- Commit Summary --
* core: added xavu_serialize_fields function
-- File Changes --
M src/core/xavp.c (91)
M src/core/xavp.h (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2603.patchhttps://github.com/kamailio/kamailio/pull/2603.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/2603
Module: kamailio
Branch: master
Commit: 28ff6b5cb50709a92e8849d885dd55e1237f5a9e
URL: https://github.com/kamailio/kamailio/commit/28ff6b5cb50709a92e8849d885dd55e…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-01-15T12:48:35+01:00
misc: tools/kemi/lua - fixed field name in python script
---
Modified: misc/tools/kemi/lua/kemiksrlib.py
---
Diff: https://github.com/kamailio/kamailio/commit/28ff6b5cb50709a92e8849d885dd55e…
Patch: https://github.com/kamailio/kamailio/commit/28ff6b5cb50709a92e8849d885dd55e…
---
diff --git a/misc/tools/kemi/lua/kemiksrlib.py b/misc/tools/kemi/lua/kemiksrlib.py
index f801a9d6a2..2a6f360a58 100644
--- a/misc/tools/kemi/lua/kemiksrlib.py
+++ b/misc/tools/kemi/lua/kemiksrlib.py
@@ -8,7 +8,7 @@
class ModuleObjGenerator(object):
# Contains the output until it should be written to disk
- output_string = ""
+ object_string = ""
def execute(self, data):
# Validate that we got some methods back. 155 is an arbitrary large number.
Module: kamailio
Branch: master
Commit: db9f768f1844e3339567522bf5a1b9f2b41b0bb6
URL: https://github.com/kamailio/kamailio/commit/db9f768f1844e3339567522bf5a1b9f…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-01-14T08:27:36+01:00
lib/trie: updated reference to userblocklist module
---
Modified: src/lib/README
Modified: src/lib/trie/dtrie.c
Modified: src/lib/trie/dtrie.h
---
Diff: https://github.com/kamailio/kamailio/commit/db9f768f1844e3339567522bf5a1b9f…
Patch: https://github.com/kamailio/kamailio/commit/db9f768f1844e3339567522bf5a1b9f…
---
diff --git a/src/lib/README b/src/lib/README
index b490787899..9ca4cec11b 100644
--- a/src/lib/README
+++ b/src/lib/README
@@ -2,9 +2,9 @@ Standalone libraries:
---------------------
binrpc - A library that provides common interface for different communication
- methods (UNIX sockets, TCP, UDP) using binary RPC as a transport form
- of data. The interface is documented directly in binrpc_api.h file and
- can by generated into HTML form by using Doxygen. There is no
+ methods (UNIX sockets, TCP, UDP) using binary RPC as a transport form
+ of data. The interface is documented directly in binrpc_api.h file and
+ can by generated into HTML form by using Doxygen. There is no
difference between compilation "with" or "without" SER (see compilation
section below).
@@ -30,7 +30,7 @@ shm_regex - Wrapper functions for regcomp, regexec, regfree and regerror
Used by modules: pa, rls, dialog, rpa
trie - Common digit trie implementation for prefix matching, used by
- carrierroute and userblacklist
+ carrierroute and userblocklist
Used by IMS modules: icscf, usrloc_scscf, usrloc_pcscf, registrar_scscf, registrar_pcscf
diff --git a/src/lib/trie/dtrie.c b/src/lib/trie/dtrie.c
index af2d93f1c4..905ddead20 100644
--- a/src/lib/trie/dtrie.c
+++ b/src/lib/trie/dtrie.c
@@ -27,13 +27,13 @@
* Provides a generic trie datastructure and utility functions to
* initialize and manage individual nodes. Its optimized towards
* the usecase of a matching tree that contains only digits, e.g.
- * for LCR or blacklist modules. Nevertheless it also supports the
+ * for LCR or blocklist modules. Nevertheless it also supports the
* matching of characters when configured correctly. For normal
* digit only matching you need to use a branches parameter of
* 10, when you use 128, the complete standard ascii charset is
* available for matching. The trie is setup in shared memory.
* - Module: \ref carrierroute
- * - Module: \ref userblacklist
+ * - Module: \ref userblocklist
* @{
*/
diff --git a/src/lib/trie/dtrie.h b/src/lib/trie/dtrie.h
index fb4388122c..179350176f 100644
--- a/src/lib/trie/dtrie.h
+++ b/src/lib/trie/dtrie.h
@@ -15,8 +15,8 @@
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
*/
@@ -27,14 +27,14 @@
* Provides a generic trie data structure and utility functions to
* initialize and manage individual nodes. Its optimized towards
* the usecase of a matching tree that contains only digits, e.g.
- * for LCR or blacklist modules. Nevertheless it also supports the
+ * for LCR or blocklist modules. Nevertheless it also supports the
* matching of characters when configured correctly. For normal
* digit only matching you need to use a branches parameter of
* 10, when you use 128, the complete standard ascii charset is
* available for matching. The trie is setup in shared memory.
* - Module: \ref carrierroute
- * - Module: \ref userblacklist
- * @{
+ * - Module: \ref userblocklist
+ * @{
*/
#ifndef _DTRIE_H_
#### Pre-Submission Checklist
- [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:
- [ ] PR should be backported to stable branches
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
we send "480 All servers busy" when no servers available for failover
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2602
-- Commit Summary --
* dispatcher: updated failover example
-- File Changes --
M src/modules/dispatcher/doc/dispatcher.cfg (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2602.patchhttps://github.com/kamailio/kamailio/pull/2602.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/2602
Actually we have installed kamailio 5.4.2 and rtpengine like load balancer in a NAT environmet. behind the nat we have 2 identycal nodes using REFER for transfer calls to another destiny. This nodes does not have another SIP message. in the other NAT side we have our public carrier.
When some nodes send to kamailio the REFER message and kamailio reroute this message to the carrier. The call is rejected due company policies.
We want know how can we do for convert or modify the REFER message into INVITE for finally transfer the call.
thank you in advance.
kamailio -v:
version: kamailio 5.4.2 (x86_64/linux) 4fdc21
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 4fdc21
compiled on 20:43:45 Dec 1 2020 with unknown
Uname -a:
Linux proxy 4.15.0-124-generic #127-Ubuntu SMP Fri Nov 6 10:54:43 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
rtpengine -v:
Version: 9.2.0.0+0~mr9.2.0.0 git-master-aa5e0244
--
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/2601
Module: kamailio
Branch: master
Commit: 0f962dca0953ef4461d1c82e229df0eb3efd9b99
URL: https://github.com/kamailio/kamailio/commit/0f962dca0953ef4461d1c82e229df0e…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2021-01-12T12:01:20+01:00
modules: readme files regenerated - lost ... [skip ci]
---
Modified: src/modules/lost/README
---
Diff: https://github.com/kamailio/kamailio/commit/0f962dca0953ef4461d1c82e229df0e…
Patch: https://github.com/kamailio/kamailio/commit/0f962dca0953ef4461d1c82e229df0e…
---
diff --git a/src/modules/lost/README b/src/modules/lost/README
index 81a4fa4833..07c5835483 100644
--- a/src/modules/lost/README
+++ b/src/modules/lost/README
@@ -27,6 +27,8 @@ Wolfgang Kampichler
3.1. exact_type (int)
3.2. response_time (int)
3.3. location_type (string)
+ 3.4. geoheader_type (int)
+ 3.5. geoheader_order (int)
4. Functions
@@ -41,8 +43,10 @@ Wolfgang Kampichler
1.1. Set exact_type parameter
1.2. Set response_time parameter
1.3. Set location_type parameter
- 1.4. lost_held_query() usage
- 1.5. lost() usage
+ 1.4. Set geoheader_type parameter
+ 1.5. Set geoheader_order parameter
+ 1.6. lost_held_query() usage
+ 1.7. lost() usage
Chapter 1. Admin Guide
@@ -59,6 +63,8 @@ Chapter 1. Admin Guide
3.1. exact_type (int)
3.2. response_time (int)
3.3. location_type (string)
+ 3.4. geoheader_type (int)
+ 3.5. geoheader_order (int)
4. Functions
@@ -131,6 +137,8 @@ Chapter 1. Admin Guide
3.1. exact_type (int)
3.2. response_time (int)
3.3. location_type (string)
+ 3.4. geoheader_type (int)
+ 3.5. geoheader_order (int)
Besides parameters listed, this module uses http_client therefore
according parameters may apply.
@@ -182,6 +190,40 @@ Chapter 1. Admin Guide
modparam("lost", "location_type, "civic geodetic locationURI")
...
+3.4. geoheader_type (int)
+
+ A Geolocation header may include a list of locationValues pointing to
+ either a Presence Information Data Format Location Object (PIDF-LO) in
+ the SIP body using a content-indirection (cid:) URI per RFC4483
+ (https://tools.ietf.org/html/rfc4483), or an http(s) URI pointing to an
+ external source. This parameter supports filtering of the following
+ types:
+ * 0 (any) - any URI (first or last)
+ * 1 (cid) - cid URI (aka Location-by-Value)
+ * 2 (http) - http URI (aka Location-by-Reference)
+ * 3 (https) - https URI (aka Location-by-Reference)
+
+ Default: 0 (any)
+
+ Example 1.4. Set geoheader_type parameter
+ ...
+ modparam("lost", "geoheader_type", 1)
+ ...
+
+3.5. geoheader_order (int)
+
+ A Geolocation header may include a list of locationValues. This
+ parameter sets the order of the URI used to retrieve location
+ information, either the first element of a certain type or the last.
+ Values are 0 (first) or 1 (last).
+
+ Default: 0 (first)
+
+ Example 1.5. Set geoheader_order parameter
+ ...
+ modparam("lost", "geoheader_order", 0)
+ ...
+
4. Functions
4.1. lost_held_query(con, [id,] pidf-lo, url, error)
@@ -210,7 +252,7 @@ Chapter 1. Admin Guide
This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE,
FAILURE_ROUTE, and BRANCH_ROUTE.
- Example 1.4. lost_held_query() usage
+ Example 1.6. lost_held_query() usage
...
modparam("http_client", "httpcon", "heldsrv=>http://service.org/api/held");
...
@@ -246,7 +288,7 @@ r(pidf)\n");
This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE,
FAILURE_ROUTE, and BRANCH_ROUTE.
- Example 1.5. lost() usage
+ Example 1.7. lost() usage
...
modparam("http_client", "httpcon", "heldsrv=>http://service.org/api/held");
modparam("http_client", "httpcon", "lostsrv=>http://service.org/api/lost");
@@ -307,3 +349,6 @@ var(name)\n");
Note: to test the module with a mapping service (LOST), an API key may
be requested under the following link (search for "GET ACCESS"):
https://gridgears.at/.
+
+ Note: in case modparam "geoheader_type" is set to 2 (http), the module
+ may use 3 (https) as fallback and vice versa.
Module: kamailio
Branch: master
Commit: f9f26adc11d96367a40947642b20bfdda246875e
URL: https://github.com/kamailio/kamailio/commit/f9f26adc11d96367a40947642b20bfd…
Author: Wolfgang Kampichler <dev(a)kampichler.info>
Committer: Wolfgang Kampichler <dev(a)kampichler.info>
Date: 2021-01-12T11:56:47+01:00
lost: added Geolocation header value list support
- the Geolocation header value parsing now supports
a list of location URIs of type (cid, http and https).
- types may be filtered and the list sequence may be
changed via new module parameters.
- besides: README update and code refactoring.
---
Modified: src/modules/lost/doc/lost_admin.xml
Modified: src/modules/lost/functions.c
Modified: src/modules/lost/lost.c
Modified: src/modules/lost/pidf.c
Modified: src/modules/lost/pidf.h
Modified: src/modules/lost/utilities.c
Modified: src/modules/lost/utilities.h
---
Diff: https://github.com/kamailio/kamailio/commit/f9f26adc11d96367a40947642b20bfd…
Patch: https://github.com/kamailio/kamailio/commit/f9f26adc11d96367a40947642b20bfd…