Filter
Top Products
TANDBERG Border Controller User Manual
B.2.2 Installing the H.350 schemas
The following ITU specification describes the schemas which are required to be installed on the
LDAP server:
H.350 Directory services architecture for multimedia conferencing - An LDAP schema to repre-
sent endpoints on the network.
H.350.1 Directory services architecture for H.323 - An LDAP schema to represent H.323 end-
points.
H.350.2 Directory services architecture for H.235 - An LDAP schema to represent H.235 ele-
ments.
The schemas can be downloaded in ldif format from the web interface on the Border Controller.
To do this, navigate to the Border Controller Configuration → Files page and click on the links for
the schemas.
Copy the downloaded schemas to the OpenLDAP schema directory:
/etc/openldap/schemas/commobject.ldif
/etc/openldap/schemas/h323identity.ldif
/etc/openldap/schemas/h235identity.ldif
Edit /etc/openldap/slapd.conf to add the new schemas. You will need to add the following lines:
include /etc/openldap/schemas/commobject.ldif
include /etc/openldap/schemas/h323identity.ldif
include /etc/openldap/schemas/h235identity.ldif
The OpenLDAP daemon (slapd) must be restarted for the new schemas to take effect.
B.2.3 Adding H.350 objects
Create the organizational hierarchy
Create an ldif file with the following contents:
# This example creates a single organisational unit to contain
# the H.350 objects
dn: ou=h350,dc=my-domain,dc=com
objectClass: organizationalUnit
ou: h350
Add the ldif file to the server using the command:
slapadd -l <ldif file>
This organizational unit will form the BaseDN to which the Border Controller will issue searches.
In this example the BaseDN will be ou=h350,dc=my-domain,dc=com.
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 Border Controller read access to the BaseDN and therefore limit access to other
sections of the directory.
69