[asterisk-users] pstn hangs up: MWI no message waiting ??

[Doug Bailey]

----- "sean darcy" <seandarcy2 at gmail.com> wrote:

> Doug Bailey wrote:
> > ----- "sean darcy" <seandarcy2 at gmail.com> wrote:
> > 
> >> pstn incoming on a TDM400P, sometimes i* won't answer, going into
> >> a loop like this:
> >>
> >>   -- Starting simple switch on 'DAHDI/4-1'
> >> [Jan 16 10:38:55] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got
> event
> >>
> >> 18 (Ring Begin)...
> >> [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got
> event
> >> 2 
> >> (Ring/Answered)...
> >> [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7299 ss_thread: MWI: 
> >> Channel 4 no message waiting!
> > 

As part of the implementation of issue 8587, a check was incldued for MWI
messages preceded by Ring Pulse Alert Signals (RPAS).  The RPAS is answered by
chan_dahdi as a standard call and the MWI message is processed.  As part of the
implementation, if the MWI message was included, the channel was hung up.

This did not take into account that possibility of MWI messages included into 
the to standard CID spills.  I believe this is the case here and the MWI 
portion of the CID spill is causing the channel to hang up.

You can look at commit 169154 for a fix or simply remove the ast_hangup calls
immediately after the message "MWI: channel %d no message waiting!\n" and
"MWI: Channel %d no message w