![Azatel AzaCall200 Administrator'S Manual Download Page 113](http://html1.mh-extra.com/html/azatel/azacall200/azacall200_administrators-manual_3042505113.webp)
100
Administrator Guide – AzaCall200 VOIP Multi-Protocol Gateway
Condition 5:
It means that gateway device is out of service or boot code is not functioning properly.
Appendix C.
Software Description
The different software associated with the gateway device can be classified into 3 types: boot
code, firmware, and configuration.
Boot code:
Stored in the device’s FLASH memory and is necessary to boot up a system.
- The gateway device allows administrators to upgrade the boot code when necessary.
- Please note that if boot code becomes corrupt while upgrading, do not reboot the device with the
corrupt boot code and immediately run the upgrade commands to perform the upgrade again. Rebooting
the device with corrupt boot code may cause the gateway device to become unstable and experience a
system-hang condition.
- To recover from such hang condition, copy the entire software (boot code + firmware) into the gateway
device’s Flash memory using a FLASH Programmer rather than via TFTP. It may be necessary to remove
the Flash memory chip from the PCB for this procedure.
- For additional upgrade procedures, please refer to section A.2.2.
Firmware (AP):
Stored in the device’s FLASH memory and is necessary to provide VOIP service.
There are 3 ways to upgrade the firmware for the gateway device. Generally speaking, the Auto
Provisioning function can download the latest firmware from the provisioning server automatically; users
however, may upgrade the firmware themselves via the web interface. If upgrade fails and the firmware
becomes corrupt, the administrator can also log into maintenance mode to recover the device via remote
telnet or console port. For additional upgrade procedures, please refer to section A.2.2.
Configuration:
Stored in the FLASH or RAM, depending on whether configurations have been saved into
FLASH or not.
The gateway device’s configuration file can be upgraded using the same 3 approaches as the firmware. If
the users do not specify any configurations, the system will create a default configuration as long as the
firmware is working.
For additional upgrade procedures, please refer to section A.2.2.
In addition to the types of software codes described above, another item worth mentioning is the
“
Board ID
”. When a user or administrator upgrades firmware using any of the approaches
described above, the firmware version used will depend on a “compatible list” which specifies if
the firmware version is suitable given the BoardID residing in the gateway device.
Appendix D.
Recovery Procedure
The following recovery procedures may apply when neither auto provisioning nor web interface
is working, and the boot code has a version number of V1.6.5j or later.