Hi `kamailio/kamailio`!
This is a one-off automatically generated pull request from LGTM.com :robot:. You might have heard that we’ve integrated LGTM’s underlying CodeQL analysis engine natively into GitHub. The result is [**GitHub code scanning**](https://docs.github.com/en/code-security/code-scanning/automati…!
With LGTM fully integrated into code scanning, we are focused on improving CodeQL within the native GitHub code scanning experience. In order to take advantage of current and future improvements to our analysis capabilities, we suggest you enable code scanning on your repository. Please take a look at our [blog post for more information](https://github.blog/2022-08-15-the-next-step-for-lgtm-com-github-code-scanning/).
This pull request enables code scanning by adding an auto-generated [`codeql.yml` workflow file for GitHub Actions](https://docs.github.com/en/code-security/code-scanning/automatical… to your repository — take a look! We tested it before opening this pull request, so all should be working :heavy_check_mark:. In fact, you might already have seen some alerts appear on this pull request!
Where needed and if possible, we’ve adjusted the configuration to the needs of your particular repository. But of course, you should feel free to tweak it further! Check [this page](https://docs.github.com/en/code-security/code-scanning/automatically-… for detailed documentation.
Questions? Check out the FAQ below!
### FAQ
<details>
<summary>Click here to expand the FAQ section</summary>
#### How often will the code scanning analysis run?
By default, code scanning will trigger a scan with the CodeQL engine on the following events:
* On every pull request — to flag up potential security problems for you to investigate before merging a PR.
* On every push to your default branch and other protected branches — this keeps the analysis results on your repository’s *Security* tab up to date.
* Once a week at a fixed time — to make sure you benefit from the latest updated security analysis even when no code was committed or PRs were opened.
#### What will this cost?
Nothing! The CodeQL engine will run inside GitHub Actions, making use of your [unlimited free compute minutes for public repositories](https://docs.github.com/en/actions/learn-github-actions/usage….
#### What types of problems does CodeQL find?
The CodeQL engine that powers GitHub code scanning is the exact same engine that powers LGTM.com. The exact set of rules has been tweaked slightly, but you should see almost exactly the same types of alerts as you were used to on LGTM.com: we’ve enabled the [`security-and-quality` query suite](https://docs.github.com/en/code-security/code-scanning/automatically… for you.
#### How do I upgrade my CodeQL engine?
No need! New versions of the CodeQL analysis are constantly deployed on GitHub.com; your repository will automatically benefit from the most recently released version.
#### The analysis doesn’t seem to be working
If you get an error in GitHub Actions that indicates that CodeQL wasn’t able to analyze your code, please [follow the instructions here](https://docs.github.com/en/code-security/code-scanning/automatically-… to debug the analysis.
#### How do I disable LGTM.com?
If you have LGTM’s automatic pull request analysis enabled, then you can [follow these steps to disable the LGTM pull request analysis](https://lgtm.com/help/lgtm/managing-automated-code-review#disabli…. You don’t actually need to remove your repository from LGTM.com; it will automatically be removed in the next few months as part of the deprecation of LGTM.com ([more info here](https://github.blog/2022-08-15-the-next-step-for-lgtm-com-github-code-scanning/)).
#### Which source code hosting platforms does code scanning support?
GitHub code scanning is deeply integrated within GitHub itself. If you’d like to scan source code that is hosted elsewhere, we suggest that you create a mirror of that code on GitHub.
#### How do I know this PR is legitimate?
This PR is filed by the official LGTM.com GitHub App, in line with the [deprecation timeline that was announced on the official GitHub Blog](https://github.blog/2022-08-15-the-next-step-for-lgtm-com-github-code-scanning/). The proposed GitHub Action workflow uses the [official open source GitHub CodeQL Action](https://github.com/github/codeql-action/). If you have any other questions or concerns, please join the discussion [here](https://github.com/orgs/community/discussions/29534) in the official GitHub community!
#### I have another question / how do I get in touch?
Please join the discussion [here](https://github.com/orgs/community/discussions/29534) to ask further questions and send us suggestions!
</details>
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3295
-- Commit Summary --
* Add CodeQL workflow for GitHub code scanning
-- File Changes --
A .github/workflows/codeql.yml (62)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3295.patchhttps://github.com/kamailio/kamailio/pull/3295.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3295
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3295(a)github.com>
As of openssl 1.1.1s SSL_load_error_strings(); exists only in this form in include/openssl/ssl.h:
```c
# if OPENSSL_API_COMPAT < 0x10100000L
# define SSL_load_error_strings() \
OPENSSL_init_ssl(OPENSSL_INIT_LOAD_SSL_STRINGS \
| OPENSSL_INIT_LOAD_CRYPTO_STRINGS, NULL)
# endif
```
It does not exist, when OPENSSL_API_COMPAT == 0x10100000L. When openssl is ./Configure’d with `no-deprecated`then OPENSSL_API_COMPAT is set in include/openssl/opensslconf.h to OPENSSL_MIN_API=0x10100000L. That is: when OpenSSL 1.1.1s is `./Configure no-deprecated`, the macro SSL_load_error_strings() does not exist, but tls_h_mod_pre_init_f() calls it. This might or might not help:
```diff
diff --git a/src/modules/tls/tls_init.c b/src/modules/tls/tls_init.c
index 4c858bbbd8..784168c6f7 100644
--- a/src/modules/tls/tls_init.c
+++ b/src/modules/tls/tls_init.c
@@ -647,8 +647,8 @@ int tls_h_mod_pre_init_f(void)
#else
LM_DBG("preparing tls env for modules initialization (libssl <=1.0)\n");
SSL_library_init();
-#endif
SSL_load_error_strings();
+#endif
tls_mod_preinitialized=1;
return 0;
}
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/6df13e614cf6898b6d67f36c9b185a7…
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/commit/6df13e614cf6898b6d67f36c9b185a7530102ef1/92954312(a)github.com>
stirshaken: Properly handle intermediary/chain certificates when caching certificates
- requires patch to libstirshaken (https://github.com/signalwire/libstirshaken/pull/124) to do anything
- if patched version of libstirshaken detected, uses new methods to store all intermediary certs
- unrelated minor logging tweaks
<!-- 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
- [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:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [x] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
The guts of this PR have been submitted to the libstirshaken side based on the suggestions of my previous PR. I didn't mean to close it but since I hadn't created a branch, it got closed when I updated my repo. Original PR is https://github.com/kamailio/kamailio/pull/3175
I've been running this in production for a day and it seems to be performing the same as my previous attempt.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3289
-- Commit Summary --
* stirshaken: Properly handle intermediary/chain certificates when caching certificates
-- File Changes --
M src/modules/stirshaken/stirshaken_mod.c (24)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3289.patchhttps://github.com/kamailio/kamailio/pull/3289.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3289
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3289(a)github.com>
Hi,
the new module app_python3s is causing compilation issues, probably needs to be included in the exclude list:
$ make cfg
$ make all
make[2]: python3.8-config: Command not found
CC (gcc) [M app_python3s.so] apy3s_exception.o
apy3s_exception.c:22:10: fatal error: Python.h: No such file or directory
22 | #include <Python.h>
| ^~~~~~~~~~
compilation terminated.
Thanks,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com<https://gilawa.com/>
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3298
-- Commit Summary --
* Typos: withing → within
-- File Changes --
M doc/tutorials/presence/cfg/full_ps.cfg (2)
M doc/tutorials/presence/cfg/ps.cfg (2)
M etc/kamailio.cfg (2)
M etc/sip-router.cfg (2)
M misc/examples/ims/pcscf/kamailio.cfg (2)
M misc/examples/kamailio/acc-mysql.cfg (2)
M misc/examples/kamailio/nathelper.cfg (2)
M misc/examples/kemi/kamailio-basic-kemi-jsdt.js (2)
M misc/examples/kemi/kamailio-basic-kemi-lua.lua (2)
M misc/examples/kemi/kamailio-basic-kemi-native.cfg (2)
M misc/examples/kemi/kamailio-basic-kemi-python.py (2)
M misc/examples/kemi/kamailio-basic-kemi-python3s.py (2)
M misc/examples/kemi/kamailio-basic-kemi-sqlang.sq (2)
M misc/examples/mixed/kamailio-minimal-anycast.cfg (2)
M misc/examples/mixed/kamailio-minimal-proxy.cfg (2)
M misc/examples/mixed/nathelper.cfg (2)
M misc/examples/pkg/kamailio-basic.cfg (2)
M misc/examples/pkg/kamailio-oob.cfg (2)
M misc/examples/pkg/sip-router-basic.cfg (2)
M misc/examples/pkg/sip-router-oob.cfg (2)
M misc/examples/presence/full-no-failover.cfg (2)
M misc/examples/presence/no-db.cfg (2)
M misc/examples/webrtc/kamailio-default-websocket.cfg (2)
M misc/examples/webrtc/websocket.cfg (2)
M src/modules/app_java/kamailio_java_folder/java-untested/Kamailio.java (2)
M src/modules/cnxcc/example/kamailio-cnxcc.cfg (2)
M src/modules/db_cassandra/kamailio_cassa.cfg (2)
M src/modules/db_text/README (2)
M src/modules/db_text/doc/db_text.cfg (2)
M src/modules/dispatcher/README (2)
M src/modules/dispatcher/doc/dispatcher.cfg (2)
M src/modules/sca/README (2)
M src/modules/sca/doc/sca.cfg (2)
M src/modules/websocket/README (2)
M src/modules/websocket/doc/websocket_admin.xml (2)
M src/modules/xprint/xp_lib.c (2)
M test/unit/5.cfg (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3298.patchhttps://github.com/kamailio/kamailio/pull/3298.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3298
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3298(a)github.com>
Module: kamailio
Branch: master
Commit: b6d4d057a01d29cf9499788432fc9d00ad4737f8
URL: https://github.com/kamailio/kamailio/commit/b6d4d057a01d29cf9499788432fc9d0…
Author: Henning Westerholt <hw(a)gilawa.com>
Committer: Henning Westerholt <hw(a)gilawa.com>
Date: 2022-12-11T10:19:55Z
db_text: spelling fix withing -> within
---
Modified: src/modules/db_text/doc/db_text.cfg
---
Diff: https://github.com/kamailio/kamailio/commit/b6d4d057a01d29cf9499788432fc9d0…
Patch: https://github.com/kamailio/kamailio/commit/b6d4d057a01d29cf9499788432fc9d0…
---
diff --git a/src/modules/db_text/doc/db_text.cfg b/src/modules/db_text/doc/db_text.cfg
index de2202f9fc0..2e48a6d0a9e 100644
--- a/src/modules/db_text/doc/db_text.cfg
+++ b/src/modules/db_text/doc/db_text.cfg
@@ -76,7 +76,7 @@ route{
# use different transport protocol
if (!method=="REGISTER") record_route();
- # subsequent messages withing a dialog should take the
+ # subsequent messages within a dialog should take the
# path determined by record-routing
if (loose_route()) {
# mark routing logic in request
Module: kamailio
Branch: master
Commit: 9419fb2f4288149d71b191e05743df2df5fa42f7
URL: https://github.com/kamailio/kamailio/commit/9419fb2f4288149d71b191e05743df2…
Author: Henning Westerholt <hw(a)gilawa.com>
Committer: Henning Westerholt <hw(a)gilawa.com>
Date: 2022-12-11T10:19:54Z
docs/tutorials: spelling fix withing -> within
---
Modified: doc/tutorials/presence/cfg/full_ps.cfg
Modified: doc/tutorials/presence/cfg/ps.cfg
---
Diff: https://github.com/kamailio/kamailio/commit/9419fb2f4288149d71b191e05743df2…
Patch: https://github.com/kamailio/kamailio/commit/9419fb2f4288149d71b191e05743df2…
---
diff --git a/doc/tutorials/presence/cfg/full_ps.cfg b/doc/tutorials/presence/cfg/full_ps.cfg
index 7aae4372d1c..800336f0c40 100644
--- a/doc/tutorials/presence/cfg/full_ps.cfg
+++ b/doc/tutorials/presence/cfg/full_ps.cfg
@@ -191,7 +191,7 @@ route{
# use different transport protocol
if (!method=="REGISTER") record_route();
- # subsequent messages withing a dialog should take the
+ # subsequent messages within a dialog should take the
# path determined by record-routing
if (loose_route()) {
# mark routing logic in request
diff --git a/doc/tutorials/presence/cfg/ps.cfg b/doc/tutorials/presence/cfg/ps.cfg
index 51391965e1f..fedf6305227 100644
--- a/doc/tutorials/presence/cfg/ps.cfg
+++ b/doc/tutorials/presence/cfg/ps.cfg
@@ -252,7 +252,7 @@ route[RPC]
route[RR]
{
- # subsequent messages withing a dialog should take the
+ # subsequent messages within a dialog should take the
# path determined by record-routing
if (loose_route()) {
# mark routing logic in request
The default value for `tls_method` is `TLSv1`: https://kamailio.org/docs/modules/devel/modules/tls.html#tls.p.tls_method . This value is suboptimal as default.
Please change the default value to `TLSv1.2+` and remove `modparam("tls", "tls_method", …)` from misc/examples/outbound/edge_websocket.cfg and misc/examples/webrtc/websocket.cfg .
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3301
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3301(a)github.com>
The documentation on using openssl_mutex_shared.so is contradicting.
https://github.com/kamailio/kamailio/blob/master/src/modules/tls/README#L293 says:
> For OpenSSL (libssl) v1.1.x, it is required to preload 'openssl_mutex_shared' library shipped by Kamailio. For more details see 'src/modules/tls/openssl_mutex_shared/README.md'.
https://github.com/kamailio/kamailio/blob/master/src/modules/tls/utils/open… says:
> IMPORTANT: the workaround of using this preloaded shared library is no longer needed starting with Kamailio v5.3.0-pre1 (git master branch after September 14, 2019). The code of this shared library has been included in the core of Kamailio and the same behaviour is now achieved by default.
It is unclear, if openssl_mutex_shared.so must be preloaded.
In case the library is not needed anymore, it shall not be compiled and installed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3304
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3304(a)github.com>
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3303
-- Commit Summary --
* test/: add a space between comma and quote
-- File Changes --
M test/misc/cfg/acc-test.cfg (2)
M test/misc/cfg/gen.cfg (2)
M test/misc/cfg/mobile61.cfg (2)
M test/misc/cfg/nc.cfg (4)
M test/misc/cfg/ser.cfg (2)
M test/misc/cfg/stress.cfg (2)
M test/misc/cfg/test1.cfg (2)
M test/misc/cfg/th-uri.cfg (24)
M test/misc/cfg/use_jab.cfg (16)
M test/unit/11.cfg (2)
M test/unit/13.cfg (2)
M test/unit/14.cfg (2)
M test/unit/19.cfg (2)
M test/unit/20.cfg (2)
M test/unit/21.cfg (6)
M test/unit/22.cfg (2)
M test/unit/25.cfg (2)
M test/unit/26.cfg (2)
M test/unit/28.cfg (2)
M test/unit/30.cfg (2)
M test/unit/35.cfg (2)
M test/unit/41.cfg (2)
M test/unit/45.cfg (2)
M test/unit/5.cfg (12)
M test/unit/50.cfg (2)
M test/unit/60.cfg (18)
M test/unit/61.cfg (14)
M test/unit/7.cfg (2)
M test/unit/presence.cfg (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3303.patchhttps://github.com/kamailio/kamailio/pull/3303.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3303
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3303(a)github.com>
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3299
-- Commit Summary --
* misc/examples: add a space between comma and quote
-- File Changes --
M misc/examples/ims/icscf/kamailio.cfg (32)
M misc/examples/ims/pcscf/kamailio.cfg (26)
M misc/examples/ims/pcscf/route/mo.cfg (18)
M misc/examples/ims/pcscf/route/mt.cfg (12)
M misc/examples/ims/pcscf/route/register.cfg (6)
M misc/examples/ims/scscf/kamailio.cfg (140)
M misc/examples/kamailio/acc-mysql.cfg (2)
M misc/examples/kamailio/acc.cfg (2)
M misc/examples/kamailio/fork.cfg (2)
M misc/examples/kamailio/msilo.cfg (4)
M misc/examples/kamailio/nathelper.cfg (6)
M misc/examples/kamailio/pstn.cfg (4)
M misc/examples/kamailio/replicate.cfg (2)
M misc/examples/kamailio/serial_183.cfg (2)
M misc/examples/kemi/kamailio-basic-kemi-jsdt.js (8)
M misc/examples/kemi/kamailio-basic-kemi-lua.lua (8)
M misc/examples/kemi/kamailio-basic-kemi-native.cfg (10)
M misc/examples/kemi/kamailio-basic-kemi-python.py (8)
M misc/examples/kemi/kamailio-basic-kemi-python3s.py (8)
M misc/examples/kemi/kamailio-basic-kemi-ruby.rb (6)
M misc/examples/kemi/kamailio-basic-kemi-sqlang.sq (8)
M misc/examples/mixed/acc.cfg (2)
M misc/examples/mixed/dbtext.cfg (2)
M misc/examples/mixed/kamailio-minimal-anycast.cfg (8)
M misc/examples/mixed/kamailio-minimal-proxy.cfg (8)
M misc/examples/mixed/msilo.cfg (8)
M misc/examples/mixed/nathelper.cfg (2)
M misc/examples/mixed/onr.cfg (2)
M misc/examples/mixed/pstn.cfg (4)
M misc/examples/mixed/replicate.cfg (2)
M misc/examples/mixed/serial_183.cfg (2)
M misc/examples/mixed/voicemail.cfg (16)
M misc/examples/mixed/welcome.cfg (2)
M misc/examples/obsoleted/backup.cfg (2)
M misc/examples/obsoleted/bat.cfg (2)
M misc/examples/obsoleted/blb.cfg (4)
M misc/examples/obsoleted/imgw.cfg (38)
M misc/examples/obsoleted/mobile66.cfg (2)
M misc/examples/obsoleted/register.cfg (2)
M misc/examples/obsoleted/secondary.cfg (6)
M misc/examples/obsoleted/sms.cfg (2)
M misc/examples/obsoleted/smsgw.cfg (18)
M misc/examples/obsoleted/test.cfg (6)
M misc/examples/obsoleted/tmtest.cfg (2)
M misc/examples/obsoleted/to_fox.cfg (4)
M misc/examples/obsoleted/use_jabs.cfg (22)
M misc/examples/outbound/edge.cfg (4)
M misc/examples/outbound/edge_websocket.cfg (4)
M misc/examples/outbound/registrar.cfg (6)
M misc/examples/pkg/kamailio-basic.cfg (10)
M misc/examples/pkg/kamailio-oob.cfg (10)
M misc/examples/pkg/sip-router-basic.cfg (2)
M misc/examples/pkg/sip-router-oob.cfg (6)
M misc/examples/pkg/sipcapture.cfg (6)
M misc/examples/presence/full-no-failover.cfg (8)
M misc/examples/presence/no-db.cfg (2)
M misc/examples/webrtc/kamailio-default-websocket.cfg (18)
M misc/scripts/serconf.sh (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3299.patchhttps://github.com/kamailio/kamailio/pull/3299.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3299
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3299(a)github.com>
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
We have a rare crash in kamailio v5.3 running on Debian Buster in production environment. The crash (segmentation fault) happens while app_json module is writing accounting data to syslog upon receiving ACK for successful INVITE transaction over IPv6 UDP socket.
### Troubleshooting
We checked the server health and service load at the time of crash, everything looks normal. We inspected the core dump generated by kamailio, and it seems that there is some sort of race condition causing the crash, the ACK completes the INVITE transaction, so kamailio was fetching the transaction data from memory to write accounting record to syslog, however, that data is corrupted or deleted by some other kamailio process. We do not see anything unusual in kamailio log related to crash. Perhaps it is related to this older but [unresolved crash report](https://github.com/kamailio/kamailio/issues/2998).
#### Reproduction
No, we are unable to reproduce it in our lab.
<!--
If the issue can be reproduced, describe how it can be done.
-->
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
Output of `bt full` (first 16 function traces),
```gdb
#0 0x0000561a11a47ec7 in match_by_name (avp=0xd, id=52, name=0x7ffccc7967f8) at core/usr_avp.c:379
avp_name = 0x7f10ead4f190
#1 0x0000561a11a48d15 in search_next_avp (s=0x7ffccc7967f0, val=0x7ffccc7967d0) at core/usr_avp.c:500
matched = 0
avp = 0x7f10ead4f180
list = 0x7f10dc3196a8
__func__ = "search_next_avp"
#2 0x0000561a11a486d1 in search_avp (ident=..., val=0x7ffccc7967d0, state=0x7ffccc7967f0) at core/usr_avp.c:466
ret = 0x7f10ead4f180
st = {flags = 273, id = 10, name = {n = -567873331, s = {s = 0x7f11de26f0cd "mapped_identity_user)", len = 20}, re = 0x7f11de26f0cd}, avp = 0x7f10f0114820}
list = 0x7f10f4d2b208
__func__ = "search_avp"
#3 0x0000561a11a4804b in search_first_avp (flags=1, name=..., val=0x7ffccc7967d0, s=0x7ffccc7967f0) at core/usr_avp.c:415
id = {flags = 1, name = {n = -573917191, s = {s = 0x7f11ddcab7f9 "from_mandant);tm", len = 12}, re = 0x7f11ddcab7f9}, index = 0}
#4 0x00007f11dcfb0392 in pv_get_avp (msg=0x7f11de70c4b0, param=0x7f11de6cf7b0, res=0x7ffccc796930) at pv_core.c:1793
name_type = 1
avp_name = {n = -573917191, s = {s = 0x7f11ddcab7f9 "from_mandant);tm", len = 12}, re = 0x7f11ddcab7f9}
avp_value = {n = -563284264, s = {s = 0x7f11de6cf6d8 "", len = -563034960}, re = 0x7f11de6cf6d8}
avp = 0x2000000
avp_value0 = {n = -864458672, s = {s = 0x7ffccc796850 "\300hy\314\374\177", len = -587590620}, re = 0x7ffccc796850}
avp0 = 0x7f11dcd1bc90 <val_arr+336>
idx = 0
idxf = 0
p = 0x14d0960 <error: Cannot access memory at address 0x14d0960>
p_ini = 0x8f6c38 <error: Cannot access memory at address 0x8f6c38>
p_size = 22042
n = 0
state = {flags = 497, id = 52, name = {n = -573917191, s = {s = 0x7f11ddcab7f9 "from_mandant);tm", len = 12}, re = 0x7f11ddcab7f9}, avp = 0xd}
__func__ = "pv_get_avp"
#5 0x0000561a11a77f17 in pv_get_spec_value (msg=0x7f11de70c4b0, sp=0x7f11de6cf798, value=0x7ffccc796930) at core/pvapi.c:1404
ret = 0
__func__ = "pv_get_spec_value"
#6 0x00007f11dcd0c43a in extra2strar (extra=0x7f11de6cf788, rq=0x7f11de70c4b0, val_arr=0x7f11dcd1bb90 <val_arr+80>, int_arr=0x7f11dcd1c4d4 <int_arr+20>,
type_arr=0x7f11dcd1c725 <type_arr+5> "\002\002\002\002\002\002\002\002\001") at acc_extra.c:222
value = {rs = {s = 0x0, len = 0}, ri = 0, flags = 0}
n = 18
i = 0
__func__ = "extra2strar"
#7 0x00007f11dc2afc85 in acc_json_send_request (req=0x7f11de70c4b0, inf=0x7ffccc796af0) at acc_json_mod.c:308
attr_cnt = 5
i = 5
m = 0
o = 0
object = 0x561a13e7b7f0
__func__ = "acc_json_send_request"
extra = 0x561a11c6f34a
#8 0x00007f11dcce5a84 in acc_run_engines (msg=0x7f11de70c4b0, type=0, reset=0x0) at acc.c:581
inf = {env = 0x7f11dcd423a0 <acc_env>, varr = 0x7f11dcd1bb40 <val_arr>, iarr = 0x7f11dcd1c4c0 <int_arr>, tarr = 0x7f11dcd1c720 <type_arr> "\002\002\002\002\001\002\002\002\002\002\002\002\002\001",
leg_info = 0x0}
e = 0x7f11de6cfa10
__func__ = "acc_run_engines"
#9 0x00007f11dccf90a4 in acc_onack (t=0x7f10f4d2b008, req=0x7f10f52e2620, ack=0x7f11de70c4b0, code=-4) at acc_logic.c:657
__func__ = "acc_onack"
#10 0x00007f11dccf959c in tmcb_func (t=0x7f10f4d2b008, type=4, ps=0x7ffccc796d10) at acc_logic.c:696
__func__ = "tmcb_func"
#11 0x00007f11dd158e87 in run_trans_callbacks_internal (cb_lst=0x7f10f4d2b080, type=4, trans=0x7f10f4d2b008, params=0x7ffccc796d10) at t_hooks.c:254
cbp = 0x7f10f70688d8
backup_from = 0x561a11d83f30 <def_list+16>
backup_to = 0x561a11d83f38 <def_list+24>
backup_dom_from = 0x561a11d83f40 <def_list+32>
backup_dom_to = 0x561a11d83f48 <def_list+40>
backup_uri_from = 0x561a11d83f20 <def_list>
backup_uri_to = 0x561a11d83f28 <def_list+8>
backup_xavps = 0x561a11d16180 <_xavp_list_head>
__func__ = "run_trans_callbacks_internal"
#12 0x00007f11dd158fae in run_trans_callbacks (type=4, trans=0x7f10f4d2b008, req=0x7f11de70c4b0, rpl=0x0, code=-4) at t_hooks.c:279
params = {req = 0x7f11de70c4b0, rpl = 0x0, param = 0x7f10f70688e8, code = -4, flags = 0, branch = 0, t_rbuf = 0x0, dst = 0x0, send_buf = {s = 0x0, len = 0}}
#13 0x00007f11dd0bd4b4 in t_newtran (p_msg=0x7f11de70c4b0) at t_lookup.c:1437
lret = -2
my_err = -562995536
canceled = 0
__func__ = "t_newtran"
#14 0x00007f11dd14fb4b in t_relay_to (p_msg=0x7f11de70c4b0, proxy=0x0, proto=0, replicate=0) at t_funcs.c:243
ret = 0
new_tran = 32764
t = 0x7f11de70c4b0
dst = {send_sock = 0x561a11867b90 <_start>, to = {s = {sa_family = 43008, sa_data = "_V\004\271f\377\000\000\000\000\000\000\000"}, sin = {sin_family = 43008, sin_port = 22111, sin_addr = {
s_addr = 4284922116}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 43008, sin6_port = 22111, sin6_flowinfo = 4284922116, sin6_addr = {__in6_u = {
__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 294026128}, sas = {ss_family = 43008,
__ss_padding = "_V\004\271f\377", '\000' <repeats 16 times>, "\220{\206\021\032V\000\000\260^q\336\021\177\000\000H\221?\336\021\177\000\000\030\203\017\336\021\177", '\000' <repeats 14 times>, "\032V\000\000\000\000\000\002\000\000\000\000\000\250_V\004\271f\377\030e\217", '\000' <repeats 13 times>, "\220{\206\021\032V\000\000p\223y\314\374\177\000", __ss_align = 0}}, id = 0, send_flags = {f = 0,
blst_imask = 0}, proto = -128 '\200', proto_pad0 = 111 'o', proto_pad1 = -13191}
port = 0
host = {s = 0x2 <error: Cannot access memory at address 0x2>, len = 0}
comp = 0
__func__ = "t_relay_to"
#15 0x00007f11dd1737b4 in _w_t_relay_to (p_msg=0x7f11de70c4b0, proxy=0x0, force_proto=0) at tm.c:1691
t = 0x7f11de70c4b0
res = 0
__func__ = "_w_t_relay_to"
#16 0x00007f11dd174aab in w_t_relay (p_msg=0x7f11de70c4b0, _foo=0x0, _bar=0x0) at tm.c:1891
No locals.
```
Module parameters for `acc_json`,
```python
# -- acc_json CDR parameters --
modparam("acc_json", "acc_output_syslog", 1)
modparam("acc_json", "acc_flag", 1)
modparam("acc_json", "acc_log_facility", ACC_JSON_FACILITY)
modparam("acc_json", "acc_extra", "iu=$ou;ou=$ru;f=$fu;t=$tu;cq=$cs;id=$avp(identity_user);mi=$avp(mapped_identity_user);fp=$avp(from_provider);fs=$mf;ld=$avp(lastdst);u1=$ua;u2=$avp(ua_rsp);x1=$hdr(X-RTP-Stat);x2=$avp(xrtp_rsp);xt1=$hdr(X-RTP-Stat-Add);xt2=$avp(xrtp_add_rsp);tt=$avp(target);ct=$ct;fm=$avp(from_mandant);tm=$avp(to_mandant);mc=$avp(m_target)")
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
Nov 28 16:11:59 sip-proxy2 kamailio[1370]: ALERT: <core> [main.c:766]: handle_sigs(): child process 1596 exited by a signal 11
Nov 28 16:11:59 sip-proxy2 kamailio[1370]: ALERT: <core> [main.c:769]: handle_sigs(): core was generated
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```YAML
INVITE sip:4900000000@[xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx];uniq=8ED0C01913346AA654117F901E24D SIP/2.0
Record-Route: <sip:[yyyy:yyy:yyy:yyy:yyy:yyy:yyy:yyy];r2=on;lr=on>
Record-Route: <sip:bbb.bbb.bbb.bbb;r2=on;lr=on>
Record-Route: <sip:ccc.ccc.cc.ccc;lr=on;ftag=n6719nbq-CC-1031-OFC-1773;did=637.7591>
History-Info: <sip:+4900000000@sip-proxy.de>;index=1
History-Info: <sip:+4900000000@sip-proxy.de;user=phone>;index=1.1;np=1
Record-Route: <sip:ddd.ddd.ddd.ddd;lr=on>
Via: SIP/2.0/UDP [yyyy:yyy:yyy:yyy:yyy:yyy:yyy:yyy];branch=z9hG4bKd674.46e0b6bab175e9465a766f3602eb1723.0
Via: SIP/2.0/UDP ccc.ccc.cc.ccc;branch=z9hG4bKd674.fbdcb55027bdeb56205b8bd53e09641b.0
Via: SIP/2.0/UDP ddd.ddd.ddd.ddd;branch=z9hG4bKd674.c1356dc9c4dd64165b1d2a7b6dcc8061.0
Via: SIP/2.0/UDP ee.eee.eee.ee:5060;branch=z9hG4bKud6dm320bogcnc1dqvu0.1
Call-ID: b6a6a84q4nw41b9icb46b1441ccbzcnv(a)zz.zz.z.zz
From: "+491111111111"<sip:+491111111111@sip-server.de;transport=udp;user=phone>;tag=n6719nbq-CC-1031-OFC-1773
To: "+4900000000"<sip:+4900000000@sip-proxy.de;user=phone>
CSeq: 1 INVITE
Max-Forwards: 61
P-Early-Media: supported
Contact: <sip:+491111111111@ee.eee.eee.ee:5060;user=phone;transport=udp>
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,REFER,UPDATE
Supported: timer
Min-SE: 90
Session-Expires: 1800;refresher=uac
Content-Length: 550
Content-Type: application/sdp
v=0
o=- 1159782858 1 IN IP6 aaaa:aaa:aaa:a:aaa:aaa:aaa:aa
s=-
c=IN IP6 aaaa:aaa:aaa:a:aaa:aaa:aaa:aa
b=RR:3000
b=RS:1000
b=AS:80
t=0 0
a=rtpengine:dda0c1ad4f21
m=audio 20798 RTP/AVP 9 8 96 0 110
b=RR:1837
b=RS:612
b=AS:80
a=maxptime:240
a=msi:mavodi-0-15b-89-6-ffffffff-b5930000-5e88bfbb24c0a-948-ffffffffffffffff-@ff.fff.fff.f-gg.ggg.ggg.g;UAGLEJ04-24
a=rtpmap:9 G722/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:96 G726-32/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:110 telephone-event/8000
a=fmtp:110 0-15
a=sendrecv
a=rtcp:20799
a=ptime:20
SIP/2.0 100 Trying
Via: SIP/2.0/UDP [yyyy:yyy:yyy:yyy:yyy:yyy:yyy:yyy];branch=z9hG4bKd674.46e0b6bab175e9465a766f3602eb1723.0
Via: SIP/2.0/UDP ccc.ccc.cc.ccc;branch=z9hG4bKd674.fbdcb55027bdeb56205b8bd53e09641b.0
Via: SIP/2.0/UDP ddd.ddd.ddd.ddd;branch=z9hG4bKd674.c1356dc9c4dd64165b1d2a7b6dcc8061.0
Via: SIP/2.0/UDP ee.eee.eee.ee:5060;branch=z9hG4bKud6dm320bogcnc1dqvu0.1
From: "+491111111111" <sip:+491111111111@sip-server.de;user=phone>;tag=n6719nbq-CC-1031-OFC-1773
To: "+4900000000" <sip:+4900000000@sip-proxy.de;user=phone>
Call-ID: b6a6a84q4nw41b9icb46b1441ccbzcnv(a)zz.zz.z.zz
CSeq: 1 INVITE
User-Agent: AVM FRITZ!Box 7490 (UI) 113.07.29 (Oct 26 2021)
Content-Length: 0
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP [yyyy:yyy:yyy:yyy:yyy:yyy:yyy:yyy];branch=z9hG4bKd674.46e0b6bab175e9465a766f3602eb1723.0
Via: SIP/2.0/UDP ccc.ccc.cc.ccc;branch=z9hG4bKd674.fbdcb55027bdeb56205b8bd53e09641b.0
Via: SIP/2.0/UDP ddd.ddd.ddd.ddd;branch=z9hG4bKd674.c1356dc9c4dd64165b1d2a7b6dcc8061.0
Via: SIP/2.0/UDP ee.eee.eee.ee:5060;branch=z9hG4bKud6dm320bogcnc1dqvu0.1
Record-Route: <sip:[yyyy:yyy:yyy:yyy:yyy:yyy:yyy:yyy];r2=on;lr=on>
Record-Route: <sip:bbb.bbb.bbb.bbb;r2=on;lr=on>
Record-Route: <sip:ccc.ccc.cc.ccc;lr=on;ftag=n6719nbq-CC-1031-OFC-1773;did=637.7591>
Record-Route: <sip:ddd.ddd.ddd.ddd;lr=on>
From: "+491111111111" <sip:+491111111111@sip-server.de;user=phone>;tag=n6719nbq-CC-1031-OFC-1773
To: "+4900000000" <sip:+4900000000@sip-proxy.de;user=phone>;tag=0D99F03B986ED6CD
Call-ID: b6a6a84q4nw41b9icb46b1441ccbzcnv(a)zz.zz.z.zz
CSeq: 1 INVITE
Contact: <sip:4900000000@[xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx];uniq=8ED0C01913346AA654117F901E24D>
User-Agent: AVM FRITZ!Box 7490 (UI) 113.07.29 (Oct 26 2021)
Content-Length: 0
SIP/2.0 200 OK
Via: SIP/2.0/UDP [yyyy:yyy:yyy:yyy:yyy:yyy:yyy:yyy];branch=z9hG4bKd674.46e0b6bab175e9465a766f3602eb1723.0
Via: SIP/2.0/UDP ccc.ccc.cc.ccc;branch=z9hG4bKd674.fbdcb55027bdeb56205b8bd53e09641b.0
Via: SIP/2.0/UDP ddd.ddd.ddd.ddd;branch=z9hG4bKd674.c1356dc9c4dd64165b1d2a7b6dcc8061.0
Via: SIP/2.0/UDP ee.eee.eee.ee:5060;branch=z9hG4bKud6dm320bogcnc1dqvu0.1
Record-Route: <sip:[yyyy:yyy:yyy:yyy:yyy:yyy:yyy:yyy];r2=on;lr=on>
Record-Route: <sip:bbb.bbb.bbb.bbb;r2=on;lr=on>
Record-Route: <sip:ccc.ccc.cc.ccc;lr=on;ftag=n6719nbq-CC-1031-OFC-1773;did=637.7591>
Record-Route: <sip:ddd.ddd.ddd.ddd;lr=on>
From: "+491111111111" <sip:+491111111111@sip-server.de;user=phone>;tag=n6719nbq-CC-1031-OFC-1773
To: "+4900000000" <sip:+4900000000@sip-proxy.de;user=phone>;tag=0D99F03B986ED6CD
Call-ID: b6a6a84q4nw41b9icb46b1441ccbzcnv(a)zz.zz.z.zz
CSeq: 1 INVITE
Contact: <sip:4900000000@[xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx];uniq=8ED0C01913346AA654117F901E24D>
User-Agent: AVM FRITZ!Box 7490 (UI) 113.07.29 (Oct 26 2021)
Supported: 100rel,replaces
Allow-Events: telephone-event,refer
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,PRACK,INFO,SUBSCRIBE,NOTIFY,REFER,MESSAGE,PUBLISH
Content-Type: application/sdp
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 277
v=0
o=user 12824182 12824182 IN IP6 xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
s=-
c=IN IP6 xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
t=0 0
m=audio 7078 RTP/AVP 8 110
a=rtpmap:8 PCMA/8000
a=rtpmap:110 telephone-event/8000
a=fmtp:110 0-15
a=sendrecv
a=rtcp:7079
a=ptime:20
SIP/2.0 200 OK
Via: SIP/2.0/UDP [yyyy:yyy:yyy:yyy:yyy:yyy:yyy:yyy];branch=z9hG4bKd674.46e0b6bab175e9465a766f3602eb1723.0
Via: SIP/2.0/UDP ccc.ccc.cc.ccc;branch=z9hG4bKd674.fbdcb55027bdeb56205b8bd53e09641b.0
Via: SIP/2.0/UDP ddd.ddd.ddd.ddd;branch=z9hG4bKd674.c1356dc9c4dd64165b1d2a7b6dcc8061.0
Via: SIP/2.0/UDP ee.eee.eee.ee:5060;branch=z9hG4bKud6dm320bogcnc1dqvu0.1
Record-Route: <sip:[yyyy:yyy:yyy:yyy:yyy:yyy:yyy:yyy];r2=on;lr=on>
Record-Route: <sip:bbb.bbb.bbb.bbb;r2=on;lr=on>
Record-Route: <sip:ccc.ccc.cc.ccc;lr=on;ftag=n6719nbq-CC-1031-OFC-1773;did=637.7591>
Record-Route: <sip:ddd.ddd.ddd.ddd;lr=on>
From: "+491111111111" <sip:+491111111111@sip-server.de;user=phone>;tag=n6719nbq-CC-1031-OFC-1773
To: "+4900000000" <sip:+4900000000@sip-proxy.de;user=phone>;tag=0D99F03B986ED6CD
Call-ID: b6a6a84q4nw41b9icb46b1441ccbzcnv(a)zz.zz.z.zz
CSeq: 1 INVITE
Contact: <sip:4900000000@[xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx];uniq=8ED0C01913346AA654117F901E24D>
User-Agent: AVM FRITZ!Box 7490 (UI) 113.07.29 (Oct 26 2021)
Supported: 100rel,replaces
Allow-Events: telephone-event,refer
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,PRACK,INFO,SUBSCRIBE,NOTIFY,REFER,MESSAGE,PUBLISH
Content-Type: application/sdp
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length: 277
v=0
o=user 12824182 12824182 IN IP6 xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
s=-
c=IN IP6 xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
t=0 0
m=audio 7078 RTP/AVP 8 110
a=rtpmap:8 PCMA/8000
a=rtpmap:110 telephone-event/8000
a=fmtp:110 0-15
a=sendrecv
a=rtcp:7079
a=ptime:20
ACK sip:4900000000@[xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx];uniq=8ED0C01913346AA654117F901E24D SIP/2.0
Record-Route: <sip:[yyyy:yyy:yyy:yyy:yyy:yyy:yyy:yyy];r2=on;lr=on>
Record-Route: <sip:bbb.bbb.bbb.bbb;r2=on;lr=on>
Record-Route: <sip:ccc.ccc.cc.ccc;lr=on;ftag=n6719nbq-CC-1031-OFC-1773;did=637.7591>
Record-Route: <sip:ddd.ddd.ddd.ddd;lr=on>
Via: SIP/2.0/UDP [yyyy:yyy:yyy:yyy:yyy:yyy:yyy:yyy];branch=z9hG4bKd674.6295c199c1d6f3d7c65df5051cc1bd86.0
Via: SIP/2.0/UDP ccc.ccc.cc.ccc;branch=z9hG4bKd674.9ae26c2d53df7a32d7cc5201eef22b18.0
Via: SIP/2.0/UDP ddd.ddd.ddd.ddd;branch=z9hG4bKd674.398f61cd1fb592c16403d50538fc8421.0
Via: SIP/2.0/UDP ee.eee.eee.ee:5060;branch=z9hG4bK2j5dam10a02iqjq1gn00.1
Call-ID: b6a6a84q4nw41b9icb46b1441ccbzcnv(a)zz.zz.z.zz
From: "+491111111111" <sip:+491111111111@sip-server.de;user=phone>;tag=n6719nbq-CC-1031-OFC-1773
To: "+4900000000" <sip:+4900000000@sip-proxy.de;user=phone>;tag=0D99F03B986ED6CD
CSeq: 1 ACK
Max-Forwards: 61
Content-Length: 0
BYE sip:+491111111111@ee.eee.eee.ee:5060;user=phone;transport=udp SIP/2.0
Via: SIP/2.0/UDP [xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx]:5060;rport;branch=z9hG4bK66826E59C0886604
Route: <sip:[yyyy:yyy:yyy:yyy:yyy:yyy:yyy:yyy];r2=on;lr=on>
Route: <sip:bbb.bbb.bbb.bbb;r2=on;lr=on>
Route: <sip:ccc.ccc.cc.ccc;lr=on;ftag=n6719nbq-CC-1031-OFC-1773;did=637.7591>
Route: <sip:ddd.ddd.ddd.ddd;lr=on>
From: "+4900000000" <sip:+4900000000@sip-proxy.de;user=phone>;tag=0D99F03B986ED6CD
To: "+491111111111" <sip:+491111111111@sip-server.de;user=phone>;tag=n6719nbq-CC-1031-OFC-1773
Call-ID: b6a6a84q4nw41b9icb46b1441ccbzcnv(a)zz.zz.z.zz
CSeq: 2 BYE
X-RTP-Stat: CS=0;PS=3811;ES=3889;OS=609760;SP=0/0;SO=0;QS=-;PR=3853;ER=3889;OR=616480;CR=0;SR=0;QR=-;PL=0,0;BL=0;LS=0;RB=0/0;SB=-/-;EN=PCMA;DE=PCMA;JI=23,1;DL=67,67,70;IP=[xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx]:7078,[hhhh:hhh:hhh::hhh:hhh:hhh:hh]:20798
X-RTP-Stat-Add: DQ=2;DSS=0;DS=0;PLCS=32;JS=1
X-SIP-Stat: DRT=0;IR=0
Reason: Q.850; cause=16
Max-Forwards: 70
User-Agent: AVM FRITZ!Box 7490 (UI) 113.07.29 (Oct 26 2021)
Supported: 100rel,replaces
Allow-Events: telephone-event,refer
Content-Length: 0
SIP/2.0 200 OK
Via: SIP/2.0/UDP [xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx]:5060;received=xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx;rport=5060;branch=z9hG4bK66826E59C0886604
From: "+4900000000" <sip:+4900000000@sip-proxy.de;user=phone>;tag=0D99F03B986ED6CD
To: "+491111111111" <sip:+491111111111@sip-server.de;user=phone>;tag=n6719nbq-CC-1031-OFC-1773
Call-ID: b6a6a84q4nw41b9icb46b1441ccbzcnv(a)zz.zz.z.zz
CSeq: 2 BYE
Record-Route: <sip:ddd.ddd.ddd.ddd;lr=on>
Record-Route: <sip:ccc.ccc.cc.ccc;lr=on;ftag=n6719nbq-CC-1031-OFC-1773>
Record-Route: <sip:bbb.bbb.bbb.bbb;r2=on;lr=on>
Record-Route: <sip:[yyyy:yyy:yyy:yyy:yyy:yyy:yyy:yyy];r2=on;lr=on>
Content-Length: 0
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```RUST
version: kamailio 5.3.9 (x86_64/linux)
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, TLS_PTHREAD_MUTEX_SHARED
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:
compiled with gcc 8.3.0
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `lsb_release -a` and `uname -a`)
-->
```RUST
Linux sip-proxy2 4.19.0-22-amd64 #1 SMP Debian 4.19.260-1 (2022-09-29) x86_64 GNU/Linux
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3292
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3292(a)github.com>
Hello,
to summarize what happened at the devel meeting in Dusseldorf a few
weeks ago and plan the next steps for the project, we are planning an
online development meeting on Thu, Dec 8, 2022, 15:00UTC.
As usual, one of the targets is to sketch the roadmap to next major
release so the developers and community members can syncronize and plan
what should be done till Kamailio v5.7 (or 6.0) will be out as well as
discuss about current state of the project, look for new ideas to
improve collaboration within the community, a.s.o.
The meeting will be done on a matrix chat room. More details are in the
wiki page of the event, available at:
*
https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings…
Feel free to add there topics that you want to be discussed.
The proposed date is Thursday, December 08, 2022, at 15:00UTC (15:00
London/Dublin, 16:00 most of West Europe, 10:00 New York), but other
dates can be proposed if they suit for more participants.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
_______________________________________________
Kamailio (SER) - Development Mailing List
sr-dev(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
### Description
Issues building `PYTHON` module on Alpine Linux due to [sunsetting of Python2](https://www.python.org/doc/sunset-python-2/). The `python2` package (apk) has been removed from the current Alpine linux. The APKBUILD file in the current Kamailio branches includes build settings for installing the Python (python2) module. While I'm guessing it's possible to build python2 in the current Alpine container it was a conscious decision to no longer have a package for it. Given this, what is the opinion about not building this by default within the APKBUILD file?
### Troubleshooting
Running `abuild -r` fails due to lack of python2 libraries.
#### Reproduction
Running `abuild -r` fails due to lack of python2 libraries.
#### Debugging Data
N/A
#### Log Messages
N/A
#### SIP Traffic
N/A
### Possible Solutions
In `APKBUILD` remove references to `python2` and `python` (but not `python3`). I'll submit a pull request to do this.
### Additional Information
Kamailio 5.7
* **Operating System**:
Alpine Linux latest
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3257
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3257(a)github.com>
#### 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:
- [x] PR should be backported to stable branches
- [x] Tested changes locally
- [x] Related to issue #3257
#### Description
Do not build python2 module with default APKBUILD file due to python2 being sunsetted within Alpine Linux (there is no python2 APK).
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3258
-- Commit Summary --
* APKBUILD: remove python2 references
-- File Changes --
M pkg/kamailio/alpine/APKBUILD (12)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3258.patchhttps://github.com/kamailio/kamailio/pull/3258.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3258
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3258(a)github.com>
<!-- 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 -->
- [V] Commit message has the format required by CONTRIBUTING guide
- [V] Commits are split per component (core, individual modules, libs, utils, ...)
- [V] Each component has a single commit (if not, squash them into one commit)
- [V] 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)
- [V] 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 -->
- [V] PR should be backported to stable branches
- [V] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
I modified the imc module as follows:
1. propagate content-type header
2. add the option to modify member role
3. added support to db_mode. all changes are synch to db in case db_mode is set to 2.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3291
-- Commit Summary --
* imc: add support to modify member role
* imc: call handle_modify
* imc: db_mode support
* Merge branch 'kamailio:master' into master
* imc: destroy db only if db_mode is not 0
* Merge remote-tracking branch 'joeygo/master'
* imc: propagate content-type header
* Merge branch 'kamailio:master' into master
-- File Changes --
M src/modules/imc/doc/imc.xml (7)
M src/modules/imc/doc/imc_admin.xml (35)
M src/modules/imc/imc.c (326)
M src/modules/imc/imc.h (1)
M src/modules/imc/imc_cmd.c (260)
M src/modules/imc/imc_cmd.h (9)
M src/modules/imc/imc_mng.c (405)
M src/modules/imc/imc_mng.h (28)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3291.patchhttps://github.com/kamailio/kamailio/pull/3291.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3291
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3291(a)github.com>