This info is in the readme of the module, not wiki, iirc. You can make a
pull request with more details there, by adding the text to
src/modules/dispatcher/doc/dispatcher_admin.xml -- any contribution to
documentation is more than welcome.
Cheers,
Daniel
On 26.02.19 17:24, Denys Pozniak wrote:
>
Thanks!
I set in the way below, looks working. Maybe wiki needs to be updated?
4 sip:10.6.3.122:5060 0 5
4 sip:10.6.3.1:5060 0 5
4 sip:10.6.3.2:5060 0 5
4 sip:10.6.3.3:5060 0 5
4 sip:10.6.3.4:5060 0 5
4 sip:10.6.3.5:5060 0 1
вт, 26 февр. 2019 г. в 17:48, Daniel-Constantin Mierla :
> Hello,
>
Hello,
you have to set the priority field for each destination to ensure a
particular order there. While with text file one can consider the order
of appearance, this is no longer valid for database -- the order in a
table can be different that what is returned by "select * ...",
therefore the
kamcmd dispatcher.list shows gateways in reverse order (comparing to the
file) and "last hope" gw is the last one here (URI: sip:10.6.3.122:5060).
SET: {
ID: 4
TARGETS: {
DEST: {
Hello!
I use dispatcher with algorithm=1 (hashing over from URI) with module
parameter use_default=1.
So I am expecting that last string in dispatcher.list for specific set will
be the "last hope" for call routing.
dispatcher.list
..
4 sip:10.6.3.122:5060
4 sip:10.6.3.1:5060
4 sip:10.6.3.2:5060
