#### 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]