Step 3. Configure Communications Server to Work with Exchange UM
Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
Important
If you are deploying Communications Server with PBX integration, skip this step and go to Step 4. Assign Location Profile to Pool.
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.
Important
Before running the Exchange UM Integration Utility, you should have created one or more UM SIP dial plans, as described in Step 1. Configure Exchange UM to Work with Communications Server, and a Communications Server location profile for each dial plan, as described in Step 2. Create Location Profiles.
You also should have created an auto-attendant and made sure that both the subscriber access number and auto-attendant number are in E.164 format.
To run the Exchange UM Integration Utility
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.)
Double-click OcsUMUtil.exe.
.jpg "7d2ff45c-ca2b-40eb-bf04-eb63d0848739")
Click Load Data to find all trusted Exchange forests.
In the SIP Dial Plans list, select a UM SIP dial plan for which you want to create contact objects, and then click Add.
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.
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.
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:.
In the list, select the SIP domain for the contact object.
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.
In the Contact Type list, select the contact type that you want to create, and then click OK.
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.