Hello,
about 8 months since the last major release v5.8.x, therefore it is the
time to plan a bit the next steps for getting v6.0.0 out.
The Kamailio Developers Meeting is schedule in Dusseldorf, Germany
during November 19-20, 2024, where we expect to push out a consistent
number of updates. Then maybe we can wait for another 2 weeks or so to
settle down/finish those updates. After that, if no other new features
are planned by developers in short term, we can enter the testing phase,
so the new major version can be released during the second part of
January 2025 or first part of February 2025.
Therefore, if you have new features under development that might require
more than 1-1.5 months from now, and you want to get them in v6.0.0, let
us know to plan properly.
Other time lines suggestions to get to v6.0.0 are also welcome!
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Hello,
Kamailio SIP Server project is organizing another meeting of its
developers and community members during November 19-20, 2024 (Tue-Wed),
hosted again by sipgate.de in Dusseldorf, Germany.
The event is intended to facilitate the interaction between Kamailio
developers and contributors in order to offer a convenient environment
for working together on several topics of high interest for the project,
including writing code for Kamailio and its tools, improving
documentation, or discuss about future development.
Everyone from the community is welcome to join, developer or user
interested in helping the project. Please note we have a limited
capacity of seats in the meeting room, the main policy for accepting
participants being first come first server. Also, very important to be
aware that this is not an event to learn how to use Kamailio.
More details about the event, the venue, how to register, are available at:
* https://www.kamailio.org/w/developers-meeting/
Looking forward to those two intensive hacking Kamailio days in Dusseldorf!
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Module: kamailio
Branch: master
Commit: cf54baa30db65a96bd732295200503b99b566914
URL: https://github.com/kamailio/kamailio/commit/cf54baa30db65a96bd732295200503b…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2024-11-05T18:01:09+01:00
modules: readme files regenerated - snmpstats ... [skip ci]
---
Modified: src/modules/snmpstats/README
Modified: src/modules/sst/README
---
Diff: https://github.com/kamailio/kamailio/commit/cf54baa30db65a96bd732295200503b…
Patch: https://github.com/kamailio/kamailio/commit/cf54baa30db65a96bd732295200503b…
---
diff --git a/src/modules/snmpstats/README b/src/modules/snmpstats/README
index 407b6def697..83ee6cd975c 100644
--- a/src/modules/snmpstats/README
+++ b/src/modules/snmpstats/README
@@ -282,10 +282,11 @@ Chapter 1. Admin Guide
* usrloc - all scalars and tables relating to users and contacts are
dependent on the usrloc module. If the module is not loaded, the
respective tables will be empty.
- * dialog or dialog-ng - all scalars relating to the number of dialogs
- are dependent on the presence of a dialog module. Furthermore, if
- the module is not loaded, then the kamailioDialogLimitMinorEvent,
- and kamailioDialogLimitMajorEvent alarm will be disabled.
+ * dialog or ims_dialog - all scalars relating to the number of
+ dialogs are dependent on the presence of a dialog module.
+ Furthermore, if the module is not loaded, then the
+ kamailioDialogLimitMinorEvent, and kamailioDialogLimitMajorEvent
+ alarm will be disabled.
The contents of the kamailioSIPMethodSupportedTable change depending on
which modules are loaded.
diff --git a/src/modules/sst/README b/src/modules/sst/README
index a5bd40b681d..9cf8dba51c6 100644
--- a/src/modules/sst/README
+++ b/src/modules/sst/README
@@ -170,7 +170,7 @@ Chapter 1. Admin Guide
3.1. Kamailio Modules
The following modules must be loaded before this module:
- * dialog or dialog-ng - dialog module and its dependencies. (tm)
+ * dialog or ims_dialog - dialog module and its dependencies. (tm)
* sl - stateless module.
3.2. External Libraries or Applications
@@ -293,7 +293,7 @@ modparam("sst", "sst_flag", 6)
route {
...
if (method=="INVITE") {
- dlg_manage(); # Track the dialog
+ dlg_manage(); # Track the dialog
setflag(6); # set the sst flag
}
...
Module: kamailio
Branch: master
Commit: 6c408ff8c7b558a725d67898d5f1a8dc3d717c61
URL: https://github.com/kamailio/kamailio/commit/6c408ff8c7b558a725d67898d5f1a8d…
Author: Henning Westerholt <hw(a)gilawa.com>
Committer: Henning Westerholt <hw(a)gilawa.com>
Date: 2024-11-05T16:45:50Z
snmpstats: use proper name for ims module in docs
---
Modified: src/modules/snmpstats/doc/snmpstats_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/6c408ff8c7b558a725d67898d5f1a8d…
Patch: https://github.com/kamailio/kamailio/commit/6c408ff8c7b558a725d67898d5f1a8d…
---
diff --git a/src/modules/snmpstats/doc/snmpstats_admin.xml b/src/modules/snmpstats/doc/snmpstats_admin.xml
index 12a6ee152c0..538908e2573 100644
--- a/src/modules/snmpstats/doc/snmpstats_admin.xml
+++ b/src/modules/snmpstats/doc/snmpstats_admin.xml
@@ -215,7 +215,7 @@
<listitem>
<para>
- <emphasis>dialog or dialog-ng</emphasis> - all scalars relating to the number of dialogs are
+ <emphasis>dialog or ims_dialog</emphasis> - all scalars relating to the number of dialogs are
dependent on the presence of a dialog module. Furthermore, if the module is
not loaded, then the kamailioDialogLimitMinorEvent, and kamailioDialogLimitMajorEvent
alarm will be disabled.
<!-- Kamailio Pull Request Template -->
#### 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)
- [X] 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
Long overdue clean-up of `app_python3`; remove legacy modules and rely solely on KEMI.
Bring it in sync with `app_python3s`.
Larger background: this is part I of a series of commits to enable free-threading builds of python to be used in kamailio.
https://py-free-threading.github.io/
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3986
-- Commit Summary --
* app_python3: removal of legacy modules
-- File Changes --
M src/modules/app_python3/app_python3_mod.c (14)
D src/modules/app_python3/mod_Core.c (68)
D src/modules/app_python3/mod_Core.h (36)
D src/modules/app_python3/mod_Logger.c (266)
D src/modules/app_python3/mod_Logger.h (37)
D src/modules/app_python3/mod_Ranks.c (96)
D src/modules/app_python3/mod_Ranks.h (35)
D src/modules/app_python3/mod_Router.c (84)
D src/modules/app_python3/mod_Router.h (36)
M src/modules/app_python3/python_iface.c (12)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3986.patchhttps://github.com/kamailio/kamailio/pull/3986.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3986
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3986(a)github.com>
Module: kamailio
Branch: master
Commit: 0ffe157bc13e7759ae1cee63a584fad4ac9eb38f
URL: https://github.com/kamailio/kamailio/commit/0ffe157bc13e7759ae1cee63a584fad…
Author: S-P Chan <shihping.chan(a)gmail.com>
Committer: space88man <shihping.chan(a)gmail.com>
Date: 2024-11-05T11:01:08+08:00
app_python3: refactor GIL and thread state handling
* KEMI Python scripts that use Python threading for background jobs
would observe that the Python threads are not running
This is due to not releasing the GIL when returning to the Kamailio
event loop from KEMI calls
* The module was using PyGILState_Ensure / PyGILState_Release to
ensure thread-correctness
It turns out that in this case these are the wrong functions to use
The main thread is already correct due to Py_Initialize();
the PyGILState_xxx functions are redundant
To release the GIL so Python threads run we use the macros
Py_BLOCK_THREADS/Py_UNBLOCK_THREADS
Note: the PyGILState_XXX functions are for C-threads created
by Python unaware libraries
---
Modified: src/modules/app_python3/app_python3_mod.c
Modified: src/modules/app_python3/apy_kemi.h
Modified: src/modules/app_python3/python_exec.c
---
Diff: https://github.com/kamailio/kamailio/commit/0ffe157bc13e7759ae1cee63a584fad…
Patch: https://github.com/kamailio/kamailio/commit/0ffe157bc13e7759ae1cee63a584fad…