There is no connector to wait for. Xperia takes recordings three ways, and the one that suits you depends on what your telephony platform can already do rather than on which integrations we have shipped.
Push: your dialer or PBX posts recordings to Xperia's authenticated API as calls complete. Pull: Xperia fetches recordings from an endpoint you configure, on a schedule. Upload: drag and drop files in the browser, many at once, with per-file results. Most production deployments use pull, because it needs no change to the phone system beyond exposing recordings.
Xperia runs today against Asterisk and Yeastar deployments, among others, over authenticated API pull. Because ingestion is platform-agnostic, anything that can expose recordings over HTTP or post them to an API will work — including in-house dialers, which a fixed connector list would exclude.
Choosing push provisions a dedicated machine credential for uploads, separate from any human login. The setup screen shows copy-pasteable requests for authenticating and sending a recording, including the supported ways to pass audio — as a URL for Xperia to fetch, or inline with the request.
Automatic ingestion is not all-or-nothing. Set the percentage of daily calls to process and a hard daily cap, so a busy dialer cannot run through your balance unexpectedly. Individual agents can carry an additional sampling percentage where you want closer monitoring — a new hire, or someone under review.
Build rules against the fields your own system sends — queue, campaign, disposition, duration, customer tier, whatever you pass through. Rules support text, number, boolean and date-time comparisons and can be enabled or disabled individually, and each records who changed it and when. A metadata inspector shows exactly what Xperia is receiving from your side, which is usually where integration debugging starts and ends.
The fetcher can be paused and resumed, shows its last execution time, and lets you rewind the point it processes from — so a backlog after an outage is a change of one timestamp rather than a support ticket.
See it working
Questions
Three ways: your system pushes recordings to Xperia's authenticated API, Xperia pulls recordings from an endpoint you configure on a schedule, or users upload files directly in the browser including many at once. Most deployments use pull, since it requires no change to the phone system beyond exposing recordings.
Yes. Xperia runs against Asterisk deployments using authenticated API pull, where Xperia fetches call recordings from an endpoint on a schedule. No Asterisk-specific module is required.
Yes. Yeastar deployments are supported over the same authenticated API pull as other platforms, with Xperia retrieving recordings from a configured endpoint.
Almost certainly. Ingestion is platform-agnostic rather than connector-based, so any system that can expose recordings over HTTP or post them to an API will work — including in-house and custom dialers.
Yes. You can set the percentage of daily calls to process and a hard daily cap, add extra sampling for individual agents, and build filter rules against your own metadata fields so only the calls matching your criteria are analysed and billed.
A metadata inspector shows the schema and values Xperia receives from your platform, in formatted or raw form, so mismatched fields can be identified without involving support.
Related
Xperia scores every call against 48 quality dimensions across 10 categories. Weightings, pass criteria and the parameters themselves are configurable per department.
Three role tiers with organisation, department or self-level data scoping, org-wide two-factor enforcement, configurable retention with automatic deletion, and file-name masking.
Every account starts with $3 of free credit — around 75 minutes of call analysis. No card required.
Start Free