Connection Conversation Manager service in Cisco Unity Serviceability

Unanswered Question


When doing some configuration changes , the administrator is asked to :

"Restart the Connection Conversation Manager service in Cisco Unity Serviceability for these changes to take effect". However, we can't find this service in the control center !!!

anu suggestions? I just restarted the whole UC server and it worked.

best regards,

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Jaime Valencia Wed, 02/25/2009 - 17:42

if this is a CUCMBE u did looked in the CUC serviceability and not in CUCM serviceability... right??????

the service is just sitting there in CUC:

Control Center - Feature Services ->

Connection Conversation Manager

pretty hard to miss



if this helps, please rate

Nordyne01 Wed, 10/28/2015 - 06:34

I had the same problem at first.  You need to make sure that you are under the Cisco Unity Connection Serviceability instead of just Cisco Unified Servicibility in order to restart this service.

nibin_joseph Tue, 04/26/2016 - 12:04

I had an issue reported by the users organisation wide that they are not able to access voicemail and send voicemail.

The fix was: restarted 2 services "Connection Conversation Manager" & "Connection Mixer". Once these services are restarted, wait for a couple of minutes and check the functionality of the voicemail by sending and accessing the same.

You can find both these services in :

Cisco Unity Connection Web Page(Version >  Cisco Unity Connection Serviceability > Tools > Service Management > Critical Services.

Note: Restart(Stop & Start) the services one after the other (Wait for the fisrt one to come up and go for the next service)

jzangmeister Fri, 04/29/2016 - 10:50

We had a similar issue and it seems to reoccur after connection conversation manager has been running for a long period of time.  This latest occurrence was after the connection manager service was up for 2301 hours.  Access to voicemail is sporadic when the issue occurs in our environment.  Most of the time users can access voicemail, but every so often a user cannot.  Restarting the connection conversation manager service on each server resolves the problem.  FWIW, we're running CUC and CUCM version 10.5(2)SU2 which I thought was a version that resolved this bug.


This Discussion