Home WTI User's Guides
cover
1. Introduction
2. Unit Description
2.1. Front Panel Indicators
2.2. Back Panel
3. Hardware Installation
3.1.1. AC Powered Units
3.1.2. DC Powered Units
3.2. Set-Up Switches
3.2.1. Default Baud Rate for Console Port
3.2.2. Default Baud Rate for PBX Port A PBX Port B and AUX Port
3.2.3. Dialback Security Mode
3.2.4. Console Port Password
3.2.5. Power Up Default
3.3. Reset to Defaults
3.4.1. PBX Inputs A and B and AUX Port
3.4.2. Modem Port
3.4.3. Console Port
3.4.4. Network Port
4. Configuration
4.1. Access to the Command Mode
4.2. Menu System Conventions
4.2.1. Script Access to Menu Functions
4.3. Set System Parameters
4.4. Port Configuration
4.4.1. PBX Port A and PBX Port B
4.4.2. Auxiliary Port Configuration
4.4.3. Console Port Configuration
4.4.4. Modem Port Configuration
4.4.4.1. Dialback Security
4.4.5. Network Port Configuration
5. Menu System Description
5.1. Software Tree
6. Status Screens
6.1. Buffer Status Screen
6.2. File List Screen
6.3. System Status Screen
6.4. Scheduled Action Status Screens
6.5. Dialback Security Status Screen
6.6. Data Filters Alarms Status Screen
6.7. Alarm Condition Status Screen
6.8. Alarm Filter Clue Status Screens
6.10. 80 Full Alarm Status Screen
6.11. Input Contact Alarm Status Screen
6.12. Reason for Action Screen
6.13. PBX Port Status Screens
6.14. Auxiliary Port Status Screen
6.15. Console Port Status Screen
6.16. Modem Port Status Screen
6.17. Network Port Status Screen
6.18. Network Status Screen
7. The Data Filters
7.1. The Data Filter Configuration Menus
7.2. Defining the Data Filter Format
7.3. Defining Data Filter Clues
7.4. Logical and Relational Operators
7.4.1. Logical AND-OR Conditions
7.4.1.1. Logical AND Conditions
7.4.1.2. Logical OR Conditions
7.4.2. The Contains String Operator
7.5. Real Time Variables
7.6. Assigning the Data Filter to a Port
7.6. Assigning the Data Filter to a Port
8. The Alarm Filters
8.1. Common Types of Suspect Phone Activity
8.2. The Alarm Configuration Menu
8.2.1. Default Alarm Filter Actions
8.3. The Alarm Filter Configuration Menus
8.4. Defining the Alarm Filter Format
8.5. Defining the Alarm Filter Clues
8.5.1. Alarm Clue Definition
8.5.2. Editing and Deleting Clues
8.6. Logical and Relational Operators
8.6.1. Logical AND-OR Conditions
8.6.1.1. Logical AND Conditions
8.6.1.2. Logical OR Conditions
8.6.2. The Contains String Operator
8.7. Real Time Variables
8.8. Assigning the Alarm Filter to a Port
8.9. Match Parameter Definition Examples
9. PBX Inactivity Alarms
9.1. Schedules and Timers
9.2. Enabling the PBX Inactivity Alarm
10. The 80 Full Alarm
11. The Input Contact Alarms
11.1. The Optional IO Monitor
11.2. Configuring the Input Contact Alarm
12. Alarm Actions
12.1. Alarm Actions for Alarm Filter Clues
12.2. Alarm Action Summary
12.2.1. None
12.2.2. Callout
12.2.3. Alphanumeric Page
12.2.4. Numeric Page
12.2.5. SNMP Trap
12.2.6. Output Contact
12.2.7. Console
12.3. The Auto Execute Function
13. Scheduled Actions
14. Saving NetLink Parameters
14.1. Saving Parameters to Flash Memory
14.2. Saving and Restoring Parameters from an ASCII File
14.2.1. Saving Parameters to an ASCII File
14.2.2. Saving Parameters to an ASCII File
14.3. Configuring NetLink with Saved Parameters
15. Buffer Functions
15.1. Memory Partitions and Shared Data
15.1.1. Partitions and Files
15.1.2. Setting the Partition
15.1.3. Releasing the Partition
15.2. Menu Driven Data Release
15.2.1. The Buffer Functions Menu
15.2.2. Read Session Parameters
15.3. Command Driven Data Release
15.3.1. Command B00
15.3.2. The B01 Command Line
15.3.3. Command B01 Examples
15.3.4. Other Commands Used During Data Release
15.4. Retrieving Data Using FTP Push
15.4.2. FTP Push Start Time
15.5. The FTP Server Feature
15.5.1. Configuring the FTP Server Feature
15.5.2. Retrieving Data Using FTP Server
15.5.3. File Names for the FTP Server Function
15.5.5. Response Messages Generated by the FTP Server Function
15.6. The Auto Delete Function
15.7. Zmodem Data Release Mode
16. Other Menu Functions
16.1. System Functions
16.1.1. Security Level
16.1.2. Pass-Through Mode
16.1.3. Monitor Mode
16.1.4. Clear Alarm Condition
16.1.5. Clear Alarm Counters
16.1.6. Download Parameters
16.1.7. Audit Trail
16.1.8. Upload Firmware
16.2. System Diagnostics
16.2.1. Load and Test Memory
16.2.2. Send Test Message
16.2.3. Test Pager
16.2.4. Send Test SNMP Trap
16.3. Default Parameters
17.3. Real Time Mode
17.4. Selective Read
17.5. Multiple Telnet Connections
17.5.1. Conflicts with Other Command Ports
18. Command Reference Guide
18.1. Command Mode Access
18.2. Command Syntax
18.3. Command Help
18.4. Command Summary
A. Specifications
B.2. Console Port
B.2.1. NetLink Console Port
B.2.2. NetLink Console Port
C. Cable Installation
D. Supervisor Functions and User Functions
D.1. Security Mode at Start Up
D.2. Dialback Security
D.3. Supervisor Mode and User Mode Functions
E. Alarm Clue Definition Tips
E.1. Headers Banners and Other Non-Data
E.1.1. The Comparative Operators
E.1.1.1. Limit Comparisons
E.1.1.2. Exclude Non-Data Characteristics
E.1.2. Exact Match with PBX Call Record Format
E.2. Programming Support
F. Customer Service
G. Bxx Command Summary
Index
2.1. Front Panel Indicators
PollCat NetLink

