VICIdial error reference
25 errors you will eventually hit running VICIdial in production. Each entry: what the symptoms look like, what usually causes it, how to fix it, and how VICIPanel surfaces the issue before it impacts agents.
Critical severity
Critical — dialing stops
When these hit, agents can't take calls and dialing halts. Fix immediately.
Agent screen blank or stuck on loading
Agent logs in but sees a blank agent interface or a spinner that never resolves.
Asterisk not running on the dialer box
The Asterisk process is dead, no calls can be placed or received until it's restarted.
One-way audio on connected calls
Agents can hear callers but callers can't hear agents, or vice versa.
Campaign dial level stuck at zero
Campaign auto-dial level drops to 0 and never recovers, dialing stops.
Carrier trunk at capacity
Outbound calls fail because your SIP trunk has hit the carrier's concurrent channel limit.
Database connection lost
VICIdial cannot reach MySQL/MariaDB, everything stops.
Dial prefix invalid for campaign
Campaign is configured with a dial prefix that doesn't match any Asterisk dialplan extension, every dial fails instantly.
Hopper empty, dialing paused
The pre-dial lead cache is empty and the fill cron hasn't run, dialing stops until new leads enter the hopper.
Lead list not loading to hopper
Imported list exists but leads never appear in the hopper for dialing.
Phone login not active, agent cannot take calls
Agent logged in but their phone endpoint didn't register, no audio path, no calls route.
SIP trunk registration failed
Your SIP trunk is not registered with the carrier, no outbound calls can be placed.
VICIdial worker process not running
One of VICIdial's background daemons (AST_send_listen, AST_update, etc.) has died.
WebRTC softphone connection failed
Agent's browser-based softphone fails to establish audio path.
Medium severity
Medium — degraded operation
These don't stop dialing, but they cost you productivity, contact rate, or data quality.
Agent kick-all command errors out
Supervisor 'kick all agents' function errors instead of logging agents out.
AMD timeout, call routed before detection completed
Answering machine detection didn't finish in the allowed window, call routed as human by default.
API authentication failed
External system cannot authenticate to the VICIdial non-agent API.
Callback not firing at scheduled time
Scheduled callback is set but never re-enters the hopper at the expected time.
Caller ID not set, outbound calls show as unknown
Outbound calls connect but the recipient's phone shows 'Unknown' or a generic number.
DTMF keypresses not registering
Callers pressing phone keys don't trigger IVR actions, menus get stuck.
Queue overflow, inbound calls dropping
Inbound queue fills beyond configured depth, incoming calls drop or get routed to overflow.
Call recording not starting
Expected call recordings don't exist on disk after the call completes.
Report times out loading
Running a report (especially on large date ranges) times out before returning data.
Screen pop blank or showing wrong lead
When a call connects, the agent sees a blank lead form or data from a previous call.
Time synchronization error
Server clock drift is causing auth failures, SSL issues, or report inconsistencies.
Call transfer failed
Agent initiates transfer but the receiving party doesn't connect or the agent leg drops.
Catch errors before your agents do
VICIPanel monitors every VICIdial daemon, every trunk, every database connection — alerts fire 30 seconds after something breaks.