Home WTI User's Guides
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 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 Logical AND Conditions 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 Logical AND Conditions 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
2.1. Front Panel Indicators
PollCat NetLink

13. Scheduled Actions


Scheduled Actions are generally used to retrieve data from the NetLink according to a user-defined time table. Typically, the NetLink will contact your PC at the scheduled time and day, and then automatically download collected data.

In addition to its data collection function, the Scheduled Action feature can also be used to perform other tasks, such as Wellness Checks, Contact Switch operations, and etc. NetLink allows a great deal of flexibility in configuration of the Scheduled Action feature. The unit can perform any of the following actions according to the user-defined schedule:

•                      Callout: NetLink will contact a remote PC via modem, and execute a series of user-defined commands. Although these commands are usually employed to download data, they can also report memory conditions, alarm status, and etc.

•                      Page: NetLink will dial an alphanumeric pager and send a user-defined message. This allows NetLink to perform a wellness check, or inform system managers that the unit is operating properly.

•                      SNMP Trap: NetLink will send an SNMP Trap to a network manager. This option can also be used to perform a wellness check, or notify personnel that it is time to check the unit.

•                      Console Port: NetLink will contact the device connected to its Console Port in order to download data or report status.

•                      Output Contact: (Optional) NetLink will open or close the optional Output Contact switches.


Each of the two available schedules allow up to seven scheduled actions per week. This provides a total of fourteen events per week. For more information on these actions, please refer to Section 12.



1. Schdl Action: Off 11. Action: None

2. Sunday: Off 12. Phone #: (undefined)

3. Monday: Off (Cont.):

4. Tuesday: Off 13. Pager ID 1: (undefined)

5. Wednesday: Off 14. Pager ID 2: (undefined)

6. Thursday: Off 15. Pager ID 3: (undefined)

7. Friday: Off 16. SNMP Mgmt: Manager #1

8. Saturday: Off 17. Output Contacts

1/2/3/4: -/-/-/­EXCLUSION (MM/DD) 18. Message: (undefined) --/----/----/----/--(Cont.): --/----/----/----/--(Cont.): --/----/----/----/--19. Auto Execute: Off --/----/----/----/--20. Execute Cmds: (undefined) --/----/----/----/--(Cont.):

9. Add Exclusion (Cont.):

10. Delete Exclusion (Cont.):


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

Figure 13.1: Scheduled Action Configuration Menu (Schedule 1 Shown)

To access the Scheduled Action configuration menus from the Main Menu, type 24 and press [Enter], a selection menu will be displayed. Next, type 1 for Schedule 1, or 2 for Schedule 2, and press [Enter]. Both configuration menus include the following:


1. Scheduled Action: Enables/disables the Scheduled Action function. Note that in addition to enabling the schedule, the user must also define the schedule and specify the action that will be performed according to schedule.

2-8. Daily Schedules: Defines the time that the action will be performed on each day of the week. Time values are entered in 24-hour (Military) format.


9. Add Exclusion: Defines dates (such as holidays) when the Scheduled Action will not be performed. As each exclusion is defined, it will be added to the display above item 9.

10. Delete Exclusion: Deletes a date from the exclusion list.


Action Parameters:

11. Action: Defines the type of event that will occur according to the schedule. The user may select None, Callout, Alphanumeric Page, Numeric Page, SNMP Trap, Output Contact, or Console.

12. Phone #: Defines the phone number that will be dialed for a scheduled Callout or Page. This is the number for your remote modem or pager service.


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


Where PHONENO is the pager number, and MESSAGENO is any number which will notify the user that a scheduled page has occurred. For example, to dial 555-1212 and send the message "999", the phone number would be defined as "5551212@999#".

13. Pager ID 1: The first Pager ID Number used when a scheduled alphanumeric page is performed. NetLink will dial up to three pagers for each schedule.

14. Pager ID 2: The second Pager ID for this schedule.

15. Pager ID 3: The third Pager ID for this schedule.

16. SNMP Mgmt: The SNMP Manager(s) that will receive SNMP Traps generated by this schedule. This prompt can select Manager 1, Manager 2, or both. Note that IP addresses for each SNMP Manager are defined via the Network Port Configuration menu.

