[asterisk-bugs] [Asterisk 0010487]: IMAP integration with MS Exchange crashes Asterisk-1.4.10.1

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10487 
====================================================================== 
Reported By:                ewilhelmsen
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   10487
Category:                   Applications/app_voicemail
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.10.1  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-17-2007 12:59 CDT
Last Modified:              08-30-2007 15:43 CDT
====================================================================== 
Summary:                    IMAP integration with MS Exchange crashes
Asterisk-1.4.10.1
Description: 
When setting voicemail.conf to MS Exchange IMAP server I am able to record
a message and it will send to the users Exchange Inbox but when MS Exchange
sends an IMAP response to Asterisk it does not know the tagged response for
SEARCH and NOOP. After this Warning:

[Aug 17 10:59:19] WARNING[26191]: app_voicemail.c:8572 mm_log: IMAP
Warning: Unexpected tagged response: 0000003a OK SEARCH completed.
[Aug 17 10:59:19] WARNING[26204]: app_voicemail.c:8572 mm_log: IMAP
Warning: Unexpected tagged response: 0000003e OK NOOP
completed. 

Asterisk crashes and needs to be Ctrl-C to exit and restarted.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 08-30-07 15:43  
---------------------------------------------------------------------- 
Hey, everyone. Sorry that progress isn't being made on this issue, but
since I am unable to reproduce the issue locally, it's not possible to fix
this without more output from a failure case.

First off, to those who have attempted killing Asterisk with the -11
signal, do you have the DONT_OPTIMIZE compiler flag selected in menuselect?
Selecting this flag will, in general, generate more useful backtraces. Even
in a non-crash situation, a backtrace (more specifically a "thread apply
all bt full") can be extremely helpful so that it can be seen which threads
are waiting for locks.

Also, for those of you running version 1.4.11, if you compile using the
DEBUG_THREADS compiler flag in menuselect, then when the lockup happens,
you can issue the command "core show locks" on the CLI and give the output.
I'm not confident it will help a whole lot in this issue, but in general,
deadlocks can be debugged somewhat easier with this output.

Now, if those two methods don't generate any better data, then the best we
can do is to use debug and verbose log information from the time around the
crash. So far, I've seen the two lines about the unexpected tagged
response, but it would help to see other debug messages from around the
time so that I can see exactly which part of voicemail code is causing that
message to occur.

I appreciate everyone's input on this, and hope we can get this settled
soon! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-30-07 15:43  putnopvut      Note Added: 0069736                          
======================================================================