Avaya Communication Manager Administrator's Manual page 1350

Feature Reference
Administered connections
•
A local-access endpoint connecting to a local or remote-access endpoint. Examples: a DSO
cross-connect and a 4-wire leased-line modem to a 4-wire modem connection via an analog tie
trunk.
•
A local data endpoint connecting to a local or remote data endpoint such as a connection between
two 3270 data modules.
NOTE:
The following guidelines do not include AAR and ARS, or GRS administration
information for routing AC calls over trunk groups. See the respective feature elsewhere
in this book for that information.
Establishing Administered Connections
The originating switch attempts to establish an AC only if one of the following conditions exist:
•
AC is active.
•
AC is due to be active (either a permanent AC or time-of-day requirements are satisfied if it is a
scheduled AC).
•
Originating endpoint is in-service or idle state.
If the originating endpoint is not in service or is idle, no activity takes place for the AC until the endpoint
transitions to the desired state. The originating switch uses the destination address to route the call to the
desired endpoint. When the switch establishes 2 or more ACs at the same time, the switch arranges the
connections in order of priority.
AC attempts can fail for the following reasons:
•
Resources are unavailable to route to the destination.
•
A required conversion resource is not available.
•
Access is denied by COR, facilities restriction level (FRL), or Bearer Capability Class (BCC). Or,
an attempt is made to route voice-band-data over SDDN trunks in the public switch network.
•
Destination address is incorrect.
•
Destination endpoint is busy.
•
Other network or signaling failures occur.
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
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.
1350
status administered-connection
Administrator's Guide for Avaya Communication Manager
November 2003