Using the alarm and event logs helps you isolate the source of the problem, usually through the divide and conquer approach which involves:
Segmenting the configuration
Testing equipment/connections
Interpreting the results
Confirming/denying the relevance of the results
Repeating until isolation successfully points to the problem source
Tip:
It is essential that you have a thorough knowledge of the equipment and configuration and have pertinent information at hand to quickly and effectively diagnose and fix problems.
Although careful examination of the alarm/event logs is the key to understanding what the problem is, you probably do not want to look at the entire log for the following reasons:
Too much data -- the cause of the problem is likely contained in a few lines of the log.
Not all relevant -- not within the time frame.
The maintenance subsystem gathers detailed alarm and error information from three major processes:
Communication Manager— the telephony application
Server-based maintenance subsystem applications
Linux server
You can view the Alarm Log through any of the three different interfaces listed in the table.
Interfaces
Interface
Connection
Description
Maintenance Web pages
Network through server’s IP address
Recommended for most maintenance-related functions and information. The report is divided into two main sections:
Main Communication Manager interface from which you can start an:
Filtering event report: logs and explains specific events that occur during call processing. Often, these are not problems that require immediate action, but are informational.
Filtering alarm report: the main source for Communication Manager alarms, which include out-of-range temperature or voltage values, broken or fluctuating connections, defective hardware, etc.
