Overview of Cisco TelePresence Solution and Deployments

Transcription

1

2 Overview of Cisco TelePresence Solution and Deployments 2

3 Housekeeping Overview of Cisco TelePresence Solution and Deployments This session provides an overview for all components of a TelePresence deployment. Subsequent breakout sessions will cover specific components of the TelePresence solution in depth. Recent features and functionality will be covered, as well as our direction for the future. Many of the these most recent features are dependent on the grouping of specific software versions across the solution. This session will explain these requirements and dependencies to ensure a successful TelePresence deployment. This breakout will cover the entire TelePresence solution including CUCM, VCS, TelePresence Server, CTMS, MCU, TMS, CTS-Manager and endpoints. 3

4 Agenda 10 min 10 min 25 min 15 min 25 min 15 min 20 min Introduction Video evolution, TelePresence and pervasive video, terminology Creating a Unified TelePresence Solution Protocols, endpoint differences, call control, conferencing, scheduling Endpoints SIP support in CTS, TIP support for SX/EX/MX/C series, SX20, Jabber/Movi, TX series Call Control CUCM-VCS trunk, VCS role in B2B, dial plan Multipoint Technologies, TS 2.2, CTMS 1.8, Webex OneTouch, MCU 4.2, Conductor, Comparison Scheduling and Management TMS 13.1, CTS-Manager 1.8, future VMware Support, Roadmap 4

5 Introduction

6 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 6

7 LTREVT-2301 BRKEVT-2801 COCEVT-3431 BRKEVT-2802 PSOEVT-3865 BRKEVT-2807 BRKEVT-2809 COCEVT-3430 BRKEVT-2806 PSOEVT-3880 BRKEVT-2319 BRKEVT-2807 BRKEVT-2808 COCEVT-3432 BRKEVT-2805 PSOEVT-3880 BRKEVT-2806 BRKEVT-2317 Monday 10:00am Monday 1:00pm Monday 1:00pm Tuesday 8:00am Tuesday 8:00am Tuesday 11:00am Tuesday 12:30pm Tuesday 4:00pm Wednesday 8:00am Wednesday 8:00am Wednesday 11:00am Wednesday 12:30pm Wednesday 4:00pm Thursday 8:00am Thursday 10:00am Thursday 10:00am Thursday 12:00pm Thursday 12:00pm Thursday 3:30pm Overview of Cisco TelePresence Solution and Deployments Advanced Cisco TelePresence Configuration Lab Cisco TelePresence: best practices for call control integration Offering Video as an IT Service: How to Fund, Justify and Enable Cisco TelePresence: Deploying and provisioning video endpoints Managing Video in Your Organization: Enterprise Content Delivery for the WAN Enterprise Video Network Performance Analysis with Medianet Cisco TelePresence Conductor - Simple, Natural conferencing Video Interoperability: Not Just a Dream Troubleshooting Network Impairments in Enterprise TelePresence Deployments Doubling Your TelePresence ROI with Capture-Transform-Share Solutions Business to Business Video Enterprise Video Network Performance Analysis with Medianet Developing Integrations with Cisco Video Solutions Do s, Don ts and Lessons Learned during 5 Years of Video Deployment Introduction to the internals of EX-Series Personal TelePresence systems and C-series codecs Doubling Your TelePresence ROI with Capture-Transform-Share Solutions Troubleshooting Network Impairments in Enterprise TelePresence Deployments Media Transformation and Analytics: Connecting People and Media across Devices and Applications 7

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

9 Introduction Distinguishing Immersive TelePresence from Video Conferencing Remote participants were considered second tier Hollywood squares overused Remote Controls/GUI too complicated Unreliable Remote participants life size Spatial audio Simplified user interface, minimal action needed by end user Reliable 9

10 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 10

11 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 11

12 Introduction Terminology - ActivePresence and OBTP (One Button to Push) Issue How do you maintain an immersive experience in a multipoint meeting with many endpoints Answer ActivePresence: Preserve ability to see multiple endpoints, but show active speaker full-screen to maintain focus As more endpoints join it becomes harder to maintain an immersive experience User schedules TelePresence rooms in Outlook User receives confirmation Participants enter their TelePresence Rooms One button press to launch call 12

