Avaya Call Management System Free Sample Questions

For large-scale deployments supporting 2,000 concurrent sessions and multiple ACD connections, the Enterprise Profile in the OVA deployment is required. This profile allocates sufficient vCPU (typically 8-16 cores) and RAM (32GB+) to handle the heavy JDBC and reporting load. Smaller profiles (Small/Medium) have hard limits on concurrent sessions and ACD connections that would not meet the requirement.

The data link between Communication Manager and CMS is established via TCP/IP. On the CM side, this is handled by the Processor Ethernet (PE) interface or a legacy C-LAN circuit pack. This connection transmits real-time event data which CMS buffers and processes into historical intervals.

Interval data (typically 15 or 30 minutes) consumes significantly more storage than daily, weekly, or monthly summaries because it generates 48-96 records per agent/skill per day. Extending interval retention from the default (often 31-62 days) to 2 years requires massive disk space allocation compared to daily summaries.

Standard best practice for secure CMS deployments involves using eth0 for management traffic (SSH, Supervisor clients, Web access) and a secondary interface (often eth1) dedicated to the switch link (ACD traffic) to prevent client reporting loads from impacting data collection latency.

See explanation above.

In AXP Private Cloud or when using the provided OVA appliance model, the OS is delivered as a 'black box' or appliance. While the customer initiates updates, the packages are strictly controlled and provided by Avaya via service packs (RPMS). The customer does not perform standard RHEL repository updates (yum update from public repos) as this would break the supported configuration.

The processor channel configuration requires enabling the interface and specifying the Destination Node (which maps to the CMS IP address in the node-names table). The Destination Port is typically set to 0 (default/auto) or a specific port matching the CMS configuration, and the Remote Node field must match the defined node name. This establishes the logical channel over the physical Ethernet link.

During installation, the Data Storage Allocation (DSA) must be configured to define how many ACDs, agents, and vectors the system will support. If the DSA is not run or is configured with values exceeding the installed license file (WebLM or local license), the CMS processes will fail to start or will run in a restricted mode.

The cmsadm command is the primary menu-based utility for system administration tasks such as backing up data, restoring data, setting up the system, adding/removing ACDs, and managing storage intervals. It is accessed via the root or cms user shell.

CMS on RHEL uses the System Security Services Daemon (SSSD) for LDAP integration. The configuration is primarily handled in /etc/sssd/sssd.conf and the PAM stack configuration. The CMS application relies on the underlying OS authentication mechanisms to validate users against the AD source.

Real-time data is stored in memory buffers. Historical data is created by an archiving process that moves data from these buffers to the Informix database tables at specific intervals (e.g., every 15/30 minutes). If real-time works but historical is empty, the link is up (data is arriving), but the commit to disk (archiving) is failing, possibly due to disk space issues, database locks, or a crashed archiving process.