[asterisk-bugs] [Asterisk 0011083]: [patch] Empty voicemail message file causes call into voicemail to disconnect

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11083 
====================================================================== 
Reported By:                dtyoo
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   11083
Category:                   Applications/app_voicemail
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.4.13  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-24-2007 20:44 CDT
Last Modified:              11-24-2007 00:04 CST
====================================================================== 
Summary:                    [patch] Empty voicemail message file causes call
into voicemail to disconnect
Description: 
After upgrading from 1.4.9 to 1.4.13 we are having the following problem
with voicemail.  We sometimes get voicemail messages left in mailboxes
where the wav / data file is 44 bytes long.  The file basically has a
header but no data.  Under 1.4.13 calls into voicemail will be disconnected
after listening to such a message.  1.4.9 did not have this issue.

In case you are curious, these 44 byte messages are being left despite
minmessage being set to 3 in the general section of voicemail.conf.  These
messages are accompanied by a console message "app.c: No audio available on
SIP/IP ADDRESS-b50d7b38??"

Nothing special in the console / log file.  Looks the same as when a
caller hangs up normally even though in this case they are being
disconnected.
====================================================================== 

---------------------------------------------------------------------- 
 gkloepfer - 11-24-07 00:04  
---------------------------------------------------------------------- 
No, that's not exactly it.  You want to keep res as the return value from
wait_file, check to see if res < 0, and if it is, display the error and set
res = 0.  The return values >= 0 from wait_file are important to pass along
to the routine that calls play_message.

<OT>
I'm hoping that my "license" is approved pretty quickly.  I understand the
need for the disclaimer to assure that the code remains untainted, but I
figured that the paper one I signed about 2 years ago would carry-over... 
Argh.  This legal stuff is ridiculous...
</OT> 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-24-07 00:04  gkloepfer      Note Added: 0074254                          
======================================================================