Cisco 500-710 - Video Infrastructure Implementation (VII)

Cisco Spark hybrid call service integrates Cisco Spark with an existing Cisco call-control platform, such as Cisco Unified Communications Manager, Cisco Business Edition 6000/7000, or Cisco Hosted Collaboration Solution. This integration enables users to make and receive calls on their Cisco device or Spark application using the same dialing procedure as with on-premises registered endpoints. For example, users can dial extension numbers, PSTN numbers, or URIs from their Cisco device or Spark application and reach any destination that is reachable from their on-premises call-control platform.

Cisco Spark hybrid call service has two service components, called Call Service Aware and Call Service Connect1. Call Service Aware makes Cisco Spark aware of calls within your existing Cisco call control. It enables features such as call history, missed call notifications, and one-button-to-push join for meetings on Cisco Spark. Call Service Connect enables calls between Cisco Spark and your existing call control so that, to users they appear as one system. It allows users to make and receive calls on their Cisco device or Spark application using their enterprise directory number, regardless of their location or network. It also enables features such as single number reach, shared line appearance, and call transfer and forwarding.

Therefore, the correct answer is Call Service Connect, as it is the Cisco Spark hybrid call service component that integrates Cisco Spark with an existing Cisco call-control platform and makes it possible for users to make and receive calls on their Cisco device or Spark application using the same dialing procedure as with on-premises registered endpoints.

References := Cisco Spark Hybrid Services Data Sheet, The best of both worlds – Cisco Spark Hybrid Services

 = To enter system license keys in the TMS application, an engineer needs to follow these steps:

Log into TMS with Site Administrator privileges via the portal web page.

Go to Administrative Tools > Configuration > General Settings.

Enter the release key in the field labeled TMS Release Key and click the Save button.

Click the Add Option Key button to enter any option keys for additional features.

Verify that the keys are valid and activated in the License Information section. References := https://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/tms/license_info/78-19878-01_Cisco_TMS_licenses_keys.pdf https://community.cisco.com/t5/audio-and-video-endpoints/tms-api-licenses/td-p/3596708

 The role of the conference alias in the Cisco Conductor is to be dialed by a user and Conductor uses that alias to determine the conference template. This is because the conference alias is a unique identifier for a conference that is configured on the Conductor. The conference alias can be a SIP URI, an H.323 ID, or an E.164 number. When a user dials the conference alias, the Conductor matches the alias to a conference template, which defines the settings and parameters for the conference, such as the bridge pool, the media resources, the layout, the encryption, and so on1.

The other options are not correct because:

It determines the bridge pool to be selected for a conference: This is not true, as the bridge pool is determined by the conference template, not the conference alias. The bridge pool is a group of conference bridges that can host the conference. The conference template specifies which bridge pool to use for a conference, based on the priority, availability, and load balancing of the bridges2.

The conference template determines the bridge pool to be selected for a conference: This is true, but it does not describe the role of the conference alias, which is the question. The conference template determines the bridge pool, but the conference alias determines the conference template1.

It selects the Expressway to used for media traversal: This is not true, as the Expressway is not involved in the selection of the conference alias or the conference template. The Expressway is a network device that provides firewall traversal, NAT, and encryption services for video communications. The Expressway does not have the capability to select or configure conferences or conference aliases3.

References := 1: Cisco TelePresence Conductor with Cisco Unified Communications Manager Deployment Guide (XC4.0) - Configuring Conference Aliases [Cisco TelePresence Conductor] - Cisco 2: Cisco TelePresence Conductor with Cisco Unified Communications Manager Deployment Guide (XC4.0) - Configuring Conference Templates [Cisco TelePresence Conductor] - Cisco 3: Cisco Expressway Basic Configuration Deployment Guide (X12.6) - Introduction [Cisco Expressway Series] - Cisco

= To match any incoming call to the Expressway that is searching for an E.164 address of only 6 digits and append the domain cisco.com to the end, you need to use a pattern match and a replace string using regular expressions. Regular expressions are a way of describing patterns of text using special characters and symbols1. The Expressway supports the use of regular expressions in several features, such as search rules, transforms, and dial plan2.

A pattern match is a regular expression that defines the criteria for matching the incoming call. A replace string is a regular expression that defines how to modify the matched call and add the desired domain. The Expressway uses the following syntax for pattern match and replace string2:

The pattern match is enclosed in parentheses, such as (pattern).

The replace string is preceded by a colon, such as :replace.

The replace string can use backreferences to refer to the matched groups in the pattern match, such as \1, \2, etc.

For example, the pattern match and replace string (pattern):replace means that the Expressway will match the incoming call with the pattern and replace it with the replace string.

