The operator's perspective.
On VICIdial, SIP, and call-center ops.
7-day free trial · Cancel anytime · Pay with card or USDT
Page 17
Operator writing, sorted newest first.
How to create an agent account with the add_user API
A step-by-step guide to the add_user non-agent API, which creates a new VICIdial agent account from your own application.
How to call the VICIdial Non-Agent API over HTTP
A plain walkthrough of building your first VICIdial Non-Agent API call: the URL, the required parameters, and a working example you can paste into a browser.
Reading an agent's settings with user_details
A short guide to the user_details non-agent API call: what it returns, the permissions it needs, and when to use it over agent_status.
Stopping duplicate leads with add_lead duplication checks
How the add_lead duplicate_check options keep the same number from landing in your dialer twice, with the scope flags and X-day variants explained.
How to change an existing lead with the update_lead API
Use the update_lead Non-Agent API call to edit a lead in place, match it by lead ID, vendor code, or phone number, and write back changed fields.
The Non-Agent API vs the Agent API: which one you need
VICIdial ships two HTTP APIs that look alike but do different jobs. Here is how to tell them apart and pick the right endpoint for your task.
What the API source parameter is for
Every VICIdial API call takes a source parameter. It does not change behavior, but it is the label that makes your API logs readable.
Adjusting remote-agent lines with update_remote_agent
How to use the update_remote_agent non-agent API call to change a remote agent's line count, campaign, and active status from a script.
How to spot capacity problems before they hit your agents
Use VICIdial's performance graphs and 30-day stats to catch a server running out of headroom before agents start hearing lag and dropped calls.
Agent latency as a server capacity signal
Agent screen latency is not just a network complaint - rising latency values are an early sign that your VICIdial server is approaching its capacity ceiling. This post explains why latency climbs under load and how to use it as an actionable capacity signal.
How to watch disk usage on a busy dialer
Recordings, logs, and the database all grow on the same disk your VICIdial server runs on. Learn how to track disk percent-used, set retention policies, and avoid a full disk before it kills your dialer.
What high system load actually means on a dialer
High system load on a VICIdial server does not always mean the same thing. This post explains what load average measures, why it rises, and how to tell a real call surge from a runaway process.
Monitoring database load on a VICIdial server
On a single-tenant VICIdial box the database and Asterisk share the same CPU, so a slow query during peak dialing can stall your entire shift. This post explains what to watch and how to spot database pressure before it affects calls.
What the last 1000 lines of Asterisk CLI output tell you
The Asterisk Debug Page surfaces the most recent 1000 lines of CLI output alongside SIP and IAX peer status. Learn how to read these streams to spot trunk registration failures, call leg errors, and codec mismatches before they affect your agents.
How to read the LAGGED Summary Report
The LAGGED Summary Report aggregates agent lag events into totals and a timeline chart so you can see whether lag is random or bunching at predictable times. This post explains how to read the chart and what the summary numbers tell you.
Sizing a VICIdial server: how many agents and channels a box can handle
Choosing the right server size for VICIdial means understanding two linked ceilings: the number of agents who can log in and work, and the number of concurrent Asterisk channels those agents will generate. This post explains the framework for thinking about both together.
Monitoring recording storage so you never run out of disk
Call recordings are the fastest way to fill up a VICIdial server's disk. This post explains how to track storage usage, understand how quickly recordings accumulate, and set retention policies before you hit a disk-full event.
Safe CPU and load thresholds for a VICIdial box
Knowing what load average and CPU percentages are acceptable on a VICIdial server helps you act before performance degrades. This post gives you concrete thresholds based on your core count and call volume.
What causes latency gaps on the agent screen
Latency gaps on the VICIdial agent screen have several distinct root causes, from agent-side network problems to server overload. Understanding which category you are in determines the correct fix and prevents the same issue from recurring.
Server health status versus billing status: the difference
VICIfast tracks health status and billing status as two separate things. A server can be ACTIVE in billing terms while being DEGRADED or UNREACHABLE at runtime. Understanding the difference helps you troubleshoot faster.
Spotting LAGGED clusters on the timeline chart
The LAGGED Summary Report's timeline chart is the fastest way to see whether agent lag is random noise or a repeating pattern. This post walks through what a cluster looks like on the chart and how to pinpoint exactly when and why it happens.
What a DEGRADED server health status means
DEGRADED means your VICIdial server is still reachable but something is wrong at runtime - high load, a dead keepalive, or a key process that is partially down. Here is what triggers it and what to do.
What the User Group Login Report tells you about agent access
The User Group Login Report groups every agent login by user group and shows you first login, last login, and the most recent session details - campaign, server, workstation, and phone. This post explains each column and how to use it for access reviews.
How to set up uptime monitoring for your VICIdial server
A ping monitor is not enough for a VICIdial server. This post explains what to monitor, which endpoints reveal real dialer health, and how to wire up a tool like UptimeRobot or BetterStack to catch outages before your agents do.