- Add missing modules to alpine packages as listed in GH #4131
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [x] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [x] PR should be backported to stable branches
- [x] Tested changes locally
- [x] Related to issue #4131
Changes should be backported to 6.0 branch, not 5.8 branch since it contains modules
that don't exist in 5.8
#### Description
Update `/pkg/kamailio/alpine/APKBUILD` file to add modules that have been added to
Kamailio in the last few years. This also includes updating the dependency list for the
modules.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4132
-- Commit Summary --
* pkg/kamailio/alpine: Add new modules
-- File Changes --
M pkg/kamailio/alpine/APKBUILD (146)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4132.patchhttps://github.com/kamailio/kamailio/pull/4132.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4132
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4132(a)github.com>
This pull request enables db_oracle to be built against oracle 18.3.0.0.0 dev libraries using cmake.
It requires the following env variables to be set:
```
declare -x ORACLE_HOME="/usr/lib/oracle/18.3/client64/"
declare -x ORACLE_INCLUDE_DIR="/usr/include/oracle/18.3/client64"
```
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4128
-- Commit Summary --
* db_oracle: fix db_oracle build for oracle 18.3.0.0.0
-- File Changes --
M cmake/modules/FindOracle.cmake (3)
M src/modules/db_oracle/CMakeLists.txt (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4128.patchhttps://github.com/kamailio/kamailio/pull/4128.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4128
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4128(a)github.com>
Hello,
I am trying to figure out what would be the best date to branch 6.0 in
the git repo.
To allow a bit of time after returning from the winter holidays to tune
more the cmake and packaging, I would think that January 15, 2025 could
be a good choice.
If nobody comes with other opinions/suggestions, then we will go for it.
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio v6.0.0 is out – it comes with 5 new modules and important
updates to the core components and existing modules.
The increment of the first version number reflects several important
updates, among them: multi-threaded option for UDP receiving, option for
specifying a range of ports to listen to, support for expressions with
variables for most of the module functions parameters, internal
libraries are directly inked to the core, support to use cmake to
compile and install Kamailio.
You can read a bit more detailed release notes at:
* https://www.kamailio.org/w/kamailio-v6.0-0-release-notes/
Many thanks to all developers and community members that made possible
this release.
v6.0.0 brings more flexibility and optimizations across many existing
components and modules, new parameters, functions, variables and
transformations.
Enjoy Kamailio v6.0.0!
Thank you for flying Kamailio!
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com
Module: kamailio
Branch: 6.0
Commit: f540d97e3f0be21cb6abc61ac701c8fd437b4371
URL: https://github.com/kamailio/kamailio/commit/f540d97e3f0be21cb6abc61ac701c8f…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2025-01-29T11:34:17+01:00
ims_qos_npn: small docs updates
(cherry picked from commit dcdcee0d9f2326e079f905632af9db3b898330ab)
---
Modified: src/modules/ims_qos_npn/doc/ims_qos_npn.xml
Modified: src/modules/ims_qos_npn/doc/ims_qos_npn_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/f540d97e3f0be21cb6abc61ac701c8f…
Patch: https://github.com/kamailio/kamailio/commit/f540d97e3f0be21cb6abc61ac701c8f…
---
diff --git a/src/modules/ims_qos_npn/doc/ims_qos_npn.xml b/src/modules/ims_qos_npn/doc/ims_qos_npn.xml
index 0cd99dcd0c7..fa9d03eb003 100644
--- a/src/modules/ims_qos_npn/doc/ims_qos_npn.xml
+++ b/src/modules/ims_qos_npn/doc/ims_qos_npn.xml
@@ -7,7 +7,7 @@
]>
<book>
<bookinfo>
- <title>The IMS QoS Module - Neat Path Networks "branch"</title>
+ <title>The IMS QoS NPN Module</title>
<authorgroup>
<author>
diff --git a/src/modules/ims_qos_npn/doc/ims_qos_npn_admin.xml b/src/modules/ims_qos_npn/doc/ims_qos_npn_admin.xml
index dfb6ea9ed15..70459b65801 100644
--- a/src/modules/ims_qos_npn/doc/ims_qos_npn_admin.xml
+++ b/src/modules/ims_qos_npn/doc/ims_qos_npn_admin.xml
@@ -16,7 +16,7 @@
charging control functions performed by an Application Function (e.g.
P-CSCF) over the Rx interface. This module is dependent on the CDP (C
Diameter Peer) modules for communicating with PCRF as specified in 3GPP
- specification TS 29.214.</para>
+ specification TS 29.214. It is an enhaced variant of ims_qos.</para>
</section>
<section>
@@ -548,7 +548,7 @@ modparam("ims_qos", "dialog_direction", 1)
If set to 1 it will trust the bottom Via as the UE IP/port/transport when doing client identification.
</para>
<para>
- Normally, the UE identification should be done on IPsec SPIs and source IP/port of the packets.
+ Normally, the UE identification should be done on IPsec SPIs and source IP/port of the packets.
In some cases the ims_* modules trust the top Via on requests and the bottom Via on responses. In some (better)
cases this trusts the received-from IP (or the alias in the Contact header).
</para>
@@ -707,7 +707,7 @@ modparam("ims_qos", "af_signaling_port_ps", "5063")
<para><emphasis>Note:</emphasis> this is executed asynchronously. See example on how to
retrieve return value</para>
- <para><emphasis>Note:</emphasis> this authorization session triggers
+ <para><emphasis>Note:</emphasis> this authorization session triggers
event_route[qos:asr_registration], event_route[qos:rar_access_network] and event_route[qos:terminate_dialog].</para>
<example>
@@ -785,7 +785,7 @@ route[REGISTER_AAR_REPLY]
<para><emphasis>Note:</emphasis> this is executed asynchronously. See example on how to
retrieve return value</para>
- <para><emphasis>Note:</emphasis> this authorization session triggers
+ <para><emphasis>Note:</emphasis> this authorization session triggers
event_route[qos:asr_call], event_route[qos:rar_access_network] and event_route[qos:terminate_dialog].</para>
Module: kamailio
Branch: master
Commit: dcdcee0d9f2326e079f905632af9db3b898330ab
URL: https://github.com/kamailio/kamailio/commit/dcdcee0d9f2326e079f905632af9db3…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2025-01-29T11:34:01+01:00
ims_qos_npn: small docs updates
---
Modified: src/modules/ims_qos_npn/doc/ims_qos_npn.xml
Modified: src/modules/ims_qos_npn/doc/ims_qos_npn_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/dcdcee0d9f2326e079f905632af9db3…
Patch: https://github.com/kamailio/kamailio/commit/dcdcee0d9f2326e079f905632af9db3…
---
diff --git a/src/modules/ims_qos_npn/doc/ims_qos_npn.xml b/src/modules/ims_qos_npn/doc/ims_qos_npn.xml
index 0cd99dcd0c7..fa9d03eb003 100644
--- a/src/modules/ims_qos_npn/doc/ims_qos_npn.xml
+++ b/src/modules/ims_qos_npn/doc/ims_qos_npn.xml
@@ -7,7 +7,7 @@
]>
<book>
<bookinfo>
- <title>The IMS QoS Module - Neat Path Networks "branch"</title>
+ <title>The IMS QoS NPN Module</title>
<authorgroup>
<author>
diff --git a/src/modules/ims_qos_npn/doc/ims_qos_npn_admin.xml b/src/modules/ims_qos_npn/doc/ims_qos_npn_admin.xml
index dfb6ea9ed15..70459b65801 100644
--- a/src/modules/ims_qos_npn/doc/ims_qos_npn_admin.xml
+++ b/src/modules/ims_qos_npn/doc/ims_qos_npn_admin.xml
@@ -16,7 +16,7 @@
charging control functions performed by an Application Function (e.g.
P-CSCF) over the Rx interface. This module is dependent on the CDP (C
Diameter Peer) modules for communicating with PCRF as specified in 3GPP
- specification TS 29.214.</para>
+ specification TS 29.214. It is an enhaced variant of ims_qos.</para>
</section>
<section>
@@ -548,7 +548,7 @@ modparam("ims_qos", "dialog_direction", 1)
If set to 1 it will trust the bottom Via as the UE IP/port/transport when doing client identification.
</para>
<para>
- Normally, the UE identification should be done on IPsec SPIs and source IP/port of the packets.
+ Normally, the UE identification should be done on IPsec SPIs and source IP/port of the packets.
In some cases the ims_* modules trust the top Via on requests and the bottom Via on responses. In some (better)
cases this trusts the received-from IP (or the alias in the Contact header).
</para>
@@ -707,7 +707,7 @@ modparam("ims_qos", "af_signaling_port_ps", "5063")
<para><emphasis>Note:</emphasis> this is executed asynchronously. See example on how to
retrieve return value</para>
- <para><emphasis>Note:</emphasis> this authorization session triggers
+ <para><emphasis>Note:</emphasis> this authorization session triggers
event_route[qos:asr_registration], event_route[qos:rar_access_network] and event_route[qos:terminate_dialog].</para>
<example>
@@ -785,7 +785,7 @@ route[REGISTER_AAR_REPLY]
<para><emphasis>Note:</emphasis> this is executed asynchronously. See example on how to
retrieve return value</para>
- <para><emphasis>Note:</emphasis> this authorization session triggers
+ <para><emphasis>Note:</emphasis> this authorization session triggers
event_route[qos:asr_call], event_route[qos:rar_access_network] and event_route[qos:terminate_dialog].</para>