ATT DEFINITY Communications System Generic 3V4 Instructions Manual

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
   
						

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbb
ASAI Maintenance Capabilities
11
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
This chapter describes the Maintenance Capability Group.  The capabilities
available in this group are used to disable and enable switch-administered alarms
for periodic link maintenance and to obtain information about the condition of the
ASAI link.
The following capabilities are available:
HeartbeatThis capability lets the adjunct and switch
request a sanity check on the ASAI software
or the ASAI link.
Suspend alarmsThis capability lets the adjunct disable
switch-administered alarms on the ASAI link
before planned down time or routine
maintenance.
Resume alarmsThis capability lets the adjunct enable switch-
administered alarms on the ASAI link.
RestartThis capability clears out all data structures
and resources associated with the ASAI link
(for example, associations).
!CAUTION:
All adjuncts must support the restart and heartbeat procedures or the ASAI
link will not operate.  Further, it is strongly recommended that all adjuncts
incorporate suspend/resume maintenance to avoid unnecessary alarms and
resulting maintenance expenses when adjuncts are brought down for
routine maintenance or normal shutdown.
Issue 4  September 1995  11-1 
						

							ASAI Maintenance Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Heartbeatbbbbbbbb
This capability enables the adjunct or the switch to send an
application-to-application message and receive a response in order to determine
the sanity of the application on the remote endpoint.
Information Flowbbbbbbbbbbbbbbb
The sender expects a response to its request.
The switch responds to the Heartbeat within 60 seconds.
The switch sends the Heartbeat message over each established signaling link to
an adjunct every two minutes.  The adjunct is required to respond to the switch
within ten seconds.  Failure to respond to three consecutive heartbeats results in
the switch bringing the link down and attempting to bring it back up again.
Heartbeat Parametersbbbbbbbbbbbbbbb
None for this capability
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
None for this capability
Denial (NAK) Causesbbbbbbbbbbbbbbb
None for this capability
Protocol Error (NAK) Causesbbbbbbbbbbbbbbb
None for this capability
11-2  Issue 4  September 1995 
						

							ASAI Maintenance Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Suspend Alarmsbbbbbbbb
This capability enables the adjunct to disable switch alarms on an ASAI link for
maintenance functions.
NOTE:
Since unnecessary alarms can result in unnecessary maintenance
expenses, it is recommended that all adjuncts request this capability during
the shutdown sequence.
Information Flowbbbbbbbbbbbbbbb
The adjunct makes the suspend alarms request for that particular link.
The switch issues an ACK to notify the adjunct that it will not raise any alarms for
that ASAI link.
Suspend Alarms Parametersbbbbbbbbbbbbbbb
None for this capability
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
None for this capability
Denial (NAK) Cause(s)bbbbbbbbbbbbbbb
None for this capability
Protocol Error (NAK) Cause(s)bbbbbbbbbbbbbbb
None for this capability
Issue 4  September 1995  
11-3 
						

							ASAI Maintenance Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Considerationsbbbbbbbbbbbbbbb
The Suspend Alarms capability overrides any administered alarms and halts
periodic switch maintenance for the particular ASAI interface over which it is
received.
When alarms are suspended on a link, the switch continues to service that ASAI
link as follows:
The switch continues to send periodic Heartbeat requests on any link that
has suspended alarms, but does not raise alarms or attempt to re-initialize
the link if there is no response to a Heartbeat request.
The switch continues to process ASAI associations that are in progress.
The switch accepts and processes requests for new ASAI associations.
Transmitting a Suspend Alarms on an ASAI link does not affect any associations
in progress on the link.  This allows any remaining associations to terminate
gracefully.  New associations may be initiated when alarms are suspended.
11-4  Issue 4  September 1995 
						

							ASAI Maintenance Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Resume Alarmsbbbbbbbb
This capability enables the adjunct to resume switch alarms on an ASAI link.
Information Flowbbbbbbbbbbbbbbb
The adjunct makes the suspend alarms request.
The switch issues an ACK to notify the adjunct that it will raise alarms for the
ASAI link.
Resume Alarms Parametersbbbbbbbbbbbbbbb
None for this capability
ACK (Positive Acknowledgement)
Parameter(s)
bbbbbbbbbbbbbbb
None for this capability
Denial (NAK) Cause(s)bbbbbbbbbbbbbbb
None for this capability
Protocol Error (NAK) Cause(s)bbbbbbbbbbbbbbb
None for this capability
Considerationsbbbbbbbbbbbbbbb
If the adjunct does not acknowledge a Heartbeat request after sending Resume
Alarms, the switch restarts the link and generates an alarm, if alarms are
administered.
Issue 4  September 1995  
11-5 
						

							ASAI Maintenance Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Restartbbbbbbbb
