
Maintenance Objects
555-233-119
704
Issue 5 October 2002
Announcement Checksum Test (#209)
Associated with every recorded announcement is a checksum. In this test, the SP
checks a stored global checksum covering all recorded announcements against a
calculated one and returns the results to the maintenance system. If the global
checksum failed, maintenance requests the SP to check each individual
announcement’s checksum.
If the test fails, it returns the total number of defective announcements found. In
addition, associated with each failure is an error in the Error Log (Error Type 14).
The Aux Data indicates the number of the first defective announcement found.
This number corresponds to the announcement numbers on the announcement
form. Use display announcement to determine the extension related to the
announcement.
Table 59. 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 progress.
4. A record request comes in when this test is running.
If an announcement upload or download is in progress, use status
data-module <announcement data extension> to 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 list data-module.
See Note (a) at end of table for more information.
1. Wait until the blocking event is finished, and 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.
Continued on next page