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 111

Message Type Information Element
Issue 6  June 1997
4-5
Thus, both endpoints may assign an identical value and the CRV flag prevents a 
collision in their use.
Although permitted, it is recommended that adjuncts do not initiate associations 
with CRVs in the range 1 to 32, inclusive. Rather, an adjunct might start assigning 
CRVs with the highest possible values and work downwards, or begin assigning 
CRVs at 33 and work upwards.
Message Type Information Element
The message type identifies the function...

Page 112

Information Elements
4-6Issue 6  June 1997 
Codeset Information Elements
Coding Rules
Information element coding follows the rules below.
Two categories of information elements are defined:
nSingle-byte information elements (see Figure 4-3 [a] Single-byte 
information element format)
nVariable length information elements (see Figure 4-3 [b] Variable length 
information element format)
Figure 4-3. Formats of Information Elements
Table 4-3 summarizes the coding of the information element identifier bits....

Page 113

Codeset Information Elements
Issue 6  June 1997
4-7
Where the description of information elements in this specification contains spare 
bits, these bits are indicated as being set to “0.” To allow compatibility with future 
implementations, messages should not be rejected simply because a spare bit is 
set to “1.”
The second byte of a variable length information element indicates the total length 
of the contents of the remainder of that information element. It is the binary coding 
of the number of...

Page 114

Information Elements
4-8Issue 6  June 1997 
Table 4-3. Information Element Identifier Coding
87654321
1 : : ---- Single-byte information elements:
 0
0 :::::::  Variable length information elements:
 Codeset 0
 0001000
 Cause
 0001100 Connected number
 0010000 Call identity
 0010100 Call state
 0011110 Progress Indicator
 0101001 Date/time
 1101100 Calling party number
 1110000  Called party number
 1110100  Redirecting number
 1  110110 Redirection number
 1111001 Restart indicator
 111 1110 User-User...

Page 115

Codeset Information Elements
Issue 6  June 1997
4-9
One common value in the single-byte format is employed in each code set to shift 
from one code set to another. The contents of this shift item identify the code set 
to be used for the following information element(s). The code set in use at any 
given time is referred to as the active code set. By convention, code set 0 is the 
initially active code set. Codeset 6 is used for Lucent Technologies-specific 
supplementary service information elements,...

Page 116

Information Elements
4-10Issue 6  June 1997 
Figure 4-4 shows the single-byte information for the locking shift.
Figure 4-4. Locking Shift to Codeset 68 7654321
Shift Codeset 6
1 0010110Byte1
identification
   
0 in bit position 4
    indicates locking shift 

Page 117

Codeset 0 Information Elements
Issue 6  June 1997
4-11
Codeset 0 Information Elements
The codeset 0 information elements are CCITT-approved and are incorporated in 
the CCITT specification. The ASAI codeset 0 IEs drawn from this specification are 
as follows:
Call State
The Call State information element shown in Figure 4-5 displays the state of a 
CRV and is present in the BRI STATUS message. Since certain ASAI endpoints 
might transmit a BRI STATUS message to the ECS when the endpoint encounters 
a...

Page 118

Information Elements
4-12Issue 6  June 1997 
Called Party Number
The Called Party Number IE shown in Figure 4-6 identifies the destination of a 
call.
Figure 4-6. Called Party Number Information Element8 7654321
Called Party Number
0 1110000 Byte1
information element identifier
Length of Called Party Number Information Element 2
1
Ext 3
Type of Address Numbering Plan
0
SpareAddress Digits 4
etc.
Extension Bit0: description extends into next byte
1: last byte of the description element
Type ofBits...

Page 119

Codeset 0 Information Elements
Issue 6  June 1997
4-13
The ECS permits a maximum of 31 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 called party is 
not available to the ECS. In such cases, the Called Party Number IE is present in 
the event reports...

Page 120

Information Elements
4-14Issue 6  June 1997 
Calling Party Number
The Calling Party Number IE shown in Figure 4-7 identifies the origin of a call.
Figure 4-7. Calling Party Number8 7654321
CallingParty Number
0 1101100 Byte1
information element identifier
Length of Calling Party Number Information Element 2
1
Ext 3
Type of Address Numbering Plan
0
SpareAddress Digits 4
etc.
Extension Bit0: description extends into next byte
1: last byte of the description element
Type ofBits
Address765
000 unknown
0 0 1...
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