EasyManuals Logo

AudioCodes MSBG Series User Manual

AudioCodes MSBG Series
1195 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #784 background imageLoading...
Page #784 background image
User's Manual 784 Document #: LTRT-27045
Mediant 1000B Gateway & E-SBC
c. Click Apply.
To enable through CLI: configure voip > sip-definition advanced-settings > sip-
remote-reset.
45.2.6 Access Authentication with HTTP Server
You can configure the device to authenticate itself with the HTTP/S server. The device
authenticates itself by providing the HTTP/S server with its authentication username and
password. You can configure one of the following HTTP authentication schemes:
Basic Access Authentication: The device provides its username and password to
the HTTP server. The username and password is configured in the URL that you
define for downloading the file:
ini file:
AutoCmpFileUrl = 'https://<username>:<password>@<IP address
or domain name>/<file name>'
CLI:
# configure system
(config-system)# automatic update
(automatic-update)# auto-firmware https://<username>:<password>@<IP
address or domain name>/<file name>
Digest Access Authentication: The authentication username and password is
negotiated between the device and HTTP/S server, using digest MD5 cryptographic
hashing. This method is safer than basic access authentication. The digest
authentication username and password are configured using the
AUPDDigestUsername and AUPDDigestPassword parameters, respectively.
45.2.7 Querying Provisioning Server for Updated Files
Each time the Automatic Update feature is triggered, for each file and its configured URL
the device does the following:
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 ''Access Authentication with HTTP Server''
on page 784). If authentication 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"

Table of Contents

Other manuals for AudioCodes MSBG Series

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the AudioCodes MSBG Series and is the answer not in the manual?

AudioCodes MSBG Series Specifications

General IconGeneral
BrandAudioCodes
ModelMSBG Series
CategoryGateway
LanguageEnglish

Related product manuals