radhakrishna wrote:
> What is the difference between Dialog Stateful proxy and Call Stateful
> proxy?

I used these terms informally. But definitions should follow directly 
from the names:

- a dialog stateful proxy will maintain dialog state, which consists
   primarily of callid, cseq, local and remote targets (contacts),
   and route set.

- a call stateful proxy, in addition to being dialog stateful, will
   maintain call state, which will be details about offer/answer
   status and current media streams.

> Can you pls add info to Registration Stateful proxy also?

- by registration stateful I meant something a proxy that keeps some
   kind of information about registrations it has processed. For
   instance IMS expects its P-CSCFs to do this. They remember things
   like the Path negotiated in the registration.

> RadhaKrishna. Manikonda
> Software Engineer
> 3rd Floor, Ext: 1546
> Leela Palace, Airport Road
> Bangalore: 560008
> Ph: 080-41781770
> 91-9986003454
>  
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Paul Kyzivat
> Sent: Tuesday, February 28, 2006 6:46 PM
> To: [EMAIL PROTECTED]
> Cc: [email protected]
> Subject: Re: [Sip-implementors] Difference between a BBUA and stateful proxy
> 
> 
> 
> [EMAIL PROTECTED] wrote:
> 
>>Can somebody tell me the exact difference between a BBUA and a stateful
>>proxy?
> 
> 
> Whether it is stateful or not, a proxy must obey certain rules (in 3261) 
> about what it may, and may not, do. A UA has different, less restrictive 
> rules. A B2BUA *can* function in a manner similar to that of a proxy, in 
> that messages coming in one side typically result in a related message 
> going out the other side. But because it is a UA to can do things a 
> proxy is not permitted to do.
> 
> For instance, a node could act exactly like a proxy, but store dialog 
> state. (Hence be a "stateful proxy".) At some point it might use that 
> state to enable it to send a BYE, terminating the dialog. At the moment 
> it does that it ceases to be a proxy and becomes a B2BUA.
> 
> Note that neither B2BUA nor Stateful Proxy are very precise terms. 
> B2BUAs can be very much like proxies, as above. But there are other 
> kinds of B2BUAs, such as conference foci and 3pcc controllers, that bear 
> little resemblance to a proxy. Stateful proxies vary depending on how 
> much state they contain. At the simplest level there are stateless 
> proxies, transaction stateful proxies, dialog stateful proxies, call 
> stateful proxies, and registration stateful proxies.
> 
>       Paul
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> 
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to