I put together this configuration note for integrating OCS 20007 and Exchange 2007 UM. Excertps from Microsoft Technet.
Exchange 2007 UM and Office Communications Server 2007 Interoperability Configuration Notes
The following tools will be required:
· The Exchange 2007 SP1 Management Shell also known as “PowerShell”
· The script exchucutil.ps1, which performs the following tasks:
o Creates a UM IP gateway for each Communications Server 2007 Enterprise Pool.
o Creates a hunt group for each gateway. (The pilot identifier of each hunt group specifies the UM dial plan used by the Enterprise Pool that is associated with the gateway.)
o Grants Communications Server Permission to read Exchange UM objects in Active Directory.
The script exchucutil.ps1 is by default installed in <exchange_install_directory>\Scripts\
Requirements and Recommendations
· Make sure that you have deployed the following Exchange server roles either (in the same or a different forest as Communications Server 2007): Hub Transport, Client Access, Mailbox, and Unified Messaging.
Also note the following:
· If Exchange UM is installed in multiple forests, the Exchange integration steps must be performed for each Um forest. In addition, each UM forest must be configured to trust the forest in which Communications server is deployed.
· The integration steps are performed on both Exchange UM server and Communications Server. You should perform the Exchange Um integration steps before you do the Communications Server integration steps.
Configuring Exchange Um to work with Enterprise Voice consists o the following tasks:
· Creating one or more UM dial plans as needed, and the creating corresponding location profiles.
· Creating a Sip URI for each user and associating users with a UM dial plan.
· Using the exchucutil.ps1 script to:
o Create UM IP gateways.
o Create UM hunt groups.
o Grant Communications Server permission to read UM Active Directory objects.
· Creating a UM auto-attendant object.
Configuring Exchange UM using Exchucutil.ps1
1. Create a UM dial plan for each of your Enterprise Voice location profiles. If you choose to use the Exchange Management Console, create a new dial plan with the security setting SIP Secured. If you use the Exchange Management Shell, type the following script:
new-umdialplan -name <dial plan name> -UriType “SipName” -VoipSecurity <SIPSecured|Secured> -NumberOfDigitsInExtension <number of digits> -AccessTelephoneNumbers <access number in E.164 format>
For Exammple:
new-umdialplan -name SFUmDialPlan -UriType “SipName” -VoipSecurity SIPSecured -NumberOfDigitsInExtension 4 -AccessTelephoneNumbers 1162
Important
The dial plan name that you create must also be a valid Communications Server location profile name. Therefore, it must contain no more than 256 alphanumeric characters and must not contain spaces or special characters other than hyphens (-) or periods (.).
2. Obtain the FQDN for each UM dial plan.
(Get-UMDialPlan <dialplanname>).PhoneContext
Example:
(Get-UMDialPlan SFUMDialPlan).PhoneContext
3. Record the dial plan name of each UM dial plan. You will use the FQDN of each dial plan name later as the name of each UM dial plans corresponding Communications Server location profile.
4. Add the dial plan to the UM server. If you choose to use the Exchange Management Console, you can add the dial plan from the property sheet for the server. For specific instructions, see your Exchange 2007 SP1 documentation. If you use the Exchange Management Shell, type the following script:
$ums=get-umserver;
$dp=get-umdialplan –id <name of dial-plan created in step 1>;
$ums.DialPlans +=$dp.Identity;
$ums | set-umserver
Example:
$ums=get-umserver;
$dp=get-umdialplan –id SFUmDialPlan>;
$ums.DialPlans +=$dp.Identity;
$ums | set-umserver
5. Navigate to <Exchange installation directory>\Scripts, and then if Exchange is deployed in a single forest, type:
exchucutil.ps1
exchucutil.ps1 –verify
If Exchange is deployed in multiple forests, type:
exchucutil.ps1 -Forest:”<forest FQDN>” for multiple forest deployments
where forest FQDN specifies the forest in which Office Communications Server is deployed.
6. Create a UM auto-attendant for each Communications Server location profile.
New-umautoattendant -name <auto attendant name> -umdialplan < name of dial plan created in step 1> -PilotIdentifierList <auto attendant phone number in E.164 format> -SpeechEnabled $true -Status Enabled
Example:
New-umautoattendant -name SFUMAutoAttendant -umdialplan SFUMDialPlan -PilotIdentifierList 1165 -SpeechEnabled $true -Status Enabled
Office Communications Server 2007 Configuration:
This step requires the Exchange UM Integration Utility (ocsumutil.exe). This tool is located on the Office Communications Server at <installation directory>\Microsoft Office Communications Server 2007\Server\Support.
Running the Exchange UM Integration Utility
The Exchange UM Integration Utility must be run from a user account with the following characteristics:
· Membership in the RTCUniversalUserAdmins group (which includes rights to read Exchange UM settings).
· Domain rights to create contact objects in the specified OU container.
The Exchange UM Integration Utility performs the following tasks:
· Creates contact objects for each auto-attendant and subscriber access number to be used by Enterprise Voice users.
· Verifies that the name of each Enterprise Voice location profile matches its corresponding UM dial plan phone context.
To run the Exchange UM Integration Utility
1. On a Front End Server, open a command prompt and then go to <installation directory>\Microsoft Office Communications Server 2007\Server\Support, where ocsumutil.exe is located. (Or open Windows Explorer, navigate to this folder, and then double-click OcsUMUtil.exe.)
2. Double-click OcsUMUtil.exe.
3. Click Load Data to find all trusted Exchange forests.
4. In the SIP Dial Plans list, select a UM SIP dial plan for which you want to create contact objects, and then click Add.
5. In the OU Picker box, either select the OU you want and click OK, or click Make New OU to create a new organizational unit under the root or any other OU in the domain. For example, “OU=RTC Special Accounts,DC=fourthcoffee,DC=com.” When you finish, click OK. The distinguished name of the organizational unit that you have selected or created is now displayed on the Contact box in Organizational Unit.
6. In the Contact box, either accept the default dial plan name or type a new user-friendly name for the contact object that you are creating in the Name box. For example, if you are creating a subscriber access contact object, you might simply name it Subscriber Access.
7. In the SIP Address box, either accept the default SIP address or type a new SIP address. If you type a new SIP address, it must begin with SIP:.
8. In the list, select the SIP domain for the contact object.
9. In the Server or Pool list, select the Standard Edition Server or Enterprise Pool in which the contact object is to be enabled. Preferably, the pool you select is the same one pool where users enabled for Enterprise Voice and Exchange UM are deployed.
10. In the Contact Type list, select the contact type that you want to create, and then click OK.
11. Repeat steps 1 through 11 for additional contact objects that you want to create. You should create at least one contact for each auto attendant and, if you want external access, you also need a Subscriber Access contact.
To verify that the contact objects have been created, open Active Directory Users and Computers and select the OU in which the objects were created. The contact objects should appear in the details pane.
Enable the users for UM in the Exchange management console. After the are enabled you should be able to choose “Call VoiceMail” from the Microsoft Office Communicator Client.
