[asterisk-bugs] [Asterisk 0013005]: Recording speed too fast (running BRI B410P)
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Oct 10 11:19:14 CDT 2008
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: ready for testing
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-10 11:19 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.
======================================================================
----------------------------------------------------------------------
(0093489) putnopvut (administrator) - 2008-10-10 11:19
http://bugs.digium.com/view.php?id=13005#c93489
----------------------------------------------------------------------
stevedavies: Ah, I hadn't realized where the 100ms suggestion had come from
:)
Dark_Schneider: um, right now since the value is a constant, there is no
calculation at all, so you would actually be introducing a very very minute
performance decrease by making the tolerance dynamic.
Anyway, I don't consider this issue to be completely solved as of now
given Dark_Schneider971's report of the problem still existing on long
calls. On the setup where I could reproduce the problem, I applied the
patch and ran a call for approx. 16 minutes and did not encounter the
sped-up recording. I'll try more tests though and will report back if I
encounter the problem myself.
Issue History
Date Modified Username Field Change
======================================================================
2008-10-10 11:19 putnopvut Note Added: 0093489
======================================================================
More information about the asterisk-bugs
mailing list