[asterisk-bugs] [Asterisk 0018998]: [patch] Voicemail doesn't read/delete messages in one case
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Apr 1 06:02:28 CDT 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18998
======================================================================
Reported By: tootai
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18998
Category: Applications/app_voicemail
Reproducibility: always
Severity: major
Priority: normal
Status: ready for testing
Asterisk Version: 1.4.40
JIRA:
Regression: No
Reviewboard Link: https://reviewboard.asterisk.org/r/1153/
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2011-03-19 05:57 CDT
Last Modified: 2011-04-01 06:02 CDT
======================================================================
Summary: [patch] Voicemail doesn't read/delete messages in
one case
Description:
When listening the voicemailbox and new callers leave a new message
something goes wrong: after the user has read and deleted all messages, the
last one is not destroyed and the new incoming recorded messages are lost.
Below the relevant logs of an user reading his mailbox with 16 messages
waiting (#<b></b>0 to #<b></b>15). During his reading, a new message was
left while reading message #<b></b>5. All 16 messages where destroyed,
voicemailbox should and has one message, number #<b></b>16. But when
calling Voicemailmain, I get:
[2011-03-19 11:15:28] NOTICE[28981] app_voicemail.c: Resequencing Mailbox:
/var/spool/asterisk/voicemail/default/100/INBOX, expected 0 but found 1
message(s) in box with max threshold of 100.
app_voicemail.c:5917 play_message: No message attribute file?!!
(/var/spool/asterisk/voicemail/default/100/INBOX/msg0000.txt)
dh at chacomx:/var/spool/asterisk/voicemail/default/100/INBOX$ ls -al
total 532
drwxr-xr-x 2 root root 4096 2011-03-19 11:15 .
drwxr-xr-x 8 root root 4096 2011-03-19 11:14 ..
-rwxr-xr-x 1 root root 45144 2011-03-18 22:00 msg0016.gsm
-rw-r--r-- 1 root root 264 2011-03-18 22:00 msg0016.txt
-rwxr-xr-x 1 root root 437804 2011-03-18 22:00 msg0016.wav
-rwxr-xr-x 1 root root 44520 2011-03-18 22:00 msg0016.WAV
So Asterisk is looking for msg0000 but found msg0016. There is no
possibility to treat this message, only rename the file as msg0000.* give
the possibility to listen and delete it.
======================================================================
----------------------------------------------------------------------
(0133272) svnbot (reporter) - 2011-04-01 06:02
https://issues.asterisk.org/view.php?id=18998#c133272
----------------------------------------------------------------------
Repository: asterisk
Revision: 312290
U branches/1.4/apps/app_voicemail.c
------------------------------------------------------------------------
r312290 | alecdavis | 2011-04-01 06:02:27 -0500 (Fri, 01 Apr 2011) | 13
lines
app_voicemail: leave_vociemail doesn't use last_message_index to store
next message
trivial change to bring inline with 1.6.2 1.8 and trunk.
The symptom was if msg0000 was missing, and the last was msg0004,
the next msgnum would be msg0000 when it should have been msg0005
(issue https://issues.asterisk.org/view.php?id=18998)
Reported by: tootai
Patches:
bug18998.diff2.txt uploaded by alecdavis (license 585)
Tested by: alecdavis
------------------------------------------------------------------------
http://svn.digium.com/view/asterisk?view=rev&revision=312290
Issue History
Date Modified Username Field Change
======================================================================
2011-04-01 06:02 svnbot Note Added: 0133272
======================================================================
More information about the asterisk-bugs
mailing list