CHAPTER47 Automatic Provisioning
Mediant 1000 Gateway & E-SBC | User's Manual
Provisioning through OVOC
AudioCodes One Voice Operations Center (OVOC) server functions as a core-network provisioning
server. The device's SNMP Manager should be configured with the IP address of the OVOC
server, using one of the methods detailed in the previous sections. As soon as a registered device
contacts OVOC through SNMP, OVOC handles all required configuration automatically, upgrading
software as needed. This alternative method doesn't require additional servers at the customer
premises, and is NAT-safe.
HTTP/S-Based Provisioning using the Automatic
Update Feature
The Automatic Update feature can be used for automatic provisioning of the device through
HTTP/S. Automatic provisioning is useful for large-scale deployment of devices. In some cases,
the devices are shipped to the end customer directly from the manufacturer. In other cases, they
may pass through a staging warehouse. Configuration may occur at the staging warehouse or at
the end-customer premises.
The device may be preconfigured during the manufacturing process (commonly known as private
labeling). Typically, a two-stage configuration process is implemented whereby initial configuration
includes only basic configuration, while the final configuration is done only when the device is
deployed in the live network.
If you use the IniFileURL parameter for the Automatic Update feature, do not use the
Web interface to configure the device. If you do configure the device through the Web
interface and save (burn) the new settings to the device's flash memory, the IniFileURL
parameter is automatically set to 0 and Automatic Updates is consequently disabled.
To enable Automatic Updates again, you need to re-load the ini file (using the Web
interface or BootP) with the correct IniFileURL settings. As a safeguard to an
unintended save-to-flash when resetting the device, if the device is configured for
Automatic Updates, the 'Burn To FLASH' field under the Reset Configuration group in
the Web interface's Maintenance Actions page is automatically set to No by default.
● For a description of all the Automatic Update parameters, see Automatic Update
Parameters or refer to the CLI Reference Guide.
● For additional security, use HTTPS or FTPS. The device supports HTTPS (RFC
2818) and FTPS using the AUTH TLS method <draft-murray-auth-ftp-ssl-16>.
Files Provisioned by Automatic Update
You can use the Automatic Update feature to update the device with any of the following files:
■ Software file (cmp)
■ Auxiliary files (e.g., Call Progress Tones, SSL Certificates, SSL Private Key)
■ Configuration file:
● ini File: Contains only ini file parameters and configures all the device's functionality.
- 892 -
To Next Page
Loading...
Need help?
General
