Cisco 500-710 - Video Infrastructure Implementation (VII)

To build a TMS phone book, an engineer needs to follow these steps:

Create a source: A source is a collection of contacts that can be imported from various sources, such as Cisco TMS endpoints, manual lists, Active Directory, H.350 directories, file-based phone books, gatekeepers, or other TMS phone books. A source can be created by going to Phone Books > Manage Phone Book Sources and clicking on New12.

Create a phone book: A phone book is a logical grouping of contacts that can be assigned to one or more systems. A phone book can be created by going to Phone Books > Manage Phone Books and clicking on New12.

Connect the source to the phone book: A source can be connected to a phone book by selecting the phone book and clicking on Connect. Then, the engineer can choose the source from the list and click on OK12.

Set the phone book on systems: A phone book can be set on systems by selecting the phone book and clicking on Set on Systems. Then, the engineer can choose the systems from the list and click on OK12. References :=https://www.cisco.com/c/en/us/support/docs/conferencing/telepresence-management-suite-tms/215223-tms-phone-books-troubleshoot-guide.html

https://www.cisco.com/c/en/us/support/docs/conferencing/telepresence-management-suite-tms/211266-How-to-Create-a-File-Based-Phonebook-in.html

The Cisco TelePresence Conductor is a conference resource manager that orchestrates and allocates conference bridges and media resources for scheduled and ad hoc conferences1.

To collect information on system activity, including TCP dumps, of the Conductor over a period of time, an engineer can use the diagnostic logging feature of the Conductor2. Diagnostic logging allows the engineer to capture detailed logs and network traces for troubleshooting and analysis2.

To enable diagnostic logging, the engineer can go to the web interface of the Conductor and navigate to Maintenance > Diagnostics > Diagnostic Logging2. The engineer can then select the components and levels of logging, the duration and frequency of logging, and the destination of the log files2.

The other options are incorrect because:

Status log is a feature of the Conductor that shows the current status of the system, such as the CPU and memory usage, the software version, the license information, and the network configuration3. It does not provide historical or detailed information on system activity or TCP dumps.

Network log is a feature of the Conductor that shows the network events and errors that occurred on the system, such as SIP messages, DNS queries, and NTP synchronization. It does not provide TCP dumps or allow the engineer to specify the components and levels of logging.

CDR records are call detail records that show the information about the calls that were made or received through the Conductor, such as the call ID, the conference name, the participants, the duration, and the quality. They do not provide information on system activity or TCP dumps.

References := 1: Cisco TelePresence Conductor Product Overview 2: Cisco TelePresence Conductor Administrator Guide (XC4.3) 3: Cisco TelePresence Conductor Web Interface Reference Guide (XC4.3) : Cisco TelePresence Conductor Network Log Messages (XC4.3) : Cisco TelePresence Conductor CDR Data Dictionary (XC4.3)

 An alias is a name or address that identifies an endpoint or a conference on the Expressway. An alias can be changed by a rule into another form at two stages within the call processing order: as a pre-search transform and as a zone transform. A pre-search transform is applied to the alias before any Call Policy, User Policy, or search rules are applied. A zone transform is applied to the alias after the search rules have matched a destination zone for the call. Both types oftransforms can modify the alias by removing or replacing its prefix, suffix, or the entire string, and by the use of regular expressions. The other options are not valid stages for changing an alias by a rule. References: Cisco Expressway Administrator Guide (X14.0) - Dial Plan and Call Processing, Cisco Expressway Basic Configuration Deployment Guide (X14.0) - Configuring Transforms

 The Cisco Meeting Server (CMS) supports H.323-to-SIP interworking, which means it can receive and send H.323 calls and convert them to SIP calls. The CMS does not support H.323 registration or call control, as it is a SIP-based solution. The CMS uses the Cisco Expressway as the edge device to handle H.323 calls from external networks. The CMS also has an optional H.323 gateway component that can be enabled on the same server or on a separate server, but this component is not supported from version 3.0 of the CMS software and has been removed. The H.323 gateway component allows the CMS to receive H.323 calls directly without the need for a gatekeeper or a Cisco Expressway. However, the H.323 gateway component does not provide call control or routing functionality, and it is recommended to use a gatekeeper or a Cisco Expressway for those purposes. References: Cisco Meeting Server 3.1, Single Combined Server Deployment Guide, Should I continue to deploy the H.323 component of Cisco Meeting Server …, Cisco Meeting Server: Enabling H.323 Calls - Fatih Erikci

The two methods that can be used in TMS to schedule conferences are Booking > New Conference and Scheduling > New Conference. These are the two main ways to create a conference in TMS, either by using the Booking menu or the Scheduling menu. Both methods allow the user to select the participants, the time, the recurrence, the dialing direction, the conference type, and the advanced settings for the conference. The difference between the two methods is that the Booking menu provides a more graphical interface with a calendar view and a drag-and-drop feature, while the Scheduling menu provides a more tabular interface with a list view and a search feature. Both methods have the same functionality and result in the same conference being created in TMS. References: Cisco TelePresence Management Suite Booking API Programmer Guide, Cisco TelePresence Management Suite User Guide

Cisco Spark is a cloud-based collaboration platform that offers messaging, calling, meeting, and video conferencing capabilities. There are two main deployment models for Cisco Spark implementation: Spark Cloud and Spark Hybrid.

Spark Cloud is the default deployment model, where all the services and features are provided by the Cisco Spark cloud. The users can access the Cisco Spark app on their devices (such as desktops, laptops, tablets, or smartphones) and communicate with other users or join meetings hosted on the cloud. The users can also use Cisco Spark-registered devices, such as IP phones, video endpoints, or room systems, to access the cloud services. The Spark Cloud deployment model is suitable for organizations that want a simple, scalable, and secure cloud solution without the need for any on-premises infrastructure or integration.

Spark Hybrid is an optional deployment model, where some of the services and features are provided by the Cisco Spark cloud, while others are provided by the existing on-premises infrastructure, such as Cisco Unified Communications Manager (CUCM), Cisco Expressway, or Cisco TelePresence Server. The Spark Hybrid deployment model allows the organizations to leverage their existing investments and integrate the Cisco Spark cloud with their on-premises systems. The Spark Hybrid deployment model offers several hybrid services, such as hybrid call service, hybrid calendar service, hybrid directory service, hybrid media service, and hybrid message service. The Spark Hybrid deployment model is suitable for organizations that want to extend the functionality and reach of their on-premises systems and enable seamless collaboration across different environments.

The other options are not valid deployment models for Cisco Spark implementation. CMR stands for Cisco Collaboration Meeting Room, which is a solution that enables users to join meetings from any device, whether it is registered to the Cisco Spark cloud or the on-premises infrastructure. CMR is not a deployment model, but a feature that can be used in both Spark Cloud and Spark Hybrid deployment models. Spark Premises is not a valid option, as Cisco Spark is a cloud-based platform and does not offer a fully on-premises deployment option. References: Cisco Spark Deployment Models, Cisco Spark Hybrid Services, Cisco Collaboration Meeting Rooms (CMR)

A subzone is a logical grouping of endpoints within a zone that allows the Expressway to apply different policies and bandwidth controls to different sets of endpoints1.

An endpoint is a device that can make or receive calls, such as a video conferencing system, a phone, or a soft client2.

When an endpoint registers with the Expressway, it is assigned to a subzone based on the following criteria3:

If the endpoint is making a traversal call (a call that crosses a firewall or a network boundary), it is assigned to the traversal subzone. A traversal call requires a traversal client zone on the Expressway that initiates the call and a traversal server zone on the Expressway that receives the call.

If the endpoint is not making a traversal call, it is assigned to a subzone based on the subzone membership rules. These rules specify the range of IP addresses or alias pattern matches for each subzone. If an endpoint’s IP address or alias does not match any of the membership rules, it is assigned to the default subzone.

