Folks,
I have recently installed Asterisk 1.6.1.1. I have two PSTN lines
connected to a TDM400 and two VoIP lines using SIP. I have a CISCO 7940
using SIP as my desk phone. Calling any of the four lines should ring
the desk phone. This works fine, except that when ringing the PSTN
lines, it activates the MWI on the 7940. I can see this happening on
the console:
[Aug 4 16:48:47] NOTICE[2964]: chan_dahdi.c:7669 ss_thread: MWI:
Channel 3 message waiting!
Looking at the offending piece of code, it seems to suggest from the
comment that it is getting the MWI from the CLID.
/* If the CID had Message waiting payload, assume that this for MWI only
and hangup the call */
if (flags & CID_MSGWAITING) {
ast_log(LOG_NOTICE, "MWI: Channel %d message waiting!\n",
p->channel);
notify_message(p->mailbox, 1);
/* If generated using Ring Pulse Alert, then ring has been answered as
a call and needs to be hungup */
if (p->mwimonitor_rpas) {
ast_hangup(chan);
return NULL;
}
}
I have set "usecallerid=no" on both interfaces and globally but I
still
cannot get it to stop.
I have failed to turn anything up on Google regarding this.
Does anyone have any suggestions please?
Mike.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20090804/169d783f/attachment.pgp
David Gibbons
2009-Aug-04 17:37 UTC
[asterisk-users] Message Waiting Indicator on DAHDI line
This may be a stupid question, but IS THERE a message waiting against your PSTN
lines?
-Dave
-----Original Message-----
From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces
at lists.digium.com] On Behalf Of Mike
Sent: Tuesday, August 04, 2009 1:33 PM
To: asterisk-users at lists.digium.com
Subject: [asterisk-users] Message Waiting Indicator on DAHDI line
Folks,
I have recently installed Asterisk 1.6.1.1. I have two PSTN lines connected to
a TDM400 and two VoIP lines using SIP. I have a CISCO 7940 using SIP as my desk
phone. Calling any of the four lines should ring the desk phone. This works
fine, except that when ringing the PSTN lines, it activates the MWI on the 7940.
I can see this happening on the console:
[Aug 4 16:48:47] NOTICE[2964]: chan_dahdi.c:7669 ss_thread: MWI:
Channel 3 message waiting!
Looking at the offending piece of code, it seems to suggest from the comment
that it is getting the MWI from the CLID.
/* If the CID had Message waiting payload, assume that this for MWI only and
hangup the call */ if (flags & CID_MSGWAITING) {
ast_log(LOG_NOTICE, "MWI: Channel %d message waiting!\n",
p->channel);
notify_message(p->mailbox, 1);
/* If generated using Ring Pulse Alert, then ring has been answered as
a call and needs to be hungup */
if (p->mwimonitor_rpas) {
ast_hangup(chan);
return NULL;
}
}
I have set "usecallerid=no" on both interfaces and globally but I
still cannot get it to stop.
I have failed to turn anything up on Google regarding this.
Does anyone have any suggestions please?
Mike.
Doug Bailey
2009-Aug-04 20:35 UTC
[asterisk-users] Message Waiting Indicator on DAHDI line
----- "Mike" <asterisk-users at norgie.net> wrote:> Folks, > > I have recently installed Asterisk 1.6.1.1. I have two PSTN lines > connected to a TDM400 and two VoIP lines using SIP. I have a CISCO > 7940 > using SIP as my desk phone. Calling any of the four lines should > ring > the desk phone. This works fine, except that when ringing the PSTN > lines, it activates the MWI on the 7940. I can see this happening on > the console: > > [Aug 4 16:48:47] NOTICE[2964]: chan_dahdi.c:7669 ss_thread: MWI: > Channel 3 message waiting! > > Looking at the offending piece of code, it seems to suggest from the > comment that it is getting the MWI from the CLID. > > /* If the CID had Message waiting payload, assume that this for MWI > only > and hangup the call */ > if (flags & CID_MSGWAITING) { > ast_log(LOG_NOTICE, "MWI: Channel %d message waiting!\n", > p->channel); > notify_message(p->mailbox, 1); > /* If generated using Ring Pulse Alert, then ring has been answered > as > a call and needs to be hungup */ > if (p->mwimonitor_rpas) { > ast_hangup(chan); > return NULL; > } > } > > I have set "usecallerid=no" on both interfaces and globally but I > still > cannot get it to stop. > > I have failed to turn anything up on Google regarding this. > > Does anyone have any suggestions please? > > Mike.This code is designed to handle Message Waiting Indication (MWI) incoming on FXO line. This data could very well be embedded in your CID spill as part of an MDMF message that also contains the caller id information. (See main/callerid.c in the callerid_feed function.) If your incoming line has a mailbox associated with it, the MWI information will be pushed to that mailbox. You may want to look at how your mailboxes are defined and the channels to which they are associated. Doug -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20090804/219c99a5/attachment.pgp