RE: [reSIProcate] Still no answers yet...
John,
as I mentioned before "an AppDialogSet is equivalent to
a call". It is created when a call starts. When you
initiate the call you create the AppDialogSet yourself
and pass it to the Dum->makeInviteSession method.
For an incoming call the AppDialogSet is created by
the stack. If you work with a derived AppDialogSet
object you need to create an AppDialogSetFactory and
pass it to dum. As the name (factory) suggests this
will enable dum to create your derived AppDialogSet
object instead of the default one.
An AppDialogSet can consist of several AppDialogs
(Request & Response but can also be more than one roundtrip).
Hence it's called ..Set.
Best regards,
Matthias
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx]On
> Behalf Of John
> Draper
> Sent: Mittwoch, 12. Oktober 2005 08:51
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [reSIProcate] Still no answers yet...
>
>
> Hi,
>
> Still trying to understand the relationship of AppDialog,
> AppDialogSet,
> and AppDialogFactory.
> I posted these questions before, haven't gotten any answers
> yet, and I
> think I may not
> be explaining my problem very well, so I'm here for a 2nd try.
>
> Here is my conception of how I think it works... it is
> incomplete, just
> as the docs are incomplete,
> and I just need to fill in the blanks...
>
> I'm defining the Client side as being a SipPhone, with the
> understanding that the
> Sip Phone can also be considered the Server side when one is
> waiting for
> a call.
>
> I'm defining the Server side as being a SIP Server, Proxy, or the
> receiving end of
> a "Phone call". Ok, with that out of the way... I continue...
>
> The number after the object indicates a specific instance of
> that object.
> I'm showing two connected SIP Users (who are not necessarily
> talking to
> each other), but just want to show how many AppDialogSets there are,
> and how they are connected.
>
> CLIENT (SipPhone)
> SERVER
> (Proxy)
> ===================
> ================
>
> AppDialogSet1
> AppDialogSet
> AppDialog1 <-----------Caller 1 -------------> AppDialog
>
> AppDialogSet2
> AppDialog2 <------------Caller 2 ------------> AppDialog
>
>
> On the client side, Am I to assume that each connected client
> would have just ONE and ONLY ONE AppDialogSet and AppDialog
> (as shown above), IE:
>
> AppDialogSet (only one of these)
> AppDialog (one of these also)
>
> But on the server side, I would presume there would be a single
> DialogSet, but there would be more then one AppDialog, one
> for each connected client, is that right? Is that how it's
> designed?
>
> AppDialogSet ----- I presume the word "Set" means it can own
> more then one dialog.
> AppDialog1 ----- connected to user1
> AppDialog2 ----- connected to user2
> AppDialog3 ----- connected to user3
>
> My next question is the lifetime of an AppDialogSet. IE:
> When is it created, and how long does it live...?
>
> Obviously the BasicCall program is not and cannot give me
> this information because in this example the lifetime is
> all contained within the "main()" that runs it... IE: It lives
> only the lifetime it has until "main()" exits... Obviously,
> no REAL SIP program will run this way - (A really poor
> example of how to show us this usage - I might add).
>
> Do I create an AppDialogSet/AppDialog in my Initialization
> phase? Or is it created and used ONLY during the INVITE
> phase, and if so, then when is it ditched?... would it be deleted
> when the call is connected, or stay around until the call is
> completed, or stay around until the Application terminates?
>
> Anyway - this is the missing link keeping me from designing
> this properly. I sure wish someone would set me straight.
> The documentation clearly does not explain this very well.
>
> John
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>