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.
Prerequisites
- Make sure your Exchange 2010 organization meets the following
requirements:
- A UM dial plan has been created. For detailed steps, see
Create a UM Dial
Plan.
- A UM mailbox policy has been created. For detailed steps, see
Create a UM
Mailbox Policy.
- A UM IP gateway has been created. For detailed steps, see
Create a UM IP
Gateway.
- A UM server has been added to a UM dial plan. For detailed
steps, see Add a
UM Server to a Dial Plan.
- A UM dial plan has been created. For detailed steps, see
Create a UM Dial
Plan.
- If you're running the UM Troubleshooting Tool on a local UM
server with Exchange 2010 SP1, you may not have to install all the
prerequisites listed below. They may have already been installed
along with the UM server role. However, if you're installing the UM
Troubleshooting Tool on a 64-bit computer other than a server that
is running the UM server role, you will need to install the
following components:
- Microsoft .NET Framework 3.5 Service Pack 1
(SP1) See Microsoft .NET Framework 3.5 Service Pack 1.
- If the tool will be run on a Windows Vista or Windows Server
2008 computer See Microsoft .NET Framework 3.5 Family Update for Windows
Vista x64, and Windows Server 2008 x64.
- Windows Remote Management (WinRM) 2.0 and Windows PowerShell V2
(Windows6.0-KB968930.msu) See Microsoft Knowledge
Base article 968930, Windows Management Framework Core package
(Windows PowerShell 2.0 and WinRM 2.0).
- Microsoft Unified Communications Managed API 2.0 Core Runtime
(UcmaRuntimeWebDownloadX64.msi) See Unified Communications Managed API 2.0, Core Runtime
(64-bit).
- Microsoft .NET Framework 3.5 Service Pack 1
(SP1) See Microsoft .NET Framework 3.5 Service Pack 1.
- Download and install the UM Troubleshooting Tool.
- Download Unified Messaging Troubleshooting Tool from the
Microsoft Download Center.
- Install the tool. For details, see Install the Exchange
2010 UM Troubleshooting Tool.
Important: If you will be using the UM Troubleshooting Tool in SIPClient
mode, there are several other Office Communications Server 2007 R2 or Microsoft Lync Server 2010 requirements and prerequisites that must be met. For more information, see Checklist: Deploy Office Communications Server 2007 R2 and Exchange 2010 Unified Messaging.
- Download Unified Messaging Troubleshooting Tool from the
Microsoft Download Center.
Run the UM Troubleshooting Tool on Windows 7 or Windows Vista
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.
- Click Start > All Programs >
Accessories > Windows PowerShell.
- Right-click Windows PowerShell, and from the pop-up menu
select Run as administrator.
- At the PowerShell command prompt, go to the folder where the UM
Troubleshooting Tool was installed and run the following.
Copy Code C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -psconsolefile .\Microsoft.Exchange.UM.TroubleshootingToolsnapin.psc1 -noexit -command ". '.\Microsoft.Exchange.UM.TroubleshootingTool.ps1' "
- If you're running the UM Troubleshooting Tool on Windows 7, at
the PowerShell command prompt, run the following:
Copy Code Set-ExecutionPolicy RemoteSigned
- Open the Microsoft Exchange 2010 UM Troubleshooting Tool
from the Start menu.
- In the Microsoft Exchange 2010 UM Troubleshooting Tool
window, at the prompt, type the following and press Enter.
Copy Code $cred=Get-Credential
- In the Windows PowerShell Credential Request window,
type the domain\user name and password and click OK.
- 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: