[SIPForum-discussion] hi

[resalath ahamed]

Hi all,

Its very simple,

Invite -> 100 -> 18X -> 200OK  ----- one transction (same branch id)
ACK for 200OK will have different transaction id.

BUT

Invite -> 5XX/4XX/6XX -> ACK  -------- one transaction. (same branch id)

Hope this is clear !!!!!!

regards,
resalath


On 2/9/07, Manpreet Singh <msingh at ibasis.net> wrote:
>
>  ACK to a 2xx reponse to an INVITE transaction is a NEW transaction as is
> treated the same way as it done with any new request inside a dialog. ACK to
> a non 2xx response is not a new transaction but it part of the INVITE
> transaction. Because the ACK to a 2xx is handled by the client transaction,
> it's a new transaction. ACK for a non 2xx response is handled by transaction
> layer, so that's not a new transaction.
>
> ""
> The UAC core MUST generate an ACK request for each 2xx received from
>    the transaction layer.  The header fields of the ACK are constructed
>    in the same way as for any request sent within a dialog (see Section
>    12) with the exception of the CSeq and the header fields related to
>    authentication.  The sequence number of the CSeq header field MUST be
>    the same as the INVITE being acknowledged, but the CSeq method MUST
>    be ACK.  The ACK MUST contain the same credentials as the INVITE.
> ""
>
> ""
> SIP Transaction: A SIP transaction occurs between a client and a
>          server and comprises all messages from the first request sent
>          from the client to the server up to a final (non-1xx) response
>
> RFC 3261            SIP: Session Initiation Protocol           June 2002
>
>          sent from the server to the client.  If the request is INVITE
>          and the final response is a non-2xx, the transaction also
>          includes an ACK to the response.  The ACK for a 2xx response to
>          an INVITE request is a separate transaction.
> ""
>
> A record-route is inserted to force future requests to go via itself and
> the Route header is formed based on record-routes received. So if there are
> 3 proxies on the way between client A and client B and each proxy inserts
> its own record-route for requests from A-->B, all "requests" from B--->A
> will traverse the same path ( B--->P3--->P2--->P1--->A) and B will populate
> stacked Route headers with P3,P2 and P1 in it. This way the intermediate
> proxies will know to send the request out to the downstream proxies.
>
> M
> -----Original Message-----
> From: vinoth [mailto:Vinoth.E at mobax.com <Vinoth.E at mobax.com>]
> Sent: Friday, February 09, 2007 10:57 AM
> To: darshan b n; discussion at sipforum.org
> Subject: Re: [SIPForum-discussion] hi
>
> Hi
>
>      An ACK is not a new transaction.
>
>      It is a part of Invite Transations., and is used only to acknowledge
> the final responses of Invite.
>
>      It reuses the same Branch ID as used in Invite.
>
>
> Regards,
> Vinoth Kumar.
> Mobax Networks, Coimbatore.
>
>
>
>
> ---------- Original Message ----------------------------------
> From: "darshan b n" <bn.darshan at gmail.com>
> Date:  Fri, 9 Feb 2007 15:32:36 +0530
>
> >Hi,
> >i want to know why ACK IS NOT AN TRANSACTION.............
> >I WANT TO know diff between Route and Record-Route................
> >please help me
> >
> >Regards
> >
> >Drshan
> >
> >
> >
> _______________________________________________
> 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
>
> _______________________________________________
> 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/20070209/26935f37/attachment-0002.html>