500-710 Video Infrastructure Implementation (VII) Questions and Answers

The Expressway uses subzones and pipes to control the bandwidth used by endpoints on the network. Subzones are logical groups of endpoints that share the same bandwidth policies and settings. Pipes are logical connections between subzones or zones that limit the total or per-call bandwidth available for calls. The Expressway allows the administrator to configure the bandwidth limits for each subzone and pipe, as well as the behavior when the bandwidth is insufficient or not specified. The other options are not valid methods for bandwidth control on the Expressway.  References :  Cisco Expressway Administrator Guide (X14.0) - Bandwidth Control ,  Cisco Expressway Basic Configuration Deployment Guide (X14.0) - Configuring Bandwidth Management

To write a new app in Tropo, you need to use the Web (HTTP) API, which allows you to run your app scripts on your own servers. The app scripts can be written in any of the supported languages: Groovy, JavaScript, PHP, Python, or Ruby. However, the file extension for the app scripts must be .js, regardless of the language you use. This is because Tropo uses the .js extension to identify the app scripts and load them into the Tropo engine. If you use a different extension, Tropo will not recognize your app scripts and will not execute them.  References :  Tropo WebAPI Shipped Buildpack ,  Tropo Sample Applications ,  When writing new App in Tropo, in what format should the App Scripts be saved?

 A SIP alias is an alternative address for a SIP URI, which is the standard format for identifying a user or a service in a SIP network. A SIP URI consists of a user part, an at sign (@), and a host part, such as user@host. The user part can be a username, a phone number, or any other identifier. The host part can be a domain name, an IP address, or any other network address.  For example, alice@example.com, +1234567890@voip.com, and bob@192.168.1.1 are valid SIP URIs 1 .

A SIP alias is a way of creating multiple SIP URIs for the same user or service, using different user parts or host parts. For example, if a user has a SIP URI of john.doe@cisco.com, he can also have a SIP alias of jdoe@cisco.com, or john.doe@voip.cisco.com, or any other combination of user and host parts.  A SIP alias can be useful for providing different contact options, simplifying dialing, or hiding the real SIP URI for privacy or security reasons 2 .

To configure a SIP alias, you need to have a SIP account with a SIP service provider that supports SIP alias, such as iptel.org. You also need to have a SIP device or application that can register and use the SIP alias, such as a VoIP phone, a softphone, or a router.  You can create and manage your SIP alias using the web interface of your SIP service provider, or using the configuration settings of your SIP device or application 2 .

The correct format for a SIP alias is the same as the format for a SIP URI, which is user@host. Therefore, the option C. John.doe@cisco.com is the correct format for a SIP alias, as it has a user part (John.doe) and a host part (cisco.com) separated by an at sign (@). The other options are not correct formats for a SIP alias, because:

A. 212-555-1212 : This is a phone number, not a SIP URI. It does not have a user part or a host part, and it does not have an at sign (@).

B. +12125551212 : This is also a phone number, not a SIP URI. It does not have a user part or a host part, and it does not have an at sign (@).

D. John.doe : This is only a user part, not a SIP URI. It does not have a host part, and it does not have an at sign (@).

References  :=  Session Initiation Protocol (SIP) Parameters ,  How to configure SIP Alias | DrayTek

 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 signaling 1 .  The call bridge communicates with the H.323 gateway using SIP signaling to establish and manage calls between SIP and H.323 endpoints 2 .

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 gateway 1 .

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 server 1 .

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 proxy 1 .

References  :=  1 : Cisco Meeting Server 3.5 Configuration Guides - Port Reference  2 : Cisco Meeting Server 3.5 Configuration Guides - H.323 Gateway Configuration

The SIP message that is sent from the called endpoint after the call request is accepted is “200 OK”. This message indicates that the called endpoint has agreed to participate in the session and is ready to receive media. The “200 OK” message also contains the session description protocol (SDP) information that specifies the media capabilities and parameters of the called endpoint, such as the codec, the port number, and the encryption method. The “200 OK” message is sent as a response to the “INVITE” message that was sent by the caller to initiate the session.  The caller then acknowledges the “200 OK” message by sending an “ACK” message, which completes the session establishment 1 2

The other options are not valid SIP messages that are sent from the called endpoint after the call request is accepted. “Hello” is not a SIP message at all, but a common greeting. “404 OK” is a nonsensical combination of a SIP error code and a SIP status code. “404” means “Not Found”, which indicates that the requested user or service does not exist or is not available. “OK” means “Success”, which indicates that the request was fulfilled. These two codes are contradictory and cannot be used together.  “Connect” is not a SIP message either, but a generic term for establishing a link or a communica tion 3 4   References :  SIP - Basic Call Flow - Online Tutorials Library ,  Understanding SIP INVITE method and messages - Wildix blog ,  Session Initiation Protocol - Wikipedia ,  Basic SIP Call Flows & Troubleshooting Commands - Cisco Community

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

