Deployment Guide for Cisco Spark Hybrid Media Service

Transcription

1 First Published: Last Modified: Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA Tel: NETS (6387) Fax:

2 2018 Cisco Systems, Inc. All rights reserved.

3 CONTENTS Preface CHAPTER 1 New and Changed Information ix Hybrid Media Service Overview 1 Quality of Service on Hybrid Media Nodes 2 Hybrid Media Node Demo Software 2 Hybrid Media Clusters 3 Hybrid Media Cluster Deployment 3 Cisco Spark Device Registers with Cisco Collaboration Cloud 4 Round-trip Delay Tests Cloud Device Fails to Reach On-Premises Cluster 5 Round-trip Delay Tests Cloud Device Successfully Reaches On-Premises Cluster 6 On-Premises and Cloud Call 7 On-Premises Call with Different Cluster Affinities 7 Cisco Spark Cloud Device Connects to Cloud 8 Cisco Spark On-Premises Device Connects to On-Premises Cluster 8 Cisco Spark On-Premises Device Connects to Cloud 9 CHAPTER 2 Prepare Your Environment 11 Requirements for Hybrid Media Service 11 Call Capacity on Hybrid Media Node Platforms 14 Deployment Models Supported by Hybrid Media Service 15 Deployment Models For Hybrid Media Service and Cisco Unified Communications Manager 16 Ports and Protocols Used by Hybrid Media Service 18 Bandwidth Requirements for Hybrid Media Service 22 Requirements for Cisco Spark Services and Cisco WebEx 24 Complete the Preinstallation Checklist for Hybrid Media Service 25 CHAPTER 3 Deploy Hybrid Media Service 27 iii

4 Contents Hybrid Media Service Deployment Task Flow 27 Install Hybrid Media Service Software 28 Log in to the Hybrid Media Node Console 29 Set the Network Configuration of the Hybrid Media Node 30 Register the Hybrid Media Node to the Cisco Collaboration Cloud 31 Configure Unified CM SIP Traffic Routing for Hybrid Media 32 Configure Expressway SIP Traffic Routing for Hybrid Media 36 Enable Hybrid Media Service for the WebEx Site 39 Assign Collaboration Meeting Rooms to Cisco Spark Users 39 CHAPTER 4 Manage Hybrid Media Service 41 View Hybrid Media Service Reports 41 Available Reports 41 Reporting Definitions 44 Filtering Reports 44 Exporting Reports 44 Deregister Hybrid Media Node 45 Move Hybrid Media Node 45 Set Hybrid Media Cluster Upgrade Schedule 46 Delete Hybrid Media Cluster 46 Deactivate Hybrid Media Service 47 Manage Hybrid Media Node 47 Change Hybrid Media Node Network Settings 47 Change the Administrator Passphrase of the Hybrid Media Node 48 Manage Hybrid Media Node Password Expiry 49 Run a Ping from Hybrid Media Node 49 Enable Debug User Account 49 Send Logs from Hybrid Media Node 50 Check Health of Hybrid Media Node 51 Configure Container Network on Hybrid Media Node 51 Factory Reset a Hybrid Media Node 52 CHAPTER 5 Troubleshoot Hybrid Media Service 53 Troubleshoot the Hybrid Media Node Registration 53 iv

5 Contents APPENDIX A Feature Comparison and Migration Path from Collaboration Meeting Room Hybrid to Hybrid Media Service 55 APPENDIX B TelePresence Interoperability Protocol and Segment Switching 59 v

6 Contents vi

7 Full Cisco Trademarks with Software License THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) 7

8 Full Cisco Trademarks with Software License 8

9 New and Changed Information This table covers new features or functionality, changes to existing content, and any major errors that were fixed in the Deployment Guide. For information about Hybrid Media Node software updates, see the Hybrid Media Service Release Notes. Date Change January 30, 2018 Removed TCP Port 8080 from Ports and Protocols Used by Hybrid Media Service, on page 18. January 26, 2018 In Configure Unified CM SIP Traffic Routing for Hybrid Media, on page 32, added this support statement about route patterns: Hybrid Media Nodes support two route patterns: sitename.webex.com and meet.ciscospark.com. Other route patterns are unsupported. January 11, 2018 Added Manage Hybrid Media Service, on page 41 section that contains configuration and diagnostic procedures that can be performed from Hybrid Media Nodes. ix

10 New and Changed Information Date January 5, 2018 Change Cisco Spark Hybrid Media Service now supports on-premises SIP registered endpoints joining Cisco WebEx meetings and Cisco Spark meetings. Feature overview is added to Hybrid Media Service Overview, on page 1. Prepare Your Environment chapter updates: Requirements for Hybrid Media Service, on page 11 (Licensing requirements, call control/meeting requirements, endpoint requirements.) Deployment Models For Hybrid Media Service and Cisco Unified Communications Manager, on page 16 (New section.) Ports and Protocols Used by Hybrid Media Service, on page 18 (Added ports for SIP endpoints, updated Hybrid Media Node ports.) Requirements for Cisco Spark Services and Cisco WebEx, on page 24 (New section.) Deployment chapter updates: Configure Unified CM SIP Traffic Routing for Hybrid Media, on page 32 (New section.) Configure Expressway SIP Traffic Routing for Hybrid Media, on page 36 (New section.) Enable Hybrid Media Service for the WebEx Site, on page 39 (New section.) Assign Collaboration Meeting Rooms to Cisco Spark Users, on page 39 (New section.) Manage Hybrid Media chapter updates: View Hybrid Media Service Reports, on page 41 (Added new reports and updated existing reports.) New appendices added: Feature Comparison and Migration Path from Collaboration Meeting Room Hybrid to Hybrid Media Service, on page 55 TelePresence Interoperability Protocol and Segment Switching, on page 59 December 8, 2017 Added Hybrid Media Service Deployment Task Flow, on page 27 Moved troubleshooting content to new chapter. x

11 New and Changed Information Date November 2, 2017 October 11, 2017 Change In Requirements for Hybrid Media Service, on page 11, added the following information on the subnet range used by Hybrid Media Nodes: Hybrid Media Nodes do not respond to any internal traffic originating from the /16 IP range, because this subnet is used by internal services on Hybrid Media Nodes. As a result, Hybrid Media Nodes do not communicate with external devices or clients on this subnet. Updated bandwidth diagrams with cascading information. Revised the statement on using the same VLAN or subject for nodes in a cluster. August 15, 2017 July 19, 2017 Added port 22 (SSH) to Ports and Protocols Used by Hybrid Media Service, on page 18. Added requirements and an overview for the Hybrid Media Node demo software image. xi

12 New and Changed Information xii

13 CHAPTER 1 Hybrid Media Service Overview Cisco Spark Hybrid Media Service dynamically finds the optimal mix of on-premises and cloud conferencing resources. On-premises conferences stay on premises when there are enough local resources. When local resources are exhausted, conferences then expand to the cloud. Cisco Spark Hybrid Media Node is software that is installed on a Cisco UCS server and managed in Cisco Spark Control Hub. Cisco Spark (basic and advanced) meetings, Cisco WebEx-powered meetings, and Cisco Spark calls (between two people) can be routed to the local, on-net Cisco Spark Hybrid Media node. Cisco Spark Hybrid Media Service selects the most efficient way to use the available resources. Cisco Spark Hybrid Media Service provides these benefits: Improves quality and reduces latency by allowing you to keep your calls on premises. Extends your calls transparently to the cloud when on-premises resources have reached their limit or are unavailable. Manage your Hybrid Media Nodes from the cloud with a single interface: Cisco Spark Control Hub ( Optimize resources and scale capacity, as needed. Combines the features of cloud and on-premises conferencing in one seamless user experience. Reduces capacity concerns, because the cloud is always available when additional resources are needed. Provides advanced reporting on capacity and usage in Uses local media processing when users dial in to a Cisco WebEx Meeting Center Video (formerly CMR Cloud) or Cisco Spark space meeting from standards-based SIP endpoints and clients: SIP based endpoints and clients (Cisco endpoints, Jabber, 3rd party SIP), registered to on-premises call control (Cisco Unified Communications Manager or Expressway), that call into a Cisco WebEx meeting or Cisco Spark space meeting. Cisco Spark app (including paired with room devices) that join a Cisco WebEx meeting. Cisco Spark room and desk devices (including Cisco Spark Board) that directly join a Cisco WebEx meeting. Provides optimized audio and video interactive voice response (IVR) to on-net SIP based endpoints and clients. WebEx clients (internal and external) continue to join meetings from the cloud. 1

14 Quality of Service on Hybrid Media Nodes Hybrid Media Service Overview H.323, IP dial-in, and Skype for Business (S4B) endpoints continue to join meetings from the cloud. Supports 1080p high definition video as an option for meetings, if meeting participants that can support 1080p are hosted through the local on-premises Hybrid Media nodes. (If a participant joins an in-progress meeting from the cloud, on-premises users continue to experience 1080p on supported endpoints.) Quality of Service on Hybrid Media Nodes, page 2 Hybrid Media Node Demo Software, page 2 Hybrid Media Clusters, page 3 Quality of Service on Hybrid Media Nodes For Quality of Service (QoS), Hybrid Media Nodes natively mark all traffic (audio, video, content, ix, BFCP, and so on) with DSCP AF41. Hybrid Media Node Demo Software Use the demo image for Hybrid Media Nodes only for demo purposes. We recommend that you avoid adding a demo image to an existing production cluster. The demo cluster accepts fewer calls than production and expires 90 days from registration to the cloud. Note The Hybrid Media Node demo software is not supported by Cisco TAC. Specifications See Requirements for Hybrid Media Service, on page 11 for the supported platforms and specifications for hybrid media node software. Capacity See Call Capacity on Hybrid Media Node Platforms, on page 14. Use Cases for the Hybrid Media Node Demo Software Media Anchored to On-Premises Deploy and configure the node with the demo software. Run a meeting that includes the following participants: a Cisco Spark app participant, Cisco Spark endpoint participant, and a Cisco Spark Board. After the meeting is over, from the customer view in go to Reports to access the Hybrid Media reports. In the reports, you can see that the media stayed on-premises. 2

15 Hybrid Media Service Overview Hybrid Media Clusters Meeting with Cloud and On-Premises Participants Run another meeting with a couple of Cisco Spark participants on-premises and one in the cloud. Observe that all participants can seamlessly join and participate in the meeting. Known Issue DNS works, but may fail to save network configuration under certain conditions when you use FQDN for hostname and NTP servers. As a workaround, use IP addresses only so that you can save the initial configuration. Related Topics Requirements for Hybrid Media Service, on page 11 Hybrid Media Clusters Hybrid Media Nodes are deployed in clusters. A cluster defines Hybrid Media Nodes with similar attributes, such as network proximity. Cisco Spark participants are directed to use a particular cluster or the cloud, depending on the following conditions: A client on a corporate network that can reach an on-premises cluster will connect to it the primary preference for clients that are on the corporate network. A client that cannot reach an on-premises cluster will connect to the cloud the case for a mobile device that is not connected to the corporate network. Each cluster contains logic that cascades meetings across other clusters, as needed. Cascading provides data path for media between clients in their meetings. Meetings are distributed across nodes and the clients land on the most efficient node nearest to them, depending on factors such as network topology, WAN link, and resource utilization. Reachability is determined by the client's ability to "ping" media nodes. A variety of potential connection mechanisms such as UDP and TCP are used during an actual call. Before the call, the Cisco Spark device (room, desk, and app) registers with the Cisco Collaboration Cloud, which provides a list of cluster candidates for the call. Hybrid Media Cluster Deployment Create fewer clusters when resources have similar network proximity (affinity). Whererever possible when creating clusters, add nodes that are in the same geographical region and the same data center. Typically, deploy clusters in enterprises that host frequent localized meetings. Plan where you place clusters on the bandwidth available at various WAN locations inside the enterprise. Over time, you can deploy and grow cluster-by-cluster based on observed user patterns. Clusters located in different time zones can effectively serve multiple geographies by taking advantage of different peak/busy hour calling patterns. 3

16 Cisco Spark Device Registers with Cisco Collaboration Cloud Hybrid Media Service Overview If you have two hybrid media nodes in two separate data centers (EU and NA, for example), and you have endpoints join through each data center, the nodes in each data center would cascade to a single media node in the cloud. Theses cascades would go over the Internet. If there is a cloud participant (that joins before one of the HMN participants), the nodes would be cascaded through the cloud participant s media node. Time Zone Diversity Time zone diversity can allow clusters to be shared during off-peak times. For example: A company with a Northern California cluster and a New York cluster might find that overall network latency is not that high between the two locations that serve a geographically diverse user population. When resources are at peak usage in the Northern California cluster, the New York cluster is likely to be off peak and have additional capacity. The same applies for the Northern California cluster, during peak times in the New York cluster. These aren't the only mechanisms used for effective deployment of resources, but they are the two main ones. Overflow to the Cloud When the capacity of all on-premises clusters are reached, an on-premises participant overflows to the Cisco Collaboration Cloud. This does not mean that all calls will be hosted in the cloud. Only those participants that are either remote or can't connect to an on-premises cluster will be directed to the cloud. In a call with both on-premises and cloud participants, the on-premises cluster is bridged (cascaded) to the cloud to combine all participants into a single call. Cisco Spark Device Registers with Cisco Collaboration Cloud In addition to determining reachability, the clients also perform periodic round-trip delay tests using Simple Traversal of UDP through NAT (STUN). STUN round-trip (SRT) delay is an important factor when selecting potential resources during an actual call. When multiple clusters are deployed, the primary selection criteria are based on the learned SRT delay. Reachability tests are performed in the background, initiated by a number 4

17 Hybrid Media Service Overview Round-trip Delay Tests Cloud Device Fails to Reach On-Premises Cluster of factors including network changes, and do not introduce delays that affect call setup times. The following two examples show possible reachability test outcomes. Round-trip Delay Tests Cloud Device Fails to Reach On-Premises Cluster 5

18 Round-trip Delay Tests Cloud Device Successfully Reaches On-Premises Cluster Hybrid Media Service Overview Round-trip Delay Tests Cloud Device Successfully Reaches On-Premises Cluster Learned reachability information is provided to the Cisco Collaboration Cloud every time a call is set up. This information allows the cloud to select the best resource (cluster or cloud), depending on the relative location of the client to available clusters and the type of call. If no resources are available in the preferred cluster, additional clusters are tested for availability based on SRT delay. A preferred cluster is chosen with the lowest SRT delay. Calls are served on premises from a secondary cluster when the primary cluster is busy. Local reachable Hybrid Media resources are tried first, in order of lowest SRT delay. When all local resources are exhausted, the participant connects to the cloud. Cluster definition and location is critical for a deployment that provides the best overall experience for participants. Ideally, a deployment should provide resources where the clients are located. If not enough resources are allocated where the clients make the majority of calls, more internal network bandwidth is consumed to connect users to distant clusters. 6

19 Hybrid Media Service Overview On-Premises and Cloud Call On-Premises and Cloud Call On-premises Spark devices that have the same cluster affinity (preference, based on proximity to the cluster) connect to the same cluster for a call. On-premises Spark devices with different on-premises cluster affinities, connect to different clusters and the clusters then bridged to the cloud to combine the two environments into a single call. On-Premises Call with Different Cluster Affinities 7

20 Cisco Spark Cloud Device Connects to Cloud Hybrid Media Service Overview The Spark device connects to either on-premises cluster or cloud based upon its reachability. The following show examples of the most-common scenarios. Cisco Spark Cloud Device Connects to Cloud Cisco Spark On-Premises Device Connects to On-Premises Cluster 8

21 Hybrid Media Service Overview Cisco Spark On-Premises Device Connects to Cloud Cisco Spark On-Premises Device Connects to Cloud 9

22 Cisco Spark On-Premises Device Connects to Cloud Hybrid Media Service Overview 10

23 CHAPTER 2 Prepare Your Environment Requirements for Hybrid Media Service, page 11 Call Capacity on Hybrid Media Node Platforms, page 14 Deployment Models Supported by Hybrid Media Service, page 15 Deployment Models For Hybrid Media Service and Cisco Unified Communications Manager, page 16 Ports and Protocols Used by Hybrid Media Service, page 18 Bandwidth Requirements for Hybrid Media Service, page 22 Requirements for Cisco Spark Services and Cisco WebEx, page 24 Complete the Preinstallation Checklist for Hybrid Media Service, page 25 Requirements for Hybrid Media Service Cisco Spark Hybrid Media Service is available with the offers documented at License Requirements for Cisco Spark Hybrid Services. The media for both needs to be on the Cisco Spark platform. Table 1: Call Control and Meeting Requirements for Hybrid Media Service Component Purpose Minimum Supported Version On-Premises call control Cisco Unified Communications Manager, Release 10.5(2) SU5 or later Cisco Expressway-C or E, Release X8.9.2 or later 11

24 Requirements for Hybrid Media Service Prepare Your Environment Component Purpose Meeting infrastructure Failover handling One Button to Push (OBTP) Minimum Supported Version Cisco WebEx WBS , WBS , WBS31.20, and WBS and above, enabled with Cisco WebEx video platform version 2.0. (You can verify that your WebEx site is on video platform version 2.0 if it has the Media Resource Type list available in the Cloud Collaboration Meeting Room site options.) To ensure that your site is ready for Hybrid Media Service, contact your customer success manager (CSM) or partner. Note Hybrid Media Service does not work on WebEx sites with telephony service provider (TSP) audio. Cisco Expressway C/E traversal pair, X8.7.1 or later Cisco TMS and Cisco TMSXE5.2, T31 WebEx Productivity Tools Table 2: Endpoint Requirements Component Purpose Supported WebEx Endpoints Supported versions of the Cisco Spark app Supported codecs Minimum Supported Version See WebEx Meeting Center Video Compatibility and Support. See for supported platforms. See the Cisco WebEx Meeting Center Video Conferencing Data Sheet for a list of supported audio and video codecs. Note these caveats for Hybrid Media Service: For video quality, Hybrid Media Service supports up to 1080p in certain scenarios. You can configure this setting in admin.ciscospark.com. For SIP video systems, Hybrid Media Service supports SIP clients that do dual tone multi frequency (DTMF) audio tones. The service also supports keypad markup langauage (KPML). H.323 clients are mentioned in the data sheet, but they only go to the cloud. 12

25 Prepare Your Environment Requirements for Hybrid Media Service Component Purpose Supported Cisco Spark Room Devices Minimum Supported Version Cisco Spark Room Kit Plus Cisco Spark Room Kit Plus Precision 60 Cisco Spark Room Kit Cisco Spark Room 55 Cisco Spark Room 70 Cisco Spark Board 55 Cisco Spark Board 70 Cisco TelePresence SX20 Quick Set Cisco TelePresence SX10 Quick Set Cisco TelePresence SX80 Codec Cisco TelePresence MX200 G2 Cisco TelePresence MX300 G2 Cisco TelePresence MX700 Cisco TelePresence MX800 Cisco DX70 Cisco DX80 13

26 Call Capacity on Hybrid Media Node Platforms Prepare Your Environment Table 3: Configuration Requirements for Hybrid Media Node Software Hardware Configuration Cisco Multiparty Media 410v server Specifications for Production Software Image 48vCPUs 60 GB main memory 250 GB local hard disk space Specifications for Demo Software Image Common Requirements VMware ESXi 6 or vsphere 6 or later 2 vcpus Hyperthreading enabled Cisco Meeting Server 1000 Note We do not support the first generation MM400v server. 72vCPUs 60 GB main memory 250 GB local hard disk space Specifications-based Configuration 48vCPUs 60 GB main memory 250 GB local hard disk space 2.6 GHz Intel Xeon E5-2600v3 or later processor 12vCPUs 8 GB main memory 20 GB local hard disk space 2.0 GHz or later processor For more information on the demo software, see Hybrid Media Node Demo Software, on page 2. Call Capacity on Hybrid Media Node Platforms Table 4: Call Capacity on Hybrid Media Node Platforms Server Maximum Simultaneous High Definition Calls Per Server MM410v (Full Version) Cisco Spark only 100 (720p) 75 (1080p) Standard-based SIP Endpoints and Cisco Spark apps/devices 65 (720p) 48 (1080p) 14

27 Prepare Your Environment Deployment Models Supported by Hybrid Media Service Server Maximum Simultaneous High Definition Calls Per Server CMS 1000 (Full Version) Demo Version Software Cisco Spark only 100 (720p) 75 (1080p) 10 (720p) 5 (1080p) Standard-based SIP Endpoints and Cisco Spark apps/devices 80 (720p) 60 (1080p) Deployment Models Supported by Hybrid Media Service The following are supported in a Hybrid Media Service deployment: You can deploy a Hybrid Media Node in either a data center (preferred) or demilitarized zone (DMZ). For guidance, see Ports and Protocols Used by Hybrid Media Service, on page 18. For example deployments, see Deployment Models with Cisco Unified Communications Manager The following types of address translation are supported: IPv4 Dynamic Network Address Translation (NAT) using an IP pool Dynamic Port Address Translation (PAT) Other forms of NAT should work as long as the correct ports and protocols are used, but we do not officially support them because they have not been tested. Static IP address for the Hybrid Media Node The following are not supported in a Hybrid Media Service deployment: IPv6 DHCP for the Hybrid Media Node Dual network interfaces (NICs) This capability is not used for Hybrid Media Service. Audio, video, or media that does not pass through a Hybrid Media Node: Audio from phones Peer-to-peer call between Cisco Spark app and standards-based endpoint Audio termination on Hybrid Media Node Media sent through Expressway C/E pair, Video call back 15

28 Deployment Models For Hybrid Media Service and Cisco Unified Communications Manager Prepare Your Environment Related Topics Deployment Models For Hybrid Media Service and Cisco Unified Communications Manager, on page 16 Deployment Models For Hybrid Media Service and Cisco Unified Communications Manager These examples show common Hybrid Media Service deployments and help you understand where Hybrid Media clusters can fit in to your network. Keep in mind that Hybrid Media deployment depends on factors in your network topology: Data center locations Office locations and size Internet access location and capacity In general, try to tie the Hybrid Media Nodes to the Unified CM or Session Management Edition (SME) clusters. As a best practice, keep the nodes as centralized as possible to the local branches. Hub and Spoke Architecture 16

29 Prepare Your Environment Deployment Models For Hybrid Media Service and Cisco Unified Communications Manager This deployment model involves centralized networking and internet access. Typically, the central location has a high employee concentration. In this case, a Hybrid Media cluster can be located at central location for optimized media handling. Locating clusters in branch locations may not yield benefits in the short term and may lead to suboptimal routing. We recommend that you deploy clusters in a branch only if there is frequent communication between branches. Geographic Distribution The geographically distributed deployment is interconnected, but can exhibit noticeable latency between regions. Lack of resources can cause suboptimal cascades to be setup in the short term when there are meetings between users in each geographical location. In this model, we recommend that you allocate of Hybrid Media Nodes near regional internet access. 17

30 Ports and Protocols Used by Hybrid Media Service Prepare Your Environment Geographic Distribution with SIP Dialing This deployment model contains regional Unified CM clusters. Each cluster can contain a SIP trunk to select resources in the local Hybrid Media cluster. A second trunk can provide a failover path to an Expressway pair if resources become limited. Ports and Protocols Used by Hybrid Media Service To ensure a successful deployment of Hybrid Media Service, make sure you open the following ports for use with the protocols. See this document to understand network requirements for Cisco Spark services. See the Cisco Spark Firewall Traversal Whitepaper for more information about firewall and network practices for Cisco Spark services. 18

31 Prepare Your Environment Ports and Protocols Used by Hybrid Media Service To mitigate potential DNS query issues, follow the DNS Best Practices, Network Protections, and Attack Identification documentation when you configure your enterprise firewall. Figure 1: Ports and Protocols for Management The Hybrid Media Nodes in a cluster should be in the same VLAN or subnet mask. Purpose Source Destination Source IP Source Port Transport Protocol Destination IP Destination Port Management Management computer Hybrid Media Node As required Any TCP, HTTPS Hybrid Media Node 443 SSH for access to Hybrid Media admin console Management computer Hybrid Media Node As required Any TCP Hybrid Media Node 22 Transcoding and Playback Gateway service on Hybrid Media Node(s) Hybrid Media Node As required Any TCP, HTTPS (Websocket) Any Intracluster Communication Hybrid Media Node Hybrid Media Node IP address of other Hybrid Media Nodes in the cluster Any TCP Hybrid Media Node

32 Ports and Protocols Used by Hybrid Media Service Prepare Your Environment Purpose Source Destination Source IP Source Port Transport Protocol Destination IP Destination Port Management Hybrid Media Node Cisco Collaboration Cloud As required Any UDP, NTP UDP, DNS Any TCP, HTTPS (Websockets) Cascade Signaling Hybrid Media Node Cisco Collaboration Cloud Any Any TCP Any 444 Management Hybrid Media Node Cisco Collaboration Cloud As required Any TCP, HTTPS *.docker.io *.wbx2.com *.webex.com 443 Management Hybrid Media Node (1) Hybrid Media Node (2) Hybrid Media Node (1) Any TCP, HTTPS (Websockets) Hybrid Media Node (2) * The default configuration in the OVA is configured for NTP and DNS. The OVA requires that you open those ports outbound to the internet. If you configure a local NTP and DNS server, then ports 53 and 123 are not required to be opened through the firewall. Figure 2: Ports and Protocols for Cisco Spark Meetings 20

33 Prepare Your Environment Ports and Protocols Used by Hybrid Media Service Purpose Source Destination Source IP Source Port Transport Protocol Destination IP Destination Port Calling to meeting Apps (Cisco Spark mobile, web and desktop apps) Cisco Spark room, desk, or board device Hybrid Media Node As required Any UDP and TCP (Used by the Cisco Spark app) SRTP (Any) Any 5004, 5006 Cascade Hybrid Media Node Cisco Collaboration Cloud As required UDP, SRTP (Any)** Any 5004 Cascade Hybrid Media Node Hybrid Media Node As required UDP, SRTP (Any)** Any 5004, 5006 ** TCP is also supported, but not preferred because it may affect media quality. For the best experience using Cisco Spark in your organization, configure your firewall to allow all outbound TCP and UDP traffic that is destined toward ports 5004 as well as any inbound replies to that traffic. The port requirements listed above assume that Hybrid Media Nodes are deployed either in the LAN (preferred) or in a DMZ and that Cisco Spark apps are in the LAN. Table 5: Ports and Protocols for Cisco Spark Meetings and WebEx Meeting Center Video Meetings (Standards-Based SIP Endpoints) Purpose Source Destination Source IP Source Port Transport Protocol Destination IP Destination Port Communication between all Unified CM nodes and Hybrid Media Nodes Unified CM Hybrid Media Node Unified CM IP address or FQDN 5060 TCP, UDP Hybrid Media Node host IP address 5060 Communication between all Hybrid Media Nodes and Unified CM nodes Hybrid Media Node Unified CM Hybrid Media Node host IP address 5060 TCP, UDP Unified CM IP address or FQDN

34 Bandwidth Requirements for Hybrid Media Service Prepare Your Environment Purpose Source Destination Source IP Source Port Transport Protocol Destination IP Destination Port Cascade Media to Transcoding Gateway client on Hybrid Media Node(s) Transcoding engine client on Hybrid Media Node As required UDP, SRTP Any Media to Playback Gateway client on Hybrid Media Node(s) Playback engine client on Hybrid Media Node As required Any UDP, SRTP Any Playback Engine Circle-as-a-Service Hybrid Media Node Playback engine logger on Hybrid Media Node Any TCP SIP Signaling SIP Client SIP microservice container on Hybrid Media Node As required TCP Hybrid Media Node host IP address Calling to Meeting SIP Client Gateway service on Hybrid Media Node As required Any UDP/SRTP Hybrid Media Node host IP address Bandwidth Requirements for Hybrid Media Service Below are some common meeting scenarios that involve Hybrid Media Nodes and when a cascade is created. Hybrid Media Service is adaptive depending on the available bandwidth and distributes resources accordingly. For devices in the meeting that use the Hybrid Media Node, the cascade link provides the benefit of reducing average bandwidth. Based on the active speakers in the meeting, the cascade links that are established. Each cascade can contain up to 6 streams. 22

35 Prepare Your Environment Bandwidth Requirements for Hybrid Media Service Figure 3: One-to-One Local Call Bandwidth Requirements Figure 4: One-to-One Local-Remote Call Bandwidth Requirements Figure 5: Multiparty Local Call Bandwidth Requirements 23

36 Requirements for Cisco Spark Services and Cisco WebEx Prepare Your Environment Figure 6: Multiparty Local-Remote Call Bandwidth Requirements Requirements for Cisco Spark Services and Cisco WebEx Work with your partner, customer success manager (CSM), or trials representative to correctly provision the Cisco WebEx site and Cisco Spark services for Hybrid Media Service: 1 You must have a Cisco Spark organization with Cisco Spark services. 24

37 Prepare Your Environment Complete the Preinstallation Checklist for Hybrid Media Service 2 You must have a Cisco WebEx Meeting Center Video site. To take full advantage of Hybrid Media Service, make sure your WebEx site is on Cisco WebEx video platform version 2.0. (You can verify that your WebEx site is on video platform version 2.0 if it has the Media Resource Type list available in the Cloud Collaboration Meeting Room site options.) 3 You must enable CMR for your WebEx site under user profiles. (You can do this in a bulk update CSV with the SupportCMR attribute). Note If you have a WebEx site that is managed on Cisco WebEx Site Administration, we recommend that you link it with Cisco Spark now, in order to have access to a wider set of features. Related Topics Feature Comparison and Migration Path from Collaboration Meeting Room Hybrid to Hybrid Media Service, on page 55 Complete the Preinstallation Checklist for Hybrid Media Service Use this checklist to ensure you are ready to install and configure your Hybrid Media Node. Use this checklist to ensure you are ready to install and configure Hybrid Media Nodes and integrate a Cisco WebEx site (on Cisco WebEx video platform version 2.0) with Hybrid Media Service. Procedure Step 1 Ensure the following is in place: Meet the minimum system requirements described in Requirements for Hybrid Media Service, on page 11 and License Requirements for Cisco Spark Hybrid Services. Understand the call capacity levels described in Call Capacity on Hybrid Media Node Platforms, on page 14 Understand the supported deployment models described in Deployment Models Supported by Hybrid Media Service, on page 15. Ensure that your network allows connectivity on the ports and using the protocols described in Ports and Protocols Used by Hybrid Media Service, on page 18 Ensure that your network supports the bandwidth requirements described in Bandwidth Requirements for Hybrid Media Service, on page 22 Step 2 Step 3 Work with your partner, customer success manager, or trials representative to understand and prepare your WebEx environment so that it's ready to connect to Hybrid Media Service. For more information, see Requirements for Cisco Spark Services and Cisco WebEx, on page 24. Acquire the following information from your network administrator to assign to your Hybrid Media Node: IP address Network mask 25

38 Complete the Preinstallation Checklist for Hybrid Media Service Prepare Your Environment Gateway IP address DNS servers NTP servers (Optional) Choose the hostname to be configured on the Hybrid Media Node. Note If you plan to configure Hybrid Media Node with FQDN, you must create both forward- and reverse-dns (A- and PTR-records) in the DNS configuration. Step 4 Step 5 Step 6 Before starting installation, make sure your Cisco Spark organization is enabled for Hybrid Media Service. This service is available for organizations with certain paid Cisco Spark subscriptions as documented in Requirements for Hybrid Media Service, on page 11. Contact your Cisco partner or account manager for assistance. Choose a supported hardware or specifications-based configuration for your Hybrid Media Node, as described in Requirements for Hybrid Media Service, on page 11. Note Only one network interface card (NIC) is supported. Make sure your server is running VMware ESXi 6 (or later) and vsphere 6 (or later) with a VM host operational. What to Do Next Install Hybrid Media Service Software, on page 28 26

39 CHAPTER 3 Deploy Hybrid Media Service Hybrid Media Service Deployment Task Flow, page 27 Install Hybrid Media Service Software, page 28 Log in to the Hybrid Media Node Console, page 29 Set the Network Configuration of the Hybrid Media Node, page 30 Register the Hybrid Media Node to the Cisco Collaboration Cloud, page 31 Configure Unified CM SIP Traffic Routing for Hybrid Media, page 32 Configure Expressway SIP Traffic Routing for Hybrid Media, page 36 Enable Hybrid Media Service for the WebEx Site, page 39 Assign Collaboration Meeting Rooms to Cisco Spark Users, page 39 Hybrid Media Service Deployment Task Flow Before You Begin Prepare Your Environment, on page 11 Procedure Command or Action Purpose Step 1 Install Hybrid Media Service Software, Use this procedure to deploy a Hybrid Media Node to on page 28 your host server running VMware ESXi. You install the software on-premises which creates a node. You'll register it to the cloud later. Step 2 Log in to the Hybrid Media Node Console, on page 29 Sign in to the console for the first time. The Hybrid Media Node software has a default password. You need to change this value before you configure the node. Step 3 Set the Network Configuration of the Hybrid Media Node, on page 30 Use this procedure to configure the network settings for the Hybrid Media Node. You'll set a static IP address 27

40 Install Hybrid Media Service Software Deploy Hybrid Media Service Command or Action Purpose and change the hostname and NTP servers, if needed. DHCP is not currently supported. Step 4 Step 5 Register the Hybrid Media Node to the Cisco Collaboration Cloud, on page 31 Configure the following as needed: Configure Unified CM SIP Traffic Routing for Hybrid Media, on page 32 Configure Expressway SIP Traffic Routing for Hybrid Media, on page 36 Use this procedure to register Hybrid Media Nodes to the Cisco Collaboration Cloud. When you use Cisco Spark Control Hub to register your node, you create a cluster to which the node is assigned. A cluster contains one or more media nodes that serve users in a specific geographic region. SIP devices don't support direct reachability, so you must use Unified CM or Expressway configuration to establish a relationship between on-premises registered SIP devices and your Hybrid Media Service clusters. Step 6 Step 7 Enable Hybrid Media Service for the WebEx Site, on page 39 Assign Collaboration Meeting Rooms to Cisco Spark Users, on page 39 Use this procedure to enable optimized media for Cisco WebEx Meeting Center Video meetings. Install Hybrid Media Service Software Use this procedure to deploy a Hybrid Media Node to your host server running VMware ESXi. You install the software on-premises which creates a node. You'll register it to the cloud later. Before You Begin Read the Virtualization Software Requirements documentation to understand supported harware, coresidency inforormation, supported network configuration, supported VMWare versions and features. Make sure you have these required items: A computer with: VMware vsphere client 6.0 or later For a list of supported operating systems, refer to VMware documentation. Hybrid Media Service software OVA file downloaded Download the latest Hybrid Media Service software From the customer view inhttps:// admin.ciscospark.com, and go to Services > Hybrid Media > Set Up > Settings. There, you can access both the production and demo software images. 28

41 Deploy Hybrid Media Service Log in to the Hybrid Media Node Console A supported server with VMware ESXi 6.0 or later installed and running Procedure Step 1 Step 2 Step 3 Step 4 Using your computer, open the VMware vsphere client and sign in to the ESXi system on the server. Go to File > Deploy OVF Template. On the Source page, identify where the OVA file is located, and then click Next. On the OVF Template Details page, click Next, choose the type of deployment configuration, and then click Next. MM410v CMS 1000 The options are listed in the order of increasing resource requirements. Step 5 Step 6 Step 7 Step 8 Step 9 On the Name and Location page enter a Name for this Hybrid Media Node (for example, "Hybrid_Media_Node_1"), and then click Next. On the Disk Format page, ensure that the default disk format of Thick Provision Lazy Zeroed is selected and then click Next. On the Network Mapping page, choose the network option from the list of entries to provide the desired connectivity to the VM. On the Ready to Complete page, click Finish. After deployment of the OVA is complete, your Hybrid Media Node appears in the list of VMs. Right-click the Hybrid Media Node VM, and then choose Power > Power On. The Hybrid Media Service software is installed as a guest on the VM Host. You are now ready to sign in to the console and configure your Hybrid Media Node. Troubleshooting Tips You may experience a delay of a few minutes before the node containers come up. A bridge firewall message appears on the console during first boot, during which you can't sign in. What to Do Next Log in to the Hybrid Media Node Console, on page 29 Log in to the Hybrid Media Node Console Sign in to the console for the first time. The Hybrid Media Node software has a default password. You need to change this value before you configure the node. Procedure Step 1 From the VMware vsphere client, go to your Hybrid Media Node VM, and then choose Console. 29

42 Set the Network Configuration of the Hybrid Media Node Deploy Hybrid Media Service Step 2 Step 3 Step 4 Step 5 Step 6 The Hybrid Media Node VM boots up and a login prompt appears. If the login prompt does not appear, press Enter. You may briefly see a message that indicates the system is being initialized. Use the following default username and password to log in: a) Login: admin b) Password: cisco Because you are logging in to your Hybrid Media Node for the first time, you must change the administrator passphrase (password). For (current) password, enter the default password (from above), and then press Enter. For new password, enter a new passphrase, and then press Enter. For retype new password, retype the new passphrase, and then press Enter. A "Password successfully changed" message appears, and then the initial Cisco Hybrid Media Node screen appears with a message about unauthorized access being prohibited. Press Enter to load the main menu. What to Do Next Set the Network Configuration of the Hybrid Media Node, on page 30 Set the Network Configuration of the Hybrid Media Node Use this procedure to configure the network settings for the Hybrid Media Node. You'll set a static IP address and change the hostname and NTP servers, if needed. DHCP is not currently supported.. Procedure Step 1 Step 2 Step 3 Step 4 From the main menu of the Hybrid Media Node console, choose option 2 Edit Configuration and then click Select. Read the prompt that the calls will end on this Hybrid Media Node, and then click Yes. Click Static, enter the IP address, Mask, Gateway, and DNS values for your network. Your Hybrid Media Node must have an internal IP address and resolvable DNS name. The node IP address must not belong to the IP address range reserved for Hybrid Media Node internal use. The default reserved IP address range is , which can be configured in the Diagnostic menu. Deploy all the devices on the same subnet or VLAN, so that all devices in a cluster are reachable from wherever the clients reside in your network. (Optional) Change the hostname, domain, or NTP server(s), if required. Note To ensure a successful registration to the cloud, use only lowercase characters in the hostname that you set for the Hybrid Media Node. Capitalization is not supported at this time. When using hostname, you must also enter a valid and resolvable domain. The total length of the FQDN must not exceed 64 characters. 30

