Technical review

Security and data architecture

Understand the standard PBXDom data path before installation: where the collector runs, which phone-system records it reads, what those records contain, and which deployment details require confirmation.

Review the data flow Ask a security question

No certification or compliance status is implied on this page.

Standard collector data flow

The exact PBX-side protocol and fields depend on the manufacturer, model, software release, and enabled CDR or SMDR output.

01
Phone system
The existing PBX produces CDR, SMDR, or another supported call-accounting output.
02
Local collector
A PBXDom collector runs on an always-on host that can reach that output. The host depends on the supported setup.
03
Hosted reporting
The collector forwards call records to PBXDom so reports, dashboards, and configured alerts can be produced.
04
Authorized users
Users open the hosted product to search records, view dashboards, and manage reports or alerts.

What the standard workflow handles

PBXDom is documented as a call-record reporting system, not a phone-system replacement or call-recording platform. The record fields available depend on what the PBX emits.

Call time, direction, duration, caller or dialed number
Extension, department, trunk, gateway, or site identifiers when supplied
Call outcome and cause fields supported by that PBX output
Calculated report, alert, and call-accounting values

Illustrative PBXDom report showing call timestamps, numbers, direction, extensions and trunks—not call audio — Illustrative demo data: inspect the timestamp, direction, extension and trunk fields. This demonstrates report metadata, not a security certification or call recording. View full-size fields →

Connection method by platform

These are brand-level summaries from the same source used by the compatibility checker. Final setup still depends on the exact model and release.

3CX

CDR output from the 3CX phone system