- Outlook Voice Access (OVA) does not work across multiple dial plans. Instead, a fast busy or dead air issue may occur.
- The Calls Transfer or Call Forwarding function does not work.
- Voice mail messages are not delivered to multiple mailboxes.
Test-ExchangeUMCallFlow cmdlet in Windows PowerShell. For example, run a cmdlet that resembles the following:
PS C:\> Test-ExchangeUMCallFlow [-Mode <Gateway | SIPClient> ] [-NextHop <string> ] [-CalledParty <string> ] [-CallingParty <string> ] [-Credential <PSCredential> ]
|Mode||Use the SIPClient setting for users who are enabled for Enterprise voice in O365-D and ITAR environments.|
|NextHop||Specify the fully qualified domain name (FQDN) of Lync Front End (FE) as a string value. The FE server must be indicated as an IP gateway object in the Unified Messaging (UM) configuration of the organization. Additionally, the dial plan that has the targeted user enabled must be included as a hunt group that is associated with the gateway object.|
|CalledParty||Specify the test account as a string value. For example, specify a value that resembles the following:|
|CallingParty||Specify the test account as the string value. For example, specify a value that resembles the following:|
- The test call is completed successfully. In this situation, the end-to-end solution components are online and functioning correctly.
- Failure occurs. To resolve this issue, try to use a different CalledParty account.
- Failure occurs for multiple mailboxes. To resolve this issue, please use the Exchange Online topic and the Access/performance issues sub-topic when you submit a support incident online to Microsoft Online Services Support, or contact Microsoft Online Services Support by telephone .
Article ID: 2748713 - Last Review: 17 Nov 2016 - Revision: 1