Re: [reSIProcate-users] Lifetime of AppDialog

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

The AppDialogSet should always be available as long as the InviteSession/DialogSet is still around - thus it should always be available for all InviteSession handler callbacks.

Scott

On Wed, May 26, 2010 at 8:03 AM, SCG2 <sgregor1@xxxxxxxxxxxxx> wrote:

Hi,

 

I have a piece of application state (my local RTP port number I have chosen from a pool I maintain) that I add when making a call and want access to when a call terminates.

 

To do this I derived from AppDialogSet, and hooked an instantiatino of that derivation in during call setup.

 

I assumed that during my InviteSessionHandler::onTerminated() I would still allow me access to my derived AppDialogSet object to get my application state from, but during tests it seems like my

 

appDialogSet* ads = dynamic_cast<appDialogSet*>(uacADS.get());

 

returns null, suggesting the app dialog set has already gone.

 

Is this correct and if so, is there another way I can store / retrieve call-based state data from the dum framework?

 

Thanks,

Simon.

 

 

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/