The operator's perspective.
On VICIdial, SIP, and call-center ops.
7-day free trial · Cancel anytime · Pay with card or USDT
Page 19
Operator writing, sorted newest first.
What a DEGRADED server health status means
DEGRADED means your VICIdial server is still reachable but something is wrong at runtime - high load, a dead keepalive, or a key process that is partially down. Here is what triggers it and what to do.
How to audit which managers monitored which agents
The Real-Time Monitoring Log Report records every listen-in session a manager starts - who listened, to whom, from which server, and for how long. Here is what the report contains and how to use it for compliance and accountability.
How to read the LAGGED Summary Report
The LAGGED Summary Report aggregates agent lag events into totals and a timeline chart so you can see whether lag is random or bunching at predictable times. This post explains how to read the chart and what the summary numbers tell you.
Monitoring database load on a VICIdial server
On a single-tenant VICIdial box the database and Asterisk share the same CPU, so a slow query during peak dialing can stall your entire shift. This post explains what to watch and how to spot database pressure before it affects calls.
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 Latency Gaps Report shows
The Latency Gaps Report surfaces periods where an agent's latency log goes silent while they should be logged in. These gaps are distinct from high latency - they indicate lost connectivity and are often the root cause of agents experiencing screen freezes or dropped sessions.
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.
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.
The DB Schema Compare Utility explained
The DB Schema Compare Utility checks your VICIdial database servers for schema drift by comparing tables, row counts, and column counts between the primary and any secondary server.
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.
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.
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.
What the Shared Debug Page shows for shared-agent campaigns
The Shared Debug Page exposes the agent-rotation and dialing decisions that drive shared-agent campaigns, letting you diagnose uneven pacing or campaign starvation without guessing.
How to read the Maximum System Stats report
The Maximum System Stats report shows a per-day table and bar graph for the last 30 days, tracking seven call and agent peak figures that drive capacity planning decisions.
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.
What "most concurrent agents" tells you about server sizing
The most-concurrent-agents daily peak in Maximum System Stats shows the highest number of agents logged in simultaneously, which is the figure that drives seat licensing and server headroom planning.
How to compare the settings of two campaigns side by side
Using VICIdial's Settings Compare Utility on the CAMPAIGNS type lets you see exactly which field differs between a working campaign and a broken one, without guessing.
How to check which VICIdial version each server is running
The version column on the Server Versions page lets you confirm every node in your cluster runs the same VICIdial build - a mismatch after a partial upgrade is a classic source of subtle dialer breakage.
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.
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.
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.
Checking SIP Peers and Registry from the Asterisk Debug Page
The SIP Peers and Registry section of the Asterisk Debug Page tells you whether each carrier trunk and agent phone is registered and reachable, without opening an SSH session.
What the Campaign Debug Page shows about an auto-dial campaign
The Campaign Debug Page surfaces the dialer's own back-end log lines for a chosen campaign, making it the first place to look when auto-dialing stalls or the hopper stops loading leads.