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

1. In the console tree, navigate to Organization Configuration > Unified Messaging.
   
   
2. In the action pane, click New UM Dial Plan.
   
   
3. In the New UM Dial Plan wizard, complete the following fields:
   
   
   • Name   Type the name of the dial plan. A UM dial plan name is required and must be unique. However, the name you type is used only for display purposes in the EMC and the Shell. If you have to change the display name of the dial plan after it's been created, you must first delete the existing UM dial plan and then create another dial plan that has the appropriate name. If your organization uses multiple UM dial plans, we recommend that you use meaningful names for your UM dial plans. The maximum length of a UM dial plan name is 64 characters, and it can include spaces. However, it can't include any of the following characters: " / \ [ ] : ; | = , + * ? < >.
     
     

     Important:
     Although the field for the name of the dial plan can accept 64 characters, the name of the dial plan can't be longer than 49 characters. This is because, when you create a dial plan, a default UM mailbox policy is also created that has the name <DialPlanName> Default Policy. The name parameter for both the UM dial plan and UM mailbox policy can be 64 characters long.

   • Number of digits in extension numbers   Enter the number of digits for extension numbers in the dial plan. The number of digits for extension numbers is based on the telephony dial plan created on a Private Branch eXchange (PBX). For example, if a user associated with a telephony dial plan dials a four-digit extension to call another user in the same telephony dial plan, you select 4 as the number of digits in the extension.
     
     This is a required field that has a value range from 1 through 20. The typical extension length is from 3 through 7. If your existing telephony environment includes extension numbers, you must specify a number of digits that matches the number of digits in those extensions.
     
     When you create a Session Initiation Protocol (SIP) dial plan or an E.164 dial plan and associate a UM-enabled user with the dial plan, you must still enter an extension number to be used by the user. This number is used by Outlook Voice Access users when they access their Exchange 2010 mailbox.
     
     
   • URI Type   Use this drop-down list to select the URI type for the UM dial plan. A URI is a string of characters that identifies or names a resource. The main purpose of this identification is to enable VoIP devices to communicate with other devices over a network using specific protocols. URIs are defined in schemes that define a specific syntax, format, and the protocols for the call.
     
     You can select one of the following URI types for the dial plan:
     
     Telephone extension   This is the most common URI type. The calling and called party information from the IP gateway or IP PBX will be listed in one of the following formats: Tel:512345 or 512345@<IP address>. This is the default URI type for dial plans.
     
     SIP URI   Use this URI type if you need a SIP URI dial plan when an IP PBX supports SIP routing or if you're integrating Microsoft Office Communications Server 2007 and Exchange Unified Messaging. The calling and called party information from the IP gateway or IP PBX will be listed as a SIP address in the following format: sip:<username>@<domain or IP address>:Port.
     
     E.164   E.164 is an international numbering plan for public telephone systems in which each assigned number contains a country/region code, a national destination code, and a subscriber number. The calling and called party information sent from the IP gateway is listed in the following format: Tel:+14255550123.
     
     

     Note:
     After you create a dial plan, you will be unable to change the URI type without deleting the dial plan, and then re-creating the dial plan to include the correct URI type.

   • VoIP Security   Use this drop-down list to select the VoIP security setting for the UM dial plan. By default, when you create a UM dial plan, it communicates in unsecured mode. A Unified Messaging server can operate in any mode configured on a dial plan because the Unified Messaging server is configured to listen on TCP port 5060 for unsecured requests and on TCP port 5061 for secured requests at the same time.
     
     You can select one of the following security settings for the dial plan:
     
     Unsecured   By default, when you create a UM dial plan, it communicates in unsecured mode, and the Unified Messaging servers associated with the UM dial plan send and receive data from IP gateways, IP PBXs, and other Exchange 2010 computers using no encryption. In unsecured mode, both the Realtime Transport Protocol (RTP) media channel and SIP signaling information aren't encrypted.
     
     SIP secured   When you select SIP secured, only the SIP signaling traffic is encrypted, and the RTP media channels still use TCP, which isn't encrypted. Mutual Transport Layer Security (TLS) is used to encrypt the SIP signaling traffic.
     
     Secured   When you select Secured, both the SIP signaling traffic and the RTP media channels are encrypted. An encrypted signaling media channel that uses Secure Realtime Transport Protocol (SRTP) also uses mutual TLS to encrypt the VoIP data.
     
     
   • Country/Region code   Use this field to type the country/region code number to be used for outgoing calls. This number will automatically be prepended to the telephone number that's dialed. This field accepts from 1 through 4 digits. For example, in the United States, the country/region code is 1. In the United Kingdom, it's 44.
     
     
