[asterisk-bugs] [Asterisk 0014313]: won't answer pstn on TDM400P if MWI

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14313 
====================================================================== 
Reported By:                seandarcy
Assigned To:                dbailey
====================================================================== 
Project:                    Asterisk
Issue ID:                   14313
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           1.6.1
====================================================================== 
Date Submitted:             2009-01-22 14:46 CST
Last Modified:              2009-01-29 10:09 CST
====================================================================== 
Summary:                    won't answer pstn on TDM400P  if MWI
Description: 
Incoming pstn call to a TDM400P:

 Using svn  1.6.1-169788.20090121

  -- Starting simple switch on 'DAHDI/4-1'
[Jan 22 15:33:01] NOTICE[28000]: chan_dahdi.c:7144 ss_thread: Got event 18
(Ring Begin)...
[Jan 22 15:33:04] NOTICE[28000]: chan_dahdi.c:7144 ss_thread: Got event 2
(Ring/Answered)...
[Jan 22 15:33:04] NOTICE[28000]: chan_dahdi.c:7316 ss_thread: MWI: Channel
4 no message waiting!

And that's it. Never answers the call.

Restarting asterisk makes it work. No MWI message and the line is
answered.
====================================================================== 

---------------------------------------------------------------------- 
 (0099063) dbailey (administrator) - 2009-01-29 10:09
 http://bugs.digium.com/view.php?id=14313#c99063 
---------------------------------------------------------------------- 
Assuming that the patches listed fixed the issue. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-29 10:09 dbailey        Note Added: 0099063                          
2009-01-29 10:09 dbailey        Status                   new => resolved     
2009-01-29 10:09 dbailey        Fixed in Version          => 1.6.1           
2009-01-29 10:09 dbailey        Resolution               open => fixed       
2009-01-29 10:09 dbailey        Assigned To               => dbailey         
2009-01-29 10:09 dbailey        Status                   resolved => closed  
======================================================================