Need guidance to integrate with Vicidial

General
1

Hello , we are looking for open source solution

Need guidance to integrate with Vicidial

2

Hi,

Jambonz itself is fully open source and self-hostable, so the “open source” side of your question is covered. The interesting part is really the Vicidial side — and yes, this is a solved problem if you pick the right topology.

What worked for us: connect Jambonz as a Vicidial REMOTE AGENT, not as a trunk/SBC trick.

  • Each Jambonz session is registered/logged in as a remote agent (agent screen + remote agent extension pointing at the Jambonz SIP endpoint). The dialer then treats the bot exactly like a human agent: it can be dialed into for outbound campaigns (ratio, manual, preview) and it is also reachable for inbound/closer flows.
  • The neat part: technically EVERY call is an inbound call to the agent. Outbound campaigns simply ring the “agent” (Jambonz) and bridge the customer to it, inbound goes straight to the same endpoint. One code path for both directions, no separate outbound/inbound logic in your bot.
  • Qualification and dispositions run through the Vicidial APIs: the agent API for agent-side actions (disposition, pause codes, hangup/transfer, logout) and the non-agent API for lead-side updates (lead fields, callbacks, DNC, comments). That keeps lists, statuses and reporting clean and lets the bot “qualify” a lead exactly the same way a human agent would.

Things that will bite you:

  • One remote agent session per concurrent call. Concurrency means multiple agent logins — plan your agent IDs/extension pool accordingly.
  • A disposition must be set before the agent hangs up, otherwise Vicidial thinks the agent is still on the call and blocks the next one. Build a hard timeout + always-disposition path.
  • Agent keep-alive/pause behaviour: if the bot doesn’t answer the “you are paused / waiting” cycle correctly, the dialer will stop sending calls.
  • DTMF, early media (183 vs 180) and answering-machine detection timing still need attention on the SIP side, even though Jambonz handles the media well.
  • Caller ID/DID consistency across Vicidial and Jambonz, otherwise your reports and recordings won’t line up.

I’m happy to compare notes on the details instead of theory. You can find me in the Vicidial forum as “thomasbartjel”, or send your exact requirements/call flow to info@gofonia.de and I’ll tell you honestly whether your setup fits this model.

Cheers,
Thomas