📄️ CDR Export
The CDR URL deals with the problem that the PBX needs to notify external servers about finished call legs. This is slightly different from the problem of informing about calls, as calls may go through different states. For example, when a call comes in on a trunk, goes to an auto attendant, then to a queue, it gets picked up by an agent and then is transferred without consultation to another agent. There is only one trunk CDR being written regardless of the various transitions that the whole call went through. This can be seen as the carriers perspective, who does not care much about what exactly happened inside the PBX; the only interest is to find out when the call started, when it got connected and when it got disconnected. The call records in the web interface of the system and the domain are different from that, as they display the whole call regardless of the call legs that were used inside the call object.
📄️ Record Locations
Recording to a file
📄️ Call Transcription (Cloud-Based)
OpenAI Whisper (Cloud-Based)
📄️ Call Transcription (Self Hosted)
On-Premises Whisper AI Deployment
📄️ Local Whisper AI Integration Example
Local Whisper AI Integration: Example Setup
📄️ Recording/CDR Settings
This page controls some basic settings for call recording and call detail record (CDR) generation.
📄️ Google (Voicemail Transcription)
Google offers a powerful API for converting speech into text. The Vodia PBX is currently using this feature to convert voicemail recordings into text format and includes that text in the voicemail notification which is typically sent to the user by email. This API must be enabled in the Google Cloud Console.
📄️ AWS Call S3 Recordings
AWS S3 Call Recordings
📄️ DigitalOcean Call Recordings
DigitalOcean Call Recordings
📄️ Wasabi Call Recordings
Overview
📄️ JSON CDR Example
The PBX sends raw JSON data. For clarity in the documentation below, our web server has formatted this data.