< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate-users] DUM usage


I just created the following wiki page on this subject:

http://www.resiprocate.org/DUM_Application_Shutdown

 

 

From: resiprocate-users-bounces@xxxxxxxxxxxxxxx [mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxx] On Behalf Of Mykhailo Parfeniuk
Sent: Friday, November 16, 2007 4:06 AM
To: resiprocate-users@xxxxxxxxxxxxxxx
Subject: [reSIProcate-users] DUM usage

 

Hi Scott.
I have some questions about DUM usage. I am writing softphone, that should support multiple login/logout
with different users. At moment I am tryint to implement it in such manner: on login request I create DUM 
and send REGISTER an logout I am trying to properly shutdown DUM. Here problems begin. As I understand
DUM does not wait until all handles are destroyed and it just check if all handles were destroyed
and if so then request stack to unregister TransactionUser. Otherwise it do nothing. Am I right?

Should I manually track moment at which
all handles are destroyed?

 

[Scott] This is what the ShutdownHandler callback is for.


There are also some other problem. ClientSubcription end() function does not actually terminate it. It just send
SUBCRIBE with expires 0 and on response does  not terminate subscription. 

 

[Scott] The final notify with subscription state Terminated should be ending the subscription.

 

As I understand it treat successfull response on such 
request as any other successfull response. How can I properly destroy subscriptions?
May be to achieve my goals I should use DUM in some other way?
Thanks for advance.