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

[Dan Pascu]

On Tuesday 08 March 2005 16:15, Maxim Sobolev wrote:
> In the case when user have been ringed have not picked up call timely
> the PSTN gateway should use 480 Temporarily Unavailable not 408. Check
> RFC for details. Any abuse of 408 should be reported to the gateway's
> vendor instead.

Well, I'm sure you realize the funny part or your post. SER is in the same 
boat in this regard since it generates a 408 not a 480 after a phone has 
ringed but was not answered before the INVITE timeout did expire.

But anyway, what it generates is not the issue here. Also what the PSTN 
gateway sends back is not the issue either.

The issue is to determine if the 408 that was generated internally by SER is a 
result of the fact that the gateway is dead and didn't reply at all, or the 
fact that the INVITE timeout did expire because the user didn't answer.

So it is all about distinguishing in which context falls a 408 that was 
_internally_ generated by SER. Nothing to do with what the PSTN gateway sends 
back.

Nevermind this however, as meanwhile I found a way to determine the context in 
which the 408 was generated using some ser.cfg tricks.

-- 
Dan