Exchange 2010 UM MWI enablement for CUCM

So we have all heard that Message Waiting Indicator(MWI) is now a native feature of Exchange 2010 Unified Messaging offering. To enable it on a Cisco IP phone there is a step that needs to be completed before it will work. Exchange UM uses a SIP Notify message to let Cisco Unified Communications Manager know that it needs to light the MWI on the phone. This means that Accept Unsolicited Notification needs to be enabled on the SIP trunk within CUCM.

It is also important to be aware of ensuring your line number in CUCM and the Exchange UM dial plan are using the same extension length. So if you line number on your CUCM Ip phone is 5 digits and your using translation patterns to send and receive calls to normalize to the 5 digits then your Exchange dial plan also needs to be 5 digits.

Below is an example of the SIP notify used by Exchange to signal the MWI is to be enabled:

NOTIFY from ExchangeUM
NOTIFY sip:50001@;user=phone SIP/2.0
FROM: ;epid=9B33E64896;tag=5d4cd46f51
CALL-ID: cfeb9356f91a40108d58483fb3ad94e5
VIA: SIP/2.0/TCP;branch=z9hG4bK7936d53c
EVENT: message-summary
CONTENT-TYPE: application/simple-message-summary

Messages-Waiting: yes
Message-Account: sip:50001@;user=phone
Voice-Message: 2/0

200 OK Response from CUCM
SIP/2.0 200 OK
Date: Thu, 19 Nov 2009 08:30:46 GMT
FROM: ;epid=9B33E64896;tag=5d4cd46f51
Content-Length: 0
TO: sip:50001@;user=phone;tag=1584108481
CALL-ID: cfeb9356f91a40108d58483fb3ad94e5
VIA: SIP/2.0/TCP;branch=z9hG4bK7936d53c

To enable MWI…

1)Open Cisco Unified CM Administration
2)Click System > Security Profile > SIP Trunk Security Profile

3)At the Find and List SIP Trunk Security Profiles screen, click the FIND button
4)You’ll likely then see at least two SIP Trunk Security profiles (i.e. Non Secure, Secure). Select the profile used by your SIP trunk with Ex2010UM.
5)From the SIP Trunk Security Profile Configuration menu, verify that Accept Unsolicited Notification is enabled.

Note: If your SIP trunk to UM is configured to use Digest Authentication, also be sure to select the option Enable Application Level Authorization.

6)Commit changes by clicking Save (this will restart all trunks associated with the security profile)

Thanks to Dave Howe from MS support for the great information. Check out Dave’s blog here:


  1. What version CUCM did you use in this example?

  2. I would use this document in conjunction with the advice from my blog. The information should hold true for 5.x, 6.x and 7.x CUCM.

  3. Have you done any testing with Cisco CME to Exchange 2010 UM. Our remote offices run CME independant of all the other offices but we want to centralize VM on Exchange back at corp. Proper failover to PSTN during WAN outages is critical.

  4. We are testing Exchange UM with Callmanager 8.6. We have it working but the MWI turn on and off is erratic. Sometimes it works ok but others it can take quite a while to turn on or off the light. Any ideas?


Note: Only a member of this blog may post a comment.