300-825 Sample Questions & Answers

The Meetings Dashboard in Cisco Meeting Management is the primary landing page and is designed to provide a high-level, at-a-glance summary. It shows key performance indicators such as the number of active meetings and participants, license usage, and a summary of call quality (good, fair, poor), which directly addresses the operations team's requirements.

SIP Route Patterns are used in CUCM specifically to route calls based on the domain portion of a SIP URI. The engineer would configure a SIP Route Pattern for the domain conferencing.example.com and associate it with the SIP trunk pointing to the Cisco Meeting Server. This ensures that any URI call matching that domain is sent to the CMS.

A Single Combined Meeting Server deployment places all CMS components (Call Bridge, Web Bridge, Database, etc.) on one server. To provide secure external access without placing the CMS directly on the internet, it must be paired with an Expressway-C/E. This model is ideal for small deployments as it minimizes server footprint and simplifies management while still providing secure firewall traversal for external participants.

The rxPacketLossLatest metric from the CMS API represents the percentage of packets lost on the receive (rx) path from the participant's endpoint to the Call Bridge. A high value indicates that the network path from the client to the server is experiencing issues, causing the Call Bridge to not receive all the media packets sent by the endpoint.

The certificate must contain the FQDN of the server hosting the service to allow clients to verify its identity. For the Call Bridge, its own resolvable FQDN is a mandatory SAN entry.

To support SIP TLS calls, the certificate on the Call Bridge must include the domain part of the meeting URIs (e.g., if spaces are [email protected], then meetings.company.com must be a SAN). This allows SIP clients to validate the server when making a call.

Cisco TMSXE is the application that integrates TMS with Microsoft Exchange. It reads meeting invitations from room mailboxes, processes them, and then uses the TMS API to push the formatted meeting information to the endpoints, which enables the 'Join' button to appear for OBTP.

Cisco Meeting Server's recorder component is designed to mount and write to a Network File System (NFS) share. This is the only officially supported network storage protocol for recording. The recorder service requires an NFSv3 or NFSv4 share to be configured for it to function correctly.

The Expressway-C (Core) resides on the internal network and establishes a secure traversal zone connection to the Expressway-E (Edge) in the DMZ. Its primary role is to act as a secure proxy, forwarding calls from internal systems like CUCM or CMS to the Expressway-E for external delivery, and vice versa.

This model, known as Single Split, perfectly aligns with the security requirements. The core components (Call Bridge, Database) are on the trusted internal network. The component handling direct external traffic (Web Bridge for WebRTC) is on a separate CMS instance in the DMZ. This isolates external traffic and adheres to the policy of no inbound initiated connections. Placing the Recorder internally allows it to access the internal SAN securely. An Expressway pair would also be required for B2B calls.

Cisco Meeting Server stores its detailed log files, including those for the Call Bridge, in its local file system. The primary method for accessing these files is to use a secure file transfer protocol (SFTP) client to connect to the server's management IP address and download the required log bundles.