43 Deploy Hybrid Media Service Register the Hybrid Media Node to the Cisco Collaboration Cloud Step 5 Click Save, and then click Save Changes & Reboot. During the save, DNS validation is performed if you provided a domain. A warning is displayed if the FQDN (hostname and domain) is not resolvable using the DNS server addresses provided. You may choose to save by ignoring the warning but calls will not work until the FQDN can resolve to the DNS configured on the node. After your Hybrid Media Node reboots, the network configuration changes take effect. What to Do Next Register the Hybrid Media Node to the Cisco Collaboration Cloud, on page 31 Register the Hybrid Media Node to the Cisco Collaboration Cloud Use this procedure to register Hybrid Media Nodes to the Cisco Collaboration Cloud. When you use Cisco Spark Control Hub to register your node, you create a cluster to which the node is assigned. A cluster contains one or more media nodes that serve users in a specific geographic region. Before You Begin Once you begin registration of a node, you must complete it within 60 minutes or you have to start over. Ensure that any popup blockers in your browser are disabled or that you allow an exception for admin.ciscospark.com. For best results, deploy all nodes of a cluster in the same data center. See Hybrid Media Clusters, on page 3 for how they work and best practices. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 From the customer view in go to Services, and then click Set Up from the Hybrid Media card. Note On this page, you can review the prerequisites. See Complete the Preinstallation Checklist for Hybrid Media Service, on page 25 for more information. Make sure you have installed and configured your Hybrid Media Node, click Yes, I'm ready to register my Hybrid Media Node, and then click Next. For the first field, choose one: Tip Enter a name for the cluster to which you want to assign your Hybrid Media Node Choose an existing hybrid media cluster to add the new node to. We recommend that you name a cluster based on where the nodes of the cluster are located geographically. Examples: "San Francisco" or "New York" or "Dallas." In the second field, enter the FQDN or internal IP address of your Hybrid Media Node and then click Next. Enter the same internal IP address that you used to configure the node from the console. Click Go to Node to register the node to the Cisco Collaboration Cloud. 31

44 Configure Unified CM SIP Traffic Routing for Hybrid Media Deploy Hybrid Media Service A new browser tab opens to check the node. Step 6 Step 7 Step 8 Check Allow Access to the Hybrid Media Node, and then click Continue. Click Allow. Your account is validated, your Hybrid Media Node is registered and the message "Registration Complete" appears indicating your Hybrid Media Node is now registered to the Cisco Collaboration Cloud. Click the portal link or close the tab to go back to the Media Service page. On the Media Service page, you now see the new cluster that contains the Hybrid Media Node that you registered. Your Hybrid Media Node shows a service status of Operational is ready for use in your Cisco Spark organization. Note When you deploy a new Hybrid Media Node, Cisco Spark apps and room devices won't recognize the new node for up to 2 hours. The clients check for node reachability during startup, a network change, or cache expiration. You can wait for 2 hours or, as a workaround, restart your Cisco Spark app or reboot the Cisco Spark room or desk device. Afterwards, call activity is captured in the Hybrid Media reports in Cisco Spark Control Hub. What to Do Next To register additional Hybrid Media Nodes, go to the Media Service page, click Add Resource and follow Steps 3-8. Configure Unified CM SIP Traffic Routing for Hybrid Media Configure SIP trunks to route SIP dial-in and dial-out for Cisco WebEx meetings to Hybrid Media Nodes. SIP devices don't support direct reachability, so you must use Unified CM configuration to establish a relationship between on-premises SIP devices and your Hybrid Media Service clusters. You can create a trunk routing policy that reflects cluster preferences, and is highly available and resilient to device failures. If you use Unified CM Session Management Edition (SME), configure trunks on the Unified CM SME and leaf systems so that inbound and outbound calls are evenly distributed across the Unified CM servers within the Session Management cluster. Typically, each site will have a dedicated Unified CM cluster associated with it. These clusters will be connected through intercluster SIP trunks. Each cluster will have call-in trunks to the local site for the Hybrid Media Nodes. You can also configure your deployment to handle failure or overflow conditions. This configuration helps if there's an outage or if the Hybrid Media clusters reached capacity. If the SIP meeting or call cannot be established with a cluster, the meeting or call will overflow to the cloud. Before You Begin See Deployment Models For Hybrid Media Service and Cisco Unified Communications Manager, on page 16 to understand common deployment examples. The Hybrid Media Node supports only TCP between Unified CM and SIP signaling. SIP TLS is not currently supported. 32

