Architectural Overview For Cisco TelePresence Deployments

Architectural Overview For Cisco TelePresence Deployments BRKEVT-2800 Follow us on Twitter for real time updates of the event: @ciscoliveeurope, #CLEUR

Housekeeping 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. We value your feedback- don't forget to complete your online session evaluations after each session & the Overall Conference Evaluation which will be available online from Thursday Visit the World of Solutions and Meet the Engineer Visit the Cisco Store to purchase your recommended readings Please switch off your mobile phones After the event don t forget to visit Cisco Live Virtual: www.ciscolivevirtual.com Follow us on Twitter for real time updates of the event: @ciscoliveeurope, #CLEUR 2

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 - 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, Conductor, Comparison Scheduling and Management - TMS 13.1, CTS-Manager 1.8, future VMware Support, Roadmap 3

Introduction

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 5

Cisco Live TelePresence Sessions Schedule BRKEVT-2802 Wednesday 9:00am BRKSPV-1900 Wednesday 9:00am BRKEVT-2801 Wednesday 4:00pm BRKEVT-2804 Thursday 11:30am BRKEVT-2803 Thursday 4:00pm BRKEVT-2319 Friday 9:00am BRKEVT-2922 Friday 11:00am BRKSPV-2900 Friday 11:00am Cisco TelePresence: deploying and provisioning video endpoints Deploying on enterprise network, CUCM, VCS/TMS, managing endpoints An Introduction to Managed TelePresence Service Creation Approaches to managed TelePresence, virtualized access, integrated collaboration Cisco TelePresence: best practices for call control integration CUCM-VCS integration, scalability, redundancy, security, case study Cisco TelePresence: monitoring and troubleshooting video deployments Traffic patterns, endpoint health, media transport, management options Cisco TelePresence: designing and deploying multipoint video solutions Ad hoc meetings on CUCM and VCS, Conductor, scheduling meetings Cisco TelePresence: ad hoc business to business video Expressway solution, signaling and secure media, DNS SRV, interworking Recording and Streaming Integrations for Cisco TelePresence Design, workflow considerations, TCS, MXE 3500, Show and Share Managed TelePresence Architecture and Deployment Common management, integrated call control, resilience, interconnectivity 6

Introduction Evolution of video within Cisco 2004 2005 2006 2008 2009 Is now a part of 2009 2010 2011 7

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 8

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 9

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 10

Introduction Terminology - OBTP (One Button to Push) User schedules TelePresence rooms in Outlook User receives confirmation email Participants enter their TelePresence Rooms One button press to launch call Consistent User Experience Cisco Touch 12 Cisco Touch 8 Cisco Jabber Video 11

Introduction Terminology - ActivePresence 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 ActivePresence: A specific layout/behavior in multipoint meetings that allows full screen, life size depictions for the current speaker while still showing the other participants in the meeting 12

Introduction Terminology for presentation EX/MX/C series based endpoints (all run same TC software) CTS endpoints C20 C40 C60 C90 500-32 500-37 1100 Profile 42 Profile 52 Profile 65 1300-47 1300-65 EX60 EX90 MX200 3010 3210 13

Creating a Unified TelePresence Solution

Creating a Unified TelePresence Solution SIP and TIP H.323 SIP MGCP SCCP ISDN 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? - 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 RTP/RTCP negotiated by this point via SIP SDP TIP negotiation SIP Trying, Ringing, 200 OK TIP is used in conjunction with SIP 15

Creating a Unified TelePresence Solution Supporting video standards Call Signaling Protocol Challenge: Cisco TelePresence systems (CTS) used a mixture of SIP, H.323 and TIP over SIP for call signaling and media negotiation. TIP SIP SIP H.323 Solution: CTS systems now support SIP and TIP over SIP. Likewise, our EX/MX/C series TelePresence endpoints support TIP over SIP in addition to SIP and H.323.* TIP SIP SIP CTMS *TIP was added to EX/MX/C series endpoints to allow them to connect directly to CTMS (discussed in later slide) 16

Creating a Unified TelePresence Solution Flexible resolutions on all endpoints Media Capabilities 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 17

Creating a Unified TelePresence Solution Unifying call control, registration, and routing Call Control 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. SIP H.323 18

