### Description
Issues building `PYTHON` module on Alpine Linux due to [sunsetting of Python2](https://www.python.org/doc/sunset-python-2/). The `python2` package (apk) has been removed from the current Alpine linux. The APKBUILD file in the current Kamailio branches includes build settings for installing the Python (python2) module. While I'm guessing it's possible to build python2 in the current Alpine container it was a conscious decision to no longer have a package for it. Given this, what is the opinion about not building this by default within the APKBUILD file?
### Troubleshooting
Running `abuild -r` fails due to lack of python2 libraries.
#### Reproduction
Running `abuild -r` fails due to lack of python2 libraries.
#### Debugging Data
N/A
#### Log Messages
N/A
#### SIP Traffic
N/A
### Possible Solutions
In `APKBUILD` remove references to `python2` and `python` (but not `python3`). I'll submit a pull request to do this.
### Additional Information
Kamailio 5.7
* **Operating System**:
Alpine Linux latest
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3257
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3257(a)github.com>
#### Pre-Submission Checklist
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [x] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
- [x] PR should be backported to stable branches
- [x] Tested changes locally
- [x] Related to issue #3257
#### Description
Do not build python2 module with default APKBUILD file due to python2 being sunsetted within Alpine Linux (there is no python2 APK).
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3258
-- Commit Summary --
* APKBUILD: remove python2 references
-- File Changes --
M pkg/kamailio/alpine/APKBUILD (12)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3258.patchhttps://github.com/kamailio/kamailio/pull/3258.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3258
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3258(a)github.com>
In order to support a redundant PCSCF configuration - i.e. a logical PCSCF consists of 2 physical nodes (node1 and node2) some enhancements were introduced for handling of contacts. Redundancy means that SIP messages for a client are normally handled by node1 but in case node1 is not reachable SIP messages are redirected to node2. Of course the DB_ONLY mode must work also for single PCSCF node configuration. Important aspects of this implementation are database integrity - i.e. avoid invalid table entries (for example data which are expired long time ago or have invalid states) - and keeping PCSCF cache in sync with database tables. A wrapper was built for method get_pcontact which tries to find the pcontact in cache and if search is not successful tries to download and insert from db location table - also some effort is added here to find the pcontact if it exists in cache. The contact expiry handler was modified to sync contact expiry in cache with db location entry and in case of real contact expiry sends PUBLISH to SCSCF to let NOTIFY finally delete the contact. An audit for older expired pcontacts was introduced which cares for getting rid of these contacts.
So db queries for this db mode are only supported for Mysql.
Some code was introduced to help registering callbacks for contacts which are inserted into cache when being downloaded from database - for example ims_qos callback as at the time of insertion the message that triggered the original callback registering is long gone.
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [ ] 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 in local branch based on 5.5.4
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- see top of this section -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3279
-- Commit Summary --
* ims_usrloc_pcscf: implementation of db_mode DB_ONLY (value 3)
-- File Changes --
M src/modules/ims_usrloc_pcscf/README (11)
M src/modules/ims_usrloc_pcscf/ims_usrloc_pcscf_mod.c (22)
M src/modules/ims_usrloc_pcscf/pcontact.c (85)
M src/modules/ims_usrloc_pcscf/udomain.c (511)
M src/modules/ims_usrloc_pcscf/udomain.h (5)
M src/modules/ims_usrloc_pcscf/ul_callback.c (52)
M src/modules/ims_usrloc_pcscf/ul_callback.h (10)
M src/modules/ims_usrloc_pcscf/ul_rpc.c (156)
M src/modules/ims_usrloc_pcscf/usrloc.c (7)
M src/modules/ims_usrloc_pcscf/usrloc.h (12)
M src/modules/ims_usrloc_pcscf/usrloc_db.c (50)
M src/modules/ims_usrloc_pcscf/usrloc_db.h (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3279.patchhttps://github.com/kamailio/kamailio/pull/3279.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3279
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3279(a)github.com>
We need to make commands in rtpengine module asynchronous just like it is in evapi module which improves efficiency. I need help in it.
Firstly I need to know which all commands in rtpengine has to be supported by asynchronous complementary functions.
Secondly I was trying to understand the async functionality in evapi. I understood the suspend and continue process used to implement this. But I couldn't see anywhere we are trying to continue the suspended processes.
Thank you.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3283
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3283(a)github.com>
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [ ] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [ ] PR should be backported to stable branches
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
When the stirshaken module is in use and configured to cache certifications, validation will succeed on the very first attempt but will then fail every time the certificate is loaded from cache. The reason is because this module only saves the certificate and discards the any supplied chain certificates. This patch causes the module to save all supplied certificates and properly loads them upon retrieval.
For the loading to work a patch is required in libstirshaken. A PR has already been submitted and is linked below. Without that patch the problem will persist but no other harm is done. This is a safe change to make that does not break existing behaviour.
- save all certificates provided by signor to the disk cache
- properly load all certificates when loading from cache
- requires patch to libstirshaken (PR 123); this patch causes no harm (but no benefit) without it
- resolve unrelated compiler warnings on 32bit systems
https://github.com/signalwire/libstirshaken/pull/123
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3175
-- Commit Summary --
* stirshaken: Properly handle intermediary/chain certificates when caching certificates
* stirshaken: close file in write failure cases
-- File Changes --
M src/modules/stirshaken/stirshaken_mod.c (106)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3175.patchhttps://github.com/kamailio/kamailio/pull/3175.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3175
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3175(a)github.com>
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [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 -->
For correct work geoip2 in KEMI, need preinit container for save result from module. I made changes based on phonenum module.
Without preinit in log we get err:
```
geoip2_update_pv(): container not found: XXX.XXX.XXX.XXX
```
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3288
-- Commit Summary --
* preinit container for KEMI
* add resid in Readme
* add xml doc
* update numbering
* format
-- File Changes --
M src/modules/geoip2/README (24)
M src/modules/geoip2/doc/geoip2_admin.xml (28)
M src/modules/geoip2/geoip2_mod.c (21)
M src/modules/geoip2/geoip2_pv.c (7)
M src/modules/geoip2/geoip2_pv.h (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3288.patchhttps://github.com/kamailio/kamailio/pull/3288.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3288
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3288(a)github.com>