Module7b

Lync Server 2013 and Networking

MVA Jump Start

Module Overview

• Planning for Media Requirements

• Call Admission Control
• Planning for Call Admission Control
• Media Bypass
Lesson 3: Planning for Call Admission Control

• Call Admission Control Planning Process

• Sites and Regions
• Modeling the Network
• Region Routes
• Intersite links
• Bandwidth Check
• Audio Limit Suggestions
• Video Limit Suggestions
• Example CAC Scenario
Call Admission Control Planning Process

• Identify network topology:

– Identify the hubs/backbones and network regions
– Identify the offices or locations and network sites
– Determine the network route between every pair of network regions

• Determine bandwidth limits

• Identify the IP subnets assigned to each network site

Sites and Regions

• Objects for modeling the network Site

• Network site:
• != Active Directory site Region
• != Central site
• Contains users or servers
• Does not require a server
• Is part of a region
• Regions:
• Group sites
together
• Are connected
to other regions
via region links
Modeling the Network
1.Draw your physical network
Region
2.Define regions for any area that
Site
has more than one network
connection
Region link
3.Define sites. Every site Site link
has a site-to-region link MPLS
4.Define region links
5.Define region routes for
pairs of regions not directly
connected by a link
6.Define subnets and assign to
sites
7.Assign bandwidth policies to
links
8.Put the public media relay
addresses in the appropriate site
1 of 5
1.Draw your physical network
Region
Site

Region link
Site link
MPLS
2 of 5
1.Draw your physical network
Region
2.Define regions for any area that
Site
has more than one network
connection
Region link
Site link
MPLS
3 of 5
1.Draw your physical network
Region
2.Define regions for any area that
Site
has more than one network
connection
Region link
3.Define sites. Every site Site link
has a site-to-region link MPLS
4.Define region links
5.Define region routes for
pairs of regions not directly
connected by a link
4 of 5
1.Draw your physical network
Region
2.Define regions for any area that
Site
has more than one network
connection
Region link
3.Define sites. Every site Site link
has a site-to-region link MPLS
4.Define region links
5.Define region routes for
pairs of regions not directly
connected by a link
6.Define subnets and assign to
sites
5 of 5
1.Draw your physical network
Region
2.Define regions for any area that
Site
has more than one network
connection
Region link
3.Define sites. Every site Site link
has a site-to-region link MPLS
4.Define region links
5.Define region routes for
pairs of regions not directly
connected by a link
6.Define subnets and assign to
sites
7.Assign bandwidth policies to
links
8.Put the public media relay
addresses (Edge A/V) in the
appropriate site
Region Routes

• Traffic flows from A to C via B

• Region routes are bidirectional B
• Must define route for regions not
connected by a link: A C
• Region route AC: LinkAB, LinkBC
• Region route BD: LinkBC, LinkCD
D
Intersite links

• Allow direct connection between sites

• Only traffic directly between those two sites will be accounted for on
the intersite link
• Network routing must be deterministic:
• In Lync, two sites have exactly one path
between them
• Lync does not know what your routers
actually do – only what you tell it they do
• Configured via Lync Management Shell
Bandwidth Check

• All links in the path must have enough bandwidth

• Minimum policy will be applied
• A site or a region does not require a server
• Endpoints outside of sites will not check for CAC
• Exchange UM is not CAC aware
• Edge:
– Add external AV Edge IP address
– Use subnet mask of 32

• Media bypass and CAC:

– Use media bypass only within a site
Audio Limit Suggestions

• Session count vs. quality trade-off at

same overall bandwidth usage
• Providing more for a session limit
does not necessarily allow additional
codecs, but it can cause more to be
reserved
• Media stack can adjust other
parameters to limit the bandwidth of
a codec
• This table is only a rough guide to the
expected codecs
Video Limit Suggestions

Settings can be applied by CAC or by policies described earlier:

• Send and receive limits should be set to same value
• Default: Best quality. For networks that can handle average video bitrates of 600 Kbps for P2P
and 200 Kbps for conference calls
• 1000 Kbps: Usually 848x480 in P2P and 240x240 resolution in multiview
• 350 Kbps: Requires multiview to be disabled. Allows 424x240 resolution
Example CAC Scenario

WAN Link Policy:

Audio Session Limit = 62 kbps

RT Audio WB (No FEC)

Redmond New Orleans

Internet

RT Audio NB + FEC
1 of 3 (Media Negotiation)

WAN Link Policy:

Audio Session Limit = 62 kbps

RT Audio WB (No FEC)

Redmond New Orleans

Internet
2 of 3 (Poor Network)

WAN Link Policy:

Audio Session Limit = 62 kbps

RT Audio WB (No FEC)

