Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Submitted By: Thomas Gelf (thomas_gelf)
Assigned to: Nobody/Anonymous (nobody)
Summary: engage_media_proxy failes if called after create_dialog
If I correctly understood mediaproxy.c it installs a callback handler __dialog_created, responsible for setting up the other handlers for this dialog (using dlg_api.register_dlgcb).
However, if you called create_dialog() before, "dialog_created" will not be fired again if you are using engage_media_proxy().
Proposed solution: either add a note to current documentation ("...do NOT use create_dialog when using engage_media_proxy...") or find a way to catch this situation in EngageMediaProxy (maybe: if dlg started, immediately register dialog callbacks).
>Comment By: Dan (dan_pascu)
Date: 2009-02-27 12:48
I think that the dialog module should immediately trigger the registered
callback for create dialog, if the dialog was created before that point.
This is the most obvious thing to do, as the code using the dialog module
will not have to be aware of the internal details of the dialog module and
its state, nor will it need to inspect the dialog module to figure out what
to do next.