asterisk users - Jun 2009 - IMAP voice mail storage

Hello, all.  I am attempting to use IMAP voice mail storage in Asterisk
1.6.1.1 on CentOS 5.3 using Zimbra 5.1.6.  I will not be using it as it
has proved terribly unstable - Asterisk segfaults on every voice mail
message although the message is successfully deliver to my email inbox -
but I thought I should report it.  Here are the errors from the Asterisk
console:

    -- Executing [210 at client1-internal:4]
VoiceMail("SIP/1001-ac0566e8", "210 at default,u") in new
stack
    -- <SIP/1001-ac0566e8> Playing 'vm-theperson.gsm' (language
'en')
[Jun 19 14:51:38] NOTICE[28930]: channel.c:2860 __ast_read: Dropping
incompatible voice frame on SIP/1001-ac0566e8 of format ulaw since our native
format has changed to 0x2 (gsm)
    -- <SIP/1001-ac0566e8> Playing 'digits/2.gsm' (language
'en')
    -- <SIP/1001-ac0566e8> Playing 'digits/1.gsm' (language
'en')
    -- <SIP/1001-ac0566e8> Playing 'digits/0.gsm' (language
'en')
    -- <SIP/1001-ac0566e8> Playing 'vm-isunavail.gsm' (language
'en')
    -- <SIP/1001-ac0566e8> Playing 'vm-intro.gsm' (language
'en')
[Jun 19 14:51:48] WARNING[28930]: app_voicemail.c:2704 check_quota: Mailstream
not available for mailbox: INBOX
    -- <SIP/1001-ac0566e8> Playing 'beep.gsm' (language
'en')
    -- Recording the message
    -- x=0, open writing:  /var/spool/asterisk/voicemail/default/210/tmp/umh157
format: wav49, 0x2aaaac05b798
    -- x=1, open writing:  /var/spool/asterisk/voicemail/default/210/tmp/umh157
format: gsm, 0x2aaaac05c1c8
    -- x=2, open writing:  /var/spool/asterisk/voicemail/default/210/tmp/umh157
format: wav, 0x2aaaac08d788
    -- User ended message by pressing #
    -- <SIP/1001-ac0566e8> Playing 'auth-thankyou.gsm' (language
'en')
  == Parsing
'/var/spool/asterisk/voicemail/default/210/INBOX/msg0000.txt':   ==
Found
[Jun 19 14:51:54] ERROR[28930]: app_voicemail.c:2309 mm_log: IMAP Error: Server
disables LOGIN, no recognized SASL authenticator
[Jun 19 14:51:54] ERROR[28930]: app_voicemail.c:2068 init_mailstream: Can't
connect to imap server {zimbra.mycompany.com:143/imap/notls/user=me at
mycompany.com}INBOX
[Jun 19 14:51:54] ERROR[28930]: app_voicemail.c:1819 imap_store_file: Could not
initialize mailstream for
  == Parsing
'/var/spool/asterisk/voicemail/default/210/INBOX/msg0000.txt':   ==
Found
Segmentation fault


voicemail.conf looked like this:
; IMAP voice mail storage
imapserver=zimbra.mycompany.com
;imapport=143
;expungeonhangup=yes
;imapfolder=INBOX
;imapflags=notls
;authuser=pbx at mycompany.com
;authpassword=didn'tworkanyway

210 => 6370,John Sullivan,,imapuser=me at mycompany.com

I also tried without authuser and setting passwords individually.

By the way, how does one disable IMAP storage? Without the IMAP
settings, I keep getting:

[Jun 19 15:04:48] WARNING[29032]: app_voicemail.c:1628 messagecount:
IMAP user not set for mailbox 210

I did not see a module for IMAP storage.  It would seem strange that I
would have to recompile.  Thanks - John

-- 
John A. Sullivan III
Open Source Development Corporation
+1 207-985-7880
jsullivan at opensourcedevel.com

http://www.spiritualoutreach.com
Making Christianity intelligible to secular society

John A. Sullivan III schrieb:
> By the way, how does one disable IMAP storage?
> I did not see a module for IMAP storage.  It would seem strange that I
> would have to recompile.
Sadly you have to recompile.
Disable voicemail IMAP storage in `make menuselect`.


    Philipp Kempgen
-- 
AMOOMA GmbH - Bachstr. 126 - 56566 Neuwied  ->  http://www.amooma.de
Gesch?ftsf?hrer: Stefan Wintermeyer, Handelsregister: Neuwied B14998
Asterisk: http://the-asterisk-book.com - http://das-asterisk-buch.de
Videos of the AMOOCON VoIP conference 2009 ->  http://www.amoocon.de
--

Philipp Kempgen wrote:
> John A. Sullivan III schrieb:
> 
>> By the way, how does one disable IMAP storage?
> 
>> I did not see a module for IMAP storage.  It would seem strange that I
>> would have to recompile.
> 
> Sadly you have to recompile.
> Disable voicemail IMAP storage in `make menuselect`.
Additionally, bugs should be reported to http://issues.asterisk.org if you would
like any action to be taken on the issue :)

Thanks!
Leif Madsen.