I first attempted to upgrade my Cisco Unified Communications Manager Business Edition version 18.104.22.16800-2 installation to Business Edition 5000 version 22.214.171.12400-1. This refresh upgrade failed and I performed a 126.96.36.19900-2 clean installation and restored from DRS backup. I then was able to successfully upgrade to 188.8.131.5200-1. However, when verifying DRS in the new version I noticed that the naming convention prefix of CCM had changed to UCM, and several previous DRS components were not available.
The following components are currently registered with my 184.108.40.20600-1 Disaster Recovery System:
The previous 220.127.116.1100-2 DRS components that are no longer available or registered under 18.104.22.16800-1 are as follows:
I assume these missing component names should start with UCM under the new version, but they are missing altogether. How can I make these components available under version 22.214.171.12400-1 so that I am backing up my environment fully?
I was able to force the missing DRS components to register by logging into Cisco Unified Serviceability, choosing Service Activation, then manually deactivating and reactivating the following services:
Cisco Extended Functions (for UCM_CEF) Cisco Tftp (for UCM_TFTP) Cisco Bulk Provisioning Service (for UCM_BAT) Cisco Serviceability Reporter (for UCM_REPORTER) Cisco IP Voice Media Streaming App (for UCM_MOH I believe)
One of those service reactivations also registered the missing UCM_ANN component to DRS, but I am not sure which service it was.
There are cases/situations where we have to configure custome CPTONE to resolve FXO disconnect issue. Following are situations which can arise due to FXO disconnect issue:
Phone A calls Phone B, Phone B does not answer. Phone A then goes on-hook but Phon...
Cisco announced major enhancements today to Webex Contact Center. Learn more about the highlights including
better support for the needs of large contact centers worldwide
improvements in the agent and cust...
SymptomsI’m doing a factory reset on the mobile board and it’s giving me the same issues that I wasn’t able to also send over last time. It says that it can’t connect to the server because of a firewall (we don’t have one) and then sometimes it...