4. On the Set UM Servers page, click Add and then on the Select UM Server page select the UM server that you want to add to the UM dial plan.
   
   
5. On the Completion page, confirm whether the dial plan was successfully created:
   
   
   • A status of Completed indicates that the wizard completed the task successfully.
     
     
   • A status of Failed indicates that the task wasn't completed. If the task fails, review the summary for an explanation, and then click Back to make any configuration changes.
     
     
6. Click Finish to complete the New UM Dial Plan wizard.
   
   

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

This example creates a new UM dial plan named MyUMDialPlan that uses four-digit extension numbers.

	Copy Code
New-UMDialplan -Name MyUMDialPlan -NumberofDigits 4

This example creates a new UM dial plan named MyUMDialPlan that uses five-digit extension numbers and supports SIP URIs:

	Copy Code
New-UMDialplan -Name MyUMDialPlan -UriType SIPName -NumberofDigits 5

For more information about syntax and parameters, see Set-UMDialplan.

Return to top

1. In the console tree, navigate to Organization Configuration > Unified Messaging.
   
   
2. In the result pane, click the UM IP Gateways tab.
   
   
3. In the action pane, click New UM IP Gateway.
   
   
4. In the New UM IP Gateway wizard, in the Name section, type the name of the UM IP gateway. This is the display name for the UM IP gateway.
   
   
5. In the IP Address section, type the IP address for the UM IP gateway, and then click New.
   
   

   Note:
   Alternatively, you can enter an FQDN for the UM IP gateway. If you choose to use an FQDN, you must add the appropriate host records with the correct IP addresses to the DNS zone. If you're configuring a UM IP gateway that will be associated with a dial plan that's operating in Secured mode, you must create the UM IP gateway with an FQDN.

6. On the New UM IP Gateway page, click New.
   
   
7. On the Completion page, click Finish.
   
   

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

This example creates a UM IP gateway named MyUMIPGateway that enables a Unified Messaging server to start accepting calls from an IP gateway that has an IP address of 10.10.10.1.

	Copy Code
New-UMIPGateway -Name MyUMIPGateway -Address 10.10.10.1

This example creates a UM IP gateway named MyUMIPGateway that enables a Unified Messaging server to start accepting calls from an IP gateway that has an FQDN of MyUMIPGateway.contoso.com and listens on port 5061.

	Copy Code
New-UMIPGateway -Name MyUMIPGateway -Address "MyUMIPGateway.contoso.com" -Port 5061

For more information about syntax and parameters, see New-UMIPGateway.

Return to top

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

1. In the console tree, navigate to Organization Configuration > Unified Messaging.
   
   
2. In the work pane, click the UM IP Gateways tab.
   
   
3. In the result pane, select a UM IP gateway.
   
   
4. In the action pane, click New UM Hunt Group.
   
   
5. In the New UM Hunt Group wizard, view or complete the following fields:
   
   
   • Associated UM IP gateway   This display-only field shows the name of the UM IP gateway that will be associated with the UM hunt group.
     
     
   • Name   Use this text box to create the display name for the UM hunt group. A UM hunt group name is required and must be unique, but it's used only for display purposes in the EMC and the Shell. If you have to change the display name of the hunt group after it's been created, you must first delete the existing hunt group and then create another hunt group that has the appropriate name.
     
     If your organization uses multiple hunt groups, we recommend that you use meaningful names for your hunt groups. The maximum length of a UM hunt group name is 64 characters, and it can include spaces. However, it can't include any of the following characters: " / \ [ ] : ; | = , + * ? < >.
     
     
   • Dial plan   Click the Browse button to select the dial plan that will be associated with the UM hunt group. Associating a hunt group with a dial plan is required. A UM hunt group can be associated with only one UM IP gateway and one UM dial plan.
     
     
   • Pilot identifier   Use this text box to specify a string that uniquely identifies the pilot identifier or pilot ID configured on the PBX or IP PBX.
     
     An extension number or a SIP URI can be used in this field. Alphanumeric characters are accepted in this field. For legacy PBXs, a numeric value is used as a pilot identifier. However, some IP PBXs can use SIP URIs.
     
     
