monitoring
61 posts.
Watching your dialer's uptime on the status page
VICIfast provides a public status page powered by BetterStack plus a real-time health model that tracks whether your dialer is HEALTHY, DEGRADED, or UNREACHABLE — separately from your billing status.
Read postWhat the 8162 roaming-monitor extension does
The 8162 extension lets you blind-monitor one agent after another on the same VICIdial server without hanging up your phone between listens.
Read postHow to jump between agents without hanging up
Using the 8162 roaming-monitor line you can move from one VICIdial agent to the next by pressing a single digit, with no redial in between.
Read postWhen to blind monitor versus barge in
Blind monitor when you want to listen unnoticed, barge in when you need to talk. Here is a simple rule for picking the right VICIdial phone code.
Read postHow to barge into an agent's live call from your phone
Dial the agent's full session ID on a VICIdial-attached phone to join a live call and speak to both the agent and the customer.
Read postWhat manager barge-in does on a VICIdial call
Manager barge-in lets a supervisor enter a live agent-customer call and speak to both parties, signalled by an entry tone everyone hears.
Read postA supervisor's live-listen workflow over the phone
A repeatable phone workflow for supervisors: pull session IDs, silently sweep agents through 8162, and barge only when a call needs you.
Read postWhat the barge-in entry tone tells the agent and customer
The entry tone is the audible cue both parties hear when a manager barges into a VICIdial call, signalling a third person has joined.
Read postHow cross-server monitor shortcuts work on multi-server setups
On a multi-server VICIdial cluster, an admin can wire shortcut numbers so you can monitor agents on any server from one phone. Here's the idea.
Read postHow to whisper-coach an agent without the customer hearing
True whisper-coaching, where only your agent hears you, is a web monitoring feature, not a phone dial-code. Here is the honest workflow for both.
Read postHow to keep your monitor and barge feature codes secure
VICIdial's monitor and barge phone codes are unauthenticated on the telephony side. Here's how to keep strangers from dialing into your live calls.
Read postThe VICIdial monitor and barge dial codes, explained
Every VICIdial monitor and barge phone code in one place: silent listen, roaming monitor, barge-in, and the roaming barge variant. Copy and keep.
Read postVICIdial Phone-Based Functions: The Complete Guide
A full tour of the things you can do from a phone wired into VICIdial: recording audio prompts, blind monitoring agents, roaming between sessions, and barging in.
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 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 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 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 postWhat 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 postVICIdial 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.
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 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 postWhen live monitoring connects but you can't hear the call
Monitoring shows connected but the manager hears nothing. The Real-Time Monitoring Log confirms the session happened; no audio almost always means phone, conf, or codec.
Read postHow to add a custom report to the Reports page
VICIdial lets you bolt your own reports onto the REPORTS page. Here is where the Custom Report Admin page lives and how to add one.
Read postHow to use the Asterisk Debug Page to check SIP peers and registry
The Asterisk Debug Page surfaces live SIP peers, registry status, and the last 1000 CLI lines so you can confirm a trunk is registered without SSH.
Read postHow to read the Agent Latency Report when the agent screen feels slow
The Agent Latency Report charts the web-connection latency of logged-in agents over a day. Here's how to read it when the screen feels sluggish.
Read postHow to read the LAGGED Summary Report and spot lag clusters over time
The LAGGED Summary Report charts agent lag events on a timeline so you can see clusters instead of single stutters. Here's how to read the pattern.
Read postTEXT vs HTML report format: which to pick
VICIdial reports come in TEXT and HTML formats. Here is the practical difference and when to pick each, plus where to set your default.
Read postHow to run a report against archived data
Older VICIdial call data moves to archive tables. Use the Search archived data checkbox to run a report against it without digging through SQL.
Read postHow to read the URL Log Report to debug webhook and webform calls
The URL Log Report records every URL VICIdial requested — dispo call URLs and WEBFORM clicks. Here's how to read it to find why a webhook or webform failed.
Read postHow to read the Agent LAGGED Report to find which dialer is struggling
The Agent LAGGED Report pins lag to a specific dialer and lists every lagged event by user, campaign, and time. Here's how to read both halves.
Read postHow to read the SIP Event Report and spot false answers
The SIP Event Report sorts SIP messages by ring-time and other criteria. Here is how to enable it and use it to catch false answer supervision.
Read postHow to read the Agent Parked Call Report to see hold-time drops
The Agent Parked Call Report shows parked calls by agent and timeframe for one day, the average time on hold, and how many callers dropped while waiting.
Read postHow to read the Latency Gaps Report and what a gap actually means
A latency gap is a missing stretch of latency log entries while an agent was supposed to be logged in. Here's how the Latency Gaps Report reveals session trouble.
Read postHow to read the API Log Report when an integration stops working
The API Log Report shows API entries for a date and time range, filterable by API User, Agent User, Function, and Result, so you can find why an integration broke.
Read postHow to read the Real-Time Monitoring Log Report to see who listened in
The Real-Time Monitoring Log Report shows which manager monitored which agent, when, for how long, and what kind of session it was.
Read postThe VICIdial troubleshooting playbook: where to start when something breaks
A symptom-first guide that routes you from what's broken — dead dials, false answers, slow agent screens, drops on hold — to the exact VICIdial report that holds the answer.
Read postHow to read the Agent Debug Log Report to trace one agent's session
The Agent Debug Log Report records nearly every button click and back-end call for one agent session, so you can replay exactly what their screen did.
Read postHow to Read the VICIdial Real-Time Main Report
A guided walk through the VICIdial Real-Time Main Report, from the top stat block down to the color-coded agent rows.
Read postHow to Change the Real-Time Report Display Options
The Choose Report Display Options panel in VICIdial: refresh rate, inbound NO/YES/ONLY, campaign and user-group selectors, and the extra toggles.
Read postWhat the VICIdial Real-Time Agent Colors Mean
Yellow, blue, white, purple, black: the agent state colors on the VICIdial Real-Time Main Report and why they darken over time.
Read postThe complete guide to VICIdial reports and what each tells you
A tour of every VICIdial report family — the Real-Time Main Report, All Campaigns Summary, the Whiteboard wallboard, and the deeper summary and export reports.
Read post