<!-- 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
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
Presented at Kamailio World 2018, load balancing doing congestion detection
More information can be found
http://www.castmm.com/KW2018.pdfhttps://github.com/jchavanton/kam_load_balancing
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1533
-- Commit Summary --
* dispatcher: congestion detection load balancing
-- File Changes --
M src/modules/dispatcher/dispatch.c (103)
M src/modules/dispatcher/dispatch.h (2)
M src/modules/dispatcher/doc/dispatcher.xml (2)
M src/modules/dispatcher/doc/dispatcher_admin.xml (9)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1533.patchhttps://github.com/kamailio/kamailio/pull/1533.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/1533
Module: kamailio
Branch: master
Commit: aec8c5f8d2b06fb96621aa881652d19a266d4e3d
URL: https://github.com/kamailio/kamailio/commit/aec8c5f8d2b06fb96621aa881652d19…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2018-06-05T16:46:41+02:00
modules: readme files regenerated - rtpengine ... [skip ci]
---
Modified: src/modules/rtpengine/README
---
Diff: https://github.com/kamailio/kamailio/commit/aec8c5f8d2b06fb96621aa881652d19…
Patch: https://github.com/kamailio/kamailio/commit/aec8c5f8d2b06fb96621aa881652d19…
---
diff --git a/src/modules/rtpengine/README b/src/modules/rtpengine/README
index 478eaff3bb..77c62a7563 100644
--- a/src/modules/rtpengine/README
+++ b/src/modules/rtpengine/README
@@ -52,7 +52,7 @@ Richard Fuchs
1. Admin Guide
1. Overview
- 2. Multiple RTP proxy usage
+ 2. Usage With Multiple RTPEngine Instances
3. Dependencies
3.1. Kamailio Modules
@@ -249,7 +249,7 @@ Chapter 1. Admin Guide
Table of Contents
1. Overview
- 2. Multiple RTP proxy usage
+ 2. Usage With Multiple RTPEngine Instances
3. Dependencies
3.1. Kamailio Modules
@@ -362,19 +362,19 @@ Chapter 1. Admin Guide
however due to the incompatible control protocol, it only works with
RTP proxies which specifically support it.
-2. Multiple RTP proxy usage
+2. Usage With Multiple RTPEngine Instances
- The rtpengine module can support multiple RTP proxies for
+ The rtpengine module can support multiple RTPEngine instances for
balancing/distribution and control/selection purposes.
- The module allows definition of several sets of rtpproxies.
+ The module allows definition of several sets of RTPEngines.
Load-balancing will be performed over a set and the admin has the
ability to choose what set should be used. The set is selected via its
id - the id being defined with the set. Refer to the “rtpengine_sock”
module parameter definition for syntax description.
The balancing inside a set is done automatically by the module based on
- the weight of each RTP proxy from the set.
+ the weight of each RTPEngine from the set.
The selection of the set is done from script prior using
rtpengine_delete(), rtpengine_offer() or rtpengine_answer() functions -
@@ -395,11 +395,11 @@ Chapter 1. Admin Guide
the set was selected using setid_avp, the avp needs to be set only once
before rtpengine_offer() or rtpengine_manage() call.
- From the current implementation point of view, the sets of rtpproxy
- nodes are shared memory(shm), so all processes can see a common list of
- nodes. There is no locking when setting the nodes enabled/disabled (to
- keep the memory access as fast as possible). Thus, problems related to
- node state might appear for concurrent processes that might set the
+ From the current implementation point of view, the sets of rtpengine
+ nodes are in shared memory(shm), so all processes can see a common list
+ of nodes. There is no locking when setting the nodes enabled/disabled
+ (to keep the memory access as fast as possible). Thus, problems related
+ to node state might appear for concurrent processes that might set the
nodes enabled/disabled(e.g. by fifo command). This robustness problems
are overcome as follows.
@@ -809,12 +809,12 @@ mysql> describe rtpengine;
+----------+------------------+------+-----+---------------------+-------+
mysql> select * from rtpengine;
-+-------+---------------------------+--------+----------+---------------------+
-| setid | url | weight | disabled | stamp |
-+-------+---------------------------+--------+----------+---------------------+
-| 0 | udp:rtpproxy1.domain:8800 | 1 | 0 | 2016-03-10 10:30:54 |
-| 0 | udp:rtpproxy2.domain:8800 | 1 | 1 | 2016-03-10 10:30:54 |
-+-------+---------------------------+--------+----------+---------------------+
++-------+----------------------------+--------+----------+---------------------+
+| setid | url | weight | disabled | stamp |
++-------+----------------------------+--------+----------+---------------------+
+| 0 | udp:rtpengine1.domain:8800 | 1 | 0 | 2016-03-10 10:30:54 |
+| 0 | udp:rtpengine2.domain:8800 | 1 | 1 | 2016-03-10 10:30:54 |
++-------+----------------------------+--------+----------+---------------------+
mysql> select * from version;
+---------------------------+---------------+
Module: kamailio
Branch: master
Commit: 9383174b32b6b49dd9f0757450abadb45690515f
URL: https://github.com/kamailio/kamailio/commit/9383174b32b6b49dd9f0757450abadb…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2018-06-05T16:34:48+02:00
rtpengine: docs - updated some of rtpproxy occurences to rtpengine
---
Modified: src/modules/rtpengine/doc/rtpengine_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/9383174b32b6b49dd9f0757450abadb…
Patch: https://github.com/kamailio/kamailio/commit/9383174b32b6b49dd9f0757450abadb…
---
diff --git a/src/modules/rtpengine/doc/rtpengine_admin.xml b/src/modules/rtpengine/doc/rtpengine_admin.xml
index ae875cfc4a..a43b8d8264 100644
--- a/src/modules/rtpengine/doc/rtpengine_admin.xml
+++ b/src/modules/rtpengine/doc/rtpengine_admin.xml
@@ -31,13 +31,13 @@
</section>
<section>
- <title>Multiple &rtp; proxy usage</title>
+ <title>Usage With Multiple RTPEngine Instances</title>
<para>
- The rtpengine module can support multiple &rtp; proxies for
+ The rtpengine module can support multiple RTPEngine instances for
balancing/distribution and control/selection purposes.
</para>
<para>
- The module allows definition of several sets of rtpproxies.
+ The module allows definition of several sets of RTPEngines.
Load-balancing will be performed over a set and the admin has the
ability to choose what set should be used. The set is selected via
its id - the id being defined with the set. Refer to the
@@ -46,7 +46,7 @@
</para>
<para>
The balancing inside a set is done automatically by the module based on
- the weight of each &rtp; proxy from the set.
+ the weight of each RTPEngine from the set.
</para>
<para>
The selection of the set is done from script prior using
@@ -74,8 +74,8 @@
set only once before rtpengine_offer() or rtpengine_manage() call.
</para>
<para>
- From the current implementation point of view, the sets of rtpproxy nodes
- are shared memory(shm), so all processes can see a common list of nodes.
+ From the current implementation point of view, the sets of rtpengine nodes
+ are in shared memory(shm), so all processes can see a common list of nodes.
There is no locking when setting the nodes enabled/disabled (to keep the
memory access as fast as possible). Thus, problems related to node state
might appear for concurrent processes that might set the nodes
@@ -573,12 +573,12 @@ mysql> describe rtpengine;
+----------+------------------+------+-----+---------------------+-------+
mysql> select * from rtpengine;
-+-------+---------------------------+--------+----------+---------------------+
-| setid | url | weight | disabled | stamp |
-+-------+---------------------------+--------+----------+---------------------+
-| 0 | udp:rtpproxy1.domain:8800 | 1 | 0 | 2016-03-10 10:30:54 |
-| 0 | udp:rtpproxy2.domain:8800 | 1 | 1 | 2016-03-10 10:30:54 |
-+-------+---------------------------+--------+----------+---------------------+
++-------+----------------------------+--------+----------+---------------------+
+| setid | url | weight | disabled | stamp |
++-------+----------------------------+--------+----------+---------------------+
+| 0 | udp:rtpengine1.domain:8800 | 1 | 0 | 2016-03-10 10:30:54 |
+| 0 | udp:rtpengine2.domain:8800 | 1 | 1 | 2016-03-10 10:30:54 |
++-------+----------------------------+--------+----------+---------------------+
mysql> select * from version;
+---------------------------+---------------+
Hello,
Kamailio SIP Server v5.1.4 stable release is out.
This is a maintenance release of the latest stable branch, 5.1, that
includes fixes since the release of v5.1.3. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.1.x. Deployments running previous v5.1.x
versions are strongly recommended to be upgraded to v5.1.4.
For more details about version 5.1.4 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2018/06/kamailio-v5-1-4-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Many thanks to all contributing and using Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - www.kamailioworld.com