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

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

Here you can view all the pages of manual Lucent Technologies DEFINITY Enterprise Communications Server Release 5, CallVisor, ASAI Protocol Reference Instructions Manual. The Lucent Technologies manuals for Communications System are available online for free. You can easily download all the documents as PDF.

Page 121

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...

Page 122

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...

Page 123

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...

Page 124

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...

Page 125

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...

Page 126

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...

Page 127

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...

Page 128

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...

Page 129

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* 

Page 130

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...
Start reading Lucent Technologies DEFINITY Enterprise Communications Server Release 5, CallVisor, ASAI Protocol Reference Instructions Manual

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

All Lucent Technologies manuals