U‑Capture and Avaya TSAPI
This topic provides general architecture details for the Uniphore Avaya TSAPI integration. For system deployment details specific to a customer's environment please refer to the customer's Solution Design Document from Uniphore.
Note
This topic covers the TSAPI metadata capture component only, and is designed to be used in combination with a supported U‑Capture recording integration, such as SIPREC. This in order to capture additional metadata not provided in the base integration.
The general architecture for the U‑Capture integration with Avaya TSAPI is relatively straightforward. Using this integration in combination with a supported U‑Capture recording integration, real-time call metadata events are captured via a Tlink connection to the Avaya Application Enablement Services (AES) server(s), this is in addition to the base integration’s audio and metadata captured for each recorded call.
This integration supports resiliency – in effect, this is driven by the resiliency models supported by the chosen recording deployment. Please refer to the relevant recording Guidelines topic for full details.
See Call Metadata for TSAPI specific metadata, and for metadata specific to your base integration see the relevant Integration Guidelines topic.