Pass the Cisco Field Engineer 500-710 Questions and answers with ExamsMirror

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 WebEx Telepresence is a cloud-based service that enables on-premises endpoints to register to Cisco infrastructure in the cloud and join video calls with other WebEx Telepresence users or compatible standards-based conferencing systems over the Internet. It also provides features such as directory, presence, scheduling, and management for the registered endpoints. Cisco WebEx Telepresence works with various Cisco TelePresence endpoints, such as multipurpose, integrator, personal, and video mobility systems123. References := 123

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

 = 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

= Call Service Connect is a hybrid service that allows integration between Cisco Spark and Cisco Unified Communications Manager (CUCM). Call Service Connect enables the Cisco Spark app to be used as a softphone for voice and video calling, and to share an extension with the CUCM desk phone. Call Service Connect also provides a unified call history and caller ID across Cisco Spark and CUCM devices123

Call Service Connect requires media traversal capabilities and licenses to be installed on the Expressway-C and Expressway-E pair that connects the CUCM and the Cisco Collaboration Cloud. Call Service Connect also requires mutual TLS (mTLS) authentication between the Expressway-E and the cloud, and between the Expressway-C and the CUCM. Call Service Connect depends on Call Service Aware, which is another hybrid service that synchronizes the user and device information from the CUCM to the cloud. Call Service Aware must be deployed before Call Service Connect124

References := 1Cisco Spark Hybrid Services Data Sheet 2Cisco Spark Hybrid Services Deployment Guide 3Cisco Spark Hybrid Services At-a-Glance 4Deployment guide for Hybrid Calling for Webex Devices (Device Connector)

 Cisco TMS (TelePresence Management Suite) is the application that is integrated with the CMR solutions to provide for conference scheduling. Cisco TMS allows users to schedule video conferences using a web interface, Microsoft Outlook, or Cisco Jabber. Cisco TMS also providesmanagement and monitoring of video endpoints and infrastructure, as well as reporting and analytics123 References := 1Cisco Collaboration Meeting Rooms (CMR) Premises Solution Guide Release 5 2Cisco TelePresence Management Suite - Products & Services - Cisco 3Configure Bridge Scheduling - Cisco

= The Cisco Meeting Server uses a RESTful API to interact with the server. The API commands are sent via HTTP requests to the web admin service, which processes them and returns the response. The four basic API commands are GET, POST, PUT, and DELETE. Each command has a different function and syntax, as explained below12:

GET: Retrieves existing information from the server. The syntax is GET /api/v1/