I have an HA UCCX environment and I recently experienced the subscriber UCCX showing in Partial Service. I drilled down under UCCX Serviceability > Tools > Control Center Network Services and saw that it was the VOIP Monitor Subsystem in out of service state.
I opened a Cisco TAC case and here is the fix.
Per Cisco TAC restarting the service below on SUBSCRIBER ONLY would not affect your environment during business hours.
Go to Command CLI and run the following: (case sensitive)
· utils service stop Cisco Unified CCX Cluster View Daemon
· utils service start Cisco Unified CCX Cluster View Daemon
Restart the following services on Publisher and Subscriber:
· Restart Cisco Desktop Call/Chat Service
· Restart Cisco Desktop License & Resource Manager Service
· Restart Cisco Desktop LDAP Monitor Service
· Restart Cisco Desktop VoIP Monitor Service
I did the Subscriber first and then the Publisher and the Subscriber showed In Service once again.
Do it on secondary (from cli restart Cluster View, restart "Cisco Desktop Call/Chat Service", "Cisco Desktop License & Resource Manager Service", "Cisco Desktop LDAP Monitor Service",
"Restart Cisco Desktop VoIP Monitor Service")
Then on primary. And on step restart "Cisco Desktop LDAP Monitor Service" all servers showed In Service.
Hi, thanks for this information. It was stated to do on both Servers in HA. And stated that doing this to the Subscriber would be non-impacting.
Question: When I restart all the services mentioned on the Publisher - will this impact the call center agents? Will it cause the agents on Finesse to notice or will cause a fail over to the subscriber. I did the Subscriber , just holding off on the Publisher until I know if it will impact the users.
Thanks for your time !
So forget Finesse for a moment, restarting the services mentioned on the Publisher - will this have an impact on the call center (either agents or will it cause a fail over in the HA environment) ? just trying to see if I have to announce to all the agents and do this after hours.
Not sure what causes the Voip Monitor Subsystem to go in partial or oos. I was creating a new script, application, trigger, etc ... that is when I noticed it.
I have created new in the past, just not sure what kicks this into OOS.
Kim, just wanted to thank you , TAC stated that starting these desktop services individually using the CLI would not cause a Failover or disrupt the agents while doing these actions on the Publisher. IF I had done the whole CCX Engine restert, then yes it would naturally Fail over. This did clear up my issue with Voip Monitor Service being in Partial service.