[SIPForum-discussion] Transaction in Call Hold & Call UnHold - SIP

haluk yavuz haluk.yavuz at gmail.com
Mon Jun 28 14:36:02 UTC 2010


RFC3261 Page 122

   A stateless proxy does not contain a client or server transaction.
   The transaction exists between the UA or stateful proxy on one side,
   and the UA or stateful proxy on the other side.  As far as SIP
   transactions are concerned, stateless proxies are effectively
   transparent.  The purpose of the client transaction is to receive a
   request from the element in which the client is embedded (call this
   element the "Transaction User" or TU; it can be a UA or a stateful
   proxy), and reliably deliver the request to a server transaction.

If the proxy in the middle is stateful then there are 14 transactions, o/w
there 7.

regards.

On Sun, Jun 27, 2010 at 9:51 AM, mahendra kedia <mahendrakedia at gmail.com>wrote:

> Hi All,
>
> there are 7 transaction as per the RFC3261 per side, so if u are loking to
> complete call flow there are 14 transaction in the attachment.
>
> Regards,
> Mahendra Kedia
>
> On Fri, Jun 25, 2010 at 5:07 PM, SIP Babie <sipbabie at gmail.com> wrote:
>
>> Hi All,
>>
>> Please help me to find the number of transactions in attached Call Hold-
>> Call Unhold SIP call flow.
>>
>> Regards,
>> sipbabie
>>
>> _______________________________________________
>> 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
>
>


-- 
Haluk YAVUZ
İstanbul, TURKEY
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20100628/79444a0b/attachment-0002.html>


More information about the discussion mailing list