[SR-Users] Problems with dispatcher module | feature disabled

Alessio Casco alessio.casco at nexmo.com
Tue Oct 27 18:59:44 CET 2015


Hello Daniel!

Adding the sock_avp parameter, fixes the error on the log, but the
behaviour is the same as before.


As you can see, with nothing listening on those two servers, the
loadbalancing it's still disables.


SET: {
ID: 3
TARGETS: {
DEST: {
URI: sip:media22-test.internal:5060
FLAGS: AP
PRIORITY: 0
}
DEST: {
URI: sip:media21-test.internal:5060
FLAGS: AP
PRIORITY: 0
}
}
}

Thanks
Alessio


On Tue, Oct 27, 2015 at 5:33 PM, Daniel-Constantin Mierla <miconda at gmail.com
> wrote:

> Hello,
>
> it looks like sock_avp parameter has to be set -- it is there before 4.3.0
> release, as I could spot in 'git blame' for dispatcher.c:768.
>
> Not sure is really needed for failover, I will check its usage when I get
> first chance.
>
>
> http://kamailio.org/docs/modules/stable/modules/dispatcher.html#dispatcher.p.sock_avp
>
> Cheers,
> DAniel
>
>
> On 26/10/15 17:00, Alessio Casco wrote:
>
>
> Hello!
>
> We noticed today an issue with the kamailio loadbalancing.
>
> Basically kamailio is not considering if an host is up or not, backends
> are set always as "FLAGS: AP" even if the host is down.
>
> I see this when the proxy starts :
>
> ERROR: dispatcher [dispatcher.c:768]: ds_warn_fixup(): failover functions
> used, but required AVP parameters are NULL -- feature disabled
>
> These the parameters I have set:
>
> # ----- dispatcher params -----
> modparam("dispatcher", "list_file", "/etc/kamailio/dispatcher.list")
> modparam("dispatcher", "dst_avp", "$avp(dsdst)")
> modparam("dispatcher", "grp_avp", "$avp(dsgrp)")
> modparam("dispatcher", "cnt_avp", "$avp(dscnt)")
> modparam("dispatcher", "ds_ping_method", "OPTIONS")
> modparam("dispatcher", "ds_ping_reply_codes", "class=2;class=3;code=404")
> modparam("dispatcher", "ds_ping_from", " <sip%3Aproxy at sip.nexmo.com>
> sip:proxy at sip.nexmo.com")
> modparam("dispatcher", "ds_ping_interval", 20)
> modparam("dispatcher", "ds_probing_threshold", 1)
> modparam("dispatcher", "ds_probing_mode", 1)
> modparam("dispatcher", "ds_hash_size", 10)
> modparam("dispatcher", "ds_hash_expire", 3600)
> modparam("dispatcher", "ds_hash_initexpire", 60)
> modparam("dispatcher", "ds_hash_check_interval", 10)
> modparam("dispatcher", "use_default", 0)
> modparam("dispatcher", "attrs_pvname", "$avp(carrierattr)")
> modparam("dispatcher", "setid_pvname", "$avp(carriergroup)")
> modparam("dispatcher", "flags", 2)
>
> I use 4.3.3, I think this issue started after upgrading from 4.3.1 but I
> can't say for sure.
>
> Can someone please give us some advices on this?
>
> Thanks
> Alessio
>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users at lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
> --
> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
> Book: SIP Routing With Kamailio - http://www.asipto.com
> Kamailio Advanced Training, Nov 30-Dec 2, Berlin - http://asipto.com/kat
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20151027/f1748125/attachment.html>


More information about the sr-users mailing list