Advanced LDAP Node Settings

Certain settings for authentication, presentation of results and adjustments to certain LDAP-capable end devices can be made from the root node for the LDAP database. These settings include:

To search the LDAP server, you will have to authenticate yourself for searching the LDAP server. The results will only be presented if the user name and password agree with the data in the LDAP node or with the LDAP Root Credentials. Access can be limited to an IP address range for certain end devices that do not support authentication.

Languages, Sorting and Phone Number Formatting
Select a location that you have setup from Location from here. The results of a search query will be sorted according to the rules for the country selected in the location. When connecting from LDAP-capable end devices, it may be necessary to include abbreviations for field names in the results in some cases. These abbreviations will also be used for the language selected. Phone number formatting will also be performed for the search and the results according to this location.

Phone Number Formatting
estos MetaDirectory supports a variety of phone number formats. As soon as the location has been defined, you can choose between the following phone number formats:

  • Unformatted:
    The phone number will be displayed using the international dialing format: +49301234567
  • Unformatted, reduced to internal numbers:
    The phone number will be presented using the international dialing format, reduced to internal numbers: 567
  • Legible:
    The phone number will be displayed in an easily readable format: +49 (30) 1234-567
  • Legible, reduced to internal numbers:
    The phone number will be displayed in an easily readable format, reduced to internal numbers: 567
  • Dialable:
    The phone number will be formatted for direct dialing. It will be prefixed with a corresponding external code as well as the necessary country and city codes: 567.

End Device Support
Integrating special LDAP-capable end devices is supported by templates. In addition to the pre-defined templates, the various options permit integration of any other telephone systems desired. The options in detail include:

  • Only searching phone books when there are not search results:
    Phone books will only be searched if no results are found in other databases.
  • Searching automatically for diacritical characters:
    With this option, all special diacritical forms of a character will be automatically sought in the LDAP database. Many LDAP end devices only support the ASCII character set. You will not be able to perform a search for Müller using such an end device.
    If this option has been enabled, the "Müller" record will also be found when searching for "Muller".
  • Display only results with telephone numbers:
    Only the results that include a phone number will be displayed. For this, all database fields that have been defined as telephone numbers in the Search Wizardwill be accessed.
  • End device only support one phone number per contact:
    If a contact containing more than one phone number is found, but the end device can only display one phone number per contact, a separate contact will be displayed for each phone number. To clarify for the end device which number is concerned, the name will be displayed with the abbreviation matching the database field from which the number originated.
  • Always sort results by:
    The results will be sorted by the selected attribute prior to being sent.
  • Restrict maximum length of results attributes to:
    This option will reduce the length of attributes to a specified number of characters.

Schema Mapping
In addition tot he options that can be configured from the interface, a schema replacement will be active with the selection of a pre-defined end device. Before the search request is passed to the LDAP server and before the results are returned to the client, estos MetaDirectory will replace pre-defined attributes in the request and the response. Thereby, an end device incapable of configuring which content should be sought in which database fields can be integrated. This schema mapping will be stored in the end device template files (*.termxml) in the config/default directory.

Version 3.5