D.3.3 Configuring an H.350 Directory with Active Directory Server

D.3.3.1 Notes

These instructions were written using Windows 2003. It is possible to create an H.350 Directory in Windows 2000, but by a different method. Please email Jason L. W. Lynn for more information.

D.3.3.2 Requirements

• A running Active Directory Server on Windows 2003
• Knowledge of the following values :
  • The base DN of the Active Directory Server
• Familiarity with A Recipe for Configuring and Operating LDAP Directories.

D.3.3.3 Components

• Directory Server
  • This is the actual LDAP directory server.
• callPreferenceURIObject LDIF File
  • This is the file that contains the changes necessary to support the callPreferenceURIObject object.
• commObject LDIF File
  • This is the file that contains the changes necessary to support the commObject object.
• genericIdentity LDIF File
  • This is the file that contains the changes necessary to support the genericIdentity object.
• h235Identity LDIF File
  • This is the file that contains the changes necessary to support the h235Identity object.
• h320Identity LDIF File
  • This is the file that contains the changes necessary to support the h320Identity object.
• h323Identity LDIF File
  • This is the file that contains the changes necessary to support the h323Identity object.
• sipIdentity LDIF File
  • This is the file that contains the changes necessary to support the sipIdentity object.

D.3.3.4 Resources

• callPreferenceURIObject LDIF file
  • http://lab.ac.uab.edu/vnet/documents/ldif/callPreferenceURIObject.ldf

• commObject LDIF file
  • http://lab.ac.uab.edu/vnet/documents/ldif/commObject.ldf

• genericIdentity LDIF file
  • http://lab.ac.uab.edu/vnet/documents/ldif/genericIdentity.ldf

• h235Identity LDIF file
  • http://lab.ac.uab.edu/vnet/documents/ldif/h235Identity.ldf

• h320Identity LDIF file
  • http://lab.ac.uab.edu/vnet/documents/ldif/h320Identity.ldf

• h323Identity LDIF file
  • http://lab.ac.uab.edu/vnet/documents/ldif/h323Identity.ldf

• sipIdentity LDIF file
  • http://lab.ac.uab.edu/vnet/documents/ldif/sipIdentity.ldf

D.3.3.5 Legend

Because of the differences in individual needs, certain parameters of the installed Active Directory Server may be quite different from the typical install. It is for this purpose that the following legend was created.

Parameter	Value	Example
The fully qualified domain name of the server on which Active Directory is running	<ldap_host>	h350.uab.edu
The base DN for the Active Directory Server	<ldap_base>	DC=h350,DC=uab,DC=edu
The fully qualified path to a temporary directory in Windows	<temp_dir>	C:\temp

D.3.3.6 Instructions

(1) Download the latest callPreferenceURIObject LDIF file and save it in the temporary directory <temp_dir>.

(2) Download the latest commObject LDIF file and save it in the temporary directory <temp_dir>.

(3) Download the latest genericIdentity LDIF file and save it in the temporary directory <temp_dir>.

(4) Download the latest h235Identity LDIF file and save it in the temporary directory <temp_dir>.

(5) Download the latest h320Identity LDIF file and save it in the temporary directory <temp_dir>.

(6) Download the latest h323Identity LDIF file and save it in the temporary directory <temp_dir>.

(7) Download the latest sipIdentity LDIF file and save it in the temporary directory <temp_dir>.

(8) Open a command prompt and change your current working directory to the temporary directory <temp_dir>.

(9) Run the following command.

ldifde -i -c DC=X <ldap_base> -f callPreferenceURIObject.ldf

(10) You should see the following output.

Connecting to "<ldap_host>"

Logging in as current user using SSPI

Importing directory from file "callPreferenceURIObject.ldf"

Loading entries.........

7 entries modified successfully.

(11) Run the following command.

ldifde -i -c DC=X <ldap_base> -f commObject.ldf

(12) You should see the following output.

Connecting to "<ldap_host>"

Logging in as current user using SSPI

Importing directory from file "commObject.ldf"

Loading entries.........

8 entries modified successfully.

(13) Run the following command.

ldifde -i -c DC=X <ldap_base> -f genericIdentity.ldf

(14) You should see the following output.

Connecting to "<ldap_host>"

Logging in as current user using SSPI

Importing directory from file "genericIdentity.ldf"

Loading entries.........

8 entries modified successfully.

(15) Run the following command.

ldifde -i -c DC=X <ldap_base> -f h235Identity.ldf

(16) You should see the following output.

Connecting to "<ldap_host>"

Logging in as current user using SSPI

Importing directory from file "h235Identity.ldf"

Loading entries.........

8 entries modified successfully.

(17) Run the following command.

ldifde -i -c DC=X <ldap_base> -f h320Identity.ldf

(18) You should see the following output.

Connecting to "<ldap_host>"

Logging in as current user using SSPI

Importing directory from file "h320Identity.ldf"

Loading entries............

11 entries modified successfully.

(19) Run the following command.

ldifde -i -c DC=X <ldap_base> -f h323Identity.ldf

(20) You should see the following output.

Connecting to "<ldap_host>"

Logging in as current user using SSPI

Importing directory from file "h323Identity.ldf"

Loading entries.................

16 entries modified successfully.

(21) Run the following command.

ldifde -i -c DC=X <ldap_base> -f sipIdentity.ldf

(22) You should see the following output.

Connecting to "<ldap_host>"

Logging in as current user using SSPI

Importing directory from file "sipIdentity.ldf"

Loading entries..............

13 entries modified successfully.

(23) Active Directory should now contain the necessary attributes and classes to support an H.350 Directory.

(24) Navigate to Start, Run and type '%SYSTEMROOT%\system32\domain.msc' in the text box.

(25) Click 'OK' to run the command.

(26) Right-click on your domain name, <ldap_host>.

(27) Click 'Raise Domain Functional Level'.

(28) Select 'Windows Server 2003' in the drop down box.

(29) Click 'Raise'.

(30) Click 'OK' to the warning.

(31) Click 'OK' to continue.

(32) Right-click on 'Active Directory Domains and Trusts'.

(33) Click 'Raise Forest Functional Level'.

(34) Select 'Windows Server 2003' in the drop down box (if it is not already selected).

(35) Click 'Raise'.

(36) Click 'OK' to the warning.

(37) Click 'OK' to continue.

(38) There is no need to index the attributes as they have all been indexed through the LDIF definitions.