PowerPoint Presentation

Lync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/20141Adam Jacobs Dustin HannifinPrincipal Architect, Microsoft Microsoft Solution ArchitectPolycom Inc. Polycom Inc.Video Conferencing Solutions Interoperable with LyncLync Conference 2013 2013 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/20142Some speakers at Microsoft like to use this slide for hidden notes slides. Delete it if you dont want to use it.NEXT: Notes (hidden)2/21/2014 7:52 AM3 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.AgendaBackground on Lync 2013 video capabilitiesUpdate on Lync 2013 Panoramic videoH.264 compatibility deltasStandards-based video deployment scenariosBack-to-back user agent (B2BUA), 3rd party MCU, Native integration and Office 365Aligning video solution to room size and applicationDifferent types of user experienceLync Room System standards-based video co-existenceTake AwaysUnderstand the various types of ways in which you can integrate both traditional and Lync optimized video solutions

Deeper understanding of H.264

Considerations for selecting the right solution for room video needsBackground on Lync 2013 video capabilitiesCodec changesa=rtpmap:34 H263/90000a=rtpmap:122 X-H264UC/90000a=rtpmap:117 G722/8000/2a=rtpmap:104 SILK/16000a=rtpmap:103 SILK/8000

Resolution changesPoint-to-point and multi-party calling scenarios support for 1080p30 (with H.264 SVC)RTV clients still deliver Lync 2010 capabilities (720p point-to-point and VGA for conferences)Full HD prerequisites include:Desktop resolution of 1920x1080Sufficient processor (quad core for 1080 trans./rec.) 1080p capable camera (UVC 1.5 camera with Windows 8 recommended)

H.263 was capable of CIF resolution (352 x 288) P2P videoH.264 SVC (UC) capable of up to 1080p30 videoG.722 Stereo capability leveraged by Lync Room SystemSilk AudioSilk AudioLync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/20146Background on Lync 2013 video capabilitiesGallery view video

Lync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/20147Background on Lync 2013 video capabilitiesGallery view videoDelivered via Scalable Video Coding (SVC) technology

Scenario 1. SVC only without RTV

Lync 2013 w/Panoramic videoSurface (RT)Lync 2013 Mobile (WP)Lync Room SystemLync Web AppLync 2013 Mobile (Android)

1.2.3.4.6.

5.Lync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/20148Background on Lync 2013 video capabilitiesGallery view videoDelivered via Scalable Video Coding (SVC) technology

Scenario 2. SVC with RTV

Lync 2013 w/Panoramic videoSurface (RT)Lync 2013 Mobile (WP)Lync Room SystemLync for MacLync 2013 Mobile (Android)

1.2.3.4.5.

6.Lync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/20149Background on Lync 2013 video capabilitiesPanoramic videoRTV clientsPanoramic video 1056x144 replaced with 960x144 (move from 22:3 to 20:3 ratio)Active speaker video up to 640x480 for multi-party and 720p for point-to-pointSVC clients1280x192 and 1920x288 (dual core processor sufficient)Active speaker video up to 1080p* *Note limited to desktop resolution, 720p real-world (minimizing pano will not force 1080p)

Lync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/201410H.264 compatibility deltasBitstreamVideo streams are H.264 AVC compliant (incorporating PACSI NAL units)PACSI NAL includes the following Supplemental Enhancement Information (SEI):Stream layout i.e. table of width, height, frame rate, bit rate and profile IDs which enumerates all streams and their attributesCropping information (AV/MCU only)Bitstream information for error recovery used to determine packet lossFor bitstream compatibility with standards-based H.264 AVC high profile endpoints, PACSI NAL must be discardedUCConfig Mode 1 is utilized (SVC temporal scalability with hierarchical P prediction using simulcast for spatial scalability) i.e. single stream of video per resolution with support for multiple frame rates within each stream 15/30fps

