[reSIProcate] Session handle lifecycle question

Scott Godin slgodin at icescape.com
Fri Oct 13 18:52:11 CDT 2006


You can override the AppDialogSet or AppDialog destructor to cleanup your
map.  The AppDialogSet and AppDialog go away when the session does (assuming
there are no outstanding notify subscriptions, from refers).

 

 

 

From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of Kovar,
William (Bill)
Sent: Friday, October 13, 2006 5:30 PM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] Session handle lifecycle question

 

All,

 

Is there a way to know when a session has been 'disconnected' from its
handle, i.e. handle.isValid() == false other then to check for it?? 

 

I stash session handles within my call management logic and had hoped that I
can remove them in onTerminated() but the handle is still valid and
isTerminated() = true. Is there somewhere in the destructor of either
AppDialog or AppDialogSet that I can look to find out if the session is no
longer valid? This way I can clean my calls that this session is a part of.

 

Thanks

 

Bill Kovar

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20061013/7ab6b039/attachment.htm>


More information about the resiprocate-devel mailing list