Section 9.2 of RFC3261 answers this question If the UAS did not find a matching transaction for the CANCEL according to the procedure above, it SHOULD respond to the CANCEL with a 481 (Call Leg/Transaction Does Not Exist).
On Mon, Jun 16, 2008 at 7:01 PM, Suganya D <[EMAIL PROTECTED]> wrote: > Hi, > > The following clarification is needed regarding processing of a CANCEL > message at UAS end: > > When the CANCEL request contains a CSeq number that is not the same as > the INVITE request it is trying to cancel, what is the appropriate > error message to be sent to the UAC? > > Kindly provide your views. > Thank You. > > Regards, > Suganya > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
