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

[Maxim Sobolev]

Looks like that it does what we want, the main problem then is the lack 
of proper documentation. However, my patch may be still valid since it 
provides unified way to access negative status in failure route similar 
to the way to check status in reply route. Alternatively, use of status 
builtin in the routing script should be depreciated in the favour of 
t_check_status(), which provides the same functionality.

-Maxim

Dan Pascu wrote:
> Is there any difference between this approach and using t_check_status() in 
> the failure route?
> 
> On Monday 07 March 2005 14:37, Maxim Sobolev wrote:
> 
>>Folks,
>>
>>I've found it quite limiting that there is no way to check SIP response
>>code that has lead to execution of failure_route routine. For example
>>when implementing VM one certainly would want to filter out 487 and
>>probably all 3xx class replies.
>>
>>I've put together small patch which adds new keyword - failure_status
>>that can be checked just like status, but in the failure_route. Please
>>review. Any comments or suggestions are appreciated. Patch can be found
>>here:
>>
>>http://www.portaone.com/~sobomax/ser_failure_code.diff
> 
> 
>