Hi Ricardo, So, what you say is that the 504 does not trigger the failure route ?
Regards, Bogdan Ricardo Carvalho wrote: > Thanks Bogdan, I've tried a failure_route with append_branch and > t_relay like you told, and in fact it works when the reply of the > first call atempt is for example a 500, but with 504 replys it doesn't > work! > > Do you have any clue on what can be missing? > > Best regards, > Ricardo. > > > > > > On Wed, Apr 22, 2009 at 8:08 AM, Bogdan-Andrei Iancu > <[email protected] <mailto:[email protected]>> wrote: > > Hi Ricardo, > > Use a failure route to catch the transaction failure event (due > 504 reply); from this failure route you can create new branches by > simply relaying the call to a new destination: > http://www.opensips.org/index.php?n=Resources.DocsCoreRoutes#toc3 > > Regards, > Bogdan > > Ricardo Carvalho wrote: > > Hi, > I'm implementing a route in openser.cfg which sends calls to > ENUM destinations via one SBC. In cases where there is no IP > connectivity for that ENUM calls to be delivered, my SBC > fires a timeout sending back to openser a 504 SIP message > reply. In this cases I would like to be able to implement in > openser like a fallback to a "next priority" in the dialplan > in case this 504 is received, now making openser to start a > call to my telco sip trunk. > How can I do this in openser? For the tests I made, in the > onreply_route I can identify that 504 messages, but from there > I never can manage making a new call for the destination DID > that was initially dialed because it seems like openser has > flushed the request-uri that was initially dialed... > Is there any way to do this? > Best regards, > Ricardo Carvalho. > > ------------------------------------------------------------------------ > > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