For more information refer to [MSFT-H264UCConfig] redline documentationPACSI stands for payload content scalability information and NAL refers to network abstraction layerLync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/201411H.264 compatibility deltasSIP SignalingBasic information is negotiated within SDP (i.e. codec preference, network path (ICE) and CAC)

Video resolutions, frame rate and profile support is all assumed as per UCConfig Mode 1

Remaining information is referenced within RTCP messaging:Synchronization source (SSRC) allocation Picture loss information (PLI) used to re-sync video frames in poor bandwidth conditions (when FEC fails). Microsoft PLI differs from standards-based implementationVideo source requests (VSR) used by the receiver to request a video source

Signaling is Microsoft Lync specific and not compatible with standard SIPLync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/201412Standards-based video deployment scenariosBack-to-back user agent (B2BUA)Existing endpoint is registered via standard SIPSignaling conversion is performedMedia is re-packetizedBoth media and signaling traverses B2BUAPresence is proxied on-behalf of endpointExamples include: Microsoft VIS and *Cisco VCSPros:For supported endpoints existing investment in endpoints can be leveragedCons:Multi-party calling complexity (scheduling, 3rd party MCU or content)Single active speaker video

*A/VMCU calling not supported

Lync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/201413Standards-based video deployment scenarios3rd party MCUMCU is registered to LyncSignaling is native for both Lync and non-Lync endpointsMedia transcoding (where necessary) is handled by the MCUMedia for all endpoints is sent/received by the respective MCUPresence for VMRs rather than endpointsExamples include: LifeSize UVC and Polycom RMX

Pros:Existing investment in endpoints can be leveragedContent use cases may be catered for (UX may vary)Hollywood Squares layoutCons:Manual join/3rd party integration for Lync online meeting calls

Lync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/201414Standards-based video deployment scenariosNative integrationEndpoint is registered directlySignaling is native (behaves like a Lync client)Media types natively supported (RTV and H.264 SVC)Examples include: LifeSize and Polycom

Pros:Lync online meeting join/multi-party calling supportedMedia advantages (*point-to-point, multi-stream, up to 1080p30 and Lync 2010/Mac support)Cons:Lync content may not be supportedexisting endpoints may need to be replaced/upgraded

*not for multi-party calls

Lync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/201415Example deployment scenarios to followStandards-based video deployment scenariosLync Online (Multi-Tenant)Optimized endpoints natively supported (Org-ID authenticated) i.e. LRS, CX7000

Alternative is to leverage Federation or Split-domain with on-premises Lync Server

For Split-domain an alternate video domain must be utilized

Diagram of split-domain (illustrate alternate domains for video)Lync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/201416Standards-based video deployment scenariosLync Online (Multi-Tenant)Scenario 1. Lync accounts homed within Office 365 with 3rd party MCU

Diagram of split-domain (illustrate alternate domains for video)Lync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/201417DemoLync 2013 Auto-cascading via 3rd party MCUSmart Cascading Overview

DMARMXH323/SIP EndpointLync Server AVMCU

Lync 2013 Clients

Click-to-joinConference IDLync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/201419Choosing the Right Room SystemRoom Layouts, Aesthetics, and EnvironmentalsAudio CapabilitiesContent SourcesControl Units

Sometimes More Than Cameras, Codecs, and Displays

