Implementing Cisco Contact Center Enterprise Chat and Email Free Sample Questions

TCP port 7070 is the primary port used for RMI communication between the ECE Web Servers and the ECE Data Servers. This port is essential for the application's core functionality, including data retrieval and heartbeat checks. The firewall must permit traffic on this port from the web server subnet to the data server subnet.

The ECE installer automatically creates the 'Cisco_Email' Media Routing Domain within PCCE to handle the routing of email tasks.

The ECE installer automatically creates the 'Cisco_Chat' Media Routing Domain within PCCE to manage the routing of chat sessions.

For any 'Execute DB Query' activity to function, a corresponding Data Source must be configured under Administration > Library > Data Sources in the ECE console. This configuration contains the necessary JDBC driver, connection string, and credentials. If this Data Source is missing or misconfigured, the workflow engine has no information on how to connect to the external database, resulting in a connection timeout.

This statement is false. ECE simplifies the SSO configuration process by automatically generating the Service Provider (SP) metadata. Administrators can access and download this metadata XML file directly from a specific URL on the ECE Web Server. This file is then imported into the Identity Provider (like ADFS or Azure AD) to establish the trust relationship, ensuring all parameters like entityID and assertion consumer service URLs are correct.

The ECE Workflow Engine is designed for this exact purpose. A workflow can be configured with a 'Wait' or 'Timer' activity that pauses execution for a specified duration after an email enters a queue. Following the timer, conditional logic can check if the email is still in the same queue and then execute escalation activities like 'Change Queue' and 'Send Email'.

For a 400-agent High Availability deployment, the Cisco-recommended design is to collocate the ActiveMQ messaging server on the same virtual machines as the ECE Services Servers. This provides a balance of resource utilization and resilience without requiring dedicated VMs for the messaging component.

The correct location to configure data retention policies is within the specific partition's settings. By navigating to Partition > Email > Storage Management, an administrator can define separate retention periods for email activities, including how long to keep the email body and any associated attachments. This allows for granular control over database growth.

The correct and supported method is to use the ECE Administration Console (typically at the partition or system level under a 'Properties' or 'Configuration' section). Changes made here are stored in the central database. This ensures that the configuration is applied consistently across all servers in the deployment and persists through service restarts and upgrades.

The 'entryPointId' is mandatory. It tells the ECE system which chat entry point configuration to use, which in turn determines the target queue, business hours, and other routing parameters. This is how the system knows to route the request to the 'Sales' queue.

The 'author' parameter is required to identify the customer initiating the chat. This is typically set to the customer's name or a unique identifier and is displayed to the agent in the chat console.

The 'title' parameter is required and represents the initial question or subject of the chat. This text is typically the first message the agent sees from the customer, providing immediate context for the interaction.

This is the correct command syntax. dgst is the message digest command. -sha512 specifies the correct hashing algorithm used by Cisco for signing. -verify specifies the public key to use for verification. -signature points to the detached signature file. The final argument is the ISO file itself. The output 'Verified OK' confirms authenticity.