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

According to the Cisco documentation1, the engineer can look on the Conductor web interface under Status > Calls > In Progress to view information about a call currently in progress. This page shows the details of each call, such as the call ID, the conference alias, the call type, the call state, the call duration, the call rate, the call protocol, the encryption status, and the call participants. The other options, such as Status > Calls > Calls, Logs > Event Log, and Status > Conferences > In Progress, do not show the information about a call currently in progress, but rather show the information about all calls, the event log messages, and the conferences in progress, respectively. References: 1: Cisco TelePresence Conductor Administrator Guide (XC4.3), Chapter 5: Monitoring Conferences and Calls, https://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/conductor/admin_guide/Cisco-TelePresence-Conductor-Administrator-Guide-XC4-3.pdf

 TURN servers must be configured in a resilient and scalable Cisco Meeting Servers solution on the CMS edge only. The CMS edge is the component that provides firewall traversal and NAT traversal for external participants using WebRTC or SIP. The CMS edge acts as a TURN server that relays the media traffic between the external participants and the CMS core, which hosts the conferences. The CMS edge also performs media demultiplexing and encryption/decryption for the media streams. The CMS core does not need to have TURN servers configured, as it communicates directly with the internal endpoints and the CMS edge. The Cisco Unified Communications Manager does not need to have TURN servers configured either, as it is not involved in the media path for the CMS conferences123 References := 1Cisco Meeting Server - Configuration Guides 2Cisco Meeting Server 3.8, Scaled and Resilient Server Deployment Guide 3TURN Server and WebRTC

When a source endpoint dials a destination endpoint, the first thing to occur is that an invite is sent to the SIP Server. The SIP Server is a logical entity that handles the signaling and call setup between SIP endpoints. The invite message contains the source endpoint’s identity, capabilities, and session parameters, as well as the destination endpoint’s address. The SIP Server thenroutes the invite message to the destination endpoint or to another SIP Server if the destination endpoint is in a different domain12. References := 12

An endpoint registration request message that is sent to a SIP Server contains the following two options1:

E.164 address: This is the telephone number of the endpoint, which is used to identify the endpoint in the SIP domain. The E.164 address is also known as the Address of Record (AOR), which is a high-level name that is assigned to a SIP entity without regard to the device or devices that name might use. The format for an AOR is sip:user@domain (e.g. 2025551234@sip.plivo.com)2.

SIP URI: This is the location of the endpoint, which is identified by an IP address, port number and protocol. The SIP URI is used to reach the endpoint for establishing a media session. Theformat for a SIP URI is sip:user@host:port;transport (e.g. sip:2025551234@192.168.1.120:5060;udp)1.

The other options are not correct because:

SIP Server IP address: This is not included in the endpoint registration request message, as the endpoint already knows the IP address of the SIP Server to which it is sending the message. The SIP Server IP address is usually configured in the endpoint settings as the Registration Domain or the Outbound Proxy3.

Endpoint IP address: This is not included in the endpoint registration request message, as it is already part of the SIP URI. The endpoint IP address is the host part of the SIP URI, which indicates the location of the endpoint1.

E.164URI: This is not a valid option, as there is no such thing as an E.164URI. The E.164 address is not a URI, but a telephone number that is used to identify the endpoint in the SIP domain2.

References := 1: Cisco Unified Communications System 9.0 SRND - SIP Infrastructure 2: SIP signalling- the registration process and setting up a SIP call 3: Programmable Voice - SIP Registration | Twilio

system network directory is a phone book source that imports contacts from a directory server that uses the H.350 protocol. TMS can connect to multiple system network directories and synchronize the contacts with the TMS database. The system network directory can be used to create phone books for endpoints that are managed by TMS. The other options are not valid phone book sources for TMS. References: Cisco TelePresence Management Suite Phone Book Configuration Guide, TMS Phone Books Troubleshoot Guide

The engineer needs to navigate to Systems > Configuration Templates to create this setting. This is because TMS, or Cisco TelePresence Management Suite, is a software application that enables centralized management of Cisco video conferencing and collaboration devices and systems. TMS can use configuration templates to configure and update multiple endpoints with the same settings, such as registration configurations, network settings, security settings, and so on1. The engineer can create a configuration template with the desired registration configurations for the group of endpoints in the remote office, and then schedule the template to be applied automatically every Sunday at 3:00 a.m. using the TMS Tools application2.

The other options are not correct because:

Systems > Manage Dial Plan: This is not the correct navigation, as this option is used to manage the dial plan for the video network, such as creating prefixes, aliases, and zones. This option does not allow creating or applying configuration templates3.

Systems > Provisioning: This is not the correct navigation, as this option is used to manage the provisioning of endpoints that are registered to Cisco Unified Communications Manager or Cisco VCS. This option does not allow creating or applying configuration templates4.

Systems > Navigator: This is not the correct navigation, as this option is used to manage the Navigator clusters that aggregate multiple Cisco VCS or Expressway devices into a single entity. This option does not allow creating or applying configuration templates.

References := 1: Cisco TelePresence Management Suite Administrator Guide (15.16) - Templates [Cisco TelePresence Management Suite] - Cisco 2: Cisco TelePresence Management Suite Administrator Guide (15.16) - Applying Templates [Cisco TelePresence Management Suite] - Cisco 3: Cisco TelePresence Management Suite Administrator Guide (15.16) - Dial Plan [Cisco TelePresence Management Suite] - Cisco 4: Cisco TelePresence Management Suite Administrator Guide (15.16) - Provisioning [CiscoTelePresence Management Suite] - Cisco : Cisco TelePresence Management Suite Administrator Guide (15.16) - Navigator [Cisco TelePresence Management Suite] - Cisco

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)

= The scaled and resilient server deployment model is the best solution to accommodate fail-over for Cisco Meeting Server. This model involves deploying multiple Meeting Servers clustered together to provide greater scale and resilience in the deployment. The cluster can span across different locations and support up to 2500 HD ports. The cluster can also handle the failure of one or more servers without affecting the ongoing conferences or the user experience. The cluster uses a load balancer to distribute the incoming calls among the available servers, and uses a database replication mechanism to synchronize the conference state and configuration across the servers123 References := 1Cisco Meeting Server - Configuration Guides 2CiscoMeeting Server 3.8, Scaled and Resilient Server Deployment Guide 3Cisco Meeting Server 3.8, White Paper on Load Balancing Calls Across Cisco Meeting Servers

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 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