Hi, See this thread. http://lists.cs.columbia.edu/pipermail/sip-implementors/2005-May/009288.html >* If not, why the difference between ACK after 2xx and ACK after reject ?? >From RFC 3261 The 2xx response and its ACK receive special treatment. This response is retransmitted only by a UAS, and its ACK generated only by the UAC. This end-to-end treatment is needed so that a caller knows the entire set of users that have accepted the call. Because of this special handling, retransmissions of the 2xx response are handled by the UA core, not the transaction layer. Similarly, generation of the ACK for the 2xx is handled by the UA core. Each proxy along the path merely forwards each 2xx response to INVITE and its corresponding ACK. Regards, Thangarajan. "Isaac Dudy" <[EMAIL PROTECTED] rse.com> To Sent by: <[email protected]> sip-implementors- cc [EMAIL PROTECTED] ia.edu Subject [Sip-implementors] Wait time for ACK after 2xx 07/12/2005 06:43 PM Hi all. RFC 3261 states that it is the responsibility of the transaction layer to wait additional 5 seconds when receiving ACK after reject (3xx-6xx) in order to recognize retransmissions of this ACK. In contrary to ACK after reject, ACK after 2xx is the responsibility of the transaction user. The transaction user waits up to 32 seconds after sending the 2xx for the reception of the ACK. My questions: * What is the behavior after receiving the ACK? Could the transaction just terminate or should it wait additional time to recognize retransmissions of the ACK? * If not, why the difference between ACK after 2xx and ACK after reject ?? Thanks in advance, David Isaac. _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors *********************** FSS-Private *********************** "DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. HSS accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