A user policy is a set of rules that defines how a user can access and use the video services.  A user policy can include the following options 1 :

Authentication: This option determines whether a user needs to provide credentials to access the video services, and what type of credentials are required (such as username and password, certificate, or token).

Admin policy: This option determines whether a user has administrative privileges to manage the video services, such as creating and deleting spaces, adding and removing participants, and configuring settings.

Call policy: This option determines whether a user can make and receive calls, and what type of calls are allowed (such as audio only, video only, or both).

Find Me: This option determines whether a user can be reached by other users through a single address, and how the calls are routed to the user’s devices (such as desk phone, mobile phone, or video endpoint).

The correct answer is D, Find Me, because it is one of the options that can be configured in a user policy. The other options are not correct because:

Authentication: This is not a user policy, but a security feature that can be enabled or disabled for the video services.

Admin policy: This is not a user policy, but a role-based access control feature that can be assigned to different users or groups.

Call policy: This is not a user policy, but a service policy that can be applied to different domains or zones.

References  :=  1 : Cisco Meeting Server 3.5 Configuration Guides - User Policy Configuration

 Cisco Spark is a cloud-based collaboration platform that allows users to create, share, and communicate with each other through messaging, calling, and meeting features. Cisco Spark can be integrated with an on-premises solution using hybrid connectors, which are software applications that securely connect Cisco Spark to the organization’s premises or to the Cisco Hosted Collaboration Solution (HCS) in a partner cloud. The hybrid connectors enable integration with Cisco Spark for various services, such as calendar, call, directory, media, and serviceability.  1 2 3 4 5 , three hybrid connectors that allow Cisco Spark to be integrated with an on-premises solution are:

Calendar Connector: This connector allows users to schedule and join Webex meetings from their Microsoft Exchange or Google Calendar. It also enables features such as One Button to Push (OBTP) and Personal Meeting Room (PMR) for Cisco video devices. The Calendar Connector runs as an application within Cisco Expressway or Enterprise Compute Platform (ECP).

Call Connector: This connector allows users to make and receive calls from their Cisco Spark app using their existing phone system, such as Cisco Unified Communications Manager or Cisco HCS. It also enables features such as single number reach, call control, and call history. The Call Connector runs as an application within Cisco Expressway or ECP.

Directory Connect: This connector allows users to synchronize their user directory from their on-premises Active Directory or LDAP server to Cisco Spark. It also enables features such as user search, user profile, and user activation. The Directory Connect runs as an application within Cisco Expressway or ECP.

The other options, such as Calendar Aware, Directory Service, and Calendar Service, are not hybrid connectors for Cisco Spark. Calendar Aware is a feature that allows users to see the availability of other users based on their calendar status. Directory Service is a feature that allows users to search and view the contact details of other users. Calendar Service is a feature that allows users to schedule and join meetings from their Cisco Spark app. These features are enabled by the hybrid connectors, but they are not connectors themselves.  References  :=  Cisco Spark Hybrid Services Data Sheet Cisco Spark Hybrid Services - Cisco Deployment guide for Hybrid Calendar - Deploy Expressway-based Hybrid Calendar for Microsoft Exchange Deployment guide for Hybrid Call Service - Deploy Expressway-based Hybrid Call Service Deployment guide for Hybrid Directory Service - Deploy Expressway-based Hybrid Directory Service

 The Cisco Meeting Server (CMS) supports H.323-to-SIP interworking, which means it can receive and send H.323 calls and convert them to SIP calls. The CMS does not support H.323 registration or call control, as it is a SIP-based solution. The CMS uses the Cisco Expressway as the edge device to handle H.323 calls from external networks. The CMS also has an optional H.323 gateway component that can be enabled on the same server or on a separate server, but this component is not supported from version 3.0 of the CMS software and has been removed. The H.323 gateway component allows the CMS to receive H.323 calls directly without the need for a gatekeeper or a Cisco Expressway. However, the H.323 gateway component does not provide call control or routing functionality, and it is recommended to use a gatekeeper or a Cisco Expressway for those purposes.  References :  Cisco Meeting Server 3.1, Single Combined Server Deployment Guide ,  Should I continue to deploy the H.323 component of Cisco Meeting Server … ,  Cisco Meeting Server: Enabling H.323 Calls - Fatih Erikci

