[Serdev] [Patch] Ability to check negative reply code in the failure_route

[Atle Samuelsen]

* Dan Pascu <dan at ag-projects.com> [050308 18:12]:
> On Tuesday 08 March 2005 18:52, Maxim Sobolev wrote:
> > In fact the really funny part of your own post is that you will get
> > locally generated 408 not only in the case when gateway can't be reached
> > but also in the case when final recipient has been ringed but has not
> > answered in 120 seconds. :-P
> 
> Heh, finally you understood what I wanted to accomplish. It was not the funny 
> part of my post it was the essence of my post ;)
> This is exactly what I wanted to do (distinguish between these 2 kind of 408, 
> both generated internally by ser, but as a result of different conditions)
> However as I said it's no longer an issue as I have found a way to do this 
> using some tricks in ser.cfg.


Lemme guess, your setting a flag in your reply_route, and then reading
it in the failure_route?

That works, for some reason, its a hack , but it works..

the only drawback with this is when you have multiple downstream
elements and you want to do a prioritation of them.

-Atle