The Data Filters
8.3. Defining Data Filter Clues
Data Filter match parameters describe the speciﬁc criteria that NetLink II
will use to determine if call records should be stored or discarded. Storage/
rejection criteria are referred to as "Clues". Parameters can be combined
under a single clue, or divided between a series of clues to create a logical
Clues are deﬁned using item 4 in the Data Filter Conﬁguration menu
(Figure 8.1). Each clue will usually include the following:
• Variable(s): One or more variables from the Data Filter Format,
which designate the ﬁeld(s) to be monitored. For example, the
variable may represent the call record ﬁeld for the number dialed.
• Operator(s): One or more of the logical or comparative operators
described in Section 8.4.
• Parameter(s): A description of call characteristics which will be used
as the criteria for storage or rejection. For example, speciﬁc numbers
or area codes for which records will not be stored.
To deﬁne Data Filter clues, proceed as follows:
1. Access the Data Filter Conﬁguration Menu.
2. Data Filter Action: Type 1 and press [Enter] to specify whether the
ﬁlter will store or reject records that match Clue Parameters.
3. Deﬁne Clues: Type 4 and press [Enter] to deﬁne parameters that will
be used as the criteria for storage or rejection. The Deﬁne/Edit Clue
menu will appear.
a) Clue Name: Type 1 and press [Enter] to assign a Clue Name.
This name can be used to reference a speciﬁc clue when altering
or deleting clues.
b) Match Parameters: Type 2 and press [Enter] to deﬁne the
criteria for storage or rejection. Match Parameters consist of one
or more variable(s) from the Data Filter Format, one of the logical
operators discussed in Section 8.4, and the value that will be
matched (e.g., the number dialed).
Example: If the Data Filter Format assigns "A" to represent the
call record ﬁeld for the number dialed, then A=5551212 tells
NetLink II to check this ﬁeld for the number "5551212".
c) Match Parameters may reference several variables, may include
logical operators, and may also include logical AND/OR
conditions. Please refer to the examples in Section 8.7.