You are viewing an old version of this page. View the current version.
Compare with Current ·
View Page History
If noteworthy events occur during the running of the program, or as a result of user action, depending on the your desired level of detail, these can be sent as Alerts to an administrator or other system operator by e-mail, logged to a file, and displayed in the alerts window on the Alerts Screen.
The screen consists of three portions:
| Panel | Description |
|---|---|
| Log Window | Where any noteworthy event is logged, along with the date and time it occurred and an icon illustrating the severity of the event. |
| Alert Setup | Where the user defines the action to be taken in the case of each type of event. |
| Inactivity Timer | Where the user may stop the Inactivity Timer Alarm if it is currently sounding. |
To set-up each type of alert, select the alert type from the drop-down list - choose from Level 1, Level 2 or Level 3, Level 1 alerts being the most critical. You can then specify a filename to which any event of that level will be recorded. You may also choose an e-mail address to receive notification of such an alert.
Different levels of alerts can have different log filenames and be sent to different e-mail addresses.
When amending the filename or e-mail address for a particular alert, remember to press the Save button to save your changes. Your changes become effective immediately.
The levels of alert are defined as Urgent/Critical, Warnings, and Information, and the events that cause them are described below:
The system couldn’t locate a particular configuration file.
PBX data was received from an unknown source. This could indicate a malicious attempt to falsify data.
Any error during the mathematical processing of call data.
A voluntary system shutdown occurred because an important file could not be accessed due to another process having it already open.
A PBX data template could not be located or is missing.
Any error during file access in processing PBX data.
Any error during the batch pre-process cycle.
Any error accessing the call database.
An invalid or missing tariff table.
Some discarded call data could not be saved for future inspection.
Any non-recoverable general reporting error but not including normal feedback from the reporting engine.
Any error associated with sending an e-mail.
Any error raised whilst administering scheduled reports.
Unauthorised access on the TCP data or web server ports.
Any other web server type error which could indicate a malicious attack using the HTTP protocol.
Any error when generating on-the-fly images such as those used in creating charts for reports.
Problems during the automatic archiving of historical call data.
Any occasion where the complete contents of the call database were removed.
Inactivity timer alerts
 | WARNING: Problems decoding specific PBX data where the format subscribes to a published protocol. |
 | INFO: Web page accesses including the IP address of the client requesting the page. |