[SIPForum-discussion] transaction...

[Robert Sparks]

Please also be aware of
http://tools.ietf.org/html/draft-sparks-sip-invfix

RjS

On Aug 17, 2007, at 3:29 AM, <alexzhang at gdnt.com.cn> wrote:

> What you said is not the root cause. Please refer to the RFC3261  
> -17. Transactions:
>
>       The reason for this separation is rooted in the importance of
>       delivering all 200 (OK) responses to an INVITE to the UAC.  To
>       deliver them all to the UAC, the UAS alone takes responsibility
>       for retransmitting them (see Section 13.3.1.4), and the UAC  
> alone
>       takes responsibility for acknowledging them with ACK (see  
> Section
>       13.2.2.4).  Since this ACK is retransmitted only by the UAC,  
> it is
>       effectively considered its own transaction.
>
> And in my opinion, when the transaction layer of the UAC/UAS will  
> be destroyed as soon as the 200 OK(Invite) is received. At this  
> time, the UAC and UAS already know the location of each other. It  
> means that the stateless proxy between them is not used any more.  
> The ACK, which is created in a new transaction, will be transmitted  
> from UAC to UAS directly.
> Thanks,
> Alex
> 6-554-8782
>
>
>
> From: discussion-bounces at sipforum.org [mailto:discussion- 
> bounces at sipforum.org] On Behalf Of Donald Lee
> Sent: Friday, August 17, 2007 3:05 PM
> To: Devanand Kumar
> Cc: discussion at sipforum.org
> Subject: Re: [SIPForum-discussion] transaction...
>
> because it has unique Via branch-ID, which identifying the  
> transaction.
>
>
> On 8/17/07, Devanand Kumar <devanand at techmahindra.com> wrote:
>
>
> Hi ALL,
>
>
>
> Please tell me the reason that why The ACK for a 2xx response to an  
> INVITE request is a separate transaction.
>
>
>
> Thanks and Regards,
>
> Devanand Kumar
>
>
>
> ====================================================================== 
> ======================================================
>
> Disclaimer:
>
> This message and the information contained herein is proprietary  
> and confidential and subject to the Tech Mahindra policy statement,  
> you may review the policy at http://www.techmahindra.com/ 
> Disclaimer.html externally and http://tim.techmahindra.com/ 
> Disclaimer.html internally within Tech Mahindra.
>
> ====================================================================== 
> ======================================================
>
> _______________________________________________
> 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
>
>
>
>
> -- 
> BR
> Donald
> _______________________________________________
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20070817/0c011fc9/attachment-0002.html>