1132 Matrix PRASAR UCS System Manual
System Fault Log
What’s this?
The PRASAR UCS maintains a log of all system faults. The system Fault Log has a buffer capacity of 999 records.
The Fault Log stores records using the FIFO method.
The System Fault log can be printed on a local printer or can be saved on a computer in form of a PDF. The report
can be printed or downloaded by the System Administrator in two modes:
• Online: The fault report is printed/downloaded as and when a fault occurs.
• Report (Offline): The faulty report is printed/downloaded whenever desired. In the Report (Offline) mode,
the last 999 faults recorded by the system are printed/downloaded.
The System Administrator can print/download System Fault Log, Online or Report.
Matrix PRASAR UCS supports Syslog Client for System Fault Logs. The Syslog Client enables the system to send
fault logs in syslog format to the remote ‘Syslog Server’. You can view the logs on the remote server.
How it works
• A destination port for sending the report must be selected to which the system can send the log.
• If the System Administrator has an Extended IP Phone, a DSS Key can be assigned for System Fault Log.
• Whenever a fault is detected, the LED of the Fault Log DSS key, if assigned, is turned ON.
• If more than one Extended IP extension is assigned Fault Log DSS Key, the LED of all keys will be turned
ON.
• The System Administrator must acknowledge the Fault indication by pressing the Fault Log key or by
dialing the Fault Log access code. The LED of the Fault Log key is turned OFF.
The different fault events that are logged are summarized in this table:
Event Index Activity Description
1
Octasic Program Download Fail, Mod = y y = VoIP module number
2
Octasic SYNC Failed, Mod = y y = VoIP module number
3
Octasic - Failed to Open Kernel File, Mod = y y = VoIP module number
4
Octasic - Failed to Boot, Mod =y y = VoIP module number
5
Valid MoH File Not Present. MoH will not be
played
6
Octasic X failed. System is in Thermal Sleep
Mode
X= Octasic module number