Skip to content

Limits and what is unverified

Learned from the live install, and worth knowing about yours:

  • lead_search joins several lead ids with a dash (12-11, newest first), not the comma the documentation shows. Vodial reads both.
  • VICIdial accepts a list id that does not exist and files the lead in it without complaint. Vodial cannot detect this from the reply, so check the list number in the wizard carefully: a wrong one puts every pushed lead in a list nobody opens.
  • version answers without checking the user and password. Vodial’s Test proves the login with a read-only search instead.

“Our test server” is a small stand-in for the Non-Agent API. We wrote it from VICIdial’s published documentation, and it runs inside our automated tests on the same machine. It proves that Vodial sends the requests we meant to send and reads the replies we expect from the documentation. It does not prove how your VICIdial version answers.

Phone calls are also simulated in our tests. No real call has been handed to a real in-group.

  • Reply layouts. Vodial expects the first line of a reply to start with SUCCESS or ERROR, with details after - separated by |. It reads this loosely. The exact layouts of lead_search and add_lead replies are assumptions.
  • The new lead’s id. Vodial does not rely on the add_lead reply to learn it. It searches by phone number again. If that search finds nothing, the push is still recorded, and a later status update searches again.
  • Statuses. Every status Vodial sets must already exist in VICIdial. Vodial cannot create one.
  • Which lead. The search is by phone number only. If VICIdial returns several leads, Vodial uses the first.
  • An https address, public or reached through a VPN. Private addresses are refused in production.
  • An API user of level 8 or higher with Vdc Agent API Access 1, API Allowed Functions ALL_FUNCTIONS and Modify Leads allowing leads to be added. The list and campaign must exist.
  • A firewall open to the addresses the wizard lists. A self-signed certificate works if you tick the box in the wizard and confirm its fingerprint. Vodial then accepts only that certificate, so the server is still authenticated.

See prepare your VICIdial.

Limit Value
Numbers US and Canada, +1, only. Anything else is not sent.
comments 255 characters. Summary first, then whole facts.
One call to VICIdial 15 seconds, and replies are read up to 64 KB.
Deliveries at once 4 in flight per connection, per Vodial server.
Retries 24 hours from the event, then “Gave up”.
Lead file 50 MB, 200,000 rows.
Do-not-call file 50 MB, 1,000,000 lines.
  • It does not read statuses, calls or agents back from VICIdial.
  • It does not pull a list from VICIdial by API: the Non-Agent API has no function that returns a list’s leads. To import from a VICIdial list, give Vodial a read-only database user on the connection (SELECT on the asterisk database only, on port 3306 or any port from 1024 to 65535; encryption required by default, or insecure if you choose); otherwise use import files.
  • It does not check the in-group or the list when you save. Nothing checks the list until the first lead is pushed.
  • It does not overlap password changes. See connect your VICIdial.

Run Vodial beside VICIdial, not instead of it:

  1. Connect with a test list and a test in-group.
  2. Hand over one call from a number you control and check the lead, the comments and the status.
  3. Move one real campaign, with a small list, and keep your VICIdial campaigns running.
  4. Widen only when the Delivery log stays clean for a few days.

See test and troubleshoot and simulated versus real.