Polycom SOUNDPOINT SIP 2.2.0 - Manual (Page 58)

Administrator’s Guide SoundPoint IP / SoundStation IP
4 - 10
Configuration changes can performed centrally at the boot server or locally:
Local Contact Directory File Format
An example of a local contact directory is shown below. The subsequent table
provides an explanation of each element.
Doe
John
1001
1
1
0
0
0
0
Central
(boot server)
Configuration file:
sip.cfg Set whether the directory uses volatile storage on the phone
(required on the SoundPoint IP 500 platform for directories greater
than 25 entries).
• For more information, refer to Directory on page A-58 .
XML file:
000000000000-direct
ory.xml
A sample file named 000000000000-directory~.xml (Note the extra
“~” in the filename) is included with the application file distribution.
This file can be used as a template for the per-phone <Ethernet
address>-directory.xml directories (edit contents, then rename to
<Ethernet address>-directory.xml). It also can be used to seed
new phones with an initial directory (edit contents, then remove “~”
from file name). Telephones without a local directory, such as new
units from the factory, will download the 00000000000-directory.xml
directory and base their initial directory on it. These files should be
edited with an XML editor. These files can be downloaded once per
reflash.
For information on file format, refer to Local Contact Directory File
Format , the following section.
Central
(boot server)
continued XML file: address>-directory.
xml This file can be created manually using an XML editor.
For information on file format, refer to Local Contact Directory File
Format , the following section.
Local Local Phone User
Interface The user can edit the directory contents at will.
Changes will be stored in the phone’s flash file system and backed up
to the boot server copy of <Ethernet address>-directory.xml if this
is configured. When the phone boots, the boot server copy of the
directory, if present, will overwrite the local copy.