Call Recording
SIP.IO records calls under a policy you control, ships the audio off the node, transcodes it to Opus, and serves it back only through an audited API, with a mid-call pause/resume control for card-sensitive segments. Every recording is one row you can list, play, download, or delete; every access to that audio is logged.
What you can do
- Set recording policy, not per-call flags. Rules scope to account, user, queue, or DID, with more specific scopes winning over an account-wide default.
- Record by direction. Inbound/outbound PSTN, internal extension-to-extension calls, or queue calls, independently.
- Pause and resume mid-call. Stop capture before a card number is read, resume after, into the same recording.
- Control retention. Every recording is stored free for 30 days; extend retention beyond that, up to 7 years, for a small storage add-on, priced below what the large CCaaS suites charge for the same thing. See Pricing.
- Get stereo output. Split agent and caller onto separate channels for downstream transcription or QA.
- Play, download, and delete over an audited API. No presigned links; every access is logged.
- Turn a recording into a searchable transcript and AI summary. See Call Transcription & AI Summarization.
Capability table
| Capability | Docs |
|---|---|
Recording policy (recording_rule: scope, direction, mode) | Call Recording docs |
| Pipeline: record → spool → ingest → transcode → serve | Call Recording docs |
| Mid-call pause/resume/stop/start | Call Recording docs |
| Retention control | Call Recording docs |
/v1/recordings list/get/play/download/delete | Call Recording docs |
Access logging (recording_access_log) | Call Recording docs |
| API authentication & scopes | API Authentication |
Built for compliance-minded teams
Recording is part of the cloud contact center, and it’s built the way a compliance-conscious team wants it: policy-driven instead of ad hoc, a full pipeline from capture to archive, and an access log written on every view, play, download, and delete, the same kind of trail HIPAA/SOC2-style audits ask for. See Trust for SIP.IO’s current certifications.
FAQ
How does SIP.IO decide which calls to record? A recording_rule policy table, scoped to account, user, queue, or DID (more specific scopes win), and set per call direction.
Can I pause recording before a caller reads out a card number? Yes, via POST /v1/calls/{callId}/recording with pause and resume, restarting into the same file.
Can I download or stream a recording directly from storage? No. Every play, download, and delete goes through the /v1/recordings API, never a presigned URL, and is written to an access log.