1. 4/23/2017 7:49 AM
© 2009 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.

2. Planning Voice Deployments
4/23/2017 7:49 AM
EXL410
Planning Voice Deployments
Mahendra Sekaran
Principal Group Program Manager
Microsoft Corporation
© 2007 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.

3. Agenda Review Lync 2010 Topology Network Planning Considerations
Lync 2010 Interop features
IP-PBX Interop
Media Bypass
Migration Approaches
Video Interop

4. Takeaways How to deployment enterprise voice in Greenfield environment
How to enable Interop with existing PBX

5. Agenda Review Lync 2010 Topology Network Planning Considerations
Lync 2010 Interop features
IP-PBX Interop
Media Bypass
Migration Approaches
Video Interop

6. Topologies Simplified
Standard Edition
Enterprise Edition
Topologies
Front end
Back end
AV Conf
Edge
Servers
Director
Archiving
Monitoring
Mediation
Group Chat
Optional Servers UM
SCOM

7. Deployment Model Global Central Sites Pools Sites are made of Pools
Global Deployment is a collection of Sites
Sites are made of Pools
Pools host users & services (such as IM/P, conferencing, VoIP, etc.
Pools
Central Sites
Global
Microsoft
Redmond
Tukwila-1
Tukwila-2
Dublin
Dublin-1

8. Reference Topologies Small This example 5,000 users, 3 servers
Standard Edition central site
Branch through Edge
Small with Branches
250-5,000
Single branch, with SBA
Small with Failover
Two Standard Editions - “Paired” Standard Edition to support inexpensive failover
Any

9. Reference Topologies Single Datacenter This example
< 100,000 users
This example
20,000 users, HA, 14 servers
1429 users/server
Single DC
Enterprise Edition, Single Data Center
Branch through Edge
DC with Branches
1,000 – 30,000
Two branches, one SBA, one PSTN Interconnect

10. Reference Topologies Global, Multi-Site This example
Unlimited
Site B
Site C
This example
Site 1: 18 servers
Site 2: 11 servers
Site3: 1 server
2413 users/server
Global
10,000 +
Two Data Centers with EE
One Central Site with an SE
Some SBA
Some PSTN
Very Large
Unlimited
Enterprise Edition, > Two Data Centers
Standard Editions
Survivable Branch Appliances
Branch with Standard Edition

11. Agenda Review Lync 2010 Topology Network Planning Considerations
Lync 2010 Interop features
IP-PBX Interop
Media Bypass
Migration Approaches
Video Interop

12. Bandwidth - Planning
For planning in a well managed, right-sized network, use Max BW w/o FEC.
If the network will be constrained and you want to preserve quality, use Max BW with FEC.
When understanding how much bandwidth at any given time is being used, use the Typical BW numbers. Not for planning, as usage will be greater at times.
Media
Modality
Codec
Typical BW
Max w/o FEC
Max w/FEC
Audio
Peer to Peer
RTA-W
39.8 62 91
RTA-N
29.3
44.8
56.6
PSTN
30.9
G.711
64.8 97
161
Conferencing
G.722
46.1
100.6
164.6
Siren
25.5
52.6
68.6
Video
RTV - CIF
220
260
RTV - VGA
508
610
RTV - HD
1210
1510
RTV - Pano
269
360
One-way traffic including media, typical activity, RTCP.

13. Network Planning Considerations
Lync media endpoints adapts to varying network conditions
Plan, Assess, Configure, Monitor
Use the bandwidth calculator tools to estimate Lync traffic
Assess your network infrastructure
Configure QoS to prioritize A/V traffic; e2e latency < 150ms
Continually monitor your network for configuration drifts
For constrained links – configure CAC, disable video
If IPSec is deployed, recommend disabling IPSec over the port ranges used for A/V traffic

14. Agenda Review Lync 2010 Topology Network Planning Considerations
Lync 2010 Interop features
IP-PBX Interop
Media Bypass
Migration Approaches
Video Interop

15. Voice Routing – Trunk Translations
Centrally manage number formatting prior to routing to PBX/PSTN
Alice calls London using Redmond 
Alice calls London using London GW 

16. Caller ID Presentation Controls
Natively control Caller ID presented to PSTN/PBX:
Granular controls based on callers and destination number:
Alice to external PSTN number, 
Alice to internal PBX number, 
Controlled by PSTN usage
Overrides “simultaneous ringing”:
Bob calls Alice; Bob has masking for external calls & also has simultaneous ringing
Bob’s caller-id is presented to Alice’s mobile device

17. Exchange Unified Messaging (UM)
The Only supported voice mail solution
Support for Exchange UM 2007 SP1 and newer
Co-locate UM and Mailbox servers
MAPI traffic is less tolerant of latency than VoIP in this scenario
UM and Lync in separate forests is supported
Just ensure the EUM settings in the user objects are synched to Lync forest
Exchange Online and OnPrem together?
Yes
Turn on EUM enablement setting on the user object
User Move
Lync Powershell
Edge Server is required to be deployed

18. Agenda Review Lync 2010 Topology Network Planning Considerations
Lync 2010 Interop features
IP-PBX Interop
Media Bypass
Migration Approaches
Video Interop

19. Lync Telephony Deployment
TechReady13
4/23/2017
Lync Telephony Deployment
Replace the PBX
“We’re sold – our goal is Enterprise Wide UC as soon as practical”
Connect with the PBX
“We love Lync, but I can’t replace everything yet….”
Retain the PBX
“Lync is our presence platform, but all telephony will remain on the PBX”
© 2011 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.

20. Lync Telephony Deployment
TechReady13
4/23/2017
Lync Telephony Deployment
What
How
Implications
Replace the PBX
SIP Trunking
Lync Everywhere
Gateway to PSTN
Connect with the PBX
Direct SIP to IP-PBX
Using Lync Voice where practical for the business
Gateway to TDM PBX
Retain the PBX
Separate Servers & Vendors for UC
More Costly with Suboptimal UEX
© 2011 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.

21. Replace the PBX SIP Trunking Gateway to PSTN PBX becomes obviated
Intra-company calls route through PSTN
Sensible for right combination of internal politics, Δ over time.
DIDs & Numbering
Move the numbers: Lots of carrier hassle
Get new numbers: Expensive at scale
SIP Trunking
Fastest way to future proof solution
Regional availability may be an issue
Gateway
Are scale & quantity of Mediation is a concern with SIP Trunking.
Consider deploying behind PBX’s Gateway

22. Connect with the PBX Who moves? PBX stays resident Direct SIP
Direct SIP to IP-PBX
Gateway to TDM PBX
Who moves?
Locations: Main site first, may make numbering easier.
Job functions: Those that can best prove out the ROI
Depreciation: Old equipment / stations go first, new ones later.
PBX stays resident
GW CapEx on may be disadvantageous if traffic peaks then falls
Does it make sense to reconfigure or replace the shop floor? Emergency campus phones? Garage phones?
Direct SIP
Available for most older IP-PBX releases  
Blocking interop to aid in compete against Lync.

23. IP-PBX Interoperability Pain points in OCS 2007 R2
Interoperability via Direct SIP (OIP qualification)
Very broad range of PSTN gateways, Direct SIP to IP-PBX
R2 Direct SIP requires routing media through Mediation Server
Not a significant problem for central sites
But difficult in branches:
Requires Mediation Servers in branches and/or
Media tromboning (hairpin through the WAN to Mediation Server in central site)

24. IP-PBX Interoperability in OCS 2007 R2 Direct SIP to IP-PBX
Mediation Server
OIP qualified IP-PBX
OCS pool
PBX end-points
OCS end-points
Media
Signaling

25. Lync 2010: Media Bypass Removes need for media transit
Signaling continues to transit through Mediation
B2BUA: security demarc, interop…
Media goes direct
3 Advantages + media resiliency
Based on location of Media endpoints
Bypass only occurs if client is “local” to next hop
G.711 direct – optimized for LAN-like conditions; SRTP supported
When client is not “local”, media goes through Mediation
Codec optimized for WAN using per session CAC;
Mediation provides audio healing
Enables “lightweight” Mediation (collocation with FE, SBA)

26. Lync pool with Mediation Server
IP-PBX Interoperability in Lync Direct SIP to IP-PBX with media bypass
Lync pool with Mediation Server
OIP-Qualified IP-PBX
capable of bypass
PBX end-points
Lync end-points
Media
Signaling

27. Lync 2010: Media Bypass “Always Bypass” in “Global Settings”
How it works – two approaches
“Always Bypass” in “Global Settings”
Treats as a single site ( requires good connectivity )
No Call Admission Control
Will always bypass to trunks enabled for bypass
Network Configuration Setting
Leverages Region/Sites definition
Each site/Region is assigned Bypass ID
Uses current client location
Client IP address  Bypass ID
Gateway address (for media)  Bypass ID
Comparison of the IDs, bypass if the two IDs match

28. Lync 2010: Media Bypass
How it works – two approaches

29. Lync 2010: Media Bypass Inbound calls Outbound calls
Inbound and Outbound logic
Inbound calls
Mediation receives SIP invite; IP address of media gateway in SDP
Mediation passes gateway Bypass ID to clients
Client makes bypass decision
Outbound calls
Client passes Bypass ID in SIP Invite
Mediation determines gateway Bypass ID
Mediation Server compares, call is bypassed if matches

30. Testing and Qualification for Lync Interop
Open Interoperability Program – tested or in process of testing
Survivable Branch Appliances qualified, all support bypass
5 partners – Audiocodes, Dialogic, Ferrari, HP, NET
Gateways (not all support bypass – see OIP page)
Cisco ISR series 28xx, 29xx, 38xx, and 39xx
Avaya 23xx and 41xx
Gateways from Media5, Nuera, and Quintum
IP-PBX (not all support bypass – see OIP page)
Cisco 4.x, Cisco 6.1, Cisco 7.1 and Cisco 8.x
Avaya CM/Aura 4.x, Avaya CM/Aura 5.x
Avaya CS1k 5.x, Avaya CS1k 6.x
Alcatel Lucent 9.x, Siemens 3.1Rx
Mitel, Genband, Aastra, and Huawei

31. Media Bypass – Multiple Sites, Centralized Signaling
What’s different
Centralized IP-PBX with multiple sites
Local media gateways in branch sites (ex: Cisco ISR with MTP)
Want to bypass media to local gateway when Lync is in the branch site
Media bypass in multiple sites?? How to --
Define regions and sites in network Configuration
Define (virtual) media gateways in topology builder
Associate media IP in site to each “media gateway”
Define listening ports as appropriate
Establish appropriate routing on both systems
IP-PBX unaware of Lync dynamic location; suggest routing to local trunk

32. Media Bypass – Multiple Sites, Centralized Signaling
What’s different

33. Media Bypass with CUCM In-branch call between Lync endpoint and Cisco phone via branch MTP
WAN
CUCM (MTP)
Lync
G.711
ISR (MTP)
Cisco
phone
PSTN
PBX
Endpoint
Mediation
Gateway
HQ Site
Orlando Branch

34. Media Bypass with CUCM In-branch call between Lync endpoint and Cisco phone via branch MTP
WAN
CUCM (MTP)
Lync
G.711
ISR (MTP)
Cisco
phone
PSTN
PBX
Endpoint
Mediation
Gateway
Call stays up
HQ Site
Orlando Branch

35. No Media Bypass for Calls on WAN WAN call between Lync in branch and Cisco phone via central MTP
client
WAN
CUCM (MTP)
Lync
client
RT Audio Narrowband
G.711
ISR (MTP)
Cisco phone
PSTN
PBX
Endpoint
Mediation
Gateway
HQ Site
Orlando Branch

36. Media Bypass with IP-PBX Branch call with local resiliency
Lync
Lync
Endpoint
Lync
Endpoint
WAN
CUCM (MTP)
Lync SBA
G.711
PSTN
PBX
Endpoint
Mediation
Gateway
ISR (MTP)
PBX
Endpoint
HQ Site
Orlando Branch

37. A migration and coexistence plan with CUCM and ISR
Planning Cheat Sheet
Define Topology with CUCM and ISR
Use ISR as gateway by CUCM and Lync
Use it for PSTN calls by both “PBX”
Configure ISR for Media Bypass
Direct SIP between CUCM and Lync
Configure it for extension calls by both “PBX”
Including media bypass to CUCM
Migrate users stepwise
CUCM (MTP)
ISR (MTP)
Lync

38. A migration and coexistence plan with CUCM and ISR

39. Takeaway Integrating natively with IP-PBXs can
Allow low cost Proof of Concept
Connect migrated & non-migrated users
Allow for long term coexistence
Native integration with media bypass enables
CPE-less deployment
Keeping much more of the media local, including in centralized multisite topologies

40. Agenda Review Lync 2010 Topology Network Planning Considerations
Lync 2010 Interop features
IP-PBX Interop
Media Bypass
Migration Approaches
Video Interop

41. Lync Video Strategy High quality video in every desktop
High resolution at low cost
Single client experience
Integration with applications
High quality video in every desktop
Improve the meeting room experience
Simplify and enrich user experience
Expand reach and usage
Improve productivity
Improve the
meeting room
experience
Embrace
and Lead Interoperability
Embrace and lead interoperability
Connect and integrate all legacy rooms (via gateways)
Foster innovation in endpoints natively interoperable with Lync
Develop on market standards and contribute to success of UCIF

42. Partner Approaches VTC Direct Registration Gateway/MCU
TechReady12
4/23/2017
Partner Approaches
VTC Direct Registration
Register directly
Multiparty calls on Lync AVMCU
VTC endpoints appear as contacts
Users can take advantage of existing Lync functionality
Click to call, drag and drop, right-click…
Committed partners:
Polycom, Lifesize
Gateway/MCU
Gateway pass-through
Multiparty calls hosted on partner MCU
Virtual rooms appear as contacts
Legacy VCS/telepresence interoperability, multiple views, transcoding
Committed partners:
Polycom, Lifesize, Radvision
© 2011 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.

43. Recap and Takeaways
Lync 2010 supports a variety of topologies, pick the most appropriate topology for your business needs
Although Lync 2010 endpoints adapt to varying network conditions, it is important to plan, assess, and continually monitor your network infrastructrure
Leverage the new Lync 2010 routing features to simplify your interop configuration
Lync 2010 offers a lot of flexibility in IP-PBX interop topologies - leverage media bypass to reduce TCO
Lync 2010 offers interoperates with all leading video systems natively or through a video interop gateway

44. thank you …

45. Resources Learning TechNet http://europe.msteched.com
Connect. Share. Discuss.
Microsoft Certification & Training Resources
TechNet
Resources for IT Professionals
Resources for Developers

46. Submit your evals online
4/23/2017 7:49 AM
Evaluations
Submit your evals online
© 2007 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.

47. 4/23/2017 7:49 AM
© 2012 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.
© 2009 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.