Difference between revisions of "DUM Usages"

From reSIProcate
Jump to navigation Jump to search
(from "how to use dum")
 
(Replaced "Usages are blah, blah, blah" with a definition and pointer to the usages draft)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 +
==Introduction==
 +
When a SIP method establishes a dialog, it also creates an association within the dialog, known as a dialog usage, between the endpoints. This association contains state that is not shared in the dialog such as expiration, authorization, subscription state, or current session state. SIP was originally designed with the implicit assumption that there was only one usage per dialog. However, a dialog can have multiple usages - for example, when a call is transferred using REFER. Although REFER is a straightforward example of multiple usages, it is recommended that multiple usages be avoided when they can be, since they can create complexity that makes processing difficult. For more information on why multiple usages are tricky and how you can minimize their use, see http://www.ietf.org/internet-drafts/draft-ietf-sipping-dialogusage-06.txt.
 +
 +
==DUM Usage Inheritance==
 
[[Image:DUM_Usage_Inheritance.png]]
 
[[Image:DUM_Usage_Inheritance.png]]
* Usages are blah, blah, blah.
+
 
 +
==To Be Documented==
 
* Describe what handles are here.  
 
* Describe what handles are here.  
 
* [[ClientRegistration]]
 
* [[ClientRegistration]]
Line 11: Line 16:
 
* [[Pager]]
 
* [[Pager]]
 
* [[OutOfDialogReq]]
 
* [[OutOfDialogReq]]
 
*DialogSet, Dialog, DialogSetId, DialogId
 
*Base Creator and Creators
 
*Handlers
 
*Merge Request Key
 
*Cancel Map
 
*DUM Message Flow
 
*Destroy Usage - Ref Counted Destroyer (?)
 
*Keep Alive Manager / Network Association
 
*In Memory Registration Database / Registration Persistence Manager
 
*Subscription Persistence Manager
 
*SubscriptionState (?)
 
*UserAuthInfo (?)
 

Latest revision as of 11:45, 22 March 2007

Introduction[edit]

When a SIP method establishes a dialog, it also creates an association within the dialog, known as a dialog usage, between the endpoints. This association contains state that is not shared in the dialog such as expiration, authorization, subscription state, or current session state. SIP was originally designed with the implicit assumption that there was only one usage per dialog. However, a dialog can have multiple usages - for example, when a call is transferred using REFER. Although REFER is a straightforward example of multiple usages, it is recommended that multiple usages be avoided when they can be, since they can create complexity that makes processing difficult. For more information on why multiple usages are tricky and how you can minimize their use, see http://www.ietf.org/internet-drafts/draft-ietf-sipping-dialogusage-06.txt.

DUM Usage Inheritance[edit]

DUM Usage Inheritance.png

To Be Documented[edit]