Avaya S8700 Maintenance Manual page 2306

For multi-connect configurations
Hide thumbs Also See for S8700:
Table of Contents

Advertisement

Maintenance-Object Repair Procedures
Table 8-618. Test #258 ISDN Test Call — Continued
Error
Test
Code
Result
Description / Recommendation
1117
ABORT
ISDN B-channel maintenance message is already outstanding.
1. Wait two minutes, then try again.
1118
ABORT
Far end of ISDN trunk is not administered.
1. Check the administration of the far-end ISDN trunk.
2. Issue the status trunk command, and try the test again.
1119
ABORT
The test call was aborted due to a normal call attempt on this trunk. The test
call is performed only if the trunk is idle.
1. Either wait for the normal call to terminate normally, or force it to be
1120
ABORT
The trunk-side ISDN-BRI facility is in the ISDN out-of-service/far-end state.
1. Try to change the service state via Test #256 (Service State Audit test).
1122
ABORT
There is no test line number for the far-end switch.
1. Check the Trunk Group Administration form.
1123
ABORT
There is no Feature Access Code administration for this Facility test.
1. Check the Dial Plan and Feature Administration forms.
2012,
ABORT
Internal system error
None,
1. Retry the command at 1-minute intervals up to 5 times.
2000
2. If the test continues to abort, escalate the problem.
2035
ABORT
The call has timed out, perhaps because of a lack of system resources.
1. Wait 1 minute and try again.
2036,
ABORT
Internal system error
2037
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
2038,
ABORT
A problem occurred while trying to read the test data.
2039
1. Wait one minute and then try again.
2. If the test aborts again in the same manner, there is a serious internal
2040
ABORT
Internal system error
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
8-1584
Issue 1 May 2002
dropped by using the busyout trunk command.
Then retry this test. However, the trunk may be in the
out-of-service/far-end state due to problems at the far-end switch. If that is
the case, no remedial action can be taken at this end.
problem. If so, escalate the problem.
Continued on next page
555-233-143

Advertisement

Table of Contents
loading

Table of Contents