Exchange 2010: Configure Enterprise Voice with Unified Messaging (Part 1 of 2)
Enterprise Voice is an implementation of IP telephony that uses Session Initiation Protocol (SIP) for signaling and Realtime Transport Protocol (RTP) for voice messaging. Enterprise voice enables users to make voice calls to and from telephones and to other Office communicator users (PC to PC calls).
Enterprise Voice takes benefit of the Exchange 2010 Unified Messaging infrastructure to provide voice mail, subscriber access, call notification, and auto attendant services.
In this article I would be configuring integration of OCS 2007 R2 Enterprise Voice with Exchange 2010 Unified Messaging.
Scenario:
DC-01: On Windows 2008 Server core R2_Sp1, Active Directory Domain Services and Domain System Installed. My domain name used in this setup is “NG.com” (192.168.1.11)
ExCAS-01 – Exchange 2010’s Mailbox, client Access and Hub Transport Server roles installed on Windows 2008 R2 R2_Sp1 Enterprise Edition. (192.168.1.12)
ExCAS-02 – Exchange 2010’s Mailbox Server roles installed on Windows 2008 R2 R2_Sp1 Enterprise Edition. (192.168.1.16)
ExUM-01 – On Windows 2008 R2_Sp1 Enterprise Edition, Exchange 2010 sp1 with Unified Messaging Server role Installed. (192.168.1.13)
OCSFE-01 – This Machine is running OCS 2007 R2 front end server and Internal Certification Authority on Windows 2008 SP2 Enterprise Edition.
OCS front pool Name: NGOCSpool.NG.com (192.168.1.15)
SQLSVR-01- Microsoft SQL Server 2008 Enterprise Edition installed on Windows 2008 R2 Enterprise Edition. (192.168.1.14)
Gate-01: This system has Routing and Remote Access component installed on Windows 2008 R2. This system allows network routing between base network and Lab Network. (192.168.1.21)
Client-1: On this system Microsoft Office 2010 is installed on Windows 7 Sp1 Enterprise Edition. This system is part of NG.com domain. (192.168.1.20)
I would be completing configuration of Enterprise voice Integration with Unified Messaging in three steps:
Step 1: Configure Unified Messaging on Microsoft Exchange to work with OCS 2007 R2 Enterprise Voice
Step 2: Configure Unified Messaging on Microsoft Exchange to work with OCS 2007 R2 Enterprise Voice
Step3: Configuring Users for Enterprise Voice and Unified Messaging.
Step 1: Configure Unified Messaging on Microsoft Exchange to Work with Office Communications Server
To begin with configuration we need to create a UM dial plan for Unified Messaging. A UM dial plan is an Active Directory object that represents sets or groupings of IP PBXs or PBXs that share common user extension numbers. UM dial plans in Unified Messaging require that user telephone extension numbers be unique
1. Create a new Unified Messaging Dial Plan
a. On ExCAS-01, Click Start-> All Programs -> Microsoft Exchange Server 2010 -> Exchange management console.
b. In Microsoft Management console -> Click on Microsoft Exchange on-Premises -> Organization Configuration -> Unified Messaging c. In Actions pane, click New UM Dial Plan. In new UN Dial Plan Wizard, On the New UM Dial Plan Page add details as
Name: OCSUMdial
Number of Digits in Extension Number: 5
URI Type: SIP URI
VoIP Security: Secured
Country/Region Code: 1
We must associate the UM server with UM dial plan after adding to dial plan it can answer a call. You can also associate this UM server with multiple UM dial plans. You can add EXUM-01 to this dial plan on Set UM Servers page.
d. Click New to create Dial Plan
e. Following commands will be completed when you click on New Button:
New-UMDialPlan -Name ‘OCSUMdial’ -NumberOfDigitsInExtension ‘5’ -URIType ‘SipName’ -VoIPSecurity ‘Secured’ -CountryOrRegionCode ‘1’
Set-UmServer -Identity ‘EXUM-01’ -DialPlans ‘OCSUMdial’
Leave Exchange management console open.
2. Edit UM dial plan (OCSUMdial) to add subscriber access and Dialing rule groups
Subscriber Access
A subscriber is an internal business user or network user who’s enabled for Exchange 2010 Unified Messaging. Subscriber access is used by users to access their individual mailboxes to retrieve e-mail, voice messages, contacts, and calendaring information.
Dialing rule Groups
Dialing rule groups specify settings for in-country/region and international calls that will be placed by UM-enabled users from inside your organization. After you create a dialing rule group, you must add a dialing group entry. Each dialing rule entry that’s defined in the dialing rule group determines the types of calls, in-country/region or international that users within a specific dialing rule group can make when they place outgoing calls. By default, UM-enabled users aren’t allowed to dial external telephone numbers from inside the organization. However, they’re allowed to dial UM-enabled users who are associated with the same dial plan.
a. On ExCAS-01, in Exchange Management console, on the UM Dial Plan tab, right click OCSUMDial and then click Properties.
b. In subscriber Access Tab, In Field below “Telephone Number to associate:” type +14255550001, click Add.
c. Click on Dialing rule group.
d. Under In-Country / Region Rule Groups, Click Add.
e. On the Dialing Rule Entry Page, in the Name field. Type All Calls.
f. In the Number mask and Dialed Number fields, type * (asterisk Character).
A number mask is represented by a series of Xs or asterisks and replaces the number of digits that follow the prefix for a telephone number, for example, 91425xxxxxxx, or 91425*. If a number that’s dialed by a caller matches the prefix configured in the dialing rule entry, the PBX will dial the number that was specified in the Dialed number field.
g. In the comment Field, type Allow All Calls and then click OK.
h. Click OK Again. Leave Exchange Management console Open.
3. Edit the UMOCSdial Default Policy
a. In the Exchange Management console on ExCAS-01, click UM Mailbox Policies tab.
b. Right click on UMOCSdial Default Policy and then click Properties.
c. On Dialing Restrictions tab click Add under “Select Allowed in-country/region rule groups from dial plan:”.
d. Select All Calls and then click ok.
e. Click OK again.
4. Create a New Auto Attendant.
Auto attendants help internal and external callers locate users or departments that exist in an organization and transfer calls to them.
a. In the Exchange Management console, Expand Organization configuration, click Unified Messaging, and then in the Actions pane, click New UM Auto Attendant.
b. Add following details, and then click New.
Name: NG_AA
Select Associated Dial Plan: OCSUMdial
Pilot Identifier list: +14255550000
Check Auto Attended as enabled
Check Create auto attendant as Speech-enabled.
5. Run ExchUCUtil.ps1 to configure connectivity with OCS 2007 R2.
a. On ExCAS-01, open Exchange Management Shell, at the PS Prompt, type the following and then press Enter:
Cd “C:\Program Files\Microsoft\Exchange Server\V14\Scripts”
b. At the PS Prompt, type the following and then press Enter:
.\ExchUCUtil.ps1
Wait for script to finish. Leave the Exchange management Shell running.
c. See results of script in screenshot below:
d. The UM IP Gateway and Hunt Group are created using the script ExchUCUtil.ps1.
6. Set Port No for the UM IP gateway created by ExchUCUtil.ps1. It will allow SIP communication.
a. At Exchange Management Shell command prompt type and press ENTER:
Set-UMIPGateway -Identity NGOCSpool -Port 5061
Wait for the script to finish. There will not be any output from this command. Leave the Exchange management Shell running.
7. Get the PhoneContext of the UM Dial Plan
a. At Exchange Management Shell Command prompt type the following and then press ENTER:
(Get-UMDialPlan OCSUMDial).PhoneContext
Leave the Exchange management Shell running.
In Part2 I would continuing with Step2 and Step3 of configuration