Back to All Scenarios
PASSEDvoip / pbx_service
Asterisk PBX Service Crashed — Calls Dropping
The Asterisk PBX service crashed due to a segfault in a channel driver. All active calls dropped and no new calls can be placed.
Pattern
PROCESS_CRASH_LOOP
Expected: VOIP_SERVICE_CRASH
Severity
HIGH
Confidence
72%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | VOIP_SERVICE_CRASH | PROCESS_CRASH_LOOP | |
| Severity Assessment | CRITICAL | HIGH | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
Ubuntu 22.04. Asterisk 20. 50 extensions. Crash in chan_pjsip module. All 15 active calls dropped. Service not auto-restarting.
Injected Error Messages (1)
Asterisk PBX crash — segfault in chan_pjsip module, service stopped, 15 active calls dropped, 50 extensions unreachable, SIP registrations lost, no auto-restart configured
Neural Engine Root Cause Analysis
Process crash loop detected — a service is repeatedly crashing and restarting, failing to reach a stable running state. This indicates a persistent issue such as a missing dependency, corrupted configuration, incompatible library version, memory corruption, or an unhandled exception that occurs during startup. In Kubernetes environments, this manifests as CrashLoopBackOff with exponentially increasing restart delays.
Remediation Plan
1. Check service logs immediately before each crash for the error message or stack trace.
2. Look for core dumps in /var/crash/ or the configured core dump location.
3. Verify all dependencies (config files, environment variables, database connectivity) are available.
4. Roll back to the last known working version if the crash started after a deployment.
5. For segfaults, check for library version mismatches or corrupted binaries — reinstall the package.
Improvements Applied
- Pattern classified as PROCESS_CRASH_LOOP (expected VOIP_SERVICE_CRASH)
- Severity: HIGH (expected CRITICAL)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnoopv002clig78wvx24f5