Restart provides that either endpoint may use this feature to free and reinitialize
all resources for an ASAI interface.  It also insures that if one ASAI endpoint
detects a layer 2 drop (and therefore clears all its CRVs [for example,
association] for the interface), ASAI messaging cannot continue on that interface
without the other endpoint clearing its CRVs also.
Both the switch and the adjunct initiate the Restart when:
An ASAI layer 2 link has been re-established after a link failure.
A switch or adjunct maintenance subsystem determines a need to restart
the ASAI interface.
If the switch cannot complete the Restart within a reasonable time and gets
another Restart from the other side, it ignores the latter Restart until it gets
another Restart.
Link Versionsbbbbbbbb
This section applies to both the ASAI ISDN BRI and Ethernet links.  With ASAI
Versions, the switch sends a RESTART message to the adjunct containing the
ASAI version(s) offered on the switch (currently V1 or V2). The adjunct responds
to the switchs RESTART message with a Restart Acknowledgement message
that includes the ASAI version of choice for that adjunct.  If the switch does not
support that version, the switch sends a RESTART message with a list of the
available versions.  If the adjunct sends a REstart Acknowledgement message
back with no version, the link is initialized with default version 1.  If the adjunct
sends a Restart Acknowledgement message insisting on a version not supported
by the switch, the link is not initialized and an error is logged.
Adjuncts without the versions procedure are able to perform pre-G3V4
RESTART procedures unchanged (in other words, RESTart Ð RESTart ACK).
In these cases, the ASAI link comes up with the default version.
For G3V3 and later, the Versions and link initialization and restart procedures are
covered in the 
DEFINITY Communications System CallVisor ASAI Protocol
Reference
, 555-230-221.
11-6  Issue 4  September 1995 
						

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbb
ASAI and Feature Interactions
12
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
This chapter describes the interactions between the ASAI capabilities and
specific switch features.
Call Control and Domain Control do not prohibit users from access to any
enabled switch features.  Controlled stations can access any enabled switch
feature.
Administration without Hardware
(AWOH)
bbbbbbbb
A station administered without hardware may be used as a station domain.
However, no event reports are provided to the adjunct for this domain since there
is no activity at such an extension.  This feature should not be used with ASAI
except for limited testing.
Issue 4  September 1995  
12-1 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Analog Setsbbbbbbbb
Redirection
Analog sets do not support temporary bridged appearances.  In normal
circumstances, when a call at a multifunction set is left on a simulated bridge
appearance, the call moves away from the analog set.  Thus, any domain-control
associations for the analog set receive the Call Redirected Event Report.
Alerting Event Reports are not sent to SAC-activated analog sets receiving calls.
Redirection on No Answer
Calls redirected by this feature generate the following event reports when a call
is redirected from a nonanswering station:
Call Redirected Event Report:
Provided over the Third Party Domain Control associations when the call
is redirected from a nonanswering agent.  This event is 
not provided if the
call is requeued to the split or delivered to another agent in the split.
Queued Event Report:
Generated if the call queues after being redirected.
Call Ended Event Report:
If the call cannot requeue after the call has been redirected from the
nonanswering agent, then the call continues to listen to ringback until the
caller is dropped.  In this case, a Call Ended Event Report is generated
when the caller is dropped and the call disconnected.
Direct-agent calls always redirect to the agents coverage path instead of
requeuing to the servicing ACD split.
Auto-Answer Option
The auto-answer analog sets do not receive dial tone after a Third Party Drop or
Third Party Clear Call capability.
Manual Answer Option
Manual answer analog sets receive dial tone after receiving a Third Party Drop or
Third Party Clear Call capability.
12-2  Issue 4  September 1995 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Number of Calls at Analog Sets
A maximum of three calls (one soft-held, one hard-held, and one active) may be
present at the same time.  In addition, the set may have a call waiting call.
A request to have more than three calls present is denied.  For example, if an
analog set user has three calls present and another call waiting, the user cannot
place the active call on hold or answer the call.  The only operations allowed are
to drop the active call or merge the soft-held and active waiting call.
Number of Held Calls
A maximum of two calls may be in a held state at the same time.  A request to
have a third call on hold is denied.
Switch-Hook Operation
When an analog set goes on-hook with one or two calls on hold, the user is
audibly notified.  This is not reported as an Alerting event.  When the user goes
off-hook and is reconnected to the alerting call, a Reconnected Event Report is
generated.
Going on-hook with a soft-held call and an active call causes the two calls to be
transferred from the users set.  It does not matter how the held call was placed
on soft hold.
Switch-Hook Flash Operation
If a controlled-extension analog user flashes the switch hook to put a call on soft
hold to start a new call:
1. The Hold Event Report is sent to all monitoring associations.
2. A Call Initiated Event Report is returned to all Domain Controlled
associations when the user receives the dial tone.
3. A Reconnect Event Report is returned to all associations if the user
returns to the held call.  If the held call is conferenced or transferred, the
Conferenced or Transferred event reports are sent to all associations.
An analog set supports Third Party Merge requests even if the ``switch-hook
flash field on the administration form is set to ``no.
User-Classified Calls
If a user-classified call is placed for an analog set user without a speakerphone
(or a headset), the user must either be idle or off-hook with dial tone, or go
off-hook within five seconds of the call setup request.  Otherwise, the request is
denied (NAKed).
Issue 4  September 1995  
12-3