When attempting to upgrade Cisco CallManager from version 3.2 to 3.3, the upgrade fails stating that the SQL server does not have the proper patches / service packs installed. However, the SQL server is patched as per the Cisco CallManager installation documentation.
This particular environment had three Cisco CallManagers, one publisher, and two subscribers.
One of the mirrored hard drives, from a subscriber, was pulled out and placed into a spare MCS7835, and the upgrade attempt commenced. Aside from the mirrored hard drives, all upgrades must start with the publisher, since it contains the master database.
Hello everyone,We are upgrading our CUCM cluster to version 11.6 and would need to replace about 10000 phones. The phone replacement is going to happen before the upgrade of CUCM. We have more than 20 phone services configured in our CUCM cluster. Each ph...
I have IMP 11.5 in my organisation. We want to Lunach Jabber but the management is insiting of having a two factor authentication in place before we launch it. Is there any possibility of having it? Thanking for your response. regard...
I have followed the installation guide(QM all in one solution) . I have Windows Server 2012 R2 with SQL Server 2014. When I run the setup_MonRec_1151, I get "Windows cannot find 'bin\7za.exe'. Make sure you typed the name correctly, and then try again." e...