Back to All Scenarios
PASSEDserver / pbx_crash
PBX Server Crash — All Phones Unregistered
The FreePBX server crashes due to an Asterisk segfault after a problematic module update. All 150 SIP phones lose registration. IVR, voicemail, call queues, and ring groups all go offline. No redundant PBX in place.
Pattern
VOIP_QUALITY
Severity
CRITICAL
Confidence
85%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | VOIP_QUALITY | VOIP_QUALITY | |
| Severity Assessment | CRITICAL | CRITICAL | |
| Incident Correlation | Yes | 18 linked | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
FreePBX 16 / Asterisk 20. 150 Polycom VVX phones. Server crashed after 'core show channels' segfault bug. No HA pair. Last config backup: 1 week ago. PBX runs on VMware VM.
Injected Error Messages (2)
PBX server PBX-01 crashed — FreePBX Asterisk process down, SIP registration failing for all endpoints, PBX service not responding on port 5060/5061, web GUI unreachable, all call queues and IVR menus offline
All SIP phones unregistered — PBX down, 150 Polycom VVX devices showing 'Registration Failed', SIP registration receiving no response, IVR/voicemail/call queues offline, VoIP service completely unavailable
Neural Engine Root Cause Analysis
The FreePBX server has experienced a complete system failure with the core Asterisk process down, causing cascading failures across all telephony services. The simultaneous failure of multiple services (SIP registration, web GUI, call queues, and IVR) combined with 10 correlated incidents in the same time window suggests either a critical system resource exhaustion (memory/disk), underlying infrastructure failure, or a catastrophic process crash that has rendered the entire PBX system inoperable.
Remediation Plan
1. Execute immediate service restart of Asterisk and FreePBX core services 2. Verify system resources (memory, disk space, CPU) are within acceptable limits 3. Check system logs for crash dumps or error patterns 4. Validate network connectivity and port accessibility (5060/5061, 80) 5. Test SIP registration functionality post-restart 6. Monitor call queue and IVR service restoration 7. If restart fails, escalate for manual investigation of underlying system health
Tested: 2026-03-30Monitors: 2 | Incidents: 2Test ID: cmncjjr8v020jobqejv1unx2s