Copy & paste the reason code in a scientific calculator:

-1932787617

then transform the number to Hexadecimal you will get FFFFFFFF8CCC005F, just take the second part: 8CCC005F and take a look to the attached document, and you can see this:

const unsigned long int CTIERR_DIRECTORY_LOGIN_NOT_ALLOWED= 0x8CCC005F

So again the problem is that the CCMSysUser is not authenticating.

//J

Haack,

1) Delete users (CCMSysUser / CCMAdministrator / IPMASysUser) with (OU=CISCO) in AD.

2) Creating the Schema Update Allowed Registry for AD 2003:

2a) Make sure that the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters\Schema Update

Allowed is set on the Microsoft Active Directory server to 1. This allows write access to the schema on that server.

3) run plugin (Cisco Unified CallManager Customer Directory Plugin) no CCM > Application > Install Plugins.

4) Integration password:

4a) Publisher database server, choose Start > Run and enter cmd

4b) Enter the command, CCMPWDChanger.

4c) In the Administrator Password field, enter the password of the user that was created to enable

Cisco CallManager to access the directory and next.

4d) The Cisco CallManager Password Changer window displays. The User ID drop-down list box provides

the following options: Directory Manager, CCMAdministrator, CCMSysUser, and IPMASysUser.

4e) You must change the passwords for the CCMAdministrator, CCMSysUser, and IPMASysUser accounts.

4f) In the New Password field, enter the new password.

4g) In the Confirm New Password field, enter the password again.

5) open htts://CCM/manager/list and stop the services.

6) open https://CCM/CCMService/main.asp go tools > Control Center > Servers > Stop the services (Cisco CTIManager/Cisco TFTP/Cisco Extension Mobility).

7) Boot the Server.

Good Luck!

Rafael Cardoso.