CANCEL with/without 1xx To tag

I have not seen anywhere confirmation one way or another on
this topic.


F1 A ----- INVITE -------> B
F2 A <----- 183 ------------ B
F3 A ----- CANCEL ----> B

F1 contains From tag.
F2 contains From tag and To tag

The question is: Is the F3 CANCEL required to send both From
and To tags?

RFC 3261 Section 9.1 states...

The following procedures are used to construct a CANCEL
request. The
Request-URI, Call-ID, To, the numeric part of CSeq, and From
header
fields in the CANCEL request MUST be identical to those in
the
request being cancelled, including tags. 
Thanks.

Del Stevens
CopperCom
<www.coppercom.com>


_______________________________________________
Sip-implementors mailing list
Sip-implementorscs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors

Hi Del,

You are right as per section 9.1 recommendation the To
Header should be
be identical to initial INVITE. This can also be seen in
example section
of RFC-3665 Page 70

Section 12.2.1.1 recommendation in my opinion is applicable
for all
other requests with in a dialog ( early/confirmed ).

Regards,

Indresh K Singh

-----Original Message-----
From: sip-implementors-bouncescs.columbia.edu
[mailto:sip-implementors-bouncescs.columbia.edu] On Behalf
Of Del
Stevens
Sent: Monday, April 02, 2007 10:02 AM
To: sip-implementorscs.columbia.edu
Subject: [Sip-implementors] CANCEL with/without 1xx To tag

I have not seen anywhere confirmation one way or another on
this topic.


F1 A ----- INVITE -------> B
F2 A <----- 183 ------------ B
F3 A ----- CANCEL ----> B

F1 contains From tag.
F2 contains From tag and To tag

The question is: Is the F3 CANCEL required to send both From
and To
tags?

RFC 3261 Section 9.1 states...

The following procedures are used to construct a CANCEL
request. The
Request-URI, Call-ID, To, the numeric part of CSeq, and From
header
fields in the CANCEL request MUST be identical to those in
the
request being cancelled, including tags. 
Thanks.

Del Stevens
CopperCom
<www.coppercom.com>


_______________________________________________
Sip-implementors mailing list
Sip-implementorscs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors

_______________________________________________
Sip-implementors mailing list
Sip-implementorscs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors

Section 9.2 states that server applies the transaction
matching rules of
17.2.3 for cancelling a transaction. 
Section 17.2.3 states that "a request is matched to a
transaction if the
Request-URI, To tag, ... match those of the request that
***created the
transaction*** " 

In the message sequence below, since F1 did not have To-tag,
F3 must not
have To-tag. 

Regards,
Ramakrishna 

-----Original Message-----
From: sip-implementors-bouncescs.columbia.edu
[mailto:sip-implementors-bouncescs.columbia.edu] On Behalf
Of Del
Stevens
Sent: Monday, April 02, 2007 7:32 PM
To: sip-implementorscs.columbia.edu
Subject: [Sip-implementors] CANCEL with/without 1xx To tag

I have not seen anywhere confirmation one way or another on
this topic.


F1 A ----- INVITE -------> B
F2 A <----- 183 ------------ B
F3 A ----- CANCEL ----> B

F1 contains From tag.
F2 contains From tag and To tag

The question is: Is the F3 CANCEL required to send both From
and To
tags?

RFC 3261 Section 9.1 states...

The following procedures are used to construct a CANCEL
request. The
Request-URI, Call-ID, To, the numeric part of CSeq, and From
header
fields in the CANCEL request MUST be identical to those in
the request
being cancelled, including tags. 
Thanks.

Del Stevens
CopperCom
<www.coppercom.com>


_______________________________________________
Sip-implementors mailing list
Sip-implementorscs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors


The information contained in this electronic message and any
attachments to this message are intended for the exclusive
use of the addressee(s) and may contain proprietary,
confidential or privileged information. If you are not the
intended recipient, you should not disseminate, distribute
or copy this e-mail. Please notify the sender immediately
and destroy all copies of this message and any attachments.


WARNING: Computer viruses can be transmitted via email. The
recipient should check this email and any attachments for
the presence of viruses. The company accepts no liability
for any damage caused by any virus transmitted by this
email.
 
www.wipro.com

_______________________________________________
Sip-implementors mailing list
Sip-implementorscs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors