[SIPForum-discussion] Why CANCEL cannot be in Same trasaction like ACK for Non 2xx response

Vijay Badola Vijay.Badola at onmobile.com
Tue Jan 15 15:50:06 UTC 2013


I think you should not consider only branch parameter  to calculate a SIP transaction because method is also a part of transaction otherwise INVITE transaction and CANCEL transaction would be same. So it is the METHOD that make the difference.
As I said earlier also that ACK method HAS SPECIAL TREATMENT as per Rfc 3261 so you should not compare both.

From: Vijay Kumar [mailto:vj.tech776 at gmail.com]
Sent: Tuesday, January 15, 2013 5:38 PM
To: Vijay Badola
Cc: Arun Viswanathan; Gottfried, Hal F; discussion at sipforum.org
Subject: Re: [SIPForum-discussion] Why CANCEL cannot be in Same trasaction like ACK for Non 2xx response

Same Via/Cseq num(of course methoods are diff) etc
Vijay
On Tue, Jan 15, 2013 at 4:46 PM, Vijay Badola <vijay.badola at onmobile.com<mailto:vijay.badola at onmobile.com>> wrote:
Vijay, How does CANCEL looks similar to ACK for non 2xx of INVITE?



On 01/15/2013 01:11 PM, Vijay Kumar wrote:
Arun
My question is if ACK for non 2xx final reponse which is in same transactions of INVITE.
Why CANCEL which looks similar to ACK for non 2xx final response is in different transaction
(Keeping the of the contents of ACK and CANCEL.Agreeing form RFC lines telling that both INVITE and ACK are in diffrent transaction)
Vijay
On Tue, Jan 15, 2013 at 12:52 PM, Arun Viswanathan <arunviswan at gmail.com<mailto:arunviswan at gmail.com>> wrote:
For transaction RFC 3261 says about singe request, so CANCEL is a new request and hence new transaction

a SIP transaction consists of a single request and any responses to
   that request, which include zero or more provisional responses and
   one or more final responses.

Regards

Arun Viswanathan

On Sat, Jan 12, 2013 at 3:47 AM, Gottfried, Hal F <hal.gottfried at verizon.com<mailto:hal.gottfried at verizon.com>> wrote:
Branch is used to match CANCEL and ACK to the transaction being CANCELed  or ACKed.  It is true that Call-id:CSeq-No or from-tag:CSeq-No may
 also be used but using branch parameter is the most simple approach



Hal F. Gottfried

From: discussion-bounces at sipforum.org<mailto:discussion-bounces at sipforum.org> [mailto:discussion-bounces at sipforum.org<mailto:discussion-bounces at sipforum.org>] On Behalf Of Vijay Badola
Sent: Thursday, January 10, 2013 11:11 PM
To: Vijay Kumar; discussion at sipforum.org<mailto:discussion at sipforum.org>
Subject: Re: [SIPForum-discussion] Why CANCEL cannot be in Same trasaction like ACK for Non 2xx response

Hi Vijay,

This is because as per definition of transaction, "it comprises all messages from the first request sent
from the client to the server up to a final (non-1xx) response sent from the server to the client."

Means a transaction is created by a method since INVITE and CANCEL are different method so they are treated

different transactions.

As for as ACK is concerned it is treated a special message in SIP.



Regards,

Vijay Badola

From: discussion-bounces at sipforum.org<mailto:discussion-bounces at sipforum.org> [mailto:discussion-bounces at sipforum.org] On Behalf Of Vijay Kumar
Sent: Thursday, January 10, 2013 11:52 PM
To: discussion at sipforum.org<mailto:discussion at sipforum.org>
Subject: [SIPForum-discussion] Why CANCEL cannot be in Same trasaction like ACK for Non 2xx response

Hi all
Can any one throw light on this please.

Agreed that as per 3261 INVITE and ACK for 2xx response are in different transaction
Agreed that ACK for NON 2xx response and INVITE are in same transaction

Same Via branch as INVITE,Same Cseq(Only Numeric part Cseq=1 ACK)  in ACK for NON 2xx response .(Hence ACK is for Non 2xx reponse if in same transaction as of INVITE)

BUT
Why not CANCEL be in same transaction as INVITE because of
Same Via branch,Same Cseq(Only Numeric part like Cseq= 1 CANCEL)

(Agreed RFC 3261 says CANCEL and INVITE are different transactions)
Thanks in advance
Vijay

________________________________

DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto.
Thank you - OnMobile Global Limited.

_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
Post to the list at discussion at sipforum.org<mailto:discussion at sipforum.org>



________________________________

DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto.
Thank you - OnMobile Global Limited.


________________________________

DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto.
Thank you - OnMobile Global Limited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20130115/2bafa92d/attachment-0002.html>


More information about the discussion mailing list