Thanks. On Fri, Apr 24, 2015 at 2:01 PM, Eric Tamme <[email protected]> wrote:
> As I said, failure route is transaction based, so any transaction failure > will trigger it. see > http://www.opensips.org/Documentation/Script-Routes-2-2#toc3 > > > On 04/24/2015 11:57 AM, Podrigal, Aron wrote: > > The problem is that there is no response coming back, media server 1 > crashed. > > On Fri, Apr 24, 2015 at 1:54 PM, Eric Tamme <[email protected]> wrote: > >> failure_route is called based on a transaction failure - so even if the >> request was in dialog, as long as you t_relay() it and it gets a response >> code >=300 failure route will be called on receipt of the response. >> >> -Eric >> >> >> On 04/24/2015 11:22 AM, Podrigal, Aron wrote: >> >> Hi, >> >> What is the right way to handle failures for sequential requests. So if >> Media Server #1 hangs, I wanna create a new transaction route to Media >> Server #2. >> >> -- >> Aron Podrigal >> - >> //Be happy :-) >> >> >> _______________________________________________ >> Users mailing >> [email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > > > -- > Aron Podrigal > - > //Be happy :-) > > > _______________________________________________ > Users mailing > [email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -- Aron Podrigal - //Be happy :-)
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
