[asterisk-bugs] [Asterisk 0017319]: asterisk 1.6.2.7 does not properly renumber/delete voicemail files when the maxmsg is exceeded
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Apr 7 14:22:16 CDT 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17319
======================================================================
Reported By: jsutton
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17319
Category: Applications/app_voicemail
Reproducibility: always
Severity: minor
Priority: normal
Status: acknowledged
Asterisk Version: 1.6.2.7
JIRA: SWP-1447
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-05-11 14:54 CDT
Last Modified: 2011-04-07 14:22 CDT
======================================================================
Summary: asterisk 1.6.2.7 does not properly renumber/delete
voicemail files when the maxmsg is exceeded
Description:
with
maxmsg = 2
set in voicemail.conf
If the maxmsg is exceeded due to simultaneous recording, asterisk will
fail to properly delete or renumber the voicemail messages that are over
the limit.
In this situation you are able to listen to the all of the voicemail
messages until you delete the messages that are under the maxmsg limit
which effectively orphans the messages that are over the limit.
======================================================================
----------------------------------------------------------------------
(0133515) jcovert (reporter) - 2011-04-07 14:22
https://issues.asterisk.org/view.php?id=17319#c133515
----------------------------------------------------------------------
Reporting similar problem in 1.8.2.3
There seems to be some condition unrelated to maxmsg (which we have at 100
and I'm pretty sure this user never got close to that) in which messages
are numbered in a way that Comedian Mail cannot handle them.
We have the following situation:
/var/spool/asterisk/voicemail/default/2811125/INBOX/:
total 532
-rw-r--r-- 1 root root 45606 Apr 6 11:17 msg0002.gsm
-rw-r--r-- 1 root root 267 Apr 6 11:17 msg0002.txt
-rw-r--r-- 1 root root 442284 Apr 6 11:17 msg0002.wav
-rw-r--r-- 1 root root 44975 Apr 6 11:17 msg0002.WAV
The user is told that he has one message, but when he goes to check it, he
hits this:
-- <DAHDI/i1/2811515-3c> Playing 'vm-youhave.ulaw' (language 'en')
-- <DAHDI/i1/2811515-3c> Playing 'digits/1.ulaw' (language 'en')
-- <DAHDI/i1/2811515-3c> Playing 'vm-INBOX.ulaw' (language 'en')
-- <DAHDI/i1/2811515-3c> Playing 'vm-message.ulaw' (language 'en')
-- <DAHDI/i1/2811515-3c> Playing 'vm-onefor.ulaw' (language 'en')
-- <DAHDI/i1/2811515-3c> Playing 'vm-INBOX.ulaw' (language 'en')
-- <DAHDI/i1/2811515-3c> Playing 'vm-messages.ulaw' (language 'en')
-- <DAHDI/i1/2811515-3c> Playing 'vm-opts.ulaw' (language 'en')
-- <DAHDI/i1/2811515-3c> Playing 'vm-helpexit.ulaw' (language 'en')
-- <DAHDI/i1/2811515-3c> Playing 'vm-first.ulaw' (language 'en')
[Apr 7 14:11:23] WARNING[9888]: app_voicemail.c:7492 play_message: No
message attribute file?!!
(/var/spool/asterisk/voicemail/default/2811125/INBOX/msg0000.txt)
-- <DAHDI/i1/2811515-3c> Playing 'vm-advopts.ulaw' (language 'en')
I've manually deleted the message for now, and will try to find out how to
reproduce the problem. But even if it's hard to reproduce, Asterisk needs
to be able to deal with the mailbox being in the above condition. Needs to
be able to find the first message, even if it's not 0000.
/john
Issue History
Date Modified Username Field Change
======================================================================
2011-04-07 14:22 jcovert Note Added: 0133515
======================================================================
More information about the asterisk-bugs
mailing list