Extended Administration
84
Configuration Management
During "Initialising" the phone will attempt to contact a configuration server
to determine if a configuration update is required.
The phone automatically contacts an FTP config server and downloads 2
XML configuration files in which phone-specific parameters may have
been automatically inserted by a customer management system for the
environment concerned.
• The phone can also perform this download
• on a signal from the customer management system or
• periodically as determined by a configurable time, or by an administra-
tion level optiGuide menu option.
If the downloaded configuration files show that a
different version of
software
is required, the phone will automatically initiate software down-
load from the FTP software server.
Two configuration files are used:
• a system-wide configuration file, which does not contain phone-specif-
ic parameters; and
• a device configuration file, which includes phone-specific parameters.
There is provision for downloading only a device configuration file so that
phone-specific parameters can be changed without impacting those sys-
tem-wide parameters that have been changed locally at the phone.
The configuration download mechanism is intended only for configuring
those phone parameters that are under administration control. It is not in-
tended for configuring parameters that are under user control. The chang-
es to the configuration will be reflected in the configuration INI file.
If the configuration download mechanism is not available, e.g. no FTP con-
figUD server, the phone will not perform configuration download and will
then rely on other means for configuration updates.
As a result of carrying out a configuration download, the phone will detect
whether a software update is required and if so automatically download
new software.
File Formats
Configuration files
The configuration files will be stored on the FTP server. There are two
types of configuration files:
System Wide File
The system-wide configuration file will have a well-known file name (e.g.,
"op410adv_conf.xml"), which does not contain phone-specific parameters.
Summary of Contents for HiPath 8000
Page 1: ...HiPath 8000 optiPoint 410 S V7 0 optiPoint 420 S V7 0 Administrator Manual ...
Page 114: ...Web Interface 114 Network IP and routing Network Addresses Æ page 57 ...
Page 115: ...Web Interface 115 SIP environment Configure System Information Æ page 61 ...
Page 116: ...Web Interface 116 SIP features SIP Features Æ page 64 Transfer on Ringing ...
Page 117: ...Web Interface 117 Quality of Service Quality of Service QoS Æ page 58 ...
Page 120: ...Web Interface 120 Time and date Configuring Date and Time Æ page 67 ...
Page 121: ...Web Interface 121 SNMP Use SNMP Æ page 92 Speech Change Speech Parameters Æ page 93 ...
Page 122: ...Web Interface 122 Ringer settings Configure Ringer Settings Æ page 94 ...
Page 124: ...Web Interface 124 Function keys Function Key assignments Æ page 74 ...
Page 126: ...Web Interface 126 Function key Select a function optiPoint 410 420 economy economy plus ...
Page 137: ...Web Interface 137 Address Book Address Book Æ page 162 WAP WAP Settings Æ page 81 ...
Page 141: ...Web Interface 141 RTP Statistics These parameters are used for development only ...
Page 142: ...Web Interface 142 QoS Data Collection These parameters are used for development only ...
Page 146: ...Web Interface 146 FPN Port Settings Only available in Web Interface ...