DEFINITY ECS Release 8.2 Maintenance for R8.2csi
555-233-119 Issue 1
April 2000
Maintenance Objects

3-102ANN-BD (Announcement Circuit Pack)

3
found. This number correspond s to the announcement numbers on the announcement form. The extension relating to the announc ement can be determined by the display announcement command.
Table 3-39. TEST #209 Announcement Checksum Test
Error
Code
Test
Result Description/ Recommendation
0 ABORT An error code of 0 indicates that the announcement file has been
corrupted due to a hardware fault in the TN750 board. Follow step #7
under ‘‘General Notes’’ at the beginning of this section.
1023 ABORT There are no announcements currently recorded on the circuit pack.
1024 ABORT This abort code is given for the following reasons:
1. An announcement upload or download is in progress.
2. An announcement upload or download is requested when this test is
running.
3. A record is in p rogress.
4. A record request comes in when this test is running.
If an announcement upload or download is in progress, a status
data-module <announcement data extension> command should show
that the announcement data port is connected to a NETCON data channel,
and the "card-in-use" LED for the memory card is on (to determine the
extension of the announcement data module, use the list data-module
command).
See Note (a) at end of table for more information.
1. Wait until the blocking event is finished, and then run this test again.
An upload or download could take up to 45 minutes to complete, and
a recording session is finished as soon as the station that was making
the recording is placed on-hook.
2. If the test continues to abort, and a record or upload/download is not
in progress, escalate the problem.
2000 ABORT Response to the test request was not received within the allowable time
period. If Error Type 1538 is present in the Error Log, follow the
maintenance strategy recommended for this Error Type.
2100 ABORT Could not allocate the necessary system resources to run this test.
ABORT Internal system error.
1. Retry the command at 1-minute intervals a maximum of 5 times.
Continued on next page