Below are some example scenarios and recommended event and termination event hint settings for answer machine detection:
Application to leave message after a beep
Application assumes it is a human and starts playing the human dialog. When amd_potentialmachine or amd_potentialbeep is raised the application prepares the machine dialog. When amd_machine or amd_beep is raised the application stops the currently running dialog and starts the machine dialog. This will cause the application to play to a human, if there is any indication of a machine it will restart the machine dialog. This means the machine dialog could be restarted multiple times. This is useful if there is a large pause after the voice message but before the beep. The machine dialog would play after the voice message and restart again after the beep to ensure the complete message is left. This scenario also leaves the AMD turned on in case latter beeps are detected. The AMD will eventually turn off after the maxruntime.
Application to detect if it is a human or machine
Application assumes it is a human (or nothing). When amd_human is raised then it is definitely a human. When amd_machine or amd_beep is raised it is definitely a machine. This will cause the application to stop the AMD whenever a positive detection event occurs. At this point the application can proceed down the human or machine flow..