[sr-dev] More about locally generated 408
Henning Westerholt
henning.westerholt at 1und1.de
Mon Apr 12 13:25:05 CEST 2010
On Friday 09 April 2010, Iñaki Baz Castillo wrote:
> I understand your point, but it would make more sense if 408 is just
> caused when a transaction fails due to fr_timer (no provisional
> response from destination). But this is not the case as TM generates
> 408 when fr_inv_timer expires (maybe 60-120 seconds after receiving a
> provisional response). So the 408 is a confussing response:
>
> - In the first case (fr_timer expires) there has been a real error (alarm).
> - In the second case (fr_inv_timer) there has been no problem, just
> the call progress took so long that the proxy has decided to cancel
> it.
>
> Perhaps in the second case the proxy should generate a 480 and leave
> the 408 just for fr_timer expiration?
Hi Iñaki,
hm, i'd opt to keep the 408 here. What about setting a flag if you received a
provisional response in reply_route, and then check this in your failure_route
when you process the 408? We do it this way, and did not found any problems so
far. I think Juha also proposed something like this earlier.
Cheers,
Henning
More information about the sr-dev
mailing list