Hi Satish , You got your answer but putting RFC 3261 section 9.2 phrase here to conclude this query for others
If the transaction for the original request still exists, the behavior of the UAS on receiving a CANCEL request depends on whether it has already sent a final response for the original request. If it has, the CANCEL request has no effect on the processing of the original request, no effect on any session state, and no effect on the responses generated for the original request. Thanks & regards Ankur Bansal On Fri, Sep 13, 2013 at 4:37 PM, satish agrawal <satish.agr...@gmail.com>wrote: > Thanks Brett for your prompt reply. > > I got the answer of my query in RFC 3261 section 9.2. > > Thanks, > Satish > > > On Fri, Sep 13, 2013 at 4:32 PM, Brett Tate <br...@broadsoft.com> wrote: > > > > Before final ACK if the Stack received CANCEL message > > > from terminal. then it should response with > > > "487 Request Terminated" ? > > > > If your question is about a 487 response to INVITE, the answer is no > since > > you have already sent a final response. > > > > If your question is about a 487 response to CANCEL, the answer is no > since > > your race condition would result in a 200 (or maybe 481) response. > Aspects > > (from an INVITE 2xx perspective) are discussed within RFC 5407 section > > 3.1.2. I assume 200 response is correct while within Completed state; > > however I didn't recheck the RFC 3261 and RFC 6026 state machines > > concerning the topic. > > > > > > > -- > Thanks & Regards > Satish Agrawal > New Delhi-24. > _______________________________________________ > 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
