= 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.pdfhttps://community.cisco.com/t5/audio-and-video-endpoints/tms-api- licenses/td-p/3596708

Cisco Meeting Server allows you to customize the appearance and behavior of the spaces that host the meetings. You can add a logo to the standard layout, change the background color, adjust the video quality and bandwidth, enable or disable file sharing, and more. You can also create customized layouts for specific spaces or participants, using the API or the ActiveControl app. These customization options can enhance the user experience and the branding of your organization. References: Cisco Meeting Server 3.8 Customization Guidelines, Cisco Meeting Server 3.7 and later, Administrator Guide to Screen Layouts and Pane Placement, and Customized Layouts, Cisco Meeting Server 3.6 Demo v1

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

* Cisco Expressway is a video gateway that enables interoperability between different video endpoints and protocols. It consists of two components: Expressway core and Expressway edge1.
* Cisco Meeting Server is a video conferencing solution that supports scalable and resilient deployments with multiple servers and clusters. It can integrate with various call control systems, such as Cisco Unified Communications Manager, Cisco Expressway, or Microsoft Skype for Business2.
* To integrate Cisco Expressway with Cisco Meeting Server, the following steps are required3:
* Configure the Expressway edge as the traversal server for the Meeting Server, and enable SIP and H.323 protocols on the Expressway edge.
* Configure the Expressway core as the traversal client for the Meeting Server, and enable SIP and H.323 protocols on the Expressway core.
* Configure the Meeting Server as the traversal server for the Expressway core, and enable SIP and H.323 protocols on the Meeting Server.
* Configure the call control system to route calls to the Expressway core, and configure the Expressway core to route calls to the Meeting Server.
* Optionally, configure the Expressway core to provide IM&P and video integration with Microsoft Skype for Business, if deployed in the core network with the Meeting Server.
* By integrating both Expressway core and Expressway edge with Cisco Meeting Server, the following benefits can be achieved3:
* Support for various video endpoints and protocols, such as SIP, H.323, WebRTC, and BFCP.
* Support for firewall traversal and NAT traversal for external participants.
* Support for encryption and authentication for secure communication.
* Support for load balancing and failover for high availability and scalability.
References := 1: Cisco Expressway Series – Data Sheets – Cisco 2: Cisco Meeting Server – Configuration Guides – Cisco 3: Cisco Meeting Server, Deployments with Expressway Planning and Preparation Guide

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