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 181
Codeset 6 Information Elements Issue 6 June 1997 4-75 Status BitsWhen the In-use, Idle, Maintenance-busy, and Other-unavailable status bits are set to 1, a binary-encoded count corresponding to that status follows. CountsBytes containing counts correlate with the status bits: The first count byte conveys the count for the highest order status bit set to 1. Typically, this is the “In-use” count, but it could be the idle count (for example). Subsequent bytes convey the counts for the next highest...
Page 182
Information Elements 4-76Issue 6 June 1997 User-Entered Code The User-Entered Code IE shown in Figure 4-41 conveys user-entered information (for example, authorization codes or call prompter data). Figure 4-41. User-Entered Code Information Element NE 8 7 6 54321 User-Entered Code 0 0 0 00010Byte1 Information element identifier Length of User-Entered Code contents 2 1 Ext.Type of User Code 3 1 Ext.Collect/ Collected Timeout Interval 4 0/1 Ext. User Code Data 5,..., n ASAI...
Page 183
Codeset 6 Information Elements Issue 6 June 1997 4-77 Timeout IntervalThe interval for digit collection (in seconds) once DEFINITY ECS has received the first digit (0-63 sec). Encode as all zeros if no timeout is to be used. User Code DataThe user-entered data is encoded in ASCII characters. The ECS sends up to 24 bytes of user code data (including * and #). When the User-Entered Code carries information to log in an agent where EAS is activated, then the IE contains both the agent’s EAS login...
Page 184
Information Elements 4-78Issue 6 June 1997 Version The Version IE shown in Figure 4-42 conveys the ASAI protocol version used on a specified ASAI link. It may be repeated in the RESTART message to the adjunct in the case where the ECS supports multiple versions. The RESTart Acknowledgement message can also contain this IE. Figure 4-42. Version Information Element Version Value (Octet 3) Identifier (Octet 4, etc.) The identifier need not be present. For CallVisor for Unix System V (PC/ASAI), this is...
Page 185
Issue 6 June 19975-1 5 Byte Level Messages This chapter provides the encodings for each message that passes across the ASAI interface at the byte level for the following: nEvent Reports nCall Control Capability Group nDomain (Station/ACD Split/EAS Skill) Control Capability Group nNotification Capability Group nRouting Capability Group nRequest Feature Capability Group nValue Query Capability Group nSet Value Capability Group nMaintenance Capability Group Conventions Within certain messages, specific...
Page 186
Byte Level Messages 5-2Issue 6 June 1997 The bit-wise OR operation is indicated by a vertical bar “|’’ and the resulting value is the bit-wise ORing of the values on either side of the bar. The word “or,” or a comma, indicates that the value is one of a list of possible values. The occurrence of a question mark (?) in the Byte Value column means that a hex-byte value is present. Event Reports Event Reports: REGister Messages Sent by the Adjunct None for Event Reports. Event Reports: REGister...
Page 187
Event Reports Issue 6 June 1997 5-3 Alerting Event Report (Continued on next page) Byte Description Byte Value Comments Protocol Discriminator 0x08 BRI CRV Length 0x01 or 0x02 First CRV Byte 0x? Second CRV Byte0x? Message Type 0x62 FACility Locking Shift to Code Set 6 0x96 Facility IE 0x1c Length of Facility IE 0x?? computed length Q.932 Supplementary Service 0x91 component type tag 0xa1 INVOKE component component length 0x?? computed length component length0x?? long form (length > 127) invoke...
Page 188
Byte Level Messages 5-4Issue 6 June 1997 Alerting Event Report — (Continued) Byte Description Byte Value Comments Call Identity IE 0x10 Length of Call Identity 0x02 computed value * Call identifier (2 bytes) 0x?? switch-assigned value Calling Party Number0x6c Length of Calling Party IE0x? computed length Address Type & numbering Plan Id0x?? 0x80, 0x90, 0x81, 0x91, 0xa0, or 0xa1 * Address digits0x?? 0x30 thru 0x39,0x23(#), 0x2a(*) Called Party Number IE 0x70 Length of Called Party Number 0x? computed...
Page 189
Event Reports Issue 6 June 1997 5-5 NOTE: The Calling Number IE and the Trunk Identification IE are mutually exclusive. One or the other will be present. * The first to N-1 extension digits0x30 thru 0x39 The last extension digit0xbX 0xb0 thru 0xb9 Alerting Event Report — (Continued)
Page 190
Byte Level Messages 5-6Issue 6 June 1997 Answered Event Report (Continued on next page) Byte Description Byte Value Comments Protocol Discriminator 0x08 BRI CRV Length 0x01 or 0x02 First CRV Byte 0x? Second CRV Byte0x? Message Type 0x62 FACility Locking Shift to Code Set 6 0x96 Facility IE 0x1c Length of Facility IE 0x?? computed length Q.932 Supplementary Service 0x91 component type tag 0xa1 INVOKE component component length 0x?? computed length component length0x?? long form (length > 127) invoke...