Appendix: Configuring Ldap Servers; Microsoft Active Directory; Prerequisites; Adding H.350 Objects - TANDBERG N3 User Manual

7 Appendix: Configuring LDAP
Servers

7.1 Microsoft Active Directory

7.1.1 Prerequisites

These comprehensive step by step instructions assume that Active Directory is installed. For
details on installing Active Directory please consult your Windows documentation. The
following instructions are for Windows Server 2003 Enterprise Edition, if you are not using this
version of Windows, your instructions may vary.
The following ITU specification describes the schemas which are required to be installed on
the Active Directory server:
H.350 – Directory services architecture for multimedia conferencing - An LDAP

schema to represent endpoints on the network.
H.350.1 – Directory services architecture for H.323 – An LDAP schema to represent

H.323 endpoints.
H.350.2 – Directory services architecture for H.235 - An LDAP schema to represent

H.235 elements.
The schemas can be downloaded in ldif format from the web interface on the Gatekeeper. To
do this, navigate to the Gatekeeper Configuration > Files page and click on the links for the
schemas. Copy the downloaded schemas to the Active Directory server.
Open a command prompt and for each file execute the following command:
ldifde -i -c DC=X <ldap_base> -f filename.ldf
Where <ldap base> is the base DN for your Active Directory server.

7.1.2 Adding H.350 objects

Create the organizational hierarchy
Open up the Active Directory Users and Computers MMC snap-in. Under your base DN right
click and select New > Organizational Unit. Create an Organizational unit called h350.
NOTE
It is good practice to keep the H.350 directory in its own organizational unit to separate out
H.350 objects from other types of objects. This allows access controls to be setup which only
allow the Gatekeeper read access to the BaseDN and therefore limit access to other sections
of the directory.
Add the H.350 objects
Create an ldif file with the following contents:
# MeetingRoom1 endpoint
dn: commUniqueId=comm1,ou=h350,dc=my-domain,dc=com
objectClass: commObject
objectClass: h323Identity
objectClass: h235Identity
47