| < Previous by Date | Date Index | Next by Date > |
| Thread Index |
|
One stack and one dum should be all you
need. Check out: http://wiki.resiprocate.org/wiki/index.php?title=DUM_Associating_Application_Data_with_DialogSets_and_Dialogs Scott From:
resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Kovar, William (Bill) I'm looking to build a call controller on top of DUM that
will originate and terminate signaling for various UAs and then use a B2B to do
media shuffling between incoming calls and arbitrary endpoints. I'm trying to understand what is the best way to manage app
level requests (external controller) to DUM to manipulate multiple sessions
(dialogs). I'm looking to use 1 SipStack object for the whole thing (low call
volume) but I'm not sure how many DUMs I need. I'm assuming only one (UAC side)
but I'm not following how an external request with a tag that maps to a
dialog-id can be used to send the SIP msg out correctly, i.e. how to map to the
correct dialog. Apparently I'm missing something.... Any insights?? Bill Kovar |