Planning Voice Deployments

1. EXL410 Planning Voice Deployments Subbu Chandrasekaran Senior Program Manager Microsoft Corporation

2. Agenda • Review Lync 2010 Topology • Planning for Lync 2010 features • Reference Architecture, High Availability and Resiliency • Interoperability Principles • IP-PBX Interop • Media Bypass • Migration Approaches • Video Interop

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

4. Agenda • Review Lync 2010 Topology • Planning for Lync 2010 features • Reference Architecture, High Availability and Resiliency • Interoperability Principles • IP-PBX Interop • Media Bypass • Migration Approaches • Video Interop

5. Voice Topology: Lync 2010 Archiving Monitoring DMZ PICXMPP MSN UC Endpoints AOL Yahoo Remote Users UC Pool AD DNS AV Conf. Front End (incl. Mediation) Back End Federated Businesses Edge Services Analog Devices SIP Trunking ExUM Mediation Server PSTN IP-PBX Media GW / SBA On-premise or online Circuit Packet

6. Voice Resiliency Architecture Data Center - EE Pool 1 Presence Conferencing AD & DNS Registrar (Registration & Routing) Bob’s Primary Registrar & User Services:EE Pool 1 Alice’s Primary Registrar & User Services:EE Pool 2 Backup Registrar Pool Data Center - EE Pool 2 Branch Office Presence Conferencing Registrar AD & DNS Joe’s Primary Registrar: SBA User Services:EE Pool 1 Registrar (Registration & Routing) Survivable Branch Appliance

7. Agenda • Review Lync 2010 Topology • Planning for Lync 2010 features • Reference Architecture, High Availability and Resiliency • Interoperability Principles • IP-PBX Interop • Media Bypass • Migration Approaches • Video Interop

8. Location and Enhanced 911 • Uses LIS (Location Information Server ) • Location used for Presence, Emergency Routing, or both • LIS database Contains): • Wireless Access Point (BSSID) • LLDP Port • LLDP Switch • Subnet • MAC • Location Policy used for E911 and routing • User • Subnet • E911 provided through Emergency Service Provider • Include Security Desk IM and conference • Outside United States; use location based emergency routing

9. 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

10. 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

11. 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

12. And much more… • Response Group Service • Call Park Service • Private line • Call controls such as call forwarding, simul-ring, transfer • Delegate, Team Call • Announcement server • Unassigned numbers • Common area phones • Call Admission Control

13. Agenda • Review Lync 2010 Topology • Planning for Lync 2010 features • Reference Architecture, High Availability and Resiliency • Interoperability Principles • IP-PBX Interop • Media Bypass • Migration Approaches • Video Interop

14. 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

15. Deployment Model • Global Deployment is a collection of Sites • Sites are made of Pools • Pools host users & services (such as conferencing, Voice over Internet Protocol (VoIP))

16. Deployment Options Pool-level Resiliency Multi-site Resiliency Small or Trial Deploy Single Data Center Multiple Data Centers Branch Office Site Central Site Sites that do not host a pool Sites which host a pool of either SE or EE • Branches without redundant WANs will purchase a Survivable Branch Appliance to handle voice resiliency in the branch office • Branches with a redundant WAN connection, still require basic PSTN termination with SIP Gateway. • Standard Edition Server can be utilized for improved Quality of Experience (QoE) in large, distant “branches” (truly a Central Site) with lots of conferencing utilization. • Not all branches will require resiliency – for smaller branches, use Remote User Connectivity over public internet or 3G/4G network. • Smaller organizations not requiring resiliency can choose a Standard Edition Server (SE), a single server with all roles consolidated on that server functioning • Organizations who need resiliency will choose an Enterprise Edition Pool (EE), defining a pool of multiple servers comprised of front end and back end roles • “Paired” Standard Edition can offer failover between two SE servers for lower cost and reduced functionality. • Additional Server roles required include Archiving, Director, Edge and Monitoring

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

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

19. 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

20. Survivable Branch Appliance (SBA) A purpose-built appliance optimized to provide resilient multi-modal communication for maximizing branch office user productivity. Solution re-architected for Registrar to work when UserServices role is unavailable or unaccessible. Data Center Branch Office CS Pool Edge Server SBA WAN PSTN

21. Agenda • Review Lync 2010 Topology • Planning for Lync 2010 features • Reference Architecture, High Availability and Resiliency • Interoperability Principles • IP-PBX Interop • Media Bypass • Migration Approaches • Video Interop

22. 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)

23. IP-PBX InteroperabilityinOCS 2007 R2Direct SIP to IP-PBX OIPqualifiedIP-PBX OCS pool MediationServer OCS end-points Media PBX end-points Signaling

24. 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)

25. 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

26. 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

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

28. 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

29. 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

30. 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

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

32. 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

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 Call stays up HQ Site Orlando Branch

34. 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

35. 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

36. 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) Virtually no additional Hardware required

37. A migration and coexistence plan with CUCM and ISR

38. 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 It is possible!!

39. Agenda • Review Lync 2010 Topology • Planning for Lync 2010 features • Reference Architecture, High Availability and Resiliency • Interoperability Principles • IP-PBX Interop • Media Bypass • Migration Approaches • Video Interop

40. 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

41. Video Partner Programs NATIVESOLUTIONS INTEROPERABLE SOLUTIONS • Optimized for Microsoft LyncLogo Program • Webcams • PCs • IP devices • New! Video Interoperability Program • Enable 3rd party VTC systems to interop with Lync

42. Video Interoperability Program • Connect with Lync 2010/OCS 2007 R2 • Direct registration to Lync • Gateways to bridge other systems to Lync • Process • Qualification program • Qualified partner listed on Microsoft website • Requirements • OCS 2007 R2: • Enhanced security, point-to-point video, firewall traversal • Lync 2010: • Enhanced security, point-to-point video, firewall traversal • RTVideo (HD), multiparty video on Lync MCU

43. 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

44. Cisco Telepresence Interoperability • No qualified solution available • OCS 2007 R2: in process • Lync: ask Cisco/Tandberg • One Possible Solution • VCS gateway for signaling • Tandberg “Advanced Media Gateway” for media transcoding • Need both to get HD video • Two more VCS (control, expressway) to work across firewall • Recommended approach: Use qualified partner gateway • Polycom, Radvision

45. Recap • Review Lync 2010 Topology • Planning for Lync 2010 features • Reference Architecture, High Availability and Resiliency • Interoperability Principles • IP-PBX Interop • Media Bypass • Migration Approaches • Video Interop

46. Track Resources • Lync Team Blog: http://blogs.technet.com/b/uc/ • Lync Facebook: http://www.facebook.com/MicrosoftOfficeCommunicator • Lync Server Blog: http://blogs.technet.com/b/nexthop/ • Lync Website: http://lync.microsoft.com/en-us/Pages/unified-communications.aspx

47. Resources Learning TechNet • Connect. Share. Discuss. • Microsoft Certification & Training Resources http://northamerica.msteched.com www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers • http://microsoft.com/technet http://microsoft.com/msdn

48. Complete an evaluation on CommNet and enter to win!

49. Please Complete an Evaluation Your feedback is important! Multipleways to Evaluate Sessions Be eligible to win great daily prizes and the grand prize of a $5,000 Travel Voucher! Scan the Tag to evaluate this session now on myTechEdMobile

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