45 Deploy Hybrid Media Service Configure Unified CM SIP Traffic Routing for Hybrid Media Each SIP trunk can support up to 16 Hybrid Media Node destinations (IP addresses). Incoming ports on SIP trunk security profile can be default (Non Secure SIP Trunk Profile). Hybrid Media Nodes support two route patterns: sitename.webex.com and meet.ciscospark.com. Other route patterns are unsupported. Figure 7: Example Deployment of Hybrid Media Service with Distributed Unified CM Procedure Step 1 Create a SIP profile for Hybrid Media Nodes: a) From Cisco Unified CM Administration, go to Device > Device Settings > SIP Profile, and then click Find. b) Choose Standard SIP Profile For Cisco VCS, and then click Copy. c) Enter a name for the new profile for example, Hybrid Media SIP Profile. d) Under Trunk Specific Configuration, set Early Offer support for voice and video calls to Best Effort (no MTP inserted). You can apply this setting to a new SIP trunk to the Cisco Collaboration Cloud (routed by the external domain for the WebEx site). The setting does not affect any existing SIP trunking or call routing. e) Make sure that Enable OPTIONS Ping to monitor destination status for Trunks with Service Type is checked. f) Leave all other fields with their default values and save your changes. Step 2 Add a new SIP trunk security profile for Hybrid Media Nodes: a) From Cisco Unified CM Administration, choose System > Security > SIP Trunk Security Profile, and then click Add New. b) Enter a meaningful name, such as Hybrid Media Trunk Security Profile c) Confirm these settings: 33

46 Configure Unified CM SIP Traffic Routing for Hybrid Media Deploy Hybrid Media Service Field Device Security Mode Incoming Transport Type Outgoing Transport Type Incoming Port SIP V.150 Outbound SDP Offer Filtering Value Non Secure TCP+UDP TCP 5060 Use Default Filter Step 3 d) Leave all other fields with their default values and save your changes. Add a new SIP trunk to point to your Hybrid Media Nodes: In a Unified CM-only deployment, add a single trunk. In an SME deployment, add a trunk between Unified CM and SME and another trunk between SME and Hybrid Media Nodes. Both trunks must have the same settings specified below. a) From Cisco Unified CM Administration, choose Device > Trunk, and then click Add New. b) Choose SIP Trunk for the trunk type; leave the other values and click Next. c) Enter a meaningful name, such as Hybrid_Media_SIP_Trunk_UCMtoHMN. d) For Calling and Connecting Party Info Format, check Deliver URI and DN in connected party, if available. This setting enables blended identity. It allows the SIP trunk to transmit the enterprise-side party's directory URI to Cisco Spark. e) Check Run On All Active Unified CM Nodes. f) Under SIP Information - Destination, enter an IP address or fully qualified domain name (FQDN) for each of your Hybrid Media Nodes. g) Enter 5060 for the Destination Port. h) For the SIP Trunk Security Profile, choose the Hybrid Media Trunk Security Profile that you created earlier. (For example, Hybrid Media Trunk Security Profile.) i) For the SIP Profile, choose the Hybrid Media SIP Profile that you created earlier. (For example, Hybrid Media SIP Profile.) j) Leave all other fields with their default values and save your changes. Note A Hybrid Media Service call or meeting might assign media to any node in a cluster, not just the node that terminates the SIP call. Step 4 Create a new SIP trunk to point to an Expressway. You can use a SIP trunk already in place for an existing Unified CM and Expressway deployment. If you create another one, and you also run Mobile Remote Access (MRA) with those Expressways, you can break MRA. a) From Cisco Unified CM Administration, choose Device > Trunk, and then click Add New. b) Choose SIP Trunk for the trunk type; leave the other values and click Next. c) Enter a meaningful name, such as Hybrid_Media_VCS_Trunk. 34

47 Deploy Hybrid Media Service Configure Unified CM SIP Traffic Routing for Hybrid Media d) For Calling and Connecting Party Info Format, check Deliver URI and DN in connected party, if available. This setting enables blended identity. It allows the SIP trunk to transmit the enterprise-side party's directory URI to Cisco Spark. e) Under SIP Information - Destination, enter an IP address or fully qualified domain name (FQDN) for each of your Expressways. For the Port, enter f) For SIP Profile, choose Standard SIP Profile For Cisco VCS. Step 5 Step 6 Step 7 Step 8 Step 9 Create a new route group for calls to Hybrid Media Nodes: a) From Cisco Unified CM Administration, choose Call Routing > Route/Hunt > Route Group, and then click Add New. b) Enter a meaningful name, such as Hybrid Media Node Route Group. c) Change the Distribution Algorithm to Top Down. d) In the Route Group Member Information section, Find the Devices with name Hybrid Media. e) Add the Hybrid_Media_SIP_Trunk by clicking Add to Route Group. f) Save your changes. For overflow to the cloud, create a new route group for calls to Expressway: a) From Cisco Unified CM Administration, choose Call Routing > Route/Hunt > Route Group, and then click Add New. b) Enter a meaningful name, such as Hybrid Media Expressway Route Group. c) Change the Distribution Algorithm to Top Down. d) In the Route Group Member Information section, Find the Devices with name Hybrid Media. e) Add the Hybrid_Media_VCS_Trunk by clicking Add to Route Group. f) Save your changes. Create a new route list for calls to Hybrid Media Nodes and Expressway: a) From Cisco Unified CM Administration, choose Call Routing > Route/Hunt > Route List, and then click Add New. b) Enter a meaningful name, such as Hybrid Media Node Route List. c) Set the Cisco Unified Communications Manager Group to Default, or another value depending on your configuration. d) Save your changes. e) In the Route List Member Information section, click Add Route Group, and then choose Hybrid Media Route Group. f) Leave the defaults for the other settings, and then save your changes. g) In the Route List Member Information section, click Add Route Group, and then choose Hybrid Media Expressway Route Group. h) Leave the defaults for the other settings, and then save your changes. Create a SIP route pattern for the WebEx site: a) From Call Routing > SIP Route Pattern, click Add New and enter the name Hybrid Media Route Pattern for WebEx. b) In the IPv4 pattern, enter the WebEx site for which you want optimized media For example, sitename.webex.com. c) For SIP Trunk/Route List, choose the Route List created for Hybrid Media For example, Hybrid Media Route List. d) Leave all other fields with their default values and save your changes. Create a SIP route pattern for Cisco Spark space meetings: 35

48 Configure Expressway SIP Traffic Routing for Hybrid Media Deploy Hybrid Media Service a) From Call Routing > SIP Route Pattern, click Add New, and then enter the name Hybrid Media Route Pattern for Spark. b) In the IPv4 pattern, enter the meet.ciscospark.com. c) For SIP Trunk/Route List, choose the Route List created for Hybrid Media For example, Hybrid Media Route List. d) Leave all other fields with their default values and save your changes. Configure Expressway SIP Traffic Routing for Hybrid Media Configure neighbor zones and search rules to route SIP dial-in and dial-out for Cisco WebEx meetings to Hybrid Media Nodes. SIP devices registered to an Expressway-C don't support direct reachability, so you must use Expressway configuration to establishes a relationship between on-premises SIP devices and your Hybrid Media Service clusters. You can also configure your deployment to handle failure or overflow conditions. This configuration helps if there's an outage or if the Hybrid Media clusters reached capacity. If the SIP meeting or call cannot be established with a cluster, the meeting or call will overflow to the cloud through the Expressway-C or an Expressway-C/E pair. Procedure Step 1 Create a zone that points to Hybrid Media Nodes: a) From Expressway-C, go to Configuration > Zones > Zones, and then click New. b) Configure the following fields: Field Name Value Name Type Enter a name that easily identifies the zone for example, SparkHybridMediaZone Neighbor H.323 Mode Off SIP Mode Port Transport On 5060 TCP Location 36

49 Deploy Hybrid Media Service Configure Expressway SIP Traffic Routing for Hybrid Media Field Name Peer [n] Address Value Enter any IP addresses for Hybrid Media Nodes. c) Leave the other fields with their default settings, and then save your changes. Step 2 Create a dial pattern for Hybrid Media Nodes: a) From Expressway-C, go to Configuration > Dial Plan > Search Rules, and then click New. b) Configure the following fields: Field Name Value Rule Name Priority Protocol Mode Pattern Type Pattern String Pattern Behavior On Successful Match Target Enter a rule name that easily identifies the search rule for example, example.webex.com-hmn 100 SIP Alias Pattern Match Regex.*@example.webex.com.* Leave Stop Choose the hybrid media zone that you created for example, SparkHybridMediaZone. c) Leave the other fields with their default settings, and then save your changes. Step 3 Create a zone that points to the cloud Expressway for failover: a) From Expressway-C or Expressway-E, go to Configuration > Zones > Zones, and then click New. b) Configure the following fields: Field Name Value Name Type Enter a name that easily identifies the zone for example, SparkHybridMediaFailoverZone Neighbor H.323 Mode Off 37

50 Configure Expressway SIP Traffic Routing for Hybrid Media Deploy Hybrid Media Service Field Name Value SIP Mode Port Transport On 5060 TCP Location Peer [n] Address Enter an IP address or hostname/fqdn for the cloud Expressway. c) Leave the other fields with their default settings, and then save your changes. Step 4 Create a dial pattern for the cloud Expressway: a) From Expressway-C, go to Configuration > Dial Plan > Search Rules, and then click New. b) Configure the following fields: Field Name Value Rule Name Priority Protocol Mode Pattern Type Pattern String Pattern Behavior On Successful Match Target Enter a rule name that easily identifies the search rule for example, example.webex.com-cloudfailover Enter a higher value than the rule for the local Hybrid Media Nodes. If the nodes are set to 100, set this value to 101. SIP Alias Pattern Match Regex.*@example.webex.com.* Leave Stop Choose the failover zone that you created for example, SparkHybridMediaFailoverZone Step 5 For SIP devices registered to the Expressway-C, open the device IP address in a browser, go to Setup, scroll to SIP, and choose Standards from the Type drop-down. 38

51 Deploy Hybrid Media Service Enable Hybrid Media Service for the WebEx Site Enable Hybrid Media Service for the WebEx Site Use this procedure to enable optimized media for Cisco WebEx Meeting Center Video meetings. Procedure Step 1 Step 2 From the customer view in go to Services, click the WebEx site from the WebEx meeting card, and then click Configure to access the the WebEx site configuration options. From Common Settings, click Cloud Collaboration Meeting Rooms (CMR), and then choose Hybrid for Media Resource Type. Assign Collaboration Meeting Rooms to Cisco Spark Users If you have an identity service site and manage your Cisco WebEx site through Cisco Spark Control Hub: a) From the customer view inhttps://admin.ciscospark.com, go to Users > Manage Users. To assign to users in bulk, see this document. b) Assign WebEx Collaboration Meeting Rooms to users in your organization. If you don't have an identity service site and manage your Cisco WebEx site through Site Admin: a) From Site Admin, go to User Management. b) Edit the user account and check Collaboration Meeting Room. To assign to users in bulk, see this document. 39

52 Assign Collaboration Meeting Rooms to Cisco Spark Users Deploy Hybrid Media Service 40

53 CHAPTER 4 Manage Hybrid Media Service View Hybrid Media Service Reports, page 41 Deregister Hybrid Media Node, page 45 Move Hybrid Media Node, page 45 Set Hybrid Media Cluster Upgrade Schedule, page 46 Delete Hybrid Media Cluster, page 46 Deactivate Hybrid Media Service, page 47 Manage Hybrid Media Node, page 47 View Hybrid Media Service Reports Hybrid Media Service reports are available on the Reports page of Cloud Collaboration Management, once Hybrid Media Service is active and has a cluster with at least one registered Hybrid Media Node. From the Overview page, select Reports from the menu on the left side of the screen and then, on the Reports page, click Hybrid Media Service on the upper-right side of the screen. Reports provide information about how you use your on-premises Hybrid Media Nodes and clusters in your Cisco Spark organization. With this information, you can more effectively manage your Hybrid Media resources by monitoring the capacity, utilization, and availability of your on-premises resources. You can use this information to make decisions about adding more Hybrid Media Nodes to a cluster or creating new clusters, for example. Data in the reports is collected in near real time. The Reports page is automatically refreshed often and the call activity shows up within 1 minute of availability. To help with troubleshooting, you can zoom in on data that appears on the graph and isolate to a specific time period. Available Reports Hybrid Media Service reports provide information through cards and graphs. The cards provide a snapshot of the critical metrics over a given period of time. The graphs provide a detailed trend of these metrics over 41

54 Available Reports Manage Hybrid Media Service the same period of time. You can view the information for all clusters of your organization or an individual cluster. Cards Adoption Total Number of Meetings Total number of meetings that are hosted on-premises and calls that overflowed to the Cisco Collaboration Cloud for the Cisco Spark organization. Resources Used for Meetings Summary of meetings based on where the organization s calls were hosted. On Premises Meeting and participants were hosted on the enterprise clusters. Cloud Meeting and participants were hosted on cloud clusters. Cloud and On-Premises Meeting and participants cascaded between enterprise and cloud clusters. Client Types Summary of common categories of meeting clients that are used in an organization. The categories include the following client types: Cisco Spark Desktop Windows, Mac OSX, web browser. Cisco Spark Mobile iphone, ipad, Android. Cisco Spark Devices Telepresence room device, Cisco Spark Board. SIP All SIP clients. Jabber All Jabber clients. Others Any unknown endpoints or clients that don't fit the other categories. Resources Total Calls (Resources) The sum total of participants that were on a meeting hosted on premises and participants that were hosted on the Cisco Collaboration Cloud (including overflowed to the cloud) for the Cisco Spark organization Cloud Calls Number of calls that did not use enterprise Hybrid Media Nodes, because of no connection to the enterprise network or being subject to enforced policy. Overflowed to Cloud Number of calls that were made within an enterprise but overflowed to a cloud cluster. On-Premises Number of calls that are hosted on any of the enterprise clusters. Overflowed to Cloud Data on overflowed calls in the last 24 hours: the percentage of overflow, whether there was an increase or decrease, and the number of calls that overflowed. Clusters in Service Percentage of clusters that can host calls in the organization. Graphs Adoption 42

55 Manage Hybrid Media Service Available Reports Client Type Distribution Provides usage trends of the various client types (for example, mobile, desktop, and other) that are used in your organization. Total Meetings by Resources Used Provides a trend of the number of meetings, based on where the meetings were hosted. Entire meetings hosted in the cloud Meetings hosted on-premises Meetings that are cascaded between on-premises and the cloud Resources Resource Utilization Average CPU utilization trend of all clusters in an organization (organization view) or a selected cluster compared to other clusters (cluster view). Call Activity Provides a view of the call activity trend across the organization, showing the calls that were hosted on-premises and calls hosted on the cloud. The calls that overflowed to the cloud are represented as dots (insight points) on the cloud call graph. Hover over a dot to show the number of calls that overflowed to the cloud at that instance. Call Distribution Across On-Premises Clusters Provides a view of call activity. This information helps you plan your organization's cluster capacity. Calls that cannot be hosted on this specific cluster are redirected to another on-premise cluster. These redirects are represented as dots on the graph. Hover over a dot to show the number of calls redirected from this specific cluster at that instance. Organization View Provides a view of how calls are distributed across the different on-premises clusters in the organization. This information helps you plan your organization's cluster capacity. Cluster View Provides a view of the call activity trend on a specific cluster. Clusters in Service (Org View) Below the overall availability card, you go to a specific cluster view by choosing one from the drop-down. Below the overall availability card, you go to a specific cluster view by choosing one from the drop-down. You can click on any of the clusters in the Cluster Availability graph to directly navigate to the Node Availability graph. Green clusters have all nodes in service. Yellow clusters have 1 or more nodes that are not in service. Red clusters have no nodes in service. Nodes in Service (Cluster View) Percentage of nodes that are in service to host calls over the selected time period Green nodes are in service. Red nodes are not in service. 43

