In many deployments a centralized provisioning server is used for the software update and
configuration functions. The handset supports several methods to ‘discover’ this provisioning
server:
Static You can manually configure the server address from the handset's user
interface or the Web Configuration Utility, or you can pre-provision the handset with an
initial provisioning server. The parameters are:
device.prov.serverName.set="1" and device.prov.serverName="" in a
configuration file.
DHCP DHCP option 66 is used to provide the address or URL of the provisioning
server.
DHCP INFORM The handset makes an explicit request for a DHCP option (which can
be answered by a server that is not the primary DHCP server). For more information,
see RFC 3361 and RFC 3925.
To change these parameters, go to Provisioning Server Menu.
Supported provisioning protocols
The Updater performs the provisioning functions of uploading log files, master configuration
files, software updates, and device setting menu changes.
By default, handsets are shipped with FTP enabled as the provisioning protocol. You can
change the provisioning protocol by updating the Server Type option. Or, you can specify a
transfer protocol in the Server Address, for example, http://usr:pwd@server (see Provisioning
Server Menu). The Server Address can be an IP address, domain string name, or URL. It can
be obtained through DHCP.
Supported protocols include: ftp, ftps, tftp, http and https.
In some cases a config file might need to be secured. You can use unique credentials to
connect to a server and include the transfer protocol in the configuration file name. For example,
https://usr:pwd@server/dir/file.cfg.
If a user name and password are specified as part of the server address or file name, they will
be used only if the server supports them. If a user name and password are required but not
specified, the device settings are sent to the server.
To Next Page
Loading...
