Administrator's Guide

Features and technical reference
555-233-5061456 Issue 5 October 2002
In the event of a failure, an error is entered into the error log, which generates an
alarm, if it is warranted by your alarming strategy. You can display AC failures via
the
status administered-connection command.
As long as an AC is due to be active, the originating switch continues to establish
an AC unless the attempt fails because of an administrative error (for example, a
wrong number) or service-blocking condition (for example, outgoing calls
barred).
The frequency with which failed attempts are retried is determined by the
administered retry interval (1 to 60 minutes) for each AC.
Retries are made after the retry interval has elapsed regardless of the
restorable attribute of the AC.
ACs are retried in priority order.
When you change the time of day on the switch, an attempt is made to
establish all ACs in the waiting-for-retry state.
Dropping Administered Connections
An AC remains active until one of the following occurs:
The AC is changed, disabled, or removed.
The time-of-day requirements of a scheduled AC are no longer satisfied.
One of the endpoints drops the connection. This could be because of user
action (in the case of a data endpoint), maintenance activity resulting from
an endpoint failure, busying out of the endpoint, or handshake failure. If
the endpoints are incompatible, the connection is successful until
handshake failure occurs.
NOTE:
An AC between access endpoints remains connected even if the
attached access equipment fails to handshake.
An interruption (for example, facility failure) occurs between the
endpoints.
If an AC drops because it was disabled/removed or is no longer due to be active,
no action is taken. If an AC drops because of changed AC attributes, an immediate
attempt is made to establish the connection with the changed attributes if it is still
due to be active. Existing entries in the error/alarm log are resolved if they no
longer apply. If handshake failure resulted in the dropping of the connection, in
the case of an AC involving at least one data endpoint, no action is taken for that
AC until the change administered-connection
command is executed.