ADM-CONN (Administered Connection)
Issue 5 October 2002
611
555-233-119
j. Indicate that a resource (for example, a circuit or bearer capability)
required by the administered cConnection is not presently available.
k. A network failure (38) or temporary failure (41) has occurred. Error Log
entries for other maintenance objects (for example, DS1-BD or ISDN-LNK)
may indicate a local problem.
l. A request to use a network service has been denied because the service
has not been purchased. Check the routing pattern used by this
Administered Connection and verify that the service type is correct. If the
service type appears correct, check with the customer or network provider
or both to determine what services have been purchased by the customer.
m. Indicate that outgoing calls may be barred on the originating switch (52) or
that incoming calls may be barred on the destination switch (54). To restore
an administered connection failure, use status administered connection
for current administered connection state and observe the retry count. If
the administered connection state is “failed,” verify and correct the
Administered Connection Administration Form.
n. The requested bearer capability (65), channel type (66), or facility (69) is
not implemented or is unknown to the network. Check the address of the
destination endpoint and the routing pattern used by this Administered
Connection, and verify that they are correct and available.
o. These errors indicate that an ISDN protocol error has occurred.
p. The destination endpoint (or some intermediate facility) is not compatible
with the originating endpoint. Check the BCC fields of the routing pattern
used by this Administered Connection. Also, check if the originating and
destination endpoints are compatible (for example, the originating access
endpoint is voice-grade data, and the destination access endpoint is 64k
data).