Cisco TIP Presentation
-
Upload
imtc -
Category
Technology
-
view
7.268 -
download
2
description
Transcript of Cisco TIP Presentation
Telepresence Interoperability Protocol (TIP)Overview for IMTC SuperOp 2010 Workshop
1
Allyn RomanowCisco Telepresence Systems Business Unit (TSBU)15 June 2010
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
Use Cases, Point to Point and Multi-point
TIP
MCU
TIP
Point-to-point Calls
Multipoint Calls
TIP
Call Agent
Call Agent
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
Features- What’s Interesting?
Using RTCP for signaling media control
Multiplexing similar RTP streams onto 1 RTP session
Switching (simulcasting) rather than transcoding
Security
6
Telepresence Interoperability Protocol (TIP)
Session Establishment (SIP)
TIP Message Exchange RTCP
Data RTP
CTMS
CUCMA
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)
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
All Video Streams Share 1 Common RTP Connection
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
VideoRTP Session
CTS 2CTS 1
or
All Audio Streams Share Common RTP Connection
Max 4 AAC-LD Audio Streams Center, Left and Right channels = 3 streams Line in and Audio Add-in = 1 stream
CTS 1 (In) CTS 2 (Out)
AudioRTP Session
12
CUVC
Interoperability through “Switching”
New York
London H.323 or H.320 Videoconferencing
H.264 1080p or 720p
AAC-LD
Tokyo CTMS
G.722 or G.711
Any video format CUVC supportsAny audio format CUVC supports
H.264 CIF (SD interop only)
Active SegmentCascade
Video Telephony
SIP Video Telephony
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)
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
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
Telepresence Interoperability Protocol (TIP)
TIP Use Cases – 3rd party Endpoints in Cisco Deployment
TIP
TIP
Point-to-point Calls
Multipoint CallsAdhoc, Scheduled, Static
CUCM
CUCM
EndpointsRegisteredTo CUCM (*)
EndpointsRegisteredTo CUCM (*)
Cisco TelePresence
Cisco TelePresence
Cisco CTMS or TelePresence Server
(*) Alternatively may connect to a separate call agent that connects to the CUCM via a trunk interface.
TIP
TIP
TIP Use Cases – 3rd party MCUs in Cisco Deployment
Telepresence Interoperability Protocol (TIP)
TIP
TrunkTo CUCM (*)
TIP
Cisco TelePresence
Cisco TelePresence
Cisco CTMS
Other MCU
Other MCU
(*) Alternatively may connect to a separate call agent that connects to the CUCM via a trunk interface.
TrunkTo CUCM (*)
TIP
TIP