6. On the Completion page, confirm whether the UM hunt group was successfully created:
   
   
   • A status of Completed indicates that the wizard completed the task successfully.
     
     
   • A status of Failed indicates that the task wasn't completed. If the task fails, review the summary for an explanation, and then click Back to make any configuration changes.
     
     
7. Click Finish to complete the New UM Hunt Group wizard.
   
   

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

This example creates a UM hunt group named MyUMHuntGroup that has a pilot identifier of 12345.

	Copy Code
New-UMHuntGroup -Name MyUMHuntGroup -PilotIdentifier 12345 -UMDialplan MyUMDialPlan -UMIPGateway MyUMIPGateway

This example creates a UM hunt group named MyUMHuntGroup that has multiple pilot identifiers.

	Copy Code
New-UMHuntGroup -Name MyUMHuntGroup -PilotIdentifier 5551234,55555 -UMDialplan MyUMDialPlan -UMIPGateway MyUMIPGateway

For more information about syntax and parameters, see New-UMHuntGroup.

Return to top

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

1. In the console tree, navigate to Organization Configuration > Unified Messaging.
   
   
2. In the work pane, click the UM Mailbox Policies tab.
   
   
3. In the action pane, click New UM Mailbox Policy.
   
   
4. In the New UM Mailbox Policy wizard, complete the following fields:
   
   
   • Name   Use this text box to specify a unique name for the UM mailbox policy. If you must change the display name of the UM mailbox policy after it's been created, you must first delete the existing UM mailbox policy, and then create another UM mailbox policy that has the appropriate name. To delete the UM mailbox policy, there must not be any UM-enabled users associated with the UM mailbox policy.
     
     The UM mailbox policy name is required, but it's used for display purposes only. Because your organization may use multiple UM mailbox policies, we recommend that you use meaningful names for your UM mailbox policies. The maximum length of a UM mailbox policy name is 64 characters, and it can include spaces. However, it cannot include any of the following characters: " / \ [ ] : ; | = , + * ? < >.
     
     
   • Select associated dial plan   Click Browse to select the UM dial plan that will be associated with the UM mailbox policy. You must associate a UM mailbox policy with at least one UM dial plan. However, you can also associate multiple UM mailbox policies with a single dial plan.
     
     
5. On the Completion page, confirm whether the UM mailbox policy was successfully created:
   
   
   • A status of Completed indicates that the wizard completed the task successfully.
     
     
   • A status of Failed indicates that the task wasn't completed. If the task fails, review the summary for an explanation, and then click Back to make any configuration changes.
     
     
6. Click Finish to complete the New UM Mailbox Policy wizard.
   
   

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

This example creates a UM mailbox policy named MyUMMailboxPolicy associated with a UM dial plan named MyUMDialPlan.

	Copy Code
New-UMMailboxPolicy -Name MyUMMailboxPolicy -UMDialPlan MyUMDialPlan

For more information about syntax and parameters, see New-UMMailboxPolicy.

Return to top

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

1. In the console tree, click Server Configuration.
   
   
2. In the result pane, select the Unified Messaging server you want to add to a dial plan.
   
   
3. In the action pane, click Properties.
   
   
4. On the UM Settings > Associated Dial Plans, click Add.
   
   
5. In the Select Dial Plan window, from the list of available dial plans, select the dial plan you want to add the UM server to, and then click OK.
   
   

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

This example adds a Unified Messaging server to a dial plan named MyUMDialPlan and prevents the UM server from accepting new calls. It also sets the startup mode to dual mode, which enables the UM server to accept TCP and TLS requests.

	Copy Code
Set-UMServer -Identity MyUMServer -DialPlans MyUMDialPlan -Status Disabled -UMStartupMode Dual

This example adds the Unified Messaging server named MyUMServer to two UM dial plans, named MyUMDialPlan and MyUMDialPlan2, and also sets the maximum number of incoming voice and fax calls.

	Copy Code
