[asterisk-dev] [Code Review] Allow specifying which MixMonitor to stop

telecos82 reviewboard at asterisk.org
Thu Dec 22 05:15:51 CST 2011

This is an automatically generated e-mail. To reply, visit:

Review request for Asterisk Developers.


Currently, if there are several MixMonitor started on a channel, there is no way to specify which MixMonitor to stop with StopMixMonitor. With this patch we will allow this. One limitation of current implementation was that mixmonitor datastore was not identified with a uid so there was no way to identify a concrete MixMonitor. Furthermore, when retrieving audiohook to dettach from channel, there was no control on which audiohook to dettach, it always got first audiohook found of type mixmonitor_spy_type. With this patch we are identifying MixMonitor datastore by the filename asociated to it, and dettaching the concrete audiohook contained on datastore. Furthermore a new CLI command "mixmonitor list <channel_name>" to help querying active mixmonitors on a channel.

This addresses bug ASTERISK-19096.


  http://svn.asterisk.org/svn/asterisk/trunk/apps/app_mixmonitor.c 348737 

Diff: https://reviewboard.asterisk.org/r/1643/diff




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20111222/6ca184eb/attachment.htm>

More information about the asterisk-dev mailing list