Deploying phones from the boot server, Deploying phones from the boot server –14, Deploying phones from the – Polycom SIP 2.2.2 User Manual

Page 42: Boot server

Advertising
background image

Administrator’s Guide SoundPoint IP / SoundStation IP

3 - 14

3.

Copy all files from the distribution zip file to the phone home directory.
Maintain the same folder hierarchy.
The distribution zip file contains:
— sip.ld (including a separate one for every supported model)
— sip.cfg
— phone1.cfg
— 000000000000.cfg
— 000000000000-directory~.xml
— SoundPointIP-dictionary.xml
— SoundPointIPWelcome.wav
Refer to the Release Notes for a detailed description of each file in the

distribution.

Boot Server Security Policy

You must decide on a boot server security policy.

For organizational purposes, configuring a separate log file directory is

recommended, but not required. (For more information on

LOG_FILE_DIRECTORY, refer to

Master Configuration Files

on page

A-2

.)

File permissions should give the minimum access required and the account

used should have no other rights on the server.
The phone'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 phone

needs to read, such as the application executable and the standard

configuration files, should be made read-only through file server file

permissions.

Deploying Phones From the Boot Server

You can successfully deploy SoundPoint IP and SoundStation IP phones from

one or more boot servers.

Polycom recommends allowing file uploads to the boot server where the security
environment permits. This allows event log files to be uploaded and changes made
by the phone user to the configuration (through the web server and local user
interface) and changes made to the directory to be backed up.

Advertising