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

Value Query Association
Issue 6  June 1997
2-45
Operation Value=Value Query, and
a parameter containing the Call Forwarding status (Status IE), 
a parameter containing the forwarded to extension (Redirection 
Number IE).
For coding, see ‘‘Response to Station Call Forwarding Status Query’’ on 
page 5-159 of Chapter 5, “Byte Level Messages.”
Station Status Query Procedure
The adjunct queries the ECS for status information on an extension.
1. The adjunct sends a REGister message to query for extension...

Messaging Sequences and ASAI
2-46Issue 6  June 1997 
Call Classifiers Query Procedure
The adjunct queries the ECS for the number of idle/in-use classifiers.
NOTE:
Starting with R5.5, if the USA Default Algorithm? field is set to n on the 
System Parameters OCM Call Classification form, the response to this 
query will provide the total number of ports for the TN744D and TN2182B 
boards (and any later versions) that are idle and in-use.This means that the 
response will not include any TN744C ports or...

Value Query Association
Issue 6  June 1997
2-47
Operation Value = Value Query, and 
parameters containing a list of call_ids (Call Identifier IE), 
the party_id of the principal’s extension on the call (Party ID IE), and
the state of the principal’s extension on the call (Specific Event IE).
For coding, see ‘‘Response to Call Query’’ on page 5-163 of Chapter 5, 
“Byte Level Messages.”
The contents of the Facility IE, ‘‘Response to Call Query’’ on page 5-163 in 
Chapter 5, after the invoke identifier are...

Messaging Sequences and ASAI
2-48Issue 6  June 1997 
For coding, see ‘‘Extension Type/Class Information Query’’ on page 5-148 
of Chapter 5, “Byte Level Messages.”
2. The ECS replies with a RELease COMplete message containing a return 
result FIE with:
Operation Value = Value Query, and 
a parameter containing the extension type
16 [and the class of the
station]17 (Domain IE). 
For coding, see ‘‘Response to Extension Information Query’’ on page 
5-167 of Chapter 5, “Byte Level Messages.”
Agent Login...

Value Query Association
Issue 6  June 1997
2-49
Integrated Directory Database Query Procedure
This query allows an application to pass the ECS an extension number and query 
for the corresponding name in the Integrated Directory database.
1. The adjunct sends a REGister message to query for an Integrated 
Directory name. The message contains an invoke FIE with:
Operation Value=Value Query, and 
parameters for 
a name database query (Domain IE), and 
an extension (Domain IE).
The domain type in the...

Messaging Sequences and ASAI
2-50Issue 6  June 1997 
Set Value Association
All set value requests are invocations of the ASAI Set Value Capability.
Activate Message Waiting Lamp Procedure
The adjunct turns on a message waiting lamp (MWL) at a given extension.
1. The adjunct sends a REGister message to light the MWL.
Operation Value = Set Value, and 
parameters for   
MWL Value (Item IE),   
Message waiting On (Status IE), and   
Extension (Called Party Number IE).
For coding, see ‘‘Activate Message...

Set Value Association
Issue 6  June 1997
2-51
Billing Change Request Procedure
The adjunct requests a billing change for a given call.
1. The adjunct sends a REGister message to request a billing change. The 
message contains an invoke FIE with:
Operation Value = Set Value, and 
parameters for   
Flexible Billing (Item IE)   
Call ID (Call Identity IE)   
Billing request type and amount (Generic Billing IE)
For coding, see ‘‘Billing Change Request’’ on page 5-179 of Chapter 5, 
“Byte Level Messages.”
2....

Messaging Sequences and ASAI
2-52Issue 6  June 1997 
Ending an ASAI Association
An ASAI endpoint terminates an association for the following reasons:
nThe ASAI messaging procedure terminates normally. The endpoint sends 
the RELease COMplete message prescribed by the messaging procedure 
for the type of association that is in progress. ASAI procedures use 
RELease COMplete messages containing either (or both) an FIE and/or 
Cause IE. The FIE carries an Invoke, Return Result, or Return Error 
component....

Ending an ASAI Association
Issue 6  June 1997
2-53
— The Call Control capabilities (Third Party Hold, Third Party Drop, 
Third Party Merge, Third Party Reconnect, and Third Party 
Relinquish control).
— The Stop Notification capability request within a Notification 
association.
— The Auto Dial capability in a Domain (Station) Control association.
nA RELease COMplete message if the denying endpoint does not allow the 
association to continue. The ECS always uses a RELease COMplete 
message for any denial...

Messaging Sequences and ASAI
2-54Issue 6  June 1997 
contains: invoke FIE with Operation Value = Abort, and an optional cause (Cause 
IE). The ECS always supplies a cause when it aborts an 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 type of association;
nWhen an error, unexpected, or abnormal condition occurs within the ASAI 
endpoint that terminates processing.
Special cases...