Specifications

Chapter 5 - Software Download Administration Manual (SIP/MGCP Version)
AT-VP504E FXS 49
Emergency Soft-
ware Procedure
Once the new software file is successfully downloaded into the RAM of
the AT-VP504E FXS, this file is transferred from the RAM to the
EEPROM. The AT-VP504E FXS then reboots. If the transfer from the
RAM to the EEPROM is suddenly interrupted, only a part of the
software file is transferred to the EEPROM. Without any protection
against this situation, the software file in the EEPROM is incomplete
and the AT-VP504E FXS is not functional.
A transfer may be interrupted for the following reasons:
An electrical shortage can interrupt the transfer of the
software file from the RAM to the EEPROM.
The user of the AT-VP504E FXS can accidentally power
off the unit when the software file is being transferred
from the RAM to the EEPROM.
To avoid this situation, the AT-VP504E FXS emergency software
procedure (also called rescue application) automatically starts a new
software download.
Downloading
the Emergency
Software
You must download the latest emergency software into the
AT-VP504E FXS.
To download the latest emergency software (rescue application):
1. Setup the TFTP server that will be used to download the
software (see “Configuring the TFTP Server” on page 43).
2. Contact the AT-VP504E FXS with any SNMP MIB browser.
Be sure to use the MIB modules that match the version of the
MIBs located inside the current software build of the
AT-VP504E FXS.
3. Locate the tftpGroup category in the Provisioning MIB.
This category contains all the variables you must set to
properly download a software version. These variables
include:
• Binary file name to download
• Software server address where to get the binary
file
• Port number of the software server
This can be done statically through SNMP, automatically
through the Unit Manager, or dynamically through the DHCP
server.