User's Manual 652 Document #: LTRT-10466
Mediant 500L MSBR
47.2.3 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.
47.2.4 Triggers for Automatic Update
The Automatic Update feature can be triggered by the following:
When the device is initially deployed (first-time deployment) in the network. This
trigger is referred to as Zero Configuration (see Zero Configuration on page
663).
Upon device startup (reset or power up). To disable this trigger, run the following CLI
command:
(config-system)# automatic-update
(automatic-update)# run-on-reboot off
Periodically:
• Specified time of day (e.g., 18:00), configured by the ini file parameter
AutoUpdatePredefinedTime or CLI command configure system > automatic-
update > predefined-time.
• Interval between Automatic Updates (e.g., every 60 minutes), configured by the
ini file parameter AutoUpdateFrequency or CLI command configure system >
automatic-update > update-frequency.
Centralized provisioning server request:
• Upon receipt of an SNMP request from the provisioning server.
• Upon receipt of a special SIP NOTIFY message from the provisioning server. The
NOTIFY message includes an Event header with the AudioCodes proprietary
value, "check-sync;reboot=false", as shown in the example below:
NOTIFY sip:<user>@<dsthost> SIP/2.0
To: sip:<user>@<dsthost>
From: sip:sipsak@<srchost>
CSeq: 10 NOTIFY
Call-ID: 1234@<srchost>
Event: check-sync;reboot=false