VICIfast
Blog

The operator's perspective.

On VICIdial, SIP, and call-center ops.

Long-form pieces by people who run dialers. TCPA changes that actually matter, the hidden cost of self-hosting VICIdial, choosing a SIP carrier without getting locked in, why provisioning time matters more than agent count. We post when we have something to say.
Read the docs

7-day free trial · Cancel anytime · Pay with card or USDT

Page 19

Operator writing, sorted newest first.

Watching 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.

OperationsRead post

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.

OperationsRead post

How 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.

OperationsRead post

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.

OperationsRead post

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.

OperationsRead post

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.

OperationsRead post

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.

OperationsRead post

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.

OperationsRead post

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.

OperationsRead post

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.

OperationsRead post

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.

OperationsRead post

How Allowed User Groups limits which records a group can see

Allowed User Groups controls which other user groups a manager can view and edit, scoping access to DIDs, phones, leads, and more by group.

OperationsRead post

What a Group Alias lets agents pick for manual-call caller ID

A Group Alias gives agents a menu of outbound caller IDs to choose from when placing manual calls and three-way calls from the agent screen.

OperationsRead post

What the Admin User Group field on a record does

The Admin User Group field on VICIdial records restricts which admins can view that record by user group, with --ALL-- meaning everyone.

OperationsRead post

How CID Group auto-rotation cycles your caller IDs

CID Group auto-rotation cycles one active caller ID at a time across your group on a timer, so no single number carries every call.

OperationsRead post

How to restrict VICIdial logins by IP with IP Lists

Lock VICIdial web access to known networks by building an IP List and assigning it to a user group's admin, agent or API access.

OperationsRead post

How to set up Admin Contacts for agent transfers

Admin Contacts give agents a searchable directory of non-agent phone numbers to transfer calls to, set up through Custom Transfer presets.

OperationsRead post

How Shift Enforcement on a user group restricts agent logins

Shift Enforcement ties agent logins to scheduled shifts so people only work the hours you set, with OFF, START, and ALL modes.

OperationsRead post

How to move every user from one group to another with Bulk Group Change

Bulk Group Change reassigns every member of one VICIdial user group to another in a single action, including a non-ADMIN sweep option.

OperationsRead post

What Queue Groups do in reports

Queue Groups bundle several campaigns and inbound groups under one ID so reports can show combined stats for a whole team or product line.

OperationsRead post

VICIdial system load explained

What the system load number on a VICIdial server actually means, how to read it against your CPU count, and when a high number is a real problem.

OperationsRead post

How 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.

OperationsRead post

What VICIdial CID Groups do and when to use them

CID Groups let you share one set of caller IDs across campaigns and rotate them by state, area code, or none-at-all auto-rotation.

OperationsRead post

What the user-group webphone overrides change

How the three user-group webphone overrides let you point one team at a different webphone URL, system key, or dialpad without touching anyone else.

OperationsRead post