Hi,
I've got a reinvite transaction scenario through a stateful proxy (due
to Record-Route) where the reinvite is not being ACK'd. The proxy
appears to drop state after 7 seconds or less, since, after some period,
when the retransmissions of the 200 OK back off, the time elapsed
between 200 OKs shows as 7 seconds in my logs, and the second 200 OK is
already showing up as stateless.
The ACK eventually shows up, but after something like 10 seconds.
My question is: why is the proxy dropping state for that transaction so
early? As far as I understood RFC 3261 Section 17.2.1 ("INVITE Server
Transactions"), the part that says
If timer H fires while in the "Completed" state, it implies that the
ACK was never received. In this case, the server transaction MUST
transition to the "Terminated" state, and MUST indicate to the TU
that a transaction failure has occurred.
this should be Timer H, which is listed in the table as 64*T1. The proxy
is using the default T1 value of 500 ms.
The elapsed time between the origination of the sequential INVITE and
the stateless 200 OK is 7 seconds (any stateful 200 OKs received prior
to this point are not logged). Should it not be ~32 seconds? Or have I
got it all wrong?
Thanks!
-- Alex
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
