Deployment process for integrating on-premises Unified Messaging and Lync Server 2013
Topic Last Modified: 2012-12-17
If you want to integrate Exchange Unified Messaging (UM) with Lync Server 2013, you must perform the tasks described in this topic. Also be sure that you review the planning and deployment best practices described in Guidelines for integrating on-premises Unified Messaging and Lync Server 2013. This topic assumes that you have deployed Lync Server 2013 with a collocated Mediation Server and that you have enabled users for Lync Server 2013, but not necessarily that you have performed all deployment and configuration steps to enable Enterprise Voice, as described in Deploying Enterprise Voice in Lync Server 2013 in the Deployment documentation.
Unified Messaging Integration Process
Important
It is important that you coordinate with your organization’s Exchange administrators to confirm the tasks that each of you will perform to help ensure a smooth, successful integration.
Phase | Steps | Required groups and roles | Deployment documentation |
---|---|---|---|
Deploy one of the following:
|
If you are using Microsoft Exchange Server 2013, install the following Exchange Server roles in either the same forest or a different forest as Lync Server 2013:
If Microsoft Exchange Server 2013 and Exchange Unified Messaging (UM) are installed in different forests, configure each Exchange forest to trust the Lync Server 2013 forest. If you are using Exchange 2010, install the following Exchange Server roles in either the same forest or a different forest as Lync Server 2013:
If Lync Server 2013 and Exchange Unified Messaging (UM) are installed in different forests, configure each Exchange forest to trust the Lync Server 2013 forest. |
Enterprise administrators (if this is the first Exchange Server in the organization) -OR- Exchange Organization administrator (if this is not the first Exchange Server in the organization) |
See the appropriate documentation for your version of Exchange Server:
|
Install certificates. |
Download and install certificates for each Exchange UM server from a trusted root certificate authority (CA). The certificates are required for mutual Transport Level Security (MTLS) between the servers running Exchange UM and Lync Server 2013. |
Administrators |
Configure certificates on the server running Microsoft Exchange Server Unified Messaging |
Create and configure a new Exchange UM SIP dial plan. |
On the Exchange UM server, create a SIP dial plan based on your organization’s specific deployment requirements. |
Exchange Organization administrator |
For Exchange 2007 SP1 or latest service pack, see "How to Create a Unified Messaging SIP URI Dial Plan" at https://go.microsoft.com/fwlink/p/?linkId=268632. For Exchange 2010 or latest service pack, see "Create a UM Dial Plan" at https://go.microsoft.com/fwlink/p/?linkId=268674. For Exchange 2013, see Unified Messaging at https://go.microsoft.com/fwlink/p/?LinkId=266579. |
Configure security settings for the Exchange UM SIP dial plan. |
To encrypt Enterprise Voice traffic, configure the security settings on the Exchange UM SIP dial plan as SIP Secured or Secured. This is an especially important step if you have deployed or plan to deploy Lync Phone Edition devices in your environment. For Lync Phone Edition devices to function in an environment with Exchange UM integration, Lync Server encryption settings must align with the Exchange UM dial plan security settings. For details, refer to the Deployment documentation. |
Exchange Organization administrator |
Configure Unified Messaging on Microsoft Exchange for Lync Server 2013 For Exchange 2007 SP1 or latest service pack, see also: "How to Configure Security on a Unified Messaging Dial Plan" at https://go.microsoft.com/fwlink/p/?LinkId=268696. For Exchange 2010 or latest service pack, see also: "Configure VoIP Security on a UM Dial Plan" https://go.microsoft.com/fwlink/p/?LinkId=268697. For Exchange 2013, see Unified Messaging at https://go.microsoft.com/fwlink/p/?LinkId=266579. |
Add Unified Messaging servers to the Exchange UM SIP dial plan. |
To enable a newly installed Unified Messaging server to answer and process incoming calls, you must add the Unified Messaging server to a UM dial plan. In this case, add the server to the Exchange UM SIP dial plan. |
Administrators Exchange Server administrators |
For Exchange 2007 SP1 or latest service pack, see "How to Add Unified Messaging Server to a Dial Plan" at https://go.microsoft.com/fwlink/p/?linkId=268681. For Exchange 2010 or latest service pack, see "View or Configure the Properties of a UM Server" at https://go.microsoft.com/fwlink/p/?linkId=268682. For Exchange 2013, see Unified Messaging at https://go.microsoft.com/fwlink/p/?LinkId=266579. |
Configure mailboxes with SIP addresses. |
Assign SIP addresses to the mailboxes of Enterprise Voice users who will be using Exchange UM features. |
Lync Server 2013 administrator Exchange Recipient administrator |
For Exchange 2007 SP1 or latest service pack, see "How to Add, Remove, or Modify a SIP Address for a UM-Enabled User" at https://go.microsoft.com/fwlink/p/?LinkId=268698. For Exchange 2010 or latest service pack, see "Modify a SIP Address for a UM-Enabled User" at https://go.microsoft.com/fwlink/p/?LinkId=268699. For Exchange 2013, see Unified Messaging at https://go.microsoft.com/fwlink/p/?LinkId=266579. |
Run the exchucutil.ps1 script. |
On the server running Exchange UM services, open the Exchange Management Shell and run the exchucutil.ps1 script, which does the following:
|
Exchange Organization administrator Exchange Recipient administrator |
Configure Unified Messaging on Microsoft Exchange for Lync Server 2013 |
Configure Lync Server 2013 dial plans. |
If you are integrating with Exchange 2007 SP1 or latest service pack, or Exchange 2010, create a new Enterprise Voice dial plan with a name that matches the Exchange UM dial plan fully qualified domain name (FQDN). Note You will need to do this for each UM Dial plan. If you are integrating with Exchange 2010 SP1, ensure that suitable global/site-level or pool-level Enterprise Voice dial plans have been configured. Note If you are integrating with Exchange 2010 SP1, the Lync Server dial plan and Exchange UM SIP dial plan names do not need to match. |
RTCUniversalServerAdmins |
|
Run the Exchange UM Integration tool. |
On the Lync Server 2013, run ocsumutil.exe, which:
This tool works by scanning the Active Directory for Exchange UM settings and allowing the Lync Server 2013 administrator to view, create, and edit contact objects. |
RTCUniversalServerAdmins and RTCUniversalUserAdmins Important To run ocsumutil.exe successfully, the user must belong to both of these groups. Note To create Contact objects, the user who runs ocsumutil.exe must have the correct permission to the Active Directory organizational unit (OU) where the new contact objects are stored. This permission can be granted by running the Grant-CsOUPermission cmdlet. For details, see the Lync Server Management Shell documentation. |
Configure Lync Server 2013 to work with Unified Messaging on Microsoft Exchange Server |
If necessary, perform other Enterprise Voice configuration steps. |
If you have not already configured Enterprise Voice settings on your servers or users, do one or more of the following:
Other configuration steps may be required depending on the Enterprise Voice features that you enable. |
RTCUniversalServerAdmins RTCUniversalUserAdmins |
See topics in the following sections: |
Enable Enterprise Voice users for Exchange UM. |
On the Exchange UM server, ensure that a Unified Messaging mailbox policy has been created and that each user has a unique extension number assignment, and then enable the user for Unified Messaging. |
Exchange Recipient administrator |
For Exchange 2007 SP1 or latest service pack, see "How to Enable a User for Unified Messaging" at https://go.microsoft.com/fwlink/p/?LinkId=268700. For Exchange 2010 or latest service pack, see "Enable a User for Unified Messaging" at https://go.microsoft.com/fwlink/p/?LinkId=268701. For Exchange 2013, see Unified Messaging at https://go.microsoft.com/fwlink/p/?LinkId=266579. |