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 151
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...
Page 152
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....
Page 153
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...
Page 154
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...
Page 155
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...
Page 156
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...
Page 157
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...
Page 158
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...
Page 159
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
Page 160
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...