Cisco TelePresence Interoperability Technical Overview

1. Cisco TelePresenceInteroperability Technical Overview TSBU Technical Marketing October 2008

2. Cisco TelePresence Interop Summary • Cisco TelePresence provides a unique"in-person" visual communications experience • You feel as if you are in the same room, face-to-face, with the remote participants • Interoperability provides a transition strategy • User migration from existing video conferencing to immersive visual communications • Cisco provides standards-based interoperability with existing standard-definition Videoconferencing / Video Telephony endpoints • H.320, H.323 and SCCP • Seamless interoperation with >95% of the existing video conferencing equipment installed today

3. Cisco TelePresence Interop Key Messages • Cisco TelePresence is based on open standards, including SIP, H.264, AAC-LD and G.711 • Provides interoperability between TelePresence and standard-definition Videoconferencing / Video Telephony • Solution will maintain the rich, immersive experience between TelePresence participants, while providing a bridge to existing Videoconferencing / Video Telephony devices • Leverages the existing Cisco Unified Videoconferencing 3500 Series (CUVC) Multipoint and H.320 ISDN Gateway products • Cisco has been offering the CUVC family since 1999. CUVC has a proven track record of interoperating with virtually all vendors/models/versions of H.323 and H.320 –based Videoconferencing and SCCP –based Video Telephony equipment

4. Cisco TelePresence Practical InfoWorks With a Wide Range of Endpoints • Supported Protocols • H.323 • SIP • SCCP Mac XMeeting Tandberg 1700 Tandberg 1000 Microsoft NetMeeting Polycom VSX 7000 Cisco VT Advantage Microsoft Office ClientRequires CUVC 5.6MOC client plugin Polycom HDX 9000 And many more… Cisco 7985

5. Cisco TelePresence Interop Software Version Recommendations • Cisco TelePresence Interoperability was introduced in CTS release 1.3 and CTMS release 1.1.0 • Scheduling of interop-enabled TelePresence meetings was introduced in CTS-MAN release 1.4

6. Cisco TelePresence Multipoint SwitchInteroperability London H.323 or H.320 Videoconferencing Tokyo Cisco TelePresenceMultipoint Switch(CTMS) Cisco UnifiedVideoconferencing(CUVC) SIP Video Telephony New York SCCP Video Telephony • Today, TelePresence and Videoconferencing are fundamentally different experiences and are generally maintained as separate environments • CTMS provides multipoint switching for Cisco TelePresence • CUVC provides multipoint mixing for Videoconferencing • Solution is to bridge the two environments by cascading the CTMS and CUVC together

7. Active SegmentCascade Cisco TelePresence Multipoint SwitchInteroperability – Media Plane London H.323 or H.320 Videoconferencing Tokyo CUVC CTMS SIP Video Telephony New York SCCP Video Telephony All CTS endpoints will send a copy of their audio in G.711 format H.264 1080p H.264 CIF CTMS determines which CTS segment is emitting the most dominant audio and requests it to send a copy of that segments video in CIF resolution AAC-LD CTMS mixes the G.711 channels from all CTS endpoints into a single G.711 channel and switches CIF and G.711 to CUVC G.711 Any video format CUVC supports As the dominant audio segment changes throughout the meeting,CTMS switches the CIF video stream accordingly Any audio format CUVC supports

8. Active SegmentCascade Cisco TelePresence Multipoint Switch Interoperability – Media Plane London H.323 or H.320 Videoconferencing CUVC Tokyo CTMS SIP Video Telephony New York SCCP Video Telephony H.264 1080p In the opposite direction, audio and video coming from CUVC to CTMS is switched to all CTS endpoints when the audio coming from CUVC is deemed to be the most dominant segment CIF image from CUVC is presented on the left screen of each CTS surrounded by black borders H.264 CIF AAC-LD G.711 Any video format CUVC supports Any audio format CUVC supports

9. 1920 704 1080 576 Cisco TelePresence Multipoint Switch Interoperability – User Experience CIF video received from CUVC is scaled to 4CIF resolution by the CTS codec and then displayed on TelePresence 65” 1080p display surrounded by black borders

