[asterisk-bugs] [Asterisk 0010477]: MixMonitor Splits recordings

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10477 
====================================================================== 
Reported By:                limetv
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10477
Category:                   Applications/app_mixmonitor
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:            1.4.10  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-16-2007 19:02 CDT
Last Modified:              08-22-2007 00:17 CDT
====================================================================== 
Summary:                    MixMonitor Splits recordings
Description: 
We are having an issue where MixMonitor is sometimes splitting recordings
into two files, the first being only  a few seconds long and the rest of
the recording is in a separate file.

We are using meetme conferences where one participant has triggered a
Mixmonitor recording before entering the room.
====================================================================== 

---------------------------------------------------------------------- 
 limetv - 08-22-07 00:17  
---------------------------------------------------------------------- 
We could give you this but I'm not sure how helpful this would be as we
have no way of knowing when this issue is going to happen and we make
thousands and thousands of calls a day.

I'm afraid it would be hundreds of megs of irrelevant data.

Can you maybe suggest where we look for this?

Is this a core asterisk problem that we have no control over, or could
this be a problem with our dial plans.

We did not seem to have this issue before moving to Asterisk 1.4.9 however
I can not be certain that this upgrade was the problem either.

Any suggestions where to look or if you are aware of anyone else having
this issue would be appreciated.

We have checked our code over and over, and the dial plans we use and can
not see any issues at all, so we are lost as to what this would be
happening from. Hence our support ticket as a last resort for any help or
advise. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-22-07 00:17  limetv         Note Added: 0069224                          
======================================================================