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

							Codeset 6 Information Elements
Issue 6  June 1997
4-45
If the length of the contents is greater than 127 bytes, then the long form of the 
length of the contents is used. The long form length, in the ECS/ASAI, is two 
bytes.
3 Bit 8 of the first byte is coded 1, and bits 1 to 7 of the first byte encode a 
number on less than the size of the length in bytes as an unsigned binary number 
whose MSB and LSB are bits 7 and 1, respectively. The length itself is encoded as 
an unsigned binary number whose MSB and LSB are bit 8 of the second byte and 
bit 1 of the last byte, respectively. This binary number shall be encoded in the 
fewest possible bytes, with no leading bytes having the value 0.
ASAI permits the length to be encoded in up to 127 bytes. However, two bytes 
suffice for encoding the maximum length of BRI messages.
Figure 4-24. Long Form of the Length Field in the ECS Implementation
(2 Bytes)
Component Type Tag
Table 4-10 shows the coding of the component type tag (control type).
3. ASAI permits the length to be encoded in up to 127 bytes. However, two bytes suffice for 
encoding the maximum length of BRI messages.
8 7 65432 1
10 00000 1
MSB LSB
MSB
Length of contents
(one byte in the ECS implementation)
LSB
Table 4-10. Component Type Tag
87654321
Invoke 10100001
Return result10100010
Return error 10100011
Reject 10100100 
						

							Information Elements
4-46Issue 6  June 1997 
Invoke Identifier Tags
An invoke identifier is used to identify an operation invocation and is present in the 
return result or return error response. When a protocol problem occurs with an 
FIE component, a Reject component contains the invoke-id of the problem 
component if it can be obtained. If the invoke-id cannot be ascertained, the Reject 
component contains a null invoke-id. Invoke identifiers are one byte long. The null 
invoke-id has zero length. Table 4-11 shows the coding of the component 
identifier tags.
Invoke Identifier
The invoke identifier is a binary field assigned by the sender of the Facility 
information element when the Component type tag in byte 4 indicates an invoke. 
For the remaining Component type tags (for example, return result, return error, 
and reject), the “invoke identifier” corresponds to one received in a Facility 
information element with an Invoke component type tag.
Invoke identifiers are coded in a single byte.
Operation Value Tag
Table 4-12 shows the coding for the operation value tag.
Table 4-11. Invoke Identifier Tag Coding
87654321
Invoke identifier 00000010
Null 00000101
Table 4-12. Operation Value Tag Coding
87654321
Operation value tag 0 0 0 0 0 0 1 0 
						

							Codeset 6 Information Elements
Issue 6  June 1997
4-47
Sequence Value Tag
The Return Result component contains a sequence value tag when an Operation 
Value and result are present. The sequence Value Tag, Operation Value Tag, and 
(non-null) result must all be present together, or absent from a Return Result 
component. Table 4-13 shows the encoding for the sequence tag.
Operation Value
The Operation Value specifies the ASAI capability being requested or responded 
to. Values are identified in bytes 12 and 11 of the Invoke and Return Result 
components, respectively. Table 4-14 shows the ASAI Operation Values; the ECS 
implementation currently does not use all Operation Values. Those that are not 
currently in use are marked NOT USED or RESERVED.
Table 4-13. Sequence Tag Coding
Sequence Tag 00110000 
						

							Information Elements
4-48Issue 6  June 1997 
Table 4-14. Operation Value/Error Value Coding
ASAI Operation Value 87654321
Third Party Make Call 10000011
Third Party Answer 10000100
Third Party Selective Hold 1 0 0 0 0 1 0 1
Third Party Reconnect 10000110
Third Party Transfer NOT USED10000111
Third Party Selective Drop 10001000
Third Party Merge 1 0 0 0 1 0 0 1
Event Notification Request 1 0 0 0 1 0 1 0
Reserved 10001011
Value Query 10001100
Set Value 10001101
Request Feature 1 0 0 0 1 1 1 1
RESERVED10010000
RESERVED10010001
RESERVED10010010
Third Party Clear Call 10010011
Event Notification Cancel 1 0 0 1 0 1 0 0
Event Report 10010101
RESERVED10011010
RESERVED10011011
Route 10110000
RESERVED10110001
Restart 10110010
Heartbeat 1 0 1 1 0 0 1 1
Third Party Conference NOT USED10110100
Third Party Relinquish Control 1 0 1 1 0 1 0 1
Third Party Take Control 1 0 1 1 0 1 1 0
Route Select 10110111
RESERVED10111000
Route End 10111001
Call Ended 10111011
Notification Ended 10111100
Third Party Make Call Proceed 10111101
Abort 10111110
Response Continued 10111111
RESERVED11000000
Route Proceed NOT USED11000001
Third Party Domain (Station) Control 
Request11000100
Third Party Domain (Station) Control 
Ended11000101
Third Party Auto Dial 11000110 
						

							Codeset 6 Information Elements
Issue 6  June 1997
4-49
Error Value Tag
Error reporting is specific to each capability. Table 4-15 shows the ASAI coding 
for the error value tag.
Error Value
The error value is always encoded to be the Operation Value of the requested 
service that returned the error. Table 4-15 shows these encodings.
Problem Tag
The problem tag found in the Reject component supplies information about why 
an FIE was rejected. The possible protocol problems are divided into related 
groups. Table 4-16 indicates the tags for these groups. Table 4-17 to Table 4-20 
give encodings for each set of problems within a problem tag. All ASAI problem 
codings are shown for completeness. Adjuncts should be prepared to accept any 
of them even though any given ECS release may only send a subset from the full 
set. If an adjunct receives an FIE that it cannot parse, it has the option of using a 
reject FIE (with problem tags), aborting the association, or sending a RELease 
COMplete message with a protocol error cause. These options all have the same 
effect from the ECS point of view.
Stop Call Notification 1 1 0 0 0 1 1 1
Send DTMF 11001000
Redirect Call 11001001
Third Party Listen Disconnect 1 1 0 0 1 0 1 0
Third Party Listen Reconnect 1 1 0 0 1 0 1 1
RESERVED11001100
Table 4-15. Error Value Tag Coding
87654321
Error value tag 00000010
Table 4-14. Operation Value/Error Value Coding — Continued
ASAI Operation Value 87654321 
						

							Information Elements
4-50Issue 6  June 1997 
General Problem:
Table 4-16. Problem Tag Coding
87654321
General problem 1 0 0 0 0 0 0 0
Invoke problem 10000001
Return Result problem10000010
Return Error problem 10000011
Table 4-17. General Problem Coding
87654321
Unrecognized component 0 0 0 0 0 0 0 0
Mistyped component 0 0 0 0 0 0 0 1
Badly structured component 0 0 0 0 0 0 1 0
Unrecognized component The component type tag is not a 
value in Table 4-9.
Mistyped component A mandatory part of the component 
structure is missing.
Badly-structured component The structure of the component 
cannot be parsed into one of the 
appropriate types of structures for 
the component type (Table 4-6, 
Table 4-7, Table 4-8, and Table 
4-9); could be a length error.
Table 4-18. Return Result Problem Coding
87654321
Unrecognized invocation 0 0 0 0 0 0 0 0
Result response unexpected 0 0 0 0 0 0 0 1
Mistyped result 00000010 
						

							Codeset 6 Information Elements
Issue 6  June 1997
4-51
Return Result problem:
Invoke-problem: Unrecognized invocation: The Invoke-id in a Return Result 
component is not an active 
Invoke-id; for example, there is no 
such operation in progress.
Result response unexpected: The Invoke-id in a Return Result 
component corresponds to an 
operation for which a Return result 
is not expected.
Mistyped result Indicates the type of the result 
argument used is not the “Q.931 IE 
tag” shown in Figure 4-25.
Table 4-19. Invoke Problem Coding
87654321
Duplicate invocation 0 0 0 0 0 0 0 0
Unrecognized operation 0 0 0 0 0 0 0 1
Mistyped argument 0 0 0 0 0 0 1 0
Resource limitation 00000011
Initiator releasing identifier 0 0 0 0 0 1 0 0
Unrecognized linked identifier 0 0 0 0 0 1 0 1
Linked response unexpected 0 0 0 0 0 1 1 0
Unexpected child operation 0 0 0 0 0 1 1 1
Duplicate invocation: An Invoke-id in an invoke component is 
already active.
Unrecognized operation: The type of the operation argument 
supplied is not that shown in Table 4-12, 
or the Operation Value is not a supported 
Operation Value from Table 4-14.
Mistyped argument: Indicates that the type of the operation 
argument is not the “Q.931 IE tag” shown 
in Figure 4-25.
Resource limitation: The endpoint is not able to process the 
invoked capability due to a resource 
limitation.
Initiator releasing:NOT USED 
						

							Information Elements
4-52Issue 6  June 1997 
Return Error problem:
Using Existing Q.931 IEs as Parameters
All ASAI capabilities pass Q.931 IEs as parameters within the FIE parameters 
field. When Q.931 information elements (codesets 0 and 6) are parameters for a 
component, an X.209 data element encapsulates them, thereby retaining the 
Q.931 coding for these information elements. However, ASAI prohibits 
encapsulation of an FIE in this manner. The Q.931 information elements are 
grouped by codeset, and the IEs within each grouping are arranged in order of 
their byte identifiers (see Coding Rules). The “Q.931 information elements tag” 
precedes all Q.931 IEs and encapsulates them. See Figure 4-25. Unrecognized linked identifierDOES NOT APPLY
Linked response unexpected: A linked invoke-id was not expected.
Unexpected child operation:DOES NOT APPLY
Table 4-20. Return Error Problem Coding
87654321
Unrecognized invocation 0 0 0 0 0 0 0 0
Error response unexpected 0 0 0 0 0 0 0 1
Unrecognized error 0 0 0 0 0 0 1 0
Unexpected error 0 0 0 0 0 0 1 1
Mistyped parameter 0 0 0 0 0 1 0 0
Unrecognized invocation: The Invoke-id in a return error 
component is not an active 
Invoke-id; for example, there is no 
such operation in progress.
Error response unexpected: The Invoke-id corresponds to an 
operation for which a return result is 
not expected.
Unrecognized error: The error value is not recognized. 
This means that the error value is 
not a recognized Operation Value.
Unexpected error: The Error Value is recognized, but 
is not expected for the operation 
that the Invoke-id identifies.
Mistyped parameter: The type of the result argument is 
not the Q.931 IE tag shown in
Figure 4-25. 
						

							Codeset 6 Information Elements
Issue 6  June 1997
4-53
Figure 4-25. Encapsulation of Q.931 Information Elements
87654321
01000000
Q.931 information elements tag
Q.931 information elements length
(X.209 encoded -- see section “Length of Each Component or Contents”)
First Q.931 information element
Second Q.931 information element
.
.
.
.
Last Q.931 information element 
						

							Information Elements
4-54Issue 6  June 1997 
Feature
The Feature IE shown in Figure 4-26 specifies which feature is being requested. It 
is also used to indicate the availability of a feature in a Call Offered Event Report. 
(Currently, only Flexible Billing is supplied.)
 
Figure 4-26. Feature Information Element8  7654321
Feature
0  1001000Byte1
Information element identifier
Length of Feature contents 2
1
Feature               3
Ext
ASAI FeatureBits
Encodings:7 6 5 4 3 2 1
0 0 0 0 0 0 0 Reserved
0 0 0 0 0 0 1 Change agent work mode
0 0 0 0 0 1 0 Log in agent
0 0 0 0 0 1 1 Log out agent
0 0 0 0 1 0 0 Reserved
0 0 0 0 1 0 1 Reserved
0 0 0 0 1 1 0  Flexible Billing
0 0 0 0 1 1 1 LWC on NOT USED
0 0 0 1 0 0 0 LWC off NOT USED
0 0 0 1 0 0 1 Reserved
0 0 0 1 0 1 0Call Forward — Activate
0 0 0 1 0 1 1 Call Forward — Cancel
0 0 0 1 1 0 0 Send All Calls — Activate
0 0 0 1 1 0 1 Send All Calls — Cancel