8.2.1. Default Alarm Filter Actions

 

Alarm Action parameters determine how NetLink will react when an alarm is generated. The Default Alarm Filter Actions select parameters that are applied to all newly defined Alarm Clues. This allows the user to assign identical actions to a series of clues without manually entering parameters for each clue.

Notes:

•                      Definition of the Default Alarm Filter Action parameters is optional.

•                      Default Alarm Action parameters are only applied to newly defined clues. These defaults will not be applied to PBX Inactivity Alarms, 80% Full Alarm, or Input Contact Alarm.

•                      When new Alarm Clues are defined, the default values can be altered or eliminated, as discussed in Section 8.5.1.

 

The following Default Alarm Action Parameters are available.

1                     Action: Specifies the default action that will be performed when an alarm is generated. For more information, please refer to Section 12.

2                     Phone Number: The default number that will be dialed when an Alarm Clue generates a callout or page action.

 

Note: For Numeric Paging, this prompt can specify both the Pager phone number and a numeric "message". In this case, the phone number is entered in the following format:

PHONENO@MESSAGENO#

Where PHONENO is the pager number, and MESSAGENO is any user-selected number that will notify the receiver that an alarm has occurred. For example, to dial 555-1212 and send the message "111", the phone number would be defined as "5551212@111#".

10. Pager ID 1: The first default Pager ID number. If alphanumeric pager notification is selected, this is the first pager dialed when an Alarm is triggered. NetLink can dial up to three pagers for each clue.

11. Pager ID 2: The second default Pager ID Number.

12. Pager ID 3: The third default Pager ID Number.

13. SNMP Management: The default SNMP Manager, that will receive SNMP Traps generated by Alarm Clues. IP Addresses for SNMP Managers are defined via the Network Port Configuration Menu, described in Section 4.4.5.

14. Output Contacts: The default open/close action that will be performed when an Output Contact action is generated. "C" indicates the contact will be closed, "O" indicates the contact will be opened, and a dash (-) indicates that the status of the contact will not be changed.

15. Message: Defines the default message sent when the alarm action is Alphanumeric Page, Numeric Page, SNMP Trap or Console.

16. Auto Execute: Sets the default state for the Auto Execute feature. When enabled, NetLink will execute the command string defined under item 17 when a Callout or Console action is generated.

 

17. Execute Commands: The default Auto Execute command string. This command string will be invoked when Auto Execute is enabled, and a Callout or Console Action is generated. The command string consists of a series of ^Bxx commands, which are listed in the Command Help Screen, and Section 18.

Example: To send the Site ID Message and then send all alarm records, the Auto Execute Command String would be defined as "03/01,ALM". Note that the ^B is not included in the command string, and that each command is separated by a slash (/).

on�:Tc8H>� @" lor:windowtext'>

 

 

