Ok, my mistake, the modparams related to dispatcher module were in !endif
that was not processed. In future, I will do not edit the cfg file without
code highlighting ..arrg
On Mon, Dec 19, 2011 at 3:56 PM, Mino Haluz wrote:
> Updated to 3.2.1 (debian package) and still the same behaviour.
>
> v
Updated to 3.2.1 (debian package) and still the same behaviour.
version: kamailio 3.2.1 (i386/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE
Hello,
On 12/19/11 1:35 PM, Mino Haluz wrote:
This is in the log file:
ERROR: dispatcher [dispatcher.c:640]: failover functions used, but
AVPs paraamters required are NULL -- feature disabled
it is not related to ping options. You have to upgrade first to 3.2.1 to
get the ping functionality
This is in the log file:
ERROR: dispatcher [dispatcher.c:640]: failover functions used, but AVPs
paraamters required are NULL -- feature disabled
and the output of kamctl fifo ds_list:
SET_NO:: 1
SET:: 1
URI:: sip:IP1:5060 flags=AX priority=0 attrs=
URI:: sip:IP2:5060 flags=AX priority=0 a
Hello,
is this at least version 3.2.1 (or the latest branch 3.2)?
What do you get with: kamctl fifo ds_list?
Cheers,
Daniel
On 12/19/11 12:49 PM, Mino Haluz wrote:
Hi,
please, could someone specify the conditions when the dispatcher
module sends the INFO pings to the gateways ?
modparam("
Hi,
please, could someone specify the conditions when the dispatcher module
sends the INFO pings to the gateways ?
modparam("dispatcher", "flags", 2)
modparam("dispatcher", "dstid_avp", "$avp(s:test)")
modparam("dispatcher", "dst_avp", "$avp(AVP_DST)")
modparam("dispatcher", "grp_avp", "$avp(AVP_