13 Introduction Cisco User Experience The user is being trained, but in a way that seems natural. Cisco Jabber Video Cisco TelePresence Server Cisco Touch 8 Jabber ipad Consistent user experience is more intuitive Users require less training for new rollouts, reducing time and resources normally needed for user training Cisco Touch 12 13

14 Introduction Terminology for presentation SX/EX/MX/C series based endpoints (all run same TC software) CTS/TX endpoints C20 C40 SX20 CTS1100 C60 C90 CTS Profile 42 Profile 52 Profile 65 TX9000 TX1300 EX60 EX90 MX200/300 TX

15 Creating a Unified TelePresence Solution

16 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 royalty-free. Today several third party vendors have implemented TIP on their endpoints and infrastructure. What is the relationship between SIP and TIP? H.323 SIP MGCP 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 16

17 Unified TelePresence Solution Supporting video standards Challenge: Cisco TelePresence systems used a mixture of SIP, H.323 and TIP over SIP for call signaling and media negotiation. Solution: CTS systems now support SIP and TIP over SIP. Likewise, our SX/EX/MX/C series TelePresence endpoints support TIP over SIP in addition to SIP and H.323.* Challenge: CTS systems were only capable of encoding/decoding two resolutions: 1080p and 720p. Other TelePresence endpoints supported a wider range: QCIF up to 1080p Solution: CTS systems are now capable of encoding/decoding a wider range of resolutions from CIF to 1080p. This ensures interoperability, and flexible choices for bandwidth provisioning *TIP was added to EX/MX/C series endpoints 2012 Cisco to allow and/or them its affiliates. to connect All rights directly reserved. to CTMS (discussed in later slide) 17

18 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. SX/EX/MX/C series endpoints use Cisco Video Communications Server (VCS). Solution: Integrate call control clusters via SIP trunk. Also add support for SX/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

19 Creating a Unified TelePresence Solution Conferencing Challenge: CTS endpoints use the Cisco TelePresence Multipoint Switch (CTMS) for multipoint meetings. SX/EX/MX/C series endpoints use the Cisco TelePresence Server (TS) or the Cisco Multipoint Control Unit (MCU) for meetings. CTMS TelePresence Server MCU Solution: Add TIP support on TS to allow CTS endpoints to join (Aug 2010). Add TIP support on SX/EX/MX/C series endpoints to allow them to connect directly to CTMS for multipoint calls. Add standard SIP support on CTS endpoints to allow them to connect to MCU. CTMS MCU SIP H.323 TIP 19

20 Creating a Unified TelePresence Solution Detailed review Many of the solutions just covered were introduced recently We ll go into more detail on the TelePresence architecture with these recently released updates Release TC / 13.2 Product Scope Released CTS Endpoints EX / C series TelePresence Server MCU CTS-Manager, CTMS, CTRS TMS Native Interop Portfolio Interop Solution TIP, OBTP, CUCM or VCS Registration CTS Interop Enhancement, Media/Content OBTP and EX/C series Scheduling, Cascade, Event Recording OBTP and CTS Scheduling Aug 2011 Nov 2011 Dec 2011 June p support, CUCM media resource May 2011 Oct 2011 July 2011/ April

21 Endpoints

22 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 22

23 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 23

24 Endpoints Cisco Jabber Video 4.4 Released April 4th, Released December 15th, 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 24

25 Endpoints CTS to CTS call on release and earlier INVITE SDP includes H.264 video and G711/G722,/AAC-LD audio 100 Trying, 180 Ringing, 200 OK CTS TIP (aka MUX) SDP includes H.264 video and G711/G722,/AAC-LD audio Packet includes stream send/recv capabilities TIP ACK CTS Packet includes stream send/recv capabilities RE-INVITE Updated bandwidth in SDP 100 Trying, 180 Ringing, 200 OK Updated bandwidth in SDP CTS

