Video & Unified Communications Scenarios / Design / Deployments

Transcription

1 Video & Unified Communications Scenarios / Design / Deployments Tim Janitschke Systems Engineer Sales Public Sector Germany

2 Introduction

3 Introduction TelePresence Architecture Overview Campus Call Control Conferencing Scheduling And Management Monitoring Recording and Streaming Endpoints External Connections Branch Endpoints Conferencing WAN Global B2B Inter- Network Internet Mobile Office

4 Introduction Evolution of video within Cisco Is now a part of

5 Introduction Expanding TelePresence to a Pervasive Video Solution Pervasive Video Web Collaboration Soft Clients Desktop Video Multipurpose Video Fully Immersive Challenges Keeping the focus on the experience and not the technology being used Making video as easy and reliable as voice communications Innovating new ways to collaborate

6 Introduction Pervasive video characteristics Quality Simplicity Reliability Collaboration Natural communication High definition Face-to-face, in person experience Low latency Wideband audio One button to push Active Presence Intuitive controls Integrated scheduling Ad hoc flexibility Low TCO Standards-based Investment protection Scalability Interoperability Intercompany WebEx New experiences Doing more, better

7 Creating a Unified TelePresence Solution

8 Unified TelePresence Solution SIP and TIP What is TIP? TelePresence Interoperability Protocol (TIP) evolved from a protocol Cisco designed and created to overcome challenges faced in multiscreen/multichannel TelePresence environments. Is TIP proprietary? Cisco created, then transferred,tip to the IMTC (International Multimedia Teleconferencing Consortium) to license royaltyfree. Today several third party vendors have implemented TIP on their endpoints and infrastructure. What is the relationship between SIP and TIP? H.323 MGCPSIP SCCP ISDN TIP TIP relies on an initial call negotiation using SIP. SIP is responsible for negotiating the RTP and RTCP IP addresses and ports. These RTP/RTCP channels are used not just for media, but also for the TIP signaling messages. TIP will take over after SIP and re-negotiate things like the number of video and audio streams, multiplexing of multiple media streams, etc. SIP Invite SIP Trying, Ringing, 200 OK RTP/RTCP negotiated by this point via SIP SDP TIP negotiation TIP is used in conjunction with SIP

9 Creating a Unified TelePresence Solution Unifying call control, scheduling, and management CUCM VCS Challenge: CTS endpoints use Cisco Unified Communications Manager (CUCM) for registration, call routing, etc. EX/MX/C series endpoints use Cisco Video Communications Server (VCS). Solution: Integrate call control clusters via SIP trunk. Also add support for EX/MX/C series endpoints to register to CUCM directly. Still use VCS for B2B communications and firewall traversal, as well as advanced video functions. Challenge: CTS endpoints used Cisco TelePresence System Manager (CTS-Man) to integrate with calendaring applications and schedule multipoint resources. SX/EX/MX/C series used the TelePresence Management Suite (TMS), not only to schedule, but also manage and provision endpoints and multipoint resources. Solution: Add support for CTS-Manager to manage/schedule the TelePresence Server and SX/EX/MX/C series endpoints. Add support for CTS endpoints to be managed/scheduled by TMS. Also add OBTP support on TMS. SIP H.323

10 Endpoints

11 Endpoints Introducing the SX20 Replaces the C20 quickset Turns any video screen into a powerful TelePresence system Three camera choices: 2.5x, 4x, 12x zoom Specifications: 1080p60 in main video 1080p15 in content channel SIP/H.323 support Dual-display option Wall mountable SX20 C20 C40 C60 C90

12 Endpoints Introducing the TX9000 series Series Product Family Endpoints TX Immersive TX9000, TX9200, TX1310 MX Multipurpose MX200, MX300 SX Solutions SX20 EX Desktop EX60, EX90 C Integrator C20, C40, C60, C90 E Video Phone E20 What we ve kept from the CTS 3xx0: Spatial wideband audio 65 Plasma displays 2-seat table segments One Button to Push SIP and TIP over SIP support Allows up to 18 participants with TX9200 What we ve improved on: Flat reflective light panel Less-intrusive camera cluster Choice of table color: Maple or Dark Walnut Front panel access to codecs and cabling Touch 12 user interface 42 LED content screen Central wiring tray to avoid trenching Easier assembly

13 Endpoints Cisco Jabber Video 4.4 Released April 4 th, Released December 15 th, 2011 Movi has now been re-branded, Official name is Cisco Jabber Video for TelePresence or Jabber Video for short New Features: p support - Sortable contact lists - Set-up wizard Still provisioned via TMS and registered to VCS Free Cisco Jabber Video is now in Beta and open to the public Users can download Cisco Jabber Video and make HD video calls instantly Certain features of Jabber Video are absent in the free client, these include: - Presence - Company domain addressing - Policy controls - Integrated directories/phonebooks - MCU multipoint - Provisioning