If the endpoint is not allowed to register with the Expressway, it is rejected based on the registration restriction rules. These rules specify the IP addresses or aliases of the endpoints that are denied or allowed to register with the Expressway.

Therefore, the two statements that are true about the assignment of endpoints to a subzone are:

A. A registration restriction rule must be configured that matches the endpoint’s alias or IP subnet. This statement is true because the registration restriction rules are used to filter out the endpoints that are not allowed to register with the Expressway based on their alias or IP subnet3.

E. A subzone membership rule must be configured that matches the endpoint’s alias or IP subnet. This statement is true because the subzone membership rules are used to assign the endpoints that are allowed to register with the Expressway to the appropriate subzone based on their alias or IP subnet3.

The other options are incorrect because:

B. Endpoints making a traversal call must be registered to the traversal subzone. This statement is false because the traversal subzone is not a subzone that endpoints can register to, but a subzone that endpoints are assigned to when they make a traversal call3.

C. By default, all endpoints are registered to the default subzone. This statement is false because not all endpoints are registered to the default subzone, only those that do not match any subzone membership rules or make a traversal call3.

D. By default, all endpoints are registered to the neighbor subzone. This statement is false because the neighbor subzone is not a subzone that endpoints can register to, but a subzone that represents a neighbor zone (a logical connection to another Expressway or a third-party device) on the Expressway.

References := 1: Cisco Expressway Administrator Guide (X14.0) 2: Cisco Expressway Basic Configuration Deployment Guide (X8.11) 3: Cisco Expressway Administrator Guide (X14.0) : Cisco Expressway Administrator Guide (X14.0) : Cisco Expressway Administrator Guide (X14.0)

A user policy is a set of rules that defines how a user can access and use the video services. A user policy can include the following options1:

Authentication: This option determines whether a user needs to provide credentials to access the video services, and what type of credentials are required (such as username and password, certificate, or token).

Admin policy: This option determines whether a user has administrative privileges to manage the video services, such as creating and deleting spaces, adding and removing participants, and configuring settings.

Call policy: This option determines whether a user can make and receive calls, and what type of calls are allowed (such as audio only, video only, or both).

Find Me: This option determines whether a user can be reached by other users through a single address, and how the calls are routed to the user’s devices (such as desk phone, mobile phone, or video endpoint).

The correct answer is D, Find Me, because it is one of the options that can be configured in a user policy. The other options are not correct because:

Authentication: This is not a user policy, but a security feature that can be enabled or disabled for the video services.

Admin policy: This is not a user policy, but a role-based access control feature that can be assigned to different users or groups.

Call policy: This is not a user policy, but a service policy that can be applied to different domains or zones.

References := 1: Cisco Meeting Server 3.5 Configuration Guides - User Policy Configuration

 The Cisco Meeting Server uses port 5060 for SIP signaling from the call bridge to the H.323 gateway. This is because port 5060 is the default port for SIP signaling over UDP or TCP, and the Cisco Meeting Server supports both protocols for SIP signaling1. The call bridge communicates with the H.323 gateway using SIP signaling to establish and manage calls between SIP and H.323 endpoints2.

The other options are not correct because:

4999: This is not a port used for SIP signaling, but for H.323 signaling over TCP. The Cisco Meeting Server uses port 4999 for H.323 signaling from the call bridge to the H.323 gateway1.

5222: This is not a port used for SIP signaling, but for XMPP signaling over TCP. The Cisco Meeting Server uses port 5222 for XMPP signaling from the call bridge to the XMPP server1.

6061: This is not a port used for SIP signaling, but for SIP signaling over TLS. The Cisco Meeting Server uses port 6061 for SIP signaling over TLS from the call bridge to the Expressway-C or the SIP proxy1.

References := 1: Cisco Meeting Server 3.5 Configuration Guides - Port Reference 2: Cisco Meeting Server 3.5 Configuration Guides - H.323 Gateway Configuration