If you are not sure that keepalives are configured properly or next hop
gateways can reply promptly to OPTIONS keepalives, then just let
dispatcher route calls anyhow to gateways and set a low value for
retransmission timeout (see t_set_fr() from tm module). I noticed some
old gateways forget to se
Sorry for the late reply
the dispatcher is set as follows:
# - dispatcher params -
modparam("dispatcher", "list_file", DS_LIST)
modparam("dispatcher", "flags", 2)
modparam("dispatcher", "dst_avp", "$avp(AVP_DST)")
modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)")
modparam("dispatcher
Hi Sergio,
Make sure your dispatcher probing parameters are set correctly. (reply
codes as well).
And if it happens again you can catch OPTIONS traffic with sngrep "CSeq:
[0-9]+ OPTIONS"
and see what happens on this level.
Whether Kamailio does send pings, whether replies from gw are the same as
Hello
I would start by looking at the logs when that happens. The gateway would
only get marked "ip" when there is no reply by the gateway or when it
replies with 500. Also OPTIONs not being replied promptly.
Maybe add some logging right before ds_mark_dst("ip").
Hope that helps,
Regards,
David
Hello,
Using Kamailio 5.1.6 for load balancing & failover,
I noticed that from time to time, and very rarely, the dispatcher module
stops dispatching to the Asterisk servers.
I have to execute a "kamcmd dispatcher reload" for it to (re)start working.
This is my dispatcher.list :
1 sip:10.19.XXX.Y