= To schedule a CMS conference on TMS with WebEx as a participant, the engineer needs to ensure that the WebEx server address is correctly configured in both TMS and CMS. This is because TMS uses the WebEx server address to create an externally hosted conference with a WebEx SIP URI, and CMS uses the WebEx server address to dial out to the WebEx meeting. The WebEx server address can be configured in TMS under Administrative Tools > Configuration > Network Settings > WebEx Settings, and in CMS under Configuration > WebEx.  The WebEx server address should match the WebEx site URL that is used to join the WebEx meeting 1 2 .  References  :=  1 2

A  subzone  is a logical grouping of endpoints within a zone that allows the Expressway to apply different policies and bandwidth controls to different sets of endpoints 1 .

An  endpoint  is a device that can make or receive calls, such as a video conferencing system, a phone, or a soft client 2 .

When an endpoint registers with the Expressway, it is assigned to a subzone based on the following criteria 3 :

If the endpoint is making a traversal call (a call that crosses a firewall or a network boundary), it is assigned to the  traversal subzone . A traversal call requires a traversal client zone on the Expressway that initiates the call and a traversal server zone on the Expressway that receives the call.

If the endpoint is not making a traversal call, it is assigned to a subzone based on the  subzone membership rules . These rules specify the range of IP addresses or alias pattern matches for each subzone. If an endpoint’s IP address or alias does not match any of the membership rules, it is assigned to the  default subzone .

If the endpoint is not allowed to register with the Expressway, it is rejected based on the  registration restriction rules . These rules specify the IP addresses or aliases of the endpoints that are denied or allowed to register with the Expressway.

Therefore, the two statements that are true about the assignment of endpoints to a subzone are:

A. A registration restriction rule must be configured that matches the endpoint’s alias or IP subnet.  This statement is true because the registration restriction rules are used to filter out the endpoints that are not allowed to register with the Expressway based on their alias or IP subnet 3 .

E. A subzone membership rule must be configured that matches the endpoint’s alias or IP subnet.  This statement is true because the subzone membership rules are used to assign the endpoints that are allowed to register with the Expressway to the appropriate subzone based on their alias or IP subnet 3 .

The other options are incorrect because:

B. Endpoints making a traversal call must be registered to the traversal subzone.  This statement is false because the traversal subzone is not a subzone that endpoints can register to, but a subzone that endpoints are assigned to when they make a traversal call 3 .

C. By default, all endpoints are registered to the default subzone.  This statement is false because not all endpoints are registered to the default subzone, only those that do not match any subzone membership rules or make a traversal call 3 .

D. By default, all endpoints are registered to the neighbor subzone. This statement is false because the neighbor subzone is not a subzone that endpoints can register to, but a subzone that represents a neighbor zone (a logical connection to another Expressway or a third-party device) on the Expressway.

References  :=  1 :  Cisco Expressway Administrator Guide (X14.0)   2 : Cisco Expressway Basic Configuration Deployment Guide (X8.11)  3 :  Cisco Expressway Administrator Guide (X14.0)  :  Cisco Expressway Administrator Guide (X14.0)  :  Cisco Expressway Administrator Guide (X14.0)

 The minimum number of databases that can exist within a cluster when deploying a resilient and scalable Cisco Meeting Server deployment is 3. This is because a database cluster of 3 nodes can tolerate the failure of one node and still maintain a quorum, which is the majority of nodes that are online and can agree on the state of the data. A database cluster of 2 nodes cannot tolerate any failure, as it would lose the quorum and become unavailable.  A database cluster of more than 3 nodes can also work, but it would consume more resources and increase the complexity of the deployment 1 .

References  :=  1 : Frequently Asked Questions - Why do I need a database cluster with at least 3 nodes rather than 2 for my Meeting Server deployment?

 The priority number governs the order in which the search rules query the local zone versus neighbored Expressways. The priority number is a value between 1 and 1000 that is assigned to each search rule. The lower the priority number, the higher the precedence of the search rule. The Expressway evaluates the search rules in ascending order of priority numbers, and stops when it finds a match.  The priority number determines which zone (local or neighbor) is searched first for a given destination alias 1 2 3   References  :=  1 Cisco Expressway Administrator Guide (X14.0) - Search Rules   2 Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - Routing Configuration   3 Concept of Zones Demystified On Cisco Expressway Series

The Session Description Protocol (SDP) is a protocol that defines a text-based format for describing the multimedia sessions and the media streams involved in them 1 2 .

SDP is used to convey information such as the session name, purpose, originator, timing, media types, codecs, formats, transport protocols, ports, addresses, encryption keys, bandwidth, and other attributes 1 2 .

