This is the service reading the trace settings from the registry, which usually happens at startup. If it is occurring over and over, it could be a bug with CCM services or any SR updates you have recently done. Check the following:
1) Check to see if your tracing on your CallManager service is set to Detail on any components and put it back to Default by clicking SetDefault
2) Check all of your servers (just in case) to verify that they are all on the SAME OS versions, SRs, etc (I know this one is a no-brainer, but it doesn't hurt to be sure)
3) Stop and start CallManager service across the cluster or reboot the CCM cluster
4) Roll it back to the last backup BEFORE any recent SR updates or patches and reboot the cluster
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...
You have reached the Cisco Logistics Support Center.. To Check Status of your RMA, visit Product Returns & Replacements (RMA).
Need help? Contact us by Phone or Email.
Phone: 1800 553 2447 Option 4