server-health
27 posts.
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.
Read postChecking 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.
Read postWhat 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.
Read postVICIdial 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.
Read postHow 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.
Read postThe 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.
Read postMonitoring 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.
Read postWhat peak system load tells you about your VICIdial box
Peak system load in the Server Performance Report shows the single worst run-queue depth of a shift, revealing whether your VICIdial box hit a capacity ceiling.
Read postHow 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.
Read postWhat 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.
Read postHow to turn on System Performance logging in VICIdial
System Performance logging in VICIdial must be explicitly enabled per server before any data is collected, and without it the Server Performance Report stays permanently empty.
Read postHow 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.
Read postHow 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.
Read postWhat "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.
Read postMonitoring 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.
Read postHow 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.
Read postWhat 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.
Read postThe 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.
Read postHow 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.
Read postHow 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.
Read postWhat "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.
Read postReading 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.
Read postWhat 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.
Read postHow 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.
Read postWatching server disk space from the Server Versions page
The disk-space column on the Server Versions page is your earliest warning that a VICIdial box is running out of room — and a full disk stops recordings and wedges the dialer.
Read postMonitoring VICIdial server health and capacity: a complete guide
A practical, top-to-bottom guide to watching your VICIdial server's load, channels, disk, latency, and health so problems surface before they hurt your floor.
Read postHow to read the VICIdial Server Performance Report
A plain-English walkthrough of the VICIdial Server Performance Report — what each summary stat and graph line is telling you about your box.
Read post