26 Interoperability CTS to non-cts with and later CTS INVITE SDP includes H.264 video resolutions 720p, 448p, 360p, CIF and G711/G722,/AAC-LD audio 100 Trying, 180 Ringing, 200 OK SDP includes many video and audio codecs 1700 MXP CTS endpoints are still limited to dialing numerical destinations URI dialing is released in CUCM 9.0 and later releases of CTS software (discussed in detail in later slide) No configuration needed to specify TIP over SIP or standard SIP call signaling VCS or CUCM are used to translate between SIP and other protocols (H.323, SCCP, etc) 26

27 Endpoints CTS Release 1.8 and 1.9 Video support using standard SIP negotiation and H.264 baseline CTS 1.8 requires CUCM 8.5 or later for standard SIP support* 1.8 adds support for receiving practically any resolution 1.8 adds BFCP over UDP support (requires CUCM 8.6 or later) 1.8 adds support for Cisco Touch adds support for TX endpoints *8.6 or later recommended Release 1.8 Endpoints Tested 1.8 Released Nov 28 th, Released Mar 26 th, 2012 EX/MX/C series, Movi, MXP, E20, 1000MXP, 150MXP, 45xx/42xx MCU, 89xx/99xx IP Phones, CUVA Transmit Resolutions 1280x x x x240 CTS will always transmit at 30fps, but can receive any frame rate Receive Resolutions 1280x x x x x x x x x x x x x x x x x x x x x

28 Endpoints CTS Release 1.8 Content Sharing Binary Floor Control Protocol (BFCP) - SIP standard for negotiating multiple video streams - Allows a presenter to share content so that the far end sees both content and a view of the presenter - Receiving endpoints can switch between different layouts of people and content CTS Switched Presentation - When a presentation is detected, CTS switches from sending main video to just sending the presentation channel - If BFCP negotiation fails, the endpoint will fall back to switched presentation CTS endpoints can send presentation at the following resolutions: Endpoint CTS TX TX TX 9000 TX 9200 Content Resolution XGA 1024x768 SVGA 800x600 VGA 640x480 CTS All other CTS endpoints XGA 1024x768 28

29 Endpoints When will endpoints use SIP vs. TIP? CTS to CTMS CTS to CTS CTS to TS CTS to EX/MX/C series CTS to MCU CTS to any other video endpoint SX/EX/MX/C series (TC5) to CTMS TIP TIP TIP (can fallback to SIP) SIP SIP SIP TIP CTS triple-screen endpoints are capable of using standard SIP signaling to negotiate media. However, only center display is active, and the three cameras will switch based on active speaker. 29

30 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 30

31 Endpoints SX/EX/MX/C series TC5 release A few words on TC5 and its addition of TIP support TC5 endpoints will only use TIP when connected to CTMS This means you cannot connect a CTS on or earlier with a TC5 endpoint To connect point to point between an SX/EX/MX/C series and a CTS the following versions are required: SIP or later Doesn t matter what version EX90 31

32 Call Control

33 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 33

34 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 34

35 Call Control Terminology CUCM Directory Number (DN) Route Pattern Translation Pattern Trunk Cisco Unified Mobility Locations and Regions Ad hoc Conferencing VCS Device ID Search Rule Search Rule or Transform Neighbor or DNS Zone FindMe Links and Pipes Multiway and Conductor 35

36 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 SIP CTS 3010 MXP H

37 Call Control Dial Plan E.164 and URIs E.164 An ITU-T (International Telecommunication Union) recommendation that defines the public telecommunication numbering plan used in the PSTN. It also defines the format of telephone numbers. E URI Uniform resource identifier (URI) is a string of characters used to identify a name or a resource. Such identification enables interaction with representations of the resource over a network. Alphanumeric URI mithomma@cisco.com or @cisco.com E.164 Based URI Address Scheme Example Cisco Unified CM Registration VCS Registration E Supported as Directory Number (DN) H.323 Endpoints E.164 Based URI @tsbulabs.com Not Supported Supported Alphanumerical URI user1@tsbulabs.com Not Supported Supported 37

