Hi Partha,
Thank you very much for the clarification.
Regards Vasu.
PS: more details could be found in section 15.
----- Original Message ----- From: <[EMAIL PROTECTED]>
To: "Vasudeva" <[EMAIL PROTECTED]>
Sent: Monday, January 10, 2005 8:35 PM
Subject: Re: [Sip-implementors] CANCELing an INVITE
Hi Vasu,
Please read inline
Regards Partha
"Vasudeva" <[EMAIL PROTECTED]> To <[EMAIL PROTECTED]> 01/10/2005 04:12 cc PM Subject Re: [Sip-implementors] CANCELing an INVITE
Hi,
According to Section 9.1, (refer below)
"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."
The INVITE itself could set the To-Tag in case of re-INVITE. In that case, the CANCEL MUST have the To-Tag as mentioned in section 9.1.
<Partha> CANCEL is not allowed in the case of re-Invite. CANCEL is alllowed only for the INVITE request </Partha> Regards, Vasu.
----- Original Message ----- From: <[EMAIL PROTECTED]> To: "Rohit Sonalkar" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; < [email protected]> Sent: Monday, January 10, 2005 10:50 AM Subject: Re: [Sip-implementors] CANCELing an INVITE
Hi Rohit,
The CANCEL should not have To tag as the CANCEL request must be identical to the correponding INVITE Request as explained in section 9.1.
Thanks Partha
"Rohit Sonalkar"
<[EMAIL PROTECTED]
m> To
Sent by: <[email protected]>
sip-implementors- cc
[EMAIL PROTECTED]
ia.edu Subject
[Sip-implementors] CANCELing an
INVITE
01/10/2005 09:39
AM
Limited
If an INVITE has received a provisional response, should the CANCEL sent now include the tag in the To header that appeared in the provisional response. Section 9 says the To header should match the request being cancelled, so I am not sure.
Thanks.
Rohit
_______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
*********************** HSS-Private *********************** "DISCLAIMER: This message is proprietary to Hughes Software Systemsis(HSS) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what itorintended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering,disclosing the contents of this message. HSS accepts no responsibilityforloss or damage arising from the use of the information transmitted bythisemail including damage from virus."
_______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
*********************** HSS-Private ***********************
"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended solely for the use of the individual to whom it is
addressed. It may contain privileged or confidential information and
should not be circulated or used for any purpose other than for what it is
intended. If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient, you are
notified that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. HSS accepts no responsibility for
loss or damage arising from the use of the information transmitted by this
email including damage from virus."
_______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
