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

= OAuth is an open standard for authorization that allows applications and services to access resources on behalf of a user, without sharing the user’s credentials. OAuth uses access tokens to grant permissions to applications and services to access the user’s resources1. Cisco Spark supports OAuth 2.0, which is the latest version of OAuth2.
To use OAuth access tokens with Cisco Spark, you need to follow these steps2:
* Register your application or service to Cisco Spark as an integration. You will receive a client ID and a client secret, which are used to identify your application or service to Cisco Spark.
* Redirect the user to the Cisco Spark authorization URL, where the user can login with their Cisco Spark credentials and grant permissions to your application or service. The permissions are defined by the scopes that you specify in the authorization URL. For example, if you want to access the user’s messages and rooms, you need to request the spark:messages_read and spark:rooms_read scopes.
* Receive an authorization code from Cisco Spark, which is sent to the redirect URI that you specify in the authorization URL. The redirect URI must match the one that you registered with Cisco Spark.
* Exchange the authorization code for an access token and a refresh token from Cisco Spark, using your client ID and client secret. The access token is used to access the user’s resources on Cisco Spark, such as messages, rooms, people, etc. The refresh token is used to obtain a new access token when the current one expires.
* Use the access token to make API requests to Cisco Spark on behalf of the user. You need to include the access token in the Authorization header of your HTTP requests, such as Authorization: Bearer
<access_token>.
Therefore, the two options that are requirements to use OAuth access tokens with Cisco Spark are:
* C. Applications can only request the access token when the authenticated user grants permissions to this service. This is true because the user needs to authorize the application or service to access their resources on Cisco Spark, by logging in and consenting to the scopes that the application or service requests.
* E. Services can request the access token only when the authenticated user grants permissions to this service. This is also true because the service needs to obtain the user’s consent to access their resources on Cisco Spark, by redirecting the user to the Cisco Spark authorization URL and receiving an authorization code.
The other options are not requirements to use OAuth access tokens with Cisco Spark, because:
* A. Tokens must request access to servers before applications register to Cisco Spark. This is false because tokens are not entities that can request access to servers. Tokens are strings that represent the permissions that the user grants to the applications or services. Applications or services need to register to Cisco Spark before they can request tokens, not the other way around.
* B. Servers must register to Cisco Spark as an application to request access tokens. This is false because servers are not the same as applications. Servers are physical or virtual machines that host applications or services. Applications or services are software programs that interact with Cisco Spark. Servers do not need to register to Cisco Spark, but applications or services do.
* D. Applications must register to Cisco Spark as a server to request access tokens. This is also false because applications are not the same as servers. Applications are software programs that interact with Cisco Spark. Servers are physical or virtual machines that host applications or services. Applications do not need to register to Cisco Spark as servers, but as integrations.
References := OAuth 2.0, Cisco Spark for Developers – Authentication

An IDE tool is a software application that provides comprehensive facilities to computer programmers for software development. An IDE normally consists of a source code editor, build automation tools, and a debugger. Cisco Spark is a cloud-based collaboration platform that allows users to create, share, and communicate with each other. Cisco Spark supports various programming languages, such as Python, Java, Node.js, and C#. To develop applications for Cisco Spark, developers need an IDE tool that can work with these languages and interact with the Spark APIs. 1234, one of the IDE tools that can be used with Cisco Spark is OSX: Atom. Atom is a free and open-source text and source code editor for macOS, Linux, and Windows with support for plug-ins written in Node.js, and embedded Git Control, developed by GitHub.
Atom can be customized to work with different languages and frameworks, such as Python, Java, Node.js, and C#. Atom also has a package called spark-tools that provides a set of tools for developing Cisco Spark applications, such as creating bots, webhooks, andintegrations. References := 1: Useful Developer Tools | Apache Spark 2: Create and run Spark application on cluster | IntelliJ IDEA 3: Spark development process with Python and IDE – Stack Overflow 4: Setting up IDEs – PySpark 3.5.0 documentation – Apache Spark :
spark-tools package – Atom

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

* Authentication credentials can be stored in the local database of the Expressway. This is true because the Expressway can use its local authentication database to verify the credentials of incoming requests from devices or external systems1. Alternatively, the Expressway can also use external authentication methods, such as LDAP, SAML, or OAuth1.
* SIP endpoints always need authentication credentials. This is false because the Expressway’s authentication policy can be configured separately for each zone, and it can be set to “Do not check credentials” or “Treat as authenticated” for SIP messages from local or non-local domains1. This means that some SIP endpoints may not need authentication credentials to communicate with the Expressway, depending on the zone configuration.
* The endpoint and Expressway must be configured and synchronized with an NTP server delivering an identical time stamp. This is false because the Expressway and the endpoint do not need to be synchronized with identical NTP timestamps for authentication purposes2. However, it is recommended to synchronize the Expressway and the endpoint with the same NTP server for other reasons, such as logging, troubleshooting, and certificate validation3.
* Expressways and endpoints do not need to be synchronized with identical NTP timestamps. This is true because the Expressway and the endpoint do not need to be synchronized with identical NTP timestamps for authentication purposes2. However, it is recommended to synchronize the Expressway and the endpoint with the same NTP server for other reasons, such as logging, troubleshooting, and certificate validation3.
* When a subzone is set for “Treat as Authenticated”, the endpoint must have the correct authentications configured. This is false because the “Treat as Authenticated” option means that the Expressway will not verify the credentials and will allow the message to be processed as if it has been authenticated1. This option can be used to cater for endpoints from third-party suppliers that do not support authentication within their registration mechanism1.
References := 1: Cisco Expressway Administrator Guide (X14.0) – Device Authentication 2: Cisco Expressway Administrator Guide (X14.0) – NTP Configuration 3: Cisco Expressway Administrator Guide (X14.0) – Time and Date

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