To use call analytics, you start by creating a configuration, a static structure that holds the information needed to create a call analytics pipeline. You can use the Amazon Chime SDK console to create a configuration, or call the CreateMediaInsightsPipelineConfiguration API.
A call analytics configuration includes details about audio processors, such as recording, voice analytics, or Amazon Transcribe. It also includes insight destinations and alert event configurations. Optionally, you can save your call data to an Amazon S3 bucket for further analysis.
However, configurations do not include specific audio sources. That allows you reuse the configuration across multiple call analytics workflows. For example, you can use the same call analytics configuration with different Voice Connectors or across different Amazon Kinesis Video Stream (KVS) sources.
You use the configurations to create pipelines when SIP calls occur through a Voice Connector, or when new media is sent to an Amazon Kinesis Video Stream (KVS). The pipelines, in turn, process the media according to the specifications in the configuration.
You can stop a pipeline programmatically at any time. Pipelines also stop processing media when a Voice Connector call ends. In addition, you can pause a pipeline. Doing so disables calls to the underlying Amazon machine learning services and resumes them when desired. However, call recording runs while you pause a pipeline.
The following sections explain the prerequisites for creating a call analytics configuration, and how to create one.
Topics
For more information about call analytics configurations, refer to Managing call analytics in the Amazon Chime SDK Administrator Guide.
For more information about using call analytics configurations to enable different workflows, refer to Using call analytics configurations for the Amazon Chime SDK, later in this section.
