Multiple boot servers can be configured by having the boot server DNS name
map to multiple IP addresses. The default number of boot servers is one and
the maximum number is eight. The following protocols are supported for
redundant boot servers: HTTPS, HTTP, and FTP. For more information on the
protocol used on each platform, refer to
page 3-4.
All of the boot servers must be reachable by the same protocol and the content
available on them must be identical. The parameters described in section
Server Menu
server will be tried for a file transfer and also how long to wait between each
attempt. The maximum number of servers to be tried is configurable. For more
information, contact your Certified Polycom Reseller.
Be aware of how logs, overrides and directories are uploaded to servers that maps
Note
to multiple IP addresses. The server that these files are uploaded to may change
over time.
If you want to use redundancy for uploads, synchronize the files between servers in
the background.
However, you may want to disable the redundancy for uploads by specifying
specific IP addresses instead of URLs for logs, overrides, and directory in the
<MAC-address>.cfg .
To set up the boot server:
Use this procedure as a recommendation if this is your first boot server setup.
Note
1. Install boot server application or locate suitable existing server(s).
Polycom recommends that you use RFC-compliant servers.
2. Create account and home directory.
If the provisioning protocol requires an account name and password, the server
Note
account name and password must match those configured in the phones. Defaults
are: provisioning protocol: FTP, name: PlcmSpIp, password: PlcmSpIp.
Each phone may open multiple connections to the server.
The phone will attempt to upload log files, a configuration override file,
and a directory file to the server. This requires that the phone's account has
on page
3-9
can be used to configure the number of times each
Setting up Your System
Supported Provisioning Protocols
on
3 - 13
Need help?
Do you have a question about the SIP 3.0.2 and is the answer not in the manual?