[asterisk-bugs] [Asterisk 0017873]: Record audio channels gets out of sync

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17873 
====================================================================== 
Reported By:                aureliors123
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17873
Category:                   Applications/app_mixmonitor
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.2.10 
JIRA:                       SWP-2320 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-08-16 22:16 CDT
Last Modified:              2011-05-09 10:30 CDT
====================================================================== 
Summary:                    Record audio channels gets out of sync
Description: 
When recording with mixmonitor, some record files channels gets out of
sync.
The scenario was:
- Medium call traffic: More than 60 and less than 120 concurrent calls.
- All calls are recorded
- Codec: Alaw
- Record File format: WAV GSM
- Processor load: Never more than 50%
- Asterisk Version: 1.6.2.10 (also happened in older versions, since
1.4.19)
- SO Debian 5.0.3 - 2.6.26-2-686
====================================================================== 

---------------------------------------------------------------------- 
 (0134667) iasgoscouk (reporter) - 2011-05-09 10:30
 https://issues.asterisk.org/view.php?id=17873#c134667 
---------------------------------------------------------------------- 
thanks @dvossel

I will explain my issue, but as you say there may be a number of different
issues around mixmonitor and 'sync' issues.

I currently have the problem on all incoming Dahdi calls, at present,
which lasts for a few weeks and then goes away;   as currently on the
latest svn trunk ( every few days ), this issue is still present.  I
reverted back to the latest 1.8 release and the issue is still there.  I
have all timing modules loaded, and during periods of having the issue,
i've tried just using each of them to see if the problem goes away - and it
doesn't.  

All my incoming/outgoing calls via Dahdi, have been recorded using
mixmonitor for the past 18 months, and every time the 'sync' issue appears
to appear, I track back to see what i've changed, and each time I've done
this never been able to work out what triggers it.   

The issue I have, which relates to the incoming call including the ringing
tones for my SIP extension ringing, is included in the file, has been a
number of issues about this in the past relating to audiohooks.

As I said in my previous note - I set mixmonitor from a macro which is
called by all incoming and outgoing contexts.

In the past once the issue 'resolves itself', i've not tried trying to
'make it happen' and don't want to loose it working again.

Sorry that I've been able to give you 'the precise steps to reproduce
this' as, for me and for those others who have this issue, and only happy
to see it working.

I reboot my server every day, and only use for personal calls.

The dates when I see it going from working->not-working->working are as
follows:
 Pre 12th Jan 2011 - mixmonitor was working.
12th Jan 2011 16:01 - mixmonitor started with issue
 8th Feb 2011 09:32 - mixmonitor started to work again
 4th Mar 2011 17:20 - mixmonitor started with issue
29th Mar 2011 08:05 - mixmonitor started to work again 
23rd Apr 2011 07:20 - mixmonitor started with issue 

I go back in time like this, and roughly every month or so, it changes
from working/not-working or vice versa.

Although I've not been able to give you what you asked for in 'Part 1 of
your requirements' as I won't know what triggered it. I kept records on
when it started/stopped working in relation my time-stamp logs of yum
updates, and also against each time-stamped SVN extract of Asterisk.  I
don't keep more than a few 'svn extracts' due to the large directory size
as I felt that it may not be realted to asterisk, at the time, and more to
OS or Time issues, but am know keeping the SVN at the time around it
previous started with the issue.

I am willing to offer any help I can.   

Ian 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-09 10:30 iasgoscouk     Note Added: 0134667                          
======================================================================