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

[Dan Pascu]

The patch doesn't do this. It only implements an alternative to 
t_check_status() which is more in-line with how status is checked in on_reply 
route.

However I second that it would be nice to be able to differentiate how a 
timeout occurs.

I found it would be useful if we could differentiate from a 408 that is coming 
from a remote proxy or one generated internally by SER after no response was 
received in the given time. This can help implement fallback failure routes 
for PSTN for example, where I need to know if the 408 was internally 
generated by SER because the PSTN gateway didn't respond in which case I want 
to try another PSTN gateway, or it came from the PSTN gateway because the 
PSTN phone was not answered in a given time, in which case I don't want to 
try the second gateway.

On Monday 07 March 2005 16:17, Atle Samuelsen wrote:
> Hi Maxim,
>
> I have'nt had time to look at your patch yet, but I was wondering if
> this would impliment a way to check if a user is unreachable because he
> infact times-out after a invite, (no sip-message from 100->199) or if he
> timesout because the fr_inv_timer timesout, (sip-message-from 100->199)
>
>
> The reason I want to distiguis on this is that if a user is temporary
> offline, and still in location, or just timeout because he does'nt take
> the phone.
>
>
> I'll look at the patch later tonight (or tomorrow)
>
> -Atle

-- 
Dan