Planning Voice Deployments

2. EXL410 Planning Voice Deployments Mahendra Sekaran Principal Group Program Manager Microsoft Corporation

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 Topologies Servers Optional Servers Front end Mediation Standard Edition Back end Group Chat Director Archiving Monitoring Enterprise Edition AV Conf SCOM Edge UM

7. Deployment Model • Global Deployment is a collection of Sites • Sites are made of Pools • Pools host users & services (such as IM/P, conferencing, VoIP, etc.

8. Reference Topologies Small < 5000 users This example 5,000 users, 3 servers 1667 users/server

9. Reference Topologies Single Datacenter < 100,000 users This example 20,000 users, HA, 14 servers 1429 users/server

10. Reference Topologies Global, Multi-Site Unlimited Site C Site B This example Site 1: 18 servers Site 2: 11 servers Site3: 1 server 2413 users/server

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. 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 +44221234567  01144221234567 • Alice calls London using London GW+44221234567  0221234567

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, +1 425 707 9050  +1 425 882 8080 • Alice to internal PBX number, +1 425 707 9050  +1 425 707 9050 • 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 • LyncPowershell • 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 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”

20. Lync Telephony Deployment Implications How What Replace the PBX SIP Trunking Lync Everywhere Gateway to PSTN Using Lync Voice where practical for the business Connect with the PBX Direct SIP to IP-PBX Gateway to TDM PBX More Costly with Suboptimal UEX Retain the PBX Separate Servers & Vendors for UC

21. SIP Trunking Replace the PBX 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. Direct SIP to IP-PBX Connect with the 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 InteroperabilityPain 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 InteroperabilityinOCS 2007 R2Direct SIP to IP-PBX OIPqualifiedIP-PBX OCS pool MediationServer OCS end-points Media PBX end-points 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. IP-PBX Interoperability in LyncDirect SIP to IP-PBX with media bypass Lync poolwithMediation Server OIP-QualifiedIP-PBX capable of bypass Lync end-points Media PBX end-points Signaling

27. Lync 2010: Media Bypass 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 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 CUCMIn-branch call between Lync endpoint and Cisco phone via branch MTP WAN Lync G.711 Gateway CUCM (MTP) ISR (MTP) PBX Endpoint Cisco phone PSTN Mediation Lync Endpoint Lync Endpoint HQ Site Orlando Branch

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

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

36. Media Bypass with IP-PBXBranch call with local resiliency WAN Lync Lync SBA Gateway CUCM (MTP) ISR (MTP) G.711 PBX Endpoint PBX Endpoint PSTN Mediation Lync Endpoint Lync 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 Lync CUCM (MTP) ISR (MTP)

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. LyncVideoStrategy • High quality video in every desktop • High resolution at low cost • Single client experience • Integration with applications High quality video in every desktop • 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 Improve the meeting room experience Embrace and Lead Interoperability • Improve the meeting room experience • Simplify and enrich user experience • Expand reach and usage • Improve productivity

42. Partner Approaches • VTC Direct Registration • Register directly • Multiparty calls on Lync AVMCU • VTC endpoints appear as contacts • Users can take advantage of existing Lyncfunctionality • Click to call, drag and drop, right-click… • Committed partners: • Polycom, Lifesize • Gateway/MCU • Gateway pass-through • Multipartycalls hosted on partner MCU • Virtual rooms appear as contacts • Legacy VCS/telepresence interoperability, multiple views, transcoding • Committed partners: • Polycom, Lifesize, Radvision

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 • Connect. Share. Discuss. • Microsoft Certification & Training Resources http://europe.msteched.com www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers • http://microsoft.com/technet http://microsoft.com/msdn

46. Evaluations Submit your evals online http://europe.msteched.com/sessions

47. © 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.