Got it .. sorry, my bad. It says regardless of method of request, if a cancel request matches an existing request, UAS will send 200OK response for it, following procedures in 8.2.6. Also to tag of response should match to tag of original request.
Thanks.. On Sep 17, 2013 6:16 PM, "Brett Tate" <br...@broadsoft.com> wrote: > See RFC 3261 section 9.2.**** > > ** ** > > ** ** > > *From:* Arun Arora [mailto:arun.arora....@gmail.com] > *Sent:* Tuesday, September 17, 2013 7:51 AM > *To:* Brett Tate > *Cc:* sip-implementors > *Subject:* RE: [Sip-implementors] About Cancel a Dialog**** > > ** ** > > So what I understand is if there is a use-case where CANCEL can be sent > for other than non-INVITE method, that case should be clearly outlined... > may be a sip extension rfc which specifically standardizes such scenario. > Otherwise if not explicitely mentioned CANCEL should be ignored in case of > non-INVITE requests. > If my understanding is correct then it raises a question that what a UAS > should send in response of CANCEL for a non-INVITE request even if UAS > decides to ignore it?**** > > ** ** > _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
