What PBXonix collects — and what stays on your PBX
Monitoring needs useful operational data. PBXonix separates that data from customer telephone numbers and audio: the agent removes customer numbers and caller names before transferring report records to the cloud.
What the service receives
System metrics, component states, timestamps, call durations and outcomes, and known internal extension, queue and trunk identifiers support monitoring and reports. These include individual technical report records, not only aggregated statistics. Account email addresses and display names you enter are also stored for your workspace.
What stays local
Customer phone numbers and caller names are removed before report upload. Call audio is not uploaded; recording monitoring uses counts, sizes and timestamps. SIP, AMI, database and SSH passwords are not sent to the cloud. Avoid putting customer details into display names you enter yourself.
How the agent connects
The agent runs on your PBX and opens an outbound HTTPS connection to the service. You do not need to publish AMI or forward an inbound monitoring port. Installation requires local administrator access. Your monitoring workspace requires authentication and is separate from these public product pages.
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.