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

9.1. Schedules and Timers

 

In order to allow NetLink to differentiate between periods when less PBX activity is expected (e.g. lunch hour), and periods where a lack of activity could indicate a problem, each PBX Inactivity Alarm has two weekday schedules and two weekend schedules.

During any business day, there are periods when one can expect a lower level of PBX traffic. For example, the PBX may receive about one call every five minutes for the majority of the day, and then drop to one call every 30 minutes during lunch hour. Likewise, on weekends the number of calls may also decline.

Two separate weekday schedules allow you to specify slow and heavy PBX activity periods during the work week; the two weekend schedules allow you to define slow and heavy periods on weekends. In both cases, Schedule 1 is assigned to the busy period, and Schedule 2 is assigned to the slow period. Note that Schedule 2 has priority over Schedule 1, and timer schedules are often defined to overlap.

In order to prevent NetLink from generating PBX Inactivity Alarms on holidays, up to 20 user defined holidays (exclusions) can be defined. This allows the alarm to be suppressed on holidays, or on any other day when you expect low PBX activity.

Example: If you receive one call every five minutes from 8:00 am to

5:00 pm, Timer One would be set for five minutes and Schedule One would be defined as 08:00 to 17:00. In order to compensate for a drop in activity to one call every 30 minutes during lunch, Timer Two would be set for 30 minutes and Schedule Two would be defined as 12:00 to 13:00.

r:wz we؏ (9 style='mso-list:Ignore'>•          Weekday Alarm

 

•          Weekday Schedule/Timer 1 (For Busy Periods)

•          Weekday Schedule/Timer 2 (For Slow Periods)

•          Weekend Alarm

•          Weekend Schedule/Timer 1 (For Busy Periods)

•          Weekend Schedule/Timer 2 (For Slow Periods)

•                      • PBX Inactivity Alarm 2

•          Weekday Alarm

•          Weekday Schedule/Timer 1 (For Busy Periods)

•          Weekday Schedule/Timer 2 (For Slow Periods)

•          Weekend Alarm

•          Weekend Schedule/Timer 1 (For Busy Periods)

•          Weekend Schedule/Timer 2 (For Slow Periods)

 

='AX-i�Y' �3' font-family:"BACIO N+ Times New Roman","serif"; mso-bidi-font-family:"BACIO N+ Times New Roman"'>cannot be recovered.