[asterisk-dev] res_monitor information

[Russell Bryant]

On 02/17/2010 02:36 AM, Kirill 'Big K' Katsnelson wrote:
> On 100216 1213, Russell Bryant wrote:
>> [...]I would like to note that Monitor() is mostly just there for
>> legacy purposes. Unless you have a specific need for Monitor(), I
>> would strongly suggest using MixMonitor(), instead.
>
> Just my 2c. In our application, Monitor() is a lifesaver. We are
> archiving uncompressed G.711u, merging them into 2-channel files without
> mixing. As we are running fully automated, unmonitored AI agents, and
> use audio bits of real calls to track down speech understanding
> problems, and for regression testing. I'd certainly feel sorry to see
> the feature go!

I absolutely would not be in favor of removing it anytime soon.  It's 
just that the code behind MixMonitor is a bit more ... "modern", and I'm 
more comfortable with it.

Monitor() will never go away for backwards compatibility purposes.  The 
underlying implementation may change someday to not have two completely 
different implementations of call monitoring, but all of the interfaces 
and behavior would remain.

-- 
Russell Bryant
Digium, Inc. | Engineering Manager, Open Source Software
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
www.digium.com -=- www.asterisk.org -=- blogs.asterisk.org