38 Call Control CUCM Dial Plan and registration Registration with URI Issue: Can endpoint register with URI? What this affects: Calls to that endpoint. If an endpoint cannot register a URI, then anyone trying to call that endpoint needs to dial a E.164 DN number CUCM 9.0 allows endpoints to register with a DN and have a URI alias. This allows users to reach this endpoint by dialing a URI. Dialing URIs Issue: Most CUCM endpoint user interfaces are not capable of dialing URIs What this affects: CTS endpoints are limited to dialing E.164 numbers. If CTS is trying to reach a URI destination on VCS, FindMe must be used Future Support Future CTS release will allow users to dial E.164 or URIs using the Cisco Touch 12. CUCM allows domain based routing of SIP URI calls; however most CUCM endpoints are not capable of dialing URI addresses today Today, only SX/EX/MX/C/E series CUCM endpoints can dial URI numbers 38

39 Call Control CUCM release 9.0 Released July 2012 Starting with CUCM 9.0 endpoints can have an alphanumeric URI alias associated with their Directory Number Dialing either the URI or the DN will route call to endpoint URIs can be associated with SIP or SCCP endpoints The endpoint itself has no notion of their associated URI, they still register with DN User portion (left-hand side) of URI is case sensitive, host portion is case insensitive Endpoints can have up to 5 URI alias s associated with their DN One URI is considered the primary URI. This will be used for calling party id Each URI can be in a separate partition EX90 EX90 dials alice@cucm.cisco.com CUCM blends Bob s DN and URI for caller ID 9971 sees call coming from bob@cucm.cisco.com and DN: Primary URI: bob@cucm.cisco.com URI: bob.home@cucm.cisco.com DN: Primary URI: alice@cucm.cisco.com SIP 39

40 Call Control CUCM release 9.0, Inter-Cluster routing A URI is owned by one CUCM cluster Integrated Lookup Service (ILS) handles URI routing between clusters ILS can provide URI Syncing, which is the exchanging of URI route strings between member clusters in the network Each cluster replicates its URIs and route string to its neighbors Hub and spoke replication topology URI syncing can also use URIs imported from non-cucm clusters (VCS) Starting with 9.0, SIP Route Patterns can point to SIP trunk or Route List (previous versions were limited to SIP Trunk only) cucm.cisco.com left-hand-side(lhs) right-hand-side(rhs) EX90 dials steve@cisco.com EX90 SIP sjc.cisco.com steve@cisco.com? ILS ILS Route String Send to rtp.cisco.com CUCM sends call to rtp.cisco.com cluster rtp.cisco.com Steve CUCM URI Routing Logic " Is LHS a DN? -route based on existing translation rules, registered DNs, and route patters " Does whole URI match a local URI in the CSS? -route to local endpoint Does URI match an entry in ILS? -route based on route string provided by ILS, using SIP Route Patterns and Trunks Does RHS of URI match a SIP route pattern? -route according to SIP route pattern 40

41 Call Control SX/MX/EX/C series and E20 on CUCM E20 (TE 4.1) CUCM 8.5(1) EX, C series (TC5) CUCM 8.6(1) MX, SX (TC5) CUCM 8.6(2) Customers now have a choice, these endpoints can register to CUCM or VCS Cisco Discovery Protocol (CDP) including voice VLAN support and QoS CUCM TFTP Support Shared directory support E.164 and alphanumeric URI dialing Native voic , call forwarding, music on hold, single-line (with up to four calls on hold/one active), Cisco Unified Mobility support CUCM 41

42 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 42

43 Conferencing

44 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 44

45 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 45

46 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 Immersive 46

47 Conferencing Cisco TelePresence Server Two models: 8710 blade Standalone 7010 Each blade or appliance supports up to 16 screens Up to four 8710 blades can be clustered Dual registers to VCS via SIP and H.323, or can be SIP trunked to CUCM Features Active Presence Supports TIP in release 2.1 and later 1080p30 and 720p60 support in 2.2 Flagship Cisco multipoint solution 47

48 Conferencing Adding a CTS endpoint to TelePresence Server version 2.1 The directory number of the CTS and IP address/hostname of the CUCM The directory number assigned to CTS in CUCM The originating IP address or hostname of the SIP INVITE received by VCS: in this case, the CUCM IP/hostname that has a SIP trunk to VCS Remote Party ID in SIP INVITE. When originating from CUCM this is the ASCII Display (Internal Caller ID) on the endpoint s Directory Number 48

