[asterisk-bugs] [Asterisk 0018358]: Cannot forward voicemail with file storage backend
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Dec 13 21:00:51 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18358
======================================================================
Reported By: cabal95
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18358
Category: Applications/app_voicemail
Reproducibility: always
Severity: major
Priority: normal
Status: acknowledged
Asterisk Version: 1.8.0
JIRA: SWP-2645
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-11-23 13:28 CST
Last Modified: 2010-12-13 21:00 CST
======================================================================
Summary: Cannot forward voicemail with file storage backend
Description:
We are running Asterisk 1.8.0 and cannot forward voicemail. We have "file
storage" backed voicemail with most users having notify + delete via e-mail
turned on. The ones that have it turned off (voicemail stays on the file
system) cannot forward voicemail. The message notification will go through
with a 0-byte attachment.
I have traced it to, I believe, the copy_message() function. At or around
line app_voicemail.c:5165 inside the copy_message() function there is a
call to vm_delete() after the message is copied. I commented out this line
and voicemail forwarding seems to be working correctly.
======================================================================
----------------------------------------------------------------------
(0129586) jcapp (reporter) - 2010-12-13 21:00
https://issues.asterisk.org/view.php?id=18358#c129586
----------------------------------------------------------------------
I have verified this problem exists in 1.8.0 and 1.8.1 but not 1.6.2.5. It
appears that an EXISTS conditional was removed, resulting in vm_delete
being called as part of the ODBC cleanup. I do not believe the EXISTS
conditional should have been removed. A patch restoring this section of
code to the same functionality as its 1.6.2.5 counterpart will follow.
Issue History
Date Modified Username Field Change
======================================================================
2010-12-13 21:00 jcapp Note Added: 0129586
======================================================================
More information about the asterisk-bugs
mailing list