Overview of Cisco TelePresence Solution and Deployments

Transcription

1

2 Overview of Cisco TelePresence Solution and Deployments Michael Thomma Technical Marketing Engineer

3 Overview of This session provides an overview for all components of a TelePresence deployment including: endpoints, call control, conferencing, and scheduling/management. Subsequent breakout sessions will cover specific components of the TelePresence solution in depth. Recent releases/products and new features and functionality will be introduced and explained. Throughout this presentation, use cases will be referenced to demonstrate deploying TelePresence in different environments. Endpoints, call control, multipoint, and management design decisions will be explained. This breakout will cover CUCM, VCS, TelePresence Server, Conductor, TMS, and endpoints. 3

4 Your Collaboration Agenda For Cisco Live! Session Number Session Name Speaker Day BRKUCC-2343 Call Admission Control and Quality of Service for Collaboration Glen Lavers Tuesday Overview of Cisco TelePresence Solution and Deployments Michael Thomma Tuesday Implementation and Management of Cisco's Enterprise Session Border Controller - Cisco Unified Border Element Darryl Sladden Tuesday BRKUCC-2934 BRKCOL-2020 Cisco Interoperability with Microsoft Tobias Neumann Tuesday BRKCOL-2023 Architecting Unified Communications to enable Workspace Transformation Vanessa Sulikowski Tuesday BRKUCC-2344 Deploying Cisco Jabber on Mobile Devices Seongho Hong Tuesday BRKUCC-2801 Cisco Expressway at the Collaboration Edge design session Kevin Roarty Tuesday BRKUCC-2008 Enterprise Dial Plan Fundamentals Johannes Krohn Wednesday BRKUCC-2444 Introduction to Common Identity for Collaboration Paulo Jorge Correia Wednesday BRKCOL-2777 Emerging Video Technologies: H.265, SVC, and WebRTC Mo Zanaty Wednesday BRKEVT-2400 Scheduling Best Practices in Telepresence and Collaboration Aniello Zanfardino Wednesday BRKEVT-2803 Designing and deploying multipoint conferencing for telepresence video Richard Murphy Wednesday BRKUCC-2340 Best practices to enable rich-media Collaboration between businesses Viraj Raut Wednesday BRKEVT-2804 Monitoring and troubleshooting network impairments in video deployments Aamer Akhter Wednesday BRKUCC-3000 Advanced Dial Plan Design for Unified Communications Networks Johannes Krohn Thursday BRKCOL-2111 Capture Transform Share Robert Morris Thursday Deploying TelePresence and Video Endpoints on Unified Communications Manager Kevin McMenamy Thursday BRKEVT-2802 BRKUCC-2800 Extend the Reach of Your Cisco Video Solution with Cisco Jabber Guest Darin Dunlap Thursday BRKCOL-2114 What you need to know about Webex Enabled TelePresence Andrew Bell Thursday BRKCOL-2369 Integrating Audio Visual Systems with TelePresence Codecs Enrico Conedera Thursday BRKUCC-3420 Advance concepts to Common Identity for Collaboration Paulo Jorge Correia Friday BRKUCC-2943 Enabling Cisco Jabber for Virtual Environments Sijin Abdulkarim Friday 4

5 Collaboration Architecture Overview Headquarters Prime Collaboration TMS CUPs Unified CM VCS-E DMZ Management Call Control VCS-C Mobile Worker Conductor CUBE Internet Unity Connection Contact Center UC App Other UC Applications ISR G2 MPLS WAN ISR G2 TS TS TS Conferencing UC Applications Edge Endpoints PSTN / ISDN Remote Site

6 Agenda Introduction Pillars of Cisco solution, Terminology, Use Cases Users and Endpoints User needs and expectations, Endpoint Differentiators, New Endpoints and Software Releases Deploying on the Network CDP, Media Resiliency Call Control Unified CM, How VCS fits, Expressway, Dial Plan Conferencing Types of Conferences, TelePresence Server, MCU, Conductor Scheduling and Management TMS 14,TMS Extensions, Interaction with Infrastructure and Endpoints, WebEx Enabled TelePresence (WeT) Q&A, Roadmap 6

7 Introduction 7

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 8

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 Standardsbased Investment protection Scalability Interoperability Intercompany WebEx New experiences Doing more, better 9

10 Introduction Terminology - OBTP (One Button to Push) OBTP: User schedules TelePresence rooms in Outlook User receives confirmation Participants enter their TelePresence Rooms One button press to launch call 10

11 Users and Endpoints 11

12 Users and Endpoints TC and TX/CTS Endpoints CTS/TX endpoints TC based endpoints (SX/EX/MX/C series) (all run TC software) SX20 C20 C40 C60 CTS CTS 1100 TX 13x0-65 EX60 EX90 C90 CTS 3xx0 TX 9xx0 Profile 42 Profile 55 Profile 65 MX200/300 Latest Endpoint Release: CTS: (41) Nov 2013 TX: (90) Nov2013 Latest Endpoint Release: TC: Jan

13 Users and Endpoints Determining the Proper Experience for Users How immersive must the experience be? Resolution, mono/stereo/spatial audio Screen size, camera quality Will the user share content? If so what type of content? Doc cam, H.239 and BFCP Motion vs sharpness Will they be mobile? VPN home offices and non-vpn offices BYOD What environment will the endpoint be in? Personal space, dedicated room How simple must it be?

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

15 Users and Endpoints 15

16 Users and Endpoints TX9000 series Series Product Family Endpoints TX Immersive TX9000, TX9200, TX1310 MX Multipurpose MX200, MX300 SX Solutions SX20 EX Executive EX60, EX90 DX Smart Desk Phone DX650 C Integrator C20, C40, C60, C90 What we ve improved on: Supported on CUCM 8.5 and above What we ve kept from the CTS and T3: 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 Central wiring tray to avoid trenching Front panel access to codecs and cabling Flat reflective light panel Less-intrusive camera cluster Choice of table color: Maple or Dark Walnut 42 LED content screen Easier assembly Easier access to power and network connections 16

17 Users and Endpoints Introducing the DX650 What is it? The newest IP phone from Cisco (it also does video!) Main features: 7-inch multitouch screen Bluetooth 2 USB 2.0 ports HDMI output up to 1920 x 1200 Android 4.0 Supported on CUCM 7.1.5, 8.5, 8.6, 9.0 and above PoE 1080p30 Full HD video 17

18 Users and Endpoints Introducing the MX300 G2 Available Now! Main features: 55 screen with 1080p60 video resolution Supported on TC7 and later Multisite capable (3+1) (requires option key) Dual display output New Touch 10 Interface 10 bright & sharp (IPS) screen Hard buttons for easy access Wheel base, Floor stand, Wall mount Based on SX20 codec 18

19 Users and Endpoints Introducing the Speaker Track 60 Available 1H CY14 Main features: Superior HD video quality 1080p60 Exceptional zoom capability 10x optical, 20x with digital Low latency, direct switching between speakers Both cameras can be used independently when Speaker Track 60 is off Exceptional accuracy in tracking of active speakers, including facial recognition Recognition of partial faces Vertical and horizontal tracking Dual hunting camera capable Will be Supported with C40, C60 and C90 codecs on TC or later 19

20 20

21 Users and Endpoints Jabber Update Jabber for Windows: 9.6(0) Dec 2013 Jabber for Mac: 9.2(1) Sep 2013 Jabber for ipad: 9.3(4) Nov 2013 Jabber for iphone: 9.5 Oct 2013 No video Jabber for Android: (voice and IM) 9.1(3) June 2013 URI dialing in Jabber for Windows Video added to Jabber for iphone (already present in ipad) Jabber for Mac now supported on Apple OS X Mavericks 10.9 Jabber for ipad now supported on IOS 7 Jabber for Windows 9.2 Localizations: Arabic Italian Bulgarian Catalan (Spain) Japanese Romanian Chinese (China) Korean Croatian Chinese (Taiwan) Norwegian Slovak Czech Polish Slovenian Danish Portuguese (Brazilian) Serbian Dutch Portuguese (Portugal) Russian English Spanish Finnish French Swedish Hungarian German Thai Hebrew Greek Turkish 21

22 Comparison of Cisco video capable endpoints Jabber DX 650 EX Series MX Series Profiles TX 1310 TX 9x00 Capacity 1 person 1 person 1 person Depends on system and environment Depends on system and environment Up to 6 people Up to 18 people Headset /Handset Depending on client computer Aux audio input Aux audio input Content Sharing External Screen Depending on client computer EX90 only Resolution Up to 720p Up to 1080p30 Up to 1080p60 Up to 1080p30 Up to 1080p60 Up to 1080p60 Up to 1080p60 Remote Registration With VPN connection With VPN connection With traversal connection With traversal connection With traversal connection Embedded Multisite EX90 only Audio only Audio only Audio only OBTP 22

23 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? 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. H.323 SIP MGCP SCCP ISDN TIP 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 23

24 Users and Endpoints Standards Support CTS/TX endpoints support SIP for call setup and media negotiation starting in release and later (available for nearly 3 years) H.264 baseline profile when TIP is not used Single screen support only (CTS 3x00 and TX 9x00 will only use center screen) CUCM 8.5 or later required No configuration necessary for this. If TIP fails to negotiate endpoint will fallback to standard SIP TC based endpoints support standard H.323 and SIP for call setup/media negotiation H.261, H.263, H.263+, H.264 Receive and transmit up to 1080p 30fps (60fps on some endpoints) CTS/TX will always transmit at 30fps, but can receive any frame rate 24

25 Users and Endpoints When will a Cisco endpoint use TIP? TIP TX/CTS to TX/CTS TX/CTS to CTMS TC endpoint to CTMS TX/CTS to TS (TelePresence Server) SIP TX/CTS to TC endpoint TX/CTS to DX TX/CTS to MCU TX/CTS to any other video endpoint TX and 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. Since SIP and TIP both support HD video and content sharing, user does not need to (and will not) know which protocol is being used behind the scenes. 25

26 Users and Endpoints Content sharing Benefit of separate media channel for content allows users to customize their experience Content sharing allows users in a video call to share additional media in a separate video stream (presentation, doc camera, etc) H.323 uses H.239 SIP uses Binary Flow Control Protocol (BFCP) TIP uses a method called Auto-Collaborate Endpoint C60/C90 C40 SX20 Content Resolution Up to 1080p30/WUXGA Up to WXGAp30 Up to 1080p15 EX90 SVGA (800 x 600) to WUXGA (1920 x 1200) EX60/MX200/MX300 SVGA (800 x 600) to 1080p (1920 x 1080) CTS TX 1310 TX 9x00 Up to 1080p30 * Up to 1080p30 * Up to 1080p30 * All other CTS endpoints XGA (1024 x 768) Requires TX6 software on endpoint * In case of content channel failure, fallback is Composite or Switched video Composite Switched 26

27 Users and Endpoints Annotation TX6 release adds support for annotation Supported on CTS500-32, TX13x0, and TX 9xx0 Supported in TIP and standards based SIP calls Endpoints that support Annotation can take a snapshot of what is currently being shared, and annotate on it Any system in a TelePresence conference that can view a presentation can view the annotated presentation Users cannot save their annotated presentation after the call is finished 27

28 Users and Endpoints Free Jabber Free Cisco Jabber Video is open to the public, in all markets 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

29 Deploying on the Network 29

30 Deploying on the Network Cisco Discovery Protocol (CDP) CDP Support (min version) CTS/TX Endpoints 1.0 EX/MX/SX/Profile Endpoints TC5 E20 TE4.2 CDP is a data-link layer (layer 2) protocol and runs on all Ciscomanufactured equipment that includes: routers, bridges, access servers, switches, and endpoints. A Cisco device enabled with CDP sends out periodic interface updates to a multicast address in order to make itself known to neighbors. CDP allows two systems to learn about each other, even if they use different network layer protocols. CDP is used by endpoint to discover it s assigned VLAN

31 Deploying on the Network Additional Services and Ports Used Network Services CDP Discover VLAN DHCP (UDP ports 67,68) Option 150 (CUCM Address) Option 242 (TMS address) NTP (UDP port 123) DNS (UDP port 53) HTTP (TCP ports 80, 443, 8080, 6970) Obtain configuration and firmware Voice/Video Services SIP UDP port 5060 TCP ports 5060, 5061 RTP UDP ports

32 Video Bandwidth Requirements Environmental Factors that affect bandwidth: Lighting Motion Color / Patterns Endpoint Settings Quality Setting / Optimal Definition Profile / Call Rate CTS/TX Endpoints TC Endpoints

33 Deploying on the Network Video Bandwidth Requirements Things to consider: Is network protocol overhead included in quoted bandwidth requirements? This usually adds ~20 percent to total bandwidth Is the quoted bandwidth requirement the average or maximum bit rate? Average rates can be used unless video is being deployed on an overlay network, in which case the maximum values may be necessary to use References: Cisco Jabber for Windows: Cisco TX series: TC Endpoints, look for Optimal Definition in admin guides: 33

34 Deploying on the Network How to Preserve User Experience in Non-Ideal Networks? Si Low-speed Links Serialization delay affects frame jitter Gradual Decoder Refresh Repair-P Frames Si Old/ QoS-unaware Network Devices Small packet buffers Encoder Shaping Link Failures Sudden decrease of bandwidth Dynamic Rate Adjustment Loss Bursts Repair scheme worsens things Long-Term Reference Frames Repair-P Frames Bad Links Continuous packet loss (<5%) Forward Error Correction 34

35 Deploying on the Network Media resiliency Gradual Decoder Refresh (GDR) Predicted portion Intra -macroblock portion Decoder Encoder Serialization delay on low-speed links can cause large I-frames to arrive too late and be discarded Solution: Gradual Decoder Refresh (GDR) distributes intra picture data over N frames GDR frames contain a portion of intra macroblocks and a portion of predicted macroblocks Once all N frames have been received, decoder has fully refreshed the picture

36 Deploying on the Network Media resiliency typical packet loss scenario I1 I1 Encoder P1 P2 P3 P4... P5 P2 P P5...? P5 I1 I1 I1 P4 P3 P2 P1 Out of Sync (OOS) P1 Decoder Loss of a P-frame triggers request for a new I-frame Encoding and transmitting large I-frame takes time If any of the I-frame packets get lost, restart the process Flickering/pulsing of video when new I-frame arrives Video freeze or artifacts when multiple packets are lost

37 Deploying on the Network Media resiliency Long Term Reference Frames and Repair-P Frames (LTRF/LTRP) LTRF1 Long-Term Reference Frame (not actually sent on the wire) LTRF1 Encoder P1 P2 P3 P4 P5... P2 P ? P5 P4 Repair-P Frame Built from last sync ed LTRF P3 P2 P1 P1 P5 Decoder ACK LTRF1 OOS (P4) Keep encoder and decoder in sync with active feedback messages Encoder instructs decoder to store raw frames at specific sync points as Long-Term Reference Frames (part of H.264 standard) Decoder uses back channel (i.e. RTCP) to acknowledge LTRF s When a frame is lost, encoder creates Repair-P differential frame based on last synchronized LTRF

38 Deploying on the Network Media resiliency - Forward Error Correction (FEC) Encoder Decoder... LTRF Repair-P... R1 R Binary XOR R1 FEC FEC Binary XOR R2 Defined in RFC 5109, allows decoder to recover from limited amount of packet loss (up to ~5%) without losing synchronization Can be applied at different levels (1 FEC packet every N data packets) to protect important frames in lossy environments Trade-off is bandwidth increase 38

39 Deploying on the Network Media resiliency summary Combining all these techniques has been shown to preserve acceptable user experience even in high packet loss situations (up to 10-15%) Many of these mechanisms are currently implemented in Cisco TelePresence endpoints: CTS/TX Series EX/MX/SX/C Series Encoder shaping 1.2 TC 4.0 GDR 1.6 TC 5.0 LTRF and Repair-P 1.6 TC 4.0 FEC TC 4.0 Dynamic Rate Adjustment 1.7 TC

40 Agenda Introduction Pillars of Cisco solution, Terminology, Use Cases Users and Endpoints User needs and expectations, Endpoint Differentiators, New Endpoints and Software Releases Deploying on the Network CDP, Bandwidth Requirements, Media Resiliency Call Control Unified CM, How VCS fits, Expressway, Dial Plan Conferencing Types of Conferences, TelePresence Server, MCU, Conductor Scheduling and Management TMS 14,TMS Extensions, Interaction with Infrastructure and Endpoints, WebEx Enabled TelePresence (WeT) Q&A, Roadmap 40

41 Call Control 41

42 Call Control Cisco CUCM and Cisco VCS Cisco 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 UCS servers Uses a variety of voice and video protocols including SCCP, SIP, H.323, and MGCP Cisco VCS Designed initially for video deployments Two types: VCS Control VCS Expressway Supports 2500 registrations on single VCS, 10,000 in a cluster 42

43 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) TelePresence (Provisioning/managing of CTS, E, SX, EX, MX, TX and C series endpoints) CUCM Unity CUPS Contact Center CUCM VCS-C PSTN VCS-E Business to Business (Expressway Traversal) Additional Video Services (H.323 to SIP, 3 rd party video, IPv4 to IPv6, Jabber Video) VCS Internet Remote Registrations (Without VPN) 43

44 Call Control VCS only environment Most Recommendation functionality Vision CUCM VCS-C VCS-E Reasons for a VCS only deployment H.323 endpoints Existing voice PBX in place (non-cisco) Video only deployment Mostly room based systems TMS needed for provisioning VCS Only Deployment VCS-C VCS-E Fully Supported 44

45 How VCS Traversal Works Enterprise Network DMZ Outside Network CUCM Internet VCS-C Firewall VCS-E Firewall Signaling Media 1. VCS-E is the traversal server installed in DMZ. VCS-C is the traversal client installed inside the enterprise network. 2. VCS-C initiates traversal connections outbound through the firewall to specific ports on VCS-E with secure login credentials. 3. Once the connection has been established, VCS-C sends keep-alive packets to VCS-E to maintain the connection 4. When VCS-E receives an incoming call, it issues an incoming call request to VCS-C. 5. VCS-C then routes the call to CUCM to reach the called user or endpoint 6. The call is established and media traverses the firewall securely over an existing traversal connection

46 Call Control Evolution of traversal technology with Unified CM Problem: Remote CUCM endpoints require VPN connection to register Mobile clients rely on additional app (AnyConnect) VPN isn't always needed (or possible) Solution: Evolve VCS software to allow CUCM endpoints to take advantage of traversal technology 46

47 Call Control A New Feature and a New Product Available Now New Feature: Mobile and Remote Access Connect remotely with Jabber and TC endpoints Register directly to UCM (or higher) Voice, Video, IM&P, Directory, Visual Voic outside the network without a VPN New Product: Cisco Expressway C and Expressway E Based on same OS as VCS-C and VCS-E Same GUI, SIP Stack as VCS-C and VCS-E Supported with limited scale on existing VCS appliance via upgrade and new option key 47

48 Call Control Cisco VCS Compared to Cisco Expressway Feature Comparison Cisco VCS Family (VCS-C/VCS-E) NEW - Cisco Expressway Series (Expr-C/Expr-E) Mobile and Remote Access Y Y Video / TelePresence Device Registration & Provisioning Y N Video Session Management & Call Control Y N Video Interworking (IPv4 to IPv6, H.323-SIP, Microsoft Interop, Standards-based 3rd Party Video endpoints) Business to Business Video Y Y Y 1 Jabber Guest Y Y WebEx Enabled TelePresence Y N 2 Enhanced Security Y N Y 1 VCS required for Intra-domain Federation (FindMe) 2 Expressway-C cannot have TS or MCU registered to it 48

49 Call Control Both VCS and Expressway run x8.1 software X8.1 Cisco VCS New Offering Cisco Expressway VCS-Control No Change VCS-Expressway No Change Expressway-C Or Core Expressway-E Or Edge Specialized video applications for video-only customer base (GK, SIP Proxy, interworking, traversal) Superset of X8.1 features No changes to existing licensing model Solution designed for and sold exclusively with UCM 9.x and above Subset of X8.1 features No additional cost for server software license for CUCM 9.1+ customers 49

50 Call Control Expressway Series 50

51 Call Control Cisco Expressway Licensing No Additional Cost for Virtual Edition Fixed and Mobile Users at no additional cost Mobile and Fixed Endpoint registration IM & Presence Video and Audio Media Sessions No Cost with UCM 9.x CUCM Expressway-C Expressway-E Internet Firewall Firewall Similar to Traversal Calls Business to Business Concurrent Sessions Business to Business Video and Audio Media Sessions Expressway Rich Media Session $750 a la carte

52 Call Control Cisco Jabber Remote Access Options Unified CM & applications AnyConnect VPN Layer 3 VPN Solution Secures the entire device and it s contents AnyConnect allows users access to any permitted applications & data Unified CM & applications Expressway Firewall Traversal New Offering Session-based firewall traversal Allows access to collaboration applications ONLY Personal data not routed through enterprise network

53 Call Control Expressway solution version requirements Versions Required: Cisco Expressway X8.1 Cisco Unified CM Cisco TelePresence TC 7.0 (7.1 recommended) Jabber depends on platform No support for Cisco Unified CM 8.6 ICE (STUN/TURN) support not included in Cisco Unified CM 10.0, on roadmap for 10.5 The X8.1 release delivers three key capabilities enabling the Expressway Mobile and Remote Access Feature XCP Router for XMPP traffic HTTPS Reverse proxy Proxy SIP registrations to UCM

54 Call Control What can a Jabber client do with Expressway? Inside firewall (Intranet) DMZ Outside firewall (Public Internet) Access visual voic Internet Unified CM Expressway C Expressway E Make voice and video calls Launch a web conference Share content Search corporate directory Instant Message and Presence

55 Call Control Expressway protocol workload summary Inside firewall (Intranet) DMZ Outside firewall (Public Internet) Protocol Security Service Internet SIP TLS Session Establishment Register, Invite, etc. via UCM Unified CM Expressway C Expressway E Media SRTP Audio, Video, Content Share, Advanced Control (RTP/SRTP, BFCP, ix/xccp) Unified CM IM&P Conference Resources HTTPS TLS Logon, Provisioning/Configuration, Contact Search, Visual Voic XMPP TLS Instant Messaging, Presence Other UC Infrastructure & Resources

56 Call Control Expressway Hybrid Deployment - Cloud based IM&P Inside firewall (Intranet) DMZ Outside firewall (Public Internet) Protocol Security Service Internet SIP TLS Session Establishment Register, Invite, etc. via UCM Unified CM Expressway C Unified CM IM&P Conference Resources Expressway E Other UC Infrastructure & Resources webex Messenger Media SRTP Audio, Video, Content Share, Advanced Control (RTP/SRTP, BFCP, ix/xccp) HTTPS TLS Logon, Provisioning/Configuration, Contact Search, Visual Voic XMPP TLS Instant Messaging, Presence

57 Call Control CUCM release 9.0 URI support 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 Can be changed in CUCM 9.1 EX90 DN: Primary URI: bob@cucm.cisco.com URI: bob.home@cucm.cisco.com 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: alice@cucm.cisco.com SIP 57

58 Call Control Video Enhancements in CUCM 10.0 H.265 (HEVC) pass-through by CUCM H.264 SVC pass-through by CUCM SIP Trunk status can be monitored in RTMT Flexible DSCP and Video Promotion Allows better QoS treatment of media when desktop video endpoint is in call with immersive video endpoint. Self-provisioning by end users 58

59 Conferencing 59

60 Conferencing Many, many options Endpoint characteristics and capabilities Additional applications Conductor TMS Telepresence Server Multipoint platforms MCU Call control CUCM VCS MSE 8000 CTMS PVDMs

61 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) Ad Hoc Rendezvous Scheduled Cisco Multipoint Control Unit (MCU) Ad Hoc Rendezvous Scheduled Cisco TelePresence Multipoint Switch (CTMS) Ad Hoc Rendezvous Scheduled Embedded Conferencing (Multisite) Ad Hoc Rendezvous Scheduled 61

62 Conferencing Embedded conferencing - Multisite Endpoints capable of Multisite: C40 C60 C90 EX90 SX20 MX300 G2 Part Numbers: LIC-P65-C90-MS LIC-P55DC60-MS LIC-EX90-MS LIC-INTP-C90-MS CUCM Endpoint Configuration TC based Endpoint Configuration 62

63 Conferencing One platform for all video conferencing TelePresence Server Support for wide range of codecs Optimized conferencing ActiveControl support Multiple layouts and PIN support Available in hardware and VMWare Supports multiscreen and single screen endpoints Uses new Flex API for advanced features CTMS Only supports TIP endpoints (and 9971) No transcoding all endpoints must negotiate same resolution No layouts, full screen active speaker only EoS (Jan 2014) MCU H.323 and SIP support Auto Attendant Basic cascading No TIP support No optimized conferencing Legacy API PVDM3 No content channel No encryption Max 4CIF resolution on transcoded video Limited codec support No support for H

64 Conferencing Cisco TelePresence Server Supports H.323, SIP, and TIP Recent software upgrades has increased per blade port count Can be trunked to CUCM, registered to VCS, or managed by Conductor Features Active Presence Supports TIP in release 2.1 and later 1080p30 and 720p60 support in 2.2 Supports 3rd party multiscreen solutions Flagship Cisco multipoint solution 64

65 Conferencing TelePresence Server protocol support Version 1.0 H.323 H H.323 H.239 FECC 2.1 H.323 H.239 FECC SIP BFCP RTCP TIPv6 2.2 H.323 H.239 FECC SIP BFCP RTCP TIPv6 TIPv7 3.0 H.323 H.239 FECC DTMF SIP BFCP RTCP TIPv6 TIPv7 TelePresence Server is the only multipoint platform that supports both Cisco and non-cisco multiscreen systems TelePresence Server is the only multipoint platform that supports H.323, SIP, and TIP (no option keys necessary) (for layout control) 3.1 H.323 H.239 FECC DTMF SIP BFCP RTCP TIPv6 TIPv7 ActiveControl Cisco Clearpath 65

66 Conferencing TelePresence Server Platform Form Factors TelePresence Server on VMware Appliances Blade 8-core/16vCPU 8 to 32 ports at 360p30 1 to 4 ports at 1080p30 10-core/20vCPU 8 to 49 ports at 360p30 1 to 6 ports at 1080p to 41 ports at 360p30 1 to 5 ports at 1080p to 81 ports at 360p30 1 to 20 ports at 1080p to 97 ports at 360p30 1 to 12 ports at 1080p to 97 ports at 360p30 1 to 12 ports at 1080p30 Note: For simplicity, only capacity for 360p30 and 1080p30 are shown. TS is capable of many other resolutions and frame rates with differing limits on capacity. All numbers represent remotely managed mode (Conductor required) capability. See release notes for further detail. 66

67 Conferencing TelePresence Server Experience Single screen experience in release 2.3 and later Multiscreen experience Single ActivePresence Prominent Equal 67

68 Conferencing TelePresence Server (7010 and 8710) licensing and capacity changes Version Version 2.2 or Version 2.3 or or Version OR HD = 720p30 Full HD= 1080p30 / 720p60 Optional optimization of resources discussed later Up until TS 2.2, max of 16 screen licenses could be utilized on a single 7010 or 8710 blade Release 2.3 made the following changes: Max number of useable licenses was decreased from 16 to 12 The port count for 720p30 calls was increased from 16 ports to 24 ports These enhancements effectively gave existing customers 8 additional HD ports at no cost For existing 8710 customers who had a fully licensed 16 port TS, the now unnecessary 4 licenses could be used for future expansion on new 8710s 68

69 Conferencing TelePresence Server Deployment VCS CUCM Conductor TS Ad Hoc Rendezvous CUCM VCS TS Scheduled SIP H.323 HTTP(s) 69

70 Conferencing MCU Several models: 8510 and 8420 blade Standalone 5300 series Standalone 4500 series Standalone 4200 series (EoS) Depending on model MCU can run in nhd, SD, HD, HD+, or Full HD mode 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 Port Mode nhd SD HD HD+ Full HD Quality 360p30 W448p30 720p30 / w448p p30 (asymmetric) 1080p30 / 720p60 70

71 Conferencing CTS/TX with MCU All Cisco video endpoints are supported on both TelePresence server and MCU CTS CUCM VCS MCU CTS 1100 TX 9000 CTS called into 4501 MCU CTS endpoints are supported on MCU series starting with In any deployment with CTS 3xx0 or TX 9xx0 triple screen systems, TelePresence Server is still the recommended multipoint solution 71

72 MCU Ad hoc CUCM conference bridge CUCM added ad hoc conference bridge support for 4200, 4500, 8420, 8510, 5310 and 5320 MCU s in version 8.6 CUCM version added support for encrypted calls to MCU MCU version 4.2 or later is required to be added as a CUCM conference bridge SIP (trunk created behind the scenes) MCU API Used by CUCM CUCM HTTP(s) MCU Create Conference Modify Conference Destroy Conference Device Query (keepalive) 72

73 Conferencing MCU - Deployment VCS CUCM Conductor MCU Ad Hoc Rendezvous CUCM VCS MCU SIP Scheduled H.323 HTTP(s) 73

74 Conferencing MCU migration to TelePresence Server Same hardware, only software and licensing is changed Cisco MCU Requires Port License Conversion (PLC) key PLC key - $0 item L-MCU5300-UPG-PAK then select L-300-PLC 1 Full HD port = 1 TS Screen License Requires Conductor Requires TSMO key on Supervisor TSMO key - $0 item L-8000-CHLIC-PAK then select L-8000-TMSO 5 SD ports = 1 TS Screen License Cisco TelePresence Server

75 Conferencing Cisco TelePresence Conductor Shipping since Nov 2011 Manages TelePresence Server (vts, 310, 320, 7010, 8710) and MCU (42xx, 45xx, 53xx, 8420 & 8510) conference resources Supports ad hoc and rendezvous conferences Dialled conference aliases are agnostic of the MCU or TS that the conference is hosted on Resilient solution providing service continuity if a power failure affects a CUCM/VCS/MCU/ TelePresence Conductor Example: CUCM or VCS Conductor Full Cascaded Meeting Whole process is transparent to the end user 75

76 Conferencing Design Conferencing with VCS as call control VCS Conductor Conductor XC 1.0 Conductor release Conductor acted as policy service to VCS MCU/TS registered to VCS Conductor instructed VCS to route calls to MCU/TS Conductor XC 2.0 introduced Conductor as a B2BUA MCU/TS SIP trunk directly to Conductor (not VCS) H.323 calls are interworked via VCS Both deployment methods fully supported (CUCM deployment still recommended choice though) SIP H.323 HTTPs CPL 76

77 Conductor Integration with call control CUCM Conductor Conductor acts as SIP B2BUA Supported with XC 2.0 and Unified CM and later VCS Future development focused on this deployment Cisco VCS still fully supported and integrated via SIP trunk to CUCM SIP H.323 HTTPs CPL 77

78 Conferencing Conductor Support for TelePresence Server Support for direct integration with CUCM SIP B2BUA puts Conductor in the signaling path Improvements to logging Limited TMS scheduling support Why add another box? Allows CUCM multipoint resources to be shared for both ad hoc and rendezvous conferences Shared multipoint resources Advanced features like optimized resources on the TS are possible Central point of management for all conferencing needs 78

79 Conferencing Example of optimization of resources TelePresence Server 3.0 Conductor 2.0 Without With Conductor Conductor Once full, additional endpoints cannot join No PR Key No PR Key No PR Key Full HD (1080p30) HD (720p30) SD (480p30) 79

80 Conferencing Conductor deployment Ad hoc calls by CUCM registered endpoints use conductor to find a multipoint resource CUCM SIP Trunk(s) configured in CUCM to Conductor Conductor Certain users are configured with custom conference experiences (specific layouts, resolutions, port limits) Endpoints registered to VCS can still use Multiway to invoke a Conductor behind CUCM VCS-C Conductor added as a conference bridge in CUCM SIP H.323 HTTPs Pools of MCUs and TelePresence Servers sit behind Conductor 80

81 Scheduling and Management 81

82 Scheduling and Management 82

83 Scheduling and Management Cisco TMS and Cisco CTS-Manager TMS CTS-Manager Provisioning and configuration of endpoints Provides hierarchal directories and phonebooks for endpoints Booking and scheduling of endpoints and infrastructure (conferncing, recording, etc) Runs on windows server 2003, 2003 R2, 2008 and 2008 R2 Robust APIs available for 3 rd party applications to schedule and monitor systems Available as software (can be run in VMWare) Linux based application based on same VoiceOS as CUCM Monitors and schedules Cisco TelePresence CTS, TX, and TC based endpoints Integrates with Exchange and Lotus Domino Available as standalone UCS server and as a VM 83

84 Scheduling and Management Cisco TMS Operating System: Windows Server bit Windows Server or 64-bit Hardware Platform 84

85 Scheduling and Management TMS and TMS extensions TMSXE TMSXN TMSBA TMSPE TMSXE Cisco TelePresence Management Suite Extension for Microsoft Exchange Windows Server 2008 Windows Server 2008 R2 Integrates TMS with Microsoft Exchange (2007, 2010) via EWS Separate Server than TMS TMSXN Cisco TelePresence Management Suite Extension for Lotus Notes Windows Server 2000 Windows Server 2003 Windows Server 2008 Windows Server 2008 R2 Integrates TMS with IBM Lotus Domino Server 7.0.x, 8.0.x, 8.5.x Separate Server than TMS TMSBA Cisco TelePresence Management Suite Extension Booking API Optional feature of TMS Provides a Web Services API that interfaces with the TMS booking engine Option Key on TMS TMSPE Cisco TelePresence Management Suite Provisioning Extension Windows Server 2003 Windows Server 2008 R2 & VCS x7.1 or later Enables provisioning of telepresence users and endpoints for large-scale deployments and setting VCS FindMe options in single user portal Replaces older TMS Agent Legacy. Both are supported in TMS 13, only TMSPE supported in

86 Scheduling and Management Dashboard Management of telepresence infrastructure System Trouble tickets Conference Status Indicator System Reporting 86

87 Scheduling and Management Directly managed vs provisioned endpoints Directly managed endpoint TMS is in constant contact with endpoint (HTTP, SNMP) Devices are shown in TMS Navigator Can be scheduled (OBTP, Automatic Connect, Manual etc) Provisioned endpoint Requires TMSPE TMS Devices Direct Managed TMS Devices Direct Managed Supported on Jabber Video, E20, EX, and MX. Endpoints are authenticated against AD or local TMS database Cannot be scheduled (at least not with OBTP, address book can be used to have multipoint meetings call out to any endpoint/user) Distributes settings and phone books to users through Cisco VCS 87

88 Scheduling and Management TMS support for TX/CTS endpoints TMS release 13.1 and later supports scheduling CTS/TX endpoints CUCM 8.5 or later is required. TMS will log into CUCM (as an application user) 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 Schedule P2P calls Read system information Monitor response status and call status Dialing from the endpoint 88

89 Scheduling and Management TMS support for TX/CTS endpoints Enable Cisco CTS Native Interop setting added in TMS 13.2 Prior to 13.2: CTS/TX endpoints could only be scheduled on TS CTS/TX could not be scheduled for point to point calls to non-tip devices This setting is removed in TMS version In this version and later this setting is effectively set to Yes permanently. 89

90 Scheduling and Management TMS call launch options Automatic Connect One Button to Push Manual Connect No Connect Reservation Automatic connect: Cisco TMS will automatically connect all the participants at the specified time and date. One Button to Push: Conference dial-in information will be automatically presented on endpoints that support One Button to Push. Manual connect: At the specified time and date, the system listed as the VC- Master will be prompted to begin the call. The call will automatically be connected when the VC-Master initiates the call. No connect: This option will reserve the room(s) and generate the call route, but not connect the route. The conference can be started by clicking Connect for the participants in Conference Control Center. Reservation: This option will reserve the room(s) and will not initiate any connections. 90

91 Scheduling and Management TMS One Button to Push OBTP is available on the Cisco Touch 12, Touch 8, 797x IP phones and onscreen display (OSD) with remote control SX/EX/MX/C series on TC5 or later can use OBTP Starting with TMS 13.2, SX/EX/MX/C series endpoints registered to CUCM can still be scheduled via TMS TC5 or later CTS 1.8 or later CTS or later TC5 91

92 Scheduling and Management TMS calendaring integration with OBTP User Interface Codec/ Endpoint Multipoint Resource TMS TMSXE Exchange User Booking request passed via WS to TMS Booking API (TMSBA) Reads event in mailbox using EWS 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 and later 92

93 Scheduling and Management Introducing Smart Scheduler TMS 14.2 and later TMSPE 1.1 and later 93

94 Conferencing Deployment Unified CM Conductor VCS-C VCS-E Internet TMS WebEx Enabled TelePresence TS TS TS Ad hoc and Rendezvous Video Conferences Scheduled Video Conferences SIP HTTPs SCCP PSTN 94

95 WebEx Enabled TelePresence (WeT) 95

96 TelePresence and WebEx Working Together Cisco TelePresence Cisco WebEx Live, face-to-face communication experience over the network Share content Personal, desktop, multipurpose, integrated, and immersive endpoints Meet anytime, anywhere, in real time Deliver presentations, show documents, and demonstrate applications Pass meeting control or control a remote desktop

97 Cisco WebEx Enabled TelePresence Solution overview WebEx Client Unified CM VCS-C VCS-E TS / MCU Other Video Endpoints H.323 Endpoints Audio, Video, and Presentation over SIP OBTP EX, MX, SX, C series TMS TMSXE CTS / TX Scheduling in Outlook with WebEx PT, WebEx mailbox or via TMS Smart Scheduler or Admin booking SIP H.323 SIP TLS Media

98 Supported Product Versions Product Product version Recommended Versions WebEx Meeting Center WBS29 TMS TMSXE TMS TMSXE VCS VCS-C, VCS-E X8.1 TMS TMSXE TelePresence MCU 8510, 8420*, 5300 series, 4500 series, 4501, & 4200 series* 4.4 TelePresence Server ** 8710, TelePresence Endpoints Any supported by MCU or TS All CUCM CUCM or higher WebEx Outlook Plug-in PT WebEx Outlook Plug-in PT WBS29 * EOS products ** MP 310/320, vts and Conductor not supported today

99 In Meeting User Experience With content sharing

100 Call to Action Visit the World of Solutions:- Cisco Campus Walk-in Labs Technical Solutions Clinics Meet the Engineer Lunch Time Table Topics, held in the main Catering Hall Recommended Reading: For reading material and further resources for this session, please visit 100

101 Complete Your Online Session Evaluation Complete your online session evaluation Complete four session evaluations and the overall conference evaluation to receive your Cisco Live T-shirt 101

102 102