Configure Lync Server 2013 to work with Unified Messaging on Microsoft Exchange Server
Topic Last Modified: 2013-04-03
This step requires the Exchange UM Integration Utility (OcsUmUtil.exe). This tool is located on the Lync Server 2013 server in the ..\Program Files\Common Files\Microsoft Lync Server 2013\Support folder.
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 RTCUniversalServerAdmins and RtcUniversalUserAdmins groups (which includes permission to read Exchange Server Unified Messaging settings).
User rights within the domain 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 dial plan matches its corresponding unified messaging (UM) dial plan phone context. This matching is necessary only if the UM dial plan is running on a version of Exchange earlier than Exchange 2010 Service Pack 1 (SP1).
Before running the Exchange UM Integration Utility, be sure that you have done the following:
Create one or more Exchange UM dial plans, as described in the Exchange product documentation.
For Microsoft Exchange Server 2010, see "Create a UM Dial Plan" at http://go.microsoft.com/fwlink/p/?linkId=186177.
For Microsoft Exchange Server 2007 Service Pack 1 (SP1), see "How to Create a Unified Messaging SIP URI Dial Plan" at http://go.microsoft.com/fwlink/p/?linkId=185771.
Create one or more corresponding Lync Server dial plans, as described in Create a dial plan in Lync Server 2013.
- If you are using a version of Exchange that is earlier than Microsoft Exchange Server 2010 SP1, you must enter the fully qualified domain name (FQDN) of the corresponding Exchange Unified Messaging (UM) SIP dial plan in the Lync Server 2013 dial plan Simple name field. If you are using Microsoft Exchange Server 2010 SP1 or latest service pack, this dial plan name matching is not necessary.
- Create an auto-attendant and make 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 type cd %CommonProgramFiles%\Microsoft Lync Server 2013\Support, and then press ENTER.
Type OcsUmUtil.exe, and then press ENTER.
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 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.
In the Name box, either accept the default dial plan name or type a new display 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.
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).
In the Server or Pool list, select the Standard Edition server or Front End 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 Phone Number list, select either Enter phone number or Use this pilot number from Exchange UM and then enter a phone number.
In the Contact Type list, select the contact type that you want to create, and then click OK.
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.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.