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 141
Codeset 6 Information Elements Issue 6 June 1997 4-35 Data Item IE The Data Item IE shown in Figure 4-20 returns information that an adjunct has queried for. The Data Item information element contains one information value. The data item type identifies what value is present in the IE. Presently, the Data Item IE is used in the response to the Integrated Directory Database query and in the reporting of ISDN Charge Advice. Figure 4-20. Data Item Information Element Data Item Type (octet 3): This byte...
Page 142
Information Elements 4-36Issue 6 June 1997 Data Item Value This value may be either an integer value, or an ASCII string. Charge amounts are encoded as integers and names are encoded as ASCII strings. If an integer is encoded, then 7 bits of each octet are used. The high bit is an extension bit, and is set to 0 except in the last octet of the value. The most significant octets are ordered first. For example, 400 (decimal), which is 0x190 (hexadecimal) is encoded in two octets: ASCII strings are...
Page 143
Codeset 6 Information Elements Issue 6 June 1997 4-37 Domain The Domain IE shown in Figure 4-21 specifies the domain for which an event is reported. . Figure 4-21. Domain Information Element8 7654321 Domain Information 0 1001001Byte1 Information element identifier Length of Domain Information contents 2 1 Domain Type 3 Ext. 0/1 Address 4* Ext Domain TypeBits 7 6 5 4 3 2 1 0 0 0 0 0 0 0 Adjunct-Monitored call audit 0 0 0 0 0 0 1 Group Extension (includes ACD split) 0 0 0 0 0 1 1 Extension 0...
Page 144
Information Elements 4-38Issue 6 June 1997 nIf the domain type is a group extension, an extension, logical agent, trunk access code, VDN, announcement, or data extension, the address field may contain the extension number (in ASCII). 1 In an incoming Domain IE the ECS will parse, the only ASCII characters the ECS permits are the digits 0 through 9. 2 There may be instances of event reports where an address should be included, but an address is not available to the ECS. In such cases, the address...
Page 145
Codeset 6 Information Elements Issue 6 June 1997 4-39 nIf the domain type is “Talk State,” the address field contains a single byte coded as follows: nIf the domain type is “Station Type,” the address field contains a single byte coded as follows: nIf the domain type is “ASAI,” the address field contains a single byte coded as follows: nIf the Domain type is Reason Codes, the address field contains a single byte with a binary value between 1-9. nFor other domain types, the address field is not used...
Page 146
Information Elements 4-40Issue 6 June 1997 Facility Information Element (FIE) The Facility information element (FIE) identifies and contains an ASAI capability request or response. CCITT Recommendation Q.932 uses an X.209 encoding of X.229 Protocol Data Units. The FIE only appears once in a message. The maximum length of the BRI message determines the number of bytes that the FIE may occupy; therefore, it imposes an upper bound on the length of an IE. Table 4-6 to Table 4-9 show the FIE encoding....
Page 147
Codeset 6 Information Elements Issue 6 June 1997 4-41 t 1. The component length is coded to indicate the number of bytes contained in the component (excluding the component type tag and the component length bytes). 2. This ASAI implementation never uses or expects linked identifiers. Refer to the Adjunct/Switch Application Interface (ASAI) Specification for a description. 3. Contains capability parameter(s) for the Invoke component type. Table 4-6. Invoke Component Invoke component SectionMandatory...
Page 148
Information Elements 4-42Issue 6 June 1997 1. The component length is coded to indicate the number of bytes contained in the component (excluding the component type tag and the component length bytes). 2. The sequence tag is an anomaly in the Return Result component. Although other components are similarly structured, the Return Result component is the only component with a sequence tag. This arises from a specific backward compatibility need for the Q.932 Return Result component with respect to other...
Page 149
Codeset 6 Information Elements Issue 6 June 1997 4-43 . 1. The component length is coded to indicate the number of bytes contained in the component (excluding the component type tag and the component length bytes). 2. The ASAI specification and the Q.932 specification have an “error value” here in the return error component. Both ASAI and Q.932 have the same encoding for the “error value tag” in the return error component and the “operation value tag” in the Invoke component. This means that what...
Page 150
Information Elements 4-44Issue 6 June 1997 Component/Content Length Lengths up to 127 bytes are coded using the short form of Recommendation X.209: bit 8 is set to zero and the remaining seven bits are a binary encoding of the length with bit 1 the least significant bit. This length encoding is identical to that of Recommendation Q.931 for lengths up to 127 bytes. . Figure 4-23. Format of the Length Field (Short Form) 1. The component length is coded to indicate the number of bytes contained in the...