In this question, the pattern match should match an E.164 address of only 6 digits. An E.164 address is a global phone number that can have up to 15 digits, starting with a plus sign (+)3. To match only 6 digits, we can use the following regular expression:

({6}\d) : This means that the Expressway will match any 6 consecutive digits (\d) and capture them as a group ({6}). The curly braces indicate the number of repetitions of the preceding character. The parentheses indicate the grouping of the characters.

The replace string should append the domain cisco.com to the end of the matched E.164 address. To do this, we can use the following regular expression:

:\1@cisco.com : This means that the Expressway will replace the matched E.164 address with the first captured group (\1) followed by an at sign (@) and the domain cisco.com.

Therefore, the correct pattern match and replace string using regular expressions are:

pattern match: ({6}\d)

replace string: \1@cisco.com

The other options are incorrect because:

A. pattern match: ({6}) : This means that the Expressway will match any 6 consecutive characters () and capture them as a group. The asterisk means that the preceding character can be repeated zero or more times. This is too broad and can match non-digit characters as well.

C. pattern match: ({5}\d) : This means that the Expressway will match any 5 consecutive digits (\d) and capture them as a group. This is too short and will not match an E.164 address of 6 digits.

D. replace string: \6@cisco.com : This means that the Expressway will replace the matched E.164 address with the sixth captured group (\6) followed by an at sign (@) and the domain cisco.com. This is incorrect because there is only one captured group in the pattern match, so \6 will not refer to anything.

F. replace string: $@cisco.com : This means that the Expressway will replace the matched E.164 address with a dollar sign ($) followed by an at sign (@) and the domain cisco.com. This is incorrect because the dollar sign is a special character in regular expressions that means the end of the string. To use it literally, it needs to be escaped with a backslash ().

References := Regular Expressions, Cisco Expressway Basic Configuration Deployment Guide, E.164 : The international public telecommunication numbering plan

The Cisco TelePresence Management Suite (TMS) is a software application that provides scheduling, management, and monitoring of video conferencing resources1.

The TMS Conference Control Center (CCC) is a web-based interface that allows administrators and schedulers to view and control the active and completed conferences on the TMS2.

The CCC requires Java to be installed and enabled on the web browser of the user who accesses it3. Java is a programming language and platform that allows web applications to run on different devices and browsers4.

If the CCC is not displaying the interface on a scheduler’s computer, but it operates properly on the administrator’s computer, the most likely cause is that Java must be properly updated and configured on the scheduler’s computer. This means that the scheduler’s computer either does not have Java installed, has an outdated or incompatible version of Java, or has Java disabled or blocked by the browser settings or security software35.

To fix this issue, the scheduler should follow these steps35:

Check if Java is installed on the computer by visiting [this website].

If Java is not installed, download and install the latest version of Java from [this website].

If Java is installed, check if it is up to date by visiting [this website].

If Java is not up to date, download and install the latest version of Java from [this website].

Check if Java is enabled and allowed on the web browser by following the instructions for the specific browser from [this website].

Check if Java is blocked by any firewall, antivirus, or security software on the computer and adjust the settings to allow Java to run.

Restart the web browser and try to access the CCC again.

The other options are incorrect because:

NET or IS are not related to the CCC or Java. NET is a framework for developing and running applications on Windows. IS is a common abbreviation for information systems, which are the combination of hardware, software, data, and people that support organizational goals.

The server domain of the scheduler’s computer is not relevant to the CCC or Java. The server domain is the name of the network that the computer belongs to, such as example.com. Theserver domain does not affect the display of the CCC, as long as the computer can access the TMS web server through the network.

The network has a port blockage is unlikely to be the cause of the CCC not displaying the interface, because the CCC uses the same port as the TMS web server, which is port 80 by default. If the network had a port blockage, the scheduler would not be able to access the TMS web server at all, not just the CCC.

References := 1: Cisco TelePresence Management Suite - Overview 2: Cisco TelePresence Management Suite Administrator Guide (14.4) 3: Cisco TelePresence Management Suite Administrator Guide (14.4) 4: What is Java and why do I need it? 5: Why are Java applications blocked by your security settings with the latest Java? : [Do I have Java?] : [Download Java] : [Verify Java Version] : [How do I enable Java in my web browser?] : What is .NET? : What is Information Systems? : What is a Domain Name Server (DNS) and How Does it Work? : Cisco TelePresence Management Suite Installation and Upgrade Guide (14.4)

The TMS Systems > Navigator menu selection is a feature of the Cisco TelePresence Management Suite (TMS) that allows users to view and manage the video conferencing systems that are registered to TMS1.

The TMS Systems > Navigator menu selection is not visible on a scheduler’s computer if the scheduler does not have adequate permissions associated to their log in credentials. This is themost likely cause because TMS uses a role-based access control system that defines different levels of permissions for different types of users2.

The scheduler must have the System Navigator permission enabled in their user account settings to be able to see and use the TMS Systems > Navigator menu selection2. The administrator can grant or revoke this permission by editing the user account in TMS > Administrative Tools > User Administration2.

The other causes are less likely because they are not related to the visibility of the TMS Systems > Navigator menu selection. They may affect the connectivity or functionality of TMS, but not the user interface34.

The scheduler’s computer has a port blockage: This may prevent the scheduler from accessing TMS or communicating with the video conferencing systems, but it does not affect the display of the TMS Systems > Navigator menu selection.

NET or US is not set up on the scheduler’s computer: NET and US are optional components of TMS that provide network and user synchronization features, respectively5. They are not required for the scheduler to see or use the TMS Systems > Navigator menu selection.

The network has a port blockage: This may prevent TMS from communicating with the video conferencing systems or other TMS servers, but it does not affect the display of the TMS Systems > Navigator menu selection.

References := 1: Cisco TelePresence Management Suite Administrator Guide (15.13) - Navigator 2: Cisco TelePresence Management Suite Administrator Guide (15.13) - User Administration 3: Cisco TelePresence Management Suite Administrator Guide (15.13) - Required Ports for Cisco TMS Communication 4: Cisco TelePresence Management Suite Administrator Guide (15.13) - Troubleshooting 5: Cisco TelePresence Management Suite Administrator Guide (15.13) - Network and User Synchronization

Cisco WebEx is a cloud-based collaboration platform that offers various products and services for online meetings, webinars, training, and support1.

Cisco WebEx products have different capacities and features depending on the type and purpose of the online event2.

the only Cisco WebEx product that can support up to 3000 attendees is the Cisco WebEx Event Center345. The Cisco WebEx Event Center is designed for large-scale webinars and online events that require registration, presentation, Q&A, polling, and recording2.

The other options are incorrect because:

Cisco WebEx Meeting Center is the core product for online meetings and video conferencing that supports up to 1000 participants2.

Cisco WebEx Training Center is a product for online training and education that supports up to 1000 participants and offers breakout sessions, testing, and grading2.

Cisco WebEx Support Center is a product for remote technical support and customer service that supports up to 5 participants and offers chat, file transfer, and remote control2.

References := 1: Cisco WebEx - Overview 2: Support for Webex Meetings 3: Webex Events (new) is now Webex Webinars 4: Compare Webex Webinars and Webex Events (classic) 5: Maximum attendee size for Training or Meeting events?

CMR Cloud stands for Collaboration Meeting Rooms Cloud, which is a video conferencing service that combines WebEx Meeting Center with WebEx Video Bridge into one, always-available meeting experience1.

To schedule a CMR Cloud meeting, the following products can be used23:

Microsoft Exchange with WebEx Integration: This option allows users to schedule CMR Cloud meetings directly from Microsoft Outlook for Windows or Mac, using the WebEx Productivity Tools plug-in. Users can also add external video and audio dial-in participants, and use their Personal Room as the meeting location23.

TMS Smart Scheduler: This option allows users to schedule CMR Cloud meetings from the Cisco TelePresence Management Suite (TMS) web interface, using the Smart Scheduler feature. Users can also add video endpoints, audio participants, and WebEx users to the meeting, and use their Personal Room or a conference alias as the meeting location23.

The other products are not valid options for scheduling a CMR Cloud meeting, because23:

Microsoft Exchange with WebEx Scheduler App: This option allows users to schedule WebEx meetings from Microsoft Outlook Web App, but not CMR Cloud meetings.

WebEx Scheduler App: This option allows users to schedule WebEx meetings from a mobile device, but not CMR Cloud meetings.

Microsoft Exchange with WebEx TMSXE Integration: This option allows users to schedule CMR Hybrid meetings from Microsoft Outlook, but not CMR Cloud meetings. CMR Hybrid is a different service that combines WebEx Meeting Center with on-premises TelePresence Server and Conductor4.

References := 1: Cisco Collaboration Meeting Rooms (CMR) Cloud 2: Cisco Collaboration Meeting Rooms (CMR) Cloud Quick Reference Guide 3: Cisco Collaboration Meeting Rooms (CMR) Cloud Configuration Guide (TMS 15.0) 4: Cisco Collaboration Meeting Rooms (CMR) Hybrid Configuration Guide (TMS 15.0)