AudioCodes Mediant 3000, User Manual

Page: 553 / 872

Version 6.6 553 Mediant 3000
User's Manual 42. Automatic Update
42 Automatic Update
Automatic provisioning is useful for large-scale deployment of devices. In some cases, the
devices are shipped to the end customer directly from the manufacturer. In other cases,
they may pass through a staging warehouse. Configuration may occur at the staging
warehouse or at the end-customer premises.
The devices may be pre-configured during the manufacturing process (commonly known
as
private labeling ). Typically, a two-stage configuration process is implemented such that
initial configuration includes only basic configuration, while the final configuration is done
when the device is deployed in a live network.
Automatic provisioning can be used to update the following files:

Software file ( cmp)

Auxiliary files (e.g., Call Progress Tones)

Configuration file (ini)
The Automatic Update mechanism is applied per file, using specific parameters that define
the URLs to the servers where the files are located, and the file names (see Automatic
Update Parameters on page
856 ). These files can be stored on any standard Web, FTP, or
NFS server and can be loaded periodically to the device using HTTP, HTTPS, FTP, or
NFS. This mechanism can be used even for devices that are installed behind NAT and
firewalls.
The Automatic Update mechanism can be triggered by the following:

Upon device startup.

At a user-defined time of day (e.g., 18:00), configured by the ini file parameter
AutoUpdatePredefinedTime.

Periodically (e.g., every 60 minutes), configured by the ini file parameter
AutoUpdateFrequency.

Upon startup but before the device is operational, if the Secure Startup feature is
enabled (see 'Loading Files Securely (Disabling TFTP)' on page
561 ).

Upon receipt of a special SIP Notify message (see 'Remotely Triggering Auto Update
using SIP NOTIFY' on page
561 )
When implementing Automatic Updates using HTTP/S, the device determines whether the
file on the provisioning server is an updated one as follows:

Configuration file: The device checks the timestamp according to the HTTP server
response. Cyclical Redundancy Check (CRC) is only checked if the
AUPDCheckIfIniChanged parameter is enabled. The device downloads the
configuration file only if it was modified since the last successful configuration update.

Software file (cmp): The device first downloads the file and then checks if its version
number is different from the software version file currently stored on the device's flash
memory.

Auxiliary files (e.g., CPT): These files are updated only once. To update the auxiliary
file again, you must modify the settings of the related parameter that configures its
URL.
42.1 BootP Request and DHCP Discovery upon Device
Initialization
After the device powers up or is physically reset, it broadcasts a BootP request to the
network. If it receives a reply from a BootP server, it changes its network parameters (IP
address, subnet mask and default gateway address) to the values provided. If there is no
reply from a BootP server and if DHCP is enabled (DHCPEnable = 1), the device initiates a
standard DHCP procedure to configure its network parameters.