The operator's perspective.
On VICIdial, SIP, and call-center ops.
7-day free trial · Cancel anytime · Pay with card, PayPal, or USDT
Page 18
Operator writing, sorted newest first.
Server health status versus billing status: the difference
VICIfast tracks health status and billing status as two separate things. A server can be ACTIVE in billing terms while being DEGRADED or UNREACHABLE at runtime. Understanding the difference helps you troubleshoot faster.
How to set up uptime monitoring for your VICIdial server
A ping monitor is not enough for a VICIdial server. This post explains what to monitor, which endpoints reveal real dialer health, and how to wire up a tool like UptimeRobot or BetterStack to catch outages before your agents do.
How to watch disk usage on a busy dialer
Recordings, logs, and the database all grow on the same disk your VICIdial server runs on. Learn how to track disk percent-used, set retention policies, and avoid a full disk before it kills your dialer.
What the last 1000 lines of Asterisk CLI output tell you
The Asterisk Debug Page surfaces the most recent 1000 lines of CLI output alongside SIP and IAX peer status. Learn how to read these streams to spot trunk registration failures, call leg errors, and codec mismatches before they affect your agents.
Signs your VICIdial server needs more capacity
Knowing when your VICIdial box is running out of headroom before calls start dropping is the difference between proactive management and a mid-shift crisis. This post walks through the concrete signals that tell you capacity is maxed out.
How to read the Agent LAGGED Report
The Agent LAGGED Report tells you exactly which servers and agents experienced timing lag events and when. Learn how to use both sub-reports to isolate whether lag is a server-side problem or an individual agent problem.
Safe CPU and load thresholds for a VICIdial box
Knowing what load average and CPU percentages are acceptable on a VICIdial server helps you act before performance degrades. This post gives you concrete thresholds based on your core count and call volume.
How many agents can one VICIdial server handle?
There is no fixed agent limit in VICIdial — the ceiling is set by CPU, RAM, and system load. This post explains what drives agent capacity on a single box and how to read the signals that tell you you are approaching the limit.
Agent latency as a server capacity signal
Agent screen latency is not just a network complaint — rising latency values are an early sign that your VICIdial server is approaching its capacity ceiling. This post explains why latency climbs under load and how to use it as an actionable capacity signal.
What high system load actually means on a dialer
High system load on a VICIdial server does not always mean the same thing. This post explains what load average measures, why it rises, and how to tell a real call surge from a runaway process.
How to read the Asterisk Debug Page
The Asterisk Debug Page gives you SIP and IAX peer status, outbound registry state, and the last 1000 lines of Asterisk console output without requiring SSH access to the server.
How to read the Campaign Debug Page
The Campaign Debug Page surfaces the dialer's own back-end log lines for one campaign so you can see exactly why it stopped dialing, hopper-loading, or pacing correctly.
Reading your 30-day call-volume trend in Maximum System Stats
The 30-day call-volume series in Maximum System Stats lets you spot growth, seasonality, and creeping peaks before they breach your server or trunk capacity ceiling.
What off-hook minutes tells you about server usage
Off-hook minutes in the Server Performance Report counts the total time all Asterisk channels were carrying calls during a shift, making it a direct measure of server utilization and capacity headroom.
What the average channels-in-use number means
The average channels-in-use figure on the Server Performance Report tells you how many concurrent Asterisk audio paths the server carried on average across a shift.
Monitoring the Asterisk channel count on your VICIdial server
The Asterisk channel count in the Server Performance Report shows how many live audio paths are open at any moment, helping you separate real call surges from runaway processes.
What the Internal Process Logs page shows you
The Internal Process Logs page gives you a 7-day history of every back-end VICIdial process across all servers — launch counts, start times, and run durations that reveal what broke and when.
VICIdial CPU time explained: USER, SYSTEM, and IDLE percentages
The USER, SYSTEM, and IDLE percentages in VICIdial's Server Performance Report show exactly where CPU time is going and whether your box is approaching its processing limit.
The Settings Compare Utility explained
The Settings Compare Utility lets you pick two records of the same type and see every setting side by side, with differences highlighted so you know exactly what changed.
How to find a database schema mismatch between servers
When VICIdial logs show Unknown column errors or replication breaks after an upgrade, the DB Schema Compare Utility pinpoints which table or column is missing on which server.
What "most concurrent calls" tells you about your peak load
The most-concurrent-calls figures in VICIdial Maximum System Stats capture the single highest simultaneous call count reached each day, which is what actually sizes your trunks and server.
How to read the Server Performance Report graphs
The Server Performance Report graphs four metrics over time on the same axes, and reading them together is the key to diagnosing whether call problems come from hardware or software.
How to read the Server Versions page
The Server Versions page shows every server in your VICIdial cluster in one table, letting you confirm health, version alignment, and disk headroom at a glance.
Monitoring VICIdial back-end processes for restarts and hangs
Using Internal Process Logs to spot a crashing VICIdial process — high launch count with short run times means keepalive is restarting it repeatedly, which is a sign of a real fault.