VOIP RECORDING SCOPE, COVERAGE AND ACCEPTANCE WORKSHEET
Guide: https://yenra.com/voip-recording/
Updated September 7, 2026

Purpose: translate approved recording requirements into observable tests.
Complete the legal/policy section with the responsible adviser before
enabling production capture. This file prescribes no universal consent
mechanism or retention period. Use authorized participants and synthetic
test content; protect test exports and credentials.

POLICY AND REVIEW
Purpose: __________________ Included users/queues/routes: _______________
Participant locations, remote workers and transfer destinations: _________
Applicable rules and legal review reference/date: _______________________
Approved basis, notice wording/timing and consent evidence: ______________
Handling of declined consent/new participants/sensitive content: _________
Retention schedule and trigger; hold/release/deletion rules: ______________
Policy owner/version: _______________ Technical owner: _________________

PATH AND COVERAGE
Platform/recorder/releases and compatibility evidence: ___________________
Recording-client location and recording-server destination: _____________
Encryption/key owners; recording-path failure policy: ____________________
For fictional interaction R-001, define expected capture at each stage:
Queue/notice: ______________ Caller and Agent A: _________________________
Hold and consultation: _____ Agent B joins/takes over: ___________________
External transfer: _________ End point or alternate capture: _____________
Link call IDs to recording segments and participant metadata. Repeat for
required mobile, remote, conference and alternate-route cases. A successful
ordinary call establishes coverage only for that tested path.

FICTIONAL STORAGE EXERCISE (DECIMAL UNITS)
1,000 calls/day x 6 minutes/call x 60 seconds/minute x 2 channels
x 64,000 bits/second/channel / 8 bits/byte = 5,760,000,000 bytes/day.
That is 5.76 GB/day, or 172.8 GB for an illustrative 30 days of audio.
Thirty days is not a retention recommendation. Add actual container/index
overhead, transcripts, replicas, backups and growth. Measure stored files
from the chosen format; transport codec rates alone do not determine size.
Actual calls/day: ____ Minutes/call: ____ Stored format/channels: _________
Measured bytes per representative file: _____ Capacity plan: ____________

ACCESS AND LIFECYCLE
Roles permitted to search/play/export/share/delete/place holds: __________
Audit log location and review owner: ___________________________________
Audio, metadata, transcript, export and backup lifecycle mapping: ________
Key recovery procedure and owner: ______________________________________

END-TO-END ACCEPTANCE
1. Assign test ID/time zone; confirm approved notice and consent behavior.
2. Speak a harmless identifying phrase per participant; exercise coverage.
3. Search as an ordinary reviewer; play every required segment and verify
   both voices, participant changes, order and timestamps against call logs.
4. Confirm an unauthorized test account is denied. Open an approved export
   and verify that its identifier and expected content remain available.
5. In a scheduled recording-path failure test, observe approved call
   behavior, alert delivery, recovery and reconciliation of missing records.
6. Use test records to check expiry, hold/release and documented deletion
   across agreed locations. Disappearance from search is limited evidence.
Expected/actual/evidence: __________ Open issue/owner: ___________________
Acceptance decision/date: ______________________________________________

Sources: RFC 7245 architecture; RFC 7866 protocol; RFC 9806 corrects the
metadata media type to application/rs-metadata+xml. Legal source examples
and their limited U.S. scope are linked in the guide; obtain scenario-specific
review for the actual deployment.
https://www.rfc-editor.org/rfc/rfc9806.html
https://learn.microsoft.com/en-us/microsoftteams/teams-compliance-recording-setup