Re: [reSIProcate] process incoming calls design question - UML seq diagram attached
Hi Justin,
There is some documentation for the stack proper, but little documentation for
DUM.
Your contributions would be/are greatly appreciated, and will inspire others!
We are hosting a wiki at
http://warsaw.sjc.purplecomm.com/wiki/
As you will see, there is an outline there but not yet much content.
A link from SipFoundry.org/reSIProcate would be helpful; who can do this --
Alan?
thanks,
david
Quoting Justin Matthews <justin.matthews@xxxxxxx>:
> 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
>