The operator's perspective.
On VICIdial, SIP, and call-center ops.
7-day free trial · Cancel anytime · Pay with card or USDT
Page 40
Operator writing, sorted newest first.
How to read the User Group Login Report to confirm where an agent logged in
Use the User Group Login Report to confirm an agent's most recent login: campaign, server IP, computer IP, extension, and phone login.
Calls placed but not connecting: a first-things-to-check guide
Calls dial out but never reach a person? Read the per-attempt SIP response codes in the Dial Log and Carrier Log reports to find the cause.
Diagnosing carrier rejects: reading the codes your provider sends back
Use the Hangup Cause and Carrier Log reports to read your carrier's rejection codes, filter to a specific cause, and decide what to change.
What CHANUNAVAILABLE means and why it's usually a line-count problem
CHANUNAVAILABLE means the dialer ran out of lines before it could hand the call to the carrier. It's a local capacity limit, not a carrier reject.
How to read the AMD Log Report when answering-machine detection looks wrong
The AMD Log Report shows the result of answering-machine detection on each placed call. Here is how to read it and tell real misfires from carrier noise.
How VICIdial decides a call counts as a sale
VICIdial counts a call as a sale based on one setting on the call status: the Sale attribute. Here is how it works and where it shows up in reports.
TEXT 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.
How 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.
How 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.
How 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.
How to read the Dial Log Report and what the SIP codes mean
The Dial Log Report groups every placed call by its SIP response code. Here is how to read each column and turn a wall of codes into a real diagnosis.
How 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.
What sales-per-hour means and how VICIdial computes it
Sales-per-hour in VICIdial is sales divided by talk time, but one report divides by system time instead. Here is how to read both.
How 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.
What first-call resolution is and how VICIdial computes it
First-call resolution in VICIdial is calls handled divided by leads handled. Here is where the column lives and how to read it.
How 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.
How 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.
How 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.
The 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.
How 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.
How 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.
How to read the Caller ID Log Report to see which CIDs you've burned
The Caller ID Log Report breaks calls down by the caller IDs a campaign used, so you can see which numbers are burned and rotate them before they go spammy.
Human answered vs customer contact: what the difference means in reports
VICIdial reports lean on two status flags: human answered and customer contact. They sound similar but measure different things. Here is the difference.
How 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.