Hello, RFC3261 defines how transactions should be handled. It clearly defines the role of a "client" transaction and a "server" transaction. The "client" transaction is required to start request timers T1 and T2. T1 is a retransmission timer and T2 is a lifetime timer. T2 is always 64*T1 (which allows for 7 retransmissions before the session is to be torn down)
My question is as follows: In the server transaction (meaning I'm receiving the request), should I start T2? I would expect to receive a CANCEL back from the UA after T2 has fired. If I haven't received this CANCEL I'm going to want to tear the session down so it doesn't waste space in my transaction pool. If this sounds appropriate, what value should I use for T2? If I use the RFC-specified 64*T1 I would expect that there's a possibility of the UA's cancel coming in while or after I have torn the session down. What's a good amount of time to allow the UA to send the CANCEL before just blindly tearing the session down. -Daniel _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
