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
Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 5, CallVisor, ASAI Protocol Reference Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
Codeset 6 Information Elements Issue 6 June 1997 4-55 Generic Billing Data The Generic Billing Data IE shown in Figure 4-27 specifies the billing for a specified call. It also provides billing information as an event field in the Offered Event and in route requests. . Figure 4-27. Generic Billing Data Information Element8 7654321 0Generic Billing Data 1010110Byte1 Information element identifier 2 Length of Generic Billing Data contents 1 ExtType of Billing Data 3 1 ExtEncoding scheme 4* Billing data (hundreds) 5* Billing data (tens) 6* Billing data (units) 7* Billing data (tenths) 8* Billing data (hundredths) 9* Type of BillingBits Data7 6 5 4 3 2 1 0 0 1 0 0 0 0 New rate 0 0 1 0 0 0 1 Flat rate 0 0 1 0 0 1 0 Premium Charge 0 0 1 0 0 1 1 Premium Credit 0 0 1 1 1 0 0 Free call EncodingBits Scheme7 6 5 4 3 2 1 0 0 0 0 0 1 0 IA5
Information Elements 4-56Issue 6 June 1997 Item The Item IE shown in Figure 4-28 specifies the item being queried or set in the Value Query and Set Value capabilities. NOTE: The ECS permits only one item in a Value Query or Set Value capability invocation. Figure 4-28. Item Information Element8 7654321 Item 0 1001101Byte1 Information element identifier Length of Item contents 2 1 Item (Note) 3 Ext ASAI ITEM Encodings:Bits Item 7 6 5 4 3 2 1 0 0 0 0 0 0 0 Reserved 0 0 0 0 0 0 1 Date/Time 0 0 0 0 0 1 1 MWL Status 0 0 0 1 1 0 1 Agent Login Audit 0 0 1 1 0 1 0 ACD Split NOT USED 0 0 1 1 0 1 1 Party Query Information 0 0 1 1 1 0 0 Call Query Information 0 0 1 1 1 0 1 Extension Query Information 0 0 1 1 1 1 1 Billing Change Request
Codeset 6 Information Elements Issue 6 June 1997 4-57 Lookahead Interflow The ECS passes the PRI Lookahead Interflow IE shown in Figure 4-29 with Call Offered Event Reports. This information element contains the calling information associated with the call at the previous ECS. Thus, when a call interflows from one ECS to another, the second ECS can pass information such as Dialed Number Identification Service (DNIS) to an adjunct on that ECS. . Figure 4-29. Lookahead Interflow Information Element8 7654321 0 1111011Byte1 Length of Lookahead Interflow Contents 2 1Priority Type 3 ext Level Interflow 1 0 0 Time Stamp 4 ext Hours 10 Time Stamp 5 ext Minutes 10 Time Stamp 6 ext Seconds 1/0 DNIS Name Display ext ASCII Characters Type InterflowBits (Byte 3)321 0 0 0 All interflow (reserved) 0 0 1 Threshold interflow (reserved) 0 1 0 Vectoring interflow Priority LevelBits (Byte 3)7654 0 0 0 0 Not in queue 0001Low 0010Medium 0011High 0100Top
Information Elements 4-58Issue 6 June 1997 Time Stamp (Bytes 4-6) Hours: 5 bits: 0 through 23 Minutes: 6 bits: 0 through 59 Seconds: 6 bits: 0 through 59 DNIS NAME Display Characters (Bytes 7 through 21)Variable: 0 through 15 ASCII characters. For interoperation with existing services, these should be printable ASCII characters.
Codeset 6 Information Elements Issue 6 June 1997 4-59 Management Information Element (MIE) The Management Information Element (MIE) shown in Figure 4-30 carries information to suspend and resume alarming on ASAI interfaces. The ASAI subset of the MIE structure and encoding shown here are part of a more general encoding from the ISDN Basic Rate Interface (BRI) Specification. NOTE: BRI permits the parameter bytes (7a through 7c) to be repeated. The ASAI interface currently uses only one parameter in an MIE. With present ASAI use of the MIE, the parameter bytes are present only when the Operation Class is Confirmed Operation. Figure 4-30. Management Information Element Transaction Reference (byte 4): ASAI supports only a synchronous use of the MIE. This requires that the Transaction Reference value be zero. Non-zero values are used only for asynchronous management operations. The ECS takes the transaction value from a request (in this case, zero) and returns it in the response to that request. 87654321 Management Information 01111010Byte1 Information element identifier Length of Contents 2 Management Protocol Discriminator 3 0 000001 1 0/1 Transaction Reference 4 ext0 0 0 0 0 0 0 0/1 OP Classspare Op Type 5 ext x x 0 0 0/1 Operation Value 6 ext 0/1 Parameter Identifier *7a ext Length of parameter *7b Parameter Value *7c
Information Elements 4-60Issue 6 June 1997 Operation Class (byte 5, bits 5 through 7): may contain the following encodings on the ASAI interface: Operation Type (byte 5, bits 1 through 2): has only one permitted encoding on an ASAI interface. Operation Value (byte 6): has only one permitted encoding on an ASAI interface. Parameter Identifier (byte 7a through 7c): only one parameter is permitted on an ASAI interface. The Permitted values for the Alarm Status Parameter are: If the ECS rejects a MIM message, the Operation Class is set to reject, the Operation Type is irrelevant and is always encoded as “0 0”, and the Operation Value field contains a Management Error Code. The possible values for the Management Error Code are: 7 6 5 0 0 1 Confirmed Operation 0 1 0 Return Result 1 0 1 Reject 2 1 0 0 Action 7 6 5 4 3 2 1 0 0 0 0 0 1 0 Link Alarm Status Change 7 6 5 4 3 2 1 1 0 1 0 0 1 1 Alarm Status Parameter 8 7 6 5 4 3 2 1 0 0 0 0 0 1 0 0 Suspend Alarming on link 0 0 0 0 0 0 1 1 Resume Alarming on Link 7 6 5 4 3 2 1 0 0 0 0 0 0 1 Protocol Violation 0 0 0 0 0 1 0 Unrecognized Operation
Codeset 6 Information Elements
Issue 6 June 1997
4-61
Old Party Identifier
The Old Party Identifier IE shown in Figure 4-31 associates a previous
party-identifier with the current one in situations where a call event merges two
calls and the ECS may reassign party-ids. The correspondence of Old Party
Identifier information elements with Party Identifier information elements
correlates the old and new party identifiers. The following figure provides the
format of this information element.
NOTE:
The adjunct should accept both one- and two-byte party-id values.
Figure 4-31. Old Party Identifier
From Call (byte 3; bit 7)
Party ID (bytes 4, 4a; bits 7-1)
Binary number assigned by the ECS 8 7 6 54321
Old Party Identifier
0 0 0 10111Byte 1
Information element identifier
Length of Old Party Identifier contents 2
1From Spare
ExtCall0 00000 3
0
Party ID 4
Ext
1
Party ID 4a
Ext
Bit 7
0 Other Call
1 Resulting Call
Information Elements 4-62Issue 6 June 1997 Originating Line Information The Information Identifier (II) Digits IE shown in Figure 4-32 shows the II-Digits carried in the Originating Line Identifier IE. Figure 4-32. Originating Line Information Data Information Element NOTE: See Bellcore’s Local Exchange Routing Guide, Document Number TR-EOP-000085 for further information. This document is updated quarterly.8 7654321 0Orig Line Info 0000001Octet1 Information element identifier Length of OLI Contents 2 II-Digits 3
Codeset 6 Information Elements Issue 6 June 1997 4-63 Party Identifier The Party Identifier IE shown in Figure 4-33 identifies a party on a third party call for call feedback event reporting or call control. NOTE: The current implementation uses a single byte for the Party_id field. For forward compatibility, any adjunct implementation should be prepared to accommodate two-byte Party_ids. Figure 4-33. Party Identifier Information Element Party ID (bytes 3, 3a; bits 7 through 1) Binary number assigned by the ECS. This value is between 1 and 6 for non-bridged parties and is greater than 6 for bridged parties.8 7654321 Party Identifier 0 1000100Byte 1 Information element identifier Length of Party Identifier contents 2 0 Party ID3 Ext 1 Party ID 3a Ext
Information Elements 4-64Issue 6 June 1997 Resource Identifier The Resource Identifier IE shown in Figure 4-34 identifies the resource for which a query is being made. Figure 4-34. Resource Identifier Information Element8 7654321 Resource Identifier 0 1010001Byte 1 Information element identifier Length of Resource Identifier contents 2 1 Resource Type 3 Ext Resource Type:Bits 7 6 5 4 3 2 1 0 0 0 0 0 0 0 Reserved 0 0 0 0 0 0 1 Tone Detection/Call Classification 0 0 0 0 0 1 0 Tones