Category
Running VICIdial day to day: reports, capacity, time zones, phones and the words on the screen.
A VICIdial server keeps several clocks and a stock ViciBox ships them disagreeing. How servers.local_gmt shifts calling windows, and how to check each clock.
5 Nov 2026 · 5 min read
MySQL treats Blended and BLENDED as one VICIdial campaign, yet both spellings get stored. Where that breaks code, exports and reserved-name checks.
5 Nov 2026 · 4 min read
Plain definitions of the VICIdial terms that come up in every support ticket, with the table or field name for each and a link to the longer post.
Budget 80 to 90 kbps each way per agent on G.711 and 24 to 30 kbps on compressed codecs. The packet arithmetic, the server-side total, and what to measure.
A nightly dump of a 2.9 GB VICIdial database streamed off-box in 75 seconds, a restore check in 20, and why recordings need their own plan.
The add_lead API call in practice. Required fields, the duplicate_check values, the replies to parse, and the speed we measured loading 1,000 rows.
A week-by-week plan for a new VICIdial floor. What to settle before the first call, when to switch on auto-dialing, and the limits that bite in month one.
Key-only SSH, a drop-in ordering trap, a default-deny firewall, a manager interface on loopback and API passwords kept out of logs.
A VICIdial move is a database import with rules. Which tables travel, which never do, what gets rewritten, and how to prove nothing was lost.
The database can look quiet while calls are still up. How to quiesce a VICIdial floor and which single command proves nothing is on the wire.