ASAI and Call Control
The Alerting and Call Connected Event Reports are sent to the adjunct when the call is being delivered at a physical endpoint (agent/extension). The Connected Party number item and its extension are included in these event reports. For announcements, the connected party extension is the same as that specified for the calling endpoint in the Third Party Make Call request. For hunt groups and splits, this is the member/agent extension receiving the call.
The Call Ended Event Report is sent to the adjunct when the call is dropped because of a busy, reorder, denial,
If a SIT was detected, the call is either dropped (call ended message is sent with cause=SIT value), or it is considered answered depending on how the ECS is administered. If an ISDN progress message is received with a cause value that maps to a SIT tone, then a call is dropped or answered depending upon the ECS administration. See Table
For G3V3 and later, an ASAI adjunct may request Answering Machine Detection (AMD) for a
If an answering machine is detected, a cause value is sent in either the Answered or the Call Ended message to indicate such, and the call is either dropped or connected. If the treatment selected is connect, an Event Report is sent to the adjunct. The treatment may be specified either
NOTE:
When AMD is requested on a
For
Switch-Classified Call Originator
When the destination answers, the originator receives ringing. If the originator intraflows with priority, the new destination receives priority ringing. The originator receives the zip tone if it is in
