File Location For Automatic Update - AudioCodes Mediant 500L User Manual

Enterprise session border controller (e-sbc) & media gateway
Hide thumbs Also See for Mediant 500L:
Table of Contents

Advertisement

User's Manual
CLI Script File: Contains only CLI commands and configures all the device's
functionalities (except commands such as show, debug or copy). The file updates
the device's configuration only according to the configuration settings in the file.
The device's existing configuration settings (not included in the file) are retained.
The device does not undergo a reset and therefore, this file typically contains
configuration settings that do not require a device reset. If a reset is required, for
example, to apply certain settings, you must include the following CLI command
(root level) at the end of the file:
# reload if-needed
To configure the URL of the server where the file is located, use the
AUPDCliScriptURL ini file parameter or CLI command, configure system >
automatic-update > cli-script <URL>.
Startup Script File: Contains only CLI commands and configures all the device's
functionalities (except commands such as show, debug or copy). The file updates
the device's configuration according to the configuration settings in the file and
sets all other parameters that are not included in the file to factory defaults. The
file causes two device resets to apply the settings. Therefore, the file typically
contains the Automatic Update settings and other configuration settings that
require a device reset. The URL of the server where this file is located is
configured by the AUPDStartupScriptURL ini file parameter or CLI command,
configure system > automatic-update > startup-script <URL>.

48.2.2 File Location for Automatic Update

The files for updating the device can be stored on any standard Web (HTTP/S), TFTP, or
FTP, server. The files can be loaded periodically to the device using HTTP/S, TFTP, or
FTP, . This mechanism can be used even when the device is installed behind NAT and
firewalls. The Automatic Update feature is done per file and configured by specifying the
file name and URL address of the provisioning server where the file is located. For a
description of the parameters used to configure URLs per file, see ''Automatic Update
Parameters'' on page 1016.
Below are examples for configuring the file names and their URLs for Automatic Update:
ini File:
IniFileURL = 'http://www.corp.com/configuration.ini'
CptFileURL = 'http://www.corp.com/call_progress.dat'
AutoCmpFileUrl = 'http://www.corp.com/SIP_F7.00A.008.cmp
FeatureKeyURL = 'https://www.company.com/License_Key.txt'
CLI:
# configure system
(config-system)# automatic update
(automatic-update)# cli-script https://company.com/cli/<MAC>
(automatic-update)# startup-script https://company.com/startup/<MAC>
(automatic-update)# voice-configuration http://www.company.com/configuration.ini
(automatic-update)# call-progress-tones http://www.company.com/call_progress.dat
(automatic-update)# feature-key http://www.company.com/License_Key.txt
(automatic-update)# auto-firmware http://www.company.com/SIP_F7.00A.008.cmp
Note:
the device's MAC address for enabling the device to download a file unique to the
device. For more information, see ''MAC Address P;aceholder in Configuration File
Name'' on page 836.
Version 7.2
For configuration files (ini), the file name in the URL can automatically contain
835
Mediant 500L Gateway & E-SBC
48. Automatic Provisioning

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents