Microsoft ® Lync™ Server 2010Bandwidth Management and Call Admission ControlModule 15
Microsoft Corporation
Agenda
• Objectives• Solution Overview• Differentiators• Planning and Provisioning
2
Problem
• Bandwidth• Finite resource
• Difficult to “right provision”
• Affects real-time traffic and all other traffic
• Call Admission Control• Control utilization of real-time traffic
3
Experience: OCS 2007 and OCS 2007 R2• User Impact
• Additional calls can always be placed• Oversubscription affects all users
• Network Impact• How to plan?• Workarounds
• Set MaxAudioVideoBandwidth• Disable Video• DiffServ
4
Experience: Lync Server 2010
• User Impact• Calls are rejected if they result in oversubscription• Guaranteed voice/video quality
• Network Impact• Can now be architectured• Protect network against unexpected spikes• Off-load media through Internet• Reroute voice traffic through Public Switched Telephone
Network (PSTN)
5
Call Admission Control (CAC)• Rich capabilities
• Reroute or fail session• Fully configurable• Dynamically enforced by link and media type
• Cost effective• Simple – no additional physical servers required• No requirement for specific network hardware or integration
• Unified Communications modality support• Audio• Video
• Customizable • Customizable to meet customer needs
6
Concepts
• Allow/deny calls based on bandwidth
• Different implementations• Same goals
• Not necessarily same design
• Not necessarily compatible
7
Call Admission ControlSolution overview
WAN link
Site 3
Site 1
Policy Response
Send response•Accept call•Reroute•Reject invite
Site 2
Policy Request
Status synchronization
Policy service
8
Link 1
Call Admission ControlRe-route overview
Internet
PSTN9
CAC – Bandwidth Policy Service
• Installed on one pool in each site• Integrated High Availability (requires Enterprise
Edition)• Synchronized across pools • Managed through Windows PowerShell™• Transparent to client applications
10
Requirements
• Internet Protocol (IP) subnets should map to geo-locations
• Media terminating endpoints must be Lync 2010• Clients• Pools (including multipoint control units (MCUs))• Mediation Server• Edge Server
11
Recommendations
• Profiling user utilization of network is useful in defining CAC policies
• Configure Quality of Service (QoS) and use in conjunction with CAC policies
12
Planning Process
1. Identify network hubs/backbones > network regions
2. Identify the locations within network regions> network sites
3. Determine the IP subnet(s) assigned to each network site4. Identify the links that connect network regions
For each link:a. Determine the maximum BW capacity b. Define the BW capacity (CAC policy)
5. Determine the preferred network route between every pair of network regions
13
UC Session Bandwidth Costs• Bandwidth numbers include
overhead for framing, encryption, and IP routing information in addition to actual encoded media and based on 20ms audio p-times
• Typical bandwidth values bit rate are measurements of typical activity level values under good network conditions (i.e. no FEC for audio sessions)
• Typical bandwidth number can be used for capacity planning to assess if a network should be considered “right provisioned”
• Upper Limit numbers can be used for initial capacity planning
• Monitor actual Bandwidth usage of UC sessions and then refine
14
Audio/Video Capacity Planning for Peer-to-Peer Sessions
Audio/Video Capacity Planning for Conferences
Audio Capacity Planning for PSTN
Media Codec Typical stream
bandwidth (Kbps)
Maximum stream
bandwidth without FEC
Maximum stream
bandwidth with FEC
AudioRTAudio Wideband
39.8 62 91
AudioRTAudioNarrowband
29.3 44.8 56.6
Main video CIF RTVideo 220 260 Not applicable
Main video VGA
RTVideo 508 610 Not applicable
Main video HD RTVideo 1210 1510 Not applicable
Panoramic video
RTVideo 269 360 Not applicableAudio G.722 46.1 100.6 164.6
Audio Siren 25.5 52.6 68.6
Main video CIF RTVideo 220 260 Not applicableMain video VGA
RTVideo 508 610 Not applicable
Panoramic video
RTVideo 269 360 Not applicable
Audio G.711 64.8 97 161
AudioRTAudio Narrowband
30.9 44.8 56.6
Example: Identify Network Regions
• Identify network hubs and backbones• Identify central site for each network
regionNorth America
Chicago-NA-MCS-deployment01
EMEALONDON-EMEA-MCS-deployment01
APACBEIJING-APAC-MCS-deployment01
15
Example: Identify Network Sites
• Sites with no bandwidth constraint
• Sites with Bandwidth constraint Collect following information:• Total bandwidth capacity of
the WAN link• Bandwidth limit for audio• Per Session Bandwidth limit
for audio• Bandwidth limit for video• Per Session Bandwidth limit
for video Site 1 Region Bandwid
th (kbps)
Audio limit (kbps)
Audio session limit (kbps)
Video limit (kbps)
Video session limit (kbps)
Reno North America 10000 4000 200 2800 700Portland North America 5000 2000 200 1400 700Albuquerque North America 5000 2000 200 1400 700Chicago North America -Detroit North America -New York North America -
• WAN capacity – 5 mbps• Audio limit – 2 mbps• Audio session limit – 200 kbps• Video limit – 1.4 mpbs• Video session limit – 700 kbps North America
Chicago
New York
Detroit
Albuquerque Reno
Portland
WAN capacity – 5 mbpsAudio limit – 2 mbpsAudio session limit – 200 kbpsVideo limit – 1.4 mbpsVideo session limit – 700 kbps
WAN capacity – 5 mbpsAudio limit – 2 mbpsAudio session limit – 200 kbpsVideo limit – 1.4 mbpsVideo session limit – 700 kbps
WAN capacity – 10 mbpsAudio limit – 4 mbpsAudio session limit – 200 kbpsVideo limit – 2.8 mbpsVideo session limit – 700 kbps
16
Example: Identify Cross Links
North America
Chicago
New York
Detroit
Albuquerque Reno
Portland
WAN capacity – 5 mbpsAudio limit – 2 mbpsAudio session limit – 200 kbpsVideo limit – 1.4 mbpsVideo session limit – 700 kbps
WAN capacity – 5 mbpsAudio limit – 2 mbpsAudio session limit – 200 kbpsVideo limit – 1.4 mbpsVideo session limit – 700 kbps
WAN capacity – 10 mbpsAudio limit – 4 mbpsAudio session limit – 200 kbpsVideo limit – 2.8 mbpsVideo session limit – 700 kbps
WAN capacity – 20 mbpsAudio limit – 12 mbpsAudio session limit – 200 kbpsVideo limit – 5 mbpsVideo session limit – 700 kbps
Name Site 1
Site 2 Bandwidth (kbps)
Audio limit (kbps)
Audio session limit (kbps)
Video limit (kbps)
Video session limit (kbps)
RENO-ALBU-CROSSLINK
Reno Albuquerque
20000 12000 200 5000 700
17
Example: Populate IP Subnets per Network Site
North America
Chicago
New York
Detroit
Albuquerque Reno
Portland
WAN capacity – 5 mbpsAudio limit – 2 mbpsAudio session limit – 200 kbpsVideo limit – 1.4 mbpsVideo session limit – 700 kbps
WAN capacity – 5 mbpsAudio limit – 2 mbpsAudio session limit – 200 kbpsVideo limit – 1.4 mbpsVideo session limit – 700 kbps
WAN capacity – 10 mbpsAudio limit – 4 mbpsAudio session limit – 200 kbpsVideo limit – 2.8 mbpsVideo session limit – 700 kbps
172.29.79.0/23, 157.57.215.0/25, 172.29.90.0/23, 172.29.80.0/24
172.29.80.0/23, 157.57.216.0/25, 172.29.91.0/23, 172.29.81.0/24
172.29.78.0/2410.71.109.0/24, 157.57.209.0/23
157.57.211.0/23, 172.28.152.128/25
157.57.210.0/23, 172.28.151.128/25
172.29.77.0/2410.71.108.0/24, 157.57.208.0/23
Site Region Bandwidth (kbps)
Audio limit (kbps)
Audio session limit (kbps)
Video limit (kbps)
Video session limit (kbps)
Subnets
Reno North America 10000 4000 200 2800 700 172.29.79.0/23, 157.57.215.0/25, 172.29.90.0/23, …
Portland North America 5000 2000 200 1400 700 172.29.77.0/24 10.71.108.0/24, 157.57.208.0/23
Albuquerque North America 5000 2000 200 1400 700 172.29.79.0/23, 157.57.215.0/25, 172.29.90.0/23…
Chicago North America - 157.57.211.0/23, 172.28.152.128/25Detroit North America - 172.29.78.0/24 10.71.109.0/24,
157.57.209.0/23New York North America - 172.29.80.0/23, 157.57.216.0/25,
172.29.91.0/23…
18
Example: Identify Routes Between Network Regions
Name Region 1 Region 2 Network linkNA-EMEA-ROUTE North America EMEA NA-APAC-LINK, EMEA-APAC-LINK
EMEA-APAC-ROUTE EMEA APAC EMEA-APAC-LINK
NA-APAC-ROUTE North America APAC NA-APAC-LINK
North America
EMEA
APACNA-APAC-LINK
EMEA-APAC-LINK
WAN capacity – 50 mbpsAudio limit – 20 mbpsAudio session limit – 200 kbpsVideo limit – 14 mbpsVideo session limit – 700 kbps
WAN capacity – 25 mbpsAudio limit – 10 mbpsAudio session limit – 200 kbpsVideo limit – 7 mbpsVideo session limit – 700 kbps
19
Example ScenarioCAC profile type
WAN link per session audio limit
Available audio WAN link per session video limit
Available video Per user app sharing limit
Optimized for Session Count(w/ Wide Band P2P)
60 kbps RTAudio NB + FECSiren + FECRTAudio WB (no FEC)
250 kbps RTVideo – CIF (15fps)
256 kbps
Balanced 95 kbps (Above plus) RTAudio WB + FECG.711 (no FEC)G.722 (no FEC)
600 kbps (Above plus) RTVideo – VGA (30fps)
512 kbps
Optimized for Quality
165 kbps (All Above plus)G.711 + FECG.722 + FEC
1500 kbps (All Above plus)RTVideo – HD (30fps)
None
New JerseyRedmond
WAN Link Policy:Audio Session Limit = 60 kbps
RT Audio WB (no FEC)
20
Example ScenarioProfile type WAN link per
session audio limit
Available audio WAN link per session video limit
Available video Per user app sharing limit
Maximum Sessions
60 kbps RTAudio NB + FECSiren + FECRTAudio WB (no FEC)
250 kbps RTVideo – CIF (15fps)
256 kbps
Balanced 95 kbps (Above plus) RTAudio WB + FECG.711 (no FEC)G.722 (no FEC)
600 kbps (Above plus) RTVideo – VGA (30fps)
512 kbps
Highest Quality
165 kbps (All Above plus)G.711 + FECG.722 + FEC
1500 kbps (All Above plus)RTVideo – HD (30fps)
None
New JerseyRedmondInternet
WAN Link Policy:Audio Session Limit = 60 kbps
RT Audio NB (+ FEC)
21
Network Quality of Service – DiffServ• Where do we recommend Quality of Service (QoS)?
• When Right Provisioning not possible and so Constrained wide-area network (WAN) Links (pair with WAN bandwidth Policies)
• Audio prioritization already deployed for other Voice over Internet Protocol (VoIP) solution (ensure level playing field)
• Differentiated Services Code Point (DSCP) - field in an IP packet to assign levels of service for network traffic
• Example “Fully Managed” Network DeploymentMedia type
Per hop behavior
Queuing and dropping
Notes:
Audio EF Priority Queue Low loss, low latency, low jitter, assured BWPair with WAN Bandwidth Policies on constrained links
Video AF41 BW Queue + DSCP WRED Class 4. Low drop priority.Pair with WAN Bandwidth Policies on constrained links
SIP Signaling CS3 BW Queue Class 3.BW allocation should be sufficient to avoid drops
App Sharing AF21 BW Queue + DSCP WRED Class 2. Low drop priority.Pair with End User Policy Caps
File Transfer AF11 BW Queue + DSCP WRED Class 1. Low drop priority.Pair with End User Policy Caps
22
Demo
23
Bandwidth notmanaged
Media Endpoint Requirements
• CAC functionality depends on called endpoint• Call to legacy client will ignore CAC
• Will always be established• Bandwidth will not be managed
Lync Server 2010
Lync Server 2010
Bandwidth managed
Lync Server 2010
Lync Server 2010
Bandwidthmanaged
Bandwidthmanaged
OCS 2007OCS 2007
R2
OCS 2007OCS 2007
R2
24
User Experience
• Alternate path or rerouting• Seamless to caller and callee
• Blocked call• No pop-up for callee
• Missed call notifications
WAN BobBobAliceAlice
25
Call
delayed by 20
seconds
PSTN
Franz
Bob
Bob
User Experience
26
PSTN Rerouting
• Only audio
• No toast if no bandwidth• Call deflection/redirection not possible
• Secondary ring list not rerouted• E.g. team ring, delegates
• Conferencing not rerouted via PSTN• Can join conference from another device
• Cannot escalate calls to conference via PSTN
• However, session to conference to auto attendant is rerouted through PSTN
27
Summary
• Fully configurable • Locations, topology, links, and limits
• Specify routes for Audio and Video
• Policy rules by link and media type
• Policy override
• Dynamically enforced• Full path assessed at session initiation
• Dynamic user-location-based policy enforcement
• High availability with real time redundancy
• If session would exceed limits, re-route or fail
• May use different route for audio and video if desired 28
Q&A
29
30
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.
© 2011 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. This document may contain information related to pre-release software, which may be substantially modified before its first commercial release. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred.