ASAI and Domain Control
■Invalid association (CS0/81) The association does not exist.
■Protocol error (CS0/111)
The Q.932 protocol has been violated or the capability invoked is not consistent with this association. For example, invoking a Third Party Domain Control Request over a Call Control association is inconsistent.
NOTE:
For more information regarding protocol errors and a complete list of reason codes (cause values), see the DEFINITY Enterprise Communications Server CallVisor ASAI Protocol Reference,
Considerations
The Third Party Merge capability may also be used by the adjunct to transfer to the supervisor. A sample scenario is presented below. Note that this is not the only way in which to effect a transfer to the supervisor.
An ACD agent handling the transfer may request (via data keyboard) that the call be transferred to the supervisor. The adjunct:
1.Places the existing call on hold
2.Issues a Third Party Make Call capability (with the
3.When the supervisor is either alerted or answers, the adjunct may merge the supervisor call and the previously held call using the Third Party Merge capability. (This capability is requested on the same association with the held call.)
Since this was a transfer request, the conf/trans_flag parameter is set to TRANSFER and the ECS drops the ACD agent from the connection after the merge takes place.
If the ACD agent requested a supervisor conference, the same procedure would have taken place but the conf/trans_flag would have been set to CONFERENCE. The ECS does not drop the ACD agent from the resulting connection, and a
