Specification and Requirements
This topic contains specifications and requirements for the Avaya TSAPI component only. Only specifications relevant to this integration are listed here.
Prerequisites
The following Avaya requirements must be met in order to capture metadata using Avaya TSAPI.
A CTI user must be created, more information on how to create the CTI user see Configuring CTI Users in the Avaya Documentation Center.
In general, these integration guidelines assume that:
A U‑Capture Core Services Kubernetes cluster has been deployed.
One or more Collectors have been deployed.
Each Collector has been fully configured for your telephony integration(s).
Call Metadata
The following TSAPI call metadata will be captured for each recorded call:
Answering Name
Answering Number
Call Direction
Called Name
Called Number
Caller Name
Caller Number
Other Party Name
Other Party Number
Redirection Name
Redirection Number
Station Extension
Station Name
Trunk Group Number
External Call ID (Avaya UCID)
User To User Info (UUI)
In addition to the above metadata, Avaya Aura Call Center Elite provides the following metadata:
Agent Name
Agent Login ID
Queue ID (ACD Hunt Group Extension)
Queue Name (ACD Hunt Group Name)
Firewall Port Considerations
The following ports will need to be opened (globally, not for specific processes) on any firewalls between the Collector(s) and the Avaya AES Server:
Port | Protocol | Purpose |
|---|---|---|
450 | TCP | The TSAPI Service port on the AES. |
1050-1065 | TCP | Unencrypted Tlink ports on the AES. |
1066-1081 | TCP | Encrypted Tlink ports on the AES. |
Note
The ports described above are specifically for this integration. Other ports are required for general U‑Capture Collector functionality.