[asterisk-bugs] [Asterisk 0018240]: [patch] VoicemailMain Exits Without Warning
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Nov 12 10:49:45 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18240
======================================================================
Reported By: leobrown
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18240
Category: Applications/app_voicemail
Reproducibility: have not tried
Severity: minor
Priority: normal
Status: confirmed
Asterisk Version: SVN
JIRA: SWP-2496
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-02 06:46 CDT
Last Modified: 2010-11-12 10:49 CST
======================================================================
Summary: [patch] VoicemailMain Exits Without Warning
Description:
Hi
I've seen problems with VoicemailMain crashing in the past, from not being
able to lock paths, open audio files etc.
However, I have a VoiceMailMain which is opening a mailbox, but existing
after verifying a correct password.
The console trace is below, but because Asterisk is not crashing, I can
not provide a backtrace. Could you please give me some guidance on how to
further debug, as debug level 10 (shown below) only shows it
locking/unlocking paths and then exiting.
I have checked all permissions and even removed mailboxes and let Asterisk
create the paths itself. Voicemail() works fine, but VoicemailMain does
not. The relevant entry from voicemail.conf is also
Leo
======================================================================
----------------------------------------------------------------------
(0128829) jpeeler (administrator) - 2010-11-12 10:49
https://issues.asterisk.org/view.php?id=18240#c128829
----------------------------------------------------------------------
Yes, the old code with ERROR_LOCK_PATH did not account for things that it
should have. And I added more code that is critical, so just going back to
that is not the proper fix. I really did mean the patch I listed. Examining
the different behaviors of the backends is indeed confusing and I don't
even want to type it out. Basically there is confusion between -1 meaning
error and the mail index returning -1 for 0 messages. However, given that
-1 is a widely used convention of meaning error (and is used here in
voicemail) the checking of < -1 should be limited as the second patch has
done.
Issue History
Date Modified Username Field Change
======================================================================
2010-11-12 10:49 jpeeler Note Added: 0128829
======================================================================
More information about the asterisk-bugs
mailing list