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 371
Maintenance Issue 6 June 1997 5-187 Acknowledge Restart of an ASAI Interface 1. This locking shift must be present when the Version IE is present; otherwise, it is omitted. Byte Description Byte Value Comments Protocol Discriminator 0x08 BRI CRV Length 0x01 or 0x02 global CRV CRV Value 0x80 flag bit set with zero value Second CRV Value Byte0x00 Message Type 0x4e RESTart ACKnowledge Restart Indicator IE 0x79 length of Restart Ind. 0x01 all interfaces 0x87 Locking Shift to Code Set 610x96 Version IE 0x1b...
Page 372
Byte Level Messages 5-188Issue 6 June 1997 Heartbeat Byte Description Byte Value Comments Protocol Discriminator 0x08 BRI CRV Length 0x01 or 0x02 First CRV Byte 0x? assigned value Second CRV Byte0x? assigned value Message Type 0x64 REGister Locking Shift to Code Set 6 0x96 Facility IE 0x1c Length of Facility 0x?? computed length Q.932 Supplementary Service 0x91 component type tag = invoke 0xa1 INVOKE component component length 0x?? computed length component length0x?? long form (length > 127) invoke...
Page 373
Maintenance Issue 6 June 1997 5-189 Response to Heartbeat Byte Description Byte Value Comments Protocol Discriminator 0x08 BRI CRV Length 0x01 or 0x02 First CRV Byte 0x? Second CRV Byte0x? Message Type 0x5a RELease COMplete 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 0xa2 RETURN RESULT component component length 0x?? computed length component length0x?? long form (length > 127) invoke identifier tag...
Page 374
Byte Level Messages 5-190Issue 6 June 1997 Maintenance Messages Sent by the Adjunct Suspend/Resume Alarming for ASAI Interface Byte Description Byte Value Comments Protocol Discriminator 0x08 BRI CRV Length 0x01 or 0x02 global CRV CRV Value 0x00 zero value Second CRV Value Byte0x00 Message Type 0x00 MIM — first byte Message Type 0xf7 MIM — second byte Locking Shift to Code Set 6 0x96 MIE 0x7a MIE length 0x07 MIE Prot Disc 0x03 MIE Trans Ref 0x80 synchronous MIM operation MIE Op class & Type 0x90 class...
Page 375
Maintenance Issue 6 June 1997 5-191 Maintenance Messages Sent by switch Acknowledge Suspend/Resume Alarming for ASAI Interface Byte Description Byte Value Comments Protocol Discriminator 0x08 BRI CRV Length 0x01 or 0x02 global CRV CRV Value 0x80 flag bit set with zero value Second CRV Value Byte0x00 Message Type 0x00 MIM — first byte Message Type 0xf7 MIM — second byte Locking Shift to Code Set 6 0x96 MIE 0x7a MIE length 0x04 MIE Prot Disc 0x03 MIE Trans Ref 0x80 response to synchronous MIM operation...
Page 376
Byte Level Messages 5-192Issue 6 June 1997 Reject MIM Message Byte Description Byte Value Comments Protocol Discriminator 0x08 BRI CRV Length 0x01 or 0x02 global CRV CRV Value 0x80 flag bit set with zero value Second CRV Value Byte0x00 Message Type 0x00 MIM — first byte Message Type 0xf7 MIM — second byte Locking Shift to Code Set 6 0x96 MIE 0x7a MIE length 0x04 MIE Prot Disc 0x03 MIE Trans Ref 0x?? taken from request MIE Op class & Type 0xd0 class = reject MIE Operation 0x81, 8x82 Management Error Code
Page 377
Issue 6 June 19976-1 6 Maintenance The ECS Support for BRI Endpoints The ECS requires all ASAI interfaces be administered as fixed or automatic Terminal Endpoint Identifier (TEI), point-to-point interfaces. Although the ECS also supports multipoint for BRI station sets, an ASAI interface is more restricted. This restriction means an adjunct: nMust support either fixed or automatic TEI, but does not have to support both nDoes not need to support layer 3 SPID initialization nOnly needs to support a...
Page 378
Maintenance 6-2Issue 6 June 1997 ASAI Endpoint Administration To administer an ASAI interface, the system administrator enters the add station command. On the station form, the administrator first sets the station type to ASAI. The administrator must MANUALLY administer the ASAI interface as a fixed or automatic TEI, point-to-point link. nFixed TEI defaults to NO for ASAI station type. The administrator should leave this set to NO for an automatic TEI ASAI endpoint or change it to YES for an ASAI...
Page 379
ASAI Link Alarming Issue 6 June 1997 6-3 ASAI Link Alarming The ASAI Adjunct Alarm Administration Feature permits a customer to tune the level of alarm reporting for ASAI adjuncts. Using the feature, the customer can administer on-board and off-board alarms for ASAI ports and/or endpoints to raise warnings or minor or major alarms. Once an item is administered to raise a certain level of alarm, it alarms all ASAI links at that level. The system default is to provide warnings. When an adjunct or...
Page 380
Maintenance 6-4Issue 6 June 1997 Management Information Messages The ECS uses BRI Management Information Messages to suspend and/or resume alarms on an ASAI interface. If the ECS receives any other message with a Management Protocol Discriminator on an ASAI interface, the message is ignored. Temporary Layer 2 Drop The BRI specification contains a procedure for a temporary loss of Link Access Protocol for D Channel (LAPD) connectivity. The procedure states that when connectivity is lost at layer 2,...