### Description
I have a problem with publish/notify messages generated from Kamailio towards a monitoring device after multiple branches has been created.
When the call is forked by kamailio, invites are generated towards each callee user agent depending on how many branches we have in the call.
When one of the callee user agents sends back 200 ok to enter the conversation, kamailio automatically sends a CANCEL towards the user agents that lost the race condition and didnt take the call.
When …
[View More]this happens, a notify is set to the monitoring user agent with the state "terminated" but this is wrong since the call is up and we are in conversation.
#### Reproduction
1. set up a monitoring device that subscribes to B events.
2. Register more than one device to B to make kamailio behave like a forking proxy
3. Call B and observe the notify message sent to the monitoring device, in particular the <dialog id="xxx" value
### Possible Solutions
I think this can be solved just adding some random uuid inside the xml field sent inside the xml of the NOTIFY message:
The random uuid must be different for each branch.
### Additional Information
version: kamailio 5.5.1 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, NO_SIG_DEBUG, 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_BLOCKLIST, 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: unknown
compiled with gcc 10.2.1
* **Operating System**:
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
Linux sp1 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux
--
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/2906
[View Less]
#### 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 …
[View More]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 -->
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [x] Related to issue #2906
#### Description
This change solves the issue of parallel forking, subscriber
was receiving NOTIFY messages with the same id for different branches
fixes #2906
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2908
-- Commit Summary --
* <a href="https://github.com/kamailio/kamailio/pull/2908/commits/8a924ee177b4764cd5da…">pua_dialoginfo: generate uuid as id instead of use callid value</a>
-- File Changes --
M src/modules/pua_dialoginfo/Makefile (11)
M src/modules/pua_dialoginfo/dialog_publish.c (18)
M src/modules/pua_dialoginfo/pua_dialoginfo.c (47)
M src/modules/pua_dialoginfo/pua_dialoginfo.h (9)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2908.patchhttps://github.com/kamailio/kamailio/pull/2908.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/2908
[View Less]
### Description
I have compiled Kamailio on aarch64 hosts with Google ASAN. Also used system memory manager ("make MEMPKG=sys cfg").
During compilation used flags
```
-fsanitize=address -fsanitize=undefined -fno-sanitize-recover=all -fsanitize=float-divide-by-zero -fsanitize=float-cast-overflow -fno-sanitize=null -fno-sanitize=alignment
```
When Kamailio is started with the default config file I get an error
```
core/script_cb.c:85:31: runtime error: left shift of 1 by 31 places cannot be …
[View More]represented in type 'int'
```
As used 64 bit CPU, looks like a strange this error
### Additional Information
compiled commit 102d5dab4f45cab238ffeb72e7ddf378c8daa17d
* **Operating System**:
```
[root@logger-west kamailio]# uname -a
Linux example.com 4.18.0-305.7.1.el8_4.aarch64 #1 SMP Tue Jun 29 21:32:00 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
[root@logger-west kamailio]# lsb_release -a
LSB Version: :core-4.1-aarch64:core-4.1-noarch
Distributor ID: CentOS
Description: CentOS Linux release 8.4.2105
Release: 8.4.2105
Codename: n/a
```
--
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/2897
[View Less]
Thanks to Jason Shugart at INdigital. Fix consist of caring of removing references to previously retrieved tcp connections. GH #2880
<!-- 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 …
[View More]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 -->
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [x] Related to issue #2880 (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
Just do some missing `tcpconn_put` calls on MSRP module after a tcpconn_get.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2890
-- Commit Summary --
* <a href="https://github.com/kamailio/kamailio/pull/2890/commits/19714ebaa0f653f65d83…">msrp: fix some tcpconn where memory was never cleaned up</a>
-- File Changes --
M src/modules/msrp/msrp_netio.c (5)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2890.patchhttps://github.com/kamailio/kamailio/pull/2890.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/2890
[View Less]
<!-- 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, …
[View More]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)
- [x ] 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
- [ x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
The database cluster modules (db_cluster) does not allow manual controle over database connections in the cluster.
This change adds some rpc commands to allow this.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2893
-- Commit Summary --
* <a href="https://github.com/kamailio/kamailio/pull/2893/commits/a58e7a235c1300cfbdaf…">db_cluster: RPC commands to control database connections</a>
-- File Changes --
M src/modules/db_cluster/db_cluster_mod.c (249)
M src/modules/db_cluster/dbcl_data.c (33)
M src/modules/db_cluster/dbcl_data.h (5)
M src/modules/db_cluster/doc/db_cluster.xml (5)
M src/modules/db_cluster/doc/db_cluster_admin.xml (61)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2893.patchhttps://github.com/kamailio/kamailio/pull/2893.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/2893
[View Less]
Add CIFuzz workflow action to have fuzzers build and run on each PR.
This is a service offered by OSS-Fuzz, on which Kamailio already runs.
Signed-off-by: David Korczynski <david(a)adalogics.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 …
[View More]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)
- [x ] 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 -->
Add CIFuzz Github action to build and run fuzzers on pull requests.
This will run the fuzzers for 600 seconds (split between all the fuzzers) in the CI when a pull request is made and is a service by OSS-fuzz. It can help with catching bugs early and catch regressions.
Documentation for CIFuzz can be found here: https://google.github.io/oss-fuzz/getting-started/continuous-integration/
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2903
-- Commit Summary --
* <a href="https://github.com/kamailio/kamailio/pull/2903/commits/f10ba5c9e81f0ae0f2f6…">github/workflow: add CIFuzz integration</a>
-- File Changes --
A .github/workflows/cifuzz.yml (26)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2903.patchhttps://github.com/kamailio/kamailio/pull/2903.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/2903
[View Less]
Hi guys,
We are quite newby about Kamailio and we are trying to use it as a load
balancer. While installing certificates we started having problems.
We use Kamailio (vers. 5.5) deployed on a VM (Ubuntu, 20.04 LTS).
We cannot connect via TLS Kamailio VM with clients or other TCP VM.
Our Kamailio currently exposes only port 5060 in UDP and TCP.
Even doing a port scan on localhost, port 5061, used for the TLS protocol,
is instead closed.
There are 3 things worth noting:
- All ports for all …
[View More]protocols are open on the firewall;
- Before we set the disable_tcp option to "no", the 5060 was only reachable
in UDP;
- Even if you put a non-existent certificate, the system does not return an
error so we cannot understand if the goodness of the certificates affects
the opening of the door. Furthermore, we did not find any different
behavior when switching from crt format (key for the private key) to PEM.
If someone can help us would be very appreciated.
Thank you very much
Here is our tls configuration:
kamailio.cfg
#!define WITH_TLS 1
...
disable_tcp=no
auto_aliases=no
….
loadmodule "sl.so"
loadmodule "tls.so"
...
modparam("tls", "private_key", "/etc/kamailio/key.pem")
modparam("tls", "certificate", "/etc/kamailio/crt.pem")
modparam("tls", "ca_list", "/etc/kamailio/ca.pem")
enable_tls=yes
tls.config
[server:default]
method = TLSv1.2+
verify_certificate = no
require_certificate = no
private_key = /etc/kamailio/kamailio-selfsigned.key
certificate = /etc/kamailio/kamailio-selfsigned.pem
#ca_list = /etc/kamailio/tls/cacert.pem
#crl = /etc/kamailio/tls/crl.pem
[client:default]
#method = TLSv1.2+
verify_certificate = no
require_certificate = no
*Sent with Shift
<https://tryshift.com/?utm_source=SentWithShift&utm_campaign=Sent+with+Shift…>*
[View Less]
Module: kamailio
Branch: master
Commit: 01434fa89bac3174ff68c08cf776dc73abb2eb2d
URL: https://github.com/kamailio/kamailio/commit/01434fa89bac3174ff68c08cf776dc7…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-10-25T19:23:08+02:00
textopsx: docs - fixed title for sections
---
Modified: src/modules/textopsx/doc/functions.xml
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]01434fa89bac3174ff68c08cf776dc7…
Patch: https://github.com/kamailio/kamailio/commit/01434fa89bac3174ff68c08cf776dc7…
---
diff --git a/src/modules/textopsx/doc/functions.xml b/src/modules/textopsx/doc/functions.xml
index 3de3a6c8e6..7500cbaa85 100644
--- a/src/modules/textopsx/doc/functions.xml
+++ b/src/modules/textopsx/doc/functions.xml
@@ -559,11 +559,11 @@ hf_iterator_end("i1");
</section>
<section id="textopsx.f.hf_iterator_next">
<title>
- <function moreinfo="none">textopsx.f.hf_iterator_next(iname)</function>
+ <function moreinfo="none">hf_iterator_next(iname)</function>
</title>
<para>
Move the iterator to the next header. It must
- be called also after bl_iterator_start() to get the first
+ be called also after hf_iterator_start() to get the first
header.
</para>
<para>
@@ -594,7 +594,7 @@ hf_iterator_end("i1");
</section>
<section id="textopsx.f.hf_iterator_prev">
<title>
- <function moreinfo="none">textopsx.f.hf_iterator_prev(iname)</function>
+ <function moreinfo="none">hf_iterator_prev(iname)</function>
</title>
<para>
Move the iterator to the previous header. It must
@@ -757,7 +757,7 @@ bl_iterator_end("b1");
</section>
<section id="textopsx.f.bl_iterator_next">
<title>
- <function moreinfo="none">textopsx.f.bl_iterator_next(iname)</function>
+ <function moreinfo="none">bl_iterator_next(iname)</function>
</title>
<para>
Move the iterator to the next line in the body. It must
[View Less]
Hi!
I just stumbled into a hard-to-find problem with Kamailio.
The symtom was that Kamailio simply did not read a lot of incoming messages, so they did not get any response. We saw traffic coming in on the interface with tcpdump, but not in the kamailio logs. Restarting Kamailio solved the problem for a while, then it started again.
I noticed there was something related to the DB, so for testing I disabled all db-based functions, but missed siptrace that connected and operated in the …
[View More]background by the config settings, nothing in the routing script.
I finally traced the problem to the siptrace module. The db table had grown way too big (due to attacks) and adding new records to it took way too much time. During that time, with SIPtrace waiting for confirmation, the process locked and packets where dropped.
Kamailio still handled calls, but a lot of calls was dropped.
I will solve this shortly by setting up a parallell smaller Kamailio that logs to database instead of running siptrace with DB in a production server.
But in order for others not to find themselves in this very hard to find situation, is there something that can be done to the siptrace code so it doesn’t execute in the same process that listens for incoming SIP messages? It would be a huge improvement to just block a background process so that siptrace doesn’t work, instead of blocking a listen process and drop traffic.
I don’t think I can write that code. Sorry. Otherwise it would have been a high priority, because these problems in production drove me almost insane. Restarting - all works fine. After a few hours the first packets are lost. Calls getting through for some customers all of the time.
Sorry for a long post, but I want this in the archives to help others.
Regards,
/O
[View Less]
I config ims_diameter_server as below:
```
#!ifdef WITH_DIAMETER_SERVER
# IMS_DIAMETER_SERVER
event_route[diameter:request]{
xlog("L_INFO","ims Got diameter message");
# diameter_request("hss.ims.mnc001.mcc001.3gppnetwork.org", $diameter_application, $diameter_command, $diameter_request);
diameter_request_async("hss.ims.mnc001.mcc001.3gppnetwork.org", $diameter_application, $diameter_command, $diameter_request);
xlog("L_INFO","ims Forwarded Diameter Request");
}
…
[View More]event_route[diameter:response] {
xlog("L_INFO","ims Reply to Diameter request is $diameter_response\n");
}
#!endif
```
And got a response from hss:

but got <null> response in log:
> 90(124) INFO: <script>: ims Got diameter message90(124) DEBUG: ims_diameter_server [avp_helper.c:59]: avp2json(): AVP((nil) < 0x7f44c2ad16f0 >0x7f44c2ad0c08);code=263,flags=40;
> 89(123) INFO: <script>: ims Reply to Diameter request is <null>
$diameter_response is <null>, why, how to fix it?
--
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/2900
[View Less]