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

Daniel-Constantin Mierla miconda at gmail.com
Mon Nov 2 09:01:14 CET 2015



On 28/10/15 15:49, Alessio Casco wrote:
> Hello!
>
> Thanks to @cezar91 we finally spot the issue, basically kamailio it's
> transforming t_code=0 (timeout) to 408 and the dispatcher module sees
> this last value.
>
> Oct 28 14:16:32 net21-test /usr/sbin/kamailio[31911]: DEBUG: tm
> [t_reply.c:1311]: t_should_relay_response(): ->>>>>>>>> T_code=0,
> new_code=408
> Oct 28 14:16:32 net21-test /usr/sbin/kamailio[31911]: DEBUG: tm
> [t_reply.c:2135]: local_reply(): DEBUG: local transaction completed
> 408/0 (totag retr: 0/1024)
> Oct 28 14:16:32 net21-test /usr/sbin/kamailio[31911]: DEBUG:
> dispatcher [dispatch.c:2489]: ds_options_callback(): OPTIONS-Request
> was finished with code 408 (to sip:media21-test.internal:5060, group 3)
>
> So if you set on "ds_ping_reply_codes" class=4 or code=408, kamailio
> will consider the backend up even if it doesn't actually receives that
> specific code.
>
> Do you think it worth to update the docs and advice about this behaviour?
> I just spot now the typo on the first email about the code sorry!

Feel free to do a pull request on github for dispatcher documentation
where you add the notes you think it helps clarifying better such
situation. Contributions to documentation are always welcome!

Cheers,
Daniel

>
> Thanks for your help
> Alessio
>
> On Wed, Oct 28, 2015 at 12:53 PM, Daniel-Constantin Mierla
> <miconda at gmail.com <mailto:miconda at gmail.com>> wrote:
>
>     Hello,
>
>     can you want the network traffic and see if the OPTIONS requests
>     are sent out?
>
>     Cheers,
>     Daniel
>
>
>     On 27/10/15 18:59, Alessio Casco wrote:
>>     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 <mailto: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: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 list
>>>         sr-users at lists.sip-router.org
>>>         <mailto:sr-users at lists.sip-router.org>
>>>         http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>         -- 
>>         Daniel-Constantin Mierla
>>         http://twitter.com/#!/miconda <http://twitter.com/#%21/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
>>         <mailto:sr-users at lists.sip-router.org>
>>         http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>>
>>
>>     _______________________________________________
>>     SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>     sr-users at lists.sip-router.org <mailto:sr-users at lists.sip-router.org>
>>     http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>     -- 
>     Daniel-Constantin Mierla
>     http://twitter.com/#!/miconda <http://twitter.com/#%21/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 <mailto:sr-users at lists.sip-router.org>
>     http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>

-- 
Daniel-Constantin Mierla
http://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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20151102/3f3a4319/attachment.html>


More information about the sr-users mailing list