[reSIProcate] Session handle lifecycle question

[Scott Godin]

AppDialog::getInviteSession()


________________________________

From: Kovar, William (Bill) [mailto:bkovar at avaya.com]
Sent: Mon 10/16/2006 6:18 PM
To: Scott Godin; resiprocate-devel at list.sipfoundry.org
Subject: RE: [reSIProcate] Session handle lifecycle question


Scott,
 
Yes I know about the destruction part, but I can't seem to figure out how to get to the session. Can you enlighten me as to the method call to be used in the destructor of AppDialog to get the session handle (or session)?

________________________________

From: Scott Godin [mailto:slgodin at icescape.com] 
Sent: Friday, October 13, 2006 7:52 PM
To: Kovar, William (Bill); resiprocate-devel at list.sipfoundry.org
Subject: RE: [reSIProcate] Session handle lifecycle question



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/20061016/71513ebe/attachment.htm>