Demand test descriptions and error codes - Avaya Support

Communication Manager Maintenance Object Repair Procedures
c. Error Type 2: a request has been made to use a transit network or common carrier that cot
be accessed. Check the routing pattern used by this administered connection and verify
that the inter-exchange carrier specified is correct.
d. Error Types 6, 21, 31, 127: the exact failure cause is unknown or has been mapped to one
of these values. If this is a permanent condition, try reversing the direction of the
Administered Connection (originate the administered connection from the destination
switch). This may yield another failure cause.
e. Error Type 17: the destination endpoint is not available. Check the status of the destination
endpoint at the far-end switch. The status for the destination endpoint will not be available
on the switch where this error is logged. At the far end, use status access-endpoint or
status data-module to see whether the endpoint is busy, out-of-service, or otherwise
unavailable.
f. Error Types 18, 102: this switch sent an ISDN message to another switch that either did not
respond (18) or did not respond within the time allowed (102). This could be due to link
failure, or congestion, or an outage at the other switch.
g. Error Type 22: the address of the destination endpoint has changed. Change the
administered connection accordingly. The destination endpoint will not be administered on
the switch where this error is logged.
h. Error Types 34, 42, 44, 58: a resource (for example, a circuit or bearer capability) required
by the administered connection is not currently available.
i. Error Types 38, 41: a network failure (38) or temporary failure (41) has occurred. Error Log
entries for other MOs (for example, DS1-BD) may indicate a local problem.
52 Maintenance Alarms for Communication Manager, Media Gateways and Servers