Installation guide

Figure 5-40 Viewing and editing contacts in Local LDAP server
You can define three types of LDAP servers:
The local built-in LDAP server
You can define only one local LDAP server. When selected, you can edit, create or delete
the details of any contacts stored locally (Figure 5-40 on page 96). The local LDAP server
has a password which can be changed if needed.
Note
You cannot remove the local LDAP server.
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
define more than one of these LDAP servers, where each requires only the IP address of
the remote endpoint and its LDAP password.
SCOPIA Management's built-in LDAP server
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 registered to an endpoint.
Note
If the SCOPIA Management LDAP server has a Root DN defined, you must specify the
RootDN field when defining that LDAP server.
A third-party LDAP server, such as Microsoft Active Directory
The contacts of a third party LDAP are read-only from the endpoint. The LDAP tree must
have the following specific structure and naming conventions:
The Root DN must 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
commObjects should be listed under both organizational units.
RADVISION | Installation Guide for SCOPIA XT5000 Series Version 3.1 Initial Configuration | 96