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

Topic Last Modified: 2011-03-19

The Microsoft Exchange 2010 UM Troubleshooting Tool is an Exchange Management Shell cmdlet named Test-ExchangeUMCallFlow. You can use the cmdlet to diagnose configuration errors specific to call answering scenarios and to test whether voice mail is functioning correctly in both on-premises and cross-premises Microsoft Exchange Server 2010 Service Pack 1 (SP1) UM deployments. You can use this cmdlet in deployments with Microsoft Office Communications Server 2007 R2 or Microsoft Lync Server 2010 or in UM deployments with IP gateways or IP PBXs.

By default, when you're running the UM Troubleshooting Tool, it uses the credentials that are used when you log on to the computer. The credentials used are those that are specified for the calling party. You must set or specify the credentials to be used when you're running the UM Troubleshooting Tool in SIPClient mode. However, you don't need to set the credentials when running the UM Troubleshooting Tool in Gateway mode.

Prerequisites

Set the credentials to use with the UM Troubleshooting Tool

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "UM server" entry in the Unified Messaging Permissions topic.

  1. Open the Microsoft Exchange 2010 UM Troubleshooting Tool from the Start menu.

  2. In the Microsoft Exchange 2010 UM Troubleshooting Tool window, at the prompt, type the following and press Enter.

    Copy Code
    $cred=Get-Credential
    
  3. In the Windows PowerShell Credential Request window, type the domain\user name and password and then click OK.

  4. In the Microsoft Exchange 2010 UM Troubleshooting Tool window, specify the necessary cmdlet parameters to test for call flow. For example:

    Copy Code
    Test-ExchangeUMCallFlow -Mode SIPClient -CallingParty tonysmith@contoso.com - CalledParty jamiestark@contoso.com NextHop ocsfe.contoso.com -Credential $cred
    

Other Tasks

After you set the credentials for the UM Troubleshooting Tool, you may also want to: