You will be able to find into the logs files(historical logs):
kern.log : Contains dump from Kernel while interacting with hardware while booting UP
messages: Provide information related to internal process interaction and file access process. It uses syslog-ng
eventlog\Main.log: Process monitoring, typical you should look here if the system boots.
eventlog\all.log : Contain all log, which include information from all different file into single file.
I think it will be really useful if you check those logs and try to find for error messages and make sure it is the same time the C40 reboot suddently.
If you can not find any useful information, you always have the option to open a TAC case to analyze those logs for you, but how i mentioned before make sure the historical log include the date and the time the issue occurred
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...