17. Output Contacts: (Optional) When an Output Contact action is scheduled, this prompt selects the Open/Close operation for the optional Output Contacts. An "O" indicates that the corresponding contact will be opened as scheduled, a "C" indicates the contact will be closed, a dash (-) indicates that the status of the contact will not be changed.



18. Message: Defines the message that will be sent for a Scheduled Callout, Alphanumeric Page, SNMP Trap, or Console Action.

19. Auto Execute: When this item is enabled, NetLink can be scheduled to automatically execute the command string defined under item 20.

20. Execute Commands: The Auto-Execute command string. This command string consists of a series of NetLink ^Bxx commands, with each command separated by a backslash character and a forward slash character (e.g. \/04\/01). ^Bxx commands are described in Section 18. For more information on Auto-Execute command strings, please refer to Section 12.3.


When the Schedule Action feature is used to download data or send a wellness message, the Auto Execute string must be defined in order to specify the exact task to be performed. For example, to instruct the NetLink to automatically send the Site ID message and then send all alarm records, the Auto Execute string would be defined as "\/03\/01,ALM".


•                      When the Auto-Execute string is defined, commands are entered without the ^B character, and each individual command is separated by a slash character.

•                      In order for the Auto Execute feature to function, item 19 must be enabled, the command string must be defined, and item 11 (Action) must be set to perform a Callout or Console action.


tm2�p\H>� @" mage002.png" align=left hspace=12 alt="Text Box: |19:18|067|R.JONES |OUT|12145551234 |25:36|04.75| |19:20|092|J.SMITH |OUT|18008547226 |01:07|00.00| |21:21|002|R.JONES |OUT|12135551212 |30:15|05.75| " v:shapes="_x0000_s1027">



Figure 8.8: Alarm Filter Format; Match Parameters Example 2

Where: A is the time the call was received or placed. D is the first seven digits of the number dialed.

Match Parameters for this Alarm Clue would be defined as follows:





Example 3: Lengthy International Calls

This clue requires that you are familiar with the average duration of international calls placed in the course of a normal day. For example, if your average international call lasts about 10 minutes, and you are suddenly billed for a two hour call, this could indicate phone abuse.

For this example, assume that the Alarm Filter Format is defined as shown below. Note that the first three lines in Figure 8.9 are sample call records, and the fourth line is the Alarm Filter Format. The variables A, B, and C are not used for this clue.



Figure 8.9: Alarm Filter Format; Match Parameters Example 3

Where: D is the field that lists the first seven digits of the number dialed. E is the field that lists the call duration.

Match Parameters for this Alarm Clue would be defined as follows:



D=011----Counts calls where the first three digits of the number dialed are "011". The remaining 4 digits are entered as wild card characters (-).

* is the logical AND operator. E>=20:00 Counts calls that last 20 minutes or longer.

Example 4: The "Contains String" Operator ($)

This clue provides an example of how the "Contains String" operator ($) can search a field for a specific text string, without regard for the string's position within the field. This is useful in cases where the call record includes a field with right justified numbers (e.g. the number dialed).

For this example, assume that the Alarm Filter Format is defined as shown below. Note that the first three lines in Figure 8.10 are sample call records, and the fourth line is the Alarm Filter Format.



Figure 8.10: Alarm Filter Format; Match Parameters Example 4

Where A is the field that lists the number dialed.

In this example, the PBX also records digits entered after the call has connected. This is often seen in cases where the caller is prompted to press numbers in order to access a specific department or extension. In the third line of the example, the digits "11#2" represent digits entered after the call was connected.

Match Parameters for this Alarm Clue would be defined as follows:


Where A$1900 tells NetLink to count calls that have the string "1900" anywhere in the "A" field. When the "$" operator is used, wild card characters are not used to fill the remaining digits.

Note: When the "Contains String" operator is used, the clue may also count call records that do not fit the intended purpose of the clue. For example, the clue in this example would also count calls to any number that contains the string "1900", such as "555-1900".