AudioCodes Mediant 4000 SBC User Manual page 736

Session border controllers
Hide thumbs Also See for Mediant 4000 SBC:
Table of Contents

Advertisement

CHAPTER 40    Automatic Provisioning
1.
If you have configured the device to authenticate itself to the HTTP/S server for secure
access, the device sends the access authentication username and password to the HTTP/S
server (for more information, see
succeeds, Step 2 occurs.
2.
The device establishes an HTTP/S connection with the URL host (provisioning server). If the
connection is HTTPS, the device verifies the certificate of the provisioning server, and
presents its own certificate if requested by the server.
3.
The device queries the provisioning server for the requested file by sending an HTTP Get
request. This request contains the HTTP User-Agent Header, which identifies the device to the
provisioning server. By default, the header includes the device's model name, MAC address,
and currently installed software and configuration versions. Based on its own dynamic
applications for logic decision making, the provisioning server uses this information to check if
it has relevant files available for the device and determines which files must be downloaded
(working in conjunction with the HTTP If-Modified-Since header, described further on in this
section).
You can configure the information sent in the User-Agent header, using the
[AupdHttpUserAgent] parameter or CLI command, configure system > http-user-
agent. The information can include any user-defined string or the following supported string
variable tags (case-sensitive):
<NAME>: product name, according to the installed License Key
<MAC>: device's MAC address
<VER>: software version currently installed on the device, e.g., "7.00.200.001"
<CONF>: configuration version, as configured by the ini file parameter, [INIFileVersion] or
CLI command, configuration-version
The device automatically populates these tag variables with actual values in the sent header.
By default, the device sends the following in the User-Agent header:
User-Agent: Mozilla/4.0 (compatible; AudioCodes;
<NAME>;<VER>;<MAC>;<CONF>)
For example, if you configure [AupdHttpUserAgent] to "MyWorld-<NAME>;<VER>(<MAC>)",
the device sends the following User-Agent header:
User-Agent: MyWorld-Mediant;7.00.200.001(00908F1DD0D3)
If you configure the [AupdHttpUserAgent] parameter with the <CONF> variable tag,
you must reset the device with a save-to-flash for your settings to take effect.
4.
If the provisioning server has relevant files available for the device, the following occurs,
depending on file type and configuration:
File Download upon each Automatic Update process: This is applicable to software
(.cmp) and configuration files.In the sent HTTP Get request, the device uses the HTTP If-
Modified-Since header to determine whether to download these files. The header contains
the date and time (timestamp) of when the device last downloaded the file from the
specific URL. This date and time is regardless of whether the file was installed or not on
the device. An example of an If-Modified-Since header is shown below:
If-Modified-Since: Mon, 1 January 2014 19:43:31 GMT
Access Authentication with HTTP
- 703 -
Mediant 4000 SBC | User's Manual
Server). If authentication

Advertisement

Table of Contents
loading

Table of Contents