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

15.5.5. Response Messages Generated by the FTP Server Function

 

The FTP Server function will send the following messages in response to commands issued by the FTP client:

Positive Preliminary Reply

150 Opening data connection.

Positive Completion Reply

200 Type set to A. 200 Type set to I. 200 PORT command successful. 200 NOOP command successful. 214 Syntax: ABOR (abort operation) 214 Syntax: DELE <sp> filename 214 Syntax: HELP [<sp> <string>] 214 Syntax: LIST (return file list) 214 Syntax: NOOP (no operation) 214 Syntax: PASS <sp> password 214 Syntax: PORT <sp> h1, h2, h3, h4, p1, p2 214 Syntax: PWD (return current directory) 214 Syntax: QUIT (terminate service) 214 Syntax: RETR <sp> filename 214 Syntax: SYST (get type of OS) 214 Syntax: TYPE <sp> [A | I]

15-26

Positive Completion Reply (Continued)

214 Syntax: USER <sp> username 214 Syntax: XPWD (return current directory) 214 The following commands are currently supported:

 

421 Too many attempts, closing control connection. 425 Can't open data connection. 426 Can't build data connection: Connection refused. 426 Transfer aborted. Data connection closed.

Permanent Negative Completion Reply

500 Invalid 500 Syntax 501 Syntax 502 Unknown 530 Please 530 Already

530 TYPE 550 File

other 550 File 553 File 553 File

is userid/password.

 

logged in. not supported.

unrecognized).

argument). and PASS.

can't be retrieved, partition

port. can't be deleted, partition is doesn't exist. is empty.

set by not set.

:p>H>� @" ass=CM186 style='margin-top:0in;margin-right:0in;margin-bottom:7.35pt; margin-left:26.0pt;line-height:10.55pt'>11. Read Session: Specifies the type(s) of file that will be sent to the FTP server. When PBX data is collected, NetLink sorts records according to the port where the data was received (PBX A, PBX B, or AUX), and the Alarm Filter matched. The "Read Session" item allows you to select data based on these criteria, and determine the starting point by record number. For more information, please refer to Section 15.1. The "Read Session Parameters" submenu includes the following items:

 

a) Source Port: Option 1 allows you to select records based on the NetLink port where they were received. When selected, NetLink will display an additional submenu, which is used to toggle each port On or Off. This item can be used to select one, two or all of the available source ports. (Default = All).

Example: If PBX Port A and the AUX Port are both toggled "On", the FTP Push session will only send data received at PBX Port A or the AUX Port; data received via PBX Port B would not be sent.

15-14

b) Data Type: Allows you to choose records based on the Data Type. When selected, NetLink will display a submenu, which is used to choose one of the following file types. Note that only one file type can be selected at a time. (Default = All).

1                     All: Send all records, both Alarm and Non-Alarm.

2                     Standard (Non-Alarm): Send only records that did not match a clue for Alarm Filter 1 or Alarm Filter 2.

3                     Alarm Filter 1 (All): Send only records that matched any clue defined for Alarm Filter 1.

4                     Alarm Filter 1 (By Clue): Send only records that matched a specific clue defined for Alarm Filter 1.

5                     Alarm Filter 2 (All): Send only records that matched any clue defined for Alarm Filter 2.

6                     Alarm Filter 2 (By Clue): Send only records that matched a specific clue defined for Alarm Filter 2.

7                     All Alarms: Send all records that matched either Alarm Filter 1 or Alarm Filter 2.

 

Notes:

•                      When the "By Clue" options are selected, NetLink will prompt you to enter the clue name. If an invalid clue name is entered, the prompt will be redisplayed.

•                      When Data Type and Source Port are assigned, then the FTP Push function will own this partition while the data transfer is in progress. Other users will not be able to read data from this partition until the FTP Push is complete and the FTP connection is terminated. For example, if FTP Push is set to select Non-Alarm data (Data Type) received via PBX Port B (Source Port), then the Console Port will not be able to read Non-Alarm Data received via PBX Port B until FTP Push is complete and the partition is released.

 

c) Start Record: The starting point for data release. Note that this value can be either positive or negative (Default = 1).

•                      Positive Numbers: If a positive number is entered, the unit will count forward from the beginning of the selected group (Source Port / Data Type). For example, if this value is "15", NetLink will begin with the 15th record in the group.

•                      Negative Numbers: If a negative number is entered, NetLink will count backwards from the end of the records in the selected group. For example if the Start Record is set at "-3", then NetLink will send the last three records in the selected group.

 

 

12. Push Action: Enables / disables the FTP Push operation. After you have selected FTP Push parameters, make certain to set the Push Action to On. The Push Action must be enabled in order for the FTP Push feature to function. (Default = Off).

Note: If the Push Action feature is "Off", the selected FTP Push operation will not be performed.

13. Periodic Push: The amount of time that will elapse between FTP Push operations. This allows you to schedule the FTP Push feature to regularly transfer data to your FTP Server. For example, if the Periodic Push is set at 30 minutes, then every 30 minutes, the NetLink will automatically transfer stored data to your FTP Server. (1 to 9,999 Minutes, Default = 1,440 Minutes / 24 Hours).

 

