Asterisk incident management and call quality alerts
PBXonix brings existing PBX alerts and call quality problems into one incident centre. See what happened, take ownership, add technical comments and follow recovery without hourly reminders for an unchanged problem.
One incident, from detection to recovery
The incident list shows active, unacknowledged, acknowledged and resolved problems, with PBX and alert-type filters. Each incident has a start time, duration, responsible team member, timeline and comments. Taking ownership does not close the problem: monitoring confirms recovery. Existing alert history remains available.
Quality alerts that require sustained evidence
By default, quality alerts check three consecutive completed minutes. In every minute, at least ten RTCP observations must be available for the metric, and its observation-weighted average must reach 2% packet loss, 30 ms jitter or 300 ms round-trip delay. Each PBX and media direction is evaluated separately. A short peak or a missing sample does not trigger an alert. Thresholds, duration and minimum observations can be adjusted for the organization.
Recovery confirmed by fresh measurements
The same incident stays open while the problem persists. Recovery requires fresh measurements of every metric that triggered the incident, below 80% of its threshold for the configured duration. Missing RTCP, an offline collector or an insufficient number of observations cannot be treated as restored audio quality. These network indicators do not guarantee intelligible audio and do not estimate MOS.
Email and Telegram without hourly repeats
New quality incidents use the email recipients and Telegram chats already configured in Settings, with per-channel alert-type controls. Opening and confirmed recovery each generate one notification cycle; an unchanged open incident is not sent again every hour. Delivery retries remember destinations that already accepted the message. Messages link directly to the incident.
Maintenance and related events
Pause notifications for a selected PBX for 15 minutes to 24 hours. Monitoring and incident history continue, and notifications resume automatically. If a problem opens and recovers entirely during the pause without an opening message, no unexplained recovery notification is sent. While a PBX-offline incident is open, dependent trunk, Asterisk, queue and quality notifications are grouped under it. Events close in time are shown as related observations, not proof of a common cause.
Technical context with private conversations
The quality module uses numerical RTCP aggregates already sent by the local agent. Customer phone numbers, audio, packet captures and raw SIP messages are not uploaded. Workspace members can add technical comments; the form asks them not to include customer details or passwords. Access to incidents, comments and assignments is restricted to the organization.
A closer look at your PBX
Explore the monitoring tools and the data behind them.
Keep your calls connected.
We'll help you see how.
Start monitoring for free ↗Asterisk · FreePBX · IssabelHelp me connect my PBX
Tell us your PBX type and the step you are on. Do not send passwords or access tokens.
We count aggregate page and demo events, without visitor IDs, cookies for analytics or session recordings. Browser privacy signals are respected.