Compare
AMDSure vs FreeSWITCH mod_amd and mod_com_amd
FreeSWITCH has two paths: an open module that ports Asterisk's timing rules, and SignalWire's commercial mod_com_amd. Both are rules on silence and speech timing.
| AMDSure | FreeSWITCH AMD | |
|---|---|---|
| The 3% abandon rule | Shadow mode measures people wrongly sent to voicemail on your own calls, beside your built-in AMD(), with the sample size: your detector's share of the 3% abandon rate, before you switch. People are decided first, 2.55 s on average. | No measurement; the same rules as AMD() with the same blind spot. |
| How it decides | A compiled agent on your Asterisk box measures the call (a real voice detector, tones, a learned acoustic model, the sound of the pickup itself); AMDSure's server applies the rules and signs the verdict. | The same silence and word-timing rules as Asterisk's AMD(), with the same parameter names (silence_threshold, maximum_number_of_words, total_analysis_time). |
| Where the audio goes | Stays on your server. The agent sends numbers (speech probabilities, tone events, model scores), never audio, unless you switch learning on. | Stays on your server. |
| Time to a verdict | Median 4.6 s to a verdict on live calls from the pickup, 2.3 s on recordings that start mid-greeting; short greetings decide at about 2 s, beeps and known greetings sooner. | Up to the analysis time you set. |
| Price | Free: 50,000 verdicts a month, two servers, no card. Starter $69 a month for 500,000 then $0.0002; Growth $269 for 5,000,000 then $0.00012; Scale $899 for 25,000,000 then $0.00008. | mod_amd (webitel): free, open source. mod_com_amd: commercial licence from SignalWire, price on request. |
| What it reports | Person, voicemail, call screener, unsure, each with a reason, a confidence and the time to the verdict. And what answered, by name: Verizon, AT&T and other carriers' default greetings, number read-outs, iPhone, Samsung and Google call screening, a disconnected number (the intercept tones), fax, busy, dead air, a false answer. Stamped on the call as AMDSURE_KIND for the dialer. | amd_result and amd_cause channel variables, human or machine. |
| Works on | Asterisk 18 to 22 and everything built on it: VICIdial, ViciBox, FreePBX, Issabel, GoAutoDial, custom dialers. FreeSWITCH in development. | FreeSWITCH only. |
| Proof before you switch | Shadow mode runs beside your built-in AMD() on every call and stamps its verdict on the call; the dashboard shows people wrongly sent to voicemail and voicemails caught, against AMD(), before you switch. | None built in. FreeSWITCH's own documentation says no algorithm reaches 100 percent and tuning is per deployment. |
| When it fails | Open, to your own AMD(). A brain outage costs seconds, never a call. | It is the fallback. |
| Your audio and training | Your call audio is used for training only with the learning checkbox on, which you can turn off at any time; phone numbers are never seen. | None. |
Where FreeSWITCH AMD is good
An open port of Asterisk's rules, and a commercial module. Free or licensed.
- Free (open module) and on your box.
- Familiar parameters for anyone who tuned Asterisk.
Where AMDSure differs
- Same rules on loudness as AMD(), same weaknesses: no voice model, no screener detection, tuning by hand.
- AMDSure's FreeSWITCH mode is in development; today AMDSure serves Asterisk-based dialers. If you run FreeSWITCH, ask us for the date.
Sources
Facts about FreeSWITCH AMD come from its own documentation and pricing pages on the dates noted; tell us at [email protected] if something has changed and we will fix it. Other comparisons: Stock AMD(), AMDY, Twilio AMD, Telnyx AMD, Plivo, SignalWire AMD, Vonage, VM Hunter.
See it on your own traffic.
A 20 minute call. We show the console with live numbers, then set up shadow mode on your dialer so you can judge for yourself.
Start free