49 Conferencing TS Automatic Identification of CTS Endpoints With TS 2.2 and CTS endpoint version (or later) no longer need to manually add Cisco endpoints to TS When CTS endpoint dials into 2.2 TS, TIP is negotiated and advanced conference features enabled Resolves issues with having CTS and non-cts endpoints on the same CUCM 49

50 Conferencing TS Automatic Identification of CTS Endpoints INVITE SIP/2.0 Via: SIP/2.0/TCP :5060;branch=z9hG4bK23a64c83c7a6 From: "Michael Thomma" To: Date: Tue, 31 May :26:02 GMT Call-ID: Supported: timer,resource-priority,replaces Min-SE: 1800 User-Agent: Cisco-CUCM8.6 Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY CSeq: 101 INVITE Expires: 180 Allow-Events: presence, kpml Supported: X-cisco-srtp-fallback Supported: Geolocation Call-Info: <sip: :5060>;method="notify;event=telephone-event;duration=500" Cisco-Guid: Session-Expires: 1800 P-Asserted-Identity: "Michael Thomma" Remote-Party-ID: "Michael Thomma" Contact: Max-Forwards: 67 Content-Length: 0 x-cisco-tip;x-cisco-multiple-screen=1 CUCM 8.5 and CTS or later is required to pass the x-cisco-tip and x-cisco-multiple-screen SIP headers If CTS endpoint is pre or CUCM version pre-8.5, you still need to manually configure CTS endpoints on TS 50

51 Conferencing TelePresence Server Active Conference 51

52 Conferencing TelePresence Server Experience 52

53 Conferencing TelePresence Server Deployment SIP Trunk to CUCM CUCM TS Dual Register to VCS VCS TS CUCM SIP trunk to VCS TS dual registered to VCS CUCM VCS TS Characteristics Route Patterns on CUCM point to TS Any H.323 traffic interworked by CUCM No H.239 support Recommended for Existing CUCM customers without VCS Deployments that rely heavily on CUCM CSS and partitions SIP only video deployments Characteristics Conferences on TS register via SIP and H.323 to VCS No interworking required on VCS H.239 and BFCP supported Recommended for Existing VCS only deployments Mixed environments with SIP and H.323 video Video only deployments without IP telephony Characteristics Conferences on TS register via SIP and H.323 to VCS SIP endpoints register to CUCM, H.323 endpoints to VCS Route Patterns on CUCM point to VCS for TS conferences Recommended for Customers looking for the best combined video and UC solution CUCM customers looking to add B2B video SIP H

54 Conferencing CTMS Software-based solution Schedulable with CTS-Manager CUCM communication via SIP trunk Scheduled and Non-Scheduled meeting support Voice Activated Switching Speaker & Room Supports up to 48 segments H p, 720p, 360p & CIF video support AAC-LD, G.722 & G.711 audio support Auto Collaborate Support Flow Control Distributed deployment with geographical selection (CTS-Manager required) 54

55 Conferencing CTMS version requirements for SX/EX/MX/C series support SX/EX/MX/C series endpoints running TC5 can register to CUCM or VCS CTS release 1.8 or later is required for TC5 endpoint interop on CTMS CUCM 8.6 CUCM CTS 1.8 CTS 1.8 TC5 SIP CTMS CTMS 1.8 Media 55

56 Conferencing TC5 on CTMS details Call Control CUCM Registration Call Protocol : SIP Call rate: 3075 Kbps TIP mode: Auto VCS Registration SIP Protocol Required Features Supported OBTP IVR Not Supported Roster List Video: H264 SIP HD Video is compatible with CTS versions 1.8 and above only LTRP and CABAC are NOT supported Audio: AAC-LATM Sends and Receives single stream in each direction Presentation: Video at 5 fps TIP Media Audio mixed with main audio CTMS 56

57 Conferencing CTMS version requirements If a pre-1.8 CTS joins CTMS and TC5, endpoints are connected, but unpredictable behavior will occur (i.e. not supported) Same is true if an MXE 1.2 or earlier joins CUCM MXE CTS MXE 1.2 One-way video between TC5 endpoints and non-1.8 CTS endpoints One-way video between TC5 endpoints and MXE CTMS SIP Media 57

58 Conferencing CTMS Version Recommendations Bottom line, if you upgrade to any of the versions below, it is best to upgrade to all the listed versions (or later) to prevent any unexpected behavior and to allow full functionality of the latest features CUCM CTMS CTS-Manager CUCM 8.6 CTMS 1.8 CTS-Man 1.8 CTS 1.8 TC5 58

59 Conferencing CTMS Webex OneTouch TC5 SX/EX/MX/C series endpoints can connect directly to CTMS 1.8 and participate in Webex OneTouch meetings When they are the active speaker, these endpoints send a copy of their video in wcif format so that Webex attendees see them in the Webex portal All endpoints receive content from Webex and are able to share content to Webex Non-TIP endpoint MXE CTMS 1.8 EX90 TC5 CTS 1.8 CTMS MXE 5600 can be used for non-tip endpoints to join CTMS Webex OneTouch meetings Media 59

60 Main Features Two way video & audio with TelePresence Server or TelePresence MCU for conferencing Easy Scheduling with TMS and Cisco Outlook Productivity Tool Any TelePresence endpoint registered to CUCM or VCS One Button to Push/OneTouch to join TelePresence with Webex Two way data content share Audio via SIP/IP, or PSTN audio including third party TSP Audio providers WebEx Meeting Center and mobile clients VCS Expressway to WebEx Cloud

61 WebEx OneTouch 2.0 Architecture Solution Overview OneTouch scheduling in Outlook with WebEx Productivity Tool or via TMS admin booking All Others Microsoft Outlook TMS VCS C Audio, Video and Presentation over SIP/IP Video & Presentation(SRTP) WebEx Client EX Series TS/MCU VCS E Signaling(TLS) SX, MX, C Series CUCM CTS / TX Series OBTP on all CTS, TX, EX, SX, MX and C Series

62 OneTouch Video from WebEx on EX90 Only Active WebEx speaker is shown Initially one layout, Active Speaker From WebEx to TelePresence: -Video: 90p-720p -Content: XGA Video resolution may downgrade to preserve best experience for all Lip-sync mis-match possible with TSP audio 62

63 WebEx Meeting Center Client Video of the active speaker from TelePresence -Video: qcif-720p -Content: TS2.3 XGA -TS 3.0 XGA-720p Video resolution may downgrade to preserve best experience for all Lip-sync mis-match possible with TSP audio

64 Draft View, subject to change WebEx Meeting Center full screen Theater view Active Speaker with ActivePresence from TelePresence Server Other WebEx participants shown below

65 Conferencing CTMS Network Multipoint (NMP) Ability to connect multiple CTMSs and create one large virtual meeting Benefits of a network multipoint meeting: Larger meetings Bandwidth savings across expensive network connections Switching technology keeps latency low, preserving user experience 3 segment stream (like a 3010) CTMS Media CTMS 65

66 Conferencing CTMS Network Multipoint (NMP) Static meetings only at this time (scheduled meetings planned for CTS-Man 1.9 release) Maximum of two CTMSs networked per meeting Non-secure meetings only Commercial bundle not supported Relies on CUCM partitions and calling search spaces CUCM version 8.5 or later required No CUVC support Limited Event Controls No support for video announce, VIP, and Lecture mode 66

67 Conferencing MCU Port Mode Quality nhd 360p30 Several models: 8510 and 8420 blade Standalone 5300 series Standalone 4500 series Standalone 4200 series SD HD HD+ Full HD 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 67

68 Conferencing MCU deployment MCU 4.2 Released May 2011 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 68

69 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 69

70 Conferencing CTS with MCU CTS CUCM VCS MCU CTS 1100 CTS 3010 CTS endpoints are supported on MCU 45xx series starting with In any deployment with CTS 3xx0 or TX 9xx0 triple screen systems, TelePresence Server is still the recommended multipoint solution CTS called into 4501 MCU 70

71 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 71

72 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 72

