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

[jrose]

> On Dec. 22, 2011, 3:07 p.m., jrose wrote:
> > Alright, this looks good.
> 
> jrose wrote:
>     EDIT:  Actually, revoke that.  Missed kpfleming's recent post.
> 
> jrose wrote:
>     Ok, so what kpfleming is suggesting is basically this...
>     Create the search term based on something supplied to mixmonitor via an argument.  Like...
>     
>     MixMonitor(filename.extension,i(name_of_channel_variable))
>     
>     When mixmonitor is created and this option is present, this channel variable will be populated with some uniquely identifying string (at least uniquely identifying for the channel) which you'll need to create with some heuristic... possibly involving the system time that the variable is created or something similar.
>     
>     Then from there you'd just use that as your identifier for stopmixmonitor.