Notes:

•                      A periodic FTP Push operation will be delayed if targeted files are being accessed by another user at the time scheduled for data transfer. NetLink will delay the periodic push until the partition is released, or the other user exits command mode. If the delay lasts longer than the Xmit Delay period, the periodic push will be canceled.

•                      A periodic push will not be performed if the specified files are empty (no data.)

 

14. Xmit Attempts: The number of times NetLink will attempt to retransmit data if the FTP operation fails. (1 to 99 Attempts, Default = 5 Attempts).

Note: NetLink will not perform additional transmit attempts if the specified file(s) are empty, or if the Server Address, User Name, Password, or Account info have not been supplied.

15. Xmit Delay: The amount of time that will elapse between Transmit Attempts (Xmit Attempts). (1 to 99 Min., Default = 5 Min.)

16. Auto Delete: Enables/Disables the Auto Delete function for FTP Push operations. When enabled, NetLink will delete records from memory after the server acknowledges reception. (Default = Off).

17. Start Time: Specifies an exact start time for the next FTP Push operation as described in Section 15.4.2. (Default = undefined.)

 

Miscellaneous:

21. Force FTP Push: When selected, the unit will immediately perform an FTP Push using parameters entered at items one through

16. If the partition (Source Port / Data Type) owned by the FTP Push feature is empty, NetLink will not attempt to connect to the Server. A Forced FTP Push will not effect the Periodic Push schedule.

15-16

 

22. Test FTP Push: Sends test data in order to determine if FTP Parameters are correctly set. If the Test FTP Push cannot establish a connection with the server, NetLink will display a message that describes the reason the test failed. (e.g. incorrect password).

Note: After you have selected new FTP Push parameters, it is recommended to use the "Test FTP Push" feature to make certain that newly defined parameters will work with your FTP server.

23. Stop FTP Push: Terminates any FTP Push operation in progress. Note that when this item is selected, NetLink will immediately terminate a Periodic Push or Force FTP Push.

 

15.4.1. File Names Created by FTP Push

When the FTP Push feature is used, NetLink will assign a name to the file that receives the data. This file name will be based on the user-defined, base file name, the source port, and data type. If desired, file names can also include an automatically incremented three character extension. As shown in Figure 15.5, the filename consists of the following components:

Note: This file naming convention applies only to data transferred by the FTP Push feature. A different file naming convention is employed when data is transferred using the FTP Server. For more information, please refer to Section 15.5.3.

C File Name (Up to Four Characters): The base file name defined via item 6 in the FTP Push Configuration menu. If the file name is not defined, NetLink will use the first three characters of the Site ID message. If the Site ID message is not defined, the letters "PNL" will be used. Note that if the file name is less than four characters, the remaining characters in this field will not be used.

e Source Port (Up to Three Characters): NetLink will enter from one to three characters to indicate which input port(s) originally received the data. NetLink will enter an "A" for PBX Port A, "B" for PBX Port B, and/or "X" for the Aux Port. If fewer than three source ports are indicated, the remaining characters in this field will not be used.

Figure 15.5: FTP Push File Names

 

 

® Data Type (One Character): The selected Data Type (File Type). NetLink will list the number for the data type selected at the FTP Push Configuration menu (see item 11 "Read Session"). These numbers are as follows:

1                     All: Both Alarm Records and Non-Alarm Records.

2                     Standard (Non-Alarm): Only Non-Alarm Records

3                     Alarm Filter 1 (All): All records that matched any clue defined for Alarm Filter 1.

4                     Alarm Filter 1 (By Clue): Only records that matched a specific clue defined for Alarm Filter 1.

5                     Alarm Filter 2 (All): All records that matched any clue defined for Alarm Filter 2.

6                     Alarm Filter 2 (By Clue): Only records that matched a specific clue defined for Alarm Filter 2.

7                     All Alarms: All records that matched any clue defined for either Alarm Filter 1 or Alarm Filter 2.

 

For example, if Data Type is defined as "All" (item 1) then the file

name will have a "1" in this field.

@ File Extension (Three Characters; Optional): NetLink can append a sequentially numbered (000 to 999) three digit extension. This number will be incremented after each successful data transfer. If the Data Type or Source Port are changed, the file extension will be reset to "000".

Examples:

•                      If the File Name is defined as "DATA", and the FTP Push Configuration menu has been set to download all data (Option 1) received via PBX Port B (B), then the first file name written at the FTP server would be "DATAB1.000".

•                      If the File Name is defined as "PBX", and the FTP Push Configuration menu has been set to download Standard Data (Option 2) received via PBX Port A, PBX Port B, and the AUX Port (ABX), then the first file name written at the FTP server would be "PBXABX2.000".

•                      If the File Name has not been defined, but the Site ID message is "ATLANTA", and the FTP Push Configuration Menu has been set to download all alarm data (Option 7) received via the AUX Port (X), then the first file name written at the FTP server would be "ATLX7.000"

 

15-18