Study guide
6.3 Message Waiting Indication (MWI) & Troubleshooting
Cisco 350-801 CLCOR CCNP/CCIE Collaboration Core v2.0
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Collaboration Architecture, Deployment Models, Sizing & Upgrades
1.1 Collaboration Architecture & Deployment Models 1.2 Capacity Planning, Sizing & Bandwidth Considerations 1.3 High Availability, Redundancy & Disaster Recovery 1.4 Cisco Unified CM Cluster Upgrade Process
2 Chapter 2: Edge Architecture, Security & Network Services
2.1 Collaboration Edge Architecture: CUBE & Expressway 2.2 Security Protocols & PKI: SSO, OAuth, TLS & SRTP 2.3 Network Infrastructure Services: DNS, NTP, DHCP & LDAP
3 Chapter 3: Protocols, Codecs & Endpoint Provisioning
3.1 SIP Signaling Architecture & Call Flows 3.2 Session Description Protocol (SDP) & Early Offer vs. Delayed Offer 3.3 Audio/Video Codecs & DTMF Relay 3.4 Endpoint Deployment, Onboarding & Troubleshooting
4 Chapter 4: CUCM Dial Plan Fundamentals & Digit Analysis
4.1 Partitions and Calling Search Spaces (CSS) 4.2 Route Patterns, Route Groups & Route Lists 4.3 Translation Patterns, Transformation Patterns & Digit Manipulation 4.4 Globalized Call Routing & Local Route Group (LRG)
5 Chapter 5: Advanced Call Control, Call Routing & User Management
5.1 Call Admission Control (CAC), Locations & AAR 5.2 Toll Fraud Prevention & Call Privileges 5.3 CUCM User Management, LDAP Integration & RBAC 5.4 Administrative XML (AXL) API & Dial-Plan Troubleshooting Tools
6 Chapter 6: Cisco Unity Connection & Voicemail Integration
6.1 Cisco Unity Connection Architecture & SIP Integration 6.2 Mailbox Provisioning, User Templates & Class of Service 6.3 Message Waiting Indication (MWI) & Troubleshooting 6.4 Call Handlers & Directory Handlers
7 Chapter 7: IOS XE Voice Gateways, CUBE & Media Resources
7.1 Cisco IOS XE Voice Gateways & Dial Peers 7.2 Voice Translation Rules and Translation Profiles 7.3 Cisco Unified Border Element (CUBE) Configuration & Redundancy 7.4 IOS XE Media Resources & DSP Management
8 Chapter 8: Webex Architecture, Control Hub, Meetings & Messaging
8.1 Webex Suite Overview & Control Hub Architecture 8.2 Cloud Identity Management, SCIM & Directory Connector 8.3 Webex Developer Platform & APIs 8.4 Configuring Webex Cloud Meetings 8.5 Configuring Webex Cloud Messaging
9 Chapter 9: Webex Calling Routing, Permissions & PSTN Connectivity
9.1 Webex Calling Architecture, Locations & Number Management 9.2 Webex Calling Routing, Trunks & Dial Plans 9.3 Webex Calling Call Routing Process & Translation Patterns 9.4 Webex Calling Toll Fraud Prevention, Call Permissions & Operating Modes 9.5 PSTN Connectivity: Cloud-Connected PSTN (CC-PSTN) & Cisco Calling Plans 9.6 Webex Calling Local Gateway (LGW) Architecture & Configuration
10 Chapter 10: Webex Hybrid Services & Cloud Connected UC
10.1 Cloud-Connected UC (CCUC) Architecture & Telemetry 10.2 Webex Hybrid Calendar & Hybrid Directory Services 10.3 Webex Video Mesh & Hybrid Data Security
11 Chapter 11: Media Quality, QoS Engineering & Troubleshooting
11.1 Real-Time Media Characteristics & Impairments 11.2 QoS Classification, Marking & Trust Boundaries 11.3 Low Latency Queuing (LLQ) Configuration on Cisco IOS XE 11.4 Troubleshooting Media Quality & Call Failures
6.3 Message Waiting Indication (MWI) & Troubleshooting
Key Takeaways Explain This Topic AI
Message Waiting Indication (MWI) updates the telephone visual indicator using either modern RFC 3842 unsolicited SIP NOTIFY messages or legacy outdial dialed extension patterns.
RFC 3842 SIP NOTIFY MWI sends a message-summary body (new, old, and urgent counts) over the SIP trunk; no call is placed, so a port enabled for MWI is busy only for an instant.
The most prevalent cause of SIP NOTIFY MWI failure is omitting the 'Accept Unsolicited Notification' checkbox on the CUCM SIP Trunk Security Profile or applying a Calling Search Space on the SIP trunk that cannot see the phone DN partition.
Legacy Outdial MWI consumes dedicated voice messaging ports to dial configured MWI On and MWI Off numbers in CUCM, which can cause severe port starvation and delayed notifications during peak hours.
Synchronize All MWIs on This Phone System (Telephony Integrations > Phone System) makes CUC resend the correct MWI state for every mailbox, fixing lamps that are out of step with the message store.
Last updated: October 2026
6.3 Message Waiting Indication (MWI) & Troubleshooting
Message Waiting Indication (MWI) is the critical signaling feedback loop that alerts telephone subscribers to the presence of unheard voice messages. When a caller deposits a message, Cisco Unity Connection (CUC) notifies Cisco Unified Communications Manager (CUCM), which instructs the target Cisco IP Phone to illuminate its handset LED lamp and display an envelope icon on the liquid crystal display (LCD).
Diagnosing MWI failures is a frequent requirement in enterprise collaboration environments. Understanding the exact signaling mechanisms and protocol flows is essential for effective troubleshooting.
1. MWI Signaling Mechanisms: SIP NOTIFY vs. Legacy Outdial
Enterprise collaboration deployments implement MWI using one of two primary architectures: SIP NOTIFY MWI (RFC 3842) or Legacy Outdial MWI . +-----------------------------------------------------------------------------------+
- | MWI SIGNALING METHOD COMPARISON |
- | |
- | METHOD 1: RFC 3842 SIP NOTIFY MWI (MODERN BEST PRACTICE) |
- | +------------------------+ SIP NOTIFY (Unsolicited) +-----------------+ |
- | | Unity Connection (CUC) | -------------------------------> | CUCM Cluster | |
- | | | <------------------------------- | | |
- | +------------------------+ SIP 200 OK +--------+--------+ |
- | * No call placed; port busy for an instant | |
- | * Fast, lightweight, scalable IP signaling v |
- | [ IP Phone Lamp ] |
- | |
- | METHOD 2: LEGACY OUTDIAL MWI (DEPRECATED / TRADITIONAL) |
- | +------------------------+ Dials MWI On (e.g. 2500) +-----------------+ |
- | | Unity Connection (CUC) | ===============================> | CUCM Cluster | |
- | | | (Seizes Outdial Port) | | |
- | +------------------------+ +--------+--------+ |
- | * Consumes physical/virtual Voice Messaging Ports | |
- | * Prone to port starvation during peak traffic v |
- | [ IP Phone Lamp ] |
- +-----------------------------------------------------------------------------------+
- Method 1: RFC 3842 Unsolicited SIP NOTIFY MWI
In a standard SIP integration, CUC utilizes the RFC 3842 standard ( Session Initiation Protocol (SIP) Event Package for Message Waiting Indication and Summary ).
When a message state changes (e.g., a new message arrives, or an unread message is marked read or deleted), CUC sends an unsolicited SIP NOTIFY request directly to CUCM across the existing SIP Trunk.
- Anatomy of an RFC 3842 SIP NOTIFY Message: NOTIFY sip:2002@10.1.1.10:5060 SIP/2.0
- Via: SIP/2.0/TCP 10.1.10.51:5060;branch=z9hG4bK5f6a7b8c9d
- From: <sip:5000@10.1.10.51>;tag=cucmwi102938
- To: <sip:2002@10.1.1.10>
- Call-ID: 1122334455@10.1.10.51
- CSeq: 1001 NOTIFY
- Max-Forwards: 70
- Event: message-summary
- Subscription-State: terminated
- Content-Type: application/simple-message-summary
- Content-Length: 94
- Messages-Waiting: yes
- Message-Account: sip:2002@10.1.10.51
- Voice-Message: 2/4 (1/2)
- Fax-Message: 0/0 (0/0)
Key header fields and syntax breakdown:
Event: message-summary : Identifies this transaction as an MWI state notification.
Messages-Waiting: yes : Directs the switch to illuminate the visual lamp ( no turns the lamp off).
Voice-Message: 2/4 (1/2) : Reports detailed message counts formatted as: Voice-Message: New Normal + New Urgent Old Normal + Old Urgent ( New Urgent Old Urgent ) \text{Voice-Message:} \; \frac{\text{New Normal + New Urgent}}{\text{Old Normal + Old Urgent}} \; \left( \frac{\text{New Urgent}}{\text{Old Urgent}} \right) Voice-Message: Old Normal + Old Urgent New Normal + New Urgent ( Old Urgent New Urgent ) In this example, the user has 2 new messages and 4 old messages (with 1 new urgent message and 2 old urgent messages).
Method 2: Legacy Outdial MWI
In legacy SCCP or older telephony configurations, CUC does not transmit SIP NOTIFY packets. Instead, CUC treats MWI lamp toggling as an outbound telephone call:
In CUCM, administrators define two dialed numbers: Message Waiting On (e.g., 2500 ) and Message Waiting Off (e.g., 2501 ).
When extension 2002 receives a voicemail, CUC seizes a configured Dial-Out Voice Messaging Port .
The port places a brief call to the MWI On number, identifying extension 2002 as the target; CUCM turns the lamp on and the call ends.
When the user has no more new messages, a port places a similar call to the MWI Off number.
Architectural Comparison
Evaluation Metric RFC 3842 SIP NOTIFY MWI Legacy Outdial MWI
Port Consumption No call placed; the MWI-enabled port is used only for an instant Places a call on a dial-out port for every lamp change
- Scalability High; handles hundreds of updates per second Constrained by available dial-out port licenses
- Latency Instantaneous (< 100 ms) Queued; can take minutes or hours under load
- Information Density Detailed; delivers new/old/urgent message counts Binary state only (Lamp ON or Lamp OFF)
Configuration Simplicity Native to SIP Trunk; no dialed patterns required Requires MWI On / MWI Off numbers and route partitions
2. Common MWI Failure Modes and Troubleshooting Workflows
When a user reports that their voicemail lamp remains dark despite having unheard messages (or stays illuminated after all messages are deleted), administrators must isolate the failure point using a structured troubleshooting methodology. +-----------------------------------------------------------------------------------+
- | MWI ROOT CAUSE ISOLATION MATRIX |
- | |
- | SYMPTOM: SIP NOTIFY MWI FAILS (LAMP NEVER ILLUMINATES) |
- | +-----------------------------------------------------------------------------+ |
- | | | |
- | | 1. CUCM returns 'SIP/2.0 404 Not Found' to CUC NOTIFY | |
- | | Cause: SIP Trunk Calling Search Space (CSS) lacks the partition of DN. | |
- | | Fix: Add Phone Directory Number Partition to the SIP Trunk's CSS. | |
- | | | |
- | | 2. CUCM returns 'SIP/2.0 403 Forbidden' or drops NOTIFY | |
- | | Cause: 'Accept Unsolicited Notification' is UNCHECKED on SIP Profile. | |
- | | Fix: Check 'Accept Unsolicited Notification' in Security Profile. | |
- | | | |
- | | 3. CUC sends NOTIFY to wrong IP address | |
- | | Cause: Port Group points to non-call processing CUCM Publisher/TFTP. | |
- | | Fix: Update CUC Port Group to point to active CUCM Subscribers. | |
- | +-----------------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------------+
- Issue 1: Calling Search Space (CSS) Partition Misconfiguration
When CUC sends NOTIFY sip:2002@10.1.1.10:5060 , CUCM acts as a SIP receiver and must route the notification to internal Directory Number 2002 .
CUCM uses the Calling Search Space configured on the incoming SIP Trunk to search for DN 2002 .
If DN 2002 resides in the Internal_Phones_PT partition, but the SIP Trunk's CSS contains only the Gateway_PT partition, CUCM cannot find the destination directory number.
Diagnostic Indicator : CUCM responds to CUC's SIP NOTIFY with a SIP/2.0 404 Not Found message. The lamp never turns on.
Resolution : Ensure the Calling Search Space assigned to the CUC SIP Trunk in CUCM includes the partitions containing all subscriber directory numbers.
Issue 2: SIP Trunk Security Profile Misconfiguration
By default, standard SIP security profiles reject unsolicited notifications to prevent denial-of-service (DoS) lamp flooding.
Under System > Security > SIP Trunk Security Profile , inspect the profile assigned to the CUC SIP trunk.
If the Accept Unsolicited Notification checkbox is unchecked, CUCM rejects incoming RFC 3842 NOTIFY packets with SIP/2.0 403 Forbidden or ignores them.
Resolution : Check the box for Accept Unsolicited Notification and reset the SIP trunk.
Issue 3: Outdial Port Starvation (Legacy Outdial MWI)
In systems utilizing Legacy Outdial MWI, CUC must seize a Voice Messaging Port configured with the Send MWI Requests attribute.
During the morning busy hour (8:00 AM – 9:30 AM), hundreds of users arrive, listen to messages, and delete them.
If the CUC Port Group only has 2 or 3 ports dedicated to outdialing, all outdial ports become saturated.
MWI turn-off requests enter a software buffer queue. Users see their lamp remain illuminated for 30 to 60 minutes after emptying their inbox.
Resolution : Transition to RFC 3842 SIP NOTIFY MWI, or reallocate additional Voice Messaging Ports from "Answering" to "Send MWI Requests".
3. MWI Synchronization Utility & Diagnostics
When network disruptions, cluster failovers, or database maintenance cause phone lamp states to fall out of sync with actual mailbox contents (e.g., lamps remain lit with zero unheard messages), administrators can synchronize the system without restarting services.
Synchronizing MWIs
In Cisco Unity Connection Administration > Telephony Integrations > Phone System , open the phone system and run Synchronize All MWIs on This Phone System :
CUC checks the unheard-message state of every mailbox on that phone system.
It resends the correct on or off request for each user (a SIP NOTIFY, or an MWI call in an SCCP integration), overriding whatever state the phone currently shows.
For a single user, resend or check MWI from that user's Message Waiting Indicators page.
Traces and Status Checks
In Cisco Unity Connection Serviceability > Trace > Macro Traces , enable Traces for MWI problems , reproduce the issue, and collect the logs with RTMT.
RTMT's Port Monitor for Unity Connection shows which ports are busy and what they are doing, which helps confirm port starvation.
show cuc cluster status on the CLI confirms that both servers are running and shows which one has Primary status.
In CUCM, administrators inspect MWI signaling using the Cisco Unified Real-Time Monitoring Tool (RTMT) :
Collect Cisco CallManager traces.
Filter by Event: message-summary or search for the subscriber directory number (e.g., 2002 ).
Verify that CUCM returns SIP/2.0 200 OK to CUC's NOTIFY request, followed by CUCM sending a Skinny or SIP NOTIFY downstream to the IP phone.