Creating a Unified TelePresence Solution Conferencing Multipoint Technology Challenge: CTS endpoints use the Cisco TelePresence Multipoint Switch (CTMS) for multipoint meetings. CTMS is a TIP-only device. 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 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

Creating a Unified TelePresence Solution Common scheduling platform across all endpoints Scheduling and Management TMS Challenge: CTS endpoints used Cisco TelePresence System Manager (CTS-Man) to integrate with calendaring applications and schedule multipoint resources. 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 EX/MX/C series endpoints. Add support for CTS endpoints to be managed/scheduled by TMS. Also add OBTP support on TMS. CTS-Manager 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 Product Scope Released 1.7.4 1.8 TC5 2.2 4.2 1.8 13.1/ 13.2 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 2011 360p support, CUCM media resource May 2011 Oct 2011 July 2011/ March 2012 21

Endpoints

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

Interoperability CTS to non-cts with 1.7.4 and later CTS 500-37 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 in the roadmap for 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) 24

Endpoints CTS Release 1.8 Released November 28 th, 2011 Video support using standard SIP negotiation and H.264 baseline CTS 1.8 requires CUCM 8.5 or later for native interop support* 1.8 adds support for receiving practically any resolution 1.8 adds BFCP over UDP support (requires CUCM 8.6 or later) Support for Cisco Touch 12 *8.6 or later recommended Release 1.8 Endpoints Tested EX/MX/C series, Movi, MXP, E20, 1000MXP, 150MXP, 45xx/42xx MCU, 89xx/99xx IP Phones, CUVA Transmit Resolutions 1280x720 640x368 352x288 352x240 CTS will always transmit at 30fps, but can receive any frame rate Receive Resolutions 1280x720 1024x768 640x480 768x448 640x368 352x288 352x240 320x180 256x144 176x144 320x240 576x488 512x288 704x480 704x576 720x400 800x448 848x480 912x512 1024x576 800x600 http://www.cisco.com/en/us/products/ps8332/products_device_support_tables_list.htm 25

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 Switched Presentation - When a presentation is detected, CTS switches from sending main video to just sending the presentation channel - In CTS 1.8 if BFCP negotiation fails, the endpoint will fall back to switched presentation 26

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 EX/MX/C series (TC5) to CTMS TIP TIP TIP (can fallback to SIP) SIP SIP SIP TIP CTS 3xx0 triple-screen endpoints are capable of Native Interop. However, only center display is active, and camera will switch based on active speaker. 27

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

Endpoints EX/MX/C series TC5 Support for CTMS TC5 introduces TIP support on EX, MX and C series endpoints to allow interop with CTMS CTS release 1.8 is required for TC5 interop on CTMS 1.8 CUCM 8.6 CUCM CTS 1.8 CTS 1.8 TC5 CTMS 1.8 CTMS Required EX/MX/C series interop with CTS endpoints on CTMS requires CUCM 8.6, CTS 1.8, CTMS 1.8, and TC5 Recommended Even if above call flow isn t needed, Cisco still recommends upgrading the entire solution to these releases for features in 1.8 and TC5 29

Endpoints 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 1.7.3 or earlier with a TC5 endpoint To connect point to point between an EX/MX/C series and a CTS the following versions are required: SIP 1.7.4 or later Doesn t matter what version EX90 30

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

Endpoints Cisco Jabber Video Released December 15 th, 2011 Movi has now been re-branded Official name is Cisco Jabber Video for TelePresence (we like our long names) or Jabber Video for short New Features: - 1080p support - Sortable contact lists - Set-up wizard - Tool Tips Still provisioned via TMS and registered to VCS 32

Call Control

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 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 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 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 CTS 1100 SIP Dual Profile 52 CTS 3010 37 EX90 SIP H.323

Call Control Trunk and Neighbor Peer Address Configuration 38

Call Control External connectivity Cisco Unified Border Element (CUBE) - SIP inspection - No NAT traversal - SP voice interconnect VCS Expressway - NAT traversal with H.460.18, Assent or SIP - TURN and ICE support - Media flows through VCS-C and VCS-E - Video interconnect SIP 39

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.164 408-555-1234 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 4085559876@cisco.com E.164 Based URI Address Scheme Example Cisco Unified CM Registration VCS Registration E.164 14081234567 Supported as Directory Number (DN) H.323 Endpoints E.164 Based URI 14080000000@tsbulabs.com Not Supported Supported Alphanumerical URI user1@tsbulabs.com Not Supported Supported 40

