Module: kamailio
Branch: master
Commit: 6048a966df29b6447052b93cd86ecaf3eaaa7a41
URL: https://github.com/kamailio/kamailio/commit/6048a966df29b6447052b93cd86ecaf…
Author: Aleksandar Yosifov <alexyosifov(a)gmail.com>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2019-12-19T10:56:49+01:00
ims_ipsec_pcscf: new parameter in ipsec_forward()
- added a new optional parameter in ipsec_forward()
to set or not 'send force socket' for request
messages. Useful for ipsec and tcp connections.
If set to 1 - send requests through existing
ipsec tunnel when tcp is used. In combination
with tcp_reuse_port=yes.
---
Modified: src/modules/ims_ipsec_pcscf/cmd.c
Modified: src/modules/ims_ipsec_pcscf/cmd.h
Modified: src/modules/ims_ipsec_pcscf/doc/ims_ipsec_pcscf_admin.xml
Modified: src/modules/ims_ipsec_pcscf/ims_ipsec_pcscf_mod.c
---
Diff: https://github.com/kamailio/kamailio/commit/6048a966df29b6447052b93cd86ecaf…
Patch: https://github.com/kamailio/kamailio/commit/6048a966df29b6447052b93cd86ecaf…
Module: kamailio
Branch: master
Commit: e99bfd2368c28e920f92af9ade1c29cb2ba709da
URL: https://github.com/kamailio/kamailio/commit/e99bfd2368c28e920f92af9ade1c29c…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2019-12-17T19:31:12+01:00
modules: readme files regenerated - tm ... [skip ci]
---
Modified: src/modules/tm/README
---
Diff: https://github.com/kamailio/kamailio/commit/e99bfd2368c28e920f92af9ade1c29c…
Patch: https://github.com/kamailio/kamailio/commit/e99bfd2368c28e920f92af9ade1c29c…
---
diff --git a/src/modules/tm/README b/src/modules/tm/README
index 4b23eacb58..71ae54e48e 100644
--- a/src/modules/tm/README
+++ b/src/modules/tm/README
@@ -117,7 +117,7 @@ Daniel-Constantin Mierla
4.36. t_lookup_cancel([1])
4.37. t_drop_replies([mode])
4.38. t_save_lumps()
- 4.39. t_load_contacts()
+ 4.39. t_load_contacts([mode])
4.40. t_next_contacts()
4.41. t_next_contact_flow()
4.42. t_check_status(re)
@@ -372,7 +372,7 @@ Chapter 1. Admin Guide
4.36. t_lookup_cancel([1])
4.37. t_drop_replies([mode])
4.38. t_save_lumps()
- 4.39. t_load_contacts()
+ 4.39. t_load_contacts([mode])
4.40. t_next_contacts()
4.41. t_next_contact_flow()
4.42. t_check_status(re)
@@ -1724,7 +1724,7 @@ modparam("tm", "rich_redirect", 3)
4.36. t_lookup_cancel([1])
4.37. t_drop_replies([mode])
4.38. t_save_lumps()
- 4.39. t_load_contacts()
+ 4.39. t_load_contacts([mode])
4.40. t_next_contacts()
4.41. t_next_contact_flow()
4.42. t_check_status(re)
@@ -2473,7 +2473,7 @@ failure_route[1] {
t_relay();
}
-4.39. t_load_contacts()
+4.39. t_load_contacts([mode])
This is the first of the three functions that can be used to implement
serial/parallel forking based on q and +sip.instance values of
@@ -2489,18 +2489,33 @@ failure_route[1] {
nothing.
If the current destination set contains more than one branch, the
- function sorts them according to increasing value of the q parameter
- and then stores the branches in reverse order into the XAVP.
+ function sorts them according to the algorithm selected with the 'mode'
+ paramenter and then stores the branches in reverse order into the XAVP.
The q parameter of a branch contains a value from range 0-1.0 and it
expresses relative preference of the branch among all branches in the
destination set. The higher the q value the more preference the user
- agent gave to the branch. Branches with higher q values will be tried
- before branches with lower ones when serial forking takes place.
+ agent gave to the branch. The parameter 'mode' controls which type of
+ algorithm kamailio will apply to sort the branches based on the q
+ values:
+
+ - '0' or missing: branches with higher q values will be tried before
+ branches with lower ones when serial forking takes place Equals q
+ values will result in a parallel forking.
+
+ - '1': branches are ordered using a proportional algorithm that uses to
+ q value as the weight of the branch. Higher is the q value, higher is
+ the probability to be tried as first. Equals q values means equals
+ probability to be tried. Differently from the previous mode there is no
+ possibility to have parallel forking. Branches with q values equals to
+ 0 or lower are not considered by the ordering algorithm, but just added
+ at the end of the list as backup option if all other branches fail.
+ This algorithm can be useful in case of endpoints in ACTIVE-ACTIVE
+ configuration to load-balance the calls.
After calling t_load_contacts(), function t_next_contacts() and
possibly also t_next_contact_flow() need to be called one or more times
- in order to retrieve the branches based on their q value.
+ in order to retrieve the branches based on their order.
Function returns 1 if loading of contacts succeeded or there was
nothing to do. In case of an error, function returns -1 (see syslog).
#### Pre-Submission Checklist
- [ ] 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:
- [ ] PR should be backported to stable branches
- [ ] Tested changes locally
- [ ] Related to issue #2167
#### Description
Extended t_load_contacts function with the parameter 'mode'.
It can be used to define the algorithm to use for ordering the contacts.
If 0, or missing, the standard algorithm with be used.
If 1, the new weight-based algorithm will be used.
The new algorithm uses the q value as the weight of the branch.
Higher is the q value, higher is the probability to be tried as first. Equals q values means equals probability to be tried.
Branches with q values equals to 0 or lower are not considered by the ordering algorithm, but just added at the end of the list as backup option if all other branches fail.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2178
-- Commit Summary --
* tm: new weight-based call-termination distribution
-- File Changes --
M src/modules/tm/doc/functions.xml (33)
M src/modules/tm/t_serial.c (266)
M src/modules/tm/t_serial.h (7)
M src/modules/tm/tm.c (9)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2178.patchhttps://github.com/kamailio/kamailio/pull/2178.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/2178
Module: kamailio
Branch: master
Commit: 1399714fbba63732f94eb8034dabb1e565ca832a
URL: https://github.com/kamailio/kamailio/commit/1399714fbba63732f94eb8034dabb1e…
Author: Marco Capetta <mcapetta(a)sipwise.com>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2019-12-17T19:29:36+01:00
tm: new weight-based call-termination distribution
Extended t_load_contacts function with the parameter 'mode'.
It can be used to define the algorithm to use for ordering
the contacts.
If 0, or missing, the standard algorithm with be used.
If 1, the new weight-based algorithm will be used.
The new algorithm uses the q value as the weight of the branch.
Higher is the q value, higher is the probability to be tried
as first. Equals q values means equals probability to be tried.
Branches with q values equals to 0 or lower are not considered by
the ordering algorithm, but just added at the end of the list
as backup option if all other branches fail.
---
Modified: src/modules/tm/doc/functions.xml
Modified: src/modules/tm/t_serial.c
Modified: src/modules/tm/t_serial.h
Modified: src/modules/tm/tm.c
---
Diff: https://github.com/kamailio/kamailio/commit/1399714fbba63732f94eb8034dabb1e…
Patch: https://github.com/kamailio/kamailio/commit/1399714fbba63732f94eb8034dabb1e…
- only handles active dialogs in state 4
- wipes out a given dialog callously
- no subcalls to dialog-ending functions
- dialog is then removed by the recurring cleaning function execution
- as discussed in sr-users in topic "[Dialog] Removing entries from dialog memory"
#### Pre-Submission Checklist
- [ ] 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:
- [ ] PR should be backported to stable branches
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
Hi,
As discussed in the sr-users mailing-list, I am proposing this PR to add a very simple new rpc command to the dialog module. dlg.kill_active_dialog kills any given active dialog from memory.
A paragraph in the dialog documentation precises the dangerous nature of this command, to be used with caution.
Please feel free to discuss about it.
Thanks!
Julien
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2111
-- Commit Summary --
* dialog: adding RPC dlg.kill_active_dlg command
-- File Changes --
M src/modules/dialog/dialog.c (56)
M src/modules/dialog/doc/dialog.xml (5)
M src/modules/dialog/doc/dialog_admin.xml (33)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2111.patchhttps://github.com/kamailio/kamailio/pull/2111.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/2111