10. Cisco TelePresence Interop Benefits and Caveats Benefits: • Maintains the rich, immersive experience for Cisco TelePresence meeting participants • Provides standards-based interoperability with minimal additional hardware requirements • No-charge software update to CTS and CTMS • Customer only needs to provide a CUVC 3500 Series MCU, which they may already have Caveats: • Will increase the amount of bandwidth required to/from each CTS by an additional 768kbps in order to transmit and receive the CIF and G.711 streams • Interop segment is limited to CIF resolution video at 768kbps and G.711 audio in this release

11. Cisco TelePresence InteroperabilityMax Bandwidth Per CTS – With Interop Added

12. Cisco TelePresence Interop Other Caveats / Limitations • CUVC 5.5 and 5.6 are the only supported model of MCU • The CUVC MCU must be dedicated to TelePresence and controlled by Cisco TelePresence Manager. You cannot share this MCU with CUCV-M or Cisco MeetingPlace controlled meetings • Encryption is not supported for interop-enabled multipoint meetings (e.g. Secure RTP (sRTP) on the TelePresence side does not interoperate with H.235 on the Videoconferencing side) • TelePresence participants and CUVC participants will not be able to share slides, documents or document cameras (e.g. Auto Collaborate on the TelePresence side does not interoperate with H.239 on the CUVC side • Recommend using MeetingPlace or WebEx to facilitate collaboration • Far End Camera Control (FECC) will not be provided. TelePresence participants will not be able to control (zoom, pan or tilt) the cameras of CUVC participants • Reduces CTMS and CUVC port capacity by 1 per meeting. E.g. CTMS can support up to 48 segments, and CUVC-3515-24 can support up to 24 participants. Reduce by 1 each for each simultaneous meeting

13. GK Cisco TelePresence Multipoint Switch InteroperabilitySignaling Plane CUCM CUCM Gatekeeper London H.323 or H.320 Videoconferencing Tokyo CUVC CTMS SIP Video Telephony New York Video Telephony • Myriad ways to configure the signaling paths…the above represents the “recommended” way SIP H.323 SCCP

14. Cisco TelePresence InteropHow It Works - Signaling Plane Summary • Details on how the right ½ of the diagrams work can be found in the Video Telephony SRND at www.cisco.com/go/srnd, initially published for CallManager release 4.0 in 2004 and updated for CallManager release 4.1 in 2005 • Details on how the left ½ of the diagrams work can be found in the Cisco TelePresence SRND at www.cisco.com/go/srnd, published in 2007 • The integration of these two environments is documented in the CTMS Administration Guide at http://www.cisco.com/en/US/docs/telepresence/multipoint_switch/1_1/admin/guide/dh_interop_2.html • Other reference documentation: • CUCM Administration Guide(s)http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html • CUVC 5.5 Administration Guidehttp://www.cisco.com/en/US/docs/video/cuvc/5_5/mcu/3545/configuration/guide/cuvc_3545config_wrapper.html • CTS-Manager 1.4 Administration Guide • http://www.cisco.com/en/US/docs/telepresence/cts_manager/1_4/Admin_Guide/ctm_cfg.html#wp1094191 • Questions can be sent to ask-telepresence-technical@cisco.com

15. Cisco TelePresence InteropHow It Works - Scheduling • CTS-Manager 1.4 supports only one CUVC MCU • CUVC MCU and EMP must be dedicated for TelePresence

16. Cisco TelePresence InteropHow It Works - Scheduling • Step 1: User Schedules Meeting using Outlook or Notes • Step 2: User accesses CTS-Manager using link in meeting confirmation email

17. Cisco TelePresence InteropHow It Works - Scheduling • Step 3: User selects Video Conferencing tab • Step 4: User enables interop for the meeting • Step 5: User selects “Send Email” After theses steps are complete a new confirmation email is sent out containing the Videoconferencing access#

18. CTMS Cisco TelePresence rooms get One Button to Push Cisco TelePresence InteropHow It Works - Scheduling CUVC Video conferencing units dials the video conferencing access number

20. Appendix: Step-by-StepConfiguration Example

21. GK Introduction Cisco TelePresence Environment Video Conferencing Environment Call Manager 5.1(2b) or greater Cisco IOS Gatekeeper CTMS 1.1.0 CUVC 5.5 or greater with EMP CTS Endpoint 1.3.0 H.323 Videoconferencing Endpoints In the following slides, it is assumed that the TelePresence systems are already setup to do multipoint calls and the Video Conferencing Endpoints are already configured to make regular video calls. See the reference documentation for more information about the CTMS and MCU pre-requisite configuration if needed. Cisco Confidential

22. Outline • CUCM Configuration • Add SIP Trunk • Add a Route Pattern for CTMS to CUVC • CTMS Configuration • Add a Static Meeting with Interop Enabled • CUVC Configuration • Enable SIP and create a service prefix for the Interop Conference • Gatekeeper Configuration • Define the zone with an IP address • Legacy Endpoints Configuration • Point it to the Gatekeeper IP Address • How to setup an Interop Call • References

23. Start Here

24. Device  Trunk

25. Add New trunk

26. Select the SIP Trunk Select the SIP Device Profile Add a SIP Trunk to CUVC • This is the SIP trunk that CTMS will use to create the cascade connection to CUVC

27. Include the IP Address of the MCU under Destination Address Select the default Non Secure SIP Trunk Profile Select the default Standard SIP Profile Choose a Device Name and a Description representing your CUVC MCU Save and Reset

28. Call Routing  Route/Hunt Route Pattern

29. Add New Route Pattern to the CUVC SIP Trunk • This is the Route Pattern that will point to the CUVC SIP Trunk you just created

30. Select a Route Pattern that matches the MCU Service Prefix Select the MCU SIP Trunk Add Description

31. Outline • CUCM Configuration • Add SIP Trunk • Add a Route Pattern for CTMS to CUVC • CTMS Configuration • Add a Static Meeting with Interop Enabled • CUVC Configuration • Enable SIP and create a service prefix for the Interop Conference • Gatekeeper Configuration • Define the zone with an IP address • Legacy Endpoints Configuration • Point it to the Gatekeeper IP Address • How to setup an Interop Call • References

32. Login to the CTMS Click on the Static Meetings to create one

33. Add a new Static Meeting Add a New Static Meeting

34. Enable Interop Enter the CUVC Number that CTMS will dial to create the cascade connection Set up a Static Meeting with Interop Enabled • Configure the static meeting in the same way you would for a regular multipoint call • For Interop: Enable Interop and enter the phone number of the CUVC Service Prefix • Make sure to match the CUVC number to the route pattern you created in CUCM

35. Static Meetings You have successfully created a static meeting with Interop Enabled NOTE: Optionally you may create multiple static meetings to host concurrent interop meetings

36. Outline • CUCM Configuration • Add SIP Trunk • Add a Route Pattern for CTMS to CUVC • CTMS Configuration • Add a Static Meeting with Interop Enabled • CUVC Configuration • Enable SIP and create a service prefix for the Interop Conference • Gatekeeper Configuration • Define the zone with an IP address • Legacy Endpoints Configuration • Point it to the Gatekeeper IP Address • How to setup an Interop Call • References

37. CUVC • Enable SIP • Enable H.323 • Under Services tab - Create a Prefix • Configure it as MCU and not a gateway • Optional Configurations in MCU (not necessary for basic Interop setup) Following CUVC configuration assumes that it is a dedicated MCU for TelePresence Interop

38. Login to the MCU

39. Under Protocols  H.323 Verify that H.323 is enabled and the Gatekeeper IP Address is configured

40. Enter the CallManager IP Address as the SIP server. Make sure that the type of the connection matches the Security Profile settings in the Call Manager. Enable SIP Under Protocols  SIP

41. Under Protocols  SCCP You do not need to enabled the SCCP protocol Interop Calls

42. Services  Add

43. Enter a Service Prefix that manages the Call Manager Route Pattern to CUVC and the CUVC Number you programmed in CTMS Enter a Service Description Select HD/SD Continuous Presence Set Max Call Rate to 768 kbps Support Image size up to CIF Define Parameters for the New Service We recommend setting the rate to 768K and CIF since it’s the minimum required for an interop meeting but feel free to try higher rates.

44. Basics – Optional

45. Conference Control – Optional

46. Themes – Optional

47. Quality of Service – Optional

48. Dynamic Layouts – Optional

49. Alert Indications – Optional

50. Advanced – Optional