3Com V6100, User Manual Manual, Page: 287 / 496

V6100 and V7122 User Guide
287
Automatic Update Mechanism
The V7122 is capable of automatically updating its cmp , ini and configuration files. These
files can be stored on any standard Web, FTP or NFS server/s and can be loaded
periodically to the gateway via TFTP (only for
cmp and ini files), HTTP, HTTPS, FTP or NFS.
This mechanism can be used even for Customer Premise(s) Equipment (CPE) devices that
are installed behind NAT and firewalls.
The Automatic Update mechanism is applied separately to each file. For the detailed list of
available files and their corresponding parameters, see
Table 43 .
The Automatic Update mechanism assumes the external Web server conforms to
the HTTP standard. If the Web server ignores the If-Modified-Since header, or
doesn’t provide the current date and time during the HTTP 200 OK response, the
gateway may reset itself repeatedly. To overcome this problem, adjust the update
frequency (AutoUpdateFrequency)
Three methods are used to activate the Automatic Update mechanism:
ƒ
After the V7122 starts-up (see the Startup process described in Figure 95 ).
ƒ
At a configurable time of the day (e.g., 18:00). This option is disabled by default.
ƒ
At fixed intervals (e.g., every 60 minutes). This option is disabled by default.
The following ini file example can be used to activate the Automatic Update mechanism.
Figure 94 Example of an ini File Activating the Automatic Update Mechanism
# DNS is required for specifying domain names in URLs
DnsPriServerIP = 10.1.1.11
# Load an extra configuration ini file using HTTP
IniFileURL = 'http://webserver.corp.com/3Com/inifile.ini'
# Load Call Progress Tones file using HTTPS
CptFileUrl = 'https://10.31.2.17/usa_tones.dat'
# Load Voice Prompts file using FTPS with user ‘root’ and password ‘wheel’
VPFileUrl = 'ftps://root:wheel@ftpserver.corp.com/vp.dat'
# Update every day at 03:00 AM
AutoUpdatePredefinedTime = '03:00'
# Note: The cmp file isn’t updated since it is disabled by default
(AutoUpdateCmpFile).