Applies to: Exchange Server 2013
Topic Last Modified: 2012-06-29
Use the Get-UMCallRouterSettings cmdlet to retrieve the properties for a Client Access server that runs the Microsoft Exchange Unified Messaging Call Router service and returns a list of available Client Access servers from Active Directory.
For information about the parameter sets in the Syntax section below, see Syntax.
This example displays a list of all the Client Access servers running the Microsoft Exchange Unified Messaging Call Router service in the Active Directory forest.
The Get-UMCallRouterSettings cmdlet retrieves the properties for a Client Access server that runs the Microsoft Exchange Unified Messaging Call Router service and returns a list of available Client Access servers from Active Directory. When the cmdlet is used for a single Client Access server, it returns the UM call router properties including
UMDialPlans. The properties and their values for the Client Access server are stored in the Unified Messaging section of the Exchange Server configuration object in Active Directory.
After this task is completed, the cmdlet returns the parameters and the values specified.
You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Client Access Server (UM call router service)" entry in the Unified Messaging Permissions topic.
The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that retrieves data from Active Directory.
The Server parameter specifies the name of the Client Access server that runs the Microsoft Exchange Unified Messaging Call Router service that's viewed. This parameter specifies the directory object ID for the UM call router.
To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.