<!-- 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 -->
expires_range should not make expires smaller than min_expires.
A valid value might be made to small, which triggers 423 when min_expires_mode is set to 1
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2365
-- Commit Summary --
* registrar: expires_range should not make expires < min_expires
-- File Changes --
M src/modules/registrar/sip_msg.c (11)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2365.patchhttps://github.com/kamailio/kamailio/pull/2365.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/2365
Hello,
the formal notification that the development for the next major version
5.4.0 is now frozen. The focus has to be on testing the master branch.
Also, the master branch should not get commits with new features till
the branch 5.4 is created, expected to happen in 2-4 weeks, a matter of
how testing goes on. Meanwhile, the commits with new features in the C
code can be pushed to personal branches, pull requests can still be
done, but they will be merged after branching 5.4.
Can still be done commits with documentation improvements, enhancements
to related tool (e.g., kamctl, kamcmd), exporting missing KEMI
functions and completing the functionality of the new modules added in 5.4.
Once the branch 5.4 is created, new features can be pushed again to
master branch as usual. From that moment, the v5.3.0 should be out very
soon, time used for further testing but also preparing the release of
packages.
If someone is not sure if a commit brings a new feature, just make a
pull request and it can be discussed there on github portal or via
sr-dev mailing list.
A summary of what is new in upcoming 5.4 is going to be built at:
* https://www.kamailio.org/wiki/features/new-in-5.4.x
Upgrade guidelines will be collected at:
* https://www.kamailio.org/wiki/install/upgrade/5.3.x-to-5.4.0
Everyone is more than welcome to contribute to the above wiki pages,
especially to the upgrade guidelines, to help everyone else during the
migration process from v5.3.x to 5.4.x.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
<!-- 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
- [ ] 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
- [ X] Related to issue #2361
#### Description
When a destination is selected using one of the hash algorithms (over Call-ID, From, etc.)
and destination is not available, then the next is selected. This causes the following problem :
All messages to the unavailable destination will be sent to the same unique destination.
This will cause that one destination will receive double load and the rest will continue with the same.
Solution : To better distribute messages, while also guaranteeing the same distribution of the hash, a re-hash of the hash is made.
As the rehash could select the same or other failed destination, it can rehash several times. The number of rehashes made is controlled by :
modparam("dispatcher", "ds_rehash_max", -1)
Which can take the following values :
-1 : The total count of destinations is used
0 : Disabled. Reverts to original implementation.
Positive number. Maximum number of rehashes.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2362
-- Commit Summary --
* dispatcher : better distribution when using hash and destination is not available.
-- File Changes --
M src/modules/dispatcher/dispatch.c (192)
M src/modules/dispatcher/dispatcher.c (103)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2362.patchhttps://github.com/kamailio/kamailio/pull/2362.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/2362
Hello,
based on the discussions during the last online devel meeting, the plan
is to release the next major version (Kamailio v5.4.0) around the mid of
this summer.
Therefore I propose to freeze the development on Thursday, June 18,
2020. Then we will have about 4-6 weeks of testing before the release is
out. Master will be unfrozen when the branch 5.4 is created (usually
that was done after 3-4 weeks in the testing phase).
If you are planning to introduce new features in the 5.4 release series,
be sure you push them to master branch or create a pull request till the
freezing date.
If anyone else wants a different time line for 5.4.0 release, let us
know and we can discuss to match the best for everyone.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla