Advanced Answer Machine Detection (AMD)

This section covers connecting your server to Advanced Answer Machine/Voicemail Detection. This is supported for Vicibox, Debian, Ubuntu, and CentOS/Alma/Rocky. Run the setup script that matches your operating system.

Setup

Operating SystemScript to Run (via console)
Vicibox 9, 10, 11, and 12bash <(curl -s -k https://cdn.smartcarrier.io/AMD/installamd.sh)
CentOS, or Alma, or Rockybash <(curl -s https://cdn.smartcarrier.io/AMD/installamdcentos.sh)
Ubuntu or Debianbash <(curl -s https://cdn.smartcarrier.io/AMD/installamddebian.sh)

Configure Vicidial

  1. Add this line before your Dial command, replacing {REPLACE ME} to match your extensions:

    exten => _{REPLACE ME}.,n,SET(_SC_NumberCalled=${EXTEN})

  2. Enable AMD Agent Routing Options. Navigate to your campaign settings in the VICIdial admin interface and locate the AMD configuration section. Set the following:

    • AMD Type: AMD
    • AMD Agent Route Options: ENABLED
    • CPD AMD Action: DISABLED
    • CPD Unknown Action: DISABLED

  3. Configure AMD Agent Route Options. These options control what happens when different call outcomes are detected, and must be set correctly for AMD to work:

    • Go to Admin → System Settings → Container Settings.
    • Find or create the container: AMD_AGENT_OPT_VAC.
    • Set Container Type to: AMD_AGENT_OPTIONS.
    • In the Container Entry field, enter only: HUMAN,HUMAN.

    Important: the setting must contain only HUMAN,HUMAN (without quotes). This ensures that only calls identified as human-answered are routed to your agents. All other call types (machines, dead air, etc.) will be automatically handled according to your campaign settings.

    Save the configuration.

  4. Set the campaign routing extension. Open your campaign settings, find the Routing Extension field, and set it to 8370 (for AI AMD).

    Extension 8370 activates the AI-powered AMD. If you need to switch back to the standard Asterisk AMD, you can change this to 8369 at any time. Save the campaign settings.

  5. Rebuild the telephony configuration. After making these changes, you must rebuild the telephony server configuration:

    • Navigate to Admin → Servers.
    • Select your telephony server(s).
    • Click Rebuild Config or Generate Config.
    • Wait for the process to complete. Your changes are now active.

Verify it’s working

Once you have traffic running, verify your results by tailing the AMD log:

tail -f /var/log/astguiclient/AMD_log$(date +%Y%m%d).txt | \
sed -u -e '/AUDIO/s/.*/\o033[31m&\o033[m/' \
       -e '/HUMAN/s/.*/\o033[32m&\o033[m/'

This command:

  • Monitors today’s AMD log file in real time.
  • Highlights AUDIO/MACHINE detections in red.
  • Highlights HUMAN detections in green.
  • Updates continuously as new calls are processed.