Module: kamailio
Branch: 5.7
Commit: c5a22a4bfc9310f41facf8dfe8aa9c610f432817
URL: https://github.com/kamailio/kamailio/commit/c5a22a4bfc9310f41facf8dfe8aa9c6…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-05-17T11:29:20+02:00
Makefile.defs: set LIBSSL_SET_MUTEX_SHARED by default to 1
- one can set LIBSSL_SET_MUTEX_SHARED=0 in make command line to switch
to detection mode if it is need to set it or not based on libssl
version
- GH #3458, GH #3384
(cherry picked from commit 5e0fb402a7755ea22c41c0b8fcefbdf9694442b8)
---
Modified: src/Makefile.defs
---
Diff: https://github.com/kamailio/kamailio/commit/c5a22a4bfc9310f41facf8dfe8aa9c6…
Patch: https://github.com/kamailio/kamailio/commit/c5a22a4bfc9310f41facf8dfe8aa9c6…
---
diff --git a/src/Makefile.defs b/src/Makefile.defs
index bd15e29269d..78a2dcc87ec 100644
--- a/src/Makefile.defs
+++ b/src/Makefile.defs
@@ -181,7 +181,7 @@ LD_EXTRA_OPTS ?=
# enable workaround for libssl 1.1+ to set shared mutex attribute
-LIBSSL_SET_MUTEX_SHARED ?=
+LIBSSL_SET_MUTEX_SHARED ?= 1
ifneq ($(LIBSSL_SET_MUTEX_SHARED), 1)
ifeq ($(CROSS_COMPILE),)
### Description
On systems running libssl 1.1+, the compile flag `TLS_PTHREAD_MUTEX_SHARED` is set to avoid an issue with deadlocks. However, if the system does not have `pkg-config` installed, the build completes successfully without setting this compile flag. As such, users with this particular configuration are at risk of TLS-related deadlocks.
### Troubleshooting
This scenario arose for me when I experienced suspected TLS-related deadlocks in Kamailio 5.4.1. Particularly, in a simple configuration, multiple UDP workers were using t_relay to near-simultaneously connect to the same TLS host. After some time, the UDP workers stopped responding while executing this simple route block. I cannot definitively conclude this issue was the same deadlock bug. The compile flag `TLS_PTHREAD_MUTEX_SHARED` was not set and `pkg-config` was not installed.
I found [this mailing list thread](https://lists.kamailio.org/pipermail/sr-users/2019-December/107759.… discussing TLS deadlocks and the build process and the user was running Kamailio 5.3.1, libssl 1.1 but did not have `TLS_PTHREAD_MUTEX_SHARED` set. This issue may explain how this user ended up in that situation.
#### Reproduction
Tested against Kamailio 5.4.1 and latest master.
On a system with libssl 1.1+, build (including the `tls` module) with `pkg-config` installed and run `kamailio -I`. `TLS_PTHREAD_MUTEX_SHARED` flag is set.
```
Version: kamailio 5.7.0-dev3 (x86_64/linux) b75b6e
Default config: /usr/local/etc/kamailio/kamailio.cfg
Default paths to modules: /usr/local/lib64/kamailio/modules
Compile flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED
```
Uninstall `pkg-config` and rebuild. `TLS_PTHREAD_MUTEX_SHARED` flag is not set.
```
Version: kamailio 5.7.0-dev3 (x86_64/linux) b75b6e
Default config: /usr/local/etc/kamailio/kamailio.cfg
Default paths to modules: /usr/local/lib64/kamailio/modules
Compile flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, 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_BLOCKLIST, HAVE_RESOLV_RES
```
When `pkg-config` is not installed, the build also outputs the following log lines, however the build does not fail.
```
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
/bin/sh: 1: pkg-config: not found
```
### Possible Solutions
Some thoughts about options:
1. It looks like effort has been applied in other areas to support the absence of `pkg-config`, so potentially support libssl 1.1+ detection without `pkg-config`.
2. Require `pkg-config` on build and fail without it.
3. Enable `TLS_PTHREAD_MUTEX_SHARED` by default as I assume most people are running libssl 1.1+ these days, and disable it if libssl < 1.1 detected.
Personally I have installed `pkg-config` and rebuilt, however I think for the safety of others building from source that the compile flag should be correctly set or the build should fail.
### Operating System
```
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
Linux debian-kamailio 4.19.0-20-amd64 #1 SMP Debian 4.19.235-1 (2022-03-17) x86_64 GNU/Linux
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3384
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3384(a)github.com>
The current build of kamailio (master) does not set `TLS_PTHREAD_MUTEX_SHARED` when building with `--with-openssl11` on systems with multiple versions of OpenSSL installed resulting in deadlocks in the TLS module.
All module Makefiles look for the `SSL_BUILDER` environment variable to provide a `pkg-config` command to find the `libssl` to link against. The variable is set to `pkg-config libssl11` by the RPM build when specifying `--with-openssl11`. Unfortunately, in `src/Makefile.defs`, there is an alternative way to look for a similar `pkg-config` command. However, this one always uses the `pkg-config libssl`, which - on systems with multiple versions of OpenSSL - usually points to OpenSSL 1.0.x. In turn the build thinks it will link against OpenSSL 1.0.x and will not set `KSR_PTHREAD_MUTEX_SHARED`.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3458
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3458(a)github.com>
Module: kamailio
Branch: master
Commit: 5e0fb402a7755ea22c41c0b8fcefbdf9694442b8
URL: https://github.com/kamailio/kamailio/commit/5e0fb402a7755ea22c41c0b8fcefbdf…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-05-17T11:24:58+02:00
Makefile.defs: set LIBSSL_SET_MUTEX_SHARED by default to 1
- one can set LIBSSL_SET_MUTEX_SHARED=0 in make command line to switch
to detection mode if it is need to set it or not based on libssl
version
- GH #3458, GH #3384
---
Modified: src/Makefile.defs
---
Diff: https://github.com/kamailio/kamailio/commit/5e0fb402a7755ea22c41c0b8fcefbdf…
Patch: https://github.com/kamailio/kamailio/commit/5e0fb402a7755ea22c41c0b8fcefbdf…
---
diff --git a/src/Makefile.defs b/src/Makefile.defs
index a40cfa55cd3..ca7d525b688 100644
--- a/src/Makefile.defs
+++ b/src/Makefile.defs
@@ -181,7 +181,7 @@ LD_EXTRA_OPTS ?=
# enable workaround for libssl 1.1+ to set shared mutex attribute
-LIBSSL_SET_MUTEX_SHARED ?=
+LIBSSL_SET_MUTEX_SHARED ?= 1
ifneq ($(LIBSSL_SET_MUTEX_SHARED), 1)
ifeq ($(CROSS_COMPILE),)
th_mask_callid_str & th_unmask_callid_str functions used for API call to encode/decode call-ID uses static array declaration for callid_mbuf was unable to free callid data lump after use and leads to memory leak. when these functions was used through API call for topos module memory leak bug as reported
qm_free(): BUG: bad pointer 0x7faec4a7xxxx (out of memory block!) called from core: core/data_lump.c: free_lump(470)
This two funtions are not used other than API.
<!-- 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 -->
- [ ] 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:
<!-- 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/3456
-- Commit Summary --
* topoh: memory leak fix for API call
-- File Changes --
M src/modules/topoh/th_msg.c (36)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3456.patchhttps://github.com/kamailio/kamailio/pull/3456.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3456
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3456(a)github.com>
**incompatible-pointer-types**
```
make[3]: 'libsrdb1.so.1.0' is up to date.
LD (gcc) [M sipcapture.so] sipcapture.so
CC (gcc) [M siptrace.so] siptrace.o
siptrace.c: In function 'ki_sip_trace_msg':
siptrace.c:1234:74: warning: passing argument 4 of 'trace_send_hep_duplicate' from incompatible pointer type [-Wincompatible-pointer-types]
trace_send_hep_duplicate(vmsg, saddr, taddr, (duri && duri->len>0)?&duri:NULL,
^
In file included from siptrace.c:58:
siptrace_hep.h:30:34: note: expected 'struct dest_info *' but argument is of type 'str **' {aka 'struct _str **'}
str *body, str *from, str *to, struct dest_info *, str *correlation_id);
^~~~~~~~~~~~~~~~~~
CC (gcc) [M siptrace.so] siptrace_hep.o
CC (gcc) [M siptrace.so] siptrace_send.o
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3457
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3457(a)github.com>
Hello,
with a few public holidays coming soon around here, I am considering to
release 5.7.0 this week on Wednesday, May 17, 2023. Rather short notice,
but there were no major bug reports that need to be tracked.
The list of new features is being built in the wiki:
 -
https://github.com/kamailio/kamailio-wiki/blob/main/docs/features/new-in-5.…
The other tutorials related to this major release should be ready by
then as well.
Should anyone think more time is needed, then it can be postponed, not a
problem at all.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com
Module: kamailio
Branch: 5.7
Commit: 422d469fb52c31074ff00eec445eff45fdfebb39
URL: https://github.com/kamailio/kamailio/commit/422d469fb52c31074ff00eec445eff4…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2023-05-16T18:16:35+02:00
modules: readme files regenerated - modules ... [skip ci]
---
Modified: src/modules/topos/README
---
Diff: https://github.com/kamailio/kamailio/commit/422d469fb52c31074ff00eec445eff4…
Patch: https://github.com/kamailio/kamailio/commit/422d469fb52c31074ff00eec445eff4…
---
diff --git a/src/modules/topos/README b/src/modules/topos/README
index 1f8e8c191dd..be21cb2ef51 100644
--- a/src/modules/topos/README
+++ b/src/modules/topos/README
@@ -171,6 +171,7 @@ Chapter 1. Admin Guide
requests).
* database module - to store the data for topology stripping and
restoring.
+ * topoh module - in case of Call-ID mask for Call-ID masking.
2.2. External Libraries or Applications
@@ -228,11 +229,11 @@ modparam("topos", "db_url", "dbdriver://username:password@dbhost/dbname")
3.3. mask_callid (int)
- Note: this functionality is not implemented yet - the parameter is
- present in order to be in pair with topoh module.
-
- Whether to replace or not the Call-ID with another unique id generated
- by Kamailio.
+ Whether to encode the Call-id: header. Some SIP extensions include the
+ Call-id in the SIP message payload or header, so it is safe to not
+ encode Call-id in such cases. Well-known extensions such as call
+ transfer or conference join will be added to work with encoded Call-id.
+ Topoh module should be loaded with use_mode paramerter set to 1
Default value is 0 (do not mask).
Module: kamailio
Branch: 5.7
Commit: 7e1f330e2dc916138aa9a899da49c452b9f59740
URL: https://github.com/kamailio/kamailio/commit/7e1f330e2dc916138aa9a899da49c45…
Author: harish <toharishs(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-05-16T18:03:54+02:00
Topos: Added CallID Mask Document for Topos
Added document for Call-ID Mask in Topos Module
(cherry picked from commit 14d4b2422c0fed27fecf01665197f9d0669aa24e)
---
Modified: src/modules/topos/doc/topos_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/7e1f330e2dc916138aa9a899da49c45…
Patch: https://github.com/kamailio/kamailio/commit/7e1f330e2dc916138aa9a899da49c45…
---
diff --git a/src/modules/topos/doc/topos_admin.xml b/src/modules/topos/doc/topos_admin.xml
index dcf61a0fed6..82e7c1e45eb 100644
--- a/src/modules/topos/doc/topos_admin.xml
+++ b/src/modules/topos/doc/topos_admin.xml
@@ -57,6 +57,12 @@
for topology stripping and restoring.
</para>
</listitem>
+ <listitem>
+ <para>
+ <emphasis>topoh module</emphasis> - in case of Call-ID mask
+ for Call-ID masking.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</section>
@@ -130,14 +136,14 @@ modparam("topos", "db_url", "&exampledb;")
<section id="topos.p.mask_callid">
<title><varname>mask_callid</varname> (int)</title>
<para>
- Note: this functionality is not implemented yet - the
- parameter is present in order to be in pair with topoh
- module.
- </para>
- <para>
- Whether to replace or not the Call-ID with another
- unique id generated by &kamailio;.
+ Whether to encode the Call-id: header. Some SIP extensions include
+ the Call-id in the SIP message payload or header, so it is safe to
+ not encode Call-id in such cases. Well-known extensions such as
+ call transfer or conference join will be added to work with encoded
+ Call-id.
+ Topoh module should be loaded with use_mode paramerter set to 1
</para>
+
<para>
<emphasis>
Default value is 0 (do not mask).
### Description
I'm noticing an issue with certain RPC after upgrading to 5.6. I'm using "db_postgres".
If I run ul.flush like this:
```
kamcmd ul.flush
# no output
```
None of the in-memory registrations are flushed to the DB and in the log I see a bunch of lines like this:
```
May 12 20:39:16 <dummy-hostname> /usr/sbin/kamailio[9006]: ERROR: <core> [db.c:481]: db_use_table(): invalid connection parameter
May 12 20:39:16 <dummy-hostname> /usr/sbin/kamailio[9006]: ERROR: usrloc [ucontact.c:1142]: db_update_ucontact_ruid(): sql use_table failed
May 12 20:39:16 <dummy-hostname> /usr/sbin/kamailio[9006]: ERROR: usrloc [urecord.c:433]: wb_timer(): updating contact in db failed (aor: fake-1(a)aor.com)
May 12 20:39:16 <dummy-hostname> /usr/sbin/kamailio[9006]: ERROR: <core> [db.c:481]: db_use_table(): invalid connection parameter
May 12 20:39:16 <dummy-hostname> /usr/sbin/kamailio[9006]: ERROR: usrloc [ucontact.c:1142]: db_update_ucontact_ruid(): sql use_table failed
May 12 20:39:16 <dummy-hostname> /usr/sbin/kamailio[9006]: ERROR: usrloc [urecord.c:433]: wb_timer(): updating contact in db failed (aor: fake-2(a)aor.com)
```
I see the same thing with ul.db_users:
```
kamcmd ul.db_users location
# returns the following output
error: 500 - Failed to use table
# in the log
ERROR: <core> [db.c:481]: db_use_table(): invalid connection parameter
```
### Troubleshooting
#### Reproduction
Seems to happen consistently on 5.6, using psql as the db engine. I tested on 5.4 and it's not happening.
It's easier to test with ```kamcmd ul.db_users location``` because you need registrations that haven't been flushed to the DB for the error to manifest.
* **Operating System**:
```
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
Kernel:
4.19.0-21-cloud-amd64
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3452
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3452(a)github.com>
Module: kamailio
Branch: master
Commit: 3823056e55db45831abc584a7df2b8998c18cf10
URL: https://github.com/kamailio/kamailio/commit/3823056e55db45831abc584a7df2b89…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2023-05-16T14:16:33+02:00
modules: readme files regenerated - usrloc ... [skip ci]
---
Modified: src/modules/usrloc/README
---
Diff: https://github.com/kamailio/kamailio/commit/3823056e55db45831abc584a7df2b89…
Patch: https://github.com/kamailio/kamailio/commit/3823056e55db45831abc584a7df2b89…
---
diff --git a/src/modules/usrloc/README b/src/modules/usrloc/README
index 2eedbf74dc..00b0743e9a 100644
--- a/src/modules/usrloc/README
+++ b/src/modules/usrloc/README
@@ -1305,7 +1305,9 @@ modparam("usrloc", "db_clean_tcp", 1)
4.5. ul.flush
- Triggers the flush of USRLOC memory cache into DB.
+ Triggers the flush of USRLOC memory cache into DB from the RPC process.
+ It succeeds only if the the db_mode is set to a value that enables
+ connectivity to database.
4.6. ul.add
Module: kamailio
Branch: master
Commit: f4deff8d064e9931fd4ee4fe1bbe166901e7c617
URL: https://github.com/kamailio/kamailio/commit/f4deff8d064e9931fd4ee4fe1bbe166…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-05-16T14:07:22+02:00
usrloc: docs updated for ul.flush to indicate it depends on db mode
---
Modified: src/modules/usrloc/doc/usrloc_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/f4deff8d064e9931fd4ee4fe1bbe166…
Patch: https://github.com/kamailio/kamailio/commit/f4deff8d064e9931fd4ee4fe1bbe166…
---
diff --git a/src/modules/usrloc/doc/usrloc_admin.xml b/src/modules/usrloc/doc/usrloc_admin.xml
index ca2295ac67a..61491648a0c 100644
--- a/src/modules/usrloc/doc/usrloc_admin.xml
+++ b/src/modules/usrloc/doc/usrloc_admin.xml
@@ -1633,7 +1633,9 @@ modparam("usrloc", "db_clean_tcp", 1)
<function moreinfo="none">ul.flush</function>
</title>
<para>
- Triggers the flush of USRLOC memory cache into DB.
+ Triggers the flush of USRLOC memory cache into DB from the RPC process. It
+ succeeds only if the the db_mode is set to a value that enables connectivity
+ to database.
</para>
</section>
<section id="usrloc.r.add">
Module: kamailio
Branch: master
Commit: f5f681c43a4736e4ec3ce5f16e11e61305384d79
URL: https://github.com/kamailio/kamailio/commit/f5f681c43a4736e4ec3ce5f16e11e61…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2023-05-16T13:31:19+02:00
modules: readme files regenerated - topos ... [skip ci]
---
Modified: src/modules/topos/README
---
Diff: https://github.com/kamailio/kamailio/commit/f5f681c43a4736e4ec3ce5f16e11e61…
Patch: https://github.com/kamailio/kamailio/commit/f5f681c43a4736e4ec3ce5f16e11e61…
---
diff --git a/src/modules/topos/README b/src/modules/topos/README
index 1f8e8c191d..be21cb2ef5 100644
--- a/src/modules/topos/README
+++ b/src/modules/topos/README
@@ -171,6 +171,7 @@ Chapter 1. Admin Guide
requests).
* database module - to store the data for topology stripping and
restoring.
+ * topoh module - in case of Call-ID mask for Call-ID masking.
2.2. External Libraries or Applications
@@ -228,11 +229,11 @@ modparam("topos", "db_url", "dbdriver://username:password@dbhost/dbname")
3.3. mask_callid (int)
- Note: this functionality is not implemented yet - the parameter is
- present in order to be in pair with topoh module.
-
- Whether to replace or not the Call-ID with another unique id generated
- by Kamailio.
+ Whether to encode the Call-id: header. Some SIP extensions include the
+ Call-id in the SIP message payload or header, so it is safe to not
+ encode Call-id in such cases. Well-known extensions such as call
+ transfer or conference join will be added to work with encoded Call-id.
+ Topoh module should be loaded with use_mode paramerter set to 1
Default value is 0 (do not mask).
Added Call-ID mask Support for Topos with API call from Topoh to mask the callID
Call-ID mask happens before the request is sent downstream and unmasked when received from downstream.
<!-- 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, ...)
- [ ] 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:
<!-- 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/3347
-- Commit Summary --
* Topos: Added Call ID mask when sending to Downstream
* Topos: Added CallID Mask Document for Topos
-- File Changes --
M src/modules/topos/doc/topos_admin.xml (20)
M src/modules/topos/topos_mod.c (119)
M src/modules/topos/tps_msg.c (37)
M src/modules/topos/tps_msg.h (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3347.patchhttps://github.com/kamailio/kamailio/pull/3347.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3347
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3347(a)github.com>
Module: kamailio
Branch: master
Commit: 14d4b2422c0fed27fecf01665197f9d0669aa24e
URL: https://github.com/kamailio/kamailio/commit/14d4b2422c0fed27fecf01665197f9d…
Author: harish <toharishs(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-05-16T13:17:44+02:00
Topos: Added CallID Mask Document for Topos
Added document for Call-ID Mask in Topos Module
---
Modified: src/modules/topos/doc/topos_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/14d4b2422c0fed27fecf01665197f9d…
Patch: https://github.com/kamailio/kamailio/commit/14d4b2422c0fed27fecf01665197f9d…
---
diff --git a/src/modules/topos/doc/topos_admin.xml b/src/modules/topos/doc/topos_admin.xml
index dcf61a0fed6..82e7c1e45eb 100644
--- a/src/modules/topos/doc/topos_admin.xml
+++ b/src/modules/topos/doc/topos_admin.xml
@@ -57,6 +57,12 @@
for topology stripping and restoring.
</para>
</listitem>
+ <listitem>
+ <para>
+ <emphasis>topoh module</emphasis> - in case of Call-ID mask
+ for Call-ID masking.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</section>
@@ -130,14 +136,14 @@ modparam("topos", "db_url", "&exampledb;")
<section id="topos.p.mask_callid">
<title><varname>mask_callid</varname> (int)</title>
<para>
- Note: this functionality is not implemented yet - the
- parameter is present in order to be in pair with topoh
- module.
- </para>
- <para>
- Whether to replace or not the Call-ID with another
- unique id generated by &kamailio;.
+ Whether to encode the Call-id: header. Some SIP extensions include
+ the Call-id in the SIP message payload or header, so it is safe to
+ not encode Call-id in such cases. Well-known extensions such as
+ call transfer or conference join will be added to work with encoded
+ Call-id.
+ Topoh module should be loaded with use_mode paramerter set to 1
</para>
+
<para>
<emphasis>
Default value is 0 (do not mask).
Hi,
we've come around to test again what happens if we set 'core.shmem' to a size larger than 4G. The original issue has been reported here #2824. We are running Kamailio 5.6 at commit `24989241cfc58c6ba47d48c9a86921251f4ba235`
We are querying the `core.shmen` parameter via RPC and getting the following response from the server:
```
<?xml version="1.0"?>
<methodResponse>
<params>
<param>
<value><struct><member><name>total</name><value><int>-80</int></value></member><member><name>free</name><value><int>-66333776</int></value></member><member><name>used</name><value><int>63570392</int></value></member><member><name>real_used</name><value><int>66333696</int></value></member><member><name>max_used</name><value><int>68268896</int></value></member><member><name>fragments</name><value><int>2560</int></value></member></struct>
</value>
</param>
</params>
</methodResponse>
```
As you can see, the issue still persists.
Thanks
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3450
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3450(a)github.com>
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3454
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3454(a)github.com>
ob_load_api(): unable to import bind_ob --> even after including "outbound" module
sctp_core_check_support(): SCTP API not enabled --> even after including "sctp" module
db_check_table_version(): invalid version 4 for table presentity found, expected 5
Docker File
FROM debian:11
#MAINTAINER Yan Grunenberger <yan(a)grunenberger.net>
ENV DEBIAN_FRONTEND noninteractive
RUN apt-get -o Acquire::Check-Valid-Until=false update
RUN apt-get -yq update
RUN apt-get -yq dist-upgrade
RUN apt-get -yq install git-core
RUN apt-get -yq install gcc
RUN apt-get -yq install flex
RUN apt-get -yq install bison
RUN apt-get -yq install default-libmysqlclient-dev
RUN apt-get -yq install make
RUN apt-get -yq install g++
RUN apt-get -yq install libssl-dev
RUN apt-get -yq install libcurl4-openssl-dev
RUN apt-get -yq install libsctp-dev lksctp-tools
RUN apt-get -yq install libxml2-dev
RUN apt-get -yq install libc6-i386
RUN apt-get -yq install libpcre3-dev
RUN apt-get -yq install build-essential libxslt-dev zip unzip expat zlib1g-dev curl libncurses5-dev libexpat1-dev
RUN apt-get -yq install htmldoc rpm
RUN mkdir -p /usr/local/src/kamailio-master
WORKDIR /usr/local/src/kamailio-master
RUN git clone https://github.com/kamailio/kamailio.git
WORKDIR /usr/local/src/kamailio-master/kamailio
RUN git checkout -b 5.6.2
#RUN make include_modules="db_mysql ims_usrloc_pcscf ims_registrar_pcscf" cfg
RUN make include_modules="db_mysql ims_usrloc_pcscf ims_registrar_pcscf xmlrpc cdp cdp_avp ims_icscf presence ims_usrloc_scscf ims_registrar_scscf ims_auth ims_charging ims_dialog ims_diameter_server ims_isc ims_ocs ims_qos outbound dispatcher" cfg
RUN make all
RUN make install
RUN apt-get -yq install default-mysql-client
#RUN apt-get -yq install mysql-client
ENTRYPOINT ["/usr/local/sbin/kamailio","-f","/usr/local/etc/kamailio/kamailio-scscf.cfg","-D"]
Getting Below error :
docker-IMS-VoLTE$ sudo docker logs 3e61c85f59b7
0(1) INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module
WARNING: no fork mode
0(1) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded
0(1) INFO: rr [rr_mod.c:188]: mod_init(): outbound module not available
0(1) ERROR: <core> [db.c:466]: db_check_table_version(): invalid version 4 for table presentity found, expected 5 (check table structure and table "version")
0(1) ERROR: presence [presence.c:421]: mod_init(): Error during version check for db table: presentity, check database structure.
0(1) ERROR: <core> [core/sr_module.c:993]: init_mod(): Error while initializing module presence (/usr/local/lib64/kamailio/modules/presence.so)
ERROR: error while initializing modules
0(1) WARNING: <core> [core/mem/q_malloc.c:487]: qm_free(): WARNING: free(0) called from cdp_avp: cdp_avp_mod.c: cdp_avp_destroy(226)
0(1) INFO: cdp [cdp_mod.c:255]: cdp_exit(): CDiameterPeer child stopping ...
0(1) INFO: cdp [cdp_mod.c:257]: cdp_exit(): ... CDiameterPeer child stopped
0(1) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
loading modules under config path: /usr/local/lib64/kamailio/modules/
Listening on
udp: scscf.net1.test [172.18.0.3]:6060
Aliases:
*: scscf.net1.test:*
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3455
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3455(a)github.com>
FHOSS
DOCKER File
FROM debian:11
#MAINTAINER Yan Grunenberger <yan(a)grunenberger.net>
ENV DEBIAN_FRONTEND noninteractive
RUN apt-get -o Acquire::Check-Valid-Until=false update
RUN apt-get -yq update
RUN apt-get -yq dist-upgrade
RUN apt-get -yq install -f
RUN apt-get -qy install ant
RUN apt-get -qy install subversion
RUN apt-get -yq install libc6-i386
RUN apt-get -yq install dos2unix
RUN apt-get -yq install software-properties-common
RUN apt-get -yq install wget -y
RUN wget https://d3pxv6yz143wms.cloudfront.net/8.212.04.2/java-1.8.0-amazon-corretto… && \
apt-get update && apt-get install java-common && apt-get install -y --no-install-recommends apt-utils && \
dpkg --install java-1.8.0-amazon-corretto-jdk_8.212.04-2_amd64.deb
ENV JAVA_HOME /usr/lib/jvm/java-1.8.0-amazon-corretto
ENV PATH $JAVA_HOME/bin:$PATH
RUN mkdir -p /opt/OpenIMSCore
WORKDIR /opt/OpenIMSCore
RUN svn checkout svn://svn.code.sf.net/p/openimscore/code/FHoSS/trunk FHoSS
WORKDIR /opt/OpenIMSCore/FHoSS
RUN JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF8 ant compile deploy
ENTRYPOINT ["sh", "/root/run.sh"]
**run.sh**
#!/bin/bash
# Starting HSS
/bin/pwd -P
cd /opt/OpenIMSCore/FHoSS/deploy || exit
echo "$PATH"
echo "$JAVA_HOME"
echo "Building Classpath"
CLASSPATH=$CLASSPATH:log4j.properties:.
for i in lib/*.jar; do CLASSPATH="$i":"$CLASSPATH"; done
echo "Classpath is $CLASSPATH."
$JAVA_HOME/bin/java -cp $CLASSPATH de.fhg.fokus.hss.main.HSSContainer $1 $2 $3 $4 $5 $6 $7 $8 $9
I'm getting below error.
ubuntu@ip-172-31-10-118:~/docker-IMS-VoLTE$ sudo docker logs 31f6119eb481
/bin/pwd: ignoring non-option arguments
/opt/OpenIMSCore/FHoSS
/usr/lib/jvm/java-1.8.0-amazon-corretto/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
**/root/run.sh: 27: Syntax error: end of file unexpected (expecting "done")**
/usr/lib/jvm/jdk-20
Building Classpath
Where Syntax seems okay & JAVA_HOME="/usr/lib/jvm/java-8-openjdk-amd64/" -> this was not passing directlt because of Debian version 11.
Please Suggest.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3453
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3453(a)github.com>
Module: kamailio
Branch: master
Commit: 7f2d55ce62783536f4c5c28a5935d9c3b20da311
URL: https://github.com/kamailio/kamailio/commit/7f2d55ce62783536f4c5c28a5935d9c…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2023-05-15T23:01:09+02:00
modules: readme files regenerated - tls_wolfssl ... [skip ci]
---
Modified: src/modules/tls_wolfssl/README
---
Diff: https://github.com/kamailio/kamailio/commit/7f2d55ce62783536f4c5c28a5935d9c…
Patch: https://github.com/kamailio/kamailio/commit/7f2d55ce62783536f4c5c28a5935d9c…
---
diff --git a/src/modules/tls_wolfssl/README b/src/modules/tls_wolfssl/README
index bffec53ba4..29db26c237 100644
--- a/src/modules/tls_wolfssl/README
+++ b/src/modules/tls_wolfssl/README
@@ -64,6 +64,10 @@ loadmodule "tls_wolfssl.so"
The wolfSSL TLS module is intended to be compiled with a recent version
of wolfSSL (5.2.0+).
+ Default compilations of the library will not work with Kamailio's own
+ memory allocation. See https://github.com/wolfSSL/wolfssl/issues/5264
+ for more details.
+
4. Compiling the wolfSSL TLS Module
The development package for wolfSSL is required (libwolfssl-dev or