Hello,
when trying to set a destination to inactive using dispatcher.set_state after setting the state to "i", when I do a "dispatcher.list" I see the state as "ix". The "x" state appears not to be documented.
After a short time (seconds) the flags return to state "ip" (probing). According to the module documentation I should be able to set the "probing" mode.
1. Why doesn't probing mode remain disabled? 2. What is state "x"?
Cheers, -Sven
hi. Sven.
1. Have you set modparam("dispatcher", "ds_probing_mode", 1)? If so, it will be moved to PROBING mode after ds_ping_interval 2. 'X' means "not any set". just a cross ;)
2016-01-13 16:17 GMT+03:00 Sven Neuhaus neuhaus@tyntec.com:
Hello,
when trying to set a destination to inactive using dispatcher.set_state after setting the state to "i", when I do a "dispatcher.list" I see the state as "ix". The "x" state appears not to be documented.
After a short time (seconds) the flags return to state "ip" (probing). According to the module documentation I should be able to set the "probing" mode.
- Why doesn't probing mode remain disabled?
- What is state "x"?
Cheers, -Sven
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello,
to complete: if you want destination to not to be pinged anymore and not used for routing, you have to disable (deactivate) it, not to set it in state inactive. There are three states:
- active - inactive (at any time can become active based on ping activity) - disabled (it is going to be ingored for pinging as well)
The x is as Dmitri said, just a placeholder to say no flag is set there and have always the output being two chars.
Cheers, Daniel
On 13/01/16 16:08, Dmitri Savolainen wrote:
hi. Sven.
- Have you set modparam("dispatcher", "ds_probing_mode", 1)? If so,
it will be moved to PROBING mode after ds_ping_interval 2. 'X' means "not any set". just a cross ;)
2016-01-13 16:17 GMT+03:00 Sven Neuhaus <neuhaus@tyntec.com mailto:neuhaus@tyntec.com>:
Hello, when trying to set a destination to inactive using dispatcher.set_state after setting the state to "i", when I do a "dispatcher.list" I see the state as "ix". The "x" state appears not to be documented. After a short time (seconds) the flags return to state "ip" (probing). According to the module documentation I should be able to set the "probing" mode. 1. Why doesn't probing mode remain disabled? 2. What is state "x"? Cheers, -Sven _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Savolainen Dmitri
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi Dmitri,
Am 13.01.2016 um 16:08 schrieb Dmitri Savolainen:
- Have you set modparam("dispatcher", "ds_probing_mode", 1)? If so, it
will be moved to PROBING mode after ds_ping_interval
Yes, I have it set to 1. So if I set ds_probing_mode to 0 ("only the gateways with state PROBING are tested"), do I have to set state PROBING manually at startup for all gateways? Or are gateways set to probing by default?
- 'X' means "not any set". just a cross ;)
Good to know. Thanks.
Daniel wrote:
to complete: if you want destination to not to be pinged anymore and not used for routing, you have to disable (deactivate) it, not to set it in state inactive. There are three states:
I somehow overlooked "disabled" state. What I really want it for new calls not to use a certain gateway any more so I can take it down for maintenance once all calls have finished. If I set it to "disabled", will it have an effect on calls that are ongoing? For example DTMF sent via SIP info packets?
-Sven
So if I set ds_probing_mode to 0 ("only the gateways with state PROBING are tested"), do I have to set state PROBING manually at startup for all gateways? Or are gateways set to probing by default?
in ds_probing_mode=0 not any PROBING by default. if you just want to test your node after startup(and kamcmd dispatcher.reload), you may set state to "AP" (flag=8 in dispatcher table), Node will moved to "AX" if test OK (and stop pinging up to setting PROBING mode again via kamcmd or configuration script), or "IP" if test failed
if you want to test your node forever, set ds_probing_mode to 1
If I set it to "disabled", will it have an effect on calls that are
ongoing? For example DTMF sent via SIP info packets?
Usually dispatcher used only for initial requests, so indialog request will send to DX node. But it may be changed via config
2016-01-14 12:34 GMT+03:00 Sven Neuhaus neuhaus@tyntec.com:
Hi Dmitri,
Am 13.01.2016 um 16:08 schrieb Dmitri Savolainen:
- Have you set modparam("dispatcher", "ds_probing_mode", 1)? If so, it
will be moved to PROBING mode after ds_ping_interval
Yes, I have it set to 1. So if I set ds_probing_mode to 0 ("only the gateways with state PROBING are tested"), do I have to set state PROBING manually at startup for all gateways? Or are gateways set to probing by default?
- 'X' means "not any set". just a cross ;)
Good to know. Thanks.
Daniel wrote:
to complete: if you want destination to not to be pinged anymore and not used for routing, you have to disable (deactivate) it, not to set it in state inactive. There are three states:
I somehow overlooked "disabled" state. What I really want it for new calls not to use a certain gateway any more so I can take it down for maintenance once all calls have finished. If I set it to "disabled", will it have an effect on calls that are ongoing? For example DTMF sent via SIP info packets?
-Sven
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users