Event Notification

All call progress events are reported to CCXML as a transition event of "bvr.callprogress". The event contains three fields

connection
connectionid
type

The type field will contain one of the following values

Table 1. AMD Events
Value	Description	Potential Usage
amd_unknown	maxruntime has elapsed and no previous termination event has occurred	No result - assume a machine
amd_human	Voice has been detected and has lasted for less than amdtime. The is probably a human.	Treat the called party as human, start human dialog
amd_potentialmachine	Voice has been detected for longer than amdtime and is still being detected. This is potentially a machine.	Probably a machine, prepare the machine dialog
amd_machine	Voice has been detected for longer than amdtime and has finished. This is a machine.	Is a machine, start the machine dialog
amd_potentialbeep	A potential beep has been detected for longer than beepontime. This is potentially a beep	Probably a machine, prepare the machine dialog
amd_beep	The beep has finished for at least beepofftime. This is a beep.	Is a machine, start the machine dialog
fax	A fax tone has been detected for the minimum required duration. This is a fax machine.	Is a fax machine, hang up

Multiple events maybe generated for a given call.

For example if the AMD is configured to report all events and only stop on unknown, human and beep then the following event sequence could be generated:

amd_potentialmachine (after amdtime has been reached)
amd_machine (voice has stopped speaking)
amd_potentialbeep (start of a beep detected)
amd_beep (beep has finished - AMD stopped)