14 Endpoints SX/EX/MX/C series release TC5 Released December 2 nd, 2011 Support for registration to CUCM Support for OBTP (with TMS or CTS-Man) Web interface enhancements Localization of Cisco Touch 8 Software upgrade from TMS agent TIP support for CTMS multipoint calls Audio add-in for EX60 and EX90

15 Endpoints Provisioned by CUCM

16 Call Control

17 Call Control CUCM Software-based call processing system built on Linux Started as a video PBX in 1997 Supports 30,000 endpoints in a cluster Runs on Cisco MCS and UCS servers Uses a variety of voice and video protocols including SCCP, SIP, H.323, and MGCP

18 Call Control VCS Designed specifically for video deployments Two types: VCS Control VCS Expressway Supports 2500 registrations on single VCS, 10,000 in a cluster

19 Call Control Connecting CUCM and VCS Clusters CUCM SIP Trunk connects to VCS Neighbor Zone SIP trunk connects CUCM call control with VCS call control H.323, SCCP, MGCP translated to SIP before being sent to other call control cluster Encryption supported (some dependence on where endpoints are registered) Some of the recent CUCM features which help functionality of SIP connection to VCS include: Replace IP address with Organizational Top Level Domain in call signaling Support of 80-bit authentication tag for encryption in addition to 32-bit CUCM Cluster VCS Cluster EX90 SIP 3 rd Party H.323 CTS 3010 MXP SIP H.323

20 Call Control Cisco Unified Communications Solution IP Telephony (PSTN Gateways, IP phones, Toll Bypass, Voice BRI/PRI/T3/FXO/FXS, Provisioning) Unified Messaging (Unity Voic , Jabber Chat, Speech Connect, Voice IVR, integration, Click to Call) Contact Center (Enterprise/Express, Agent Presence, Routing Logic) Mobility (Single Number Reach, Barge, Shared Lines) CUCM Unity CUPS Contact Center CUCM V VCS PSTN VCS Internet TelePresence (Provisioning/managing of CTS, E, SX, EX, MX, TX and C series endpoints) Business to Business (Expressway Traversal) Additional Video Services (H.323 to SIP, 3 rd party video, IPv4 to IPv6, Jabber Video) VCS

21 Conferencing

22 Conferencing Conferencing Platform Form Factors TelePresence Server CTMS MCU ports at 720p30 or 12 ports at 1080p30 UCS 210 M2 48 ports at 720p30 or 1080p , to 96 ports at 360p30 2 to 40 ports at 1080p , 4505, 4510, 4515, ports 720p30 or 12 ports 1080p30 MCS 7845-I3 MCS 7845-I2 MCS 7845-H2 48 ports at 720p30 or 1080p30 6 to 40 ports at 720p30 3 to 20 ports at 1080p ports at 480p30 10 ports at 1080p ports at 720p15/480p , 4205, 4210, 4215, to 40 ports at 720p15/480p30

23 Conferencing Transcoding vs. Switching Transcoding Active Presence Ability for different bandwidth speeds/resolutions Custom layouts Size of meetings is limited by DSP hardware Higher cost per port MCU TelePresence Server Switching Extremely low latency (<10ms) Ability to scale higher Low cost per port Can be virtualized Limited to basic full-screen video switching (No Active Presence) All endpoints must support and agree on single resolution/frame rate Interoperability requires additional hardware (transcoding) CTMS

24 Conferencing Types of conferences Ad hoc Conference Impromptu meetings, they are not scheduled beforehand,nor require an administrator to initiate them. Suitable for smaller, on-the-fly, meetings. A point-to-point call escalated to a multipoint call is considered ad hoc. Rendezvous Conference Also called meet-me/permanent/static conferences, requires endpoints to dial in to a pre-determined number. Often used for recurring meetings which involve different endpoints each time. Scheduled Conference Provides a guarantee that endpoints and multipoint resources will be available at a certain time. Endpoints join manually or are automatically connected by the multipoint resource. TelePresence Server (TS) SIP, H.323, TIP support Multi-screen support (both Cisco and 3 rd party) Active Presence Rendezvous and scheduled conferences Cisco TelePresence Multipoint Switch (CTMS) TIP support Multi-screen support Active speaker switching Rendezvous and scheduled conferences Cisco Multipoint Control Unit (MCU) SIP and H.323 support Customized layouts FECC and Auto Attendant Ad hoc, rendezvous, and scheduled conferences

