Hi Jitendra We can send BYE 4 seconds after the last retransmission of 2xx response as this is the maximum time we wait for the ACK to reach.
Thanks & Regards, Sanjay Dhand -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jitendra Singh Bhadoriya Sent: Thursday, May 08, 2008 3:10 PM To: JEEVANANDHAM KARTHIC KUMAR Cc: sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] 200 OK Retransmission Hi Karthic, I have a doubt here. The retransmission of the 2xx response In case ACK is not received will happen as below 1st 2xx - 0 2nd 2xx - 0.5 sec 3rd 2xx - 1.5 sec 4th 2xx - 3.5 sec 5th 2xx - 7.5 sec 6th 2xx - 11.5 sec 7th 2xx - 15.5 sec 8th 2xx - 19.5 sec 9th 2xx - 23.5 sec 10th 2xx - 27.5 sec 11th 2xx - 31.5 sec If even after 64*T1 (that is 32 seconds) the ACK is not received, the dialog Is confirmed but the session is terminated by sending BYE (as per RFC-3261). But after how many seconds of sending the last 2xx the BYE will be sent. How much time interval would be there between sending last 2xx (sent at 31.5 sec) and the BYE request(sent for session termination). Thanks Jitendra. -----Original Message----- From: JEEVANANDHAM KARTHIC KUMAR [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 3:40 PM To: Jitendra Singh Bhadoriya Cc: sip-implementors@lists.cs.columbia.edu Subject: RE: [Sip-implementors] 200 OK Retransmission Hello Jitendra, I think we can confirm from following section in RFC 3261 13.3.1.4 The INVITE is Accepted The 2xx response is passed to the transport with an interval that starts at T1 seconds and doubles for each retransmission until it reaches T2 seconds (T1 and T2 are defined in Section 17). Response retransmissions cease when an ACK request for the response is received. This is independent of whatever transport protocols are used to send the response. If the server retransmits the 2xx response for 64*T1 seconds without receiving an ACK, the dialog is confirmed, but the session SHOULD be terminated. This is accomplished with a BYE, as described in Section 15. UAC Point of view: 13.2.2.4 2xx Responses ACK MUST be passed to the client transport every time a retransmission of the 2xx final response that triggered the ACK arrives. The UAC core considers the INVITE transaction completed 64*T1 seconds after the reception of the first 2xx response. At this point all the early dialogs that have not transitioned to established dialogs are terminated. Once the INVITE transaction is considered completed by the UAC core, no more new 2xx responses are expected to arrive. thanks, Karthic -----Original Message----- From: Jitendra Singh Bhadoriya [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 3:25 PM To: JEEVANANDHAM KARTHIC KUMAR; sip-implementors@lists.cs.columbia.edu Subject: RE: [Sip-implementors] 200 OK Retransmission Hi karthic, The Timers G and Timer H are used in case the INVITE Server Transaction has received 3xx-6xx response from TU and it has to retransmit these response until it gets an ACK. In the RFC 3261 nowhere it is given that for 200 OK also the Same retransmission process is applicable. Only what it says is - "If, while in the "Proceeding" state, the TU passes a 2xx response to the server transaction, the server transaction MUST pass this response to the transport layer for transmission. It is not retransmitted by the server transaction; retransmissions of 2xx responses are handled by the TU." So can you please let me know from where I can confirm that the same Processing is true for 200 OK also. Regards, Jitendra. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of JEEVANANDHAM KARTHIC KUMAR Sent: Wednesday, May 07, 2008 3:05 PM To: Jitendra Singh Bhadoriya; sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] 200 OK Retransmission Hi, UAS should retransmit 200 OK at the interval of Timer G(initially T1 then 2*T1) up to the timer H (64*T1). Ref RFC 3261: A Table of Timer Values Timer G - INVITE response retransmit interval Timer H - Wait time for ACK receipt Regards, Karthic -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jitendra Singh Bhadoriya Sent: Wednesday, May 07, 2008 2:40 PM To: sip-implementors@lists.cs.columbia.edu Subject: [Sip-implementors] 200 OK Retransmission Hi, When a UAS receives INVITE, it responds with 200 OK. But in case, the UAC does Not sends an ACK for the 200 OK, then how many times the 200 OK is retransmitted and At what interval this re-transmission happens (Assuming non-reliable transport such as UDP). >From RFC-3261 I am only able to find out the following Section : 17.2.1 or RFC - 3261 says "If, while in the "Proceeding" state, the TU passes a 2xx response to the server transaction, the server transaction MUST pass this response to the transport layer for transmission. It is not retransmitted by the server transaction; retransmissions of 2xx responses are handled by the TU." So please tell me how many times the TU will retransmits 2xx for which it has not an ACK. Thanks & Regards, Jitendra _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility forloss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
