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, PayPal, or USDT

Page 19

Operator writing, sorted newest first.

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

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.

OperationsRead post

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.

OperationsRead post

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.

OperationsRead post

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.

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

OperationsRead post

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.

OperationsRead post

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.

OperationsRead post

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

OperationsRead post

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

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

What VM Message Groups give agents on a voicemail drop

VM Message Groups let agents pick from a ranked, time-aware list of pre-recorded messages to leave when transferring a call to voicemail.

OperationsRead post

What the system-wide IP blacklist blocks

VICIdial's system-wide IP blacklist blocks every web service for any user coming from a listed address, regardless of their user group.

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 Admin Changes audit on a user record

The Admin Changes section on a VICIdial user record logs who changed a setting, from which IP, what changed and when, giving you a per-user audit trail.

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

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

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

How IP Lists scope admin, agent and API access per user group

VICIdial gives every user group three independent IP whitelists for admin, agent and API access, so you can lock each surface to its own set of networks.

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

How Allowed Queue Groups scopes report visibility for a group

Allowed Queue Groups limits which queue groups a user group can see inside queue-based reports, keeping managers focused on their own queues.

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