User`s manual

SIP User's Manual 11. Advanced System Capabilities
Version 5.0 249 October 2006
11.3 Automatic Update Mechanism
The gateway 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 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, refer to Table
6-2 on page 138.
Note: 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 gateway starts-up (refer to the Startup process described in Figure 11-3).
 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 11-2: 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/AudioCodes/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:[e-mail]/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).
Refer to the following notes:
 When HTTP or HTTPS are used, the gateway contacts the Web server/s and queries
for the requested files. The ini file is loaded only if it was modified since the last
automatic update. The cmp file is loaded only if its version is different from the version
stored on the gateway’s non-volatile memory. All other auxiliary files (e.g., CPT) are
updated only once. To update a previously-loaded auxiliary file, you must update the
parameter containing its URL.
 To load different configurations (ini files) for specific gateways, add the string ‘<MAC>’
to the URL. This mnemonic is replaced with the gateway's hardware MAC address.
Resulting in an ini file name request that contains the gateway’s MAC address.
 To automatically update the cmp file, use the parameter ‘CmpFileURL’ to specify its
name and location. As a precaution (to protect the gateway from an accidental
update), the Automatic Update mechanism doesn’t apply to the cmp file by default.
Therefore, (to enable it) set the parameter ‘AutoUpdateCmpFile’ to 1.