Monitor RTP packet loss, jitter and round-trip delay on Asterisk, FreePBX and Issabel. See when quality changed, narrow it down to a trunk or extension, and decide what to check next.
30 days free. No card required. No audio uploads.
Illustrative example · synthetic measurements, not customer data
Packet loss over 15 minutes
Read the mean, peak and measurement count together. Averages can hide short bursts, while a single peak does not establish a sustained problem.
The receiver reports missing RTP packets for an RTCP reporting interval. Loss can coincide with gaps or broken speech.
Compare the same period across trunks and extensions. Check whether the increase is isolated or shared.
Jitter describes variation in packet arrival timing. PBXonix converts the RTCP value to milliseconds when the codec clock is known.
Check whether bursts line up with busy network periods. Compare wired and Wi-Fi paths where relevant.
RTT measures the RTCP round trip. High values can be a clue when callers struggle to take turns. It does not measure one-way voice delay.
Compare with the usual RTT for that connection. Check the network route, congestion and the scope of the change.
These are PBXonix diagnostic guide values, not universal voice-quality guarantees. Codec behavior, jitter buffers and the media path matter. Alert thresholds and duration are configured separately in settings.
Three worked examples using made-up values. They suggest a direction for investigation; they do not automatically identify a faulty device or provider.
Check the last update and RTCP measurement count. A connected agent can still be waiting for quality observations.
Use the last hour, 24 hours or seven days. Compare the complaint time with both the mean and the peak.
Filter by PBX and media direction. Compare available measurements for known trunks and internal extensions.
Review the incident timeline, assign an owner and record the checks performed. Compare the same metrics after the change.
Enable quality notifications in settings. Choose thresholds, duration and a minimum number of observations, then receive email or Telegram alerts. Review the problem and recovery in the incident centre; use maintenance mode for planned work.
The quality module uploads numerical minute aggregates and known technical endpoint identifiers. Customer phone numbers, caller names, audio, packet captures and raw SIP messages are not uploaded. The agent connects to the cloud over outbound HTTPS.
Means are weighted by RTCP observation counts, not by calls or packets. Measurements are grouped, not individual call recordings. PBXonix does not calculate MOS. Quiet charts cannot rule out codec, handset or acoustic problems.
SIP registration describes signaling availability. RTP carries the media, and RTCP reports on that media path. A trunk can remain registered while packet loss, jitter or delay affects a conversation. Check trunk state and call-quality measurements together.
PBXonix collects RTCP reporting events exposed by Asterisk. The collection path has been validated on Asterisk 16 and 20 with chan_sip and PJSIP. FreePBX and Issabel support depends on the underlying Asterisk version, event availability, monitoring permissions and media configuration.
Not every RTCP observation contains every metric. Jitter needs a known codec clock for conversion to milliseconds; RTT also depends on report contents and direction. Direct media or missing RTCP can leave the charts empty. Unavailable values are shown as missing, never as zero.
No. Each metric mean is calculated from the available RTCP observations, weighted by their count. A longer call may produce more observations. Measurement counts are not counts of unique calls, and the loss mean is not a packet-weighted loss percentage for the whole PBX.
The call-quality module sends numerical aggregates and known technical PBX endpoint identifiers. It does not upload customer phone numbers, caller names, audio, packet captures or raw SIP. You can read the Security & data page for the broader collection model.
Yes. Quality alerts can be enabled in settings, with thresholds, duration and minimum observation requirements. Email and Telegram delivery use the configured notification channels. The incident centre helps track ownership, technical comments and recovery.
Explore the monitoring tools and the data behind them.
30-day free trial · Asterisk, FreePBX and Issabel
English interface. Subtitles in your language. Demonstration data.
Explore the demo →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.
