# Define an Active Directory User Data Source

You can also choose to retrieve users from an existing Microsoft Active Directory server for the Speech Auto Attendant user data source. Both technologies use the LDAP protocol to look up/retrieve information.

To configure the user data source for Active Directory:

1. In the navigation tree, click Auto-Attendant. The Auto-Attendant menu items appear.

2. Click Data Source. The User Data Source window appears.

3. In the Source Type field, select Active Directory from the drop-down menu. The data source configuration fields for the LDAP server appear.

4. In the LDAP Server Address field, enter the fully qualified domain name (FQDN) of the LDAP server OR its IP address, OR the root Directory Server Entries (DSE).

   Note: To use the FQDN of the data source server or a root DSE, the NuPoint UM system must be configured to communicate with a DNS server that can resolve the FQDN of the LDAP server or root DSE.

5. In the LDAP Search Base field, enter the location in the Active Directory data structure from which the list of users should be fetched. Note: You can select the Recursive check box to tell the Auto-Attendant to browse sub-directories of that location (context) in the data structure.

6. In the LDAP Object Classes field, enter the LDAP entities that will be retrieved and used in the Auto-Attendant. You can specify alternate object classes if the LDAP server is configured to use the sub-class of the user. You can enter multiple object classes in this field, separated by commas.

7. In the LDAP SAA Private User Attribute field, enter the LDAP server Extended Attribute used to identify users as Private. (For example, the LDAP database might use an attribute called "extensionAttribute10" to hold the True or False flag for Private User? In this case, you would enter extensionAttribute10 in this field.)

8. In the LDAP SAA User Attribute field, enter the LDAP server Extended Attribute used to identify SAA enabled users. (For example, the LDAP database might use an attribute called "extensionAttribute11" to hold the True or False flag for SAA User? In this case, you would enter extensionAttribute11 in this field.)

9. In the LDAP SAA Default User Extension Attribute field, enter the LDAP server Extended Attribute used to identify the extension or telephone number to direct SAA calls to. (For example, "extensionAttribute12" may contain a reference to "homeTelephone" or "mobile". These are variables that are associated with telephone numbers in the LDAP database.

10. In the LDAP Administrator DN field, enter the administrator user credentials in order to retrieve data from the LDAP server.

11. In the LDAP Login Password field, enter the administrator password in order to retrieve data from the LDAP server.

12. ClickSave.

The system automatically selects every mailbox that is in the specified LDAP server data structure for the Speech Auto Attendant user data source. All users matching the configuration parameters will be picked up for the user data source.

You can exclude specific users from the Speech Auto Attendant user data source through the optional Active Directory Snap-In.

You can click the Test Connection button to test the connection for the current configuration. This test can take a few minutes to execute depending on various parameters (network latency, LDAP server performance, etc.). A dialog shows the progress and reports validity of the connection. In the case of an invalid connection, a message indicating the source of the connection problem is displayed.