Lucent Technologies DEFINITY Enterprise Communications Server Release 5, CallVisor, ASAI Protocol Reference Instructions Manual

Domain (Station) Control Procedure
Issue 6  June 1997
2-25
If the ECS cannot accept the request, the ECS returns a denial. For coding, 
see ‘‘Domain Control: Request is Denied — Association Continues’’ on 
page 5-90 of Chapter 5, “Byte Level Messages.”
3. Various sequences of event reports and adjunct requests for call control 
may occur. In terms of the message procedure, the event reporting and call 
control are a sequence of FACility messages flowing across the interface.
Third Party Answer Procedure...

Messaging Sequences and ASAI
2-26Issue 6  June 1997 
Call Control Procedures
Once the adjunct has control of a third party call, within either a Call Control or 
Domain (Station) Control, it may invoke various call control capabilities.
The adjunct passes the CRV for the Call Control or Station Control association in 
the FACility message containing these capability requests.
If the ECS denies any of these requests, a FACility message carries the denial so 
that the call control association continues....

Call Control Procedures
Issue 6  June 1997
2-27
2. The ECS drops the party and replies with a return result FACility message. 
The invoke-id in the return result has the same value as the invoke-id in the 
third party drop request. For call control coding, see ‘‘Call Control: 
Acknowledgment (No Parameters) Association Continues’’ on page 5-61 of 
Chapter 5, “Byte Level Messages.” For domain control coding, see 
‘‘Domain Control: Acknowledgment (No Parameters) Association 
Continues’’ on page 5-89 of...

Messaging Sequences and ASAI
2-28Issue 6  June 1997 
2. The ECS reconnects the party to the call and replies with a return result 
FACility message. The invoke-id in the return result has the same value as 
the invoke-id in the third party reconnect request. For call control coding, 
see ‘‘Call Control: Acknowledgment (No Parameters) Association 
Continues’’ on page 5-61 of Chapter 5, “Byte Level Messages.” For domain 
control coding, see ‘‘Domain Control: Acknowledgment (No Parameters) 
Association...

Call Control Procedures
Issue 6  June 1997
2-29
Adjuncts receiving event reports for the calls involved in the Third Party Merge 
receive an acknowledgement, Transfer Event Report, Conference Event Report, 
or Call Ended depending on the role they played in the merge, the type of merge, 
and what they are monitoring.
Third Party Clear Call Procedure
The Third Party Clear Call capability may be used only in Call Control 
associations and may not be used in Third Party Domain (Station) Control...

Messaging Sequences and ASAI
2-30Issue 6  June 1997 
Redirect Call Procedure
Starting with G3V4, the Redirect Call procedure includes the following sequence 
of messages:
1. The ECS sends the adjunct a FACility message with an invoke FIE 
containing:
Operation Value = Redirect Call, 
[the party the call is redirected from] (Party ID IE), 
the number that the call is redirected to (Redirection Number IE), and
[the call_id of the call to be redirected] (Call Identity IE).
For call control coding, see...

Call Control Procedures
Issue 6  June 1997
2-31
2. The ECS listen-disconnects the call and replies with a return result FACility 
message. The invoke-id in the return result has the same value as the 
invoke-id in the Listen Disconnect request. For coding, see ‘‘Call Control: 
Acknowledgment (No Parameters) Association Continues’’ on page 5-61 of 
Chapter 5, “Byte Level Messages.”
Third Party Listen Reconnect Procedure
NOTE:
Third Party Listen Reconnect capability may only be used in the Third Party...

Messaging Sequences and ASAI
2-32Issue 6  June 1997 
Notification Association Procedure
An adjunct can request that the ECS supply event reports over three types of 
domains: ACD splits, Vector Directory Numbers (VDNs) and trunk groups. The 
ACD split domains cannot be administered as controlled splits or vector-controlled 
splits. The event reports provide the adjunct with call related information.
The event reports for these domains all contain a call identifier that associates 
call-related event...

Notification Association Procedure
Issue 6  June 1997
2-33
5. If, during the normal course of event reporting, the ECS has reason to 
terminate the event reporting (such as the domain being administered out 
of existence), the ECS sends a RELease COMplete message to terminate 
the association. The message contains an invoke FIE with:
Operation Value = Notification Ended and 
a cause (Cause IE).
For coding, see ‘‘switch Ends Notification Reporting Association’’ on page 
5-105 of Chapter 5, “Byte Level...

Messaging Sequences and ASAI
2-34Issue 6  June 1997 
Routing Association Procedure
The ECS can ask the adjunct to supply a route for an incoming call.
1. The ECS sends a REGister message containing an invoke FIE with:
Operation Value = Route, and
parameters containing [CPN/BN] (Calling Party Number IE
or Trunk Identification),
9 
the dialed number (Called Party Number IE),
the call identifier for the call to be routed (Call Identity IE), 
the VDN making the route request (Domain IE),
10 
[PRI Lookahead...