Siemens OPTIPOINT 410 S V6.0 - Manual (Page 15)

XML Configuration Management
A31003-J4260-M101-2-76A9, 03-2007
2-2 XML Configuration Management, Administrator Manual
xml_02.fm
File Formats
If the configuration download setup program is not available, for example, if a configuration up-
date server has not been installed, the phone does not initiate a download. In this case, an al-
ternative procedure must be used for the configuration update.
2.2 File Formats
2.2.1 Configuration Files
Configuration files are stored on the configuration server. There are two kinds of configuration
files.
2.2.1.1 System Configuration File
The system configuration file has a unique name for every phone model (for example,
op410adv_conf.xml). This file does not contain any phone-specific parameters (see
!
page
3-2).
2.2.1.2 Device Configuration File
Each device configuration file name contains the MAC address of the corresponding phone (for
example, op410adv_conf001E300A9F3.xml). This file only contains phone-specific parame-
ters (see
!
page 3-2).
2.3 Download
2.3.1 Downloading Configuration Files
Every phone expects a default account named "config" on the FTP server with the password
"config" (the plug-and-play settings are also located in the "Configuration management set-
tings" dialog on the phone’s Web interface
!
page 4-25). Once the configuration files have
been downloaded, the phone checks the file versions. To do this, it searches for a "system-
config-version" tag in the system configuration file and a "device-config-version" tag in the de-
vice configuration file.
The phone then compares the system configuration file version with the version in the last
download. If the version has changed, the phone executes the write instructions in the system
and device configuration files
If the system configuration file version has not changed but the device configuration file version
has, the phone only executes the write instructions from the device configuration file. If neither
version has changed, the action is terminated.