Greetings gurus,
I've been going working on a proxy for while now, and am currently
staring to look at timer C handling.
The short version: Should I reset timer C when I create a new txn,
on a failure scenario(according to 3263)?
Longer version:
I've become a bit puzzled on what I should do in a failure scenario,
matching the one described in 3263, which causes me to create a new
transaction and make a second (Nth) attempt.
My question arose since timer C is supposed to started be "per transaction",
and this would lead me to assume that I would reset the timer for every
attempt, since each attempt has a new branch => new txn.
But if I do that, then one of the scenarios in 16.8 (below) becomes,
at least with default timer values, impossible.
Since timer C is 3 minutes, and every time i get a failure I create a
new txn, which resets the timer. And failure occurs if txn times out
which normally happens after just 32 secs.
Then timer C should never be able to fire, because we'd keep creating
new txns, and resetting the timer all the time?
And since the rule about interpreting this case as a 408 is so clear,
i was wondering wether I am resetting timer C when I shouldnt..
Regards
Taisto Qvist
Network Architect.
--
16.8 Processing Timer C
If timer C should fire, the proxy MUST either reset the timer with
any value it chooses, or terminate the client transaction. If the
client transaction has received a provisional response, the proxy
MUST generate a CANCEL request matching that transaction. If the
client transaction has not received a provisional response, the proxy
MUST behave as if the transaction received a 408 (Request Timeout)
response.
--
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
