VICIdial AI Integration Options Compared, From SIP Transfers to Dialplan Bridges
Four ways to attach an AI voice agent to VICIdial, what each one gives up on dispositions, transfers, latency, recording and DNC, and the questions to ask any vendor.
If you run VICIdial and want an AI voice agent to take some of your calls, the first question is not which vendor. It is which architecture. The VICIdial AI integration options on the market look similar in a demo, but they attach to your dialer in very different places, and that decides whether dispositions land on the lead, whether a hot caller can be handed to an in-group, whether recordings stay where your QA team looks for them, and whether a "stop calling me" ever reaches your DNC list.
This article lays out the four common approaches, what each one gives up, and a checklist you can put in front of any vendor. It is written for the person who administers the cluster, not for the person who signs the contract.
What any VICIdial AI integration has to do
Before comparing approaches, it helps to list the jobs. An AI agent on VICIdial has to:
- Hear the caller and talk back with low enough delay that the conversation feels normal, including letting the caller interrupt.
- Control the call: end it, or move it to a person (an in-group, an extension or a number) without the caller hanging up.
- Know which lead it is talking to, so results land on the right record.
- Write the result back: a status, notes, and DNC requests, in the place your reports and hopper already read.
- Leave recording and reporting intact, so QA and compliance do not need a second system.
Every approach below handles some of these well and makes others harder. None of them is wrong in every case.
The four VICIdial AI integration options
1. Send the call to an outside AI service over a SIP trunk or carrier
The simplest idea: the AI vendor gives you a phone number or a SIP address, and VICIdial sends answered calls to it, through your carrier or a SIP peer, the way it would send a call to any outside number.
It works quickly, but the call now has a second leg that VICIdial treats as just another outbound call. The AI side usually does not know the VICIdial lead id unless you pass it in a SIP header or the caller ID. Handing a qualified caller back to your closers means either a SIP transfer (which has to be configured and supported on both ends) or a brand new call into one of your DIDs, which arrives without the lead attached unless the in-group looks it up. If the second leg goes over the PSTN, you also pay carrier minutes twice. Results come back only if the vendor calls your API or you import their report.
2. IVR and AGI scripts
Asterisk can hand a channel to a script through AGI (or FastAGI over the network). The script plays a prompt, records the caller until silence, sends the recording to a speech recognizer, asks a language model what to say, synthesizes the reply and plays it.
This keeps everything on your dialer and gives the script direct access to the channel. The trade-off is that it is turn based: the caller speaks, waits while the turn is processed, then listens. Interrupting the agent mid-sentence is hard to do well, and each turn adds the full record, recognize, think and speak delay. It suits short menus and simple confirmations better than open conversation. Script and audio processing also run on, or close to, the dialer, so load needs watching.
3. A dialplan media bridge
Here a dialplan entry streams the call's audio, both directions and continuously, to an AI service, while a separate control channel lets the service hang up or transfer the call. Asterisk offers a few ways to stream media: chan_rtp (the UnicastRTP channel, Asterisk 15 and newer), AudioSocket, and ARI external media. The caller never leaves your dialer, so the call can be recorded and reported there like any other, and the AI can be interrupted mid-sentence because audio flows in real time.
This is the approach Bridgeside AI uses. One generated entry in VICIdial's Custom Dialplan Entry serves every campaign; a call to 85 plus a campaign's three-digit dial code reaches that campaign's agent:
exten => _85XXX,1,Answer()
same => n,Set(GW=https://app.bridgeside.ai)
same => n,Set(PORT=${CURL(${GW}/api/asterisk/rtp?token=<org token>&agent=${EXTEN:2}&channel=${URIENCODE(${CHANNEL})}&lead=${URIENCODE(${CALLERID(name)})}&phone=${URIENCODE(${CALLERID(num)})})})
same => n,GotoIf($["${PORT}" = ""]?fail)
same => n,Dial(UnicastRTP/<bridgeside media address>:${PORT}/c(ulaw),,b(voicebot-jb^s^1))
same => n,Hangup()
same => n(fail),Playback(all-circuits-busy-now)
same => n,Hangup()
The CURL asks for a UDP port for this one call and passes the channel name, VICIdial's caller ID name (which carries the lead id on auto-dialed calls) and the number. Audio flows as G.711 ulaw. Hangups and transfers go over AMI (Hangup and Redirect), and after the call the status, a two-line summary and any DNC request are written back through the non-agent API. AudioSocket is not part of the default setup but is available on request through our contact page.
4. Agent assist tools
The fourth option does not put an AI on the line at all. It listens to your human agents' calls and suggests answers, flags compliance phrases or writes the notes afterwards. This can lift the quality of human calls, but every conversation still needs a person, so it does not change how many calls your floor can handle. It is worth knowing about because some products described as VICIdial AI are this kind of tool.
What each option gives up
| SIP or carrier to outside AI | AGI scripts | Dialplan media bridge | Agent assist | |
|---|---|---|---|---|
| Disposition on the lead | Only if the vendor writes it back | Yes, the script can | Yes, through the non-agent API | Human agent sets it |
| Transfer back to an in-group | Needs SIP transfer or a new inbound call | Yes, on the dialer | Yes, AMI Redirect on the live call | Not applicable |
| Conversational latency | Extra network leg | Full delay on every turn | Streaming, interruptible | Not applicable |
| Recording | Depends where the second leg is recorded | On the dialer | Call stays on the dialer | On the dialer |
| DNC requests | Only if the vendor writes them back | Script must write them | Written through the non-agent API | Human agent handles |
The pattern is clear. The further the conversation moves away from your dialer, the more you depend on the vendor to send results back, and the more ways a lead can drop out of your reporting.
Questions to ask any vendor
Use these whether or not you are talking to us. Ask for answers in writing, with the actual configuration.
- Where does the audio go? A SIP leg, an AGI script, or a media stream from the dialplan? Which Asterisk version does it need?
- Do I need a new trunk, carrier or number? If yes, who pays for the second leg's minutes?
- How does the AI know the lead id? Ask to see where it is read from.
- How does a transfer reach my closers? The same live call moved to an in-group, or a new call? Does the closer's screen show the lead?
- What gets written back to VICIdial, and through which interface? Status, comments, DNC, callbacks.
- What access do you need on my server? AMI permissions, API user level, firewall ports, and from which addresses.
- Where are recordings and transcripts kept, and for how long? Does the vendor store call audio?
- How is a do-not-call request handled end to end? Ask for a test you can run yourself.
- How do I turn it off? It should be one routing change on your side.
- How is it priced? Per minute, per channel, both, and what happens when the balance or allowance runs out.
Where Bridgeside fits
Bridgeside AI is a dialplan media bridge. It needs Asterisk 15 or newer (VICIdial's own Asterisk 16 and 18 builds are fine), an AMI user permitted only from Bridgeside's address, and a non-agent API user at level 8 or higher with Modify Leads. There is no SIP trunk change. Each campaign has its own script, voice and transfer target, and new campaigns never touch the dialplan again. The VICIdial integration page summarizes the setup, and the complete VICIdial AI integration guide walks through the architecture. If you want to see how the media leg relates to your carriers and codecs, read VICIdial SIP trunks and AI agents.
Pricing is per minute from prepaid credit, from 4.5 cents a minute, and pay as you go has no monthly fee; details are on the pricing page. You can try it with 60 free minutes and no card at app.bridgeside.ai.
FAQ
What are the VICIdial AI voice agent integration options?
There are four: sending the call to an outside AI service over a SIP trunk or carrier, running AGI or IVR scripts on the dialer, bridging the call's audio from the dialplan to an AI service while controlling it over AMI, and agent assist tools that help human agents rather than talk to callers.
Which voice AI agents integrate with VICIdial?
Any service that can receive audio from Asterisk can be attached to VICIdial in some way, so the better question is how deeply it integrates. Check whether it writes dispositions and DNC requests back through the non-agent API, transfers the live call to an in-group, and leaves recording on your dialer. Bridgeside AI does all three.
Which VICIdial AI integration option has the lowest latency?
A streaming approach, where audio flows both ways continuously from the dialplan, avoids waiting for a full recording on every turn and lets the caller interrupt. Network distance between your dialer and the AI service then matters most.
Do I need a new SIP trunk to add AI to VICIdial?
Not with a dialplan media bridge. The AI leg is plain RTP from your Asterisk server, and your carriers stay as they are. Only the SIP or carrier approach adds a leg through a trunk.
Can I try more than one approach?
Yes. Each approach sits behind a route, so you can point one campaign at one option and another campaign at a different one, compare dispositions, and remove whichever you do not keep.