I recently upgraded our CUC cluster from 18.104.22.16800-5 to 22.214.171.12400-14. Upgrade went fine and everything appears to be working. However, on my Publisher, the Connection Serviceability feature service is active but stopped. I've rebooted the Pub, still stopped. I've tried starting the service through CLI with utils service start Connection Serviceability, command failed. Service is running fine on Sub and I can access the cuservice page on both the Pub and Sub. Under cluster management, Pub is running as Primary and Sub as secondary. Anyone ever run into this? Should it be this way? If not, thoughts on resolving?
Also, Connection Administration was the same way after upgrade and reboot, but was able to start by simply clicking on the Start button. Haven't rebooted server since I manually started this service to see if it automatically starts.
Today, Cisco announced new advances for meetings. A couple of insights:
1. Scheduling meetings is even easier
2. New video devices
3. New headsets
Click here to learn more about these exciting advances in Cisco meeting technolog...
How does the phone registered in CUCM environment?
-The phone will obtains power via PoE or AC adapter.-The phone will loads its locally stored firmware image.-The phone learns the voice vlan id via cdp from the switch.-Via...
To participate in this event, please use the button to ask your questions
This topic is a chance to discuss more about the concepts, best deployment practices and troubleshooting tips for Webex Hybrid services. Ask qu...