Call Control Dial Plan E.164 and URIs Both addressing schemes are relevant in enterprise deployments today: - E.164 addresses allow easy integration with PSTN and audio-only endpoints - URI addresses allow easier B2B communications by using domain names and are generally more intuitive for end users to operate Historically audio-only endpoints (IP phones) have used E.164 addresses, while SIP video endpoints tend to use URIs. Users were typically given an audio endpoint and a separate video endpoint. Now we often see users issued a single endpoint that is used for both audio and video calls. While video becomes more pervasive, desktop TelePresence endpoints like EX90, Cius, E20 and Jabber will need to support both address schemes. 41

Call Control Dial Plan and registration in CUCM CUCM allows domain based routing of SIP URI calls; however most CUCM endpoints are not capable of dialing URI addresses today Today, only EX/MX/C series CUCM endpoints can dial URI numbers 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 Future Support CUCM 9.0 allows endpoints to register with a combination DN and URI. 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. 42

Call Control E20 on CUCM Customers now have a choice, E20 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 voicemail, call forwarding, music on hold, single-line (with up to four calls on hold/one active), Cisco Unified Mobility support 43

Call Control EX/MX/C series TC5 support on CUCM 8.6 Customers now have a choice, EX/MX/C series endpoints can register to CUCM or VCS CUCM native provisioning, registration and core phone features Cisco Discovery Protocol (CDP) 360p support DHCP Option 150 Corporate Directory Music on Hold (unicast) 44

Unified Communications with Enhanced Video and TelePresence Services Video Communications Server (VCS) Expressway Firewall Traversal Inter-Company and Teleworker Unified Advanced Enterprise Conferencing Features (conductor) SIP Communications Multipoint Services 3rd-party video endpoints H.323 video endpoints SIP to H.323 interworking Microsoft OCS interoperability via Advanced Media Gateway 3 rd Party / H.323 Endpoints 45

Conferencing

Conferencing Introduction 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 predetermined 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 47

Conferencing Conferencing Platform Form Factors TelePresence Server CTMS Version 1.8 MCU 7010 UCS 210 M2 4203, 4205, 4210, 4215, 4220 16 ports at 720p30 or 12 ports at 1080p30 8710 16 ports 720p30 or 12 ports 1080p30 48 ports at 720p30 or 1080p30 MCS 7845-I3 MCS 7845-I2 MCS 7845-H2 48 ports at 720p30 or 1080p30 6 to 40 ports at 720p15/480p30 4501, 4505, 4510, 4515, 4520 6 to 40 ports at 720p30 3 to 20 ports at 1080p30 8420 40 ports at 720p15/480p30 8510 80 ports at 480p30 10 ports at 1080p30 48

Conferencing Transcoding vs. Switching Transcoding Active Presence Ability for different bandwidth speeds/resolutions Customize layouts Higher latency (especially in cascaded meetings) Size of meetings is limited by DSP hardware Higher cost per port MCU TelePresence Server Switching Latency is low (<10ms) Ability to scale higher Cost per port 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 49

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 Features Active Presence Supports TIPv6 in release 2.1 and later 1080p30 and 720p60 support in 2.2 50

Conferencing CTS Endpoints Triple or Single Screen - CTS-500/CTS-1X00 - CTS-30X0/CTS-32X0 Media Negotiated to TIP - Channel Multiplexing - LTRP - Auto Collaborate Telepresence Server Host TelePresence Meetings Media Capability - Up to 1080p30 - Auto Collaborate/H.239/BFCP - TIP with CTS Traditional Media Capability Exchange Separate Call per Segment SIP/H.323 Endpoints Triple or Single Screen Cisco T1/T3 Regular VC Endpoints Media Capability Traditional Exchange -SDP over SIP -H.245 -Up to 1080p + H.239/ BFCP Polycom RPX CTS CTS TelePresence Server Jabber Video MX200 VC Endpoint 51

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 52

Conferencing TS Automatic Identification of CTS Endpoints With TS 2.2 and CTS endpoint version 1.7.4 (or later) no longer need to manually add Cisco endpoints to TS When 1.7.4 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 53

