[asterisk-bugs] [Asterisk 0013005]: Recording speed too fast (running BRI B410P)

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13005 
====================================================================== 
Reported By:                alexb_uk
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   13005
Category:                   Applications/app_mixmonitor
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.4.21 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-07-07 05:12 CDT
Last Modified:              2008-10-08 14:24 CDT
====================================================================== 
Summary:                    Recording speed too fast (running BRI B410P)
Description: 
Hi,

I have been asked by Digium support to raise a bug against Mixmonitor for
making corrupt recordings in the latest version of Asterisk (1.4.21.1 and
1.4.21).

The bug does not appear when running 1.4.19.2 (with or without the latest
Zaptel drivers).

The recordings are playing back at high speed and with very bad quality.

I'm not the only person seeing this issue:
http://forums.digium.com/viewtopic.php?t=20985

Someone on the forum claims this bug has previously been raised and fixed
but sorry I could not locate it in Mantis.

Just to note I have tested the original WAV files prior to converting them
to MP3 and the issue remains.

The audio on the call itself is near perfect.

There are no errors in the logs / on the console.


Hardware:
  Digium B410P card on BT ISDN2e lines (UK).


Example Command:
   [Jul  3 11:06:20] VERBOSE[29391] logger.c:     -- Executing
[s at macro-record:19] MixMonitor("mISDN/11-u10",
"/tmp/03072008-110620--IN.wav||/usr/local/bin/wav2mp3
"/tmp/03072008-110620--IN.wav" "03072008-110620--IN.mp3" "1215079580.4" "0"
"X"") in new stack


If anyone is kind enough to look into this issue but doesnt have access to
a BRI setup then please let me know and I can provide remote access to a
server that does.


I could be incorrectly assuming this is related to BRI as I would have
thought this issue would have been found already if it happened on T1/E1
lines.  I do have access to an E1 line although it will take me a little
time to update a server and test.  Please let me know if this would be
helpful.


Thanks for any help.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0012837 Chanspy audio is delayed or lost
====================================================================== 

---------------------------------------------------------------------- 
 (0093379) putnopvut (administrator) - 2008-10-08 14:24
 http://bugs.digium.com/view.php?id=13005#c93379 
---------------------------------------------------------------------- 
blitzrage: I don't think this is related to issue 12837, since chanspy does
not have a sync trigger on the audiohook in use, so this code path would
not have been followed for it.

I have uploaded 13005_tolerance.patch. In this, I have defined a tolerance
of 100 ms (thanks very much to Steve Davies for the suggestion) so that the
streams may get out of sync by a maximum of 100 ms before the audiohooks
get flushed and resync.

I have tested this on my setup where I was reproducing the problem at will
and to my knowledge, the problem does not exist any more. I would like
confirmation from those who have been experiencing this themselves, though,
before I commit the changes to the 1.4 branch.

Speaking of which, the patch I have uploaded was made against the latest
1.4 svn , but given that I can't think of anything audiohook-related which
has been done since 1.4.22 was tagged, the patch should apply cleanly to
the 1.4.22 tag as well. Please le me know how testing goes with this. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-08 14:24 putnopvut      Note Added: 0093379                          
======================================================================