AudioCodes Mediant 500 E-SBC, User Manual

Page: 591 / 920

User's Manual 40. Automatic Update Mechanism
Version 6.8 591 Mediant 500 E-SBC
♦
ini:
CptFileURL = 'https://www.company.com/call_progress.dat'
♦
CLI:
(config-system)# automatic-update
(automatic-update)# call-progress-tones
http://www.company.com/call_progress.dat
(automatic-update)# tls-root-cert https://company.com/root.pem
Software (.cmp) File:
♦
ini:
CmpFileUrl =
'https://www.company.com/device/v.6.80A.227.005.cmp'
♦
CLI:
(config-system)# automatic-update
(automatic-update)# firmware
https://www.company.com/device/v.6.80A.227.005.cmp
Notes:
•
For one-time file download, the HTTP Get request sent by the device does not
include the If-Modified-Since header. Instead, the HTTP-User-Agent header can
be used in the HTTP Get request to determine whether firmware update is
required.
•
When downloading SSL certificates (Auxiliary file), it is recommended to use
HTTPS with mutual authentication for secure transfer of the SSL Private Key.
5. If the device receives an HTTP 301/302/303 redirect response from the provisioning
server, it establishes a connection with the new server at the redirect URL and re-
sends the HTTP Get request.
40.2.6 File Download Sequence
Whenever the Automatic Update feature is triggered (see 'Triggers for Automatic Update'
on page
588 ), the device attempts to download each file from the configured URLs, in the
following order:
1. ini file
2. Periodic software file (.cmp) download
3. One-time software file (.cmp) download
4. Auxiliary file(s)
The following files automatically instruct the device to reset:

Periodic software file (.cmp)

One-time software file (.cmp)
When multiple files requiring a reset are downloaded, the device resets only after it has
downloaded and installed all the files. However, you can explicitly instruct the device to
immediately reset for the following files:

ini file: Use the ResetNow in file parameter
Warning: If you use the ResetNow parameter in an ini file for periodic automatic
provisioning with non-HTTP (e.g., TFTP) and without CRC, the device resets after
every file download. Therefore, use this parameter with caution and only if necessary
for your deployment requirements.