Sam, Sec 15 of 3261 says
"The caller's UA MAY send a BYE for either confirmed or early dialogs, and the callee's UA MAY send a BYE on confirmed dialogs, but MUST NOT send a BYE on early dialogs." The callee UA may be expecting BYE instead of CANCEL once early dialog is established as a result of RINGING. -Ranga --- sam n <[EMAIL PROTECTED]> wrote: > Hi all, > > Thanks for your prompt replies :-) > > The weird thing is that once i send the CANCEL, i > get the OK response > but the other phone does not stop ringing. After > sending a BYE it > stops ringing, and then remembers to send me back > the 487 Transaction > canceled response, with the Cseq number matching the > CANCEL. > > So for some reason, it doesn't seem to be sending it > back until i try > to terminate the call using BYE, not CANCEL. > > Thus, the call-flow is: > > INVITE (cseq = 1)-------------------------> > > <------------------------ TRYING (cseq = 1) > <------------------------ RINGING (cseq =1) > > CANCEL (cseq = 1)-------------------------> > > <------------------------ OK (cseq = 1) > > <remote phone continues to ring> > > BYE (cseq = 2)-------------------------> > > <------------------------ 487 Transaction canceled > (cseq = 1) > <------------------------ OK (cseq = 2) > > One of the respondents indicated that once the other > phone is RINGING, > i cannot cancel the INVITE. However, RINGING is not > a final response, > so hence it should be able to cancel that request. > > Any ideas? > > Many thanks. > Sam > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > __________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
