Module: kamailio
Branch: master
Commit: 14a87383fbae102b430ed6cfdba2559f1768cdd0
URL: https://github.com/kamailio/kamailio/commit/14a87383fbae102b430ed6cfdba2559…
Author: Jurijs I <jurijs.ivolga(a)gmail.com>
Committer: Henning Westerholt <henningw(a)users.noreply.github.com>
Date: 2019-01-10T21:49:58+01:00
dispatcher: update for module docs (#1804)
- update for module docs (#1804)
- Some minor comments for dispatcher module were added
- Additionally a description were added, what the several states means when dispatcher list are executed
---
Modified: src/modules/dispatcher/doc/dispatcher_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/14a87383fbae102b430ed6cfdba2559…
Patch: https://github.com/kamailio/kamailio/commit/14a87383fbae102b430ed6cfdba2559…
---
diff --git a/src/modules/dispatcher/doc/dispatcher_admin.xml b/src/modules/dispatcher/doc/dispatcher_admin.xml
index 3b40c04622..c0a55b27ad 100644
--- a/src/modules/dispatcher/doc/dispatcher_admin.xml
+++ b/src/modules/dispatcher/doc/dispatcher_admin.xml
@@ -631,12 +631,16 @@ modparam("dispatcher", "force_dst", 1)
<itemizedlist>
<listitem>
<para>Value 0: If set to 0, only the gateways with state PROBING are tested.
- After a gateway is probed, the PROBING state is cleared in this mode.</para>
+ After a gateway is probed, the PROBING state is cleared in this mode.
+ This means that no probing will be executed at all only if flag in config file is set to 8/PROBING
+ (please check destination list file syntaxis for more details), it will probe only one time at startup or
+ after dispatcher reload.</para>
</listitem>
<listitem>
<para>Value 1: If set to 1, all gateways are tested. If set to 1 and
there is a failure of keepalive to an active gateway, then it is
- set to TRYING state.</para>
+ set to TRYING state. This means that probing will be executed all the time,
+ but you can skip some servers with flag 4 in destination list file, for example.</para>
</listitem>
<listitem>
<para>Value 2: if set to 2, only gateways in inactive state with
@@ -1701,8 +1705,21 @@ onreply_route {
</para>
<programlisting format="linespecific">
&sercmd; dispatcher.list
- </programlisting>
- </section>
+ ...
+DEST: {
+ URI: sip:192.168.0.1:5060
+ FLAGS: AP
+ PRIORITY: 12
+}
+ ...
+</programlisting>
+<para>FLAGS consist out of 2 letters. First letter describe status of destination: A-active,
+ I – inactive, T – trying, D – disabled. Second letter might be P or X. P is for probing,
+ so AP means destination is active and it is tested by SIP options continuously.
+ X means that there are no probing or sip pinging. So AX means that destination is assumed as active
+ and it is not tested by SIP options. DX respectively is disabled destination what is not tested and etc.
+</para>
+ </section>
<section id="dispatcher.r.reload">
<title>
<function moreinfo="none">dispatcher.reload</function>
If you want to document the changes needed to upgrade the config defined in the howto, please, be my guest and write a post in your blog, or a whole howto, if you prefer, so other people can benefit of those hours you spent searching for the solution of your problem.
Sorry, but, I still don't see how this is related to kamailio default config or the lack of upgrade documentation.
Again, there's a mailing list sr-users(a)lists.kamailio.org where you can ask for help. This is for actual bugs in the code.
--
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/commit/673f4af214fcb613ce227b5c9b1b805…
hi @linuxmaniac due either kamailo or asterisk talk about that problem i spend many days in setup the migration from 4 to 5.. due kamailio does not property redirect to asterisk due that changes in the related commit.. that change are in nowhere place in the network.. neither in the documentation that you pointed.. due the table sopected "sipusers" are related to asterisk.. that seems not changed between vesions of asterisk.. but has a change in kamailio!
due the cited " asipto howto, " are not official and theres no documentation about that integracion up to date, that change about spected version table at asterisk side are not pointed... **i dont know why the kamailio now spected that "sipusers" table of asterisk need version 7, this commit only defines the version of the kamailio suscriber table.. so if that are as i just said. it a bug!**
--
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/commit/673f4af214fcb613ce227b5c9b1b805…
related to https://github.com/kamailio/kamailio/issues/1780 that was silenced due a really true! was update a force upgrade without documented! now kamalio and asterisk integration has a version check incompatibility that can be workaround with ... `modparam("auth_db", "version_table", 0)` that by default are "1"
--
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/commit/673f4af214fcb613ce227b5c9b1b805…
Update for Readme Dispatcher module. I added some minor comments for dispatcher module, what I think might be useful for somebody.
<!-- 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/1803
-- Commit Summary --
* Update for Readme Dispatcher module
-- File Changes --
M src/modules/dispatcher/doc/dispatcher_admin.xml (8)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1803.patchhttps://github.com/kamailio/kamailio/pull/1803.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/1803