Module3

Designing Exchange Server 2013 Unified

Messaging Integration with Lync Server 2013

MVA Jump Start

Module Overview

• Overview of Exchange Server 2013 Unified Messaging

• Integrating UM with Lync Server 2013
Overview of Exchange Server 2013 Unified Messaging

• Architecture
• UM Listening Ports
Architecture

• Exchange Server 2013

• Client Access Server (CAS) CAS
UM Call Router
• Mailbox Server (MBX) Redirect

• Lync Server 2013

• FE is IP Gateway to Exchange
• Inbound Routing
MBX
• Exchange UM Routing UM Service

Signaling (SIP)
Media (RTP)
UM Listening Ports
Integrating UM with Lync Server 2013

• Create Exchange SIP URI Dial Plan

• Configure Exchange UM Startup
• Configure Certificates
• Run ExchUCUtil.ps1
• Configure Lync Server 2013 to work with UM
• Voicemail Routing
• Exchange Call Authorization and Routing
• Subscriber Access Number
• Secondary Dial Plan Support
http://technet.microsoft.com/en-us/library/bb676409(v=exchg.150).aspx
Creating a New Dial Plan

1. Create the Exchange UM dial plan

• Type: SIP URI
• Security mode: Secured

2. Add all CAS and MBX servers to dial plan

• Required so that Lync can trust the UM servers
to send calls

Set-UMService ExBE1 -DialPlans "North America"

Set-UMCallRouterSettings ExFE1 -DialPlans "North America"
Setting the Startup Mode of the UM Server

3. Set StartupMode to TLS or Dual (if integrating with TCP gateways)

Set-UMService ExBE1 -UMStartupMode TLS

Set-UMCallRouterSettings ExFE1 - UMStartupMode TLS

4. Open the Exchange Management

Shell and run:

%Program Files%\Microsoft\
Exchange Server\V15\Scripts\
ExchUCUtil.ps1
Certificate Recommendations

• Import a certificate that's valid and signed by a private or public CA

• When deploying TLS with UM, you must:
– Use local computer’s FQDN in certificate’s Subject Name (SN)
– Applies to certificates used for Client Access and Mailbox servers

• Using same root CA for all certificates is less complex

• A non-wildcard Subject Name required for Lync Server and Exchange
to work together
Running ExchUCUtil.ps1

• Grants Lync Server permission to read Exchange UM Active Directory

components, specifically, the SIP URI dial plans
• Creates UM IP gateways
• Creates an Exchange UM hunt group for each UM IP gateway
Configuring Lync Server 2013 to work with UM

• Users may now be enabled for Unified Messaging and calling from
Lync will be possible
5. OCSUmUtil.exe is used to create special contact objects that allow
PSTN dialing to Subscriber Access and Auto Attendants.
Voicemail Routing

• InboundRouting
Inbound
• Adds opaque=app:exum (for an Exchange UM application)
Routing
• Or, app:voicemail (for the user’s voicemail server)
• ExumRouting
• Adds Diversion header when a call has been diverted to Exum
Exchange UM voicemail. Routing
• It will be the user’s SIP URI

• Summary: Exchange
• InboundRouting decides that the call should go to Exchange UM
(either voicemail deposit or auto attendant)
• ExumRouting gets the call to Exchange
Exchange Call Authorization and Routing

• Use Lync Server voice policies instead of Exchange dial codes, rules,
and authorization
• Lync Outbound Routing will apply Lync Server voice policy to use
based on function generating call
• Authenticated caller: use Enterprise Voice policy of user
• Play on phone
• Subscriber access contacts or directory
• Unauthenticated caller: use enterprise voice policy of the Lync Server UM
contact object

Get-CsExumContact MainAA | Grant-CsVoicePolicy –PolicyName Seattle

Subscriber Access Number

• PSTN number for subscriber access directs to a specific dial plan

• If an organization desires a single subscriber access number to
publish, all users must be on same dial plan
• Extensions within a dial plan must be unique
Secondary Dial Plan Support

• Users sometimes have 2 or more UM extensions in different UM Dial

Plans
• For example, Lync phone (SIP URI dial plan) and station set (TelExtn dial plan)
• UM will take voice messages on all extensions
• Can log into Outlook Voice Access from all extensions
©2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be
registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the
current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be
interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this
presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.