RE: [reSIProcate] process incoming calls design question - UML seqdiagram attached
You may want to have a look at the AppDialog and AppDialogSet objects. A
quick sample of their use is in BasicCall.cxx. You can override with your
own derived class and store pointers to these objects in your app.
-----Original Message-----
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Justin
Matthews
Sent: Saturday, January 22, 2005 3:10 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] process incoming calls design question - UML
seqdiagram attached
Hello,
I have a question on how to use the dum. After handling the callbacks with
my InviteSessionHandler derived class, I would like to store a minimal
amount of information so that I can get the appropriate InviteSession for a
call at a later time. For example, when onNewSession is called I need to
asynchronously pass the information about the new call to my apps internal
system which will eventually call InviteSession::provisional and then
InviteSession::send. How would my internal system get the appropriate
InviteSession? What is the best way to do this? Simply store the
ServerInviteSessionHandle passed into my InviteSessionHandler? Ideally I
would not like to keep track of dum data objects such as the handle. Is
there a way to get a reference to the correct InviteSessionHandle using
parts of the message (callid, to, from)?
Also, I will be doing at least a few more UML diagrams such as the one
attached. Please let me know if it is incorrect. Being a newbie to the
system I find this is the best way for me to jump on the learning curve.
Are similar docs being developed right now for the dum? I am willing to
continue to post my docs to this thread and/or be educated on the current
documentation plan to help in generating similar docs for the project.
Thanks,
-Justin