Http-Based Provisioning - AudioCodes Mediant 4000 SBC User Manual

User's Manual
The protocol can be HTTP, HTTPS, FTP, or TFTP. As shown above, the URL can include
both the software and configuration filenames. In this case, they must be separated by a
semicolon (;) and without spaces.
If the URL does not specify a configuration filename or the file does not exist on the
provisioning server, the device requests from the server a "default" configuration file whose
name includes the device's product name and MAC address (<Product><MAC>.ini, for
example, "M800B00908f5b1035.ini"). If this "default" file also does not exist on the server,
the device attempts to retrieve another "default" configuration file whose name includes
only the device's product name (<Product>.ini, for example, "M800B.ini"). The device
makes up to three attempts to download the configuration file if a failure occurs (i.e., file not
exist or any other failure reason). This applies to each of the configuration files, as
mentioned previously.
If the URL specifies a software file, the device makes only one attempt to download the file
(even if a failure occurs). If the URL does not specify a software file, the device does not
make any attempt to download a software file.
Once the device downloads the file(s), it undergoes a reset to apply the configuration
and/or software. In addition, once the file(s) has been downloaded, the device ignores all
future DHCP Option 160 messages. Only if the device is restored to factory defaults will it
process Option 160 again (and download any required files).

To enable provisioning using DHCP Option 160:
1. Make sure that the DHCP server is configured with the appropriate information
(including the URL address of the provisioning server for Option 160).
2. Make sure that the required configuration and/or software files are located on the
provisioning server.
3. Enable DHCP client functionality, as described in DHCP-based Provisioning on page
661.
4. Enable the device to include DHCP Option 160 in the DHCP Parameter Request List
field of the DHCP request packet that is sent to the DHCP server. Do this by loading
an ini file to the device with the following parameter setting:
DhcpOption160Support = 1
5. Reset the device with a save-to-flash for your settings to take effect.

41.1.2 HTTP-based Provisioning

An HTTP or HTTPS server can be located in the network in which the device is deployed,
storing configuration and software files for the device to download. This does not require
additional servers and is NAT-safe.
For example, assume the core network HTTPS server is https://www.corp.com. A master
configuration
https://www.corp.com/gateways/master.ini. This file could point to additional ini files,
Auxiliary files (e.g., call progress tones), and software files (cmp), all on the same HTTP
server or different HTTP servers in the network.
The main advantage of this method is that the device can be configured to periodically
check the HTTP server for file updates. HTTP(S) is not sensitive to NAT devices, enabling
configuration whenever needed without on-site intervention. For additional security, the
URL may contain a different port, and username and password.
The only configuration required is to preconfigure the device(s) with the URL of the initial
(master) ini file. This can be done using one of the following methods:

DHCP, as described in ''DHCP-based Provisioning'' on page 661 or via TFTP at a
Version 7.2
ini file can
663
be stored on
41. Automatic Provisioning
the server,
Mediant 4000 SBC
e.g.,