Take a look at
3.25. ds_ping_reply_codes(string)
This parameter defines the valid response codes, which are accepted as a
valid reply to the PING-Method. It is a list separated by colons, whery you
may define either a single code (e.g. "code=202" would accept 202 as an
additional, valid response) or a class of responses, you want to accept
(e.g. "class=2" would accept everything from 200 to 299 as valid response).
This parameter can be modified via ser config framework.
Default value is “” (only 200 OK is accepted).
Example 1.26. Set the “ds_ping_reply_codes” parameter
... modparam("dispatcher", "ds_ping_reply_codes",
"class=2;code=403;code=488;class=3") ...
Default i think is 500 but you might have some other codes enabled.
On Tue, Mar 27, 2018, 18:30 Daniel W. Graham <d...@cmsinter.net> wrote:
> Enough time spent and was able to answer my question.
>
>
>
> Failure_route controls the condition(s), however what I was not seeing was
> a 500 response sent from another off network peer which was triggering the
> event route per the failure route config criteria.
>
>
>
> -dan
>
>
>
> *From:* sr-users <sr-users-boun...@lists.kamailio.org> * On Behalf Of *Daniel
> W. Graham
>
> *Sent:* Tuesday, March 27, 2018 12:15 PM
>
>
> *To:* Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
> *Subject:* Re: [SR-Users] Dispatcher Routing Failure
>
>
>
> Sorry, let me clarify my last statement –
>
>
>
> I’m seeing dispatcher:dst-down event route getting hit even though all sip
> requests are answered by dispatcher destination. Those requests resulting
> in 503 error (maybe others, not confirmed yet) appear to be triggering the
> dispatcher:dst-down event route.
>
>
>
> So looking for the criteria that dispatcher module uses to determine a
> ‘failed request’.
>
>
>
> Any thoughts?
>
>
>
> -dan
>
>
>
> *From:* sr-users <sr-users-boun...@lists.kamailio.org> *On Behalf Of *Daniel
> W. Graham
> *Sent:* Tuesday, March 27, 2018 12:04 PM
> *To:* Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
> *Subject:* Re: [SR-Users] Dispatcher Routing Failure
>
>
>
> I’m seeing dispatcher:dst-down event route getting hit but no prior failed
> sip requests that I see in packet capture.
>
>
>
> Any thoughts on what could be happing?
>
>
>
> -dan
>
>
>
> *From:* sr-users <sr-users-boun...@lists.kamailio.org> *On Behalf Of *Daniel
> W. Graham
> *Sent:* Friday, March 23, 2018 12:40 PM
> *To:* Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
> *Subject:* [SR-Users] Dispatcher Routing Failure
>
>
>
> What constitutes a ‘failed request’ in dispatcher module, in which a
> gateway is marked inactive?
>
>
>
> From documentation –
>
> ds_ping_interval
>
> With this parameter you can define the interval for sending a request to a
> gateway marked as inactive upon a *failed request routing to it*.
>
>
>
> ds_probing_threshold
>
> If you want to set a gateway into inactive mode, there can be a specific
> number of *failed requests* until it will change from "active" to
> "inactive".
>
>
>
> Thanks,
>
>
>
> -dan
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
