Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2

Topic Last Modified: 2011-04-28

After you install the Unified Messaging server role on a computer running Microsoft Exchange Server 2010 and enable and configure Unified Messaging, you can use multiple diagnostic tests and a software-based telephone application to test telephony connectivity and the operation of the Unified Messaging server. This topic gives you information about the diagnostic tests for testing a Unified Messaging server.


There are three diagnostic tests that can be used to test the functionality of an Exchange 2010 Unified Messaging system and a Unified Messaging server: Local, Local with a TUILogon, and Remote. The Test-UMConnectivity cmdlet can be used to check connectivity to Unified Messaging servers in several ways, depending on the parameters used with the cmdlet. For testing Unified Messaging functionality, you can use these tests:

  • Local   The Test-UMConnectivity cmdlet verifies Voice over IP (VoIP) communication with the Unified Messaging server running on the same local computer.

  • Local with TUILogon   The Test-UMConnectivity cmdlet tries to establish VoIP communication with the Unified Messaging server running on the same computer. If it connects, it tries to sign in to one or more UM-enabled mailboxes by sending the extension number and PIN of the mailbox. If the –TUILogon parameter is supplied, the following parameter values must also be supplied for the test to complete successfully. You must supply the following parameters with the appropriate information for the test mailbox:

    • –Phone   This parameter must contain the extension number for the test mailbox.

    • –PIN   This parameter must contain the PIN of the UM-enabled mailbox.

    • –UMDialPlan   This parameter must contain the dial plan associated with the test mailbox.

    When you use this diagnostic test, you must create a test mailbox using the New-TestCasConnectivity.ps1 script located in the %ExchangeRoot%\Scripts folder. Mailboxes created using this script can also be used for other kinds of connectivity testing, for example, with Microsoft Exchange ActiveSync. When you create the test mailbox, you have the option to also enable the test mailbox for Unified Messaging by specifying the -UMDialPlan and -UMExtension parameters. If you created the test mailbox but didn't enable it for Unified Messaging, you can use the Enable-UMMailbox cmdlet or the Exchange Management Console to enable the test mailbox.

    If the –TUILogonAll parameter is supplied with the Test-UMConnectivity cmdlet, the Test-UMConnectivity cmdlet will try to log on to each Client Access server connectivity test mailbox created using the New-TestCasConnectivityUser.ps1 script in the current Active Directory site.

  • Remote   The Test-UMConnectivity cmdlet tries to connect to a remote Unified Messaging server by placing a call through an IP gateway. After it connects, it performs connectivity checks on the remote Unified Messaging server and the media paths.

    If you receive the following message, you should restart the Microsoft Exchange Unified Messaging service because it has stopped or is not responding: "The Test-UMConnectivity task encountered an error while trying to make a call. Details: Unable to establish a connection."