SDP is typically used in conjunction with other signaling protocols, such as SIP, H.323, or RTSP, to establish and control the multimedia sessions 1 2 .

SDP does not itself provide any mechanism for transporting the media streams; it only describes them.  The actual media transport is done by protocols such as RTP, which uses the information provided by SDP to set up the appropriate ports and codecs 1 2 .

References  :=  1 :  Session Description Protocol - Wikipedia   2 :  RFC 4566 - SDP: Session Description Protocol

 A template is being persistently pushed to the endpoint from TMS. 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 templates to configure and update multiple endpoints with the same settings, such as alias information, network settings, security settings, and so on 1 .  If a template is applied to an endpoint, any manual changes made to the endpoint will be overwritten by the template settings the next time the template is pushed by TMS 2 . Therefore, if an administrator notices that the alias information changes revert back to their original state the following day, it is most likely that a template is being persistently pushed to the endpoint from TMS.

The other options are not correct because:

The changes are not being saved properly on the endpoint: This is not likely, as the changes are successful and visible on the endpoint until the next day.  If the changes were not saved properly on the endpoint, they would not take effect at all or would be lost after a reboot or power cycle of the endpoint 3 .

A template is being pushed persistently to the endpoint from the Expressway: This is not possible, as the Expressway does not support pushing templates to endpoints. The Expressway is a network device that provides firewall traversal, NAT, and encryption services for video communications. The Expressway does not have the capability to configure or update endpoints with templates.

The alias information of the endpoint is duplicated on another endpoint: This is not relevant, as the alias information of the endpoint is not affected by the alias information of another endpoint. The alias information is a unique identifier for the endpoint that is used for registration and dialing purposes. The alias information of another endpoint does not overwrite or interfere with the alias information of the endpoint in question.

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) - Configuring Endpoints [Cisco TelePresence Management Suite] - Cisco : Cisco Expressway Basic Configuration Deployment Guide (X12.6) - Introduction [Cisco Expressway Series] - Cisco : Cisco Expressway Basic Configuration Deployment Guide (X12.6) - Registering Aliases [Cisco Expressway Series] - Cisco

= To match an alias from the cisco.com domain, with the host portion of the alias consisting of first name.1st name, with no limits on the length of either name, you need to use a regular expression that can capture any characters before and after a dot (.) and before the @ sign.  A regular expression is a way of describing patterns of text using special characters and symbols 1 .  The Expressway supports the use of regular expressions in several features, such as search rules, transforms, and dial plan 2 .

The regular expression that can match the desired alias is:

(. ).(. )@cisco.com : This means that the Expressway will match any characters (.) zero or more times ( ) before and after a dot (.) and before the @ sign, and capture them as two groups ((. )). The parentheses indicate the grouping of the characters. The dot is a special character in regular expressions that means any character, so it needs to be escaped with a backslash () to match it literally. The @ sign and the cisco.com are matched literally.

For example, this regular expression will match John.Doe@cisco.com, Jane.Smith@cisco.com, Bob123.Alice456@cisco.com, etc. and capture John, Doe, Jane, Smith, Bob123, and Alice456 as groups.

The other options are not correct because:

B. (\d*).(\d)@cisco.com : This means that the Expressway will match any digits (\d) zero or more times ( ) before and after a dot (.) and before the @ sign, and capture them as two groups ((\d )). The parentheses indicate the grouping of the characters. The \d is a special character in regular expressions that means a digit from 0 to 9. This is too restrictive and will not match any characters other than digits, such as letters or symbols.

C. (. )/(. )@cisco.com : This means that the Expressway will match any characters (.) zero or more times ( ) before and after a slash (/) and before the @ sign, and capture them as two groups ((. )). The parentheses indicate the grouping of the characters. The slash is not a special character in regular expressions, so it is matched literally. This is incorrect because the alias does not contain a slash, but a dot, between the first name and the last name.

D. (. ).( )@cisco.com : This means that the Expressway will match any characters (.) zero or more times ( ) before and after a dot (.) and before the @ sign, and capture them as two groups ((. )). The parentheses indicate the grouping of the characters. The dot is a special character in regular expressions that means any character, so it is not escaped with a backslash () to match it literally. This is incorrect because the dot will match any character, not just a dot, between the first name and the last name.

References  :=  Regular Expressions ,  Cisco Expressway Basic Configuration Deployment Guide

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

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

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 type 2 .

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 conference 2 .

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

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 configuration 2 .

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

= 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 devices 1 2 3

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 Connect 1 2 4

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

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

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. The format 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 Proxy 3 .

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 endpoint 1 .

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 domain 2 .

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

