Call Manager 5.1 critical services?

Unanswered Question
Aug 14th, 2008

We are configuring our alert system to notify us when our servers are still up but the actual services have stopped. Can anyone help us with which of the actual services in call manager 5.1 will affect function for the end users even thought the server is still up and running? Our CM 5.1 is linex based.

Any feedback would be great.

Thank you.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Jaime Valencia Thu, 08/14/2008 - 10:39

i would say

A Cisco DB

A Cisco DB replicator


CallManager Admin

CallManager Serviceability

CallManager Serviceability RTMT

Database Layer Monitor

License Manager




Other services might also be important but it depends on what you're using.

If JTAPI apps then add the CTIManager, if using media resources then add IP Voice Media Streaming, etc



if this helps, please rate

victoriabardy Thu, 08/14/2008 - 11:26

Thank you for your response. We are looking for what specifically would kill call manager services. We located the actual services on Unity but that is windows based and a little more straight forward. Do you know what the Call Manager services start/stop ties out to in Linux? That is the string that we would tie out to the monitor.

Any idea? Please let me know.

And thank you again.

Jaime Valencia Thu, 08/14/2008 - 13:09

callmanager service can be stopped independently of other services. also you if any of the DB services go down any kind of change in the admin or CFA, EM, etc won't work so i would look at DB services also



if this helps, please rate

Hi Java,

I work with Vicky. Do you know what the name of the processes are? It's my understanding that the CLI is not the linux root. For example, I should be able to use "ps aux | grep callmanager". We need the process names to monitor the appropriate services using our Network Monitor. SNMP is already configured. Thanks!


Jaime Valencia Tue, 08/19/2008 - 11:33

sorry, i don't know the names of the actual processes. as you mention what you get is a secure CLI on which most linux commands won't work. you would need to get root access to find out the real names of the processes, but TAC only provides root access to apply workarounds for bugs or to perform troubleshooting



if this helps, please rate


This Discussion