The Local Central Directory provides to the connected handsets a Central Address book which is stored on the base itself.

How to load the Local Central Directory to the base

The Local directory import can be performed in 2 ways:

  • manually uploading the directory file
  • configuring the base to download the local directory file from a server

Manually uploading the directory:

In order to manually upload the directory you need first to prepare the directory file (see the supported formats below). Once you have the directory file you should:

  1. logon on the base web interface
  2. click on the Central Directory menu
  3. make sure the Location is set to Local
  4. under the Import Central Directory section click on the Select file button
  5. select the directory file from your computer
  6. click the Load button

Some seconds after clicking the Load button the registered handsets will display the Central Directory soft key and icon on the middle of screen.

Configuring the base to download the local directory

First of all you have to prepare the address book file in a tbook format (see the supported formats below). Now you can proceed configuring the download:

  1. logon on the base web interface
  2. click on the Central Directory menu
  3. make sure the Location is set to Local
  4. fill the Server field with the HTTP URL of the directory up to the last folder (Eg.: http://server.com/snom-directory/ )
  5. fill the Filename field with the name of the XML file (Eg. snom_directory.xml)
  6. optionally set a reload interval (in seconds), please avoid too short intervals that can overload the base and server
  7. click the Save button

After clicking the Save button the base will download the directory file and the handsets will show the Central Directory soft key and icon on the middle of screen.


Please note that the Server and the Filename fields will be concatenated to create the download URL, so don't forget to add the trailing slash to on the Server or the starting slash on the Filename, some examples:


Server field
Filename field
Concatenated URL
Note
http://172.16.18.22
tbook.xml
http://172.16.18.22tbook.xml
FAIL: Malformed URL
http://172.16.18.22/folder
tbook.xml

http://172.16.18.22/foldertbook.xml

FAIL: Malformed URL

http://172.16.18.22/folder
/tbook.xml

http://172.16.18.22/folder/tbook.xml

OK: Well formed URL

http://172.16.18.22/
tbook.xml

http://172.16.18.22/tbook.xml

OK: Well formed URL
http://172.16.18.22
/tbook.xml
http://172.16.18.22/tbook.xml

OK: Well formed URL

http://172.16.18.22/
/tbook.xml

http://172.16.18.22//tbook.xml

WARNING: double slash not supported by some HTTP server

Local Directory supported formats

The Local Directory can be imported via web interface or downloaded from the base in three different formats:

  1. tbook
  2. IPPhoneDirectory
  3. CSV

The tbook format

The tbook format is an XML-based file where you can define the name and the number, the number will be listed as Home number. You cannot have multiple numbers per contact. Tbook format can be used only on downloaded Local directory. Here an example:

<?xml version="1.0"?>
<tbook>
  <item>
    <name>John Doe</name>
    <number>230</number>
  </item>
  <item>
    <name>Ray Albert</name>
    <number>211</number>
  </item>
  <item>
    <name>Tony Green</name>
    <number>223</number>
  </item>
</tbook>

The IPPhoneDirectory format

This format is an XML file suitable only for manual uploading on the base, using this format you can define Home, Office and Mobile phone types, here an example:

<?xml version="1.0"?>
<IPPhoneDirectory>
    <DirectoryEntry>
        <Name>John Doe</Name>
        <Telephone>123</Telephone>
        <Office>345</Office>
        <Mobile>123</Mobile>
    </DirectoryEntry>
    <DirectoryEntry>
        <Name>Ray Albert</Name>
        <Telephone>8971</Telephone>
        <Office>1233</Office>
        <Mobile>1233</Mobile>
    </DirectoryEntry>
</IPPhoneDirectory>

CSV

This is the simplest directory file: is a comma separated value file composed by 2 columns, the first one is the contact name, second is the number. The CSV format is suitable only for manual uploading on the base. Here an Example:

Mark,9345
Jack,+493011111111
Kurt Maier (snom),8745
Mary Miller,9856
Miller Mary,9856
Dr. Smith,(917)5550145
Dr. Smith,917 555 0145
Tim Meier,(040)111111111

Note: 

  • the name filed must not exceed the 23 characters
  • the name field cannot contain the comma
  • the number field cannot exceed the 21 chiphers
  • the number filed can contains only digits, space, parentheses and the + symbol


Format
Valid for download / provisioning
Valid for manual upload
tbook
YES
NO
IPPhoneDirectory
NO
YES
CSV
NO
YES


At the bottom of this page you can download the directory files examples.

Removing a Local Directory from a base

In case you need to remove the Local directory from a DECT base you have to:

  1. logon on the base web interface
  2. click on the Central Directory menu
  3. click the Load button without selecting any file from your computer

This will wipe out the Local directory from the base.

Local Directory and Multicell deployments

In a multicell deployment usage of Local Directory should be considered keeping in mind the following concepts:

  • the settings regarding the Local Directory (Server Address, Filename, etc..) are synchronised via the multicell
  • the Local Directory data are not synchronised via the multicell: each base is responsible for his own local directory
  • in case the Local Directory is downloaded form the base, all the bases on the system will download the address book, make sure all the bases can access the server providing the directory file
  • in case of manual uploading of the Central Directory, the directory must be manually uploaded on all the bases of the system
  • an handset will load the Central Directory from the base where the SIP registration is located. Example: if an handset is DECT-wise registered to the base A and the SIP registration is handled on the base B, such handset will access the Local Directory of the base B
  • the downloaded Central Directory is stored on permanent memory: in case the download URL isn't accessible the base will keep the downloaded data, the data will persist a reboot