Asterisk error – 1.6.2 SVN – voicemail files “corrupted”

Home » Asterisk Users » Asterisk error – 1.6.2 SVN – voicemail files “corrupted”
Asterisk Users 2 Comments

Hi,

I know I am using SVN, but I was wondering if anybody ever came across this
error. I can’t read my voicemails because files seems to be corrupted, for
lack of a better word. When I do access my messages, I get those errors:

[Dec 2 19:45:05] NOTICE[25993]: app_voicemail.c:7432 open_mailbox: Mailbox:
/var/spool/asterisk/voicemail/xxx/709/INBOX, expected 0 but found 3
message(s) in box with max threshold of 100.

[Dec 2 19:45:05] NOTICE[25993]: app_voicemail.c:7432 open_mailbox: Mailbox:
/var/spool/asterisk/voicemail/xxx/709/INBOX, expected 0 but found 3
message(s) in box with max threshold of 100.

[snipped]

[Dec 2 19:45:07] WARNING[25993]: app_voicemail.c:7207 play_message: No
message attribute file?!!
(/var/spool/asterisk/voicemail/xxx/709/INBOX/msg0000.txt)

Well, there isn’t a msg0000.txt file, I can see that. There is a
msg0003.txt and msg0005.txt (along with the appropriate wav files). Looking
into the directory, all files seem there. Except the sequence doesn’t start
at 0000.

I have thousands of mailboxes, only one has been reported as having this
problem. There might be more though.

1) How do I fix this? I don’t mind manually fixing it when it happens,
but what’s wrong exactly?

2) If this isn’t the right list for this (considering it’s a SVN
question), what is?

I’m using SVN because of the blind transfer issue somebody mentioned
yesterday.

Mike

2 thoughts on - Asterisk error – 1.6.2 SVN – voicemail files “corrupted”

  • There is nothing wrong with using SVN.

    I have seen this once on a 1.6.2 system a while back. I just renamed
    the TXT and audio files to be sequencial numbers starting at 0000 and
    everything worked again. Asterisk assumes the voicemail message files
    are named that way, and it errors out if that is not the case.

    -Jonathan

  • There should not be anything within the Asterisk process to cause this.
    However, I _have_ seen this exact issue with certain 3rd party vendors
    that supply a tool for checking voicemail via a web interface. The
    offending tools make no effort to reorder the messages after certain
    messages are deleted, which is a really bad thing to do. If this is, in
    fact, the issue, please ask the vendor to fix the interface, because in
    the current form, it is severely broken behavior.