VoIP.infoThe independent guide to business communications.
VoIP.info Guide

Planning business call recording

Decide purpose, access, storage and retention before enabling recording across every call.

Reviewed 2026-10-17Foundational

Start with the business requirement

Recording can support a defined operational purpose, but it creates stored conversation data and additional administration. Decide which calls need recording, who may retrieve them and how long they are retained. Avoid enabling universal recording merely because the platform offers it.

Confirm the applicable obligations

Consent, notice, employment and retention requirements vary by jurisdiction and context. Obtain advice appropriate to the business and configure the required notice process. This planning guide does not determine the legal basis for recording a particular call.

Model storage and recovery

Estimate volume from actual recorded duration and chosen format, then validate growth during a pilot. Confirm whether recording files are included in backups and who controls exported copies. A recording link in a call report can outlive the underlying file.

Test the complete workflow

Check incoming, outgoing, transferred and conference calls according to the intended policy. Verify that authorized users can retrieve the correct file and unauthorized users cannot. Include storage alerts, deletion and recovery in acceptance. Recording increases the PBX workload and should be part of capacity validation.

Applying the reference

The Sangoma reference explains PBX feature concepts; some screenshots and interface instructions describe older releases. This planning guide does not rely on those screenshots as a FreePBX 17 setup procedure. Confirm the installed module and current provider feature behavior before rollout.

Treat TelVox recording configuration as intent, not evidence

The TelVox Connect provider record keeps a dual-channel or number-level recording setting separate from consent, call scope, recording state, retrieval, decoded content, retention and legal authorization.

Keep external control outside consent and retention proof

An accepted AMI MixMonitor action or stop event is not lawful-capture, audio-quality or retention evidence. The Asterisk guide preserves those boundaries.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Continue your research

Guide

Plan a business phone system

Turn staff workflows and continuity needs into a testable brief for hosted or self-managed VoIP.

Read guide →
Hub

FreePBX

Plan and administer a FreePBX 17 system on Debian 12 using the supported project installation path.

Explore topic →
Interactive tool

Concurrent call planning calculator

Turn an explicit simultaneous-use assumption into a rounded-up external-call scenario.

Open tool →
Provider research · Current TelVox Connect trunk, authentication, call, number, recording, webhook, pricing and security documentation plus Renav Limited company identification reviewed October 16, 2026; Connect is live but its API is v0.x, and coverage, portability, emergency calling, fax, messaging, codecs, DTMF transport, RTP, media protection, redundancy, concurrency, call-start limits, availability, compatibility, exact pricing and support performance remain account, order, route or version specific; no account, API key, trunk, SIP credential, number, registration, webhook, callback, recording, packet, media stream, emergency call or live call was inspected or tested

TelVox Connect SIP trunks: provisioning, credentials and call evidence

Separate TelVox API access, trunk lifecycle, SIP registration, webhooks, callbacks and call outcomes while keeping pre-v1 and account-specific limits explicit.

Read guide →
Guide · Current branch-23-generated and branch-22 AMI MixMonitor, MixMonitorMute and StopMixMonitor action references, current MixMonitorStart, MixMonitorMute and MixMonitorStop event references, and current dialplan MixMonitor and StopMixMonitor references reviewed October 17, 2026; AMI request, action response, channel-bound audiohook, start or mute or stop event, filename, open file handle, durable file, decoded audio, retention and caller outcome remain separate evidence boundaries; installed branch, loaded app_mixmonitor module, manager permissions, event filters, channel lifetime, storage, legal basis and generated FreePBX dialplan remain deployment specific; no PBX, module, manager account, credential, session, channel, audiohook, event stream, file, packet, media stream, recording or live call was inspected or tested

Asterisk AMI MixMonitor controls and recording-event evidence

Separate AMI recording requests, channel-scoped audiohooks, start, mute and stop events, file-handle release, stored files, decoded audio and retention outcomes.

Read guide →
Troubleshooting · Current branch-23-generated and branch-22 AMI MixMonitor, MixMonitorMute and StopMixMonitor action references, current MixMonitorStart, MixMonitorMute and MixMonitorStop event references, and current dialplan MixMonitor and StopMixMonitor references reviewed October 17, 2026; AMI request, action response, channel-bound audiohook, start or mute or stop event, filename, open file handle, durable file, decoded audio, retention and caller outcome remain separate evidence boundaries; installed branch, loaded app_mixmonitor module, manager permissions, event filters, channel lifetime, storage, legal basis and generated FreePBX dialplan remain deployment specific; no PBX, module, manager account, credential, session, channel, audiohook, event stream, file, packet, media stream, recording or live call was inspected or tested

Asterisk AMI MixMonitor starts but the recording is missing, empty or wrong

Trace one disputed AMI recording through channel identity, action response, start and stop events, options, path, file-handle release, storage, decoding, transfer boundaries and retention.

Read guide →