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-bounces@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-bounces@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