Topic Last Modified: 2010-07-29

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager runs Exchange Management Shell cmdlets to monitor your Exchange organization. Running cmdlets triggers one or more Operations Manager alerts if a problem is detected.

To learn more about this alert, in Operations Manager, do one or more of the following:


Product Name


Product Version

14.0 (Exchange 2010)

Event ID


Event Source

MSExchange Monitoring UMConnectivity Local Voice

Server Role

Ex14. Unified Messaging

Rule Path

Microsoft Exchange Server/Exchange 2010/Unified Messaging/Availability/Service

Rule Name

UM Connectivity (Local Voice) transaction failure - Call wasn't answered before time-out.


This alert indicates that a connectivity transaction error occurred and an incoming call wasn't answered by a Unified Messaging server. The Test-UMConnectivity cmdlet runs every 5 minutes on a Unified Messaging server. It tries to check for the server's availability by sending a SIP request. In situations, when the Microsoft Exchange Unified Messaging service is not responsive and the cmdlet fails on two consecutive attempts, this alert is triggered. Information provided in the Operator Console may help you understand and resolve this alert. Specifically, it may help you do the following:

  • Determine the Unified Messaging server involved in the triggering of this alert.

  • Determine the error code associated with the logging of this alert.

For more information, see Testing Unified Messaging Server Functionality.

User Action

To resolve this alert, do one or more of the following:

  • Make sure that the Microsoft Exchange Unified Messaging service is running.

  • Verify the event logs in the events viewer and look for warnings or errors raised approximately at the same time of the alert. Each warning and error must be verified as it might indicate what caused the problems seen by the Microsoft Exchange Unified Messaging service.

  • Verify that other applications or processes aren't using more system resources than are required.

  • Restart the Microsoft Exchange Unified Messaging service.

  • Review the Operator Console for detailed information about the cause of this alert. For more information, see the introduction section.

  • Review the Application log and System log on your Exchange 2010 servers for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.

For more information about the Test-UMConnectivity cmdlet, see Test-UMConnectivity.

For More Information

If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.