Hello,
the branch 5.8 was created, therefore the master branch is open for
adding new features, to be part of future release series v5.9.x (or
whatever version is decided for next series).
Any bug fix committed to master that applies to 5.8.x or older stable
branches should be backported as usual with "git cherry-pick -x ..." to
appropriate branches like 5.8 or 5.7.
Expect that v5.8.0 will be released in a few weeks from now.
Based on the workflow used during the past years, the next future
…
[View More]release v5.9.0 should be out after another 8-10 months of development,
plus 1-2 months of testing, so sometime during the last part of 2024 or
the beginning of 2025.
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
[View Less]
Hello,
the branch 5.8 has been created, to be used for releasing v5.8.x series.
To check out this branch, the following commands can be used:
git clone https://github.com/kamailio/kamailio kamailio-5.8
cd kamailio-5.8
git checkout -b 5.8 origin/5.8
Pushing commits in this branch:
git push origin 5.8:5.8
Note that 5.8 is an official stable branch, so only bug fixes, missing
kemi exports (discuss on sr-dev if not sure) or improvements to
…
[View More]documentation or helper tools can be pushed to this branch.
As usual, if there is a bug fixed, commit and push first to master
branch and then cherry pick to 5.8 branch:
git cherry-pick -x COMMITID
In few weeks, the first release from branch 5.8 will be out,
respectively Kamailio v5.8.0.
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
[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)
- [ ] 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 -->
This PR adds the support of using PVs in the `prefix` parameter.
Also refactors the properties into a structure for each file.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3763
-- Commit Summary --
* file_out: Prefix can use PVs
* file_out: Refactor
-- File Changes --
M src/modules/file_out/file_out.c (140)
M src/modules/file_out/types.c (38)
M src/modules/file_out/types.h (17)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3763.patchhttps://github.com/kamailio/kamailio/pull/3763.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3763
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3763(a)github.com>
[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)
- [ ] 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/3761
-- Commit Summary --
* microhttpd: fixed typo in the documentation
-- File Changes --
M src/modules/microhttpd/doc/microhttpd_admin.xml (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3761.patchhttps://github.com/kamailio/kamailio/pull/3761.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3761
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3761(a)github.com>
[View Less]
<!--
Module pipelimit add pl.reload RPC Command
-->
### Description
Sometimes it is necessary to dynamically add current limiting rules without restarting kamailio.
After adding pipe rules in the database, it is hoped that the new rules can be reloaded into memory through the rpc command.
### Expected behavior
#### Actual observed behavior
#### Debugging Data
```
(paste your debugging data here)
```
#### Log Messages
<!--
-->
```
(paste your log messages here)
```
#### …
[View More]SIP Traffic
<!--
-->
```
(paste your sip traffic here)
```
### Possible Solutions
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.7.0 (x86_64/linux) f1e91d
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
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: f1e91d
compiled on 14:56:02 May 17 2023 with gcc 4.8.5
```
* **Operating System**:
```
Debian 9+, Ubuntu 16.04+, CentOS 7, ...
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3632
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3632(a)github.com>
[View Less]
remove stray debug print statement that results in generated code being invalid
<!-- 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 ...&#…
[View More]39;
- 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)
- [ ] 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/3760
-- Commit Summary --
* tools/kemi: fix bug in mock
-- File Changes --
M misc/tools/kemi/python_mock/kemi_mock.py (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3760.patchhttps://github.com/kamailio/kamailio/pull/3760.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3760
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3760(a)github.com>
[View Less]
Hello,
just a question about the https://rpm.kamailio.org/ repository, especially regarding git master builds. It seems that the git master build there was updated last autumn. It would be great if it could be updated, now as we want to test for the coming release.
Thank you,
Henning Westerholt
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com<https://gilawa.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, …
[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, ...)
- [ ] 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 -->
This PR adds a new parameter `prefix` to the function and its docs. It allows the message to be fixed with a prefix string.
Also fixes some leak issues.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3758
-- Commit Summary --
* file_out: Free allocated memory
* file_out: Add a prefix paramater
-- File Changes --
M src/modules/file_out/doc/file_out_admin.xml (13)
M src/modules/file_out/file_out.c (32)
M src/modules/file_out/types.c (9)
M src/modules/file_out/types.h (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3758.patchhttps://github.com/kamailio/kamailio/pull/3758.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3758
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3758(a)github.com>
[View Less]
Hello all,
I've noticed that there seems to be a regression with the topos module,
more specifically the redis flavour, but I'm assuming the storage backend
shouldn't make a difference.
I have confirmed this affects both 5.6.5 and 5.7-nightly, so I'm assuming
some backported commit is to blame. Kamailio 5.6.4 used previously, to the
best of my memory, was not affected.
Early dialog UPDATEs sent from the callee seem to be somehow malformed,
since the 200 OK the UAS produces goes directly to …
[View More]the UAC despite having
executed record_route() for the original INVITE. I can't imagine how this
is possible, I thought responses always honour the Via header and record
route shouldn't play a role in this case, right?
Simply turning topos off restores the intended behaviour, however, so I
can't help but think this is somehow related. Here's two call flows
demonstrating the behaviour:
* Topos on, 200 OK to UPDATE missing: https://pastebin.com/raw/J0zQeM5g
* Topos off, 200 OK to UPDATE routed correctly:
https://pastebin.com/raw/49yErezb
I was wondering if anyone is aware of any commits that might be responsible
for this. Additionally, is there an archive of debian packages with
previous point releases so that I can confirm this regression with the
latest versions?
Thank you!
Best regards,
George
[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 -->
- [ ] 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
- [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
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
This PR fixes small bugs, and improves docs.
#### Main bug fix:
- Fixup now should be able to handle the string from `.cfg` with multiple PVs, strings, and more.
- Add fixup_free functions
#### Smaller fixes:
- `base_folder` should not contain a trailing slash. Trailing slash is allowed, but resulting paths can contain `//log_file.extenion`, which in more OS is fine and equal to `/`.
- Add initial Readme and fix some docs.
- Switch to `str` type in internal types for better string handling.
- Free message when done
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3756
-- Commit Summary --
* file_out: Change default base folder format
* file_out: Add initial Readme and improve docs
* file_out: Switch to str type for string handling
* file_out: Free message when done
* file_out: Improve logging
* file_out: Fix fixup functions to handle all string.
-- File Changes --
A src/modules/file_out/README (171)
M src/modules/file_out/doc/file_out_admin.xml (4)
M src/modules/file_out/file_out.c (52)
M src/modules/file_out/types.c (19)
M src/modules/file_out/types.h (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3756.patchhttps://github.com/kamailio/kamailio/pull/3756.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3756
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3756(a)github.com>
[View Less]
### Description
Scenario: Kamailio servers running behind a loadbalancer (AWS network loadbalancer in this case). This causes all packets to come from the same IP address in Kamailio's POV.
The change https://github.com/kamailio/kamailio/commit/a902e4a032a85a7755de32eeadac800… introduced a connection limit per source IP address. This obviously conflicts with the setup mentioned above. We need up to 10000 client connections, which would seem to all come from the same IP address.
Apart from …
[View More]this limit being introduced without a changelog entry (at least I didn't find one), I would expect it to be configurable. But from the commit it looks like it is a compile time option only.
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
#### Log Messages
```
Feb 15 09:24:00 sipproxy /usr/sbin/kamailio[174]: CRITICAL: <core> [core/tcp_main.c:4447]: handle_new_connect(): hit the limit of connections per source IP (100.68.15.172:33334) - rejecting
Feb 15 09:24:01 sipproxy /usr/sbin/kamailio[174]: CRITICAL: <core> [core/tcp_main.c:4447]: handle_new_connect(): hit the limit of connections per source IP (100.68.15.172:1153) - rejecting
Feb 15 09:24:01 sipproxy /usr/sbin/kamailio[174]: CRITICAL: <core> [core/tcp_main.c:4447]: handle_new_connect(): hit the limit of connections per source IP (100.68.15.172:59946) - rejecting
```
### Additional Information
Using the packages from the official Kamailio repository.
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.7.4 (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, 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
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 11.4.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`)
-->
```
Ubuntu Jammy
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3755
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3755(a)github.com>
[View Less]
Hi,
we at sipgate would like to know if there is a reason why the xhttp_prom
module doesn't export statistics like stats.fetch all.
We are missing the tls.info as well as pkg.stats values.
Is there a reason for this? Are there any pointers on how we could
implement it ourselves and provide patches?
Best regards
Christian Berger
--
Christian Berger - berger(a)sipgate.de
Telefon: +49 (0)211-63 55 55-0
Telefax: +49 (0)211-63 55 55-22
sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf
…
[View More]HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois
Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391
www.sipgate.de - www.sipgate.co.uk
[View Less]
Module: kamailio
Branch: master
Commit: c89fe41b1583af74cdf7e20d2357d7c90990839f
URL: https://github.com/kamailio/kamailio/commit/c89fe41b1583af74cdf7e20d2357d7c…
Author: S-P Chan <shihping.chan(a)gmail.com>
Committer: S-P Chan <shihping.chan(a)gmail.com>
Date: 2024-02-14T15:20:35+08:00
db_mysql: fix typos
The option opt_ssl_ca is a string not integer.
The comment for ea81e6cb should show the code fix as
mysql_options(ptr->con, MYSQL_OPT_SSL_CA, (void *)db_mysql_opt_ssl_ca)
-…
[View More]--
Modified: src/modules/db_mysql/doc/db_mysql_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/c89fe41b1583af74cdf7e20d2357d7c…
Patch: https://github.com/kamailio/kamailio/commit/c89fe41b1583af74cdf7e20d2357d7c…
---
diff --git a/src/modules/db_mysql/doc/db_mysql_admin.xml b/src/modules/db_mysql/doc/db_mysql_admin.xml
index 7297f2d1b15..18c703838ce 100644
--- a/src/modules/db_mysql/doc/db_mysql_admin.xml
+++ b/src/modules/db_mysql/doc/db_mysql_admin.xml
@@ -219,7 +219,7 @@ modparam("db_mysql", "opt_ssl_mode", 1)
</example>
</section>
<section id="db_mysql.p.opt_ssl_ca">
- <title><varname>opt_ssl_ca</varname> (integer)</title>
+ <title><varname>opt_ssl_ca</varname> (string)</title>
<para>
Configures the CA certs used to verify the MySQL server cert when
SSL is enabled.
[View Less]
Module: kamailio
Branch: master
Commit: a61bfe9fb8357cedf5cb22e2698ec5d817fcfe5a
URL: https://github.com/kamailio/kamailio/commit/a61bfe9fb8357cedf5cb22e2698ec5d…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2024-02-14T08:16:19+01:00
modules: readme files regenerated - db_mysql ... [skip ci]
---
Modified: src/modules/db_mysql/README
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]a61bfe9fb8357cedf5cb22e2698ec5d…
Patch: https://github.com/kamailio/kamailio/commit/a61bfe9fb8357cedf5cb22e2698ec5d…
---
diff --git a/src/modules/db_mysql/README b/src/modules/db_mysql/README
index 8e135cdcbf2..17f8795581a 100644
--- a/src/modules/db_mysql/README
+++ b/src/modules/db_mysql/README
@@ -32,6 +32,7 @@ Daniel-Constantin Mierla
3.5. insert_delayed (integer)
3.6. update_affected_found (integer)
3.7. opt_ssl_mode (integer)
+ 3.8. opt_ssl_ca (integer)
4. Functions
5. Installation
@@ -46,9 +47,10 @@ Daniel-Constantin Mierla
1.5. Set insert_delayed parameter
1.6. Set update_affected_found parameter
1.7. Set opt_ssl_mode parameter
- 1.8. Set a my.cnf group in db_url parameter
- 1.9. Adding a kamailio group to my.cnf
- 1.10. Using [client] and specific group
+ 1.8. Set opt_ssl_ca parameter
+ 1.9. Set a my.cnf group in db_url parameter
+ 1.10. Adding a kamailio group to my.cnf
+ 1.11. Using [client] and specific group
Chapter 1. Admin Guide
@@ -69,6 +71,7 @@ Chapter 1. Admin Guide
3.5. insert_delayed (integer)
3.6. update_affected_found (integer)
3.7. opt_ssl_mode (integer)
+ 3.8. opt_ssl_ca (integer)
4. Functions
5. Installation
@@ -107,6 +110,7 @@ Chapter 1. Admin Guide
3.5. insert_delayed (integer)
3.6. update_affected_found (integer)
3.7. opt_ssl_mode (integer)
+ 3.8. opt_ssl_ca (integer)
3.1. ping_interval (integer)
@@ -212,6 +216,21 @@ modparam("db_mysql", "update_affected_found", 1)
modparam("db_mysql", "opt_ssl_mode", 1)
...
+3.8. opt_ssl_ca (integer)
+
+ Configures the CA certs used to verify the MySQL server cert when SSL
+ is enabled.
+
+ Required when opt_ssl_mode = 4 or 5 and db_mysql is built with
+ libmysqlclient.
+
+ Default value is NULL (NULL - not configured).
+
+ Example 1.8. Set opt_ssl_ca parameter
+...
+modparam("db_mysql", "opt_ssl_ca", "/etc/ssl/certs/mysql-ca.pem")
+...
+
4. Functions
No function exported to be used from configuration file.
@@ -238,12 +257,12 @@ modparam("db_mysql", "opt_ssl_mode", 1)
* mysql://user:pass@[group]/db
* mysql://[group]/db
- Example 1.8. Set a my.cnf group in db_url parameter
+ Example 1.9. Set a my.cnf group in db_url parameter
...
modparam("usrloc", "db_url", "mysql://[kamailio]/kamailio)
...
- Example 1.9. Adding a kamailio group to my.cnf
+ Example 1.10. Adding a kamailio group to my.cnf
...
[kamailio]
socket = /path/to/mysql.sock
@@ -257,7 +276,7 @@ default-character-set = utf8
both your specific group and the client group, then the value is taken
from the last one.
- Example 1.10. Using [client] and specific group
+ Example 1.11. Using [client] and specific group
...
[client]
socket = /run/mysql/mysqld.sock
[View Less]
Hello all,
Following up on this, I made a patch (attached), could you please review
and apply if it looks ok?
The patch creates a new core cfg variable which, if set, will reject any
incoming NEW tcp connection attempt, so we can use this to gracefully drain
kamailio.
Thanks & Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
phone: +34669448337
Forwarded Conversation
Subject: Reject TCP SYN
------------------------
From: David Villasmil <david.villasmil.work(a)gmail.…
[View More]com>
Date: Thu, Feb 8, 2024 at 2:27 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Hello all,
Is there any way of actually rejecting (RST) NEW tcp connection attempts,
while allowing the ongoing ones to finish naturally?
I’m thinking maybe we can add this feature?
Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
phone: +34669448337
----------
From: Henning Westerholt <hw(a)gilawa.com>
Date: Fri, Feb 9, 2024 at 2:08 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Cc: David Villasmil <david.villasmil.work(a)gmail.com>
Hello,
what about e.g. just using something like iptables, nftables etc..?
iptables -A INPUT -p tcp --syn --destination-port <port> -j REJECT
--reject-with icmp-host-prohibited
Cheers,
Henning
----------
From: David Villasmil <david.villasmil.work(a)gmail.com>
Date: Fri, Feb 9, 2024 at 2:42 PM
To: Henning Westerholt <hw(a)gilawa.com>
Cc: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Hey, Henning, yeah I thought about that, but thought that maybe there was a
better way to do it via Kamailio
Thanks!
Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
phone: +34669448337
[View Less]
### Description
I've recently spent some time debugging a case with JsSIP and usernames in form of a generated string which can be both upper and lower case letters plus digits.
On BYE from callee to JsSIP, it responded with a "404" and "Request-URI does not point to us" in the console while debugging.
JsSIP is using the Contact returned in the 200 OK to REGISTER (which is transformed to all lower case) for new outgoing INVITE.
It does not match this against the one used in BYE correctly, and …
[View More]return "404".
I see there is a setting in the registrar about this:
```
3.11. case_sensitive (integer)
If set to 1 then AOR comparison and also storing will be case sensitive, if set to 0 then AOR comparison and storing will be case insensitive.
This is recommended. This parameter can be modified via Kamailio config framework.
Default value is 0.
```
Since the RFC states that username should be handle case-sensitive, maybe it would be smart to change this default?
```
Comparison of the userinfo of SIP and SIPS URIs is case-
sensitive. This includes userinfo containing passwords or
formatted as telephone-subscribers.
...
The URIs within each of the following sets are not equivalent:
SIP:ALICE@AtLanTa.CoM;Transport=udp (different usernames)
sip:alice@AtLanTa.CoM;Transport=UDP
```
#### Reproduction
Make a registration with a username containing both upper and lower case characters. It will be stored in all lower case.
### Possible Solutions
Change default value.
Regardless of the outcome on this case - at least now there is a note about it here too.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3719
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3719(a)github.com>
[View Less]
Module: kamailio
Branch: 5.7
Commit: 2f0cca81bfc47783098e4c869b038229cd3e4ed0
URL: https://github.com/kamailio/kamailio/commit/2f0cca81bfc47783098e4c869b03822…
Author: S-P Chan <shihping.chan(a)gmail.com>
Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Date: 2024-02-12T07:52:26+01:00
Sample etc/kamailio.cfg: global var tls_threads_mode
- load tls first if used
- global var tls_threads_mode
---
Modified: etc/kamailio.cfg
---
Diff: https://github.com/kamailio/…
[View More]kamailio/commit/2f0cca81bfc47783098e4c869b03822…
Patch: https://github.com/kamailio/kamailio/commit/2f0cca81bfc47783098e4c869b03822…
---
diff --git a/etc/kamailio.cfg b/etc/kamailio.cfg
old mode 100644
new mode 100755
index fe7b111a012..a95a652b935
--- a/etc/kamailio.cfg
+++ b/etc/kamailio.cfg
@@ -220,6 +220,13 @@ enable_tls=yes
/* upper limit for TLS connections */
tls_max_connections=2048
+
+/* For OpenSSL 3 integration
+ * functions calling libssl3 can be invoked in a transient thread
+ * 0: disable threaded calls
+ * 1: use threads for process#0 only
+ * 2: use threads for all processes */
+tls_threads_mode=1
#!endif
/* set it to yes to enable sctp and load sctp.so module */
@@ -257,6 +264,12 @@ voicemail.srv_port = "5060" desc "VoiceMail Port"
/* set paths to location of modules */
# mpath="/usr/local/lib/kamailio/modules/"
+# when using TLS with OpenSSL it is recommended to load this module
+# first so that OpenSSL is initialized correctly
+#!ifdef WITH_TLS
+loadmodule "tls.so"
+#!endif
+
#!ifdef WITH_MYSQL
loadmodule "db_mysql.so"
#!endif
@@ -319,10 +332,6 @@ loadmodule "rtpproxy.so"
#!endif
#!endif
-#!ifdef WITH_TLS
-loadmodule "tls.so"
-#!endif
-
#!ifdef WITH_HTABLE
loadmodule "htable.so"
#!endif
[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
This PR restores the default behaviour of stable branch and makes libssl thread-guard work opt-in.
- user's config from 5.7.3 will run unchanged
- backport tls_threads_mode = 0|1|2 from dev; user must explicitly opt-in to libssl changes
Scenario 1: user does not change 5.7.3 configuration; then libssl thread-guards will be disabled and Kamailio will run as before
Scenario 2: user must opt-in to libssl thread-guards; `tls_threads_mode` has been backported from dev and user must use `tls_threads_mode = 1` in the configuration. The default value is `tls_threads_mode = 0`
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3754
-- Commit Summary --
* core: added tls_threads_mode global parameter
* core/rthreads.h: use global ksr_tls_threads_mode to constrain thread
* Sample etc/kamailio.cfg: global var tls_threads_mode
* tls: restore default to bypass thread guards
-- File Changes --
M etc/kamailio.cfg (17)
M src/core/cfg.lex (2)
M src/core/cfg.y (9)
M src/core/globals.h (1)
M src/core/rthreads.h (33)
M src/main.c (5)
M src/modules/tls/tls_mod.c (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3754.patchhttps://github.com/kamailio/kamailio/pull/3754.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3754
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3754(a)github.com>
[View Less]
<!--
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:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio…
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* https://lists.kamailio.org/mailman3/postorius/…
[View More]lists/sr-dev.lists.kamailio.o…
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
Note that an issue report may be closed automatically after about 2 months
if there is no interest from developers or community users on pursuing it, being
considered expired. In such case, it can be reopened by writing a comment that includes
the token `/notexpired`. About two weeks before considered expired, the issue is
marked with the label `stale`, trying to notify the submitter and everyone else
that might be interested in it. To remove the label `stale`, write a comment that
includes the token `/notstale`. Also, any comment postpone the `expire` timeline,
being considered that there is interest in pursuing 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
While doing a call, new dialogue is not created in PCSCF. RX feature is on. As per my understanding, ims_dialog has one call back function and it invokes dlg_onreq() function and a new dialgue can be created (function is dlg_new_dialog). And in the traces, that is not happening.
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
### Troubleshooting
I have added additional traces for troubleshooting, and I can see that in case of PCSCF, new dialog is not created. And later on Rx feature is not working as expected.
#### Reproduction
Everytime
<!--
If the issue can be reproduced, describe how it can be done.
-->
Need to do Two UEs VoLTE registration and then a call from UE1 to UE2
#### 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.
-->
```
(paste your debugging data here)
```
#### 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).
-->
```
(paste your log messages here)
```
#### 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).
-->
```
(paste your sip traffic here)
```
### 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`
```
(paste your output here)
```
root@openims-node-focal:/usr/local/etc/kamailio# kamailio -v
version: kamailio 5.7.2 (x86_64/linux) 02958e
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
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: 02958e
compiled on 18:07:29 Oct 17 2023 with gcc 9.4.0
* **Operating System**:
ubuntu
uname -a
Linux openims-node-focal 5.4.0-166-generic #183-Ubuntu SMP Mon Oct 2 11:28:33 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
<!--
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`)
-->
```
(paste your output here)
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3676
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3676(a)github.com>
[View Less]
<!--
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…
[View More]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
The reginfo notifications sent via pua_reginfo + presence_reginfo contains the version fixed to `0`.
The pua docs report the param `reginfo_increase_version` which should increase the version if enabled, but currently does nothing.
Looking into the code seems to confirm that, param is read from `pua` module but is not used anywhere. While the param `dlginfo_increase_version` seems to be used for the intended scope.
#### Reproduction
Setup pua + pua_reginfo to publish registration informations and observe that version param of reginfo is always 0, not respecting pua `reginfo_increase_version` setting.
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.6.1 (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_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 9.4.0
```
* **Operating System**:
```
Linux Debian bullseye/sid
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3234
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3234(a)github.com>
[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 -->
This PR updates `file_out` module to support the definition of extension and interval on a per-file basis.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3750
-- Commit Summary --
* file_out: Add support for multiple files, extensions and interval
* file_out: Update docs
-- File Changes --
M src/modules/file_out/doc/file_out_admin.xml (117)
M src/modules/file_out/file_out.c (164)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3750.patchhttps://github.com/kamailio/kamailio/pull/3750.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3750
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3750(a)github.com>
[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
Add global config var
```
enable_tls_thread=1 #0 | 1 | 2
```
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3745
-- Commit Summary --
* step-1
* step-2
* step-3
-- File Changes --
M src/core/cfg.lex (2)
M src/core/cfg.y (5)
M src/core/globals.h (1)
M src/core/rthreads.h (19)
M src/main.c (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3745.patchhttps://github.com/kamailio/kamailio/pull/3745.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3745
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3745(a)github.com>
[View Less]
fixes code generation when python keywords are used
fixes formating issues of generated code
fixes crash from pv.setl reporting parameters as null instead of 'none'
made example more complete
<!-- 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
- [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
- [ ] 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/3751
-- Commit Summary --
* tools/kemi: update kemi_mock for python
-- File Changes --
M misc/tools/kemi/python_mock/kemi_mock.py (51)
M misc/tools/kemi/python_mock/test.py (12)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3751.patchhttps://github.com/kamailio/kamailio/pull/3751.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3751
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3751(a)github.com>
[View Less]
Module: kamailio
Branch: master
Commit: 6918c9e34b826f8d8c7fb1746851055fa35f8ece
URL: https://github.com/kamailio/kamailio/commit/6918c9e34b826f8d8c7fb1746851055…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2024-02-09T10:01:34+01:00
modules: readme files regenerated - ldap ... [skip ci]
---
Modified: src/modules/ldap/README
---
Diff: https://github.com/kamailio/kamailio/commit/6918c9e34b826f8d8c7fb1746851055……
[View More]Patch: https://github.com/kamailio/kamailio/commit/6918c9e34b826f8d8c7fb1746851055…
---
diff --git a/src/modules/ldap/README b/src/modules/ldap/README
index 921f45822f1..d69005f864e 100644
--- a/src/modules/ldap/README
+++ b/src/modules/ldap/README
@@ -31,6 +31,7 @@ Christian Schlatter
4. Parameters
4.1. config_file (string)
+ 4.2. connect_mode (int)
5. Functions
@@ -82,12 +83,13 @@ Christian Schlatter
1.6. ldap_client_bind_timeout example
1.7. Example LDAP Configuration File
1.8. config_file parameter usage
- 1.9. Example Usage of ldap_url
- 1.10. Example Usage
+ 1.9. Set connect_mode parameter
+ 1.10. Example Usage of ldap_url
1.11. Example Usage
1.12. Example Usage
1.13. Example Usage
1.14. Example Usage
+ 1.15. Example Usage
2.1. Example code fragment to load LDAP module API
2.2. Example LDAP module API function call
@@ -114,6 +116,7 @@ Chapter 1. Admin Guide
4. Parameters
4.1. config_file (string)
+ 4.2. connect_mode (int)
5. Functions
@@ -418,6 +421,7 @@ ldap_client_bind_timeout = 500
4. Parameters
4.1. config_file (string)
+ 4.2. connect_mode (int)
4.1. config_file (string)
@@ -428,6 +432,17 @@ ldap_client_bind_timeout = 500
Example 1.8. config_file parameter usage
modparam("ldap", "config_file", "/usr/local/etc/kamailio/ldap.ini")
+4.2. connect_mode (int)
+
+ Control if the module must stop loading when connecting to server fails
+ during start up. Values: 0 - stop loading; 1 - continue even if
+ connecting to database server fails..
+
+ Default value: 0
+
+ Example 1.9. Set connect_mode parameter
+modparam("ldap", "connect_mode", 1)
+
5. Functions
5.1. ldap_search(ldap_url)
@@ -458,7 +473,7 @@ modparam("ldap", "config_file", "/usr/local/etc/kamailio/ldap.ini")
Kamailio pseudo variables and AVPs included in ldap_url do get
substituted with their value.
- Example 1.9. Example Usage of ldap_url
+ Example 1.10. Example Usage of ldap_url
Search with LDAP session named sipaccounts, base
ou=sip,dc=example,dc=com, one level deep using search filter
@@ -492,7 +507,7 @@ ldap://ldap_1/dc=example,dc=com?
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE,
BRANCH_ROUTE, and ONREPLY_ROUTE.
- Example 1.10. Example Usage
+ Example 1.11. Example Usage
...
# ldap search
if (!ldap_search("ldap://sipaccounts/ou=sip,dc=example,dc=com??one?(cn=$rU)"))
@@ -570,7 +585,7 @@ ldap_result("telephoneNumber/$avp(s:tel_number)");
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE,
BRANCH_ROUTE, and ONREPLY_ROUTE.
- Example 1.11. Example Usage
+ Example 1.12. Example Usage
...
# ldap_search call
@@ -639,7 +654,7 @@ ldap_result("SIPIdentitySIPURI/$avp(i:10)", "/^[^@]+@(.+)$/\1/");
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE,
BRANCH_ROUTE, and ONREPLY_ROUTE.
- Example 1.12. Example Usage
+ Example 1.13. Example Usage
...
# ldap_search call
...
@@ -688,7 +703,7 @@ if (!ldap_result_check("sn/$ru", "/^sip:([^@]).*$/\1/"))
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE,
BRANCH_ROUTE, and ONREPLY_ROUTE.
- Example 1.13. Example Usage
+ Example 1.14. Example Usage
...
# ldap_search call
...
@@ -745,7 +760,7 @@ if (ldap_result_next())
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE,
BRANCH_ROUTE, and ONREPLY_ROUTE.
- Example 1.14. Example Usage
+ Example 1.15. Example Usage
...
if (!ldap_filter_url_encode("cn=$avp(s:name)", "$avp(s:name_esc)"))
{
[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 -->
This PR aims to give the option for ldap to allow kamailio to start-up even if server is not reachable/available when starting.
It follows similar logic to https://github.com/kamailio/kamailio/commit/2df43b992b1e6932974bd0c928c0465… for SQL.
A new config parameter for `ldap` module is defined, `connect_mode`, that defaults to 0, preserving the old behavior. If it's set `1`, `kamailio` will not exit and allow `ldap` to try and reconnect when necessary.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3747
-- Commit Summary --
* ldap: option to start even when connecting to server fails
* ldap/docs: Add connect_mode docs
-- File Changes --
M src/modules/ldap/doc/ldap_admin.xml (18)
M src/modules/ldap/ldap_mod.c (15)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3747.patchhttps://github.com/kamailio/kamailio/pull/3747.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3747
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3747(a)github.com>
[View Less]
### Description
Via sngrep I can see call was terminated via BYE message but was not terminated on RTPengine hosts. The `rtpengine-ctl list sessions all` show calls that was terminated properly via BYE message.
In the kamailio config used `rtpengine_manage` function.
I do not have any idea how to troubleshoot this.
Could you suggest next step and I will add more details for this issue
### Additional Information
* **Kamailio Version**
Used 5.6.4 with small customization.
```
version: …
[View More]kamailio 5.6.4 (aarch64/linux) 06ad45
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-NOSMP, 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: 06ad45
compiled on 16:37:11 Aug 7 2023 with gcc 8.5.0
```
* **Operating System**:
CentOS 8 Stream, aarch64
```
[root@sbc-a0 ~]# uname -a
Linux sbc-a0.nga911.com 4.19.113-300.el8.aarch64 #1 SMP Fri May 12 11:47:07 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux
[root@sbc-a0 ~]# cat /etc/os-release
NAME="CentOS Stream"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Stream 8"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream"
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3749
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3749(a)github.com>
[View Less]
#### 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
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [X] New feature …
[View More](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
@henning @miconda this is a draft for the 5.7 stable branch which disables threading for process_no > 0. This restricts thread wrappers to the parent process.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3744
-- Commit Summary --
* [DRAFT]: restrict thread execution to process_no = 0
-- File Changes --
M src/core/rthreads.h (18)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3744.patchhttps://github.com/kamailio/kamailio/pull/3744.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3744
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3744(a)github.com>
[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
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
Audit of libssl calls with default kamailio.cfg + database using MariaDB and PostgreSQL and add libssl thread guards.
Debian 12: for the default kamailio.cfg we build db_mysql / db_postgres / db_unixodbc and enable database with SSL
1. mariadb-client, libmariadb-dev, odbc-mariadb
2. postgresql-15, postgresql-client-15, odbc-postgresql
This PR adds thread guards for all function calls that touch thread-locals in process#0thread1
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3748
-- Commit Summary --
* core/rthreads.h: thread wrapper for db_XXXX_query
* db_postgres: libssl thread guard for db_postgres_close
* db_unixodbc: libssl thread guards for db_unixodbc_(close|free_result|query)
* db_mysql: libssl thread guard for db_mysql_close
-- File Changes --
M src/core/rthreads.h (53)
M src/modules/db_mysql/km_dbase.c (8)
M src/modules/db_postgres/km_dbase.c (8)
M src/modules/db_unixodbc/dbase.c (27)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3748.patchhttps://github.com/kamailio/kamailio/pull/3748.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3748
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3748(a)github.com>
[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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
After enabling the Topos module, we ran into a bit of trouble with early in-dialog notifies. We use the `event: talk` package from Cisco Broadsoft to be able to do call control, as described in chapter 6 here: https://pubhub.devnetcloud.com/media/broadsoft-docs/docs/pdf/BW-SIPAccessSi…
This will send a NOTIFY with a header `Event: talk` before the first `200 OK`. Currently this doesn't work with the topos module, since the NOTIFY method without a B-side contact will not check the INVITE record. When added to those methods in `tps_msg.c`, it tries to check the SUBSCRIBE for all NOTIFY's in `tps_storage.c`. The NOTIFY with `Event: talk` will follow on an INVITE, so there was a small change needed there.
I've limited it to just the NOTIFY's with the `Event: talk` header, to minimize any impact.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3627
-- Commit Summary --
* topos: add compatiblity for early in-dialog NOTIFY
-- File Changes --
M src/modules/topos/tps_msg.c (5)
M src/modules/topos/tps_storage.c (3)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3627.patchhttps://github.com/kamailio/kamailio/pull/3627.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3627
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3627(a)github.com>
[View Less]
Hi everybody,
I normally use MongoDB as DB engine in my projects and I would like to get all MongoDB advantages when working with Kamailio. For this reason, I need to deal with arrays of information inside a document (for example, an array of contacts inside a document).
And now the question: is it possible to insert, update and search info in a MongoDB document by using arrays via srdb1 lib? If yes, how? And if not, are you thinking about implementing it in the future?
Thank you very much …
[View More]for your time.
Regards,
Mario
[View Less]
### Description
Request the RPM packaging of wolfSSL 5.6.6 for the upcoming freeze
### Expected behavior
I intend to bump the internal submodule to 5.6.6 and it would be good if Kamailio RPM packages could be updated.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3713
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3713(a)github.com>
### Description
OpenSSL integration update was back-ported to 5.7 fixing tls and outbound.
The commonly used modules db_mysql, db_unixodbc, db_postgres - fixed on master - did not receive thread-local fixes in time for 5.7.4.
Kamailio configurations with tls +(database module) may see shm errors
Some database modules are observed to initialise OpenSSL even if the actual db connections are in clear.
### Troubleshooting
- run the main kamailio process under gdb.
- set breakpoint on …
[View More]CRYPTO_THREAD_set_local (an OpenSSL internal thread-local function)
- observe if any calls happen in Thread#1—this is the failure case
### Workaround
When combining tls + database module switch to tls_wolfssl instead
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3738
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3738(a)github.com>
[View Less]
@miconda @linuxmaniac - compilation fixes and handling of older versions(libmariadb-dev) squash-included here. Thank you.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/ede2af94386b99a87311351fcbdd152…
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/commit/ede2af94386b99a87311351fcbdd15280dc11034/138246612(a)github.com>
@linuxmaniac - I have included the Xenial fix from master here. Thanks!
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/9a87d12d6e9e68cd8c0ff7ac5755e89…
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/commit/9a87d12d6e9e68cd8c0ff7ac5755e899cf81b703/138246585(a)github.com>
#### 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 #3738 (replace XXXX with an open issue number)
#### Description
5.7.4 has OpenSSL fixes for tls and outbound but missed out the db modules—the most common users of libssl
This PR updates db_mysql, db_unixodbc, db_postgres to init libssl in a thread to handle more configurations (tls + db module)
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3740
-- Commit Summary --
* core: backport OpenSSL thread-local fixes
* db_mysql: backport OpenSSL thread-local fixes
* db_postgres: backport OpenSSL thread-local fixes
* db_unixodbc: backport OpenSSL thread-local fixes
-- File Changes --
A src/core/rthreads.h (100)
M src/modules/db_mysql/km_dbase.c (9)
M src/modules/db_postgres/km_dbase.c (19)
M src/modules/db_unixodbc/dbase.c (11)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3740.patchhttps://github.com/kamailio/kamailio/pull/3740.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3740
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3740(a)github.com>
[View Less]
version: kamailio 5.5.2 (arm6/linux) 55e232
raspberry pi 3b
I initially stated that I was running on 5.5.3 but I was mistaken. However I checked the 5.5.3 source and it appears to be the same.
I think that there is a bug in the tm module with respect to the "tm:local-response" event route. In the "t_reply.c" file, there is a static variable called '_tm_local_response_set_lookup'. This variable is initialized at load time to zero. It is checked in the '_reply_light()' routine and will …
[View More]initiate a local callback from the config script if "armed". The problem as I see it is that if the callback is readied, the variable is set to one. But it is never reset.
So the observed behavior is as follows. A REGISTER is received and the request_route arms the callback. The REGISTER requires an authorization (local database sqlite). After the 401 is sent back, the callback via the event route is called as expected. All good except that the event route script fragment is never executed again after the first call... ever, even if it's a new REGISTER request.
I would think that somewhere in the tm module, the variable should be reset to zero so that subsequent transactions can initiate the event route again. Or maybe the variable ought to live somewhere in the transaction cell???
. . .
t_on_reply ("MY_FRAG");
t_on_failure ("MY_FRAG");
. . .
event_route [tm:local-response] {
xlog ("L_NOTICE", IN tm:local-response\n");
my_function();
}
. . .
So 'my_function()' is only called once.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3064
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3064(a)github.com>
[View Less]
### Description
I have enabled `tcp_accept_haproxy=yes`, inbound TCP connection received on IPv6 kamailio socket but client real IP is IPv4.
When kamailio add `Record-Route` header then added IPv6 header and not added IPv4.
Example
```
INVITE sip:xxxx@example.com SIP/2.0
Record-Route: <sip:9sovfn2oP7ozLQID7BkFxBNt/CfE+wc=@[2600::6]:5060;r2=on;lr=on>
Record-Route: <sip:9sovfn2oP7ozLQID7BkFxBNt/CfE+wc=@[2600::6]:5060;transport=tcp;r2=on;lr=on>
```
From client perspective Kamailio make …
[View More]protocol conversion from the IPv4 to IPv6, and expected to see IPv4 in the IPv4 address in the received 'Record-Route' headers to use in the future requests.
Because client receiving IPv6 only and client does not have IPv6 address, then `ACK` message cannot be send to Kamailio.
### Expected behavior
Kamailio will use Kamailio server load balancer address to generate `Record-Route` headers.
Load balancer IP address can be received from the HAPROXY protocol.
#### Actual observed behavior
Kamailio use listeneer socket IP to generate `Record-Route` headers.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3666
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3666(a)github.com>
[View Less]
### Description
partition is now a reserved word in MariaDB 10.
the column name is correctly quoted with native libmysqlclient/libmariadb so works
the column name is not quoted with unixodbc+(libmyodbc8|libmaodbc) and so fails
### Troubleshooting
try unquoted insert
-- fails unixodbc+libmaodbc
insert into location (partition) values (1000);
-- works native libmysqlclient|libmariadb
insert into location (`partition`) values (1000);
#### Reproduction
1. config enable usrloc / registrar …
[View More]with unixodbc + MySQL/MariaDB connector
#### Debugging Data
SQL insert into statement fails
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3742
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3742(a)github.com>
[View Less]
Hello,
the formal notification that the development for the next major version
5.8.0 is now frozen. The focus has to be on testing the master branch.
Also, the master branch should not get commits with new features till
the branch 5.8 is created, expected to happen in 2-4 weeks, a matter of
how testing goes on. Meanwhile, the commits with new features in the C
code can be pushed to personal branches, new pull requests can still be
done, but they will be merged after branching 5.8.
Can still …
[View More]be done commits with documentation improvements, enhancements
to related tools (e.g., kamctl, kamcmd), merging exiting pull requests
at this moment, exporting missing KEMI functions and completing the
functionality of the new modules added for 5.8.
Once the branch 5.8 is created, new features can be pushed again to
master branch as usual. From that moment, the v5.8.0 should be out very
soon, time used for further testing but also preparing the release of
packages.
If someone is not sure if a commit brings a new feature, just make a
pull request and it can be discussed there on github portal or via
sr-dev mailing list.
A summary of what is new in upcoming 5.8 is going to be built at:
* https://www.kamailio.org/wikidocs/features/new-in-5.8.x/
Upgrade guidelines will be collected at:
* https://www.kamailio.org/wikidocs/install/upgrade/5.7.x-to-5.8.0/
Everyone is more than welcome to contribute to the above wiki pages,
especially to the upgrade guidelines, to help everyone else during the
migration process from v5.7.x to 5.8.x.
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
[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
- [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
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
This PR fixes an issue regarding KEMI framework for onsend_route.
KSR.set_drop() in [ksr_onsend_route](https://www.kamailio.org/wikidocs/cookbooks/5.7.x/core/#o… does not make kamailio dropping the message when using kemi (python3) (probably holds true for other engines too):
This is exactly the example from [documentation](https://kamailio.org/docs/tutorials/devel/kamailio-kemi-fram…:
```
def ksr_onsend_route(self, msg):
KSR.set_drop()
exit()
```
The issue arises because we are not setting `ret = 0` when the drop flag is set, but instead check if it's not set to return `ret=1` (The case for native that returns `0` but no `DROP_R_F` was set).
**Note**:
KEMI Case: `ret = 1` always See [app_python3/apy_kemi.c](https://github.com/kamailio/kamailio/blob/79697b4d5…
Native case: `ret` can be `0` for drop, or `1` for success
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3718
-- Commit Summary --
* core: Fix check to also work for KEMI framework
-- File Changes --
M src/core/onsend.c (13)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3718.patchhttps://github.com/kamailio/kamailio/pull/3718.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3718
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3718(a)github.com>
[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 -->
This pull request is intended to introduce a new, straightforward module that can efficiently stream output to files while also handling changes based on a specific interval. The module contains only one function that streams a chunk of text to the current output file handle associated with the given file index.
It's not 100% completed but the basic features are there. Any reviews and of course naming of the module, much appreciated.
---
How the module works:
- Set parameter `base_folder` to define where you want your logs to be saved.
- Set `base_filename` (up to 10) to define the names of your files. Each is associated with an index according to the order you defined it. First `base_filename`'s index is 0, second's index is 1 and so on. This is appended with a new timestamp when `interval_seconds` are passed.
- Set `interval_seconds` to define how much time before the file is closed and a new one is opened. Right now shared for all files.
- Set `extension` to define what should be the extension of files. Right now shared for all files.
Use the provided function `file_out` to write any text (including pvs) to a specific file you want.
---
**Example:**
Define parameters such as:
```
# kamailio.cfg
...
loadmodule "file_out.so"
modparam("file_out", "base_folder", "/tmp/kamailio/file_out/")
modparam("file_out", "base_filename", "accounting")
modparam("file_out", "base_filename", "missed_calls")
modparam("file_out","interval_seconds", 600)
modparam("file_out","extension", ".txt")
...
request_route {
...
file_out("0", "Writing to accounting.txt file $rm from $fu (IP:$si:$sp)");
file_out("1", "Writing to missed_calls.txt file $rm from $fu (IP:$si:$sp)");
...
}
```
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3741
-- Commit Summary --
* file_out: Add new module
* file_out: Add docs
-- File Changes --
A src/modules/file_out/Makefile (8)
A src/modules/file_out/doc/Makefile (4)
A src/modules/file_out/doc/file_out.xml (39)
A src/modules/file_out/doc/file_out_admin.xml (191)
A src/modules/file_out/file_out.c (380)
A src/modules/file_out/types.c (88)
A src/modules/file_out/types.h (25)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3741.patchhttps://github.com/kamailio/kamailio/pull/3741.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3741
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3741(a)github.com>
[View Less]
Module: kamailio
Branch: master
Commit: 4c144ac1ad40008b5bd9396aa18d7630145b4c4c
URL: https://github.com/kamailio/kamailio/commit/4c144ac1ad40008b5bd9396aa18d763…
Author: Henning Westerholt <hw(a)gilawa.com>
Committer: Henning Westerholt <hw(a)gilawa.com>
Date: 2024-02-01T19:22:53Z
file_out: small doc adaptions
---
Modified: src/modules/file_out/doc/file_out_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/4c144ac1ad40008b5bd9396aa18d763…
Patch: https://github.…
[View More]com/kamailio/kamailio/commit/4c144ac1ad40008b5bd9396aa18d763…
---
diff --git a/src/modules/file_out/doc/file_out_admin.xml b/src/modules/file_out/doc/file_out_admin.xml
index ed6b18268d0..a701156ccba 100644
--- a/src/modules/file_out/doc/file_out_admin.xml
+++ b/src/modules/file_out/doc/file_out_admin.xml
@@ -17,15 +17,15 @@
<section>
<title>Overview</title>
<para>
- This is a simple module to support fast streaming output to file name
- and handle that changes on an interval. It implements only one function
- that streams a chunk of text to the current output file handle.
+ This is a small module to support fast streaming output to files
+ and process this changes depending on an interval. It implements only one
+ function that streams a chunk of text to the current output file handle.
</para>
<para>
The module can be used to write logs for up to 10 different log files.
Each log file can be configured to have a different name and extension.
- String can contain pseudo-variables. The module will replace the
- pseudo-variables with the actual values. The module will also rotate
+ The processed string can contain pseudo-variables. The module will replace
+ the pseudo-variables with the actual values. The module will also rotate
the log files at a specified interval. The interval is specified in seconds.
</para>
</section>
[View Less]
Module: kamailio
Branch: master
Commit: dd5c9a5204eb946e731550a0ee7f3046c7065515
URL: https://github.com/kamailio/kamailio/commit/dd5c9a5204eb946e731550a0ee7f304…
Author: Xenofon Karamanos <xk(a)gilawa.com>
Committer: GitHub <noreply(a)github.com>
Date: 2024-02-01T18:15:17+01:00
file_out: Module to log custom strings to files (GH #3741)
* add new module to log custom strings to files (GH #3741)
* support for multiple files and also file balancing
* smaller refactorings will be …
[View More]done afterwards (use string in function for names with internal matching, make worker sleep also configurable
* a round of tests has been done, but it will be certainly tested more in the next days
---
Added: src/modules/file_out/Makefile
Added: src/modules/file_out/doc/Makefile
Added: src/modules/file_out/doc/file_out.xml
Added: src/modules/file_out/doc/file_out_admin.xml
Added: src/modules/file_out/file_out.c
Added: src/modules/file_out/types.c
Added: src/modules/file_out/types.h
---
Diff: https://github.com/kamailio/kamailio/commit/dd5c9a5204eb946e731550a0ee7f304…
Patch: https://github.com/kamailio/kamailio/commit/dd5c9a5204eb946e731550a0ee7f304…
[View Less]
Hello,
I propose to aim freezing the development for 5.8.x series at the end of
the 1st of February 2024 (Thursday).
New features that one wants to get in this release series have to be
pushed to git repository or pull requests made for them. Afterwards
usually follows a 4-6 weeks of testing till the first release 5.8.0.
Unfreezing will happen earlier, after the first weeks of testing when
the 5.8 branch will be created.
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/…
[View More]miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
[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 #3738 (replace XXXX with an open issue number)
#### Description
5.7.4 has OpenSSL fixes for tls and outbound but missed out the db modules—the most common users of libssl
This PR updates db_mysql, db_unixodbc, db_postgres to init libssl in a thread to handle more configurations (tls + db module)
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3739
-- Commit Summary --
* geoip: docs - removed trailing spaces
* geoip2: docs - removed trailing spaces
* group: docs - removed trailing spaces
* gzcompress: docs - removed trailing spaces
* h350: docs - removed trailing spaces
* htable: docs - removed trailing spaces
* http_async_client: docs - removed trailing spaces
* imc: docs - removed trailing spaces
* ims_auth: docs - removed trailing spaces
* ims_charging: docs - removed trailing spaces
* ims_diameter_server: docs - removed trailing spaces
* ims_icscf: docs - removed trailing spaces
* ims_isc: docs - removed trailing spaces
* ims_ocs: docs - removed trailing spaces
* ims_qos: docs - removed trailing spaces
* ims_registrar_pcscf: docs - removed trailing spaces
* ims_registrar_scscf: docs - removed trailing spaces
* ims_usrloc_pcscf: docs - removed trailing spaces
* ims_usrloc_scscf: docs - removed trailing spaces
* ipops: docs - removed trailing spaces
* jansson: docs - removed trailing spaces
* janssonrpcc: docs - removed trailing spaces
* json: docs - removed trailing spaces
* jsonrpcc: docs - removed trailing spaces
* kafka: docs - removed trailing spaces
* kazoo: docs - removed trailing spaces
* keepalive: docs - removed trailing spaces
* kex: docs - removed trailing spaces
* lcr: docs - removed trailing spaces
* ldap: docs - removed trailing spaces
* log_custom: docs - removed trailing spaces
* log_systemd: docs - removed trailing spaces
* lost: docs - removed trailing spaces
* lrkproxy: docs - removed trailing spaces
* mangler: docs - removed trailing spaces
* matrix: docs - removed trailing spaces
* maxfwd: docs - removed trailing spaces
* memcached: docs - removed trailing spaces
* misc_radius: docs - removed trailing spaces
* misctest: docs - removed trailing spaces
* mqtt: docs - removed trailing spaces
* mqueue: docs - removed trailing spaces
* msilo: docs - removed trailing spaces
* msrp: docs - removed trailing spaces
* mtree: docs - removed trailing spaces
* nat_traversal: docs - removed trailing spaces
* nathelper: docs - removed trailing spaces
* ndb_cassandra: docs - removed trailing spaces
* ndb_mongodb: docs - removed trailing spaces
* ndb_redis: docs - removed trailing spaces
* nosip: docs - removed trailing spaces
* nsq: docs - removed trailing spaces
* osp: docs - removed trailing spaces
* outbound: docs - removed trailing spaces
* p_usrloc: docs - removed trailing spaces
* path: docs - removed trailing spaces
* pdb: docs - removed trailing spaces
* pdt: docs - removed trailing spaces
* peering: docs - removed trailing spaces
* permissions: docs - removed trailing spaces
* pike: docs - removed trailing spaces
* pipelimit: docs - removed trailing spaces
* prefix_route: docs - removed trailing spaces
* presence: docs - removed trailing spaces
* presence_conference: docs - removed trailing spaces
* presence_dialoginfo: docs - removed trailing spaces
* presence_mwi: docs - removed trailing spaces
* presence_profile: docs - removed trailing spaces
* presence_reginfo: docs - removed trailing spaces
* presence_xml: docs - removed trailing spaces
* print: docs - removed trailing spaces
* print_lib: docs - removed trailing spaces
* pua: docs - removed trailing spaces
* pua_bla: docs - removed trailing spaces
* pua_dialoginfo: docs - removed trailing spaces
* pua_json: docs - removed trailing spaces
* pua_reginfo: docs - removed trailing spaces
* pua_usrloc: docs - removed trailing spaces
* pua_xmpp: docs - removed trailing spaces
* pv: docs - removed trailing spaces
* pv_headers: docs - removed trailing spaces
* qos: docs - removed trailing spaces
* rabbitmq: docs - removed trailing spaces
* ratelimit: docs - removed trailing spaces
* regex: docs - removed trailing spaces
* registrar: docs - removed trailing spaces
* rls: docs - removed trailing spaces
* rr: docs - removed trailing spaces
* rtimer: docs - removed trailing spaces
* rtjson: docs - removed trailing spaces
* rtp_media_server: docs - removed trailing spaces
* rtpengine: docs - removed trailing spaces
* rtpproxy: docs - removed trailing spaces
* sanity: docs - removed trailing spaces
* sctp: docs - removed trailing spaces
* sdpops: docs - removed trailing spaces
* seas: docs - removed trailing spaces
* secfilter: docs - removed trailing spaces
* sipcapture: docs - removed trailing spaces
* sipt: docs - removed trailing spaces
* siptrace: docs - removed trailing spaces
* siputils: docs - removed trailing spaces
* sl: docs - removed trailing spaces
* sms: docs - removed trailing spaces
* smsops: docs - removed trailing spaces
* snmpstats: docs - removed trailing spaces
* sqlops: docs - removed trailing spaces
* sst: docs - removed trailing spaces
* statistics: docs - removed trailing spaces
* statsd: docs - removed trailing spaces
* stirshaken: docs - removed trailing spaces
* stun: docs - removed trailing spaces
* tcpops: docs - removed trailing spaces
* textops: docs - removed trailing spaces
* textopsx: docs - removed trailing spaces
* tls: docs - removed trailing spaces
* tm: docs - removed trailing spaces
* tmrec: docs - removed trailing spaces
* tmx: docs - removed trailing spaces
* topos: docs - removed trailing spaces
* tsilo: docs - removed trailing spaces
* uac: docs - removed trailing spaces
* uac_redirect: docs - removed trailing spaces
* uid_auth_db: docs - removed trailing spaces
* uid_avp_db: docs - removed trailing spaces
* uid_domain: docs - removed trailing spaces
* uid_gflags: docs - removed trailing spaces
* uid_uri_db: docs - removed trailing spaces
* uri_db: docs - removed trailing spaces
* userblocklist: docs - removed trailing spaces
* usrloc: docs - removed trailing spaces
* utils: docs - removed trailing spaces
* uuid: docs - removed trailing spaces
* websocket: docs - removed trailing spaces
* xcap_client: docs - removed trailing spaces
* xcap_server: docs - removed trailing spaces
* xhttp: docs - removed trailing spaces
* xhttp_pi: docs - removed trailing spaces
* xhttp_prom: docs - removed trailing spaces
* xhttp_rpc: docs - removed trailing spaces
* xlog: docs - removed trailing spaces
* xmlops: docs - removed trailing spaces
* xmpp: docs - removed trailing spaces
* xprint: docs - removed trailing spaces
* pua_dialoginfo: safety check for request pointer
* core: fix compilation for older kernels
* core: fix indentation on tcp_main.c
* core: copy the value between quotes for #!defexps
* pkg: version set to 5.7.3 for rpms and alpine specs
* pkg: deb specs updated for v5.7.3
* Makefile.defs: version set to 5.7.3
* ChangeLog: content updated for v5.7.3
* pkg/docker: set branch 5.7 and refresh [skip ci]
* github: refresh alpine workflow [skip ci]
* core: resolve - cast after pointer operations for RES_AR
* core/mem: tlsf - cast to char* for pointer operations
* core: resolve - variables initialisation
* app_python3: reformat exports structures
* app_python3: use module name prefix for exports structure
* app_python3s: reformat exports structures
* app_python3s: use module name prefix for exports structure
* app_lua: reformat exports structures
* app_lua: use module name prefix for exports structure
* app_jsdt: use module name prefix for exports structure
* app_ruby: use module name prefix for exports structure
* textops: do not print module name in log messages
* avpops: do not print module name in log messages
* avp: do not print module name in log messages
* dialog: do not print module name in log messages
* dialog: use literal module name for stats group
* http_async_client: use literal module name for stats group
* imc: use literal module name for stats group
* ims_auth: use literal module name for stats group
* ims_icscf: use literal module name for stats group
* ims_registrar_scscf: use literal module name for stats group
* ims_usrloc_pcscf: use literal module name for stats group
* msilo: use literal module name for stats group
* nat_traversal: use literal module name for stats group
* p_usrloc: use literal module name for stats group
* registrar: use literal module name for stats group
* sipcapture: use literal module name for stats group
* siptrace: use literal module name for stats group
* sst: use literal module name for stats group
* tmx: use literal module name for stats group
* tsilo: use literal module name for stats group
* usrloc: use literal module name for stats group
* websocket: use literal module name for stats group
* Makefile.groups: tlsa in packaging group ktls if KTLS_INCLUDE_TLSA=yes
* pkg/kamailio/deb: include tlsa in tls package [skip ci]
* Makefile.groups: fix ktls when KTLS_INCLUDE_TLSA is not set
* tls: rework init mode 1 to set PTHREAD_PROCESS_SHARED
* tls: init early the local lock for memory
* core: parse privacy recompute lenght of rest to parse
* pv: remove extra len increment for some uri transformations
* pkg/kamailio/deb: override lintian error on stretch [skip ci]
* tls: OpenSSL 3.x thread-local, init libssl in thread or PROC_SIPINIT
* tls: fix compilation with OpenSSL <= 1.1.1
* tls: OpenSSL 1.1.1 thread-local, init libssl in thread
* tls: thread-local, revert 1a9b0b6361 as double-layer locking is redundant
* tls: OpenSSL 3.x/1.1.1 thread-local, clean-up dead code and preprocessor blocks
* outbound: OpenSSL 3.x thread-local, init libssl in thread
* outbound: OpenSSL 1.1.1 thread-local, init libssl in thread
* outbound: build, fix missing argument name
* tls: historical code comment on repeating SSL_CTX per worker
* tls: remove thread-enablement on EVP_RAND_CTX
* outbound: update to OpenSSL 3 API
* tls_wolfssl: update to v5.6.6-stable
* tls_wolfssl: mask outer make DESTDIR=XX if building internal submodule
* dialog: don't send the BYE if dialog is in deleted state (#3714)
* core: set proto on fixing forward actions
* dialog: prevent duplicate of leg1 attributes in json for dmq
* uac: fix socket length settings
* core: xavp - info long when skipping serializing a field
* dialog: check first the size
* tm: check get_t() result for consistency
* registrar: check returned branch pointer
* core: check if conversion could not be done
* app_python3: check allocated pointer
* core: srjson - init vars and check scanned values
* pv: typo in transformation log message
* pv: removed unnecessary condition
* tm: make lookup event_route[tm:local-response] only once
* tmx: rework cleaning up on init failure
* statsd: use bool type for local variable to match return of function
* core: fixed haproxy protocol parser
* dialog: fixed saving dialogs on shutdown that are already loaded at startup when using db_mode 3
* htable: read rpc number value as long
* http_async_client: exit mod_init if tm is not loaded
* core: keep listen socket even if advertise address does not resolve
* tls: set parameter name for tls_h_mod_randctx()
* tls_wolfssl: clean-up—using wolfSSL native naming for functions / structs
* pkg: version set to 5.7.4 for rpms and alpine specs
* pkg: deb specs updated for v5.7.4
* Makefile.defs: version set to 5.7.4
* ChangeLog: content updated for v5.7.4
* xlog: add kemi xlog_facility function
* tls_wolfssl: clean-up OpenSSL compatibility
* tls_wolfssl: use shared WOLFSSL_CTX
* tls_wolfssl: refactor custom BIO
* tls_wolfssl: clean-up; remove OpenSSL-isms
* tls_wolfssl: clean-up; continue to remove OpenSSL-isms
* tls_wolfssl: allow building with debian libwolfssl35
* tls_wolfssl: fix ring buffer write
* tls_wolfssl: clang-format
* tls_wolfssl: fix possible uninitialised variable
* tls_wolfssl: un-break jammy using libwolfssl32
* core: backport OpenSSL thread-local fixes
* db_mysql: backport OpenSSL thread-local fixes
* db_postgres: backport OpenSSL thread-local fixes
* db_unixodbc: backport OpenSSL thread-local fixes
-- File Changes --
M .github/workflows/alpine.yml (46)
M .github/workflows/main.yml (4)
M .gitmodules (1)
M ChangeLog (18373)
M README (2)
M etc/kamailio.cfg (8)
M etc/sip-router.cfg (16)
M misc/external/wolfssl/wolfssl (2)
M misc/fuzz/fuzz_parse_msg.c (73)
M misc/fuzz/fuzz_uri.c (18)
M misc/tools/pike_top/pike_top.c (370)
M misc/tools/protoshoot/protoshoot.c (240)
A misc/tools/route_graph/README (16)
M misc/tools/route_graph/route_graph.py (345)
M pkg/docker (2)
M pkg/kamailio/alpine/APKBUILD (6)
M pkg/kamailio/deb/bionic/changelog (36)
M pkg/kamailio/deb/bionic/kamailio-tls-modules.lintian-overrides (2)
M pkg/kamailio/deb/bionic/rules (4)
M pkg/kamailio/deb/bookworm/changelog (36)
M pkg/kamailio/deb/bookworm/kamailio-tls-modules.lintian-overrides (2)
M pkg/kamailio/deb/bookworm/rules (4)
M pkg/kamailio/deb/bullseye/changelog (36)
M pkg/kamailio/deb/bullseye/kamailio-tls-modules.lintian-overrides (2)
M pkg/kamailio/deb/bullseye/rules (4)
M pkg/kamailio/deb/buster/changelog (36)
M pkg/kamailio/deb/buster/kamailio-tls-modules.lintian-overrides (2)
M pkg/kamailio/deb/buster/rules (4)
M pkg/kamailio/deb/debian/backports/xenial (3)
M pkg/kamailio/deb/debian/changelog (36)
M pkg/kamailio/deb/debian/kamailio-tls-modules.lintian-overrides (2)
M pkg/kamailio/deb/debian/rules (4)
M pkg/kamailio/deb/focal/changelog (36)
M pkg/kamailio/deb/focal/kamailio-tls-modules.lintian-overrides (2)
M pkg/kamailio/deb/focal/rules (4)
M pkg/kamailio/deb/jammy/changelog (36)
M pkg/kamailio/deb/jammy/kamailio-tls-modules.lintian-overrides (2)
M pkg/kamailio/deb/jammy/rules (4)
M pkg/kamailio/deb/jessie/changelog (36)
M pkg/kamailio/deb/jessie/kamailio-tls-modules.lintian-overrides (2)
M pkg/kamailio/deb/jessie/rules (4)
M pkg/kamailio/deb/precise/changelog (36)
M pkg/kamailio/deb/precise/kamailio-tls-modules.lintian-overrides (2)
M pkg/kamailio/deb/precise/rules (4)
M pkg/kamailio/deb/sid/changelog (36)
M pkg/kamailio/deb/sid/kamailio-tls-modules.lintian-overrides (2)
M pkg/kamailio/deb/sid/rules (4)
M pkg/kamailio/deb/stretch/changelog (36)
M pkg/kamailio/deb/stretch/kamailio-tls-modules.lintian-overrides (2)
M pkg/kamailio/deb/stretch/rules (4)
M pkg/kamailio/deb/trusty/changelog (36)
M pkg/kamailio/deb/trusty/kamailio-tls-modules.lintian-overrides (2)
M pkg/kamailio/deb/trusty/rules (4)
M pkg/kamailio/deb/wheezy/changelog (36)
M pkg/kamailio/deb/wheezy/kamailio-tls-modules.lintian-overrides (2)
M pkg/kamailio/deb/wheezy/rules (4)
M pkg/kamailio/deb/xenial/changelog (36)
M pkg/kamailio/deb/xenial/kamailio-tls-modules.lintian-overrides (2)
M pkg/kamailio/deb/xenial/rules (4)
D pkg/kamailio/obs/README (16)
A pkg/kamailio/obs/README.md (35)
A pkg/kamailio/obs/kamailio-8-x86_64.cfg (19)
A pkg/kamailio/obs/kamailio-9-x86_64.cfg (19)
M pkg/kamailio/obs/kamailio.spec (4)
A pkg/kamailio/scripts/create-src-rpm.sh (37)
A pkg/kamailio/scripts/git-archive-all.sh (24)
M src/Makefile (8)
M src/Makefile.defs (6)
M src/Makefile.groups (14)
M src/core/action.c (1737)
M src/core/action.h (21)
M src/core/async_task.c (183)
M src/core/async_task.h (6)
M src/core/atomic/atomic_alpha.h (381)
M src/core/atomic/atomic_arm.h (335)
M src/core/atomic/atomic_common.h (29)
M src/core/atomic/atomic_mips2.h (388)
M src/core/atomic/atomic_native.h (10)
M src/core/atomic/atomic_ppc.h (308)
M src/core/atomic/atomic_sparc.h (61)
M src/core/atomic/atomic_sparc64.h (336)
M src/core/atomic/atomic_unknown.h (273)
M src/core/atomic/atomic_x86.h (390)
M src/core/atomic_ops.c (49)
M src/core/atomic_ops.h (44)
M src/core/atomic_ops_init.h (2)
M src/core/basex.c (551)
M src/core/basex.h (713)
M src/core/bit_count.c (2)
M src/core/bit_count.h (8)
M src/core/bit_scan.c (16)
M src/core/bit_scan.h (263)
M src/core/bit_test.h (57)
M src/core/cfg.lex (10)
M src/core/cfg.y (19)
M src/core/cfg/cfg.c (197)
M src/core/cfg/cfg.h (74)
M src/core/cfg/cfg_ctx.c (1116)
M src/core/cfg/cfg_ctx.h (112)
M src/core/cfg/cfg_script.c (288)
M src/core/cfg/cfg_script.h (32)
M src/core/cfg/cfg_select.c (202)
M src/core/cfg/cfg_select.h (10)
M src/core/cfg/cfg_struct.c (674)
M src/core/cfg/cfg_struct.h (318)
M src/core/cfg_core.c (457)
M src/core/cfg_core.h (53)
M src/core/cfg_parser.c (0)
M src/core/cfg_parser.h (0)
M src/core/char_msg_val.h (0)
M src/core/clist.h (0)
M src/core/comp_defs.h (0)
M src/core/compiler_opt.h (0)
M src/core/config.h (0)
M src/core/core_cmd.c (0)
M src/core/core_cmd.h (0)
M src/core/core_stats.h (0)
M src/core/counters.c (0)
M src/core/counters.h (0)
M src/core/crc.c (0)
M src/core/crc.h (0)
M src/core/crypto/md5.c (0)
M src/core/crypto/md5.h (0)
M src/core/crypto/md5utils.c (0)
M src/core/crypto/md5utils.h (0)
M src/core/crypto/rijndael.c (0)
M src/core/crypto/rijndael.h (0)
M src/core/crypto/sha256.c (0)
M src/core/crypto/sha256.h (0)
M src/core/crypto/shautils.c (0)
M src/core/daemonize.c (0)
M src/core/daemonize.h (0)
M src/core/data_lump.c (0)
M src/core/data_lump.h (0)
M src/core/data_lump_rpl.c (0)
M src/core/data_lump_rpl.h (0)
M src/core/dns_cache.c (0)
M src/core/dns_cache.h (0)
M src/core/dns_func.c (0)
M src/core/dns_func.h (0)
M src/core/dns_wrappers.h (0)
M src/core/dprint.c (0)
M src/core/dprint.h (0)
M src/core/dset.c (0)
M src/core/dset.h (0)
M src/core/dst_blocklist.c (0)
M src/core/dst_blocklist.h (0)
M src/core/endianness.c (0)
M src/core/endianness.h (0)
M src/core/error.c (0)
M src/core/error.h (0)
M src/core/events.c (0)
M src/core/events.h (0)
M src/core/fastlock.h (0)
M src/core/fix_lumps.h (0)
M src/core/flags.c (0)
M src/core/flags.h (0)
M src/core/fmsg.c (0)
M src/core/fmsg.h (0)
M src/core/forward.c (0)
M src/core/forward.h (0)
M src/core/futexlock.h (0)
M src/core/globals.h (0)
M src/core/hash_func.c (0)
M src/core/hash_func.h (0)
M src/core/hashes.h (0)
M src/core/id.c (0)
M src/core/id.h (0)
M src/core/io_wait.c (0)
M src/core/io_wait.h (0)
M src/core/ip_addr.c (0)
M src/core/ip_addr.h (0)
M src/core/kemi.c (0)
M src/core/kemi.h (0)
M src/core/kemiexec.c (0)
M src/core/list.h (0)
M src/core/local_timer.c (0)
M src/core/local_timer.h (0)
M src/core/lock_alloc.h (0)
M src/core/lock_ops.c (0)
M src/core/lock_ops.h (0)
M src/core/lock_ops_init.h (0)
M src/core/locking.c (0)
M src/core/locking.h (0)
M src/core/lump_struct.h (0)
M src/core/lvalue.c (0)
M src/core/lvalue.h (0)
M src/core/mem/dl_malloc.c (0)
M src/core/mem/dl_malloc.h (0)
M src/core/mem/f_malloc.c (0)
M src/core/mem/f_malloc.h (0)
M src/core/mem/ll_malloc.c (0)
M src/core/mem/ll_malloc.h (0)
M src/core/mem/mem.h (0)
M src/core/mem/memapi.h (0)
M src/core/mem/memdbg.h (0)
M src/core/mem/meminfo.h (0)
M src/core/mem/memtest.c (0)
M src/core/mem/pkg.c (0)
M src/core/mem/pkg.h (0)
M src/core/mem/q_malloc.c (0)
M src/core/mem/q_malloc.h (0)
M src/core/mem/sf_malloc.c (0)
M src/core/mem/sf_malloc.h (0)
M src/core/mem/shm.c (0)
M src/core/mem/shm.h (0)
M src/core/mem/shm_mem.h (0)
M src/core/mem/src_loc.h (0)
M src/core/mem/tlsf_malloc.c (0)
M src/core/mem/tlsf_malloc.h (0)
M src/core/mem/tlsf_malloc_bits.h (0)
M src/core/mod_fix.c (0)
M src/core/mod_fix.h (0)
M src/core/modparam.c (0)
M src/core/modparam.h (0)
M src/core/msg_translator.c (0)
M src/core/msg_translator.h (0)
M src/core/name_alias.h (0)
M src/core/nonsip_hooks.c (0)
M src/core/nonsip_hooks.h (0)
M src/core/onsend.c (0)
M src/core/onsend.h (0)
M src/core/parser/contact/contact.c (0)
M src/core/parser/contact/contact.h (0)
M src/core/parser/contact/parse_contact.c (0)
M src/core/parser/contact/parse_contact.h (0)
M src/core/parser/digest/digest.c (0)
M src/core/parser/digest/digest.h (0)
M src/core/parser/digest/digest_keys.h (0)
M src/core/parser/digest/digest_parser.c (0)
M src/core/parser/digest/digest_parser.h (0)
M src/core/parser/digest/param_parser.c (0)
M src/core/parser/digest/param_parser.h (0)
M src/core/parser/hf.c (0)
M src/core/parser/hf.h (0)
M src/core/parser/keys.h (0)
M src/core/parser/msg_parser.c (0)
M src/core/parser/msg_parser.h (0)
M src/core/parser/parse_addr_spec.c (0)
M src/core/parser/parse_addr_spec.h (0)
M src/core/parser/parse_allow.c (0)
M src/core/parser/parse_allow.h (0)
M src/core/parser/parse_body.c (0)
M src/core/parser/parse_body.h (0)
M src/core/parser/parse_content.c (0)
M src/core/parser/parse_content.h (0)
M src/core/parser/parse_cseq.c (0)
M src/core/parser/parse_cseq.h (0)
M src/core/parser/parse_date.c (0)
M src/core/parser/parse_date.h (0)
M src/core/parser/parse_def.h (0)
M src/core/parser/parse_disposition.c (0)
M src/core/parser/parse_disposition.h (0)
M src/core/parser/parse_diversion.c (0)
M src/core/parser/parse_diversion.h (0)
M src/core/parser/parse_event.c (0)
M src/core/parser/parse_event.h (0)
M src/core/parser/parse_expires.c (0)
M src/core/parser/parse_expires.h (0)
M src/core/parser/parse_fline.c (0)
M src/core/parser/parse_fline.h (0)
M src/core/parser/parse_from.h (0)
M src/core/parser/parse_hname2.c (0)
M src/core/parser/parse_hname2.h (0)
M src/core/parser/parse_identity.c (0)
M src/core/parser/parse_identity.h (0)
M src/core/parser/parse_identityinfo.c (0)
M src/core/parser/parse_identityinfo.h (0)
M src/core/parser/parse_methods.c (0)
M src/core/parser/parse_methods.h (0)
M src/core/parser/parse_nameaddr.c (0)
M src/core/parser/parse_nameaddr.h (0)
M src/core/parser/parse_option_tags.c (0)
M src/core/parser/parse_option_tags.h (0)
M src/core/parser/parse_param.c (0)
M src/core/parser/parse_param.h (0)
M src/core/parser/parse_ppi_pai.c (0)
M src/core/parser/parse_ppi_pai.h (0)
M src/core/parser/parse_privacy.c (0)
M src/core/parser/parse_privacy.h (0)
M src/core/parser/parse_refer_to.c (0)
M src/core/parser/parse_refer_to.h (0)
M src/core/parser/parse_require.c (0)
M src/core/parser/parse_require.h (0)
M src/core/parser/parse_retry_after.c (0)
M src/core/parser/parse_retry_after.h (0)
M src/core/parser/parse_rpid.c (0)
M src/core/parser/parse_rpid.h (0)
M src/core/parser/parse_rr.c (0)
M src/core/parser/parse_rr.h (0)
M src/core/parser/parse_sipifmatch.c (0)
M src/core/parser/parse_sipifmatch.h (0)
M src/core/parser/parse_subscription_state.c (0)
M src/core/parser/parse_subscription_state.h (0)
M src/core/parser/parse_supported.c (0)
M src/core/parser/parse_supported.h (0)
M src/core/parser/parse_to.c (0)
M src/core/parser/parse_to.h (0)
M src/core/parser/parse_uri.c (0)
M src/core/parser/parse_uri.h (0)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3739.patchhttps://github.com/kamailio/kamailio/pull/3739.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3739
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3739(a)github.com>
[View Less]
- [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 …
[View More]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
Introduce utility functions that run module functions in a thread —- primary use case is to init libssl in a thread. Also to avoid a lot of duplicate pthread_XXXX code.
Does not affect core as it is just a header file, however it could be put into core or a utility object.
This infra is applied to a few modules to see the code savings.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3736
-- Commit Summary --
* core: add infrastructure to run functions in threads
* db_unixodbc: use core/rthreads.h
* db_mysql: use core/rthreads.h
* db_postgres: use core/rthreads.h
* outbound: use core/rthreads.h
-- File Changes --
A src/core/rthreads.h (77)
M src/modules/db_mysql/km_dbase.c (10)
M src/modules/db_postgres/km_dbase.c (32)
M src/modules/db_unixodbc/dbase.c (11)
M src/modules/outbound/outbound_mod.c (13)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3736.patchhttps://github.com/kamailio/kamailio/pull/3736.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3736
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3736(a)github.com>
[View Less]
### Description
Applies to `db_mysql` built with mariadb-connector-c; TLS is not working
Option 1: configure mariadb server to use TLS (optional)
Option 2: configure mariadb server to use TLS (mandatory)
### Troubleshooting
1. wireshark inspect the pcap dump of traffic to :3306 and look for ClientHello
2. gdb main kamailio process and set breakpoint at `SSL_new`
#### Reproduction
1. Option 1: server advertises SSL, but db_mysql will always choose plain
3. Option 2: server advertises SSL(and …
[View More]requires SSL), connection will fail
### Additional Information
#### Kamailio version
* master
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3735
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3735(a)github.com>
[View Less]
Module: kamailio
Branch: master
Commit: dad7c857eaab613deed27ab687ddd0b1fdf8001b
URL: https://github.com/kamailio/kamailio/commit/dad7c857eaab613deed27ab687ddd0b…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2024-01-30T14:32:10+01:00
modules: readme files regenerated - db_mysql ... [skip ci]
---
Modified: src/modules/db_mysql/README
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]dad7c857eaab613deed27ab687ddd0b…
Patch: https://github.com/kamailio/kamailio/commit/dad7c857eaab613deed27ab687ddd0b…
---
diff --git a/src/modules/db_mysql/README b/src/modules/db_mysql/README
index 8d9f526cbe1..8e135cdcbf2 100644
--- a/src/modules/db_mysql/README
+++ b/src/modules/db_mysql/README
@@ -94,7 +94,9 @@ Chapter 1. Admin Guide
The following libraries or applications must be installed before
running Kamailio with this module loaded:
* mysql - the development libraries for the MySQL database. In some
- Linux distributions named "libmysqlclient-dev".
+ Linux distributions named "libmysqlclient-dev". MariaDB - the
+ development libraries for the MariaDB database. In some Linux
+ distributions named "libmariadbclient-dev".
3. Parameters
@@ -199,8 +201,9 @@ modparam("db_mysql", "update_affected_found", 1)
SSL_MODE_DISABLED, any other value is passed to the mysql_options(),
not checking if it is defined.
- Note: this option is supported only by libmysqlclient, not by
- libmariadbclient.
+ MariaDB client configuration uses the following values: 0, 1 use plain,
+ 2/3/4 for MYSQL_OPT_SSL_ENFORCE, 5 for MYSQL_OPT_SSL_VERIFY_SERVER_CERT
+ (see MariaDB Connector/C documentation) Other values are ignored.
Default value is 0 (0 - off).
[View Less]
#### 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
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [X] New …
[View More]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
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
When db_mysql is built with mariadb-connector-c it does not use TLS and fails if the server requires TLS. It seems to be related to the fact that the MYSQL object needs to have a minimal non-NULL configuration (unlike MySQL Connector/C).
This is a minimal setting to allow TLS. A more full-featured solution would be to enable db_mysql to read from an external configuration file.
@linuxmaniac, kindly take a look
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3734
-- Commit Summary --
* db_mysql: enable TLS when building with mariadb-connector-c
-- File Changes --
M src/modules/db_mysql/km_my_con.c (9)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3734.patchhttps://github.com/kamailio/kamailio/pull/3734.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3734
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3734(a)github.com>
[View Less]
Module: kamailio
Branch: master
Commit: 2bcc32a14e63d895077071715b0321fbdcdb8a33
URL: https://github.com/kamailio/kamailio/commit/2bcc32a14e63d895077071715b0321f…
Author: S-P Chan <shihping.chan(a)gmail.com>
Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Date: 2024-01-30T14:28:26+01:00
db_mysql: update docs for MariaDB Connector/C builds
---
Modified: src/modules/db_mysql/doc/db_mysql_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]2bcc32a14e63d895077071715b0321f…
Patch: https://github.com/kamailio/kamailio/commit/2bcc32a14e63d895077071715b0321f…
---
diff --git a/src/modules/db_mysql/doc/db_mysql_admin.xml b/src/modules/db_mysql/doc/db_mysql_admin.xml
index 51c9b5b728d..f1ff53df0ed 100644
--- a/src/modules/db_mysql/doc/db_mysql_admin.xml
+++ b/src/modules/db_mysql/doc/db_mysql_admin.xml
@@ -46,6 +46,7 @@
<listitem>
<para>
<emphasis>mysql</emphasis> - the development libraries for the MySQL database. In some Linux distributions named "libmysqlclient-dev".
+ <emphasis>MariaDB</emphasis> - the development libraries for the MariaDB database. In some Linux distributions named "libmariadbclient-dev".
</para>
</listitem>
</itemizedlist>
@@ -198,7 +199,10 @@ modparam("db_mysql", "update_affected_found", 1)
defined.
</para>
<para>
- Note: this option is supported only by libmysqlclient, not by libmariadbclient.
+ MariaDB client configuration uses the following values: 0, 1 use plain, 2/3/4 for MYSQL_OPT_SSL_ENFORCE,
+ 5 for MYSQL_OPT_SSL_VERIFY_SERVER_CERT (see MariaDB Connector/C documentation)
+
+ Other values are ignored.
</para>
<para>
<emphasis>
@@ -298,4 +302,3 @@ default-character-set = utf8
</para>
</section>
</chapter>
-
[View Less]
Hello dear developers!
I'm developing a module that can have several sets of similar connections.
I see that some modules allow specifying a sequence of settings in one
parameter through the symbol ";", as sample:
modparam("htable", "htable",
"customer=>size=8;dbtable=customer;cols='dids,description';coldelim=';'")
or my example:
modparam("module", "module",
"connection=>alice;id=aliceid;password=alicepwd;timeout=60;param=123")
modparam("module", "module",
"connection=>bob;id=bobid;…
[View More]password=bobpwd;timeout=90;param=456")
I don't find it user friendly.
Can I offer users blocks with settings that should start with some
parameter, for example "connection", as in the example:
modparam("module", "connection", "alice") # first block of settings
modparam("module", "id", "aliceid")
modparam("module", "password", "alicepwd")
modparam("module", "timeout", 60)
modparam("module", "param", 123)
modparam("module", "connection", "bob") # second block of settings
modparam("module", "id", "bobid")
modparam("module", "password", "bobpwd")
modparam("module", "timeout", 90)
modparam("module", "param", 456)
modparam("module", "connection", "john") # third block of settings
...
If you think that this is not compatible with the kamailio configuration
ideology, I will give up my idea :)
[View Less]
Bumps [ammaraskar/gcc-problem-matcher](https://github.com/ammaraskar/gcc-problem-m… from 0.2.0 to 0.3.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/ammaraskar/gcc-problem-matcher/releases"… releases</a>.</em></p>
<blockquote>
<h2>Update for node16 deprecation</h2>
<…
[View More]p>Github has deprecated node16 actions, this update fixes the deprecation warning emitted. See <a href="https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/">https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/ammaraskar/gcc-problem-matcher/commit/0f9c86f… Update to use node20, fixes <a href="https://redirect.github.com/ammaraskar/gcc-problem-matcher/issue…
<li>See full diff in <a href="https://github.com/ammaraskar/gcc-problem-matcher/compare/0.2.0.… view</a></li>
</ul>
</details>
<br />
[
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3733
-- Commit Summary --
* github: [skip ci]: bump ammaraskar/gcc-problem-matcher
-- File Changes --
M .github/workflows/main.yml (2)
M .github/workflows/pull_request.yml (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3733.patchhttps://github.com/kamailio/kamailio/pull/3733.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3733
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3733(a)github.com>
[View Less]
### Description
Kamailio fails to start after recent changes were made to improve support for OpenSSL 3.X. The failure occurs for both OpenSSL 3.X and OpenSSL 1.1.X, and are the same as failures I had been seeing on previous Kamailio versions when using OpenSSL 3.X. These errors were not occurring for OpenSSL 1.1.X prior to commits on Jan 4, 2024.
My configuration is using the unixodbc module to communicate with a Microsoft SQL Server database. Furthermore, the dispatcher module is configured …
[View More]to use the database.
With this configuration, Kamailio always fails at startup. It may log a "freeing already free pointer bug" or sometimes indicates pointer corruption. In either case, it fails to connect to the database.
#### Reproduction
Start Kamailio with configuration files similar to the following. For the log file shown below, Kamailio was started with "kamailio -dd -E --atexit=no"
[kamailio.txt](https://github.com/kamailio/kamailio/files/14068346/kamailio.…
[tls.txt](https://github.com/kamailio/kamailio/files/14068347/tls.txt)
#### Log Messages
[kamailio.log](https://github.com/kamailio/kamailio/files/14068278/kamailio.…
#### SIP Traffic
None. Problem occurs during initialization.
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
version: kamailio 5.8.0-dev2 (x86_64/linux) 4db5d7-dirty
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
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_SEND_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: 4db5d7 -dirty
compiled on 17:44:29 Jan 26 2024 with gcc 9.4.0
* **Operating System**:
Distributor ID: Ubuntu
Description: Ubuntu 20.04.6 LTS
Release: 20.04
Codename: focal
Kernel: 5.4.0-170-generic
(Similar behavior is seen on Ubuntu 22.04 using OpenSSL 3.X.)
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3727
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3727(a)github.com>
[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:
- [X] PR should be backported to stable branches
- [ ] Tested changes locally
- [X] Related to issue #3727
#### Description
PostgreSQL may be configured to use SSL: init in a thread
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3730
-- Commit Summary --
* db_postgres: init libssl in a thread
-- File Changes --
M src/modules/db_postgres/km_dbase.c (17)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3730.patchhttps://github.com/kamailio/kamailio/pull/3730.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3730
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3730(a)github.com>
[View Less]
#### 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 …
[View More](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
- [ ] Tested changes locally
- [X] Related to issue #3727
#### Description
`mod_init()` in configuration can initialise libssl in rank 0(thread#1). User report is with regard to using `db_unixodbc`; however the same errors can be reproduced with `db_mysql` replacing `db_unixodbc`.
This PR inits libssl in a separate thread.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3729
-- Commit Summary --
* db_mysql: init libssl in a thread
-- File Changes --
M src/modules/db_mysql/km_dbase.c (17)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3729.patchhttps://github.com/kamailio/kamailio/pull/3729.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3729
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3729(a)github.com>
[View Less]
- [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 …
[View More]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
- [X ] Related to issue #3727
#### Description
The bug report kamailio configuration is using dispatcher + unixodbc and the database driver (tested with MariaDB ODBC, user reports with MS SQL Server(not tested)) inits libssl in rank 0(thread 1).
This PR will init in a thread.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3728
-- Commit Summary --
* db_unixodbc: init libssl in a thread
-- File Changes --
M src/modules/db_unixodbc/dbase.c (17)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3728.patchhttps://github.com/kamailio/kamailio/pull/3728.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3728
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3728(a)github.com>
[View Less]
Hi everybody,
I normally use MongoDB as DB engine in my projects and I would like to get
all MongoDB advantages when working with Kamailio. For this reason, I need
to deal with arrays of information inside a document (for example, an array
of contacts inside a document).
And now the question: is it possible to insert, update and search info in a
MongoDB document by using arrays via srdb1 lib? If yes, how? And if not,
are you thinking about implementing it in the future?
Thank you very much …
[View More]for your time.
Regards,
Mario
[View Less]