Conferencing TS Automatic Identification of CTS Endpoints INVITE sip:81126220@172.19.236.19:5060 SIP/2.0 Via: SIP/2.0/TCP 172.19.236.70:5060;branch=z9hG4bK23a64c83c7a6 From: "Michael Thomma" <sip:21065@172.19.236.70>;tag=115695~552e7c5a-df83-490f-83fc-4077ebe372ef-30056562 To: <sip:81126220@172.19.236.19> Date: Tue, 31 May 2011 22:26:02 GMT Call-ID: f61d3e80-de516afa-c44-46ec13ac@172.19.236.70 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:172.19.236.70:5060>;method="notify;event=telephone-event;duration=500" Cisco-Guid: 4129111680-0000065536-0000004651-1189876652 Session-Expires: 1800 P-Asserted-Identity: "Michael Thomma" <sip:21065@172.19.236.70> Remote-Party-ID: "Michael Thomma" <sip:21065@172.19.236.70>;party=calling;screen=yes;privacy=off Contact: <sip:21065@172.19.236.70:5060;transport=tcp>;video;audio;x-cisco-tip;x-cisco-multiple-screen=1 Max-Forwards: 67 Content-Length: 0 x-cisco-tip;x-cisco-multiple-screen=1 CUCM 8.5 and CTS 1.7.4 or later is required to pass the x-cisco-tip and x-cisco-multiple-screen SIP headers If CTS endpoint is pre-1.7.4 or CUCM version pre-8.5, you still need to manually configure CTS endpoints on TS 54

Conferencing TelePresence Server Active Conference 55

Conferencing TelePresence Server Experience 56

Conferencing CTMS Software-based solution Integrated 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.264-1080p, 720p, & CIF video support AAC-LD, G.722 & G.711 audio support Auto Collaborate Support Flow Control Distributed deployment with geographical selection (CTS-Manager required) 57

Conferencing TC5 on CTMS 1.8 details Call Control CUCM Registration - Call Protocol : SIP - Call rate: 3075 Kbps - TIP mode: Auto VCS Registration - SIP Protocol Required Supported OBTP IVR Features 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 58

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

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 1.7.4 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 60

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 to prevent any unexpected behavior and to allow full functionality of the latest features CUCM CTMS CTS-Manager MXE 5600 CUCM 8.6 CTMS 1.8 CTS-Manager 1.8 MXE 1.3.1 CTS 1.8 TC5 61

Conferencing CTMS Webex OneTouch TC5 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 MXE 1.3.1 Non-TIP endpoint CTMS 1.8 CTMS EX90 TC5 CTS 1.8 MXE 5600 can be used for non-tip endpoints to join CTMS Webex OneTouch meetings Media 62

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 63

