I recently upgraded our CUC cluster from 126.96.36.19900-5 to 188.8.131.5200-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.
Contact Center users dial out/call customers from their computers via a desktop based application like Cisco Finesse Agent / CAD (Cisco Agent Desktop) application or any other 3rd party application.As per organizational process the requirement is ...
i want share with you my setup, how i configure TMS 15.6.0 with SQL 2012:
-first of all this deployment design in LAB just for practice, my deployment contain SQL and TMS in same server if you need to install TMS in another server yo...