RE: [reSIProcate] shutdown stack and DUM.
You should wait until the dum shutdown handler is called before shutting
down the stack thread. This will require you to end all active invite
sessions, registrations, etc first.
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-
> devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of papatel@xxxxxxxxxx
> Sent: Friday, December 23, 2005 3:17 AM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [reSIProcate] shutdown stack and DUM.
>
> Hi All,
>
> I have got some memory leaks after shutdown DUM and stack
regarding
> timers
> and for added transport.
>
> Application have one Stack Thread which is responsible for
process
> DUM as
> wall as SipStack.
>
> //initialization.
> - Stack Thread derived from ThreadIf class of reSIP
>
> p_clientDum = new DialogUsageManager(*p_stack);
> p_mStackThread = new CSIPStackThread(p_stack,p_clientDum);
> // additional code
> p_mStackThread->run(); //responsible for process DUM and
SipStack
>
>
> //shutdown
>
> p_clientDum->shutdown(&ShutdownHandler);
> //
>
> p_mStackThread->shutdown();
> p_mStackThread->join();
>
>
>
> is it right...?
> have any reliable way then this..?
>
> Thanks & Regards,
> Parag Patel
>
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel