Avaya XT Series Deployment Manual page 175

• A remote XT Series's built-in LDAP server
The contacts are read-only when browsing a remote XT Series's LDAP server. You can
access more than one of these LDAP servers, where each requires only the IP address of
the remote endpoint and its LDAP password.
• Avaya Meetings Management's built-in LDAP server
If the end point is connected to the cloud for auto-provisioning, the LDAP server is
automatically configured by Avaya Meetings Management.
The contacts of this server are read-only from the endpoint. You can define more than one
such server, specifying each IP address, port, and its LDAP username and password. The
resulting contact list is filtered to show only users with an endpoint associated with them.
Important:
If the Avaya Meetings Management LDAP server has a Root DN defined, you must
specify the RootDN field when accessing that LDAP server.
• A third-party LDAP server, such as Polycom CMA The contacts are read-only. You can
access more than one of these LDAP servers, where each requires only the IP address of
the remote endpoint and its LDAP password.
Important:
If a third-party LDAP server is selected, the contacts of local built-in LDAP server will not
be displayed.
• A generic LDAP server
The contacts of the generic LDAP are read-only from the endpoint. The LDAP tree must have
the following specific structure and naming conventions:
- The Root DN can be defined. For example, dc=company, dc=com.
- All users (inetOrgPerson entities) must be located under an organizational unit (ou) in the
LDAP tree. For example, ou=people.
- All endpoints (commObject entities) must be listed under an organizational unit called
h323Identity if they are to work with H.323, and SIPIdentity if they are to work as SIP
endpoints.
Since the XT Series works both as an H.323 and a SIP endpoint, all XT Series
commObject s should be listed under both organizational units.
- Each endpoint is represented by a commObject with its commUniqueId. Each
commObject contains the details of accessing this endpoint, and the user associated with
it. Define the following fields:
Table 44: commObject fields
Field
objectClass
objectClass
August 2020
Value
commObject
h323Identity
Deployment Guide for Avaya XT Series
Comments on this document? infodev@avaya.com
Configuring XT Series to use LDAP Directory
Comments
Use this exact value
Use this exact value
Table continues...
175