- Recordings
- 414.72 GB
- Voicemail
- 0.86 GB
- Logs
- 1.4 GB
- System reserve
- 20 GB
- Local backup copies
- 0 GB
436.98 GB before allowance. Full-copy sizing assumes no compression or deduplication. Copies on this volume do not protect against its failure.
Separate the things that grow
Enter total recorded call-hours per calendar day. For example, ten calls recorded in parallel for eight hours represent 80 call-hours. Enter the combined stored-file bitrate for all channels; stereo or separate directional files can require twice the mono rate.
Voicemail has its own volume, format and retention. Logs use a measured daily size instead of an audio formula. The system reserve is an explicit input for the operating system, database and other files; this calculator does not guess a PBX product's minimum requirements.
How the model adds capacity
Recording GB = daily call-hours × file bitrate × 1,000 × 3,600 ÷ 8 ÷ 1,000,000,000 × retention days. Voicemail uses minutes × 60 in place of hours × 3,600. Log GB = daily log GB × retained days.
Primary data is recordings + voicemail + logs + system reserve. Additional local full-copy backup storage is primary data × entered copies. Planned capacity is the sum multiplied by one plus the entered allowance percentage. The model assumes no compression, deduplication or incremental-backup savings.
Validate before buying a volume
With the defaults, recordings use 414.72 GB, voicemail 0.864 GB, logs 1.4 GB and the system reserve 20 GB: 436.984 GB before allowance. Adding 25% gives 546.23 GB rounded. If you retain one additional full copy on the same volume, the model doubles the pre-allowance requirement.
Copies on the same volume do not protect against that volume failing. Plan an independently protected backup destination and test restoration. Capacity is also different from disk latency, write throughput, endurance and database behavior; those require workload measurements. Monitor growth and deletion jobs after deployment.
Watch the explanation
Separates File Store destinations from backup jobs, then covers included data, retention and archive checks. Repeatedly explains why a copy on the PBX’s own disk is insufficient.
Read applicability and editorial notes →Watch this video here
FreePBX 15 interface from 2021. Check current module and migration documentation before restoring to FreePBX 17. Review used the available transcript and primary references; audio and screen readability remain unverified.
The player loads only when you choose Watch here. Playback uses YouTube’s privacy-enhanced embed; YouTube processes playback data.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.