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

Facility Information Element (FIE) General Description
Issue 6  June 1997
1-5
Facility Information Element (FIE)
General Description
The CCITT Q.932 Facility Information Element (FIE) identifies the capability being 
requested for or responded to within an association.   The FIE carries ASAI 
capability information across the ASAI. At most, one FIE may be contained in a 
REGister, FACility, or RELease COMplete message. All REGister and FACility 
messages contain an FIE. All RELease COMplete messages used...

Introduction to Layer 3 Protocol
1-6Issue 6  June 1997 
FIE Acknowledgements
ASAI Capability invocations may be:
The messaging procedures in Chapter 2, ‘‘Messaging Sequences and ASAI’’ 
explain when capability invocations require an acknowledgement. Within an ASAI 
association, an acknowledgement uses the same invoke-id and CRV in the Return 
Result or Return Error component as was present in the invoke request.
An endpoint need not wait for a capability to be acknowledged before invoking 
another...

Facility Information Element (FIE) General Description
Issue 6  June 1997
1-7
ASAI permits the rejecting endpoint to send the Reject component in either:
nA FACility message if the rejecting endpoint permits the requesting 
endpoint to continue the association and retry
nA RELease COMplete message if the rejecting endpoint terminates the 
association when an FIE protocol error occurs
Of these options, the ECS always sends a Reject component in a RELease 
COMplete message to terminate any association...

Introduction to Layer 3 Protocol
1-8Issue 6  June 1997 
4. When an ASAI endpoint invokes an operation, it uses an available 
invoke-id in the FIE. If the capability is acknowledged, then the invoke-id 
state changes to “in-use.” If the operation is not acknowledged, then the 
invoke-id state remains “available.”
5. An endpoint may assign invoke-id values in any order; they do not have to 
be sequential. Therefore, an endpoint must be able to receive invoke-ids in 
any order.
6. When an ASAI endpoint...

Aborting an ASAI Association
Issue 6  June 1997
1-9
Aborting an ASAI Association
Once an ASAI endpoint has started processing an ASAI request and finds, for 
some reason, that it cannot continue to process the request, the endpoint may 
abort the association. The abort mechanism may be used:
nWhen internal constraints within the ASAI endpoint terminate processing
nWhen a capability request is made on the wrong association
nWhen an error, unexpected, or abnormal condition occurs within the ASAI 
endpoint...

Introduction to Layer 3 Protocol
1-10Issue 6  June 1997  

Issue 6  June 19972-1
2
Messaging Sequences and ASAI
This chapter describes the ASAI message sequences for the ASAI capabilities. 
These message descriptions include information necessary for understanding the 
procedures, such as the message direction, message type (REGister, FACility, or 
RELease COMplete), the FIE component type, Operation Value, and the 
parameters within the FIE. 
The descriptions provided in this chapter focus on the information flowing across 
the ASAI. They are not bit-level...

Messaging Sequences and ASAI
2-2Issue 6  June 1997 
All procedures implicitly include the denial, association termination, protocol 
violation, reject, and abort messaging.
The message procedures are presented in this chapter in the following order:
nCommon Capabilities (Event Reports)
nCall Control Association
nDomain (Station/ACD) Control Association
nNotification Association
nRouting Association
nRequest Feature Association
nValue Query Association
nSet Value Association
nEnding an ASAI Association...

Common Capabilities
Issue 6  June 1997
2-3
Common Capabilities
The Event Report capability is common to certain other capability groups that 
require message procedure instructions.
Event Reports
The ECS sends event reports to an adjunct for controlled calls (Third Party or 
Domain) and monitored calls. A call becomes either controlled or monitored in the 
following circumstances:
nThe adjunct invoked a Third Party Make Call capability to set up the call 
(the call is controlled). Event reports are sent...

Messaging Sequences and ASAI
2-4Issue 6  June 1997 
3. Call Ended Event Reports, which terminate a Call Control association. 
A RELease COMplete message carries the call ended operation and 
terminates the association. Within a notification association, a FACility 
message carries the Call Ended operation so that the association is not 
terminated and notification of any future calls will continue to occur.
Events may be sent to monitoring, call control, and domain control adjuncts as a 
result of...