This section contains information regarding Advanced Answer Machine/Voicemail Detection. This article covers installation for Vicibox, Debian, Ubuntu, and CentOS/Alma/Rocky. You will need to run the installation script that matches your operating system.
| Operating System | Script to Run (via console) |
|---|---|
| Vicibox 9, 10, 11, and 12 | bash <(curl -s -k https://cdn.smartcarrier.io/AI+AMD/installamd.sh) |
| CentOS, or Alma, or Rocky | bash <(curl -s https://cdn.smartcarrier.io/AI+AMD/installamdcentos.sh) |
| Ubuntu or Debian | bash <(curl -s https://cdn.smartcarrier.io/AI+AMD/installamddebian.sh) |
Now, let's configure Vicidial:
- 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: Set to "AMD"
- AMD Agent Route Options: Set to "ENABLED"
- CPD AMD Action: Set to "DISABLED"
- CPD Unknown Action: Set to "DISABLED"
- Navigate to your campaign settings in the VICIdial admin interface and locate the AMD configuration section. Set the following:
- Configure AMD Agent Route Options - The AMD Agent Route Options control what happens when different call outcomes are detected. For AMD to work correctly, you must configure this setting properly:
- 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.
- Set Campaign Routing Extension:
- Finally, configure the campaign to use the AI AMD extension:
- Open your campaign settings.
- Find the Routing Extension field.
- Set it to: 8370 (for AI AMD).
- Note: 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.
- Finally, configure the campaign to use the AI AMD extension:
- Rebuild 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.
- After making these changes, you must rebuild the telephony server configuration:
How to check if it is working:
- Once you have traffic running, you may verify your results by running the following command:
- 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/' - What this command does:
- 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.
- tail -f /var/log/astguiclient/AMD_log$(date +%Y%m%d).txt | \
Technology Innovation Lab, LLC | Smart Carrier
326 Broad Street
Second Floor
Utica New York 13501
Office: +1 315 556 4800
Comments
0 comments
Please sign in to leave a comment.