Set-UMServer -Identity MyUMServer -DialPlans MyUMDialPlan, MyUMDialPlan2 -MaxCallsAllowed 50

For more information about syntax and parameters, see Set-UMServer.

Return to top

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

1. In the console tree, navigate to Organization Configuration > Unified Messaging.
   
   
2. In the work pane, click the UM Auto Attendants tab.
   
   
3. In the action pane, click New UM Auto Attendant.
   
   
4. In the New UM Auto Attendant wizard, complete the following fields:
   
   
   • Name   Use this text box to create the display name for the UM auto attendant. A UM auto attendant name is required and must be unique. However, it's used only for display purposes in the EMC and the Shell.
     
     If you have to change the display name of the auto attendant after it's created, you must first delete the existing UM auto attendant and then create another UM auto attendant that has the appropriate name. If your organization uses multiple UM auto attendants, we recommend that you use meaningful names for your UM auto attendants. The maximum length of a UM auto attendant name is 64 characters, and it can include spaces.
     
     
   • Select associated dial plan   Click Browse to select the UM dial plan to associate with this UM auto attendant. Selecting and associating a UM dial plan with the auto attendant is required. A UM auto attendant can be associated with only one UM dial plan.
     
     
   • Extension numbers   Use this field to enter the extension number that callers will use to reach the auto attendant. Type an extension number in the box, and then click Add to add the number to the list. The number of digits in the extension number that you provide doesn't have to match the number of digits for an extension number configured on the associated UM dial plan. This is because direct calls are allowed to UM auto attendants.
     
     You can also create a new auto attendant without adding an extension number, because an extension number isn't required.
     
     You can edit or remove an existing extension number. To edit an existing extension number, click Edit. To remove an existing extension number from the list, click Remove.
     
     
   • Create auto attendant as enabled   Select this option to enable the auto attendant to answer incoming calls when you complete the New UM Auto Attendant wizard. By default, a new auto attendant is created as disabled.
     
     If you decide to create the UM auto attendant as disabled, you can use the EMC or the Shell to enable the auto attendant after you finish the wizard.
     
     
   • Create auto attendant as speech-enabled   Select this check box to speech-enable the UM auto attendant. When you speech-enable the auto attendant, callers will be able to respond to the system or custom prompts used by the UM auto attendant using touchtone or voice inputs. By default, the auto attendant won't be speech-enabled when it's created.
     
     For callers to use a speech-enabled auto attendant, you must install the appropriate Unified Messaging language pack that contains Automatic Speech Recognition (ASR) support and configure the properties of the auto attendant to use this language.
     
     
5. On the Completion page, confirm whether the UM auto attendant was successfully created:
   
   
   • A status of Completed indicates that the wizard completed the task successfully.
     
     
   • A status of Failed indicates that the task wasn't completed. If the task fails, review the summary for an explanation, and then click Back to make any configuration changes.
     
     
6. Click Finish to complete the New UM Auto Attendant wizard.
   
   

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

This example creates a UM auto attendant named MyUMAutoAttendant that can accept incoming calls but isn't speech-enabled.

	Copy Code
New-UMAutoAttendant -Name MyUMAutoAttendant -UMDialPlan MyUMDialPlan -PilotIdentifierList 55000 -Enabled $true

This example creates a speech-enabled UM auto attendant named MyUMAutoAttendant.

	Copy Code
New-UMAutoAttendant -Name MyUMAutoAttendant -UMDialPlan MyUMDialPlan -PilotIdentifierList 56000,56100 -SpeechEnabled $true

For more information about syntax and parameters, see New-UMAutoAttendant.

After you've created a non-speech-enabled or a speech-enabled auto attendant, you must create and configure key mappings so that the auto attendant can function correctly. If you don't enable key mappings for either business or non-business hours, callers will hear the voice prompts but won't be able to interact with the auto attendant. To create key mappings for an auto attendant, see the following topics:

• Enable Business Hours Key Mappings on a UM Auto Attendant
  
  
• Enable Non-Business Hours Key Mappings on a UM Auto Attendant
  
  
• Configure Key Mapping Entries on a UM Auto Attendant
  
  

Return to top