Call Data & Observability
Call Data & Observability
In production, voice calls need observability: you want to answer questions like:
- Did the call connect?
- What number was dialed? What trunk was used?
- How long did the call last?
- What did the agent and user say?
- Can we review the audio later?
SIPHON supports these through call data features managed by the agent worker.
What can be saved
- Recordings (audio files)
- Metadata (structured summary: numbers, trunks, timing, status)
- Transcriptions (conversation history)
When call data is persisted
Call data is captured during the call and typically persisted when the call ends.
- Recordings start shortly after the agent joins the room.
- Metadata/transcription are saved during the exit path (and can also be saved when ending a call early).
Where call data can be stored
SIPHON’s storage layer supports:
- local filesystem folders
- S3-compatible object storage
- database backends (via URL-style configuration)
This flexibility allows:
- a simple local dev setup
- an S3-based production pipeline
- integration with existing DB infrastructure
Practical configuration
This page is conceptual.
For the exact env vars, backends, and examples, see: