04-10-2009 07:47 AM - edited 03-15-2019 05:25 PM
I've had this problem for some time now -- the Cisco Messaging Interface service keeps dying and flooding my RTMT logs with CriticalServiceDown messages. I don't use the service (from what I have read it is used to connect to 3rd party voicemail systems and I don't use any 3rd party voicemail systems). I have tried to disable the service via the web interface, but it always fails with a general database error.
Is there a way to disable the service via CLI so I can stop the flooding of my logs with bogus messages?
Thanks,
Chris
04-10-2009 03:44 PM
you can only stop, start or restart services from the CLI.
HTH
java
if this helps, please rate
04-10-2009 10:17 PM
utils service stop Cisco Messaging Interface
05-22-2009 05:09 AM
This command return this message:
Invalid service name for start/stop, valid names are:
System SSH
Cluster Manager
Service Manager
A Cisco DB
Cisco Tomcat
Cisco Database Layer Monitor
Cisco CallManager Serviceability
I still have the same issue. Any help?
Tnx
05-22-2009 05:20 AM
you can first try command
"utils service list"
This will give you the list of services and their status
Then you can give the command
"utils service stop
remember the service name has to exactly the same. Best bet is to copy service name and give the command
05-22-2009 05:28 AM
You should do it from "Cisco Unified Serviceabilty" web page.
Go to Tools > Service Activation. Deactivate "Cisco Messaging Interface" service.
Thanks!
Michael
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide