Cisco TelePresence Designing and Deploying Multipoint Video Solutions

Cisco TelePresence Designing and Deploying Multipoint Video Solutions BRKEVT-2803 Follow us on Twitter for real time updates of the event: @ciscoliveeurope, #CLEUR

Housekeeping 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

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

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, Telepresence Conductor, scheduling meetings Cisco TelePresence: ad-hoc business to business video Expressway solution, signaling and secure media, ICE, 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 4

Agenda Cisco Multipoint Solutions Overview Ad-hoc Meetings Ad-hoc Meetings on CUCM H.323 Registration of Instant Meetings on VCS Ad-hoc Meetings on VCS Rendez-vous Meetings General Overview Rendez-vous Meetings with Cisco Telepresence Conductor Rendez-vous Meetings with Cisco Telepresence Multipoint Switch Scheduled Meetings Scheduling using TMS Scheduling using CTS-Man Summary 5

Cisco Multipoint Solution Overview Product Overview PVDM3 Cisco MCU 4200 Series Cisco 4203 Cisco 4205 Cisco 4210 Cisco 4215 Cisco 4220 Cisco MCU 4500 Series Cisco 4505 Cisco 4510 Cisco 4515 Cisco 4520 Cisco MSE 8000 MSE 8510 HD MCU blade MSE 8420 SD MCU blade MSE 8710 TP Server blade Cisco 7010 TP Server CTMS Cisco Telepresence Multipoint Switch Five different roles spanning the whole Cisco Multipoint portfolio: - Telepresence Server (TS: Cisco MSE 8710 blade, Cisco 7010) - Software Multipoint Switch (CTMS) - HD MCUs (Cisco 4500 Series and 4501, MSE 8510) - SD MCUs (Cisco 4200 Series, MSE 8420) - PVDM3 on ISR routers as MCUs * MSE has more blades. We are considering only the multipoint enabled ones 7

Cisco Multipoint Solutions Overview Definitions Ad-hoc meetings: Impromptu meetings, not scheduled, require a user to initiate them. A p2p call escalated to a multipoint conference is considered ad-hoc as this usually happens without prior planning and scheduling. Example: CUCM Ad-Hoc services, Multiway on VCS Rendez-vous meetings: Rendez-vous conferences require endpoints to dial-in to a pre-determined multipoint resource. Include static conferences. I.e. everybody dial 3000 which is a rendez-vous meeting number. Scheduled meetings: happens when resources are booked only for a specific period of time and a specific number of participants Instant meetings: Similar to Rendez-vous meetings, but the dial-in number is created on-the-fly. Example: Auto-Attendant 8

Cisco Multipoint Solution Overview Comparison Chart TS CTMS HD MCU SD MCU PVDM3 Description Immersive and multi-purpose Immersive Multi-purpose HD Multi-purpose SD HD-only or SD Application Single/Multiscreen. Scheduled and rendez-vous Single/Multi screen. Scheduled and rendez-vous Single screen. Ad-hoc, scheduled, rendez-vous and instant. Single screen. Ad-hoc, scheduled, rendez-vous and instant. Single screen. Ad-hoc only Quality Up to 1080p@30fps or 720p@60fps. Individual Transcoding 720p or 1080p@30fps. No transcoding Up to 1080p@30fps or 720p@60fps. Individual Transcoding SD up to 480p Up to 720p@30fps. Limited transcoding capabilities (SD only) Scalability Up to 64 screens per meeting (8710). Up to 144 screens per chassis Up to 48 screens per CTMS; up to 90 screens with cascading Up to 60 HD/80 SD ports per conference (8510). Up to 180 HD/720 SD ports per chassis Up to 40 SD ports per conference (8420 or 4220). Up to 360 SD ports per chassis Scalability depends on HW and resolution Experience Active Presence Video Switching Continuous Presence Continuous Presence Video Switching 9

Ad-hoc meetings on CUCM CUCM uses two inferface to communicate with the MCU MCU Only 1 2 SIP for call control HTTP for resource management SIP HTTP 1 2 11

Ad-hoc meetings on CUCM Resource Management MCU Only Cisco TelePresence MCU Remote Management API 1- Create Conference (Allocate conference Resources, always start with 3 ports) 2- Modify Conference (Add/Remove ports) 3- Modify Conference (Duration Refresh) conf.create conf.modify conf.destroy HTTP 4- Destroy Conference (Release conference) 5- Device Query (Keepalive for the HTTP interface) MCU Reference API can be found here: http://www.cisco.com/en/us/docs/telepresence/infrastructure/mcu/api_guide/mcu_api_2-8.pdf 12

Ad-hoc meetings on CUCM Resource Management: MCU Registration MCU Only OPTIONS sip:172.18.199.32:5060 SIP/2.0 200 OK HTTP <device.query> 4xx/5xx/ HttpErr OPTIONS sip:172.18.199.32:5060 SIP/2.0 200 OK HTTP <device.query> 200OK HttpRes HTTP Signaling SIP Signaling 13

Ad-hoc meetings on CUCM Conference creation MCU Only Conference creation and resource reservation Participant 1 Participant 2 Participant 3 HTTP conference.create (confid=011030401001 200OK HttpRes INVITE sip:011030401001@172.18.199.32:5060 SIP/2.0 200 OK (SDP Offer audio, video) ACK (SDP Answer audio, video) INVITE sip:011030401001@172.18.199.32:5060 SIP/2.0 200 OK (SDP Offer audio, video) ACK (SDP Answer audio, video) INVITE sip:011030401001@172.18.199.32:5060 SIP/2.0 200 OK (SDP Offer audio, video) ACK (SDP Answer audio, video) 3-port conference resources allocated! HTTP Signaling SIP Signaling 14

Ad-hoc meetings on CUCM Adding the 4 th participants MCU Only Conference resources allocated for 3 participants HTTP Signaling SIP Signaling Add 4 th participant HTTP conference.modify (confid=011030401001, number of participants= 4 200OK HttpRes Allocate conference resources for 4 participants 4 th participant INVITE sip:011030401001@172.18.199.32:5060 SIP/2.0 200 OK (SDP Offer audio, video) ACK (SDP Answer audio, video) Same thing happens for the N+1 participant VCS participants can be invited provided that a search rule matching.*@172.18.199.32 and pointing to CUCM is added to VCS 15

Ad-hoc meetings on CUCM CUCM Interface MCU Minimal release is 4.2, CUCM is 8.6.1 MCU or PVDM3 MCU is added as a Media Resource MCU belongs to 4200, 4500, 8000 Series PVDM3 can also be selected PVDM3 No need to specify MCU type. CUCM will query it and discover how many ports is capable of 16

Ad-hoc meetings on CUCM CUCM Interface MRG/MRGL on CUCM can be used: - To share the load between MCUs inside the same MRG - To add redundancy between different MRGs inside the same MRGL - To differentiate the services (HD from SD) MCU or PVDM3 2 17

Ad-hoc meetings on CUCM MCU and Service Localization CUCM MCU or PVDM3 B A MRG Br MRGL Branch Branch Cisco 4501 IP WAN Central Site MRG HD MRG SD MRGL Central HD C Cisco 4505 Cisco 4205 D MRG SD MRG HD MRGL Central SD Selected MCU is the one defined in the MRG of the initiator of the conference. Since user A initiated the conference, the MCU selected is the 4501 If User C initiated the conference, the MCU selected would have been one of the two 4505s If User C initiated the conference while both 4505 were fully occupied, the 4205 would have been used If User D initiated the conference, the MCU selected would have been the 4205, if not available it would have been one of the 4505s CTS and EX/MX/C Series endpoints can participate but can t initiate the conference 18

Ad-hoc meetings on CUCM CUCM Interface MRG/MRGL on CUCM can be used: - To localize MCU resources while on mobility via Roaming Settings on the Device Pool, based on IP subnets - MRGL can be attached to the Device Pool - Devices get their device pool based on IP subnets and ad-hoc calls are directed to the nearest MCU Mobile user is in UK, let s allocate UK MCU Mobile user is in Italy, let s allocate IT MCU MCU or PVDM3 UK 10.58.9.0/24 Italy 10.50.10.0/24 19

Ad-hoc meetings on CUCM MCU Configuration MCU Only 1. Media Port Reservation set to "Enabled. This prevents to use the MCU for other ad-hoc services (i.e. MultiWay). 2. Incoming calls to unknown conferences or auto attendants set to "Disconnect Caller" 3. Time to wait when setting up ad hoc conference PIN set to "never configure PIN 20

Registration of instant meetings on VCS H.323 MCU registration to the VCS: H.323 ID MCU Only H.323 ID: Cisco4501 MCU VCS Control Mandatory: H323 ID to register Unit-wide H.323 registration. Can be alphanumeric. It can be dialed and it is sent to the default Auto Attendant. No numeric ID is appended after it. Example: Dial: Cisco4501. Enter 1234# in the AA interface. Conference 1234 is created via Auto Attendant and registered to VCS 22

Registration of instant meetings on VCS H.323 MCU registration to the VCS: MCU Service Prefix MCU H.323 Prefix: 81 VCS Control MCU Only Optional: MCU Service Prefix Must be numeric. It is registered to VCS and can be dialed even if the conference hasn t been created yet. It can be followed by more digits Incoming call to unknown conference specify what to do: Used to start an instant conference. Example: 81 Prefix for MCU registration Dial: 81 creates conference 81 on the MCU Dial: 81123 creates conference 123 on the MCU Dial: 81<any n of digits> creates conference <any n of digits> on the MCU 23

Registration of instant meetings on VCS H.323 MCU registration to the VCS: Prefix for MCU registration MCU H.323 Prefix: 81 VCS Control Optional: Prefix for MCU registration Must be numeric. It can t be dialed This prefix doesn t register on the VCS but when a MCU Only conference is created, it is prepended to the conference numeric ID. Should be set equal to the MCU Service Prefix 1 2 3 Used to add participant to an existing conference. Example: 81 Prefix for MCU registration No MCU Service Prefix 55 conf Numeric ID Registration is 8155. Dial: 8155 ok Dial: 8154 ko 24

Registration of instant meetings on VCS Call Flow for H.323 instant meetings MCU Only We want to create an instant conference. MCU prefixes are defined equal to 81; when the user calls that prefix followed by some more digits, the conference is created First call matches MCU Service Prefix Register MCU1 with prefixes 81 10.58.9.35 dial: 8155 VCS Control MCU1 2.Receive the call; conference 55 is created on MCU1 1. It matches MCU1 and MCU2 Service Prefixes. Select MCU1 (random) and send call Register MCU2 with prefixes 81 MCU2 10.58.9.37 25

Registration of instant meetings on VCS Call Flow for H.323 instant meetings The second call matches the E.164 number made by the Prefix for MCU registration followed by the conference numeric ID This is why both prefixes should have the same value MCU Only 3.Register conference 8155 10.58.9.35 dial: 8155 VCS Control MCU1 dial: 8155 2.Receive the call; conference 55 is created on MCU1 Why use prefixes? A single MCU might not need prefixes. Same prefixes for different MCU also used for load-sharing with H.323 instant conferences 10.58.9.37 MCU2 Prefixes are used to identify a single MCU when there is more than one (not in the example) 26

Registration of instant meetings on VCS MCU dual-registration to the VCS MCU SIP VCS Control H.323 SIP H323 registers: 81 812001 812002 MCU Only MCU H.323 Prefixes: 81 Conf Numeric ID: 2001 Conf Numeric ID: 2002 H.323 SIP registers conferences: 2001@mcu1.domain.com 2002@mcu1.domain.com dial: 2001@mcu1.domain.com While a SIP client can t dial 812001 since it adds the domain, a H.323 client can dial 2001@domain.com This might result in a call being interworked by the VCS: media passes through the VCS Careful planning of VCS searches can avoid this situation (see next slide as a reference) Best option would be to normalize the dialplan: 812001@domain.com for SIP users and 812001 for H.323 users 27

Registration of instant meetings on VCS How to avoid Interworking For Your Reference MCU VCS Control 2 Search Rules to normalize dial plan: (81)?(2\d{3})(@mcu.domain\.com)? Matches: 812XXX, 812XXX@mcu.domain.com, 2XXX, 2XXX@mcu.domain.com Replace: 81\2 (first rule) \2@\3 (second rule) Result: 81200X (first rule) 200X@mcu.domain.com (second rule) H323 prefix is 81 H.323 conferences are registered as: 812001 812002 SIP conferences are registered as: 2001@mcu.domain.com 2002@mcu.domain.com VCS can normalize dial plan Both search rules have same priority Example: A H.323 client dials 2XXX@mcu.domain.com. Both rules match, but replacement string 812XXX is registered as H.323, while 2XXX@mcu.domain.com is registered as SIP. Since native protocol has the precedence, 812XXX is chosen and the call not interworked 28

Ad-hoc meetings on VCS Multiway MCU Only Multiway feature is analogous to ad-hoc conferences on CUCM It uses the instant meeting concept A user in a call with another user, can add more participants making new calls and pressing join button Ad-hoc MCU for VCS using Multiway have port reservation mode set to disable. As such, they can t be shared with CUCM, which requires to enable port reservation Multiway uses a range of numbers, hidden to the user, to host ad-hoc conferences. Each number is a different conference In case of a VCS cluster, each range of numbers have to be unique for each member of the cluster 30

Ad-hoc meetings on VCS Multiway How it Works MCU Only In this example, alias to be configured on endpoint is multiway@vmct.lab Numbering range is between 5511 and 55165535 Conference are created to MCU and registered to VCS in this way (be 81 the MCU prefix for H.323): H.323: 815511 to 8155165535 SIP: 5511@vmct.lab to 55165535@vmct.lab VC1 VC2 VC3 VC1 calls VC2 VC1 calls VC3 VC1 presses join button and multiway alias is sent to VCS a SIP and H.323 conference is created into the MCU which registers: i.e. 8155100 and 55100@vmct.lab All calls are redirected to this alias. REFER method needed to add SIP third-party endpoints, H.323 routetomc facility message for H.323 endpoints On CUCM add a SIP Route Pattern vmct.lab to VCS 31

Ad-hoc meetings on VCS Telepresence Server Telepresence Server doesn t support ad-hoc and instant meetings and as such you can t create a meeting if it hasn t been previously defined in the Telepresence Server itself H.323 optional prefixes are not used. Only H.323 ID, which is not optional. SIP and H.323 conference use the same numeric ID. Only difference is the usage of domain part on SIP settings Careful planning of searches on VCS can avoid interworking SIP to H.323 calls on VCS (see reference slide How to avoid Interworking ) 32

Rendez-vous Meetings: General Overview Reference Architectures CUCM SIP SIP only No Cascading Static Redundancy Static Load Sharing MCU and TS SIP and H.323 Static cascading Static Redundancy Static Load Sharing MCU and TS j VCS SIP H.323 CUCM j VCS Conductor SIP and H.323 Automatic cascading Automatic Redundancy and load sharing based on MCU resource utilization MCU only (TS in future) SIP H.323 34

Rendez-vous Meeting with Cisco Telepresence Conductor What s Cisco Telepresence Conductor? 36

Rendez-vous Meeting with Cisco Telepresence Conductor What s Cisco Telepresence Conductor? Appliance model Policy service which uses HTTP and CPL to communicate with VCS Uses XML RPC over HTTPs to remotely configure MCUs Not in SIP and H.323 signaling path H.323 H.323 signaling VCS HTTPS Request CPL reply j SIP signaling SIP H.323 MCU pool Telepresence Conductor SIP XML RPC over HTTPS 37

Rendez-vous Meeting with Cisco Telepresence Conductor VCS and MCU Interaction Ask Conductor what to do with meet.team Cisco Telepresence Conductor dial: meet.team VCS MCUb is the best option. Send the call to MCUb MCUa MCUb MCUc 38

Rendez-vous Meeting with Cisco Telepresence Conductor Logic Flow 3. For meet.* : Choose MCUa Create conference n 8800 on MCUa Conference alias for the VCS: MCUa8800(@company.com)? 5. MCUa8800(@company.com)? Action: Send to MCUa and strip the prefix: 8800(@company.com)? 2. meet.* Conductor Conductor VCS 8800 4. Create conference: 8800 8800@company.com 1. meet.team@company.com MCUa MCUb 39

Rendez-vous Meeting with Cisco Telepresence Conductor MCU Pools MCU are added to the Cisco Telepresence Conductor They are grouped in Pools MCUs are chosen inside the pool based on their load In this case, MCU 2 is chosen since it has only 3 ports occupied If a MCU is down, it s removed from the selection algorithm until it s up again A single pool can contain up to 30 MCUs 5 ports used 3 ports used 6 ports used MCU 1 MCU 2 MCU 3 40

Rendez-vous Meeting with Cisco Telepresence Conductor MCU Service Preferences Service Preferences is an ordered list of pools Cisco Telepresence Conductor chose the correct pool based on the priority which has been given In this example Pool A has the priority set to 1, and it will be chosen. Pool B will be chosen if: Service Preferences Pool A - MCUs in Pool A are out of resources - MCUs in Pool A are not reachable Priority 1 Pool B Priority 2 41

Rendez-vous Meeting with Cisco Telepresence Conductor Conference Templates Conference Templates set up specific configuration for all the MCUs belonging to the ordered pools specified in the MCU Service Preference Type (Conference or Lecture) Limit number of participants Allow cascading Allow content Conference Layouts Parameters to pass to the MCUs in the ordered pool list or to the cascaded MCUs (encryptionrequired, PIN, layoutcontrol, etc.) 42

Rendez-vous Meeting with Cisco Telepresence Conductor Conference Aliases RegEx can be used to create aliases for conference Different aliases can endup in the same conference Conferences are created by the Cisco Telepresence Conductor when the conference start and pushed to the selected MCU(s) Aliases are directly connected to a Template and close the chain: Alias Template Service Preference MCU Pool MCU 43

Rendez-vous Meeting with Cisco Telepresence Conductor An example: Create a range of conferences Any dialed number between 5500 and 5599 starts or joins a conference. Conference is created on the MCU and its name is the same as the dialed number with no domain (5500, 5501...) SIP endpoints will dial 55XX@domain.lab and will also start or join the conference 44

Rendez-vous Meeting with Cisco Telepresence Conductor An example: Create a range of conferences This template, linked to the 55XX conference, select a Meeting as conference type Reserve 1 port for cascading and is attached to the Service Preference called Service Pool 1 Selects the layout Specify that the conference needs PIN, and that anyone can select a customized layout 45

Rendez-vous Meeting with Cisco Telepresence Conductor MCU View Before Meeting Starts MCU conferences are not active on the MCUs of the pools selected by the ServicePreference 46

Rendez-vous Meeting with Cisco Telepresence Conductor MCU Views after the Meeting has started: user has dialed 5500 After the meeting has started, a new conference named 5500 is created Even if 88800032 is the numeric ID, you can access the conference dialing 5500. The real conf numeric ID is hidden by the user and not reachable PIN and layout control are pushed into the configuration It matches the Conductor Conference Name Real conf numeric ID created by the Conductor on the MCU. Conductor uses it to route calls to the VCS, prepended by the MCU prefix, MCUa88800032. VCS strips the prefix and routes the call to the MCU 47

Rendez-vous Meeting with Cisco Telepresence Conductor Flexible alias configuration Alias can be alphanum and support RegEx When a user dials meet.record@conductor.lab, a meeting is started on the MCU selected The TCS (recorder) is automatically added as a auto-dialed participant associated to this template. Cascading is also possible if the number of users exceed the MCU capacity 48

Rendez-vous Meeting with Cisco Telepresence Conductor Automatic Cascading MCU of the same pool or belonging to pool linked by the same MCU Service Preference can cascade to each other Cascading occurs when the number of ports exceed the capacity of a single MCU Requires port reservations on the Template Ports are reserved at the Service Preference Level in the Primary MCU Cascading is hub and spoke 49

Rendez-vous Meeting with Cisco Telepresence Conductor Software compatibility TelePresence Conductor Solution Requirement To set up a backend infrastructure network with TelePresence Conductor these software versions are required: Parameter TelePresence VCS TelePresence MCU TelePresence Management Suite Unified Communication Manager H.323 Endpoint / SIP UA Supported Software version X6.0 or newer version 4.2(1.43) or newer version TMS 13.1.2 or newer version CUCM 8.5 or newer version N/A (TelePresence Conductor solution use standard H.323/SIP call flow between Endpoint and MCU via VCS) 50

Rendez-vous Meeting with Cisco Telepresence Conductor Example: MCU Localization Configuration Italian users will use Italy_Pool UK users will use UK_Pool If Italian MCUs are out of resources, UK MCUs will be used, and vice-versa meet.italy@company.com Template Italy Service Preference Italy Italy_Pool meet.uk@company.com Template UK Service Preference UK UK_Pool Priority 1 UK_Pool Priority 1 Italy_Pool Priority 2 Priority 2 51

Rendez-vous Meeting with Cisco Telepresence Conductor Example: MCU Localization Telepresence Conductor VCS Cluster User 3 User 4 User 2 User 1 Italy_Pool UK_Pool Priority 1 Cascading Link Priority 2 Telepresence Conductor and Multiway Interaction: Multiway number range can be configured to be the alias for a Conductor. In this way Multiway can also have cascading, redundancy and load-sharing. However, Conductor is not consulted when an endpoint enters the conference and this might lead to exceed the MCU port capacity 52

Rendez-vous Meeting with Cisco Telepresence Conductor Telepresence Management Suite Conference Management from TMS Active conference management via Conference Control Center 53

Rendez-vous Meeting with Cisco Telepresence Conductor Telepresence Management Suite Conference Management from TMS Adding participant Managing the conference participants Snapshot of what a user sends and receives Single participant list for cascaded conferences 54

Cisco Telepresence Multipoint Switch version 1.8 Overview CTMS is the software multipoint device for TIP endpoints only (CTS, EX/MX/C Series codec with release TC5) Only Video Switching (no Active Presence) It is trunked to CUCM. VCS devices can join a CTMS meeting using the SIP connection between CUCM and VCS EX/MX/C Series codecs can be registered to CUCM or to VCS. This holds true for scheduled meeting with CTS-Man 1.8 A single CTMS supports up to 48 segments Static redundancy and load sharing (using CSS and Partitions) and cascading CTS endpoints EX/MX/C Series 56

Cisco Telepresence Multipoint Switch version 1.8 TIP Endpoints Wide Support MX Series w/tc5 C Series and Profiles w/tc5 EX Series w/tc5 CTS World 57

Cisco Telepresence Multipoint Switch version 1.8 Rendez-vous meetings CTMS is SIP Trunked to CUCM A range of numbers for rendez-vous meeting has to be defined A Rendez-vous meeting (called static meeting on CTMS interface) is always active and can be dialed at any time 58

Cisco Telepresence Multipoint Switch version 1.8 Network Multipoint Feature (NMP) A single CTMS supports up to 48 segments If the number of participants increases, it is possible to use the Network Multipoint Feature, analogous to MCU cascading NMP works for rendez-vous meeting only (no scheduled or admin-initiated meetings) 2 CTMS max, 90 ports max (3 ports are used for NMP) No Security CUCM version 8.5, 8.6 and above No need for configuration on CTMS side All configuration is done at CUCM level 59

Cisco Telepresence Multipoint Switch version 1.8 Network Multipoint: explanation through an example CTMS1 range for rendez-vous: 7XXX CTMS2 range for rendez-vous: 8XXX Basic rule for NMP: if a number dialed into CTMS is not on the Route Pattern range of CTMS itself, the CTMS will dial that number back to the CUCM Static meeting defined as 7001 on CTMS1 and 8001 on CTMS2 Behavior: using CSS and Partition, some endpoints which dial 8001 will be directed to CTMS2, other will be directed to CTMS1, which will dial into CTMS2 60

Cisco Telepresence Multipoint Switch version 1.8 NMP: diagram Endpoint 1 Endpoint 2 dial: 8001 dial: 8001 Send 8001 to CTMS 1 Send 8001 to CTMS 2 dial: 8001 cascading link CTMS 1 8001 is not in my CTMS 2 7XXX range! Calling CUCM 8XXX 8001 is mine, call accepted 61

Cisco Telepresence Multipoint Switch version 1.8 NMP: Partition and CSS Devices CSS s Partitions Trunks CTS and TC5 Endpoints in London London_css CTMS1_part RP: 7XXX RP: 8XXX CTMS2_part CTMS1 SIP Trunk CTMS1 RP: 8XXX CTMS1 SIP Trunk CTMS1_css GK_part CTS_and_TC5_part 2XXX (for ad-hoc from CTMS Interface) CTMS2 SIP Trunk CTMS2_css CTMS1_part RP: 7XXX CTS and TC5 Endpoints in Milan Milan_css CTMS2_part RP: 7XXX RP: 8XXX CTMS2 SIP Trunk CTMS2 Route Patterns 62

Cisco Telepresence Multipoint Switch version 1.8 NMP: Partition and CSS Devices CTS and TC5 Endpoints in London 8001 CSS s Partitions Trunks London_css CTMS1_part RP: 7XXX RP: 8XXX CTMS2_part RP: 8XXX CTMS1 SIP Trunk Not mine! CTMS1 CTMS1 SIP Trunk CTMS1_css GK_part CTS_and_TC5_part 2XXX (for ad-hoc from CTMS Interface) CTMS2 SIP Trunk CTMS2_css CTMS1_part RP: 7XXX Link estabilished! CTS and TC5 Endpoints in Milan Milan_css CTMS2_part RP: 7XXX RP: 8XXX CTMS2 SIP Trunk CTMS2 Route Patterns 63

Cisco Telepresence Multipoint Switch version 1.8 NMP CSS and Partition detail For Your Reference SITE 1 Explanation Partition CSS Endpoints General CSS_CTMS1 Route Pattern for CTMS1 For cascaded meetings, i.e. 8XXX CTMS1 / SIP Trunk to CTMS1 / CSS_CTMS2 Route Pattern for CTMS1 For local meetings with no cascading, i.e. 7XXX CTMS1 / Endpoints on Site 1 can dial 8001 to join a cascaded meeting. They will arrive to CTMS1, and then CTMS1 will cascade to CTMS2, optimizing the bandwidth between Site 1 and Site 2 Endpoints on Site 1 can dial 7001 to join a local meeting with no cascading 64

Cisco Telepresence Multipoint Switch version 1.8 NMP CSS and Partition detail For Your Reference SITE 2 Explanation Partition CSS Endpoints General CSS_CTMS2 Route Pattern for CTMS2 For cascaded meetings, i.e. 7XXX CTMS2 / SIP Trunk to CTMS2 / CSS_CTMS1 Route Pattern for CTMS2 For local meetings with no cascading, i.e. 8XXX CTMS2 / Endpoints on Site 2 can dial 7001 to join a cascaded meeting. They will arrive to CTMS2, and then CTMS1 will cascade to CTMS1, optimizing the bandwidth between Site 1 and Site 2 Endpoints on Site 2 can dial 8001 to join a local meeting with no cascading 65

Cisco Telepresence Multipoint Switch version 1.8 NMP: Link cost Site 2: 22 endpoints Site 1: 10 endpoints Site 3: 10 endpoints Two concurrent meetings spanning 3 different sites. Sites 2 has 10 participants to Site 1 and 12 participants to Site 3 (total 22) With a single CTMS on site 2, the result would have been 20 participants over the WAN Adding 2 more CTMS, you can have just 6 participants over the WAN: saving roughly 70MBps of traffic over the WAN 66

Cisco Telepresence Multipoint Switch version 1.8 NMP: CTMS View CTMS 1 CTMS 2 Meeting 9001 Meeting 9001 Local endpoints 67

Scheduling using TMS Telepresence Management System Systems management Multi-vendor endpoints Infrastructure gear Diagnostics, monitoring, notification & reporting Personalization of Video TMS Agent and Scalability Support for VCS Clusters Easy, efficient setup of highly scalable E20 and Movi large scale deployments Multiple scheduling options Exchange (Outlook) Domino (Notes) Scheduler XML API 69

Scheduling using TMS Telepresence Management System Reference architecture is VCS, MCUs, TS and TMS MCUs and TS s need to be added to the TMS No support for CTMS right now Scheduling has to be enabled on the multipoint devices A range of numbers has to be configured for scheduling on TMS interface TMS can consider the endpoint embedded MCU, and schedule that instead of an external MCU: 70

Scheduling using TMS Telepresence Server Selection TMS 13.1 will always choose a TS when there is at least a CTS endpoint, regardless from the fact that the CTS supports native interoperability or not TMS will always choose a TS if no MCU is available Starting from TMS 13.2, it is possible to configure the following behavior: - Enable Cisco CTS Native Interop Call Routing set to No. A TS will always be selected if there is at least a CTS endpoint - Enable Cisco CTS Native Interop Call Routing set to Yes. A TS will be selected only if there are CTS with 3 screens. If not, a MCU will be selected. Since this behavior requires that CTS support native interoperability, please make sure that all your CTS systems support release 1.8 or above 71

Scheduling using TMS TMS: How to Join 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 72

Scheduling using TMS TMS: Scheduling Flow User schedules a meeting Using MS Exchange, Lotus Domino, Web Interface or Scheduling APIs TMS chooses the MCU/TS Using IP Zones 73

Scheduling using TMS TMS: Zone Concept Endpoints 1,2,3,4,5 are invited in the same meeting TMS could select between MCU1 and MCU2: since the majority of endpoints is in Zone Italy, MCU1 will be selected Endpoint 1 Endpoint 2 Zone Italy Endpoint 3 MCU1 Endpoint 4 MCU2 Endpoint 5 Zone UK 74

Scheduling using TMS TMS: Zone Configuration Every device can be assigned a Zone based on its location 75

Scheduling using TMS TMS: Scheduling Flow User schedules a meeting Using MS Exchange, Lotus Domino, Web Interface or Scheduling APIs TMS chooses the MCU/TS Using IP Zones Selects the number Configured as a range in TMS which is specific for each MCU Sends the information for people to join or connect automatically Email, OBTP or Automatic Connect User joins 77

Scheduling using TMS TMS, MCU/TS and VCS Interaction: Start of the conference At the selected time, the followings happen: VCS Control Conference 6000 is now routable SIP registration: 6000@company.com H323 registration (might include prefix): 816000 Conference created, registering to VCS conference.create numeric ID 6000 TMS MCU 78

Scheduling using TMS TMS, MCU/TS and VCS Interaction: Start of the conference After TMS MCU and number selection, the followings happen: VCS Control User 1 I have this, is MCU 2 Dial: 6000@company.com for SIP 6000 for H.323 816000 for H.323 w/prefixes TMS User 1 Joined conference 6000 MCU 79

Scheduling using TMS TMS, MCU and VCS Interaction: End of the conference VCS Control 6000 is not routable anymore conference.destroy Delete conference 6000 and de-register it from the VCS TMS MCU 80

Scheduling using TMS MCU/TS Failover with TMS During the meeting the MCU/TS goes out of service TMS monitors the MCU and understands it is out of services (if failover is enabled on TMS) TMS chooses another MCU/TS Using IP Zones Randomly selects the number TMS creates a meeting on the MCU with a numeric ID used for VCS registration Sends the information for people to join or connect automatically If automatic connect is the chosen method, no action is requested on user s side User joins 81

Scheduling using TMS MCU/TS Failover with TMS Automatic Connect TMS instructs the MCU/TS to call users at the selected time 11/21/11 11:16:26 AM CallConnected MCU4501 Call Connected: 5000 11/21/11 11:16:23 AM CallConnected MCU4501 Call Connected: 5010 11/21/11 11:16:20 AM CallInfo MCU4501 H323 Dial => 5000 11/21/11 11:16:20 AM CallInfo MXP1700lab Sent message to participant MXP1700lab 11/21/11 11:16:20 AM CallInfo MXP1700lab Meeting allocated on port: 1 11/21/11 11:16:20 AM CallConnected MCU4501 Call Connected: 5008 11/21/11 11:16:19 AM CallInfo MCU4501 H323 Dial => 5010 11/21/11 11:16:19 AM CallInfo MCU4501 H323 Dial => 5008 82

Scheduling using TMS MCU/TS Failover with TMS Automatic Connect The MCU/TS is unavailable 11/21/11 11:19:31 AM CallInfo Cisco4205 Meeting allocated on port: 1 11/21/11 11:19:30 AM ConferenceInfo Main system changed from MCU4501 to Cisco4205 11/21/11 11:19:30 AM ConferenceInfo Non-secure conference. Original value of the setting was 'if possible' and not all participants support encryption 11/21/11 11:19:25 AM ConferenceInfo Conference Updated 11/21/11 11:19:24 AM ConferenceWarning MCU4501 Attempting automatic MCU failover. New conference main participant will be Cisco4205. 11/21/11 11:19:19 AM PollMasterFailed MCU4501 No response from main system 11/21/11 11:19:09 AM ConferenceWarning MCU4501 Automatic MCU failover in 10 seconds. 11/21/11 11:19:09 AM PollMasterFailed MCU4501 No response from main system 83

Scheduling using TMS MCU/TS Failover with TMS Automatic Connect Another MCU/TS is selected and participants are auto-dialed 11/21/11 11:19:36 AM CallConnected Cisco4205 Call Connected: 5000 11/21/11 11:19:35 AM CallConnected Cisco4205 Call Connected: 5010 11/21/11 11:19:32 AM CallConnected Cisco4205 Call Connected: 5008 11/21/11 11:19:31 AM CallInfo Cisco4205 H323 Dial => 5000 11/21/11 11:19:31 AM CallInfo Cisco4205 H323 Dial => 5008 11/21/11 11:19:31 AM CallInfo Cisco4205 H323 Dial => 5010 11/21/11 11:19:31 AM CallInfo Cisco4205 Meeting allocated on port: 1 84

Scheduling with CTS-Manager Main Characteristics One Button to Push (OBTP) for CTS systems OBTP for EX/MX/C Series endpoints with release TC5 Scheduling multiparty meetings on Multipoint Switch for TIP devices Scheduling multiparty meetings on Telepresence Server for legacy devices CTMS/TP Server selection Possibility of including endpoints not supporting OBTP on a scheduled meeting on a Telepresence Server CTS-Man and CTMS support WebEx OneTouch 1.0 86

Scheduling with CTS-Manager 1.8 Multipoint selection CTS-Man 1.8 adds support for Cisco Telepresence Server No support for MCU 87

Scheduling with CTS-Man 1.8 CTS-Manager TelePresence Server Support CTS-Man allows adding CTMS, CUVC or MXE, and TS as bridges/servers CTS-Man utilizes an API user created on the TS to create/modify/delete meetings TS must be on version 2.2 or later Multiple TelePresence Servers can be managed A Preferred Multipoint Device can be chosen If set as primary device, CTMS will be used when endpoints are TIP compliant - TS will be used when endpoints don t have the capabilities to join CTMS or - TS will be used when CTMS is out of segments If set as primary device, TS will be used for every call - CTMS will be used when TS is out of segments - CTMS will be used when WebEx OneTouch is s requested by the user 88

Scheduling and Management CTS-Manager with EX/MX/C Series Endpoints running TC5 Groupware scheduling and e-mail 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 different possible endpoints: CTS, EX/C-Series, and Video Conferencing (non-tip) OBTP on CTS and EX/C-Series using Cisco Touch 8 or OSD with remote CTS-Man 1.8 CUCM 8.6.1 VCS TC5 CTS 3010 TC5 EX90 TC5 TC5 EX90 C90 C90 89

Scheduling and Management Direction for future Both TMS and CTS-Man 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. CTS-Manager will have several more minor releases, but bulk of engineering resources is devoted to porting all existing CTS-Man functionality to TMS platform. 90

Summary Reference architectures for Ad-Hoc, Rendez-vous and Scheduled Meetings Ad-Hoc on CUCM Ad-Hoc on VCS Rendez-Vous with Cisco Telepresence Conductor Scheduling with TMS Scheduling with CTS-Man 91

Connect with Your Peers and Cisco Discuss business, IT, architecture, adoption and product topics with peers -Unified communications, collaboration applications, customer care, telepresence Cisco Collaboration Community and User Group Interact with Cisco Product Managers, Technical Marketing Engineers and Services Consultants Learn about new product announcements Join the Collaboration User Group -Influence product direction -Access to Beta trials -Exclusive programs, advisory groups and briefings -Membership is free! Visit the Collaboration Community and join the Collaboration User Group at: www.cisco.com/go/joinconversation 92

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/ 94

Thank you. 96