Before configuring Exchange UM Server as the voice mail system for Office Communications Server, Exchange Server and Office Communications Server must already be deployed in the enterprise. Users must be configured with an Exchange mailbox and be enabled for Enterprise Voice. This chapter covers the steps specific to configuring Exchange UM to integrate with Office Communications Server.
This integration requires the following steps.
Give Office Communications Server servers read-only permissions to the Exchange UM objects in Active Directory.
Create the corresponding Exchange UM IP gateway objects in Active Directory for every Standard Edition Server and Enterprise pool.
Assign the UM IP gateways to every Unified Communications (UC)–related UM Dial Plan.
Create special contact objects for every UM subscriber access and Auto-Attendant.
Map Office Communications Server location profiles with Exchange UM Dial Plans.
To configure Exchange UM Server as the voice mail system for Office Communications, the following steps must be performed.
Configuring the Exchange UM Servers
Creating a UM Dial Plan for every location profile
Configuring the subscriber access number
Running the Microsoft Windows PowerShell tool ExchUCUtil.ps1
Creating a UM Auto-Attendant
Configuring users for Exchange UM
Exchange UM Servers must be configured with a server certificate issued by a certificate authority (CA) trusted by the Office Communications Server servers. If the Office Communications Server servers’ certificates were issued by an internal Certificate Server, then the Exchange UM Server certificate must be issued by the same CA. The certificate’s subject name must match the Exchange UM Server’s fully qualified domain name (FQDN). Install this certificate in the Local Computer store. It is recommended to restart the Exchange UM Servers after installing the server certificate.
Note
Confirm the UM Server has loaded the correct certificate by examining event 1112 under the system event log.
Next, the server certificate must be enabled for UM. On the Exchange UM Server, find the thumbprint of the certificate configured in step 1 by calling the Powershell command Get-ExchangeCertificate. This command will return the thumbprint of all server certificates configured on the server. Using the thumbprint returned, call the PowerShell command Enable-ExchangeCertificate to enable the UM service on the certificate:
Get-ExchangeCertificate Enable-ExchangeCertificate -thumbprint <value> -services UM
For every Office Communications Server location profile defined, create a corresponding UM Dial Plan. The name of the Dial Plan must match the name of the corresponding location profile. A UM Dial Plan is a logical representation of a telephony Dial Plan. In the case of Office Communications Server, this telephony Dial Plan is equivalent to a location profile. Therefore, a UM Dial Plan is equivalent to a location profile. The number of digits specified in the UM Dial Plan is recommended to match the number of digits defined in Office Communications Server as the extension number of users enabled for Enterprise Voice. In large organizations, this extension is often five digits. A UM Dial Plan establishes a link from the telephone extension number of an Exchange 2007 recipient in Active Directory to a UM-enabled mailbox. Each time that you create a UM Dial Plan, a UM Mailbox policy is also created. The UM Mailbox policy is named "<DialPlanName> Default Policy".
To create the UM Dial Plan using Exchange Server PowerShell, use the following command:
new-umdialplan -name <Dial Plan name> -UriType "SipName" -VoipSecurity SIPSecured -NumberOfDigitsInExtension <number of digits> [-AccessTelephoneNumbers <access number in E.164 format>]
Note
The AccessTelephoneNumbers field is optional and necessary only if creating a subscriber access number.
To create the UM Dial Plan by using Exchange Server Management Console, refer to Figure 12-10 and perform the steps that follow it.
Navigate to the UM Dial Plans tab in the Unified Messaging node under the Organization Configuration tree.
Click New UM Dial Plan in the action pane.
Specify a name for the UM Dial Plan that matches the name of a corresponding location profile created in Office Communications Server.
Select SIPName as the URI type.
Select SIPSecured as the VoIP security setting. If using Office Communicator Phone Edition, select Secured.
Complete the New UM Dial Plan Wizard.
Associate the Exchange UM Server with the Dial Plan created. To do this, use the following command:
$umsrv = get-umserver; $dp = get-umdialplan -id <name of dial-plan created in step 1>; $umsrv.DialPlans +=$dp.Identity; $umsrv | set-umserver
To associate the Dial Plan with the UM Server by using the Exchange Server Management Console, refer to Figure 12-11 and perform the steps that follow it.
The subscriber access number permits UM-enabled users to call the Exchange UM Server. After authenticating using their PIN, users can access their mailbox, calendar, and address book from any phone. To configure the subscriber access number:
Run ExchUCUtil.ps1 by using an administrative account with membership in RTCUniversalServerReadOnlyGroup and Exchange Organization Administrators. This tool grants the RTCComponentUniversalServices group read-only permissions to the Exchange UM objects in Active Directory. It also creates a corresponding UM IP gateway object in Active Directory that corresponds to every Office Communications Server and Enterprise pool front-end server deployed in the forest. It then associates each of these UM IP gateways with every UM Dial Plan created.
Run this command from Exchange UM Server PowerShell:
Cd %ProgramFiles%MicrosoftExchange ServerScripts exchUCUtil.ps1 exchUCUtil.ps1 -verify (to verify configuration)
If you plan to provide a company main phone number that external users can call, then you’ll want to create a UM Auto-Attendant for the UM Dial Plan created. If you choose not to create a UM Auto-Attendant, skip this step. Make sure to specify the Auto-Attendant’s phone number in E.164 format recognized by Office Communications Server; otherwise, Office Communications Server will not be able to properly route it.
To create a UM Auto-Attendant by using Exchange Server PowerShell, use the following command:
New-umautoattendant -name <auto attendant name> -umdialplan < Dial Plan name (step 2)> -PilotIdentifierList <auto attendant phone number in E.164 format> -SpeechEnabled $true -Status Enabled
To create a UM Auto-Attendant by using the Exchange Server Management Console, refer to Figure 12-12 and perform the steps that follow it.
Navigate to the UM Auto Attendant tab in the Unified Messaging node under the Organization Configuration tree.
Click New UM Auto Attendant in the action pane.
Specify a name for the Auto-Attendant.
Click Browse to select the UM Dial Plan created.
Specify an extension number in E-164 format.
Check Create Auto Attendant As Enabled.
Check Create Auto Attendant As Speech-Enabled.
Complete the New UM Auto Attendant Wizard.
Enable users for UM. By default, users enabled with an Exchange mailbox are not enabled for UM.
To enable a user for UM by using Exchange Server PowerShell, use the following command:
enable-ummailbox -identity <user alias> -ummailboxpolicy <name of the mailbox policy for UM Dial Plan (step 2)> -Extensions <extension> -SIPResourceIdentifier "<user SIP URI>" -PIN <user pin>
To enable a user for UM by using the Exchange Server Management Console, refer to Figure 12-13 and perform the steps that follow it.
Navigate to the Mailbox node under the Recipient Configuration tree.
Select the user to enable for UM.
Click Enable Unified Messaging in the action pane.
Select the UM Mailbox policy associated with the UM Dial Plan created.
Verify that the correct SIP URI for the user is specified in the SIP Resource Identifier field.
Complete the Enable Unified Messaging Wizard.
To configure Office Communications Server as the VoIP gateway for Exchange UM Server, run the tool, OcsUMutil.exe. This Exchange UM Integration Utility as shown in Figure 12-14 provides a graphical user interface (GUI) to create contact objects in Active Directory for every Auto-Attendant and subscriber access associated with the UM Dial Plan created. If the UM Dial Plan defines a pilot number, a subscriber access contact object must be created in Active Directory. The contact object makes it possible for Office Communications Server to route the phone number. This tool also verifies that there is a location profile name that matches the name of the UM Dial plan created.
%ProgramFiles%Common FilesMicrosoft Office Communications Server 2007 R2Support ocsumutil.exe
Click Load Data to find all trusted Active Directory forests.
In the SIP Dial Plans list, select the UM Dial Plan created earlier in the chapter, and click Add.
Click Browse... to the right of the Organizational Unit field and then select an organizational unit (OU), or click Make New OU to create a new OU where the contact object will be created. Click OK when you finish.
In the Name field, either accept the default Dial Plan name or type a new user-friendly name for the contact object to create. For example, if you are creating a subscriber access contact object, you might simply name it Subscriber Access.
In the SIP Address field, specify a new SIP address or leave the default. It must begin with SIP.
Select the Enterprise pool or Standard Edition Server to home the contact object. Preferably, you should select the same pool where users enabled for Enterprise Voice and Exchange UM are also homed in.
In the Phone Number field, select the radio option, "use this pilot number from Exchange UM".
In the Contact Type field, select the contact type (Subscriber Access or Auto-Attendant) to create and click OK.
Repeat steps 1–9 for additional contact objects you want to create. You should create at least one contact object for each Auto-Attendant and each subscriber access number.
Confirm you can access your voice mail by selecting Call Voice Mail, as shown in the section titled "Overview of Voice Mail Scenarios" earlier in this chapter.