[reSIProcate] Dum multi-call design

[Scott Godin]

That will probably work - but you won't know the Invite Session Handle on
placed calls until a dialog is created.  I store an array of AppDialog and
AppDialogSet pointers.  This allows you to end/cancel a call if you don't
receive any response from the far end.  You can get at the InviteSession
from these pointers.

 

Check out:
http://warsaw.sjc.purplecomm.com/wiki/index.php?title=Associating_Applicatio
n_Data_with_Dialogs/DialogSets
<http://warsaw.sjc.purplecomm.com/wiki/index.php?title=Associating_Applicati
on_Data_with_Dialogs/DialogSets> 

 

Just be careful to remove references from your array before the Dialogs are
destroyed - since DUM will delete the AppDialog/AppDialogSet objects.

 

  _____  

From: sachin ahire [mailto:sachinahire at hotmail.com] 
Sent: Thursday, March 31, 2005 11:36 AM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] Dum multi-call design

 


Hi,

I want to develop an application based on basiccall.cpp  in the dum/test to
enable sending multiple calls/invites and also an ability to receive
multiple calls.

The way i was going to do it was to have an array of lines that contains a
pointer to the InviteSessionHandler and everytime the app receives a
OnNewsession i grab one of the "unallocated" lines and copy the handle and
use it to keep track of invitesessions. 

Is this a right way to do it or if not, can somebody give me some pointers
as to how it can be done. Thanks.

Sachin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20050331/754f3c41/attachment.htm>