11 LDAP Client Configuration

The Oracle Enterprise Communications Broker supports LDAP as a communications mechanism for interaction with an LDAP server. For many enterprises, this means utilizing Active Directory, a common LDAP-based service, to request information used in SIP session routing and authentication. The Oracle Enterprise Communications Broker's LDAP client requires configuration on the Oracle Enterprise Communications Broker and the LDAP server.

Configuration aspects of LDAP client configuration include:

• LDAP server access—The user specifies LDAP server location and access preferences.
• Routing queries—The user specifies the conditions wherein the Oracle Enterprise Communications Broker performs an LDAP dip to obtain location information (home agent) for FROM and REQUEST-URIs.
• AoR queries—Optionally searches for additional AoR matches in Active Directory so that it can create additional routes to target users that have contacts stored in separate records.
• SIP Authentication queries—As an optional registration authentication mechanism, LDAP client configuration can utilize domain authentication or customized authentication server configuration on the LDAP server, as follows:
  • The use of domain authentication requires an application be installed on the domain controller.
  • Customized authentication requires the specification of compatible authentication fields on both client and server.

Note:

The user must ensure that phone numbers in the LDAP database are unique. If the Oracle Enterprise Communications Broker encounters multiple records with the same number, the lookup fails.