Redmond New Orleans

Internet
3 of 3 (FEC Required)

WAN Link Policy:

Audio Session Limit = 62 kbps

RT Audio WB (No FEC)

Redmond New Orleans

Internet

RT Audio NB + FEC
Lesson 4: Media Bypass

• What Is Media Bypass?

• Benefits of Direct Routing of Media
• Key Media Bypass Scenarios
• Media Bypass – Caveats
• Media Bypass Requirements
• Configuring Media Bypass
What Is Media Bypass?

Lync Server 2010 introduced media bypass of the Mediation Server:

• In Microsoft Office Communications Server (OCS) 2007 and
OCS 2007 R2, UC-PSTN call signaling and media always passes through a Mediation Server
• In Lync Server 2010, whenever possible, media for those calls will flow directly to the gateway
without traversing the Mediation Server:
– Applies where media streams stay within a site

Improves audio quality and facilitates reduction of total cost of ownership (TCO):
• Direct routing of media between Lync Server 2010 endpoints and gateways means no redundant
network hops are used:
– Saves bandwidth and reduces end-to-end audio latency

• Less media processing on Mediation Server:

– Fewer Mediation servers deployed
– Recommend collocation of Mediation Server role with Front Ends
Benefits of Direct Routing of Media

Topology simplification:
• Together with Survivable Branch Appliances (SBAs), removes the need for a
stand-alone Mediation Server in most local sites
• Greatly reduces total number of servers for lower TCO
Optimized media flow and Quality of Experience (QoE):
• Eliminates unnecessary hops and potential points of failure
• Saves bandwidth across wide-area network (WAN) by not hair-pinning
• Improves voice quality:
– Use of codec with optimal theoretical Mean Opinion Score (MOS)
– No needless transcoding
– Reduction in latency and in probability of network quality issues
Key Media Bypass Scenarios

• Bypass to a media gateway:

– Gateways qualified for Lync Server supported for bypass
– G.711* over SRTP direct from Lync Server to gateway

• Bypass to select IP-PBXs:

– For specific versions, see Phones and Devices Qualified for Microsoft Lync at
http://technet.microsoft.com/en-us/lync/gg278164
– Keep in-branch media between IP-PBX and Lync Server local without deploying Mediation
Server on site
– May require Media Termination Point (MTP) or similar
– G.711* direct from Lync Server to Cisco Unified Communications Manager (CUCM) MTP to
Cisco IP phone

• SIP trunking:
– Not supported – carrier SBCs generally do not accept connections from any client
Media Bypass with IP-PBX (1 of 3)

Main site call with Lync endpoint and PBX phone via Main PBX

IP-PBX
Lync
Endpoint
Lync WAN
Lync Endpoint

G.711
IP-PBX

PBX
Gateway Endpoint

PBX
Endpoint
PSTN GW / SBA

Mediation

Main Site
(with Data Center) Branch Site
Media Bypass with IP-PBX (2 of 3)

• Centralized Lync Server

IP-PBX
Lync
Endpoint
Lync WAN
Lync Endpoint
G.711

IP-PBX

PBX
Gateway Endpoint

PBX
Endpoint
PSTN
Mediation

Main Site
(with Data Center) Branch Site
Media Bypass with IP-PBX (3 of 3)

• Branch Call with Local Resiliency

IP-PBX Lync
Endpoint
Lync WAN
Lync Endpoint
G.711
GW / SBA

Gateway

PBX
Endpoint
PSTN IP-PBX
Mediation PBX
Endpoint

Main Site
(with Data Center) Branch Site
Media Bypass – Caveats

• Does not work with Call Admission Control (CAC):

– CAC does not apply to intra-network sites:
• The only scenario where media bypass should be triggered
– Cannot enable Always Bypass if CAC is enabled
• Gateway and endpoint must be in the same network site
• All traffic from the Edge server will not use media bypass
• Enabling Always Bypass causes G.711 traffic to traverse your WAN
Media Bypass Requirements

• A Mediation Server peer must support the ability to handle multiple

forked responses to an invite
• Lync clients and the media termination point (MTP) must be able to
communicate directly without going through a Mediation Server
• The gateway/IP-PBX subnet must be defined at the same site in the
Lync network configuration
Configuring Media Bypass

• Ensure that your media encryption is

configured to Optional:

Set-CsMediaConfiguration
-EncryptionLevel
SupportEncryption

• If you configured TLS to your gateways:

Set-CsTrunkConfiguration
-EnableBypass $True -
SRTPMode Optional

• Enable media bypass globally

• Configure sites and subnets
Module Review and Takeaways

• Review Question(s)
• Real-world Issues and Scenarios
• Tools
©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.