Type the Host name or IP address of the primary ICM CTI server (CG component). The default is server.

Specify the connection port on the primary ICM CTI server (CG component). The ICM adapter connects to the CTI Gateway for a corresponding Peripheral Gateway. The port for this connection is defined on the CTI Gateway in the ICM configuration. The default is 42027. The default port for a secure connection is 42030.

Select the version of the protocol you are using, or leave this set to the default value of Auto for it to be automatically determined.

Select this check box if you want to use a failover server.

Specify the host name or IP address of the backup ICM CTI server (CG component). This field is required if you select the Use Secondary Server check box. The default is server2.

Specify the connection port on the backup ICM CTI server (CG component). The ICM adapter connects to the secondary CTI Gateway for a corresponding Peripheral Gateway. The port for this connection is defined on the secondary CTI Gateway in the ICM configuration. This field is required if you select the Use Secondary Server check box. The default is 43027. The default port for a secure connection is 43030.

Select this check box if you want this adapter to perform tagging only, while the switch controls recording.

This option enables the Cisco ICM adapter to process agent state changes, specifically Agent Login and Logout. The default is enabled. To process agent login events for the associated data source Third-party systems that provide data to the system, including employee and device states, and data change events. Typical data sources are phone switches, PBXs, or LANs. from a different adapter, and not this local adapter, disable this setting.

To receive ICM events only for the extensions configured in Enterprise Manager, select this check box. You must also enter a Peripheral ID, below. These two settings in conjunction are used to receive ICM events for the configured extensions.

If you enable Device Registration, above, you must also provide a Peripheral ID to be used to query configured devices. You can find this number in the ICM event in the Recorder Integration Service log file.

Example: Recorder Integration Service log file

In the following logs, BEGIN_CALL_EVENT marks the start of the ICM call, and Int<peripheralID> indicates that the Peripheral ID is 5000.

[IEMessage |0180|D] 2013/03/27 17:24:54.291 Dispatching Event CTIEvent<si.12> --> <CallTracker> Size<6>

[IEMessage |0180|H] 2013/03/27 17:24:54.291 Int<AdapterId> = 12 ; Str<AdapterName> = ICM Adapter ; Int<SwitchId> = 255 ; Str<SwitchName> = My Cisco ; Str<description> = BEGIN_CALL_EVENT

[IEMessage |0180|H] 2013/03/27 17:24:54.291 Folder<event>

[IEMessage |0180|H] 2013/03/27 17:24:54.291 Int<messageType> = 23 ; Int<monitorId> = 19 ; Int<peripheralID> = 5000 ; Shrt<peripheralType> = 17 ; Shrt<numCTIClients> = 0 ; Shrt<numNamedVariables> = 0

[IEMessage |0180|H] 2013/03/27 17:24:54.291 Shrt<numNamedArrays> = 0 ; Shrt<callType> = 6 ; Shrt<connectionDeviceIDType> = 1 ; Int<connectionCallID> = 16781293 ; Shrt<calledPartyDisposition> = 0

This option will enable the adapter to stop screen recording based on after call work events. Off by default.

Select this option if the ICM server requires authentication. Once selected, you must also enter a Client Id and Client Password, below.

If you enable authentication, type a login name used to access the ICM CTI server (CG component). This is set to ImpactRecorder by default.

If you enable authentication, click the button beside the ClientPassword to type a Password. This password must correspond to the Client Id used to access the ICM CTI server (CG component).

Select this check box to secure communications using TLS and a Keystore. You must also enter a Keystore Filename and a Keystore Password. The keystore password should be the same as your private key password.

Create a new keystore using the instructions in "Create a Java KeyStore using OpenSSL" in the Cisco Integration Guide. Type the path to the new keystore in this field.

To integrate with the UCCE, the Verint client certificate must have the following characteristics:

Key Usages:

• Digital Signature

• Key Encipherment

• Data Encipherment

Extended Key Usages:

• Client Authentication

• Server Authentication

Enter the password for the KeyStore File.