= The traversal subzone is a conceptual subzone that does not have any registered endpoints. Its sole purpose is to control the bandwidth that is used by traversal calls. Traversal calls are calls that pass through a firewall or a NAT device, using a pair of Expressways (one acting as a traversal client and the other as a traversal server). The traversal subzone allows the administrator to set a limit on the total bandwidth that can be used by traversal calls, as well as the bandwidth per call.  This helps to optimize the network resources and prevent congestion 1 2 3   References  :=  1 Concept of Zones Demystified On Cisco Expressway Series   2 Cisco Expressway Administrator Guide (X14.3) - Clustering and Peers   3 Cisco Expressway Administrator Guide (X14.0) - Bandwidth Control

= TMS permissions are assigned to groups, and users are added to the groups. This is because TMS uses a role-based access control model, where different groups have different levels of access and privileges to the TMS functions and resources. Users can belong to one or more groups, and inherit the permissions of those groups.  TMS provides some predefined groups, such as Administrators, Booking, Users, and Read Only, and also allows creating custom groups with specific permissions 1 .

The other options are not correct because:

TMS permissions are directly assigned to individual users: This is not true, as TMS does not allow assigning permissions to individual users.  Users can only have permissions through the groups they belong to 1 .

TMS permissions can be imported from the Expressway or Cisco Unified Communications Manager: This is not true, as TMS does not support importing permissions from other systems.  TMS permissions are configured and managed within the TMS application 1 .

TMS permissions are configured in Active Directory, which is then synched to TMS: This is partially true, as TMS can integrate with Active Directory to authenticate users and import user accounts and groups. However, the permissions are not configured in Active Directory, but in TMS.  The Active Directory groups are mapped to the TMS groups, and the permissions are applied accordingly 2 .

References  :=  1 : Cisco TelePresence Management Suite Administrator Guide (15.16) - User Administration [Cisco TelePresence Management Suite] - Cisco  2 : Cisco TelePresence Management Suite Administrator Guide (15.16) - Active Directory Integration [Cisco TelePresence Management Suite] - Cisco

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

Branding on the Cisco Meeting Server refers to the customization of prompts and backgrounds for the web app, SIP calls, and IVR messages.  With a single branding license, you can customize the following aspects of the Cisco Meeting Server 1 :

The sign-in page background image, icon, and logo for the web app

The text strings for the web app

The audio messages and background image for the SIP calls

The audio messages and background image for the IVR messages

The invitation text for the web app

You can apply branding to the Cisco Meeting Server in two ways: web server hosted branding or locally hosted branding 1 . Web server hosted branding requires a web server that hosts the branding files and provides the URLs to the Cisco Meeting Server API.  Locally hosted branding requires uploading the branding files to the Cisco Meeting Server using the API 1 .

With web server hosted branding, you can use a single branding license to customize multiple logos and multiple backgrounds on multiple web bridges.  This means that you can have different branding for different web bridges, depending on the web bridge profile that you associate with the web bridge 1 . For example, you can have a web bridge with a blue logo and background for one web bridge profile, and another web bridge with a red logo and background for another web bridge profile.

With locally hosted branding, you can use a single branding license to customize a single logo and single background on a single web bridge.  This means that you can only have one branding for one web bridge, regardless of the web bridge profile that you associate with the web bridge 1 . For example, you can only have a web bridge with a green logo and background for any web bridge profile.

Therefore, the correct answer is B and E, as they describe the capabilities of web server hosted branding and locally hosted branding, respectively.  References  :=  1 : Cisco Meeting Server 3.5 Customization Guidelines,

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

Cisco WebEx is a cloud-based collaboration platform that offers various products and services for online meetings, webinars, training, and support 1 .

Cisco WebEx products have different capacities and features depending on the type and purpose of the online event 2 .

the only Cisco WebEx product that can support up to 3000 attendees is the  Cisco WebEx Event Center 3 4 5 .  The Cisco WebEx Event Center is designed for large-scale webinars and online events that require registration, presentation, Q & A, polling, and recording 2 .

The other options are incorrect because:

Cisco WebEx Meeting Center  is the core product for online meetings and video conferencing that supports up to 1000 participants 2 .

Cisco WebEx Training Center  is a product for online training and education that supports up to 1000 participants and offers breakout sessions, testing, and grading 2 .

Cisco WebEx Support Center  is a product for remote technical support and customer service that supports up to 5 participants and offers chat, file transfer, and remote control 2 .

References  :=  1 :  Cisco WebEx - Overview   2 :  Support for Webex Meetings   3 :  Webex Events (new) is now Webex Webinars   4 :  Compare Webex Webinars and Webex Events (classic)   5 :  Maximum attendee size for Training or Meeting events?