A public safety answering point records everything by default: caller audio, the dispatcher side, every radio talkgroup, the TDD channel, screen activity, and the timestamps that tie them together. Almost none of it is ever played back. The small fraction that is played back tends to be played back by a defense attorney, a state oversight body, or a reporter holding a public records request. That asymmetry is the whole design problem. Storage has to be cheap enough to hold years of unremarkable audio and rigorous enough that one call can be produced, authenticated, and defended in court. Getting NAS for emergency dispatch recording right means solving both at once.
Multi-Channel Capture Runs on a 24-Hour Clock
A mid-size PSAP with 12 call-taker positions and 30 radio talkgroups records 42 or more concurrent channels without pause. At G.711 that is roughly 64 kbps per channel; at G.729 or Opus it falls below 16 kbps. Even at the high end, 42 channels for a full year is only about 8 TB of audio. Screen recording is what changes the arithmetic: 12 positions at 1 Mbps adds 47 TB a year, and many agencies now capture it as standard practice.
Immutability Has to Be Enforced Below the Application
Recorder software marking a file read-only is not immutability. The property that matters is that no credential available to an administrator can shorten a retention lock. WORM-capable file storage with a retention timer set at write, backed by snapshots that cannot be deleted before expiry, moves the guarantee out of the application layer where an operator mistake or a compromised account can quietly undo it.
Auditors ask how the guarantee is enforced, not whether a checkbox exists. Showing the retention attribute on the volume and the failed-delete entries in the audit log is a far stronger answer than a screenshot of the recorder's settings page.
Chain of Custody Begins at the Moment of Write
Authentication in court comes down to showing that the file produced in 2031 is bit-identical to the file written in 2026. That requires a hash computed at ingest, stored separately from the media, and re-verified on a schedule. SHA-256 at write, a signed manifest, and periodic scrub results give an evidence custodian something concrete to testify to.
Access logging carries equal weight. Every read of a retained call should generate an entry with user, timestamp, and reason code. A hardened NAS storage platform that ships those events to an external syslog collector keeps the trail outside the reach of anyone who might want to edit it.
Correlating Audio With the CAD Incident Record
A call is rarely useful in isolation. The audio has to line up with the CAD incident number, the unit assignment history, and usually radio traffic on two or three talkgroups. Recorders integrate with Motorola, Hexagon, Tyler and CentralSquare CAD systems, but the storage side still has to keep the related objects retrievable together after the CAD database has been migrated twice.
Exporting a synchronized package of caller audio, dispatcher audio, radio, and CAD text for a two-hour window is a routine request. If that export costs an analyst a full day of manual assembly, the retention design has failed even though every byte is present. A NAS for emergency dispatch recording should hold those objects in one namespace under a consistent naming scheme so packaging can be scripted.
Statutory Retention Runs From 90 Days to Forever
Retention is set by state statute and agency policy, never by the vendor. Many states require 911 audio for 90 days to one year. Homicide and officer-involved-shooting material is typically held permanently. Civil liability windows push routine calls out to 3 or 7 years. The practical consequence is that a single share needs several retention classes with different clocks running side by side.
Volumes only grow under those rules. Scale-out NAS architectures that add capacity nodes without re-platforming avoid the forklift migration agencies otherwise face every four or five years, and migrations are exactly where chain of custody tends to get weakest.
Public Records Requests and Redacted Working Copies
State open-records laws force release of some call audio with caller identifiers, medical detail, and minors' names removed. Redaction produces a derivative file, and the derivative must never overwrite or stand in for the original. A separate working tier with its own quota and lifecycle keeps derivatives from silently accumulating inside the retention-locked area.
Backup Copies for a System That Cannot Lose a Day
A recorder array with local snapshots is still one site and one failure domain. Agencies that protect the recorder store off site generally use a repository model, and setting up a NAS backup repository for Veeam or an equivalent tool gives them immutable restore points with a documented recovery time.
Test the restore against a real evidentiary request, not a synthetic file. The question that matters is whether a specific call from 14 months ago can be produced with its hash intact inside the deadline written on the subpoena.
What Actually Takes Recorders Offline
Failures in PSAP recording are rarely dramatic. A certificate expires on the SIP recording trunk, a share fills because a screen-capture policy changed, or a firmware update silently drops a talkgroup. Monitoring should alert on channel-level write activity, not just array health, because an array can look perfectly healthy while three talkgroups have recorded nothing for a week.
Capacity alarms need headroom that reflects the legal obligation. NAS for emergency dispatch recording should alert at 70 percent rather than 90, because there is no lawful option to stop recording while procurement runs its course.
None of this is exotic engineering. It is retention classes mapped to statute, hashes computed at write and verified on a schedule, immutability enforced by the storage rather than the application, and a second copy that has actually been restored from at least once. StoneFly and other vendors build systems that do these things. The part no vendor can supply is the agency's own decision about what each record class is worth and how long it has to survive.
Top comments (0)