Cisco Video Infrastructure Implementation (VII) 500-710 Exam Dumps: Updated Questions & Answers (October 2025)

= Call-control devices are responsible for establishing, maintaining, and terminating calls in a Cisco Collaboration environment. They provide features such as endpoint registration, call routing, call admission control, codec negotiation, and trunk protocol translation. According to the Cisco Expressway Basic Configuration Deployment Guide, Cisco Expressway is a call-control device that enables secure communication between endpoints inside and outside the enterprise network. According to the Call Control with CUCM for Cisco CICD (210-060) course, Cisco Unified Communications Manager is a call-control device that provides centralized call processing and management for Cisco IP phones, video endpoints, and gateways.

The other options are not call-control devices, but rather collaboration devices that provide different functions. Cisco Telepresence Endpoint is a video device that enables face-to-face communication with high-quality audio and video. Cisco Meeting Server is a conferencing device that enables multiparty audio, video, and web collaboration. Cisco Content Server is a recording and streaming device that enables live and on-demand video content creation and distribution.

References := Cisco Expressway Basic Configuration Deployment Guide, Call Control with CUCM for Cisco CICD (210-060), [Cisco Collaboration Devices At-a-Glance]

 = 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 Calendar Connector for Cisco Spark Hybrid is a feature that allows users to schedule and join Webex meetings from their Microsoft Exchange calendars. To integrate the Calendar Connector with Microsoft Exchange, an impersonation account is needed on the Exchange server. An impersonation account is a service account that has the permission to access other users’ calendars and send meeting invitations on their behalf. The Calendar Connector uses the impersonation account to monitor and update the users’ calendars, and to add Webex meeting details to the invitations. To create and configure an impersonation account on Microsoft Exchange, follow the steps in the deployment guide1. References := Deployment guide for Hybrid Calendar - Deploy Expressway-based Hybrid Calendar for Microsoft Exchange

= The Expressway can act as a SIP registrar for up to 200 domains. To make the Expressway act as a SIP registrar, you must configure it with the SIP domains for which it will be authoritative. It will then handle registration requests for any endpoints attempting to register against that domain. To configure a SIP domain on the Expressway, go to Configuration > Domains and click New. Enter the domain name and select whether the Expressway or the Unified CM provides registration and provisioning services for the domain. You can also configure other options such as authentication, encryption, and call policy for the domain. After adding the domain, you must restart the Expressway for the changes to take effect. A SIP endpoint that wants to register with the Expressway must use a SIP URI that matches one of the configured domains on the Expressway. For example, if the Expressway is configured with the domain example.com, the endpoint must use a SIP URI like user@example.com to register with the Expressway. References := Cisco Expressway Administrator Guide (X14.0) - Configuring DomainsCisco Expressway Basic Configuration Deployment Guide (X14.0) - Configuring SIP Domains

 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

The Cisco Meeting Server (CMS) uses a RESTful API to configure settings on the server. The RESTful API allows the user to perform CRUD (Create, Read, Update, Delete) operations on the CMS resources using HTTP methods such as GET, POST, PUT, and DELETE. The RESTful API also supports JSON and XML formats for the request and response bodies. The CMS web interface and the Cisco Meeting Management (CMM) application use the RESTful API to communicate with the CMS. The other options are not valid types of API for the CMS. References: Cisco Meeting Server API Reference Guide, Cisco Meeting Server Basic API Functions

The Cisco Conductor is a software application that provides intelligent resource management and conference orchestration for video conferencing deployments1.

The service preference is a configuration option in the Cisco Conductor that defines the order of preference for using different bridge pools for a conference2.

A bridge pool is a logical grouping of one or more conference bridges that share the same characteristics, such as location, capacity, media encryption, and conference type2.

The service preference consists of one or more bridge pools and it determines which of these pools, in order of priority, to use for a conference2.

The service preference is applied based on the conference alias that is used to initiate or join a conference2.

The service preference does not determine the conference template, the bandwidth, or the conference alias for a conference. These are determined by other factors, such as the call control system, the conference scheduling system, or the conference bridge configuration2.

References := 1: Cisco TelePresence Conductor - Cisco 2: Cisco TelePresence Conductor Administrator Guide (XC4.3) - Service Preferences

 Cisco WebEx Meeting Center is a cloud-based service that provides video conferencing and collaboration features for WebEx clients and endpoints. It supports calls from Cisco IP phones, Cisco Jabber, Cisco TelePresence, and third-party SIP and H.323 devices. It also integrates with Cisco Unified Communications Manager (UCM) and Cisco Expressway for call control and routing. Cisco WebEx Meeting Center allows users to schedule, join, and host meetings from any device, and share content, chat, and record sessions. It also offers artificial intelligence-powered features such as noise removal, transcription, and translation. References: Cisco WebEx Meeting Center Data Sheet, Deployment guide for Calling in Webex App (Unified CM), Webex Calling for Microsoft Teams

 TMS, or Cisco TelePresence Management Suite, is a software application that enables centralized management of Cisco video conferencing and collaboration devices and systems. TMS relies on the following two operating systems and database applications1:

Windows Server: TMS requires a Windows Server operating system to run. The supported versions are Windows Server 2019, 2016, and 2012 R22.

SQL: TMS requires a SQL database application to store and manage data. The supported versions are SQL Server 2019, 2017, 2016, and 20142.

The other options are not correct because:

Oracle: TMS does not support Oracle as a database application. TMS only supports SQL Server as a database application2.

MS Access: TMS does not support MS Access as a database application. TMS only supports SQL Server as a database application2.

Linux Ubuntu: TMS does not support Linux Ubuntu as an operating system. TMS only supports Windows Server as an operating system2.

References := 1: Cisco TelePresence Management Suite (TMS) - Cisco 2: Cisco TelePresence Management Suite Installation and Upgrade Guide (15.16) - System Requirements [Cisco TelePresence Management Suite] - Cisco

 = 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