There are some problems installing Cisco CallManager 3.3(2) on a Subscriber machine. The Publisher has been upgraded to 3.3.2, then 3.3.3. This cluster uses the Netscape Directory plug-in. The fix for CSCdv02653 is applied, but that fix did not produce any results.
This issue is documented in the following Cisco Bug ID:CSCeb52723
To resolve this issue, follow these steps:
On the Publisher, verify that the HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\Directory Configuration\ DCDMGRPW registry key has a value of 0c0a000a2c101c1a100354615c. If it does not, open a DOS command prompt and type PasswordUtils ciscocisco123 to generate an encrypted password for ciscocisco123. The encrypted password will be 0c0a000a2c101c1a100354615c.
Paste it into the HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\Directory Configuration\DCDMGRPW registry key. The Subscriber installation displays this error:
?Directory Install Failed? CCM subscriber Upgrade from 3.2(x) [Integrated with AD/Netscape] to 3.3(2) Append following to CLASSPATH environment variable C:\WINNT\java\lib\jtracing.jar;C:\WINNT\java\lib\ldapbp.jar;C:\WINNT\Java\Lib\D irUser.jar; C:\WINNT\Java\Lib\DirUserNotification.jar;
Reboot the system after setting the CLASSPATH.
This is required so that applications using DirUser.jar/DirUserNotification.jar can pick up the modified CLASSPATH. Frequently, the LMHOSTS files need to be recreated on the Subscriber and Publisher. Once this is done, the installation on the Subscriber is attempted again and is successful. If the LMHOSTS file does not use the same file that is given as a sample, create a new one.
Refer to the remote registry to get the Publisher's IntegratedInstall version, which is 126.96.36.199. The Subscriber's install version is different from Publisher's. Installation is aborted or cancelled.
Change the value of IntegratedInstallVersion on the Publisher registry HKEY_LOCAL_MACHINE\Cisco Systems, Inc.\Directory Configuration to 188.8.131.52. Note: Make note of the existing value before changing it to 184.108.40.206. Set the value the same as the version being installed on the Subscriber. If 3.3(2) is installed on the Subscriber, the IntegratedInstallVersion packaged with 3.3(2) is 220.127.116.11. Verify this with any 3.3(2) server. This enables Cisco CallManager 3.3.2 to be installed on the Subscriber, as far as directory installation is concerned.
Once the Subscriber installation is complete, reset the IntegratedInstallVersion on the Publisher to the original value and upgrade the subscriber to 3.3(3).
For more information, refer the related Cisco Bug CSCec19444.
I've got CVI setup so my CUCM registered Room Kits, et al can join MS-Teams meetings. OBTP Join works a treat. The problem I've discovered is that this only works for meetings that were created after CVI was enabled. For meetings that were created be...
I've followed the configuration at https://www.cisco.com/c/dam/en/us/solutions/collateral/enterprise/interoperability-portal/direct-routing-with-cube.pdf to configure my CUBE (an ISR 4331 running IOS-XE 17.3(3) ) to connect to MS-Teams with Direct Routing...
Dear, I hope you are well.In this case I am writing to you to see if you can help me or guide me in a configuration that I have to do in connection with cisco unity. I have to set up a very simple automatic wizard but I can't find the correct option or ho...
I have received several trouble tickets in the past 2 week with basically TWO different problems:1. When creating a new Session in CANVAS with the Education Connector, faculty is getting "We are having trouble communicating with Webex at this time"and2. I...
Good afternoon, all!I'm retiring a server that, among other things, is the SFTP target for my customer's UCM Disaster Recovery System. This is a Debian 10 server with ProFTPD as the SFTP server. I can access this using WinSCP as a client and use any of th...