AMDY FREESWITCH AMD

FreeSWITCH AMD
that listens.

FreeSWITCH has no built-in answering machine detection like Asterisk’s AMD(). AMDY adds it with a Lua script and mod_audio_stream, returning a verdict your dialplan can route on.

Start free See all integrations
125ms

detection starts after answer

0

calls lost when AMDY is unreachable

50K

free detections to evaluate

THE GAP IN FREESWITCH

A beep detector
isn’t AMD.

The usual options find the voicemail tone after the greeting, rely on timing modules, or depend on one carrier’s detection.

01

mod_avmd waits for the beep

It detects the tone after a greeting, not who answered — too late for routing.

×
02

Timing modules inherit timing errors

Third-party silence detectors make the same mistakes as stock Asterisk AMD.

×
03

Carrier AMD locks you in

Detection bundled into one carrier only covers calls on that carrier.

×
HOW IT FITS

Lua script.
One stream per call.

Your dialplan runs the AMDY Lua script on answer. It streams 8 kHz mono audio over a secure WebSocket via mod_audio_stream, sets AMDSTATUS when a verdict arrives, then stops the stream.

Read the API docs
DIALPLAN.XMLEXAMPLE
<extension name="amdy_amd">
  <condition field="destination_number" expression="^amd$">
    <action application="lua" data="amdy_amd.lua"/>
    <action application="transfer"
      data="${AMDSTATUS} XML amd_routes"/>
  </condition>
</extension>
FALLBACK KEEPS NATIVE AMD8 KHZ · MONO
WHAT CHANGES

For your agents,
for your numbers.

The dialer still dials and your carrier still carries the call. The decision just gets better.

FusionPBX ready

Works on FreeSWITCH and FusionPBX installs with mod_audio_stream.

Routes on a variable

HUMAN, MACHINE or FALLBACK — route each however you like.

Only confirmed people

Unclear calls never default to HUMAN, so agents aren’t sent machines.

READY FOR A BETTER FIRST HELLO?

Try AMDY on FreeSWITCH.

50,000 free detections. Point one campaign at it and compare.

Talk to AMDY