Back to All Scenarios
PASSEDvoip / call_recording_compliance_failure
Call Recording Compliance Failure — Regulatory Risk
The call recording system stops capturing calls after the recording storage volume fills up. The VoIP system continues functioning but no calls are being recorded, putting the organization in violation of regulatory compliance requirements (HIPAA/PCI). The failure went undetected for 48 hours.
Pattern
VOIP_QUALITY
Severity
CRITICAL
Confidence
85%
Remediation
Remote Hands
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | VOIP_QUALITY | VOIP_QUALITY | |
| Severity Assessment | CRITICAL | CRITICAL | |
| Incident Correlation | Yes | 23 linked | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Remote Hands — Corax contacts on-site support via call, email, or API |
Scenario Conditions
NICE/Verint call recording system. Storage volume: 100% full (10TB NAS). Recording service silently stopped writing new files. VoIP calls continuing normally but unrecorded. Compliance requirement: 100% call recording for support center. 48 hours of unrecorded calls.
Injected Error Messages (2)
Call recording system failure — voip call recording service stopped writing to storage, recording server rec-01 disk write errors, voip compliance recording offline for 48 hours, 2,400 calls unrecorded, regulatory compliance violation (HIPAA/PCI), recording daemon running but silently failing
Recording NAS storage full — 10TB volume at 100% capacity, voip recording write operations failing with ENOSPC, oldest recordings not auto-purging (retention policy misconfigured), NAS alerting disabled during last maintenance window
Neural Engine Root Cause Analysis
The call recording server rec-01 is experiencing disk write errors that are causing the VoIP recording service to silently fail while appearing to run normally. The daemon process is running but cannot write recordings to storage, resulting in 48 hours of unrecorded calls and regulatory compliance violations. This appears to be a storage subsystem failure rather than an application-level issue, likely caused by disk corruption, filesystem errors, or storage hardware failure.
Remediation Plan
1. Immediately check disk health and filesystem status on rec-01 server 2. Verify storage mount points and disk space availability 3. Review system logs for I/O errors and storage subsystem failures 4. If disk corruption is found, run filesystem check/repair utilities 5. Consider failover to backup recording server if available 6. Restart recording service after storage issues are resolved 7. Verify recording functionality with test calls 8. Document compliance gap and notify regulatory team
Tested: 2026-03-30Monitors: 2 | Incidents: 2Test ID: cmncjsdd0048wobqe7zi6tkar