- Use description found in https://sip-router.org/wiki/ref_manual/timers
<!-- 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
- [ ] Tested changes locally
- [x] Related to issue #3939
#### Description
<!-- Describe your changes in detail -->
Fix documentation according to the description found in https://sip-router.org/wiki/ref_manual/timers. They better reflect the actual procedure.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4207
-- Commit Summary --
* tm: Update docs of fr_timer to match the implementation
-- File Changes --
M src/modules/tm/doc/params.xml (8)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4207.patchhttps://github.com/kamailio/kamailio/pull/4207.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4207
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4207(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
- [ ] 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/4192
-- Commit Summary --
* cmake: Alter some of cmake-format options
* cmake: Fix formatting according to cmake-format config file.
-- File Changes --
M CMakeLists.txt (18)
M cmake/BuildType.cmake (8)
M cmake/cmake-format.py (4)
M cmake/compiler-specific.cmake (24)
M cmake/defs.cmake (29)
M cmake/groups.cmake (45)
M cmake/modules-docs.cmake (94)
M cmake/modules/FindBerkeleyDB.cmake (60)
M cmake/modules/FindErlang.cmake (52)
M cmake/modules/FindLdap.cmake (32)
M cmake/modules/FindLibev.cmake (4)
M cmake/modules/FindLibfreeradiusClient.cmake (21)
M cmake/modules/FindMariaDBClient.cmake (3)
M cmake/modules/FindMySQL.cmake (114)
M cmake/modules/FindNETSNMP.cmake (15)
M cmake/modules/FindOracle.cmake (11)
M cmake/modules/FindRadius.cmake (6)
M cmake/os-specific/darwin.cmake (38)
M cmake/os-specific/dragonfly.cmake (9)
M cmake/os-specific/freebsd.cmake (3)
M cmake/os-specific/linux.cmake (9)
M src/CMakeLists.txt (44)
M src/core/CMakeLists.txt (16)
M src/modules/CMakeLists.txt (55)
M src/modules/app_perl/CMakeLists.txt (17)
M src/modules/auth_radius/CMakeLists.txt (7)
M src/modules/db2_ldap/CMakeLists.txt (3)
M src/modules/db_berkeley/CMakeLists.txt (3)
M src/modules/dnssec/CMakeLists.txt (5)
M src/modules/kazoo/CMakeLists.txt (3)
M src/modules/nghttp2/CMakeLists.txt (5)
M src/modules/nsq/CMakeLists.txt (5)
M src/modules/phonenum/CMakeLists.txt (16)
M src/modules/ruxc/CMakeLists.txt (3)
M src/modules/sctp/CMakeLists.txt (6)
M src/modules/secsipid_proc/CMakeLists.txt (3)
M src/modules/snmpstats/CMakeLists.txt (3)
M src/modules/tls/CMakeLists.txt (29)
M src/modules/tlsa/CMakeLists.txt (11)
M src/modules/xhttp_pi/CMakeLists.txt (7)
M utils/CMakeLists.txt (6)
M utils/db_berkeley/CMakeLists.txt (3)
M utils/kamcmd/CMakeLists.txt (26)
M utils/kamctl/CMakeLists.txt (161)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4192.patchhttps://github.com/kamailio/kamailio/pull/4192.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4192
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4192(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 -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4170
-- Commit Summary --
* hide all record routes except last one in reply messages
-- File Changes --
M src/modules/topoh/th_msg.c (16)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4170.patchhttps://github.com/kamailio/kamailio/pull/4170.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4170
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4170(a)github.com>
- add dispatcher modparam `ds_ping_socket`
- add gateway param `ping_socket`
<!-- 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)
- [ ] 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
could be useful for HA use cases where multiple kamailio nodes share a common Virtual IP (e.g.: managed by the VRRP).
we need to route requests using Virtual IP socket configured with `ds_default_sockname`/`socket` and to perform destinations probing using self-IP socket configured with `ds_ping_socket`/`ping_socket`.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4186
-- Commit Summary --
* dispatcher: added ping socket configuration
-- File Changes --
M src/modules/dispatcher/dispatch.c (32)
M src/modules/dispatcher/dispatch.h (2)
M src/modules/dispatcher/dispatcher.c (25)
M src/modules/dispatcher/doc/dispatcher_admin.xml (20)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4186.patchhttps://github.com/kamailio/kamailio/pull/4186.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4186
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4186(a)github.com>
Hello!
Over the years, there have been discussions about what options could be
made available to donate to Kamailio project in order to support its
required infrastructure, administrative or development of complex
components. Creating a foundation or using a crowdfunding platform have
been explored, trying to take in consideration the needed man power and
overhead, the transparency and accountability.
To move forward on this matter, the Kamailio management team has decided
to use Open Collective, with the fiscal host Open Collective Europe, as
the platform for accepting and managing donations, more details,
including the link where donations can be made, are published at:
- https://www.kamailio.org/w/donations/
The donations should target either the support of project administration
or the development of new feature, therefore before donating it is
recommend to email to <management [at] lists.kamailio.org> providing
some details about the scope of your donation.
We also plan to discuss about it at the next Kamailio World Conference:
May 12-13, 2025, organized again in Berlin, Germany, where many
developers and members of the management board and our community get
together, being a good opportunity to clarify and decide how to use the
donations. More details about the event at:
- https://www.kamailioworld.com
Thanks for flying Kamailio!
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, May 12-13, 2025, Berlin -- kamailioworld.com