Lucent Technologies DEFINITY Enterprise Communications Server Release 5, CallVisor, ASAI Protocol Reference Instructions Manual

							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
Length of Version IE 0x01
ASAI Version 0x?? 
						

							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 identifier tag 0x02
invoke identifier length 0x01
invoke identifier 0x??initiating — odd value
operation value tag 0x02
operation value length 0x01
Operation Value = Heartbeat 0xb3 
						

							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 0x02
invoke identifier length 0x01
invoke identifier 0x?? value from request 
						

							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 = confirmed, type = 
action
MIE Operation 0x82 Link Alarm Status Change
MIE Parameter 0xd3 Alarm Status Parameter
parameter length 0x01
new service state 0x04 or 0x03 0x04 = suspend, 0x03 = 
resume 
						

							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
MIE Op class & Type 0xa0 class = ret. reslt., type = action
MIE Operation 0x82 Link Alarm Status Change 
						

							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 
						

							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 restricted set of MIMs (used for Suspend/Resume 
alarms)
The ECS does not provide the following features for ASAI adjuncts:
nU-interface endpoints
nShort passive bus configuration
nNoninitializing endpoints
nThe use of S and Q bits and their associated functions at layer 1 
						

							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 endpoint that supports fixed TEI assignment.
nTEI pops up when Fixed TEI is set to YES. A TEI in the range 0 to 63 
must be entered. This must correspond to the TEI that the adjunct BRI 
interface uses.
nMIM Support defaults to NO for ASAI station type. This does not allow 
access to fields for Endpoint Initialization, SPID, and MIMs 
for Maintenance/Management.
nXID Testing may be enabled or disabled depending on the adjunct. Set 
the XID Testing field to YES when the ASAI host supports the LAPD XID 
inquiry message exchange. Lucent Technologies recommends including 
support of the XID test in any ASAI adjunct whenever possible. The XID 
Testing field defaults to YES for ASAI station type.
If an administrator attempts to create more than eight ASAI interfaces, the ECS 
responds with an error message and prevents the administration of more than 
eight ASAI links.
For more information, see the 
DEFINITY Communications System Generic 1 and 
Generic 3 Feature Description,
 555-230-201, or the DEFINITY Enterprise 
Communications Server Release 5 Feature Description,
 555-230-301. 
						

							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 adjunct link is 
being taken out of service for planned maintenance, it is not desirable for the ECS 
to generate alarms when the link drops. For this reason, the ECS supports a 
procedure where an adjunct should suspend and resume alarming on a specific 
link. Suspending alarms stops the ECS from generating alarms for that link. 
Resuming alarms causes the ECS to generate alarms at the administered level.
It is recommended that the Resume Alarms and Suspend Alarm capabilities be 
incorporated into any adjunct ‘‘startup’’ and ‘‘shutdown’’ operations for ASAI links.
ASAI Heartbeat
The ECS periodically sends ASAI Heartbeat messages to the adjunct. The 
adjunct must respond or the ECS maintenance subsystem takes action to tear 
down the link and re-establish it. It is recommended that any ASAI endpoint 
respond to an ASAI Heartbeat message as soon as possible after it is received.
The ECS similarly responds to any ASAI Heartbeat message that it receives from 
an adjunct so that an adjunct maintenance software subsystem can use the ASAI 
Heartbeat capability to monitor the health of the link.
ASAI Interactions with System 
Restarts
Reboot, COLD1, COLD2 System Restarts — Cause the BRI port board to be 
reset and thus cause the BRI signaling channels to be disconnected. Any ASAI 
associations are terminated.
System Warmstart, Hot Start — cause a layer 2 drop which in turn can lead to the 
adjunct clearing associations or restarting layer 3. 
						

							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, the user endpoint (for example, the adjunct) must 
clear all CRVs except those that are:
1. In the 
active state, AND
2. Connected to a B-channel
Since ASAI CRVs are never associated with a B-channel, the adjunct must 
immediately clear all CRVs associated with ASAI associations when layer 2 
connectivity is lost.
The procedure further states that if layer 2 connectivity is reestablished before a 
specified timer expires, the user endpoint (for example, the adjunct) sends 
STATUS messages only for CRVs that were not cleared as stated above. Thus, 
neither the adjunct nor the ECS may send STATUS messages for ASAI CRVs.
Layer 3
Layer 3 RESTart AND RESTart
ACKnowledgement Messages
Both the ECS and adjunct must adhere to the RESTart Procedure on an ECS 
ASAI interface. In the BRI specification, the procedure is optional in the 
user-to-network direction, but it is mandatory for an ASAI.
Layer 3 STATUS and STATUS ENQuiry Messages
Neither the ECS nor the adjunct sends the STATUS ENQuiry message on an 
ASAI interface.
BRI permits any endpoint to send a STATUS message whenever it receives an 
unexpected message. The ECS does not do so on a BRI ASAI interface. If the 
adjunct sends a STATUS message to the ECS, on a BRI ASAI interface, the ECS 
discards the STATUS message.