On-Prem AMD

Answering machine detection on your own VICIdial server

VM Hunter On-Prem AMD is a Docker container that decides HUMAN or MACHINE from the first two seconds of every answered call, on your hardware. No audio leaves your network, no calls-per-second limit, and a flat yearly price.

Why on-prem

The detector sits next to the dialer

The cloud service streams audio to VM Hunter's SpeechLLM engine. On-Prem keeps everything on the server that answers the call: the model, the audio and the verdict.

No audio leaves your network

Detection runs inside a container on your own server. Call audio is analysed there and discarded. The only thing sent to VM Hunter is a call count for billing, every five minutes.

No CPS limit

There is no per-second or per-channel cap. Dial as fast as your carrier and your hardware allow; the license counts calls per year, nothing else.

Decides in two seconds

The model listens to the first two seconds after answer and sets AMDSTATUS and AMDCAUSE for your dialplan, with no round trip to the internet on the call path.

Never blocks dialing

If the container is stopped or the license lapses, the dialplan falls back to the built-in Asterisk AMD() automatically. Your campaigns keep running either way.

Models

Two models, one license

Pick per server. Both ship in the same container and are chosen with one setting; switch any time.

Lite

Runs on the VICIdial server itself

A 0.4 MB acoustic model made for the CPU. It installs on the same machine as VICIdial, so a single-server install needs no extra hardware at all.

  • Measured on 16 cores: 5,000 calls in the detection window at once, verdicts in 1.9 s median, 2.9 s p95, no errors; about 2,500 answered calls per second
  • A 4-core dialer handles roughly 1,000 at once; 16 GB RAM is plenty for either
  • Best for single dialers and most cluster nodes

Full

Most accurate, for high volume

The larger model for the hardest audio: carrier messages, screening prompts and noisy lines. It needs more CPU per call, so size the server for the peak.

  • Measured on 16 cores: 1,000 calls in the detection window at once, verdicts in 2.0 s median, 2.6 s p95, no errors; about 500 answered calls per second
  • Runs on the dialer or on a dedicated detection box; a GPU lifts it to 5,000 at once
  • Best for large campaigns where every verdict counts
LiteFull
Where it runsSame server as VICIdialDialer or a dedicated server
Hardware4 cores and up; 8 GB RAM16 cores recommended; 16 GB RAM
Calls in the window at once, 16 cores5,000 (tested limit)1,000
Answered calls per second, 16 coresAbout 2,500About 500
Verdict time at that load1.9 s median, 2.9 s p952.0 s median, 2.6 s p95
Licensed calls per secondNo limitNo limit
DecisionFirst 2 seconds of audioFirst 2 seconds of audio
Audio sent to VM HunterNoneNone
GPUNot neededNot needed

Measured with real-time audio streams on a 16-core Ryzen 9 9950X, every call reaching its 2-second decision at the same instant. Older server CPUs do a third to a half of that per core. Figures are for the detector alone; VICIdial and Asterisk need their own headroom on a shared server, so plan on half when they share the box. The install includes scripts/replay.py to measure your own hardware.

Pricing

Flat yearly pricing by call volume

One license per customer, up to 25 dialer servers, both models, no CPS or channel limits. Renew early and the unused days and calls carry over.

Starts from

$2,000/year

for 60 million calls a year. Higher volumes are quoted per customer.

  • Both models: Lite and Full
  • No calls-per-second limit
  • No concurrent-call limit beyond your hardware
  • Up to 25 dialer servers per license, more on request
  • Verdict from the first two seconds of audio
  • HUMAN, MACHINE, SCREENING, SILENCE, TONE and BUSY causes
  • Automatic fallback to Asterisk AMD() if the container is ever unavailable
  • Works offline for 24 hours to 7 days if the license server cannot be reached
  • Model and container updates for the term
  • Email support and the install guide

Prices in USD, billed yearly. Tell us your monthly call volume and number of dialers and we reply with a quote the same day.