25 Conferencing TelePresence Server Experience

26 Conferencing MCU Several models: 8510 and 8420 blade Standalone 5300 series Standalone 4500 series Standalone 4200 series Port Mode nhd SD HD HD+ Full HD Quality 360p30 W448p30 720p30 / w448p p30 (asymmetric) 1080p30 / 720p60 Depending on model MCU can run in nhd, SD, HD, HD+, or Full HD mode Up to three 8510 blades can be clustered Two 5300 MCUs can be clustered via stacking Support H.323, SIP, H.239, BFCP, FECC, DTMF Supports resolutions from QCIF up to 1080p in 4:3 and 16:9 ratios Over 50 different layout options New 5300 MCU has feature parity with 4500 series MCU

27 Conferencing MCU deployment MCU Release 4.2 and CUCM 8.6 added the option of MCU being deployed as a CUCM media resource MCU registered to VCS MCU as CUCM media resource MCU with SIP trunk to CUCM SIP H.323 SIP HTTP SIP Characteristics MCU dual registers SIP and H.323, or registers H.323 prefix, or uses SIP trunk to VCS MCU Auto Attendant can be used for creating conferences Conductor allows intelligent resource allocation, automatic cascading Recommended for H.323 deployments Customers using Multiway with MXP/SX/EX/MX/C series endpoints Easy rendezvous conference creation with Conductor Scheduled conferencing Characteristics SIP trunk to MCU is created behind the scenes when MCU is added as a media resource MRGs and MRGLs are used for intelligent resource allocation Currently only 99xx, 89xx, and Cius can invoke CUCM video media resources Recommended for Large UC deployments with ad hoc conferencing needs Aligning with Cisco s future direction of TelePresence conferencing Characteristics SIP trunk to MCU and Route Patterns must be configured manually on the CUCM CUCM CSS s and partitions used for controlling access to MCU resources Permanent conferences configured on MCU or MCU AA used to create conferences, or TMS used for scheduling Recommended for Scheduled conferencing

28 Conferencing Cisco MCU 4.3 release Released February 2012 New in-call menu with options for: - Lock/unlock conference - Add participants - View roster list on-screen - Mute, control volume, stop/start video or disconnect certain participants - Send DTMF tones to a certain participant Increased 1080p port count on 8510 blades Tighter integration with CUCM, KPML support API improvements Pass-through content mode to save video ports

29 Conferencing Cisco TelePresence Conductor Released November 2011 Solution with TelePresence Conductor Manages MCU (42xx, 45xx, 53xx, 8420 & 8510) conference resources Dialed conference aliases are agnostic of the MCU that the conference is hosted on Resilient solution providing service continuity if a power failure affects a VCS/MCU/TelePresence Conductor Customizes the conferences generated based on the aliases dialed VCS Cluster Conductor Full Cascaded Meeting Whole process is transparent to the end user

30 Conferencing How Cisco TelePresence Conductor Works H.323 traffic VCS HTTPS Request CPL reply TelePresence Conductor SIP traffic XML RPC over HTTPS SIP/H.323 traffic CUCM MCU pool

31 Scheduling and Management

32 Scheduling and Management

33 Scheduling and Management TMS CTS-Manager

34 Scheduling and Management TMS One Button to Push OBTP is available on the Cisco Touch 12, Touch 8, 797x IP phones and on-screen display (OSD) with remote control With TMS 13.2 and CTS 1.8, multipoint meetings can be scheduled on the TelePresence Server or MCU SX/EX/MX/C series on TC5 can use OBTP TC5 on VCS CTS 1.8 CTS or later TC5 on VCS

35 Scheduling and Management Direction for future Both TMS and CTS-Manager have been developed in parallel to support all customers regardless of which endpoints they have deployed. TMS is the scheduling platform moving forward for TelePresence. Specific CTS-Manager features are being ported to TMS to ensure smooth transition.

36 TelePresence Solution VMware Support Advantages of VMware Hardware cost reduced (lower TCO) Space and power needs consolidated Redundancy and high availability Fallback via snapshots *Features and release date are subject to change Device Category VMware Support CUCM Call Control, Provisioning Yes VCS-C Call Control April 2012* TMS CTS-Man Management, Scheduling, Provisioning Supported Cisco Hardware Spec-based support UCS C200/210 M2 UCS B200/B230/B440 M2 Yes Yes UCS C200/210 M2 UCS B200 M2 Yes Yes Yes Yes No Management, Scheduling Yes UCS 210 M2 No No CTMS Multipoint Yes UCS 210 M2 No No Co-residency

37