What's new in VICIdial SVN 4032: API access, a caller ID decline report and smarter AMD

VICIdial doesn't ship big numbered releases. It moves forward one SVN revision at a time, a commit or two a week. SVN 4032 landed on 25 September 2026, and it's the version the VICIfast servers we've built since late September run. Here's what changed in it, what the few months before it added, and what has landed since.

API access is now switched on per user

The change you're most likely to notice: from 4032, every Non-agent API function that needs a login only works for users with Agent API Access turned on. Without it, the call answers ERROR: USER DOES NOT HAVE API ACCESS.

That's a good change. Before, any user who could log in to the admin reports could also call the API, so a leaked manager password went further than it should. Now API use is something you grant on purpose.

If a CRM, lead feed or script stops working after an upgrade, open that user in Admin → Users and set Agent API Access to 1. Users carried over from an older VICIdial are the usual suspects. Our guide to securing the VICIdial API covers the rest.

One extension, several devices

Just before 4032 (revision 4031), VICIdial's default PJSIP phone setup allows up to 8 devices on one Extension, and a call rings all of them, so a desk phone and a Softphone can share a line.

On VICIfast servers we keep agent phones to one device at a time on purpose: when an agent logs in somewhere new, the new device takes over cleanly instead of two devices ringing. If you need several devices on one extension, ask support and we'll set it for that phone.

See which caller IDs are being declined

The new CID SIP 603 Report lists each outbound CID (caller ID) with how many calls it placed and how many were refused with SIP 603 Decline. A number whose 603 rate is climbing is often being flagged by carriers or blocking apps, so this is an early warning to rest or replace it.

Better control over answering machines

• AMD Status Map: map each AMD (answering machine detection) result and reason (for example, a machine detected because the greeting ran long) to your own dispositions, instead of the generic AA and AM statuses. Your reports then show why a call was marked as a machine.
• Fax and false-answer hang-up: calls that turn out to be fax tones or a false answer can hang up on their own, with their own statuses. This one comes with upstream's paid ViciAMD service.
• What the detector heard: with ViciAMD, the agent screen can show the AMD result and a transcript of the greeting as the call arrives.

If you're still tuning standard AMD, start with how VICIdial's AMD decides.

Faster call routing, if you opt in

Upstream added an experimental FastAGI server: one long-running process that routes answered calls instead of starting a fresh script for every call. Upstream measured routing scripts starting in about 6 milliseconds instead of about 600 on older hardware. It's off by default, inbound support is still being finished, and we're not turning it on for customers yet.

Quieter improvements

• Internal process logs: every back-end process records when it started and that it's still running, so you can see a stalled dialer process in the admin screens.
• Safer custom dialplan: shell commands typed into carrier or custom dialplan boxes are now stripped out before Asterisk sees them.
• Cluster fix: on multi-server clusters, one dialer's clean-up can no longer touch another dialer's calls.
• Clearer call history: a lead's extended call log shows the SIP response for every attempt.
• Plus a batch of PJSIP fixes, newer MariaDB tool names, millisecond Asterisk log timestamps and a beta of a faster web lead loader.

What has landed since 4032

Only two revisions so far. 4033 lets a voicemail box or phone email several addresses (separate them with a |), and it raises the database schema to 1746. 4034 makes VICIdial run cleanly on PHP 8.5. Neither fixes a security problem in VICIdial, so they can wait for your next planned upgrade.

Which revision are you on?

Check each server's revision before planning an upgrade. Our guide to checking the VICIdial version across your servers shows where to look. Upgrade off-shift, back up the database first, and run the schema upgrade script whenever the schema number changes.

On VICIfast, we track upstream for you and roll changes out once they've been tested on our own floor. See plans and pricing.