Demystifying Integration of Lync to your Existing PABX Selvan Loganathan Lync TSP Microsoft Australia Vakhtang Assatrian WW Voice TSP Microsoft Corporation EXL231

00 Hybrid Lync 2013 Preview

About this Presentation Capabilities are subject to change Packaging and licensing have not yet been determined Any screen captures or concepts shown are pre-release and for illustration purposes only Disclaimer This presentation contains preliminary information that may be changed substantially prior to final commercial release of the software described herein. The information contained in this presentation represents the current view of Microsoft Corporation on the issues discussed as of the date of the 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 presented after the date of the presentation. This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESSED, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this presentation. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this information does not give you any license to these patents, trademarks, copyrights, or other intellectual property. All performance statistics are pre-release and subject to change

Direct SIP Lync PABX Lync user PABX phone user Direct SIP Integration SIP Lync PABX Lync user PABX phone user Gateway Integration Legacy Protocol Gateway CSTA Gateway Lync PABX Lync user PABX phone user RCC Integration Lync PABX Client API Lync User 3 rd Party Plug-in Client Side Integration

Lync PABX Client API Lync User 3 rd Party Plug-in Client Side Integration

SIP Lync PABX Lync user PABX phone user Gateway Integration Legacy Protocol Gateway Direct SIP Lync PABX Lync user PABX phone user Direct SIP Integration

CSTA Gateway Lync PABX Lync user PABX phone user RCC Integration What You Get What’s Missing ► Escalate to Lync multi-party audioconf (Multi party just on your phone is still possible) ► Receive calls at home, on the road(voice always on Deskphone) ► Synchronize Do Not Disturb ► Escalate inbound call to desktop sharing ► No delegation

OIP qualified IP-PABX capable of bypass PABX end-points Lync pool with MS role Lync end-points Media Signaling

New Lync 2013 features with Interop implications: Using Pool FQDN instead of individual machine FQDN for cert & connection checking. Failover Routing and four second socket connection timer from Mediation. DNS Load Balancing Support outbound from Mediation to SIP peer. Dual Stack IPv4/IPv6 Unsupported: Bypass on v6 & Standalone v6 on Mediation egress Passing Referred-By and History-Info from Mediation to Peer (dropped the other way) Resiliency enhancements for trunking – bidirectional OPTIONS, peer routing to backup pools Gateway / SBC SBAIP-PBX SIP Trunk E911 SP Pool FQDN for CertYesN/AOptional N/A Fail-over RoutingYesN/AOptionalYes DNS LB SupportYesN/AOptional N/A IPv4/IPv6 SupportOptional SIP Header SupportYes Optional M:N RoutingYes

Supported: Lync 2010 Mediation with Lync 2013 pool Functional at 2010 level of capability Great for customers upgrading to Lync Server 2013 with minimal impact 2013 Mediation needs to interoperate with 2013 qualified infrastructure Timing: When will X be qualified with Lync 2013? Interop testing starts when the product is completed

RCC interconnects with a legacy PBX Provides click-to-call using PABX handset & informs binary phone presence in Lync Does NOT work with Enterprise Voice – client can be either RCC or EV Interop with the PABX uses ECMA standard TR/87 for CSTA over SIP RCC is still supported in Lync 2010 and Lync 2013 P2P video calling for RCC-enabled users supported as of March 2012 update Split Audio / Video continues to remain deprecated for future There is no interop program for RCC (and there never has been….) The protocol is stable with little to no investment on either PABX or Lync side Generally available from major PABX manufacturers through their presence engines RCC is a legacy feature that ties the customer to disadvantageous PABX economics

SBCs recent addition to UCOIP qualification ACME Packet, AudioCodes, NET/Sonus Equivalent testing to Gateways & IP-PABXs Useful when customers are: Already is using an Enterprise SBC (typically ACME) for multi- vendor protocol interoperability SIP Trunking deployments to support bypass. Not qualified for firewall traversal / edge Lync edge offers support for greater range of modalities

Examples Lync interop

Q & A

EXL314 – Lync 2013 ArchitectureWed13:45-15:00 Lync Demos – Microsoft Booth EXL316 – Lync 2013 Meeting ImprovementsWed 17:00-18:15 EXL321 – Lync 2013 DeploymentThur 8:15-9:30 EXL325 – Lync 2013 Voice ImprovementsThur15:30-16:45 EXL334 – Lync 2013 Enterprise NetworkingFri13:45-15:00 EXL231 – Demystifying Integration of Lync to PBXFri8:15-9:30 EXL224 – Lync 2013 Customer Panel Q&AThur 13:45-15:00

Download and evaluate Exchange 2013 PreviewExchange 2013 Preview Download and evaluate Lync 2013 PreviewLync 2013 Preview Get a Lync Business Value Assessment Get an Exchange and Lync Technical Briefing See and test drive Exchange and Lync in our Customer Immersion Experience Centers