Lync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/201421Room System Selection GuidanceUse Case/CriteriaMobile/Home OfficeDesk/Work SurfaceExec Office/Huddle SpaceCollaboration RoomConference Room - MedConference Room - LargeTraining RoomAuditoriumNo. of PeopleOne1-21-42-62-84-108-2015+Camera TypeFixed/WebcamFixed/WebcamWebcam or Center of Table Webcam or Center of Table Pan, tilt zoom or Center of TablePan, tilt. zoom + trackingPan, tilt. zoom + trackingPan, tilt, zoom Audio CaptureWebcam/LaptopWebcam/LaptopWebcam or Table MicrophonesWebcam or Table MicrophonesTable Mics or Ceiling MountedTable Mics or Ceiling MountedCeiling MountedIntegrated in RoomDisplaysLaptopLaptopUp to 42Up to 65Up to 65Up to 65Up to 65Projection ScreenInfrastructureLync ServerLync ServerLync Server and/or Traditional Video Infrastructure Integrated with LyncLync Server and/or Traditional Video Infrastructure Integrated with LyncLync Server and/or Traditional Video Infrastructure Integrated with LyncTraditional Video Infrastructure Integrated with LyncTraditional Video Infrastructure Integrated with LyncTraditional Video Infrastructure Integrated with LyncUser EnvironmentLync or Lync OnlineLync or Lync OnlineLync, Lync Online and/or Video BridgeLync or Lync OnlineLync and/or Video BridgeLync and/or Video BridgeLync and/or Video BridgeLync and/or Video BridgeVideo SolutionLync VideoLync Video and Center of Table CameraLync, LRS and/or Traditional video SolutionsLync with Center of Table Camera or LRSLRS and/or Traditional Video SolutionsTraditional Video SolutionsTraditional Video SolutionsTraditional Video Solutions

Lync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/201422Typically Point to Point ExperienceStill a good solution for some scenariosLong Meetings (4 8 hrs +)Large MeetingsVIP Meetings (Boardroom)

$$$ - Can be cost prohibitive

What About Immersive?

Comparing Video Experiences

Up to 5 (+ panoramic) video streamsStanding Row with option to Pin Spotlight to lock video on one personAll additional features of Lync Meeting experienceParticipant RosterPresenter Mute/Unmute ControlsIn Meeting IM/P

Gallery ViewUp to 16+ video streamsCustomized Layout Options (Sometimes Admin Controlled)Typically presenter wont have Lync Meeting control experienceMeeting management services sometimes needed for large organizations

Traditional Video Infrastructure Traditional room system environments use H.239/BFCPLync content via RDP/PSOM/HTML5

Where Is My Content?

Broadcast One or two presenters. One way push of content. Multi-Party Collaboration Whiteboard, Polls, One Note Sharing, Annotations

Understanding Content DeliveryRDP Transcoding (Screen Share Only)Native BFCP Content via Lync Client Add-Ons (Client SDK)Out of band - Use separate connection with Lync soft client (User experience impacted)Lync Room System natively supports different content modalities for Lync

How to bridge the content gapIsnt Lync Mobile just another Lync client?Uses same codecs as Lync desktop client but different resolutionsMileage May Vary in interop scenarios

Mobility

Lync 2014 2014 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. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.2/21/201430Can make a P2P call with latest software updateMay not be able to send/receive RDP content depending on interop solutionOther content types typically not supportedUsing Lync Room System With Traditional Video Solutions

Video for everyone in the enterpriseP2P audio/ video experience between 3rd party VTCs and LyncContent sharing is not available Minimum feature bar3rd party hardware required

Interoperability via 3rd party Gateway

P2P audio/ video experience between 3rd party VTCs and LyncMultiparty audio/ video is supported via Lync AVMCU3rd party gateways are no longer requiredPhase I: Cisco/ TandbergNative integration on some vendor endpoints Interoperability built in to LyncLync client designed to deliver great meeting experiences with audio, video and content sharingLync Meetings are accessible anytime, from anywhere with an internet connection

Lync across Devices & platformsP2P audio/ video experience between 3rd party VTCs and LyncMultiparty audio/ video is possible via partner MCU or Lync AVMCUContent sharing between devices is limited

Interoperability via 3rd party MCUFamiliar Lync client experience designed for a conference room settingDeveloped by Microsoft as a native Lync endpoint with audio, video and contentDelivered by partners as a packaged solution

Lync Room System

32SummaryChoose the right Lync 2013 interoperability solution based upon end-user needs and strategic objectives

Other factors will come into play when determining the best room solutions such as room sizes, types, and desired end-user experiences

Alignment with respective technology departments, network, UC/messaging, voice and video is importantQuestions?