Conferencing CTMS Network Multipoint (NMP) Static meetings only at this time (scheduled meetings planned for later 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 64

Conferencing Cisco MCU 4.2 release Released May 20 th, 2011 Release 4.2 added the option of MCU being deployed as a CUCM media resource The following 3 scenarios are the most likely MCU deployments MCU registered to VCS MCU as CUCM Media Resource MCU with SIP trunk to CUCM SIP H.323 SIP HTTP SIP Can dual register with H.323 and SIP, avoiding the need to interwork MCU Auto Attendant can be used to create conferences on-the-fly TMS can be used for scheduling Conductor allows intelligent resource allocation, and automatic cascading SIP trunk to MCU is created behind the scenes when MCU is added as resource CUCM MRGs and MRGLs are used for intelligent resource allocation Not all CUCM endpoints can initiate conferences SIP Trunk and Route Patterns must be configured CUCM CSS s and partitions can be used to control access to MCU Permanent conferences configured on MCU or MCU AA can be used to dynamically create a conference 65 SIP H.323 HTTP

Conferencing Cisco MCU 4.3 release Planned release May 2012 * *Features and release date are subject to change 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 66

Conferencing CTS with MCU CTS 500-32 CUCM VCS MCU CTS 1100 CTS 3010 CTS endpoints are supported on MCU 45xx series starting with 1.7.4 Three options for placement of MCU: - direct SIP trunk to CUCM - media resource to CUCM (CTS cannot initiate conferences) - registered to VCS CTS 500-37 called into 4501 MCU In any deployment with CTS 3xx0 triple screen systems, TelePresence Server is still the recommended multipoint solution 67

Conferencing Cisco TelePresence Conductor Released November 2011 Solution with TelePresence Conductor Manages MCU (42xx, 45xx, 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 68

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 69

Conferencing Comparing platforms Feature SIP and H.323 Support TIP Support TelePresence Server CTMS MCU Comments CTMS uses SIP, but requires TIP in addition for endpoints Allows TIP endpoints to connect Webex OneTouch Integration with Webex allowing 1 way video from video endpoints to Webex cloud, 2 way audio, and 2 way presentation. Continuous Decode Continuous Decode is ability to support full range of SD and HD resolutions Although all three multipoint platforms serve conferencing needs, they have important differences TMS Scheduling CTS-Manager Scheduling Active Presence 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 TS, CTMS, and MCU are continuing to be developed and will fit different needs Custom Layouts VIP/Important Mode Director Controls 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. Unified Conferencing 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 70

Scheduling and Management

Scheduling and Management 72

Scheduling and Management TMS CTS-Manager 73

Scheduling and Management TMS 13.1 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 1.7.0 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 74

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 EX/MX/C series on TC5 can use OBTP TC5 on VCS CTS 1.8 CTS 1.7.0 or later TC5 on VCS 75

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: 13.1.2 / 3.0 CTS-Manager 1.6 and later 76

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

Scheduling and Management TMS 13.2 Planned release March 2012 * *Features and release date are subject to change Support for 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 Auto-extend conferences when there are no scheduling conflicts 78

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 79

Scheduling and Management CTS-Manager 1.8 with TC5 EX/MX/C series endpoints Groupware scheduling and email 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 8.6.1 VCS CTS 3010 EX90 TC5 MX200 TC5 80

Scheduling and Management Direction for future Both TMS and CTS-Manager have been developed in parallel this last year 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. 81

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 82

TelePresence Solution VMware Support Advantages of VMware - Hardware cost reduced (lower TCO) - Space and power needs consolidated - Redundancy and high availability - Fallback via snapshots 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 Yes Management, Scheduling Yes UCS 210 M2 No No CTMS Multipoint Yes UCS 210 M2 No No *Features and release date are subject to change Co-residency 83

Roadmap

Cisco Live TelePresence Breakouts Schedule Attend the following sessions to receive more detail on specific areas of the Cisco TelePresence solution BRKEVT-2802 Wednesday 9:00am BRKSPV-1900 Wednesday 9:00am BRKEVT-2801 Wednesday 4:00pm BRKEVT-2804 Thursday 11:30am BRKEVT-2803 Thursday 4:00pm BRKEVT-2319 Friday 9:00am BRKEVT-2922 Friday 11:00am BRKSPV-2900 Friday 11:00am Cisco TelePresence: deploying and provisioning video endpoints Deploying on enterprise network, CUCM, VCS/TMS, managing endpoints An Introduction to Managed TelePresence Service Creation Approaches to managed TelePresence, virtualized access, integrated collaboration Cisco TelePresence: Best practices for call control integration CUCM-VCS integration, scalability, redundancy, security, case study Cisco TelePresence: monitoring and troubleshooting video deployments Traffic patterns, endpoint health, media transport, management options Cisco TelePresence: designing and deploying multipoint video solutions Ad hoc meetings on CUCM and VCS, Conductor, scheduling meetings Cisco TelePresence: Ad hoc business to business video Expressway solution, signaling and secure media, DNS SRV, interworking Recording and Streaming Integrations for Cisco TelePresence Design, workflow considerations, TCS, MXE 3500, Show and Share Managed TelePresence Architecture and Deployment Common management, integrated call control, resilience, interconnectivity 85

Recommended Reading Please visit the Cisco Store for suitable reading.

Please complete your Session Survey We value your feedback Don't forget to complete your online session evaluations after each session. Complete 4 session evaluations & the Overall Conference Evaluation (available from Thursday) to receive your Cisco Live T-shirt Surveys can be found on the Attendee Website at www.ciscolivelondon.com/onsite which can also be accessed through the screens at the Communication Stations Or use the Cisco Live Mobile App to complete the surveys from your phone, download the app at www.ciscolivelondon.com/connect/mobile/app.html 1. Scan the QR code (Go to http://tinyurl.com/qrmelist for QR code reader software, alternatively type in the access URL above) 2. Download the app or access the mobile site 3. Log in to complete and submit the evaluations http://m.cisco.com/mat/cleu12/ 87

Thank you. 88