Thanks Brett, Gary and Attila for sharing your views. If the reliability is the only objective for retranmission, then in my scenario UAC should not retransmit INVITE as it has received 180 and more so it has experienced PRACK-200 successfully. Thanks again to Gary for pointing out RFC 3581. I was looking for such a reference.
I feel that SIP entities in my case are following RFC 3581. It would have been better if RFC 3581 suggest OPTION/UPDATE etc. rather than INVITE to keep pinhole alive. --- Attila Sipos <[EMAIL PROTECTED]> wrote: > Hi Brett, > > Yep, I think you're right. > > Cheers, > Attila > > PS But I really wish the UAC would cease > retransmitting its INVITEs. > I'm sure there's a rule about that somewhere ;-) > > > -----Original Message----- > From: Brett Tate [mailto:[EMAIL PROTECTED] > Sent: Tue 12/12/2006 19:05 > To: Attila Sipos; Siddhartha Bhakta; > [email protected] > Cc: > Subject: RE: [Sip-implementors] Retransmitted > INVITE after PRACK-200OKexchange > > > > > I think that the right way to respond is to > resend > > the last provisional response. > > Hi Attila, > > The main reason that I think the UAS should not > respond is because of > the following text from rfc3262 section 3. My > interpretation assumes > "SHOULD cease retransmissions" applies to both > those desiring PRACK and > those triggered by retry of INVITE. > > " Retransmissions of the reliable provisional > response cease when a > matching PRACK is received by the UA core." > > " If the PRACK does match an unacknowledged > reliable provisional > response, it MUST be responded to with a 2xx > response. The UAS can be > certain at this point that the provisional response > has been received in > order. It SHOULD cease retransmissions of the > reliable provisional > response, and MUST remove it from the list of > unacknowledged provisional > responses." > > > __________________________________________________________ Yahoo! India Answers: Share what you know. Learn something new http://in.answers.yahoo.com/ _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
