Configuration Checklist

Last Updated : Jan 23, 2024 |

No.

Task

Description

Enterprise Survivable Server (ESS) configuration on Communication Manager

1.

Add a node name for ESS server on Communication Manager

Adding a node name for Enterprise Survivable Server on Communication Manager

2.

Add a Survivable Processor on Communication Manager

Adding a Survivable Processor on Communication Manager
Communication Manager/ESS configuration for Server Roles and Network Configuration on System Manager Interface (SMI) portal.
Note:

The DC1 Communication Manager is configured for Server Roles, Network Configuration, and Duplication Parameters.

Configure the DC2, DR site as follows:

3.

Configure Communication Manager/ESS server role

Configuring the server role for the Enterprise Survivable Server in DC2

Configure Communication Manager/ESS Network Configuration

Configuring ESS network

Verify status of Survivable Processor

Verifying the status of Survivable Processor

Other Communication Manager Configuration

4.

Add Computer Telephony Integration (CTI) link to DC2 Application Enablement Services

Adding a CTI link to the DC2 Application Enablement Services

5.

Configure IP-services

Configuring IP services

6.

View the ESS cluster status

Viewing Enterprise Survivable Server cluster status

Application Enablement Services Configuration - The DC1 Application Enablement Services is configured with one switch connection that connects the Application Enablement Services to the DC1 site Communication Manager. DC1 has this configuration for voice for regular operations. The switch connection has a Telephony Server Application Programming Interface (TSAPI) link which maps to CTI link 1 on the Communication Manager.

The DC2 Application Enablement Services also has one switch connection that connects it to the DC1 Communication Manager. However, on the DC2 Application Enablement Services, the ESS is added under the switch connection in Survivable Hierarchy. The DC2 Application Enablement Services can connect to both the main Communication Manager and ESS using the same CTI link. When the Communication Manager is functional, the DC2 Application Enablement Services is connected to it through the CTI link <x>, and when the Communication Manager is non-functional, the DC2 Application Enablement Services uses the Survivable Hierarchy to connect to the ESS using the same CTI link <x>.

10.

Switch connection

The switch connection name configured on the DC2 Application Enablement Services is the same as on the DC1 Application Enablement Services. This allows you to configure the Call Server Connector (CSC) attributes in Avaya Workspaces for Call Center Elite so that the CSC can connect to either Application Enablement Services. Therefore, the Application Enablement Services user for Avaya Workspaces for Call Center Elite must have the same name and password configured on each Application Enablement Services.

This switch connection has a TSAPI link which maps to CTI link <x> on the Communication Manager and has the following attributes to be configured:

  • Link

  • Switch Connection

  • Switch CTI Link Number

  • ASAI Link version

  • Security

11.

Survivability Hierarchy - Steps to add ESS in Survivability Hierarchy

Adding Enterprise Survivable Server in Survivability Hierarchy

CallServerConnector Configuration

You must configure the CSC snap-in attributes so that the CSC connects to Application Enablement Services. The CSC is configured the same in both DC1 and DC2 Avaya Workspaces for Call Center Elite, except that the DC2 CSC must be configured with two Application Enablement Services IP addresses, one for the DC1 Application Enablement Services and the second for the DC2 Application Enablement Services.

12.

Configure CSC atts (primary)

Configuring the CallServerConnector attributes for DC1

13.

Configure CSC atts (DR)

Configuring the CallServerConnector attributes for DC2