56 Reporting Definitions Manage Hybrid Media Service Reporting Definitions The following terms are used in Hybrid Media Service reports: Participant: A person who initiates or receives a media (audio or audio and video) channel to participate in a meeting. Meeting: A group of 1 or more calls collaborating together. Hybrid Media Node: A basic media processing engine deployed on premises, which provides conferencing service. Hybrid Media Cluster: A collection of 1 or more Hybrid Media Nodes grouped together, usually based on geographic location. Organization: In this context, it refers a collection of all the clusters in your Cisco Spark organization. Filtering Reports The following filtering options are available in Hybrid Media Service reports: Cluster: At the upper-left side of the page, you can filter reports to display information for All Clusters or a specific cluster. Time: At the upper-right side of the page, you can filter the time range of the information. Available options are: Last 4 Hours Last 24 Hours Last Week Last Month Last Three Months Exporting Reports You can click the 3 dots ( ) at the upper-right corner of each Hybrid Media Service report to export the report in one of the following formats: Save As:.PNG or.jpg PDF Export:.CSV or.xlsx 44

57 Manage Hybrid Media Service Deregister Hybrid Media Node Deregister Hybrid Media Node Use this procedure to remove a Hybrid Media Node from the Cisco Colloboration Cloud. After completing this procedure, your node is removed from its cluster and is unavailable for use. After deregistering a node, the only way to make it available again is to reregister it. Procedure Step 1 Step 2 Step 3 From the customer view in go to Services, and then click Resources under Hybrid Media. From the list of resources, go to the cluster that contains the node you want to deregister, choose the node, and then click Action > Deregister Node. A message appears asking you to confirm that you want to delete the node. After you read and understand the message, click Deregister Node. Move Hybrid Media Node You may want to move a node from one cluster to another. For example, you may have a new cluster that you want to redistribute nodes to. Use this procedure to move a Hybrid Media Node. After completing this procedure, your node will only be available to the new resource. Procedure Step 1 Step 2 Step 3 Step 4 From the customer view in go to Services, and then choose Resources under Hybrid Media. From the list of clusters, go to the cluster that contains the node that you want to move, click the node and then click Perform actions on this Node. From the Actions drop-down, click Move Node. Choose one: Create a new cluster by entering a name. Choose an existing cluster. Step 5 Click Move Node. Your node is moved to the new cluster. Related Topics Move a Node in to Maintenance Mode 45

58 Set Hybrid Media Cluster Upgrade Schedule Manage Hybrid Media Service Set Hybrid Media Cluster Upgrade Schedule You can set a specific upgrade schedule or use the default schedule of 3:00 AM Daily United States: America/Los Angeles. You can also choose to postpone an upcoming upgrade, if necessary. Software upgrades for Hybrid Media Service are done automatically at the resource level, which ensures that all nodes are always running the same software version. Upgrades are done according to the upgrade schedule for the resource. When a software upgrade becomes available, you have can manually upgrade the cluster before the scheduled upgrade time. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 From the customer view in go to Services, and then click Resources under Hybrid Media. Go to a media resource, scroll to Cluster Settings, and then choose the resource name. On the Settings page, scroll to Upgrade, and then choose the time and time zone for the upgrade schedule. Note Upgrades may take longer than a few minutes if the Hybrid Media Node is waiting for active calls to end before the upgrade begins. For a more immediate upgrade process, we recommend that you schedule the automatic upgrade window outside of your regular business hours. (Optional) If needed, click Postpone to postpone the upgrade to the following day. Under the time zone, the next available upgrade date and time is displayed. (Optional) Choose a release channel, which allows you to select the type of software version to which you want to upgrade: Stable Provides the current release software version (this is the default and usually the best choice for most customers) Beta (if enabled by Cisco) Provides an upcoming software version (this is for customers who want to try out upcoming features and are willing to accept there may be known issues or defects) Delete Hybrid Media Cluster You can permanently delete a Hybrid Media cluster from the Cisco Collaboration Cloud. To complete this procedure, you must either move each node to a different cluster or deregister all the nodes. Deregistering all nodes in a cluster permanently removes them and makes them unavailable for use. The only way to make deregistered nodes available again is to reregister them. Procedure Step 1 Step 2 From the customer view in go to Services, and then click All Resources. From the list of resources, scroll to the Hybrid Media resource that you want to delete, and then click Edit Cluster Settings. Tip You can click Media to filter on just Hybrid Media resources. 46

59 Manage Hybrid Media Service Deactivate Hybrid Media Service Step 3 Click Delete Cluster, and then choose one: Click Move All Nodes. For each node, either create a new resource by entering a name or choose an existing resource from the drop-down list, and then click Continue. Click Deregister All Nodes, check the check box, and then click Delete Cluster. Deactivate Hybrid Media Service Deactivating your Hybrid Media Service removes the ability to have media remain on-premises for your meetings. Also, all in-progress meetings using Hybrid Media Nodes end and future meetings are hosted in the cloud. Once deactivated, the only way to use Hybrid Media Service is to deploy it from the beginning. Before you deactivate Hybrid Media Service, you will deregister all Hybrid Media Nodes. Procedure Step 1 Step 2 Step 3 From the customer view in go to Services, choose Settings under Hybrid Media, and then click Deactivate. Review the list of clusters, read the disclaimer, check the check box to confirm that you understand this action, and then click Deactivate When you are ready to deactivate your Hybrid Media Service, click Deactivate Service. All the Hybrid Media Nodes and clusters are removed and Hybrid Media Service is no longer configured. Manage Hybrid Media Node Change Hybrid Media Node Network Settings If your network topology changes, you have to open each Hybrid Media Node and change the network settings. You may see a caution about changing the network settings, but you can still save the changes in case you're making changes to your network after changing Hybrid Media Node settings. Procedure Step 1 Step 2 Step 3 From the main menu of the Hybrid Media Node console, choose option 2 Edit Configuration and then click Select. Read the prompt that the calls will end on this Hybrid Media Node, and then click Yes. Click Static, enter the IP address, Mask, Gateway, and DNS values for your network. 47

60 Change the Administrator Passphrase of the Hybrid Media Node Manage Hybrid Media Service Your Hybrid Media Node must have an internal IP address and resolvable DNS name. The node IP address must not belong to the IP address range reserved for Hybrid Media Node internal use. The default reserved IP address range is , which can be configured in the Diagnostic menu. Deploy all the devices on the same subnet or VLAN, so that all devices in a cluster are reachable from wherever the clients reside in your network. Step 4 Step 5 (Optional) Change the hostname, domain, or NTP server(s), if required. Note To ensure a successful registration to the cloud, use only lowercase characters in the hostname that you set for the Hybrid Media Node. Capitalization is not supported at this time. When using hostname, you must also enter a valid and resolvable domain. The total length of the FQDN must not exceed 64 characters. Click Save, and then click Save Changes & Reboot. During the save, DNS validation is performed if you provided a domain. A warning is displayed if the FQDN (hostname and domain) is not resolvable using the DNS server addresses provided. You may choose to save by ignoring the warning but calls will not work until the FQDN can resolve to the DNS configured on the node. After your Hybrid Media Node reboots, the network configuration changes take effect. Change the Administrator Passphrase of the Hybrid Media Node Use this procedure to change the administrator passphrase (password) for your Hybrid Media Node. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Open and log in to the VMware ESXi console of the VM for your Hybrid Media Node. In the main menu, choose option 3 Manage Administrator Passphrase, then 1 Change Administrator Passphrase, and then click Enter. Read the information on the password expired page, click Enter, and then click it again after the password expiry message. Press Enter. After you're signed out of the console, go back to the sign in screen, and then sign in using the admin login and passphrase (password) that you expired. You are prompted to change your password. For Old password, enter the current passphrase, and then press Enter. For New password, enter a new passphrase, and then press Enter. For Re-enter new password, retype the new passphrase, and then press Enter. A "password changed" message appears and then you go back to the sign in screen. Sign in using your new admin login and passphrase (password). 48

61 Manage Hybrid Media Service Manage Hybrid Media Node Password Expiry Manage Hybrid Media Node Password Expiry You can view information about the Hybrid Media Node passphrase (password) and expiry policy. You can also modify the numbers of days before a password expires. Procedure Step 1 Step 2 Open and log in to the VMware ESXi console of the VM for your Hybrid Media Node. In the main menu, choose option 3 Manage Administrator Passphrase, then 2 Manage Passphrase Expiry, and then click Enter. Last Passphrase Change Shows the date when the password was last changed for the Hybrid Media Node. Passphrase Expires Shows the date when the password expires for the Hybrid Media Node. Expiry Interval (Days) Sets the lifespan of the password. Enter a different value if you want to change how long a password lasts before it expires, and then click Save. Run a Ping from Hybrid Media Node You can run a ping from the Hybrid Media Node. This step tests a destination you enter and sees if the Hybrid Media Node can reach it. Procedure Step 1 Step 2 From the Hybrid Media Node console, go to 4 Diagnostics, and then choose Ping. In the ping field, enter a destination address that you want to test, such as an IP address or hostname, and then click OK. The test runs and you'll see a ping success or failure message. If you receive a failure, check the destination value that you entered and your network settings. Enable Debug User Account If support requires access to the Hybrid Media Node, you can temporarily enable a debug user account so that support can run further troubleshooting. 49