73 Conferencing Comparing platforms Feature SIP and H.323 Support TelePresence Server CTMS MCU Comments CTMS uses SIP, but requires TIP in addition for endpoints TIP Support Allows TIP endpoints to connect Although all three multipoint platforms serve conferencing needs, they have important differences TS, CTMS, and MCU are continuing to be developed and will fit different needs Unified Conferencing Webex OneTouch Continuous Decode TMS Scheduling CTS-Manager Scheduling Active Presence Custom Layouts VIP/Important Mode Director Controls Integration with Webex allowing 1 way video from video endpoints to Webex cloud, 2 way audio, and 2 way presentation. Continuous Decode is ability to support full range of SD and HD resolutions Multipoint device can have conferences created and scheduled via TMS Multipoint device can have conferences created and scheduled via CTS-Man While MCU does not support the layout known as Active Presence it does have a very similar option Ability for users to change the experience on their endpoint only during an active meeting using DTMF or FECC (TS only supports this on single-screen) Ability to designate a particular endpoint as the VIP or Important person and have them always shown regardless of active speaker Allows the mapping/locking of specific endpoint source to a specific endpoint destination. Clustering Clustering on TS or MCU requires 8710 or 8510 blades on MSE 8000 chassis Cascading Ability to combine two separate conferences on two separate platforms to increase overall scale Streaming Ability to stream active speaker in a conference Lecture Mode The CTMS and MCU version of Lecture Mode differs slightly Content Sharing CTMS only supports TIP auto-collaborate channel. MCU supports H.239 and SIP BFCP. TelePresence Server supports all three. Auto Attendant TS and CTMS require this to be enabled on per meeting basis via scheduling/management platform 73

74 Scheduling and Management

75 Scheduling and Management 75

76 Scheduling and Management TMS CTS-Manager 76

77 Scheduling and Management TMS support for CTS endpoints Released July 20 th, 2011 TMS release 13.1 adds support for scheduling CTS endpoints CUCM 8.5 or later is required. TMS will log into CUCM and return all registered CTS systems in CUCM CTS or later is required for TMS management When a CTS system is added to TMS, TMS can provide : OBTP with TelePresence Server Schedule P2P calls Read system information Monitor response status and call status Dialing from the endpoint 77

78 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 78

79 Scheduling and Management TMS and CTS-Manager calendaring integration with OBTP User Interface Codec/ Endpoint Multipoint Resource TMS or CTS-Manager Exchange User Reads event in mailbox using EWS Checks for available multipoint resources User schedules meeting User now has OBTP access to meeting Sends meeting details to multipoint device Send meeting confirmation to user Codec/endpoint pushes meeting info to user interface Pushes content to codec/endpoint TMS/TMSXE: / 3.0 CTS-Manager 1.6 and later 79

80 Scheduling and Management TMS call launch options When TMS is used as the scheduling and management platform, customers can choose between several call launch options From a CTS perspective, Automatic Connect is a new experience CTS endpoints configured for meetings with Automatic Connect display the meeting on the UI, but the user is not able to launch the call; instead, CTS is dialed by the multipoint device at the meeting start. 80

81 Scheduling and Management TMS 13.2 Sneak Peak! Planned release April 2012 * *Features and release date are subject to change Support for SX/EX/MX/C series endpoints registered to CUCM Support for CTS standard SIP calls Ability to book CTS systems on TelePresence Server or MCU Intelligence to prefer reserving TelePresence Server when a CTS system is booked Allow point to point calls between CTS systems and non-cts systems without allocating TelePresence Server Auto-extend conferences when there are no scheduling conflicts 81

82 Scheduling and Management CTS-Manager 1.8 TelePresence Server Support CTMS, CUVC or MXE, and TS can be added as bridges/servers CTS-Manager uses an API user created on the TelePresence Server to create/modify/delete meetings TelePresence Server must be on version 2.2 or later Multiple TelePresence Servers can be managed A preferred multipoint type is configured. CTS-Manager will automatically fallback to the non-preferred device if: - Preferred device is CTMS but non-tip endpoints are scheduled - Preferred device is TelePresence Server but user enables Webex OneTouch for meeting 82

