| Event Id | 526 |
| Source | CiscoUnity_Miu |
| Description | Cisco Unity had a problem while attempting to toggle an MWI. This can happen occasionally as part of normal operation, and the MWI request will be retried. If the MWI status remains unchanged for extended periods of time, or if there are many of these warnings from Cisco Unity in a short period of time, there may be an MWI misconfiguration or other problem. See the MWI section in the troubleshooting guide, and contact TAC for assistance if needed. |
| Event Information | If the Cisco CallManager site is going to be down for a while, it may make sense to remove or to at least disable MWI on the Cisco Unity ports going to that cluster. If this step is performed, errors (Cisco Unity_Notifier, Event ID: 1041, no suitable port) will appear in the Applications log, but Cisco Unity will immediately try Cluster A. Once Cluster B is available again, the ports would need to be reconfigured for MWI notification again.Unavailable port stalls MWI on other clusters.When integrating multiple Cisco CallManager clusters to one Cisco Unity system, if one of the Cisco CallManager clusters becomes unreachable (WAN failure, Cisco Callmanager outage, etc.), MWI notifications may be affected on the Cisco CallManager clusters that are still registered normally with Cisco Unity. |
| Reference Links |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.