Deploying Phones From The Boot Server; Creating Configuration Files - Polycom SoundPoint IP 200W Provisioning And Configuration Manual

Deploying Phones From the Boot Server

Creating Configuration Files

Boot Server Security Policy
You must decide on a boot server security policy.
Polycom recommends allowing file uploads to the boot server where the
security environment permits. This allows changes made to the directory to be
backed up.
File permissions should give the minimum access required and the account
used should have no other rights on the server.
The gateway's server account needs to be able to add files to which it can write
in the log file directory and the root directory. It must also be able to list files
in all directories mentioned in the [MAC].cfg file. All other files that the
gateway needs to read, such as the application executable and the standard
configuration files, should be made read-only through file server file
permissions.
To deploy the SoundPoint IP 200W phone, perform the following tasks:
• Create the configuration files
• Deploy the phones
Optionally, you can set the handset and gateway security. Refer to
Handset and Gateway Security
The SoundPoint IP 200W phone can recognize encrypted or unencrypted files,
which it downloads from the boot server and it can encrypt files before
uploading them to the boot server. There must be an encryption key on the
phone to perform these operations.
You can encrypt the configuration file using the Windows application
"Endecryptfiles".
The location from which configuration files and firmware upload files can be
downloaded is preset. This URL can be changed through configuration (see
section 6.1), but resetting the gateway to factory defaults will change this
setting back.
The configuration file must be located in a subfolder named /Config meaning
that the full path name of the requested file must be one of the following:
• unencrypted version
<NETWORK_TFTP_SERVER>/Config/<MAC_ADDRESS>.cfg
on page 3-10.
Setting up Your System
Setting
3 - 3