Cisco CLCEI 300-820 key terms

Cloud-based management portal for Webex organizations where administrators claim and assign licenses, manage users, configure services, and review analytics and troubleshooting data across the deployment.

Process that binds an existing on-premises or partner-managed deployment to a new Webex cloud organization, typically verified through a DNS TXT record or a token added to an existing public record.

Proof of ownership of an email or SIP domain, established by publishing a DNS TXT or CNAME record, that lets the cloud organization assign and manage users in that domain.

Reusable set of service entitlements, such as meetings, messaging, and calling, applied automatically to users when they are created, assigned, or synchronized into the organization.

Lightweight on-premises agent that synchronizes users from Active Directory or another LDAP source into the Webex cloud organization, keeping accounts current without manual entry.

Scheduled import of user objects and attributes from a directory source into the cloud identity store, including mappings, filtering rules, and conflict handling for existing accounts.

Authentication model in which users sign in once at an identity provider and are asserted to Webex services, removing separate cloud credentials and centralizing access policy.

Signed XML statement from an identity provider that conveys a user's identity and attributes to the service provider during federated authentication, forming the basis of the login session.

Trusted system that authenticates users and issues assertions to relying applications; in Webex deployments it is commonly a cloud or on-premises federation service.

Cloud service that connects to an on-premises or hosted mail system to read room and user calendars, enabling automatic meeting join, scheduling, and One Button to Push behavior.

On-premises application that brokers communication between Webex cloud calendar services and the mail environment, requiring impersonation rights and outbound connectivity to the cloud.

Programming interface exposed by Microsoft Exchange that the calendar connector uses to query mailboxes, create meetings, and manage room resources on behalf of the cloud service.

Exchange mailbox representing a room or device whose calendar is read by the cloud so meetings scheduled there can launch automatically on the associated video endpoint.

Feature that pushes scheduled meeting details to a video endpoint so participants can join with a single remote-control press, eliminating manual dialing of meeting identifiers.

Cisco traversal and registration appliance that pairs an internal and external node to let endpoints register from outside the network and reach internal collaboration services securely.

Two Expressway nodes, one inside and one outside the firewall, connected by a protected tunnel so signaling and media can pass without opening inbound ports to the internal network.

Deployment model using a traversal pair to register off-network endpoints and clients to on-premises call control, providing service without a dedicated VPN client.

Configuration on the external Expressway that terminates secure connections from remote endpoints and forwards traffic inward over the traversal zone to internal services.

Logical link between the internal and external Expressway nodes that carries SIP and media over a protected connection, distinct from a regular neighbor zone.

Licensing and configuration option on Expressway that enables firewall traversal for call signaling and media, required for mobile and remote access and hybrid service connectivity.

Connector software installed on an on-premises host that establishes outbound connections to Webex cloud services, enabling calendar, directory, and call routing features without inbound firewall rules.

Hybrid component that links on-premises call control to the Webex cloud, allowing cloud-registered devices and users to place and receive calls through the enterprise telephony environment.

Configuration in which endpoints register to a cloud-based call control service rather than an on-premises cluster, often paired with hybrid connectors for PSTN and enterprise dialing.

On-premises gateway, such as an Integrated Services Router or Expressway, that connects cloud calling to the PSTN and to existing on-premises call control for shared dial plans.

Set of patterns, translations, and routing rules that determines how dialed digits are interpreted and where calls are sent across on-premises, cloud, and PSTN destinations.

Ordered list of gateways or trunks used by call control to select an outbound path, with distribution and priority settings determining which device handles a given call.

Service model where call control and telephony features are delivered from the Webex cloud, with PSTN access provided by Cisco or a connected local gateway.

Architecture that keeps call control on-premises while extending cloud services to users and rooms, requiring connectors and edge components to bridge the two environments.

Overall arrangement of collaboration services, such as on-premises, cloud-only, or hybrid, that determines which components are required and how users are provisioned and routed.

Cloud object representing a physical room or desk device, carrying its own license, configuration, and calendar association independent of a user account.

Link between the calling environment and the public telephone network, provided through cloud-delivered service or on-premises gateway circuits registered to the deployment.

Technique for passing signaling and media through NAT and firewall boundaries using a trusted external node, avoiding inbound port openings to protected internal systems.

Requirement that edge nodes, connectors, and cloud services present certificates signed by a recognized authority so secure sessions can be established between components.

Marking and queuing policy applied to voice and video traffic so latency, jitter, and loss remain acceptable as media crosses enterprise and edge boundaries.

Control Hub tool that traces a user's meeting or call path and reports component status, helping isolate failures in calendar, connector, or edge connectivity.

Record of administrative actions and security-relevant events in the cloud organization, used to investigate configuration changes and satisfy compliance reviews.