[asterisk-bugs] [Asterisk 0013588]: Wav49 corrupted in voicemail

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13588 
====================================================================== 
Reported By:                tech_admin
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13588
Category:                   Applications/app_voicemail
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.21.2 
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-09-30 02:48 CDT
Last Modified:              2008-10-09 17:54 CDT
====================================================================== 
Summary:                    Wav49 corrupted in voicemail
Description: 
We are encountering a bug  with voicemail and WAV49 and we have this issue
with two new installs of asterisk on two different servers. When a user
tries to leave a message the  recorded WAV49 is completely inaudible.
Whereas the one in WAV is good. We reproduced this issue using the
‘Record’ command.


As you can guess this is creating a problem to us as emailing WAV files is
resource greedy.
Did anyone face the same issue?
Sincerely,
TA

====================================================================== 

---------------------------------------------------------------------- 
 (0093431) Corydon76 (administrator) - 2008-10-09 17:54
 http://bugs.digium.com/view.php?id=13588#c93431 
---------------------------------------------------------------------- 
What is bizarre is that there is literally NO difference in the way those
files are written between 1.4 and 1.6.  The only way that the format could
have come out different is if you were running a version prior to 1.4.19,
which is NOT what you notated in the top of this issue. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-09 17:54 Corydon76      Note Added: 0093431                          
======================================================================