Lucent Technologies 555-230-220 User Manual
ASAI and Feature Interactions
Issue 7 May 1998
12-27
For direct-agent calls, the agent’s COR is used for the termination party restriction
checks, whereas regular ACD calls use the split’s COR for the termination party
restriction checks.
checks, whereas regular ACD calls use the split’s COR for the termination party
restriction checks.
Third Party Auto Dial and Third Party Make Call calls are originated by using the
originator’s COR.
originator’s COR.
For switch-classified calls, the COR associated with the ASAI link is compared
with the COR for the destination party. If the COR check fails, the call is dropped,
and a Call Ended Event Report is sent to the adjunct with cause CS0/21.
with the COR for the destination party. If the COR check fails, the call is dropped,
and a Call Ended Event Report is sent to the adjunct with cause CS0/21.
Class of Service (COS)
The Class of Service (COS) for the originator is never checked in conjunction with
any ASAI capabilities.
any ASAI capabilities.
Conference
Manual conference from a domain-controlled station is allowed, subject to the
feature’s restrictions. The Hold Event Report is provided as a result of the first
conference button push or first switch-hook flash. The Conference Event Report is
provided as a result of the second conference button push or second switch-hook
flash, and only if the conference is successfully completed. On a manual
conference, the Call Conferenced Event Report is sent to all the active
associations for the resultant call. For conference from another association, the
requesting association receives a positive acknowledgement (ACK), and all other
associations for the call or endpoints receive the Call Conferenced Event Report.
feature’s restrictions. The Hold Event Report is provided as a result of the first
conference button push or first switch-hook flash. The Conference Event Report is
provided as a result of the second conference button push or second switch-hook
flash, and only if the conference is successfully completed. On a manual
conference, the Call Conferenced Event Report is sent to all the active
associations for the resultant call. For conference from another association, the
requesting association receives a positive acknowledgement (ACK), and all other
associations for the call or endpoints receive the Call Conferenced Event Report.
A conference can affect who is defined as the calling party and the called party on
a call. See ‘‘Event Reporting for Merging Two Calls’’ on page 3-55 and “Transfer
and Conference Interactions” sections in Chapter 3 for more information on
merged calls.
a call. See ‘‘Event Reporting for Merging Two Calls’’ on page 3-55 and “Transfer
and Conference Interactions” sections in Chapter 3 for more information on
merged calls.
A Single-Step Conference to an existing conference call will not change the
conference controller, nor will it change the ‘last added party’ in a conference.
conference controller, nor will it change the ‘last added party’ in a conference.
For a complete list of cause values, see the
DEFINITY Enterprise
Communications Server CallVisor ASAI Protocol Reference
, 555-230-221.
Advice of Charge (AOC)
Starting with R5: If an outgoing call that receives charge advice is merged with
another call, the next Charging Event Report will provide the call id of the resulting
merged call and not the call id of the call that was discontinued as a result of the
merge.
another call, the next Charging Event Report will provide the call id of the resulting
merged call and not the call id of the call that was discontinued as a result of the
merge.