VICIfast Support Team
VICIfast Support
The VICIfast support team. We run managed VICIdial full-time and write these guides from the operator's chair.
Posts by VICIfast Support
Spotting LAGGED clusters on the timeline chart
The LAGGED Summary Report's timeline chart is the fastest way to see whether agent lag is random noise or a repeating pattern. This post walks through what a cluster looks like on the chart and how to pinpoint exactly when and why it happens.
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.
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 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.
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.
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.
What causes latency gaps on the agent screen
Latency gaps on the VICIdial agent screen have several distinct root causes, from agent-side network problems to server overload. Understanding which category you are in determines the correct fix and prevents the same issue from recurring.
What the Real-Time Monitoring Log Report shows
The Real-Time Monitoring Log Report gives level-9 administrators a searchable record of every monitoring session: who listened in on whom, from which server, and what the agent was doing at the time. This post explains the fields and how to use the report for oversight and compliance.
Monitoring recording storage so you never run out of disk
Call recordings are the fastest way to fill up a VICIdial server's disk. This post explains how to track storage usage, understand how quickly recordings accumulate, and set retention policies before you hit a disk-full event.
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.
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.
How to read the Agent Latency Report
The Agent Latency Report shows per-agent HTTP response times for the agent screen throughout a shift. This post explains each column and chart, what healthy numbers look like, and which patterns signal a problem worth investigating.