If file uploads are permitted, the boot server allows these local changes to be backed up automatically. Polycom recommends the boot server central provisioning model for installations involving more than a few phones. The investment required is minimal in terms of time and equipment, and the benefits are significant.
2.2.1.1 DHCP or Manual TCP/IP Setup Basic network settings can be derived from DHCP or entered manually using the phone’s LCD-based user interface. Polycom recommends using DHCP where possi- ble to eliminate repetitive manual data entry. The following table shows the manually entered networking parameters that may be...
The master configuration file, which references the other files and is always down- loaded and parsed by the phone, will need to change to reflect these name changes. Polycom does not recommend TFTP boot servers for actively managed systems. File name management is the responsibility of the System Administrator.
Page 19
If a phone does not find its own <Ethernet address>.cfg file, it will use this one, and establish a baseline configuration. This file is part of the standard Polycom distribution of configuration files. It should be used as the template for the <Ethernet address>.cfg files.
Page 20
Typical parameters include the IP address of an application server. All phones in an installation usually share application-specific files. This file would normally be modified from Polycom tem- plates. Contain parameters unique to a particular phone user. Typical parameters include: •...
Web Server <HTTPD/> on page 91. The phone’s local user interface also permits ® Instructions: Polycom recommends allowing file uploads to the FTP server where the security environment permits. This allows event log files to be uploaded and changes made by the phone user to the configuration (via the web server and local user interface) and changes made to the directory to be backed up.
Page 103
When defining a single .fon file, there is a need for a “font delimiter”, currently “Copyright Polycom Canada Ltd” is used as an embedded delimiter, but this can be configured using “font.delimiter”. The font delimiter is important to retrieve the dif- ferent mangled .fnt blocks.
4.6.1.16 Event Logging <logging/> Logging parameter changes can impair system operation. Do not change any logging parameters Warning! without prior consultation with Polycom. The event logging system supports the following classes of events: Level Interpretation Debug only High detail event class...
Page 113
Mode 4.6.1.16.2 Scheduled Logging Parameters <scheduled/> The phone can be configured to schedule certain advanced logging tasks on a periodic basis. These attributes should be set in consultation with Polycom. Each scheduled ® Permitted Values Default 0, 1...
Name of an internal system command to be periodically meric string executed. To be supplied by Polycom. Event class to assign to the log events generated by this command. This needs to be the same or higher than log.level.change.slog for these events to appear in the log.
Need help?
Do you have a question about the Version 1.4.x 17 and is the answer not in the manual?
Questions and answers