Optivity Telephony Manager: System Administration - BT Business

616 Alarm management
Rules
Rules allow you to define actions that may be applied to a given event. Rules may only
be defined in scripts. By default, rules are examined in a top-down manner. You may
use an infer statement to explicitly specify the order in which rules are examined.
A rule consists of an if statement containing a logical expression, followed by an
instruction. A rule may also include an else statement, which is only executed if the
logical expression in the if statement is false. Within a rule, a send statement or a
function may be called. New variables may not be defined within the scope of a rule.
Example:
rule check_Meridian1_critical {
if($CurrentTrapDevice="Meridian1" and
$NormalizedSeverity=Critical) {
// print event to console
send( con,
"--> Critical Meridian1 alarm received! ",
$ErrorCode," - " , // M1 error code
$CurrentPCTime, " - ", // Time that PC
received the alarm
$CurrentTrapSource," - " , // Name of this M1
$DeviceTime," - " , // Timestamp from M1
$Text," - ", // Text with error
message
$OperatorData // More text with error
message
);
}
else{
// append event to log file
send(sample_file,"--> Critical alarm received! ",
$ErrorCode," - " , // Error code
$CurrentPCTime, " - ", // Time that PC
received the alarm
$CurrentTrapSource," - " , // Name of this device
$DeviceTime," - " , // Timestamp
$Text," - ", // Text with error
message
$OperatorData // More text with error
message
);
}
}
The preceding script defines the rule check_Meridian1_critical, which sends critical
Meridian 1 alarms to the console and appends other events to the log file sample_file.
553-3001-330 Standard 3.00 August 2005