Step 3. Configure Communications Server to Work with Unified Messaging on Microsoft Exchange Server

Topic Last Modified: 2009-01-23


If you are deploying Communications Server with Private Branch Exchange (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 %CommonProgramFiles%\Microsoft Office Communications Server 2007 R2\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 Server Unified Messaging settings).
  • Domain rights to create contact objects in the specified organizational unit (OU) container.

When you run the Exchange UM Integration Utility, it 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.


Before running the Exchange UM Integration Utility, you should have created one or more UM Session Initiation Protocol (SIP) dial plans, as described in Step 1. Configure Unified Messaging on Microsoft Exchange to Work with Office 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

  1. On a Front End Server, open a command prompt and then go to C:\ProgramFiles\Common Files\Microsoft Office Communications Server 2007 R2\Support\, where ocsumutil.exe is located.

  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 Contact box, accept the default organizational unit, or click Browse to start the OU Picker. In the OU Picker box, you can select an OU and click OK, or you can 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"), and then click OK.


    The distinguished name (DN) of the OU that you have selected or created is now displayed in the Organizational Unit box.

  6. In the Name box, either accept the default dial plan name or type a new user-friendly name for the contact object that you are creating.


    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: (that is, "SIP:" including the colon).

  8. 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.

  9. In the Phone Number list, select either Enter phone number or Use this pilot number from Exchange UM and then enter a phone number.

  10. In the Contact Type list, select the contact type that you want to create, and then click OK.

  11. Repeat steps 1 through 10 for additional contact objects that you want to create.


    You should create at least one contact for each auto attendant. If you want external access, you also need a Subscriber Access contact and to specify Direct Inward Dial (DID) numbers.

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.