When an attempt is made to create a Resource Manager (RM) Java
Telephony Application Programming Interface (JTAPI) provider from the Cisco
Customer Response Solutions (CRS) Appadmin page, the attempt fails with either
one of these error messages:
This issue occurs when you integrate Cisco CRS with Active Directory
Cisco recommends that you have knowledge of these topics:
The information in this document is based on these software and
The information in this document was created from the devices in a
specific lab environment. All of the devices used in this document started with
a cleared (default) configuration. If your network is live, make sure that you
understand the potential impact of any command.
Technical Tips Conventions for more information on document
The issue of being unable to add the RM JTAPI provider when you use
Active Directory integration can occur in these scenarios:
When you create the RM JTAPI provider on a CRS 4.x
When you configure the RM JTAPI provider on a CRS 4.x fresh install
While you perform the LDAP Migration step during the restore process,
when you migrate from a CRS 3.x system to a CRS 4.0 system
If the Cisco CallManager AD plug-in is installed with security
constraints that prevent the AD admin user from having write privileges to the
user Organizational Unit (OU), CRS is not able to create JTAPI/RM JTAPI users
in AD. This causes the configuration of these subsystems to fail. Also, when
you upgrade from CRS 3.x to CRS 4.0, the migration wizard is not able to create
these users in AD. This causes the Restore operation from the Backup and
Restore System (BARS) to fail.
If you integrate CRS with AD, then you need to perform this procedure
in all Cisco CallManager servers that are configured as JTAPI providers in
order to resolve this issue:
Browse to C:\dcdsrvr\config and open the
UMDirectoryConfiguration.ini file in Notepad.
Note: You must open the file in Notepad. If you open the file in
another text editor, the application might corrupt the file.
In the UMDirectoryConfiguration.ini file, locate the
UserDirAccess key and change the value to
From Notepad, choose File >
Save in order to save the file and close the
Choose Start > Run.
Enter regedit and click
\\HKEY_LOCAL_MACHINE\Software\Cisco Systems, Inc.\Directory
Configuration within the registry.
In the right pane, double-click the DirAccess
registry key. Delete the false registry entry and enter
true as the new registry entry.
Complete these steps in order to restart the IIS Admin Service and
its dependent services:
Choose Start > Programs >
Administrative Tools> Services.
Right-click IIS Admin Service and then choose
A dialog box prompts you to restart dependent services. These
services can differ based on your configuration.
Click Yes and restart the dependent