Presented at IMTC Telepresence Workshop June 15, 2010 Jesi, Italy Explains Cisco TIP Protocol in detail

1. 1 Telepresence Interoperability Protocol (TIP)Overview for IMTC SuperOp 2010 Workshop Allyn Romanow Cisco Telepresence Systems Business Unit (TSBU) 15 June 2010

2. Agenda What is TIP? Background Interesting Features Documentation Current status 2

3. What is TIP? Telepresence Interoperability Protocol Immediate interoperability with Cisco WHILE working on an industry standard Signaling media and media control Controls media Identifies positions and lots of functions Uses RTCP for signaling instead of SIP/SDP 3

4. Use Cases, Point to Point and Multi-point Call Agent Point-to-point Calls Call Agent TIP TIP TIP MCU Multipoint Calls

5. Background Cisco opened up TIP to kick start multi-vendor, multi-screen interoperability while IMTC, the industry work on a suite of standardshttp://www.cisco.com/go/tip Spec (v6, v7) and profile(s) TIP Library Open Source project to launch by 1 Julyhttp://tiprotocol.sourceforge.net Cisco to transfer ownership of TIP and Library to IMTC to own, govern, change control 5

6. Features- What’s Interesting? 6

7. Telepresence Interoperability Protocol (TIP) CTMS CUCMA Session Establishment (SIP) TIP Message Exchange RTCP Data RTP

8. Signaling Media Control Signals endpoints multi-screen capabilities and how streams are mapped to physical devices. Defines positional identifiers (left, right, center,aux) Uses the RTCP private extension mechanism APP packet APP MUXCTRL – number and positions of media streams can transmit and receive APP MEDIAOPTS – AAM, G.711, Refresh, codec,feedback, algorithms Uses RTP Contributing Source (CSRC)

9. RTP Muxing Multiplexes all its video and audio streams into one video RTP session and one audio RTP session CSRC used to demultiplex at receiver Advantages – getting through SIP B2BUAs, NAT/FW that does not support multiple media lines of same media type Disadvantages – non-standard

10. All Video Streams Share 1 Common RTP Connection CTS 1 CTS 2 Video RTP Session or Max 4 Video Streams Center, Left and Right Camera = 3 Video streams Data Video = 1 Video stream Each Camera stream is sent to the corresponding Display Data Video stream is sent to the Projector HDMI Outlet

11. All Audio Streams Share Common RTP Connection CTS 2 (Out) CTS 1 (In) Audio RTP Session Max 4 AAC-LD Audio Streams Center, Left and Right channels = 3 streams Line in and Audio Add-in = 1 stream

12. Interoperability through “Switching” Active SegmentCascade London H.323 or H.320 Videoconferencing Tokyo CUVC CTMS SIP Video Telephony New York Video Telephony H.264 1080p or 720p Any video format CUVC supports H.264 CIF (SD interop only) Any audio format CUVC supports AAC-LD G.722 or G.711 12

13. Security (in v7) Encryption (SRTP) with these key exchange approaches Point-to-point: Keys negotiated through DTLS (TLS over UDP) in-band within the RTP media stream [RFC 5764] Point-to-multipoint: EKT (Encrypted Key Transport)

14. Current Status Becomes part of IMTC July 31 New IMTC working group- TIP AG Process for making changes to spec Interop testing Co-chairs Source license management

15. Questions?

17. TIP Capabilities 1080p at 30 fps, or 780p AUX/collaboration screen, w/ maximum fps indication (1, 5 or 30 fps) Audio Activity Metric (for multipoint switching) Enhanced Codec capability/profile negotiation, such as CABAC, LTRP, GDR and IDR, etc. TIP feedback is ACK centric

18. Telepresence Interoperability Protocol (TIP) TIP Use Cases – 3rd party Endpoints in Cisco Deployment Endpoints Registered To CUCM (*) Point-to-point Calls CUCM Cisco TelePresence Endpoints Registered To CUCM (*) Multipoint CallsAdhoc, Scheduled, Static CUCM TIP TIP TIP TIP Cisco TelePresence Cisco CTMS or TelePresence Server (*) Alternatively may connect to a separate call agent that connects to the CUCM via a trunk interface.

19. Telepresence Interoperability Protocol (TIP) TIP Use Cases – 3rd party MCUs in Cisco Deployment Trunk To CUCM (*) Cisco TelePresence Cisco CTMS Other MCU Trunk To CUCM (*) TIP TIP TIP TIP Cisco TelePresence Other MCU (*) Alternatively may connect to a separate call agent that connects to the CUCM via a trunk interface.