Skip to main content
Skip table of contents

Active Directory Replicated Directories

If you choose Active Directory source for your replicated directory, when you hit image-20250616-145227.png you get the following new menu:

image-20250626-064402.png

Connection parameters

In this section, you can configure the Active Directory connection settings:

image-20250626-072306.png
  • Active Directory host → This is AD server’s IP or FQDN

  • Port → TCP port for AD connection. Typically, 389 for unsecure connection.

  • Security → Pull-down menu with different connection options:

    • Anonymous → Unsecure anonymous login

    • Basic → Unsecure login using authntication

    • Security, Security/Kerberos, Security/SSL, Security/Encrypt → Currently NOT supported. Please leverage LDAP Source Directory connector instead.

  • Search subtree → Check this flag to allow contacts import across all AD subtrees.

  • DN user → Service account username, with read permissions across whole AD structure.

  • Password → Service account password

  • Base DN → AD path including all domains and OUs to be imported.

  • LDAP Filter → Optional filter to apply while importing AD contacts.

A useful Test connection button allows to immediately test AD reachability and login credentials. If the test is successful, the message “Bind success” is displayed.

Import parameters

Here you can configure automatic import interval, source file(s) and other rules. See below sample:

image-20250626-072529.png
  • Import mode → Choose from pull-down menu how to feed data in the directory:

    • Disabled → directory update is suspended

    • Manual → directory update must be manually triggered

    • Periodic check → Directory update is performed at a specific time, up to 5 different time slots.

    • After import → When a previous import is completed.

  • Import time (hh:mm) → If above “Periodic check” is selected, then the automatic import is triggered up to five times per day, at the configured time slots.

  • Minimum number of contacts → This is the new/updated contacts threshold to trigger the periodical check. if contact changes are below this value, then automatic import is not performed and you can run the manual import instead.

  • Apply global dial rules → If checked, phone numbers normalization is applied, as per global Numbers' Format table.

  • Import postfix : separator and postfix → Here you can add a postfix to the imported columns and, if a delimiter is defined, you can replace the value after the delimiter with the configured postfix value.

Columns/attributes

In this section, you can define the structure of your AD import, by adding all the attributes to import, with relevant internal column name. AD connector includes a Default values structure, including most common attributes. See below:

image-20250626-073312.png

You can Select any existing row and modify field mapping. You can also remove unused attributes by clicking Delete. Finally, you can Add more AD attributes, with relevant field mapping. For each row, the following setting must be applied:

  • Internal column name → Pull-down menu including all available contact fields. Just pick the one to be added in the structure.

  • Four different mapping options:

    • Predefined attribute → Pull-down menu including most common AD attributes.

    • Free attribute/field → If required AD attribute is not included in the predefined list, you can manually add it here. This option also allows to concatenate multiple attributes into a single contact field, like “[ipPhone] [custom1]”.

    • Constant → Just fill contact field with a fixed value.

    • Empty → Blank this field.

image-20250626-073929.png

Hit Validate to save new/amended attribute. Once all fields have been added, you can Save.

Numbers' format

Within this section, you can apply multiple rules to “normalize” phone numbers to local dial rules. For example, you can instruct the system to add a prefix for outside line breakout or to replace ‘+' with '00’ for international dialing. See below:

image-20250617-082518.png

Each rule includes the following details:

  • phone number digits range when to apply the rule

  • RegEx flag, which allows you to add a complex rule based on a RegEx expression.

  • Prefix to be matched or RegEx expression

  • Value to replace the prefix

  • Text comment of your choice, to remind the rule purposes

A Test rules button allows to add a phone number and get the resulting normalized number after having applied all matched rules.

Filtering criteria

This section allows to apply filters while importing contacts data from AD source. These filters are added on top of the overall LDAP filter applied in the Connection parameters.

Two different filter types are available:

  • Include criteria → Import contacts which are fulfilling all criteria in the list.

  • Exclude criteria → Import contacts which are NOT fulfilling criteria in the list.

For each filter item, you can select the attribute to match, the criteria expression and the matching field value. Hit Validate to add each filter.

image-20250617-083836.png

Once all filters have been added, hit Save.

Segmentation zones

If you wish to limit the access to this directory to specific phone devices configured in your CUCM, then you can apply the segmentation. For this purpose, you can select how your segmentation is applied from pull-down Type menu: Device Pool, Calling Search Space, Locations, IP Addresses range. See below:

image-20250617-084829.png

If you have applied recent changes to your CUCM config, please hit Reload cache button prior to apply segmentation.

Once segmentation rule is applied, hit Save.

Please remember that segmentation is applied to one type only. For example, you can’t apply segmentation based on CSS + DP.

Key columns

It might happen that different import sources include some duplicated contacts. To avoid same contact duplication in Imagicle ConMan Entp. directories, you can define the “Distinct Column(s)” including key data, which should not be duplicated.

Up to five contact fields can be used to avoid duplications, even if we recommend to leverage just one contact field to avoid performances issues (i.e. sAMAccountName). The Distinct treatment pull-down menu allows to select how duplicated contacts are merged or just discarded:

  • Keep only first contact → First contact found is saved. Any following duplicates are ignored.

  • Merge phone columns → First contact found is saved. If following duplicates include additional phone attributes, they are added in the first entry.

  • Merge all columns → First contact found is saved. If following duplicates include additional attributes, they are added in the first entry.

  • Left Join → First contact found is saved. If same contact is included into a second directory, you can merge all missing attributes in the first entry.

image-20250617-090947.png
  • Source directory of contacts to remove → Choose from pull-down menu which directory should be considered as master for duplicated contacts. If you keep (none) default setting, then above treatment is applied as per import sequence. If a specific directory is selected, then duplicated contacts are remove from other directories but master one.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.