DMCC applications can use the LDAP enterprise directory for user authorization. The user authorization process must comply with the enterprise directory policy.

To implement the enterprise directory authorization policy, you must administer the enterprise directory settings on the AE Services management console. You must configure the following settings on the Enterprise Directory page for DMCC authorization:

• Search Filter Attribute Name: Indicates the attribute name in the user record that corresponds to the username. DMCC attempts to match the username to the attribute value. For example, SAM-Account-Name in Windows Active Directory.

• Device ID Attribute: Indicates the attribute name in the user record that corresponds to the authorized device ID. For example, a phone number that contains a provisioned E.164 number for users.

When you select an authorization method, DMCC uses LDAP to query the user record for the provisioned device ID. DMCC caches the retrieved device ID, such as a phone number. DMCC uses the data from the LDAP database and you do not have to create users on the AE Services server for request authorization. For example, if you specify +13035381234 in the request as a Tel URL, the user record contains 13035381234 as an E.164 number or 5380112 as an extension.

For more information about applying advanced authentication policies for DMCC applications, see the following documents:

• Avaya Aura®Application Enablement Services Device, Media, and Call Control Java Programmer 's Guide, 02-300359

• Avaya Aura®Application Enablement Services Device, Media, and Call Control XML Programmer's Guide, 02-300358