12. Pager ID 3: (undefined) OUTPUT CONTACTS (IDLE/NO ALARM) 13. SNMP Mgmt: Manager #1

7. Contacts 1/2/3/4: C/C/C/C 14. Output Contacts 1/2/3/4: -/-/-/­

15. Message: (undefined) (Cont.): (Cont.):

16. Auto Execute: Off

17. Execute Cmds: (undefined) (Cont.): (Cont.): (Cont.):

 

Enter Selection, Press <ESC> to return to previous menu ...

Figure 8.1: Alarm Configuration Menu

y:"BD9�A H>� @" 821 BT"; mso-bidi-font-family:"BDDGO A+ Monospac 821 BT";color:#211E1E'>

 

|OUT|19495839514

|05:36|00.75|

|08:20|092|J.SMITH

|OUT|18008547226

|11:15|00.00|

 

-AAAAA------------------------------------------------BBBBB------­

Figure 7.5: Data Filter Example 1

Where: A The field that lists the time the call was received or placed. B The field that lists call duration.

Define a Data Filter that will only store records for calls received or placed between 8:00 am (08:00) and 5:00 pm (17:00), and lasting longer than five (5) minutes. The Data Filter Action would be set at "Store", and Match Parameters would be defined as:

A>08:00&A<17:00&B>05:00

Where: A>08:00 Stores records for calls received or placed after 08:00. & Logical AND A<17:00 Stores records for calls received or placed before 17:00. & Logical AND B>05:00 Stores records for calls that last longer than five minutes.

Example 2: Multiple OR Conditions

This example shows a Data Filter that uses multiple OR conditions to store call records which conform to one of several listed characteristics. Assume the Data Filter Format is defined as shown in Figure 7.6.

 

-------AAA-------------------------------------------------------­

Figure 7.6: Data Filter Example 2

Where A indicates the field that lists the extension number.

Define a Data Filter that will only store records for calls received or placed by extensions 013, 086, 099, or 101. The Data Filter Action would be set at "Store", and Match Parameters would be defined as follows:

A=013+A=086+A=099+A=101

Where: A=013 Stores records for calls received or placed at extension 013.

•                      Logical OR A=086 Stores records for calls received or placed at extension 086.

•                      Logical OR A=099 Stores records for calls received or placed at extension 099.

•                      Logical OR A=101 Stores records for calls received or placed at extension 101.

 

Note: Match Parameters for this Data Filter could also be defined by entering each "A=xxx" expression under a separate clue name.

Example 3: Combining Logical AND Conditions and Logical OR Conditions

This example combines a logical AND condition and a logical OR Condition. Assume the Data Filter Format is defined as shown in Figure 7.7.

 

-AAAAA-BBB-------------------------------------------------------­

Figure 7.7: Data Filter Example 3

Where: A Is the field that lists the time the call was received or placed. B Is the field that lists the extension number.

Given the Data Filter Format shown in Figure 7.7, define a Data Filter that will store records for calls received or placed between 7:00 am

(07:00) and 6:30 pm (18:30). In addition, the Data Filter must also store records for calls received or placed by extension 013. The Data Filter Alarm Action would be set at "Store", and Match Parameters would be defined as follows:

(A>07:00&A<18:30)+B=013

Where: A>07:00 Stores records for calls received or placed after 07:00. & Logical AND A<18:30 Stores records for calls received or placed before 18:30.

+ Logical OR B=013 Stores records for calls received or placed at extension 013.

Note: Parentheses are used to group the two parts of the logical AND condition.

Example 4: The “Wild Card” Operator

This example shows a Data Filter that uses the “Wild Card” operator. Assume the Data Filter Format is defined as shown in Figure 7.8.

Text Box: |08:16|075|B.JOHNSON 	|IN 	| 	|00:55|00.00| 
|08:18|067|R.JONES 	|OUT|19495839514 	|05:36|00.75| 
|08:20|092|J.SMITH 	|OUT|18008547226 	|11:15|00.00|

----------------------------------AAAAAAA------------------------­

Figure 7.8: Data Filter Example 4

Where A represents the first seven characters of the call record field that lists the number dialed.

Assume that you need to only store records for long distance calls. The Data Filter Action would be set at "Store". Since long distance numbers begin with the number 1, Match Parameters would be defined as follows:

A=1-----­

Where: A=1------Stores records for calls dialed to any number that begins with a "1", regardless of the remaining six positions.

Note: Since this Data Filter uses only the first position of the “A” field, the remaining six positions (specified by the Data Filter Format) must also be accounted for. The wild card operator (-) is used to fill out the remaining six positions in the "A" field.