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

							Codeset 0 Information Elements
Issue 6  June 1997
4-15
The ECS permits a maximum of 15 address digits and sends/receives only those 
ASCII characters shown above. Any adjunct must:
a. Accept all characters shown.
b. Not send characters other than those shown. Doing so results in the ECS 
denying (return error) the request.
There may be instances of event reports where an address for the calling party is 
not available to the ECS. In such cases, the Calling Party Number IE is present in 
the event reports where ASAI requires it as a mandatory event report item. 
However, in such a case, the Address field is not present; the length of the 
resulting IE is one (1); the Type of Address and Numbering Plan are present. Any 
adjunct interfacing to the ECS should be prepared to receive the Calling Party 
Number IE in this format.
The adjunct should also be prepared to accept the default calling party number 
values “#####,” or “*****.” Address DigitsBits Address Digit
7654321 value
0110000 0
0110001 1
0110010 2
0110011 3
0110100 4
0110101 5
0110110 6
0110111 7
0111000 8
0111001 9
0100011 #
0101010 * 
						

							Information Elements
4-16Issue 6  June 1997 
Cause
The Cause IE shown in Figure 4-8 gives the reason for generating certain 
messages to provide diagnostic information (see Table 4-4).
.
NOTE:
PRI has an optional diagnostic field; ASAI does not use this field.
Figure 4-8. Cause Information Element8 7 6 5 4321
Cause
0  0 0 0 1000  Byte1
information element identifier
Length of cause information element 2
1Coding
Standard0
SpareLocation 3
Ext
1 Cause Value 4
Ext (Class) (value in class)
Diagnostics omitted - Note 1   5, etc. 
						

							Codeset 0 Information Elements
Issue 6  June 1997
4-17
CodingBits
Standard76
0 0 CCITT standard cause value
1 1 ASAI specific cause value
ASAI 
LocationBits
Code Points4321
0 0 0 0 user (for example, adjunct)
0 0 0 1 private network serving local user
(PBX switch)
ASAI Cause
Value
EncodingsThe cause value is divided into two fields, a class and a 
value within the class. Diagnostic information is optional.
ASAI CLASS
Field
EncodingsClass(0 0 0)
Class(0 0 1)
Class(0 1 0)
Class(0 1 1)
Class(1 0 0)
Class(1 0 1)
Class(1 1 0)normal event
normal event
resource unavailable
service or option not available
service or option not implemented
invalid message (parameter out of range)
protocol error (unknown message) 
						

							Information Elements
4-18Issue 6  June 1997 
Table 4-4. ASAI Coding Standard Zero Causes Returned by the ECS
Coding Standard Zero (0 0) Cause Values
Class Value # Cause
7 6 5 4 3 2 1 
0 0 0 0 0 0 1 1 Unassigned Number
0 0 1 0 0 0 0 16 Normal Clearing
0 0 1 0 0 0 1 17 User Busy
0 0 1 0 0 1 0 18 No User Responding
0 0 1 0 1 0 1 21 Call Rejected
0 0 1 0 1 1 0 22 Number Changed/SIT — Vacant
0 0 1 1 1 0 0 28 Invalid Number/Domain/SIT — Ineffective other
0 0 1 1 1 0 1 29 Facility Rejected
0 0 1 1 1 1 1 31 Normal, Unspecified/SIT — unknown
0 1 0 0 0 1 0 34 No Circuit or Channel Available/SIT — No circuit
0 1 0 1 0 0 1 41 Temporary Failure
0 1 0 1 0 1 0 42 Switching Equipment Congestion/SIT — reorder
0 1 1 0 0 1 0 50 Requested Facility Not Subscribed/Provisioned
0 1 1 0 1 0 0 52 Outgoing Calls Barred
0 1 1 1 0 1 0 58 Bearer Capability not Currently Available
1 0 1 0 0 0 1 81 Invalid CRV
1 0 1 0 0 1 0 82 Identified Channel does not exist
1 0 1 1 0 0 0 88 Incompatible Destination
1 0 1 1 1 1 1 95 Invalid Message, Unspecified
1 1 0 0 0 0 0 96 Mandatory Information Element missing
1 1 0 0 0 0 1 97 Message Non-Existent/Not Implemented
1 1 0 0 0 1 0 98 Message Not Compatible with Call State
1 1 0 0 0 1 1 99 Information Element non-existent
1 1 0 0 1 0 0 100 Invalid Information Element Contents
1 1 0 0 1 1 0 102 Recovery on Timer Expiry
1 1 0 1 1 1 1 111 Protocol Error
1 1 1 1 1 1 1 127 Normal, Unspecified 
						

							Codeset 0 Information Elements
Issue 6  June 1997
4-19
Table 4-5. ASAI Coding Standard Three Causes Returned by the ECS
In addition to the ASAI causes shown in Table 4-4 and Table 4-5, certain ASAI 
event reports may carry any cause that the ECS receives from a PRI network.Coding Standard Three (1 1) Cause Values
Class Value # Cause
7 6 5 4 3 2 1
0 0 0 1 0 1 0 10 Agent on hook
0 0 0 1 0 1 1 11 Agent not member of split
0 0 0 1 1 0 0 12 Agent state inconsistent with request
0 0 0 1 1 0 1 13 Agent logged into maximum number of splits
0 0 0 1 1 1 0 14 Incorrect number of agent login digits
0 0 0 1 1 1 1 15 Agent not logged in
0 0 1 0 0 0 0 16 In Same State
0 0 1 0 0 0 1 17 Timed Answer
0 0 1 0 0 1 0 18 Voice Energy Answer
0 0 1 0 0 1 1 19 No Answer 
0 0 1 0 1 0 0 20 Trunks not available
0 0 1 0 1 0 1 21 Classifiers not available
0 0 1 0 1 1 0 22 Queues full
0 0 1 0 1 1 1 23 Remains in Queue 
0 0 1 1 0 0 0 24 Answering Machine
0 0 1 1 0 0 1 25  Call Forwarding (Redirection)
0 0 1 1 0 1 0 26 Cover, Principal Busy (Redirection)
0 0 1 1 0 1 1 27 Out of Service 
0 0 1 1 1 0 0 28Cover, Don’t Answer (Redirection)
0 0 1 1 1 1 0 30 Redirected
0 0 1 1 1 1 1 31 Send All Calls (Redirection)
Cover All Calls (Redirection)
Go to Cover Active (Redirection)
Adjunct Redirected Call (Redirection)
Cover, All Call Appearances Used (Redirection)
0 1 0 0 1 1 0 38 Network out of order 
0 1 0 1 0 0 0 40 Resources not available
0 1 0 1 0 0 1 41 Hunt group/split not administered correctly
0 1 0 1 0 1 0 42 Reorder/Denial
0 1 0 1 0 1 1 43 Permission Denied
0 1 0 1 1 1 0 46 Administration in progress
0 1 1 0 1 0 1 53 Feature Request Rejected
0 1 1 1 1 1 1 63 Service or Option Not available 
1 0 0 1 1 1 1 79 Service or Option Not Implemented 
1 0 1 0 0 0 0 80 Incompatible Options
1 0 1 0 1 1 0 86 Call with Requested Identity has been Terminated
1 0 1 0 1 1 1 87 Internal ECS Audit 
						

							Information Elements
4-20Issue 6  June 1997 
Call Identity
The ECS uses the Call Identity IE shown in Figure 4-9 to pass a call identifier to 
an adjunct that the adjunct might use later to start a new association for 
controlling the call. The ECS currently uses the root portion of an internal call 
identifier for the call identity; the current call identity is always 16 bits in length. 
The first byte is the high-order value and the second byte is the low-order value for 
the call_id (if the call_id is greater than 255). For call_ids less than 255, the first 
byte is 0, and the second byte contains the call_id value.
NOTE:
Future ASAI specifications with bridging may increase the size of the Call 
Identity IE beyond the present two bytes.
.
Figure 4-9. Call Identity Information Element
The ECS sends two-byte call identifiers. Since various DEFINITY ECS switches 
have different call capacities, host platforms should not make any assumptions 
about the range or sequencing of call identifiers. Hosts should be prepared to 
accept any values that can be encoded in the Call Identity bytes in any order.87654321
Call Identity
00010000Byte 1
information element identifier
00000010
Length of call identity contents    2
Call Identity  3
(first byte)
Call_id  3a
(second byte) 
						

							Codeset 0 Information Elements
Issue 6  June 1997
4-21
Connected Number
The Connected Number IE shown in Figure 4-10 shows the address of the 
endpoint connected to a call. The connected number may be different from the 
calling party or called party number because the call may have interacted with a 
number of ECS features.
Figure 4-10. Connected Number Information Element8 7654321
Connected Number
0 0001100Byte 1
information element identifier
Length of Connected Number Information Element 2
1
Ext3
Type of Address Numbering Plan
0
SpareAddress 4
etc.
Extension Bit0: description extends into next byte
1: last byte of the description element
Type ofBits
Address765
000 unknown
0 0 1 international
0 1 0 national
1 0 0 subscriber
NumberingBits
Plan4321
0000 unknown
0001 ISDN/telephony numbering plan
0010 reserved
1001 private numbering plan 
						

							Information Elements
4-22Issue 6  June 1997 
The ECS permits a maximum of 15 address digits and sends/receives only those 
ASCII characters shown above. Any adjunct must:
a. Accept all characters shown.
b. Not send characters other than those shown. Doing so results in the ECS 
denying (return error) the request.
In certain ASAI messages (Transfer Event Report, for example) the Connected 
Number IE appears in a paired list of IEs. To keep one-to-one correspondence in 
such a list, the Connected Number IE appears even if an Address is not known. In 
such a case, the value of the length field is one, and the Address field is absent. 
Any adjunct interfacing to the ECS should be prepared to receive the Connected 
Number IE in this format.
The adjunct should be prepared to accept the Connected number default values 
“#####,” or “*****.” Address DigitsBits Address Digit
7 654321 value
0 110000 0
0 110001 1
0 110010 2
0 110011 3
0 110100 4
0 110101 5
0 110110 6
0 110111 7
0 111000 8
0 111001 9
0 100011 #
0 101010 * 
						

							Codeset 0 Information Elements
Issue 6  June 1997
4-23
Date/Time
The Date/Time IE shown in Figure 4-11 provides the date and/or time.
Figure 4-11. Date/Time Information Element
NOTE:
Bytes 3 through 8 are binary (bit 1 being the least significant bit).87654321
Date/Time
0 0101001 Byte 1
Information Element Identifier
Length of Date/Time contents 2
Year 3
Month 4
Day 5
Hour 6
Minute 7
Second    8* 
						

							Information Elements
4-24Issue 6  June 1997 
Progress Indicator
The Progress Indicator IE shown in Figure 4-12 conveys information from the PRI 
network to an ASAI application. The ECS passes this information without altering 
it.
.
Figure 4-12. Progress Indicator
Coding standard (byte 3)
Location (byte 3)8 7 6 5 4321
Progress Indicator
0 0 0 1 1110Byte1
Information element identifier
Length of Progress indicator contents 2
1 Coding 0
Location 3
ext standard spare
1
Progress description 4
ext
Bits
76
0 0 CCITT standard coding
Bits
4321
0000User
0001public network serving local user
0100public network serving remote user
0101private network serving remote user