This document describes one reason why Cisco Unity Express (CUE) fails to turn on the Message Waiting Indicator (MWI) on phones connected to the remote Cisco CallManager Express (CME) and provides a solution in a Cisco CallManager Express and Cisco Unity Express environment.
Note: The configuration contained in this document is not a supported configuration. This document is written for customers who want to test this environment in the lab only.
Cisco recommends that you have knowledge of these topics:
The information in this document is based on these software and hardware versions:
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
In the central site, there is one Cisco CallManager Express and one Cisco Unity Express. In the remote site, there exists only one Cisco CallManager Express. Figure 1 shows the topology.
Cisco Unity Express is able to set the MWI for phones located in the central site (see arrow A in Figure 1), but fails to turn on or turn off the MWI for all phones located in the remote site (see arrow B in Figure 1).
This problem is caused by an incorrect Cisco CallManager Express and Cisco CallManager Express/Cisco Unity Express configuration. This output shows the correct configuration: