Corporate Directory Requirements
Two requirements exist when discussing the corporate directory and CallManager:Directory accessDirectory integration
Table E-16 helps you to gather these requirements and design your customer's IPT network. After collecting the basic information from Table E-16, if your client's network is going to include directory access, obtain the information requested in Table E-17. For corporate directory integration, obtain the information requested in Table E-18.
No. | Question | Answer |
---|---|---|
1 | If your enterprise has a corporate directory deployed, what type of corporate directory is it? | |
2 | Do you require corporate directory access from IP Phones or integration of CallManager with the corporate directory? | |
3 | Do you have full redundancy for your directory? |
No. | Question | Answer |
---|---|---|
1 | Do you have a server on which to install the Cisco IP Phone Services SDK? | |
2 | What are the configuration details of the IP Phone service server on which the SDK is installed? | OS version:Service pack level:DNS name: |
The Cisco IP Phone Services SDK runs only on a Microsoft Windows 2000 or 2003 platform and uses ASP (Active Server Pages) scripts. If you plan to use any OS other than these, you have to develop your own scripts. | IP Addr.: | |
3 | What URL needs to be configured on the CallManager to provide the directory access to the IP Phones? | URLExample:http://<IP address of IP Phone services server>/ldapsearch/ldapsearch.asp |
This depends on how you have configured the virtual directories on the IIS on the IP Phone service server. | ||
4 | What is the DNS name/IP address of the corporate directory server that IP Phones can access to get the directory list? | DNS name/IP address: |
5 | What is the username and password required to access the directory for lookup? | Username Password |
Example: Cn=diruser, ou=users,dc=Cisco,dc=com | ||
6 | What is the user search base? | User search base: |
Example: ou=users, dc=Cisco,dc=com |
No. | Question | Answer | |
---|---|---|---|
1 | Who are the contacts in your corporate directory team? | Name: Role: Phone: E-mail:Name: Role: Phone: E-mail:Name: Role: Phone: E-mail: | |
2 | How many CallManager clusters exist in your network? | Number of CallManager Clusters: | |
3 | Do all the CallManager clusters run the same version of CallManager, or do they run different versions? If different, list them. | CallManager Versions: | |
4 | Are any other Cisco telephony applications deployed or planned to be deployed in the network? | CCC CER PA CRS Unity | Version: Version: Version: Version: Version: |
5 | Do any other applications currently use your directory? | App. 1: App. 2: App. 3: App. 4: | Details: |
6 | The following type of information needs to be obtained from the directory team for the existing directory architecture. The questions to ask depend on the directory being used. For example, if AD is deployed, you need to ask the following regarding the AD architecture:What is the number of forests?What is the number of domains?Where are domains located?Do you have multiple sites?Do you have multiple name spaces?What are the replication latency times?Do you have users created under multiple OUs or under a single OU? | Attach the architecture diagrams, documents that describe the directory deployment. | |
7 | Does the corporate directory team understand how the CallManager directory integration works? Do they have all the information about schema changes and possible increases in the size of the directory database?If the answer is no, do not proceed. Go back and clear up all the concerns that the directory team has regarding this whole process. | ||
8 | Who has the schema master right to modify the schema on the directory? | Name: Role: Phone: E-mail: | |
9 | Do you want to use the account that has schema master permission for CallManager to use, or do you want to give a separate account with only required permissions? | ||
10 | If you are creating a separate CCMdiruser account, what are the account name, password, and permissions given to this user? | Username (FQDN):Password:Permissions: | |
11 | What is the IP address/DNS name of the schema master, and what is the LDAP port number? | IP Address:LDAP port | |
12 | Where do you want the Cisco directory tree to be created in your directory structure? (This is referred to as the Cisco Configuration DN in CallManager.) | Example:OU=CISCOCCM_DIT,dc=Cisco,dc=com | |
13 | CallManager requires that a few user accounts be created in the directory for its operations. What is the user creation base? | Example:ou=users, dc=Cisco,dc=com |
Directory Access Requirements
Meet with the corporate directory team to obtain the information requested in Table E-17. Directory access refers to when a user presses the Directory button on the IP Phone, the LDAP queries are sent to an external server hosting the Directory Lookup service and then forwarded to the corporate directory server.
Notes/Comments
Directory access is simple compared to directory integration. Refer to Chapter 8, "Implementation," for instructions on implementing directory access on IP Phones using Microsoft Active Directory as the corporate directory.
Directory Integration
Integrating the CallManager with an external corporate directory such as Microsoft AD or Netscape Directory Server stores all the CallManager-related information in the corporate directory rather than in the CallManager default DC directory. Collect the information requested in Table E-18 to understand the requirements of CallManager integration with an existing corporate directory.
Notes/Comments
When you are proposing CallManager directory integration with a corporate directory, you must inform the corporate directory team about the schema changes that will be done on the corporate directory and address all of their questions and concerns before moving forward with directory integration.