Where to look first

Before diving into one symptom, three screens answer most of "is something actually broken, and where": System status, Active Calls, and the Calls list. This page shows what a healthy look like, so a broken one stands out.

1. System status

Open Overview > Dashboard in the sidebar and look for Status, or go straight to it — it is the page a support call usually starts with. It checks the database, Asterisk (the phone system underneath), the connection between them, the web pages, and disk space, and shows one line per service with a green or red dot.

System status page showing a green "All systems running" banner, a list of services (PostgreSQL, Asterisk, Nginx, fail2ban, Firewall timer, GeoIP timer, Web interface process, Background service process) each with a green dot and a Restart button, and Connection checks below. — System status: every service at a glance, each with its own Restart button.

The banner at the top reads All systems running, System running with warnings, or There are problems. Below it, the Services panel lists each background service with a Restart button next to it, and Connection checks shows whether the web app can actually reach the database and Asterisk's control interface (AMI) — a service can show "active" and still be unable to talk to the database, which is exactly what this second panel is for. Reboot survival confirms every service is set to start again on its own after a server reboot.

Field	Meaning
`PostgreSQL (database)`	Where every user, call, rate and invoice is stored. If this is down, almost everything else is too.
`Asterisk (PBX)`	The phone system itself — the process that actually places and connects calls.
`fail2ban (brute-force protection)`	Watches for repeated bad login/registration attempts and blocks the source IP. See A phone does not register if a real device gets caught by this.
`Firewall timer (IP blocks)`	Removes a fail2ban block again once its time is up.
`Web interface process` / `Background service process`	The two halves of the product itself: the pages you click through, and the process that watches calls, billing and schedules behind the scenes.

Restarting a service here is a real action, not a diagnostic — do it only when the status genuinely calls for it, and know that active calls on Asterisk can be affected by an Asterisk restart.

2. Active Calls

Open Overview > Active Calls. This is the calls happening right now, updating live without reloading the page — the fastest way to answer "is anything even going through at all" during a live incident.

Active Calls page with tiles for Active Calls, Connected, Ringing, CPS, Peak CPS and Peak Calls, filters for User, Device, Status, Country, Provider, DID, Source and To, and a live table currently showing "No active calls". — Active Calls: live tiles at the top, a live table below, filterable by user, device, provider and more.

The tiles at the top (Active Calls, Connected, Ringing, CPS) tell you at a glance whether calls are moving at all. If Active Calls stays at zero while a customer insists they're dialling, the problem is upstream of Asterisk even seeing the attempt — check registration next. If calls show as Ringing but never become Connected, that points at the far end (the destination or the provider), not at the phone.

3. Calls list

Open Overview > Calls for everything that already happened — filter by date, source/destination number, status, hangup cause, user, device or provider. This is where a single reported problem call gets found and opened for detail.

Calls list filtered to one device, showing columns Date, Direction, User, Device, From, To, Destination, Status, Hangup Cause, Attempts and Provider, with rows for ANSWERED and NO ANSWER calls. — The Calls list: filter down to the one call in question, then open it for the full picture.

The Status and Hangup Cause columns are the two that matter most for troubleshooting — see A call fails for how to read them. Clicking a row opens the call's full detail page, covered in the same section and in Call details.

Other places worth a glance

Situation	Where
An e-mail or SMS alert already arrived	Read what it actually says first — Alerts in the sidebar shows the rule that fired and why, so you don't have to re-diagnose from scratch.
Something looks wrong on a specific device or provider	Open it directly — every device and every registering provider carries its own live Registration status card. See A phone does not register and A provider is down.
A whole class of calls looks off (not just one)	Statistics > Hangup causes shows the distribution of every hangup code over a date range — useful for spotting a pattern rather than a one-off. See Statistics.

Note

System status also names a command-line helper (voiplix-doctor) for deeper checks and fixes. That one runs on the server itself and is a job for whoever has technical/SSH access — not something to run from the web pages. If the screens above don't explain what you're seeing, that's the point to hand it off.

Check

Between these three pages you can usually tell, within a minute, whether a problem is system-wide (System status shows red), currently happening (Active Calls), or already over and needs a specific call looked up (Calls list).