PBXDom reads call data from Asterisk through the Asterisk Manager Interface (AMI), the same TCP interface that operator panels and wallboards use. There are two collector options. The original Windows collector connects to AMI over the network on port 5038 and streams call events to the cloud as they happen; the setup is documented step by step in How to Create an Asterisk Server Dashboard in 10 Minutes. The newer Linux collector installs directly on the Asterisk server with a single shell command, runs as a daemon, and writes the required manager and CDR configuration for you. It also discovers SIP, PJSIP, and IAX extensions along with your trunks automatically, then keeps that inventory in sync as you add endpoints — the part of a manual setup that most often goes wrong. The FreePBX dashboard guide walks through the Linux install in detail.

Once the collector is registered, the event stream becomes live dashboards: call volume by hour, abandoned and missed calls, extension and trunk activity, and per-agent answer performance. Historical reports cover the same data over any date range and can be scheduled for email delivery, and alert rules notify you the moment someone dials 911 or another emergency number from any extension. If you run several Asterisk servers — or Asterisk alongside another vendor’s PBX — all of them report into a single account, so multi-site call traffic lands on one dashboard.

Coverage spans the whole Asterisk family: plain Asterisk servers, FreePBX (including the SNG7 distributions, tested with Asterisk 11 through 16), Issabel, and older Elastix installations. The Linux collector requires a 64-bit OS; for 32-bit or legacy systems, the Windows collector over AMI remains the fallback. Check the exact Asterisk system, then choose guided or self-setup for the 14-day trial.