Agenda
Lync Server high-level topology
Edge
Identity
Edge
server
MIIS
UC end points
AD
Voicemail/
archive
Front end
Exchange
Back end
Monitoring
EE pool

SCOM
Mediation Server
(optional)
IP-PSTN
gateway
More secure
federation and
interoperability
External user
ingress
File store
Pool
Fewer,
consolidated
servers
virtualized and
higher scale
DFS
Services
Web access
Persistent chat
(optional)
Reverse
proxy
PBX
Office web apps
CDR/QoE/
report DB
SQL
Consolidated
archiving
SCOM, AD, DFS
Lync Voice
Deployment types
Overview of Lync offerings
Lync Server 2013 on-premises—full UC including Enterprise Voice
Lync Online—IM, presence, and meetings without Enterprise Voice
Lync hybrid—Lync Server and Lync Online in a shared setup
Lync hosted—third-party offering of Lync Server
Voice Policies
Can be assigned per user, per site, or global
Provides admins with flexibility to control user voice entitlements
Control dialing capabilities (class of service) by assigning Public
Switched Telephone Network (PSTN) usages
Not only for users—also useful to address common area
device requirements
Routes
PSTN usages
A PSTN usage record specifies a class of call (such as internal, local,
or long distance) that can be made by various users or groups of
users in an organization
By themselves, PSTN usage records do not do anything—for them
to work, they must be associated with the following
New in Lync Server 2013, PSTN usages can now be assigned to
trunks (for session management) or placed in Voice Routing policies
for network sites (for Location-Based Routing)
Routing and authorization
Controlling gateway preference
Multiple trunks in same route
Multiple routes in the same usage
Routes in different usages
Regulatory requirements
57+ countries/regions regulate Voice over Internet Protocol (VoIP)
Regulation examples
Regulations may provide exceptions for closed user groups
(such as enterprises, educational institutions, and so on) and allow
VoIP and video within the user group, even if international
Location-Based Routing (LBR) was designed specifically to enable
compliance in India
Introducing Location-Based Routing
LBR is designed to enable compliance with regulatory requirements
that restrict toll bypass
Routes the call based on the location of the caller
Enforce routing of PSTN calls to prevent toll bypass
Scoped to specific sites, gateways, and users
Delivered in the July 2013 update to Lync Server 2013
Least Cost Routing versus
Location-Based Routing
Least Cost Routing (LCR)
Location-Based Routing
Location-Based Routing capabilities
Incoming PSTN calls
Outgoing PSTN calls
LBR regulatory compliance limitations
Call Park and response groups
Dial-in conferencing
UM routing
Consultative transfers
Location-Based Routing basics
Site
Voice Routing Policy
Unknown location
Trunk
Pool support for Location-Based Routing
Client support for Location-Based Routing
Configuring Location-Based Routing
Enable Location-Based Routing for
network sites
Enable Location-Based Routing
through trunks
Configuring Location-Based Routing
Enable Location-Based
Routing through Voice Policy
Enable Location-Based
Routing globally
Set-CsVoicePolicy
-Identity <voice policy ID>
-PreventPSTNTollBypass <$true|$false>
Set-CsRoutingConfiguration
-EnableLocationBasedRouting $true
Enabling the LBR conferencing app
The Location-Based Routing
conferencing app is disabled
by default
Design considerations
When using LBR, the site routing policy must include a route
for all possible calls
Trunks are associated with one network site
Start
Is user
enabled for
LBR?
Is global
LBR on?
Is source site
known and
LBR enabled?
Use next usage in
user’s Voice Policy
to check if call
is authorized
Normal processing
Use usages in user’s
Voice Policy
Is call
authorized
by user
Voice
Policy?
Use usages from
source site Voice
Routing Policy
to route call
Normal processing
Are
additional
usages
on the
policy?
Do no allow call
Stop
Route only to
non-LBR-enabled
trunks
Outbound routing
One policy for authorization and a different policy for routing
Scenario: caller as@contoso.com is based in Atlanta and has Atlanta Voice
Policy but is visiting Boston site which is LBR enabled
Inbound routing
Start
Is global
LBR switch
on?
Inbound
from trunk?
Is source
trunk LBR?
Get site associated with
the trunk
Is endpoint
in the
gateway
site?
Route to endpoint
Stop
Route to UM
Conferencing
LBR conferencing application ensures that a single conference does not
contain VoIP users from different sites and PSTN dial-out
Mediation
Server C
Gateway F
PSTN
gateway
FQDN F
Mediation
Server D
Gateway G
PSTN
gateway
FQDN G
Media path optimization
PSTN
MPLS
Trunks and IP-PBX interworking
Trunk and IP-PBX interworking—real life
MTP-1
PBX-10
MED-10
5060
5061
MTP-2
M:N routing
Session management
A possible alternative for PBX integration scenarios
Lync Server can support call routing from an incoming trunk to an
outgoing trunk to provide routing functionalities to other systems
By enabling intertrunk routing, the following routing paths
(among others) are enabled:
Sample scenarios
Inbound
trunk
PSTN
usage
Route
Outbound
trunk
Inbound
trunk
•
•
•
•
•
PSNT
usage
Route
Outbound
trunk
Session management
Lync supports the association of a set of PSTN usages on an
incoming trunk to determine a call route to an outgoing trunk
Intertrunk configuration remains familiar for the administrator with
the use of existing routing configuration concepts
Media bypass in intertrunk routing calls is supported
Intertrunk routing call authorization scope is at the trunk level
Configuring session management
New-CsVoiceRoute -Identity RedmondRoute -PstnUsages
@{add=“Redmond"}
-PstnGatewayList
@{add="PstnGateway:redmondgw1.contoso.com"}
Set-CsTrunkConfiguration –Identity “TrunkId”
-PstnUsages @{add=”Redmond”}
Lync call-handling services
Call queuing, treatment,
and routing for
departments
Unassigned
numbers service
Prompt playback and
transfer capability for
unassigned numbers
Team call
User define who their
calls are forked to
Group Call Pickup
Call Park and Group Call Pickup
Both features are built on the same service
Call Park
Group Call Pickup
Call Park and Group Call Pickup—planning
Orbits
Clients
Administration
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.