Video Conferencing Solutions Interoperable with Lync

2. Video Conferencing Solutions Interoperable with Lync Adam Jacobs Dustin Hannifin Principal Architect, Microsoft Microsoft Solution Architect Polycom Inc. Polycom Inc.

3. Agenda Background on Lync 2013 video capabilities Update on Lync 2013 Panoramic video H.264 compatibility deltas Standards-based video deployment scenarios Back-to-back user agent (B2BUA), 3rd party MCU, Native integration and Office 365 Aligning video solution to room size and application Different types of user experience Lync Room System standards-based video co-existence

4. Take Aways Understand 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 needs

5. Background on Lync 2013 video capabilities Codec changes a=rtpmap:34 H263/90000 a=rtpmap:122 X-H264UC/90000 a=rtpmap:117 G722/8000/2 a=rtpmap:104 SILK/16000 a=rtpmap:103 SILK/8000 Resolution changes Point-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 1920x1080 Sufficient 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 video H.264 SVC (UC) capable of up to 1080p30 video G.722 Stereo capability leveraged by Lync Room System Silk Audio Silk Audio

6. Background on Lync 2013 video capabilities Gallery view video

7. Background on Lync 2013 video capabilities 6. Gallery view video Delivered via Scalable Video Coding (SVC) technology Scenario 1. SVC only without RTV Lync 2013 w/Panoramic video Surface (RT) Lync 2013 Mobile (WP) Lync Room System Lync Web App Lync 2013 Mobile (Android) 1. 5. 4. 2. 3.

8. Background on Lync 2013 video capabilities Gallery view video Delivered via Scalable Video Coding (SVC) technology Scenario 2. SVC with RTV Lync 2013 w/Panoramic video Surface (RT) Lync 2013 Mobile (WP) Lync Room System Lync for Mac Lync 2013 Mobile (Android) 6. 5. 1. 4. 2. 3.

9. Background on Lync 2013 video capabilities Panoramic video RTV clients Panoramic 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-point SVC clients 1280x192 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)

10. H.264 compatibility deltas Bitstream Video 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 attributes Cropping information (AV/MCU only) Bitstream information for error recovery – used to determine packet loss For bitstream compatibility with standards-based H.264 AVC high profile endpoints, PACSI NAL must be discarded UCConfigMode 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 documentation

11. H.264 compatibility deltas SIP Signaling Basic 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 implementation Video source requests (VSR) used by the receiver to request a video source Signaling is Microsoft Lync specific and not compatible with standard SIP

12. Standards-based video deployment scenarios Back-to-back user agent (B2BUA) Existing endpoint is registered via standard SIP Signaling conversion is performed Media is re-packetized Both media and signaling traverses B2BUA Presence is proxied on-behalf of endpoint Examples include: Microsoft VIS and *Cisco VCS Pros: For supported endpoints existing investment in endpoints can be leveraged Cons: Multi-party calling complexity (scheduling, 3rd party MCU or content) Single active speaker video *A/VMCU calling not supported

13. Standards-based video deployment scenarios 3rd party MCU MCU is registered to Lync Signaling is native for both Lync and non-Lync endpoints Media transcoding (where necessary) is handled by the MCU Media for all endpoints is sent/received by the respective MCU Presence for VMRs rather than endpoints Examples include: LifeSize UVC and Polycom RMX Pros: Existing investment in endpoints can be leveraged Content use cases may be catered for (UX may vary) “Hollywood Squares” layout Cons: Manual join/3rd party integration for Lync online meeting calls

14. Standards-based video deployment scenarios Native integration Endpoint is registered directly Signaling 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 supported Media advantages (*point-to-point, multi-stream, up to 1080p30 and Lync 2010/Mac support) Cons: Lync content may not be supported existing endpoints may need to be replaced/upgraded *not for multi-party calls

15. Standards-based video deployment scenarios Lync 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 Example deployment scenarios to follow…

16. Standards-based video deployment scenarios Lync Online (Multi-Tenant) Scenario 1. Lync accounts homed within Office 365 with 3rd party MCU

17. Demo Lync 2013 Auto-cascading via 3rd party MCU

18. “Smart Cascading” Overview Conference ID Click-to-join DMA RMX H323/SIP Endpoint Lync 2013 Clients Lync Server AVMCU

19. Choosing the Right Room System

20. Sometimes More Than Cameras, Codecs, and Displays • Room Layouts, Aesthetics, and Environmentals • Audio Capabilities • Content Sources • Control Units

21. Room System Selection Guidance

22. What About Immersive? • Typically Point to Point Experience • Still a good solution for some scenarios • Long Meetings (4 – 8 hrs +) • Large Meetings • VIP Meetings (Boardroom) • $$$ - Can be cost prohibitive

23. Comparing Video Experiences

24. Gallery View • Up to 5 (+ panoramic) video streams • Standing Row with option to “Pin” • “Spotlight” to lock video on one person • All additional features of Lync Meeting experience • Participant Roster • Presenter Mute/Unmute Controls • In Meeting IM/P

25. Traditional Video Infrastructure • Up to 16+ video streams • Customized Layout Options (Sometimes Admin Controlled) • Typically presenter won’t have Lync Meeting control experience • Meeting management services sometimes needed for large organizations

26. Where Is My Content? • Traditional room system environments use H.239/BFCP • Lync content via RDP/PSOM/HTML5

27. Understanding Content Delivery • Broadcast – One or two presenters. One way push of content. • Multi-Party Collaboration – Whiteboard, Polls, One Note Sharing, Annotations

28. How to bridge the content gap • RDP 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

29. Mobility • Isn’t Lync Mobile just another Lync client? • Uses same codecs as Lync desktop client but different resolutions • Mileage May Vary in interop scenarios

30. Using Lync Room System With Traditional Video Solutions • Can make a P2P call with latest software update • May not be able to send/receive RDP content depending on interop solution • Other content types typically not supported

31. Video for everyone in the enterprise Interoperability “built in” to Lync Interoperability via 3rd party MCU Lync across Devices & platforms Interoperability via 3rd party Gateway Lync Room System • P2P audio/ video experience between 3rd party VTCs and Lync • Multiparty audio/ video is supported via Lync AVMCU • 3rd party gateways are no longer required • Phase I: Cisco/ Tandberg • Native integration on some vendor endpoints • P2P audio/ video experience between 3rd party VTCs and Lync • Multiparty audio/ video is possible via partner MCU or Lync AVMCU • Content sharing between devices is limited • Lync client designed to deliver great meeting experiences with audio, video and content sharing • Lync Meetings are accessible anytime, from anywhere with an internet connection • P2P audio/ video experience between 3rd party VTCs and Lync • Content sharing is not available • Minimum feature bar • 3rd party hardware required • Familiar Lync client experience designed for a conference room setting • Developed by Microsoft as a native Lync endpoint with audio, video and content • Delivered by partners as a packaged solution

32. Summary Choose 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 important

33. Questions?