Exchange 2010 Unified Messaging Beta Messaging Waiting Indicator
Another new feature in Exchange 2010 Unified Messaging is Message Waiting Indicator (MWI):
Now with Unified Messaging, users are notified of the presence of new/unread voice mail by lighting the lamp and providing a count on their supported desk phone. Additionally, users can configure their text messaging notification account to receive the beginning content of the voice mail preview in the SMS.
MWI can be enabled or disabled by configuring the following settings on the corresponding Unified Messaging Mailbox Policy and/or Unified Messaging IP Gateways:
Allow Message Waiting Indicator
Select this check box to enable or disable Message Waiting Indicator for users associated with the UM mailbox policy. Message Waiting Indicator is a feature found in most legacy voice mail systems. In its most common form, it lights a lamp on the voice mail subscriber’s phone to indicate the presence of a new voice mail. Message Waiting Indicator can also be a text message sent to the UM-enabled user’s mobile phone. If this option is disabled on the UM IP gateway, this feature isn’t available to UM-enabled users associated with the UM mailbox policy. This option isn’t available to UM-enabled users who have a mailbox on a Microsoft Exchange Server 2007 server. The default setting is enabled.
Allow Message Waiting Indicator
Select this check box to allow voice mail notifications to be sent to users for calls taken by the UM IP gateway. This setting allows for the UM IP gateway to receive and send SIP NOTIFY messages for users. The default setting allows for notifications to be sent to users.
Message Waiting Indicator is a feature found in most legacy voice mail systems. In its most common form, it lights a lamp on the voice mail subscriber’s phone to indicate the presence of a new voice mail. Message Waiting Indicator can refer to any mechanism that indicates the existence of a new message. The voice mail message could be a new or unheard voice mail. The indication that a new voice message had arrived could be found in the Inbox in clients such as Microsoft Office Outlook or Outlook Web Access. It could be a Short Messaging Service (SMS) or text message sent to a registered cellular phone, an outbound call made from an Exchange Unified Messaging server to a pre-configured number to play the new item, or lighting the desktop phone lamp for a user.
With the appropriate settings enabled, the Exchange 2010 Unified Messaging Server Role will send SIP NOTIFY messages to an IP/VoIP Media Gateway or IP-PBX with instructions to toggle the voice mail lamp on the subscriber’s phone. In the following sample Dialogic Media Gateway Call Log screen shot, you can see the following:
Call Record ID #1
Inbound call to x2418. The subscriber did not answer and a voice mail message was left.
Call Record ID #2
The subscriber at x2418 has received a new voice mail message.
Microsoft Exchange 2010 Unified Messaging sends a SIP NOTIFY message to the corresponding UM IP Gateway to turn ON the voice mail lamp for the subscriber at x2418:
NOTIFY sip:2418@10.2.1.248:5060;user=phone SIP/2.0
FROM: <sip:E14-BETA.contoso.com:5067;transport=Tcp;ms-opaque=c0f17a7698018595>;epid=8C6D79A30F;tag=6ae05021bd
TO: <sip:2418@10.2.1.248:5060;user=phone>
CSEQ: 1 NOTIFY
CALL-ID: c78cafdc22254e2a8acd52a432d98eb8
MAX-FORWARDS: 70
VIA: SIP/2.0/TCP 10.1.6.122:34646;branch=z9hG4bK9e848e7
CONTACT: <sip:2418@10.2.1.248:5060;user=phone>
CONTENT-LENGTH: 97
EVENT: message-summary
SUBSCRIPTION-STATE: terminated
USER-AGENT: RTCC/3.1.0.0
CONTENT-TYPE: application/simple-message-summaryMessages-Waiting: yes
Message-Account: sip:2418@10.2.1.248:5060;user=phone
Voice-Message: 1/0
Call Record ID #3
The subscriber at x2418 has just read the new voice mail message.
Now, Microsoft Exchange 2010 Unified Messaging sends a SIP NOTIFY message to the corresponding UM IP Gateway to turn OFF the voice mail lamp for the subscriber at x2418:
NOTIFY sip:2418@10.2.1.248:5060;user=phone SIP/2.0
FROM: <sip:E14-BETA.contoso.com:5067;transport=Tcp;ms-opaque=c0f17a7698018595>;epid=8C6D79A30F;tag=28ebdd05a
TO: <sip:2418@10.2.1.248:5060;user=phone>
CSEQ: 2 NOTIFY
CALL-ID: 4df4ae813dd14314834410759c57508d
MAX-FORWARDS: 70
VIA: SIP/2.0/TCP 10.1.6.122:50787;branch=z9hG4bKf6e0b8cc
CONTACT: <sip:2418@10.2.1.248:5060;user=phone>
CONTENT-LENGTH: 96
EVENT: message-summary
SUBSCRIPTION-STATE: terminated
USER-AGENT: RTCC/3.1.0.0
CONTENT-TYPE: application/simple-message-summaryMessages-Waiting: no
Message-Account: sip:2418@10.2.1.248:5060;user=phone
Voice-Message: 0/1
In order to deploy Exchange 2010 Unified Messaging Messaging Waiting Indicator (MWI), there are some deployment considerations that you must consider. Otherwise, if you do not properly plan accordingly, you will have a heck of a time troubleshooting MWI.
For assistance with Unified Communications (UC) planning, deployment, and telephone integration, check out some of our services:
Tags: Exchange Server 2010, Messaging Waiting Indicator, Microsoft, MWI, UM, Unified Messaging
