1

Terminal failed to erase its program flash.

2

Target image file checksum is bad.

3

Target image is incompatible with the terminal (Avaya 2420 DCP sets only).

4

Target terminal rejected image as invalid.

12

Target terminal fails to go into the download mode, timeout occurred.

13

Station firmware download engine timed out waiting for download to complete.

14

Station firmware download to a terminal had too many retries, timeout occurred.

4

Two consecutive terminals failed to download with a failure indicating that the terminals did not accept the firmware image. It is likely that any remaining terminals will also fail, so the scheduled download is stopped and any terminals in the download list that are not yet downloaded are aborted.

8

The download image file is not present. The change firmware station-download form requires that the image file be present before the form can be brought up. This error indicates a problem with the image file. As a result of this failure, the schedule cannot continue, and any terminals in the download list that are not yet downloaded are aborted.

11

There was a system error in the download process, possibly due to inter-process calls. Escalate the problem.

13

Two consecutive terminals failed to download due to internal timeouts. It is likely that all terminals will fail as well so the schedule is stopped and any remaining terminals in the download list are aborted.

14

Could not build a list of terminals from the range specified on the change firmware station-download form. Check the administered stations for exact extension numbers.

15

The scheduled stop time was reached without completion of all scheduled terminals. The status firmware station-download command indicates all terminals not downloaded with a status of ABRT and a Reason Code of 3 (see the table) . If the Continue daily until completed field is y, this error will not occur because the continuation option causes the schedule to resume the next day at the scheduled start time (see the table) .

Idle

No

There are no downloads Pending or Active, or there are no unresolved errors/alarms for the last download

Pending

No

Download has been scheduled but not yet started. Check the start time to see when it is scheduled to start.

Active

No

Download is currently active. Actively downloading terminals should be listed with a status of ACTV. If the schedule has just started and no downloads are listed, the system may be waiting for a FAC requested or terminal requested download to complete before it begins.

Resume-pending

No

Download was stopped at the Stop Date/Time but not all of the terminals have been attempted. Downloading will resume at the scheduled Start Date/Time listed on the screen.

Aborted

Yes

Download was aborted for the entire range of terminals. This could happen if the firmware image was bad, damaged or disappeared.

Failed

Yes

At least two terminals rejected the firmware as invalid. As a result, the download was aborted to avoid problems with any further terminals. Check the Reason Codes of the failed terminals in the list to find the reason why the download failed (the table) .

Completed

Yes

The scheduled download has completed either due to all terminals in the range of extensions having completed or due to the stop timer.

Disabled

Yes

An Active schedule was disabled with the disable firmware station-download command. After an active schedule is disabled, the Schedule state remains Active until all currently active terminal downloads have completed.

No Image

Yes

The download was stopped because there was no firmware image present in memory.

Restart

Yes

The download was stopped due to a system restart. You must schedule a new download for any Aborted terminals.

Sys Fail

Yes

The download was stopped due to a system error.

Sys Occ

No

The download has been suspended due to the system’s occupancy level. The schedule will resume when the occupancy level drops to a safe level.

Dnld Timeout

Yes

While the scheduled download was running, two or more consecutive terminals failed to respond to the download process.

1

ABORT

The firmware image that was noted on the change firmware station-download form has disappeared. The download schedule had to be stopped.

2

ABORT

The terminal could not be downloaded due to an internal discrepancy relating to the maximum number of downloads allowed.

3

ABORT

The terminal was not downloaded before the scheduled stop time occurred. Schedule a new download with adequate time for the downloads to complete, or select the continue daily option to allow the schedule to resume the following day.

4

ABORT

The terminal could not be downloaded because the schedule aborted for an unknown reason.

5

ABORT

The terminal did not respond to the download request.

6

ABORT

The terminal that was added to the download list at the scheduled start time no longer exists. This can occur when a station is removed during an active download schedule. Download to this terminal was aborted.

11

ABORT

The terminal was in firmware download mode when the layer 2 link to the terminal went down. The download was aborted as a result of the link down condition.

18

ABORT

The terminal was busied out by craft and could not be downloaded.

32

ABORT

Download to the terminal timed out due to an internal error in the station firmware download process.

1000

ABORT

Terminal was in use at the time that it was to be downloaded. Download to this terminal was aborted.

1012

ABORT

An internal error occurred while preparing to download to this station.

3841

ABORT or FAIL

The system restarted during an active download. As a result, all terminals that were not downloaded are marked with a status of ABORT with this reason code. All terminals that were actively downloading when the reset occurred are marked with a status of FAIL with this reason code.

128

FAIL

The terminal rejected the firmware because the firmware image failed the checksum test.

129

FAIL

The terminal rejected the firmware because the firmware image failed the image validity test. The firmware image may not be the right image for the hardware being downloaded to.

130

FAIL

The terminal being downloaded could not write its flash memory.

131

FAIL

A terminal in the range was translated to be a valid terminal for this download schedule. However, the terminal is not a valid receiver of the download.

513

FAIL

The terminal was not in service at the time that it was to be downloaded. Download to this terminal failed.

3584

FAIL

The terminal rejected the firmware image.