62 Send Logs from Hybrid Media Node Manage Hybrid Media Service Procedure Step 1 Step 2 Step 3 Step 4 From the Hybrid Media Node console, go to 4 Diagnostics, choose 2 Enable Debug User Account, and after the prompt, click Yes. After a message appears that the debug user account was created successfully, click OK to show the encrypted passphrase. You'll send the encrypted passphrase to support. They use this temporary account and decrypted passphrase to securely access your Hybrid Media Node for troubleshooting. This account expires after 3 days, or you can disable it when support is finished. Select the start and end of the encrypted data, and copy-paste it into the support ticket or that you're sending to support. After you send this information to support, return to the Hybrid Media Node console and press any key to go back to the main menu. What to Do Next When support indicates that they finished troubleshooting on the node, you can return the Hybrid Media Node console, go to 4 Diagnostics, and then choose 3 Disable Debug User Account to disable the account before it expires. Send Logs from Hybrid Media Node You may be instructed to send logs directly to Cisco or to a supported FTP server. Use this procedure to send logs directly from any Hybrid Media Nodes that you registered to the cloud. Procedure Step 1 Step 2 Step 3 Step 4 Open and log in to the VMware ESXi console of the VM for your Hybrid Media Node. In the main menu, click option 4 Diagnostics and then press Enter. Click 4 Export Log Files, provide feedback if you want, and then click Next. Choose an option: Send Logs to FTP Server, and then enter the details of the FTP server. Send Logs to Cisco, and then confirm the export of the logs. Step 5 Step 6 Choose OK to return to the Hybrid Media Node main menu. (Optional) Choose 5 Check Status of Log Files Sent to Cisco if you sent the logs to Cisco. What to Do Next After you send logs, we recommend that you send feedback directly from the Cisco Spark app so that your support contacts have all the information that they need to help you. 50

63 Manage Hybrid Media Service Check Health of Hybrid Media Node Related Topics Send Feedback in the Cisco Spark App Check Health of Hybrid Media Node You can view the node health directly from the Hybrid Media Node itself. The results are informational, but could aid in troubleshooting steps for example, if NTP synchronization is not working, you can check the NTP server value in the network settings. Procedure From the Hybrid Media Node console, go to 4 Diagnostics, and then choose 6 Check Node Health to view the following information about the node: Management Service Container ETCD (key value store that reliably stores data across a cluster) NTP Synchronized Disk Space (Free/Used%) Memory (Free/Used%) Configure Container Network on Hybrid Media Node Hybrid Media Node reserves a subnet range for internal use within the node. The default range is The nodes do not respond to any external-to-hybrid Media Node traffic originating from this range. You may want to change the container bridge IP address to avoid conflicts with other devices in your network. Procedure Step 1 Step 2 Step 3 From the main menu of the Hybrid Media Node console, go to 4 Diagnostics, and then choose 7 Configure Container Network. After the caution that states that active calls will end on the node, click Yes. Change the values for Container Bridge IP and Network Mask, as needed, and then click Save. You'll see a screen that shows the container network information, including the IP address range reserved for internal operations on the Hybrid Media Node. Click OK. 51

64 Factory Reset a Hybrid Media Node Manage Hybrid Media Service Factory Reset a Hybrid Media Node As part of deregistration cleanup, you can factory reset the Hybrid Media Node. This step removes any configuration you put in place while the node was active, but does not remove the virtual machine entry. Later, you may want to reregister this node as part of a cluster from scratch. Before You Begin You must deregister the Hybrid Media Node from the cluster that's registered in the Cisco Spark Control Hub. Procedure Step 1 Step 2 From the Hybrid Media Node console, go to 4 Diagnostics, and then choose 8 Factory Reset. Ensure that you understand the information in the note that appears, and then click Reset. The node reboots automatically after the factory reset. 52

65 CHAPTER 5 Troubleshoot Hybrid Media Service Troubleshoot the Hybrid Media Node Registration, page 53 Troubleshoot the Hybrid Media Node Registration This section contains possible errors you may encounter during registration of your Hybrid Media Node to the Cisco Collaboration Cloud and suggested steps to correct them. The domain could not be resolved. Possible Cause This message appears if the DNS settings configured on your Hybrid Media Node are not correct. Solution Sign in to the console of your Hybrid Media Node and make sure the DNS settings are correct. Could not connect to site using port 443 via SSL Possible Cause This message appears if your Hybrid Media Node cannot connect to the Cisco Collaboration Cloud. Solution Make sure your network allows connectivity on the ports required for Hybrid Media Service. For details, see Ports and Protocols Used by Hybrid Media Service, on page

66 Troubleshoot the Hybrid Media Node Registration Troubleshoot Hybrid Media Service 54

67 APPENDIX A Feature Comparison and Migration Path from Collaboration Meeting Room Hybrid to Hybrid Media Service Feature Comparison To help you understand the benefits of migrating from CMR Hybrid to Hybrid Media Service, this table shows a side-by-side comparison of the key features in each offer. Along with new features detailed below for Hybrid Media Service, the existing WebEx functionality will remain the same when combined with Hybrid Media Service. In addition to meeting enhancements, Hybrid Media Service lets you benefit from the agility of cloud-based management and continue to protect your existing investment. Feature Meeting Types Hybrid Media Service and Cisco WebEx Meeting Center Video Scheduled One Click (Instant) Personal Meeting (PMR) Consistent experience for premises and cloud-based meetings CMR Hybrid Scheduled only Scheduling Meeting Join Options WebEx Productivity Tool (Windows and Mac) Hybrid Calendar scheduling WebEx Portal Dial-in and Dial-out PIN Protected (Host) One Button To Push (OBTP) WebEx-enabled TelePresence Windows and Mac Productivity Tools TMS Scheduling Dial-in only OBTP 55

68 Feature Comparison and Migration Path from Collaboration Meeting Room Hybrid to Hybrid Media Service Feature In-Meeting Experience Capacity and Deployment Model Hybrid Media Service and Cisco WebEx Meeting Center Video Unified Roster (WebEx Client) Unified Controls (WebEx Client) Lock/Unlock meeting Mute/Unmute TelePresence participants Unlimited capacity On-premises and automatic overflow Switching and transcoding CMR Hybrid No Unified Roster (WebEx Client and TelePresence Server) Separate Controls (WebEx Client and TelePresence Server) Transcoding capacity limited to the TelePresence Server Migration Path Checklist Below is a high-level overview of how to migrate an existing site to Cisco WebEx Meeting Center Video and prepare the site to integrate with Hybrid Media Service. The steps may vary, depending on your existing environment. Work with your partner, customer success manager, or trials representative to ensure a smooth migration. 1 Make sure that the Meeting Center Video conferencing feature is provisioned on the WebEx site. 2 The site admin receives their management portal account. The admin then deploys Hybrid Media Nodes for the Cisco Spark organization. 3 The site admin assigns the CMR privilege to enable all or some CMR Hybrid users with Cisco WebEx Meeting Center Video. 4 (Optional) Disable the CMR Hybrid session type for this subset, and then enable Cisco WebEx Meeting Center Video in their user profile. 5 The site admin sets up Hybrid Media Service, and then selects Hybrid as the media resource type under Cloud Collaboration Meeting Room Options. 6 The site admin sets up on-premises TelePresence Management Suite (TMS) and One Button to Push (OBTP) to work with Cisco WebEx Meeting Center Video. See the Cisco WebEx Meeting Center Video Conferencing Enterprise Deployment Guide for guidance. 7 When the CMR privilege is enabled for a user, the WebEx Productivity Tools default to the Cisco WebEx Meeting Center Video version. All new meetings scheduled by the users are Cisco WebEx Meeting Center Video meetings. 8 If conference rooms are included in the invite, OBTP information is pushed to the conference room through TMS (for CMR Hybrid meetings only). 9 Existing meetings that were set up by CMR Hybrid users before they were switched to Cisco WebEx Meeting Center Video should continue to work as long as the customer preserves the on-premises MCU and TMS settings. 10 Existing CMR Hybrid meetings cannot be modified or updated to reflect the Cisco WebEx Meeting Center Video meeting information. If users want to use new invitation, they must delete the old meetings and create new meetings. 56

69 Feature Comparison and Migration Path from Collaboration Meeting Room Hybrid to Hybrid Media Service 11 If the customer wishes to retire the on-premises MCU, TMS, old CMR Hybrid meetings will not work. New meetings with Cisco WebEx Meeting Center Video information must be created. 57

70 Feature Comparison and Migration Path from Collaboration Meeting Room Hybrid to Hybrid Media Service 58

71 APPENDIX B TelePresence Interoperability Protocol and Segment Switching Hybrid Media Service supports negotiating TelePresence Interoperability Protocol (TIP) and multiplex (MUX) for both 1-screen and 3-screen IX and TX endpoints. For three-screen endpoints, all three screens should show video, if there are enough participants in the conference. Another three-screen system in the conference results in segment switching instead of room switching. This means that rather than all three screens becoming large when someone in another three-screen system speaks, only the active pane becomes large. The other two panes are populated by video from other systems. When shown small, all three panes are rendered together (for all devices, one or three screens) with a single bounding box and name label. Depending on the hosting resources in the cloud, some endpoints will show all three screens of a three-screen room in the film strip, while others will only show one pane. The Cisco Spark app shows just 1 pane, even if the media is on-premises. For large meetings that overflow from one node and cascade to a second, the same is seen by any endpoints hosted on a different node to the one hosting the three-screen system (only one pane visible in the layout). Presentation sharing requires BFCP to be negotiated through the call path. 59