I pasted the significant RFC section inline
Jitendra Singh Bhadoriya wrote:
> 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.
>
13.3.1.4 The INVITE is Accepted
[snipped]
Once the response has been constructed, it is passed to the INVITE
server transaction. Note, however, that the INVITE server
transaction will be destroyed as soon as it receives this final
response and passes it to the transport. Therefore, it is necessary
to periodically pass the response directly to the transport until the
ACK arrives. 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.
Rosenberg, et. al. Standards Track [Page 85]
RFC 3261 SIP: Session Initiation Protocol June 2002
Since 2xx is retransmitted end-to-end, there may be hops between
UAS and UAC that are UDP. To ensure reliable delivery across
these hops, the response is retransmitted periodically even if the
transport at the UAS is reliable.
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.
> 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
>
>
>
>
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