83 Scheduling and Management CTS-Manager 1.8 with TC5 EX/MX/C series endpoints Groupware scheduling and notifications are same as CTS endpoints Auto-discovery is available if registered to CUCM (same as CTS endpoints) In CTS-Manager 1.8 there are 3 possible endpoints: CTS, EX/MX/C series, and Video Conferencing endpoints(non-tip) OBTP on CTS and EX/MX/C series using Cisco Touch 8, or OSD with remote CTS-Man 1.8 CUCM VCS CTS 3010 EX90 TC5 MX200 TC5 83

84 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. 84

85 Introduction Video evolution, TelePresence and pervasive video, terminology Creating a Unified TelePresence Solution Protocols, endpoint differences, call control, conferencing, scheduling Endpoints Interop in CTS, TIP support for EX/MX/C series, SX20, Jabber/Movi Call Control CUCM-VCS trunk, VCS role in B2B, dial plan Multipoint Technologies, TS 2.2, CTMS 1.8, Webex OneTouch, MCU 4.2, comparison Scheduling and Management TMS 13.1, CTS-Manager 1.8, future VMware Support, Roadmap

86 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 Call Control Yes 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 Yes Management, Scheduling Yes UCS 210 M2 No No CTMS Multipoint Yes UCS 210 M2 No No Co-residency 86

87 Roadmap and Q&A

88 Complete Your Online Session Evaluation Give us your feedback and you could win fabulous prizes. Winners announced daily. Receive 20 Passport points for each session evaluation you complete. Complete your session evaluation online now (open a browser through our wireless network to access our portal) or visit one of the Internet stations throughout the Convention Center. Don t forget to activate your Cisco Live Virtual account for access to all session material, communities, and on-demand and live activities throughout the year. Activate your account at the Cisco booth in the World of Solutions or visit 88

89 LTREVT-2301 BRKEVT-2801 COCEVT-3431 BRKEVT-2802 PSOEVT-3865 BRKEVT-2807 BRKEVT-2809 COCEVT-3430 BRKEVT-2806 PSOEVT-3880 BRKEVT-2319 BRKEVT-2807 BRKEVT-2808 COCEVT-3432 BRKEVT-2805 PSOEVT-3880 BRKEVT-2806 BRKEVT-2317 Monday 10:00am Monday 1:00pm Monday 1:00pm Tuesday 8:00am Tuesday 8:00am Tuesday 11:00am Tuesday 12:30pm Tuesday 4:00pm Wednesday 8:00am Wednesday 8:00am Wednesday 11:00am Wednesday 12:30pm Wednesday 4:00pm Thursday 8:00am Thursday 10:00am Thursday 10:00am Thursday 12:00pm Thursday 12:00pm Thursday 3:30pm Overview of Cisco TelePresence Solution and Deployments Advanced Cisco TelePresence Configuration Lab Cisco TelePresence: best practices for call control integration Offering Video as an IT Service: How to Fund, Justify and Enable Cisco TelePresence: Deploying and provisioning video endpoints Managing Video in Your Organization: Enterprise Content Delivery for the WAN Enterprise Video Network Performance Analysis with Medianet Cisco TelePresence Conductor - Simple, Natural conferencing Video Interoperability: Not Just a Dream Troubleshooting Network Impairments in Enterprise TelePresence Deployments Doubling Your TelePresence ROI with Capture-Transform-Share Solutions Business to Business Video Enterprise Video Network Performance Analysis with Medianet Developing Integrations with Cisco Video Solutions Do s, Don ts and Lessons Learned during 5 Years of Video Deployment Introduction to the internals of EX-Series Personal TelePresence systems and C-series codecs Doubling Your TelePresence ROI with Capture-Transform-Share Solutions Troubleshooting Network Impairments in Enterprise TelePresence Deployments Media Transformation and Analytics: Connecting People and Media across Devices and Applications 89

90 Final Thoughts Get hands-on experience with the Walk-in Labs located in World of Solutions, booth 1042 Come see demos of many key solutions and products in the main Cisco booth 2924 Visit after the event for updated PDFs, ondemand session videos, networking, and more! Follow Cisco Live! using social media: Facebook: Twitter: LinkedIn Group: 90

91