[asterisk-users] MixMonitor creating file on non-bridged calls with option b

[Jonathan Rose]

Ikka.vertika wrote:
> From: "Ikka.vertika" <ikka.vertika at mitrakreasindo.com>
> To: "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users at lists.digium.com>
> Sent: Friday, August 3, 2012 9:20:03 AM
> Subject: Re: [asterisk-users] MixMonitor creating file on non-bridged calls with option b
> 
> 
> I have read an earlier posts in this forum that said it was a bug in
> asterisk 10.4 and there's a patch to fix it. So it already reported
> as bug.
> 
> 
> But i use asterisk 10.61 and that bug is still there, unfixed.
> 
> 
> We upgrade to the newest version for the new feature that we can use,
> and also hoping for fixed bugs. But we absolutly not hoping to get
> an extra job fixiing the bug that has supposely has been fix...

Mailing lists (and particularly the asterisk-users list) aren't the proper
place for bugs to be reported. If an issue doesn't get reported to JIRA, it
doesn't go into the evaluation process and at the end of the day, developers
are less likely to notice them and even more unlikely to be assigned to them.

I don't doubt that someone noticed the topic and created a patch for it, but
that doesn't mean the patch was applied to any build in SVN. In fact, our
license agreement for writing patches can't be verified if the patch isn't
uploaded to JIRA (and maybe reviewboard I think). Without that we can't even
legally use the patch.

Thorben Jensen <info at thorben.dk> wrote:
> Hi Jonathan,
> 
> If I set the MixMonitor option on a queue, it will not create an zero
> length file if the call is not bridged, and I just assumed it would
> be the case with option b.
> 
> 
> I have set the fileformat to raw, but if I set it to wav it will
> create a 64 byte file.
> 
> 
> Off course I can delete the files in a script, but I thought I was
> doing something wrong.
> 
> I have not made a bug report.
> 
> Regards
> Thorben

That's totally different. When you invoke MixMonitor before a call, you
are setting up MixMonitor immediately. The call itself is incidental to
that operation. When you use the MixMonitor option with Queue, the Queue
Application is responsible for starting MixMonitor, so it won't start
the MixMonitor until the call is starting.

What is going into the empty wav file by the way is a header describing the
contents of the file... I'm not an expert on the format, but I would assume
it would be things like sample rate, number of channels, etc.
For all Asterisk recordings through MixMonitor, this should be the same, so
you can use that assumption for creating your deletion script as well. There
are probably also utilities available which could be used to read the length
of a wav file so that you can delete them based on that.

If you think it's really a problem though, feel free to submit a JIRA report.

--
Jonathan R. Rose
Digium, Inc. | Software Engineer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
direct +1 256 428 6139 

Check us out at: http://digium.com & http://asterisk.org