As a general rule, CANCEL should be send to abort transactions which are not completed automatically which is INVITE. So you should send CANCEL fro INVITE. You identity the the matching pending transaction by using top most via header's branch and cseq. Thus if CANCEL is for INVITE transaction, it will have same value of cseq and top most via branch as that for INVITE. And of course, both INVITE and UPDATE have different branch values as they are independent transactions.
On Fri, Apr 11, 2008 at 12:19 PM, JEEVANANDHAM KARTHIC KUMAR <[EMAIL PROTECTED]> wrote: > Hello, > > I have confusion to cancel the UPDATE request and INVITE. > > Please consider the following scenario. > > > UAC UAS > ------------INVITE(SDP)-------> > > <-----------100 Trying-------- > > <-----------183 ( SDP))------- > > ------------PRACK------------------> > > <------------200 OK(PRACK)----- > > --------------UPDATE(SDP)-------> > > Now UAC want to terminate the session. What message UAC Should send to > UAS? > one CANCEL message is enough or It should send CANCEL for UPDATE and > then CANCEL for INVITE. > > In UAS side, > If UAS receive CANCEL request, how it will identify whether the CANCEL > for INVITE or UPDATE. > > the same problem may happen for cancelling PRACK also. > > Could you please give your view on this. > > Reagrds, > karthic kumar J > > > > _______________________________________________ > 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
