Please elaborate your point, since I got a bit confused from your answer. Do you mean 'INVITE transaction' here, since ACK anyways doesn't form its part (incase of a 2xx response)? Also, 2xx terminates the server transaction and subsequent retransmissions are then handled by TU (or UAS to be precise).
Thus, Is it wrong to infer that the 'peer-is-alive' when we get a 2xx retransmission of INVITE? **************************************************************************** *********** This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! -----Original Message----- From: Iñaki Baz Castillo [mailto:[email protected]] Sent: Thursday, July 01, 2010 12:27 AM To: Vikram Chhibber Cc: Harbhanu; [email protected] Subject: Re: [Sip-implementors] Retrans 2xx handilng - RFC-4028 2010/6/30 Vikram Chhibber <[email protected]>: > 2. Handling retransmissions of 2xx(INVITE) - > Should we restart session timer here or not? No. When a transaction server (in a proxy or in an UAS) receives a request retransmission it must re-send the last response. When a transaction client (in a proxy or in an UAC) receives a retransmission of a final response for an INVITE it must re-send the ACK. That's all, no more actions must be triggered. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
