# Audio conversation data

Customer Experience Insights supports the use of audio conversation data in addition
to chat conversation data. This is facilitated through a **SIPREC endpoint**,
a protocol that you can use to establish recording sessions and report metadata.
SIPREC is a private GA feature compatible with all CCAI products.

SIPREC works in combination with
[Cloud Speech-to-Text](https://docs.cloud.google.com/speech-to-text/docs) to generate transcripts of your
audio data before it can be analyzed by CX Insights. SIPREC can
also be used in combination with [Agent Assist](https://docs.cloud.google.com/agent-assist/docs) (to provide
agent suggestions) and [Cloud Storage](https://docs.cloud.google.com/storage/docs) (to store audio data
and transcripts) depending on your business needs.

## SIPREC overview

The SIPREC protocol is used between a Session Recording Client (SRC) and a
Session Recording Server (SRS).

An SIP user agent acts as the source of the recorded metadata \& media, sending
it to the recording service endpoint. The SRC could be a personal device
(for example, SIP phone), application server, media server, an SIP media gateway
(MG), or a Session Border Controller (SBC).

SBC and PBX phone systems are common SRCs in many call centers. There are many
different SBC and PBX systems on the market that support SIPREC. Some popular
examples are listed, and many additional systems are also compatible.

- SBCs: Cisco Cube, Avaya SBCE, Oracle E-SBC, Sonus SBC, Genband SBC, MetaSwitch Perimeta.
- PBX systems: Broadworks, Metaswitch.

Each SRC solution sends the metadata contained in the SIP header (caller ID,
extension number, and so on). Different manufacturers choose different types of
metadata to send.

## Implement SIPREC

SIPREC integration usually must be custom-designed for each customer, and thus
is a lengthy process that can take up to several months. If you are interested
in implementing this feature, contact your Google representative.