reSIProcate

Mailing Lists

Source Code

Google Search:



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

Re: [reSIProcate-users] differentiating multiple dialogs

Hi Scott!
I have some problems to understand how the AppDialog concept works. What if I have different kinds of dialogs, e.g. INVITE dialogs and SUBSCRIBE dialog - is it possible to different classes, e.g InvAppDialog class and SubAppDialog Class to support different user data depending on the dialog type?
Further, is it possible to bind user data to a registration and have this user data available in the UAS INVITE session handler? (= how do I map incoming calls to the respective registration?) 

Thanks
Klaus

Am 09.06.2010 18:09, schrieb Scott Godin:

You need to use AppDialogSets - check out:
http://www.resiprocate.org/DUM_Associating_Application_Data_with_DialogSets_and_Dialogs

<http://www.resiprocate.org/DUM_Associating_Application_Data_with_DialogSets_and_Dialogs>The
recon application is good example of how to use this.

Scott

On Wed, Jun 9, 2010 at 11:49 AM, Klaus Darilion
<klaus.mailinglists@xxxxxxxxx <mailto:klaus.mailinglists@xxxxxxxxx>> wrote:

    Hi!

    I wonder what is the best way to identify concurrent dialogs.

    For example the application registers and receives 2 incoming calls
    concurrently. Somehow in my application I have to represent the 2
    calls, and in the inviteHandler I have to correlate the onXXXevent
    to one of the calls. How is this usually done? How should my
    application hold reference to the dialog? Or is there a way to
    associate some "userdata" with a dialog and access the userdata in
    the callback?

    Is there somewhere a sample code which I should read?

    thanks
    Klaus
    _______________________________________________
    resiprocate-users mailing list
    resiprocate-users@xxxxxxxxxxxxxxx
    <mailto:resiprocate-users@xxxxxxxxxxxxxxx>
    List Archive: http://list.resiprocate.org/archive/resiprocate-users/