[sr-dev] new dialog module design: tm trigger for dialog management

[Juha Heinanen]

I aki Baz Castillo writes:

 > However I do know that using "engage_mediaproxy()" function is not
 > possible just to force MediaProxy for certains branches (i.e: those
 > detected as natted). This function is based on dialog module (just one
 > dialog entry is created as we do know). It's like a "dialog flag" so
 > there is no need to invoke mediaproxy for in-dialog requests as the
 > information about using or not mediaproxy belongs to the whole dialog.
 > This of course makes impossible to use mediaproxy just for certain
 > branches.

incorrect. function use_media_proxy() works just fine.  i would not even
dream of using engage_media_proxy(), just because it depends on dialog
module, which (based on the number of bugs fixed) seems to be by far the
buggies module of all modules.

-- juha