When a call is bad, support finally gets the right data
Audio problems are difficult to explain and even more difficult to reproduce. MaxiPBX collects useful metrics on the application side, links them to the PBX and gives support an exploitable call trace.
Diagnosis triggered by the user
From the application, the user can start a collection, make test calls, stop the collection and send the report to support.
- Clear states in the application: starting, active collection, stopping and sending
- WebRTC metrics: packet loss, jitter, latency, approximate MOS and codec
- Version information, platform, audio devices and call events
- Secrets and sensitive identifiers excluded or masked before sending
PBX escalation then ControlPlane
The PBX enriches the diagnosis with its context before transmitting it to the support portal.
- Tenant, user, collection period and sampled calls
- Quality summary, severity and downloadable artifacts
- Sessions strictly compartmentalized by customer and tenant
- Support Diagnostics page to filter, open and analyze sessions
Call trace from the CDR log
A call must retain minimal information permanently visible: direction, status, duration, source, destination, start and end.
- Call summary available even without historical PCAP
- Visual timeline of the call path
- Correlation link to collected diagnostics
- Telephony events and related artifacts when available
Network captures on demand
When reproducing a problem is needed, the administrator can trigger a short or long SIP/RTP capture as required.
- Configurable captures: a few minutes, one hour, six hours or twenty-four hours
- Triggering from PBX admin or from ControlPlane
- Authenticated download and capture status visible
- Capture « from now on », without promising to reconstruct a past call
Gereelde vrae
Does MaxiPBX record all calls in PCAP?
No. A network capture is triggered when you want to diagnose a problem. However, the call log retains essential call information.
Does a user see that the diagnosis is running?
Yes, the application must clearly display the diagnosis status: starting, active collection, stopping and sending to support.
Do diagnostics contain passwords?
No. Secrets, tokens and sensitive identifiers are excluded or masked before transmission.
A recurring audio problem at a customer?
We start a clean collection, reproduce the problem and support receives the elements needed to analyze it.