[reSIProcate-users] Separate DUM UAC/UAS?

["Brody, Chris - Acision" <chris.brody@xxxxxxxxxxx>]

Hello,

Another thing we would like to do is use different DialogUsageManager instance 
for a UAC function and UAS function. Apparently, it is possible to connect 
multiple DUM instances to a single SipStack instance, but to coordinate the 
message processing for the two DUM instances is a bit of a challenge given a 
standard select loop such as the following:
        for (/*...*/;;) {
                fdset.reset();

                mStack->buildFdSet (fdset);

                int err = fdset.selectMilliSeconds(250);
                (error check code is omitted)

                mStack->process (fdset);
                while(mDumUas->process()) ;
        }

Any suggestions and/or pointers?

P.S. In general we do not find the DUM to be very well documented, especially 
in the areas of memory ownership such as AppDialog, AppDialogSet, etc. We will 
probably have to make some better documentation for ourselves and have just 
gotten approval to contribute back to the reSIProcate community.

Thanks,
Chris

This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you.