After restarting some work and ultimately the full machine, RmCm subsystem would not get started on, it actually was jammed in INITIALIZING.
We looked over two trouble shooting guidelines without chance.
Our friend consequently unsealed a TAC case and in the end these people attached the issue. It turned out to be some form of replica concern.
Go into UCCX Publisher
1. Cisco Unified CCX Serviceability – > DataStore regulation Center -> Replication hosts 2. Click immobilize Dvds and HDS 3. push Reset duplication 4. permit CDS and HDS
SIP tracks from CUCM in TranslatorX
Having been troubleshooting a Cisco TelePresence inclusion last night together with to check the remnants to the glass trunk area on the VCS.
Since there’s no SBC in-between to debug SIP on, I’d which will make because of with RTMT. In RTMT there’s a function referred to as routine tracing which can be great. You may also view or download the Callmanager SDI/SDL track records. However browsing the records by using the built in customer or exterior book manager might end up being wearisome at the best.
Luckily Cisco has a semi-official device labeled as TranslatorX. We claim semi as it’s not on the CCO install web page it’s maybe not sustained by TAC. This resource can parse the SDI/SDL tracks from CUCM and existing all of them in a Wireshark track style.
Begin by placing your own CUCM trace degree to illustrated.
1. Serviceability -> Tracing -> Construction
2. locate CM solutions and Cisco Callmanager
3. Preset Debug Track Stage to Complete
Begin RTMT as supervisor and connect with the CUCM bar and grab the record data.
4. tracing & wood Central -> accumulate data -> Identify Cisco Callmanager (all computers)
Continue reading “One of the users received some problems with their unique UCCX 8.0 client node.”