Install

Up and running in under 30 minutes

The container is a public image. It runs in host-network mode next to Asterisk, listens on a local WebSocket, and the dialplan hands it the call audio through EAGI, the same mechanism VICIdial uses for its own scripts.

  • Run the container with your license key: docker run -d --network host -e LICENSE_KEY=AMD-… ghcr.io/vmhunterhq/acoustic-amd
  • Add one extension to extensions.conf: a copy of VICIdial's AMD extension with AMD() replaced by the detector, and AMD() kept as the fallback.
  • Point your campaign at the new extension. Verdicts land in AMDSTATUS and AMDCAUSE, so VICIdial's status mapping works unchanged.
  • Check docker logs: every verdict is logged with its cause and timing.

The step-by-step guide, the dialplan snippet and a test procedure come with the license. The cloud integration pages for VICIdial and Asterisk describe the same dialplan approach.

Which one

Cloud or on-prem?

VM Hunter cloudOn-Prem AMD
EngineSpeechLLM: understands what the callee saysAcoustic model on the first 2 seconds
Where audio goesStreamed to VM Hunter, logged with transcriptStays on your server
LimitsCalls per month, CPS and channels by planCalls per year; no CPS or channel limit
HardwareNoneCPU on your dialer (Lite) or a bigger box (Full)
Evidence per callTranscript, recording, cause in the dashboardCause and timing in the container log
PriceFrom free, plans from $100 a monthFrom $2,000 a year
FitsAny dialer, Twilio, voice AI agentsVICIdial and Asterisk sites that must keep audio in-house

Many customers run both: On-Prem on campaigns with strict data rules, the cloud service where they want transcripts and call-screening detection. The license and the API key are independent.

FAQ

Questions

What is VM Hunter On-Prem AMD?

A Docker container that runs answering machine detection on your own VICIdial or Asterisk server. It decides from the first two seconds of each answered call and sets AMDSTATUS and AMDCAUSE for the dialplan, the same way VICIdial's own AMD does, but with an acoustic model instead of beep and silence timing. Audio never leaves your server.

What does it send to VM Hunter?

Only a license check-in every five minutes: your license key, the server's fingerprint and the number of calls analysed since the last check-in, broken down by cause. No audio, no phone numbers, no transcripts.

What hardware do I need?

The Lite model runs on the CPU next to VICIdial: a small server with 4 cores and 8 GB of RAM handles about 100 simultaneous calls. For the Full model, the most accurate one, we recommend 16 cores and 32 GB of RAM, which handles around 5,000 simultaneous calls. No GPU is required.

Can it run on the same server as VICIdial?

Yes. The Lite model is built for that: it is a 0.4 MB model that runs on the CPU with Docker in host-network mode, so a single-server VICIdial install needs no extra machine. Cluster installs run one container per dialer.

Is there a calls-per-second limit?

No. The cloud plans meter CPS and channels; the on-prem license does not. The only limit is the yearly call quota of your plan and what your hardware can process.

What happens if the license server is unreachable or the container stops?

The container keeps working offline on its last signed license token, for 24 hours by default and up to 7 days by arrangement. If the container itself is down, the dialplan falls back to Asterisk's AMD() on its own, so dialing never stops.

How is it installed?

Pull the public image, run it with your license key, and add one dialplan extension that calls the detector instead of AMD(). Most installs take under 30 minutes on an existing VICIdial server; the guide and the dialplan snippet come with the license.

How is it priced?

Per year, by call volume, starting at $2,000 a year for 60 million calls on up to 25 servers. Larger volumes are quoted per customer. Renewing early carries unused days and calls into the new term.

Where do I see usage?

Call counts by day and by cause are collected at every check-in. An on-prem usage page in the VM Hunter customer dashboard is coming; until then, usage is available from support on request, and the container's own logs show every verdict.

Keep the audio on your servers

Tell us your dialer setup and call volume. You get a license key and the install guide, and the container is live the same day.