|
| |
How to Use a Value of a Field to Filter Events
The filter files provided as templates are defined without any filtering actions.
In value mode, the selection conditions must be defined in the specifications
of an action in order to be used.
Here is an example of how to define a filter action whilst editing an
event file with the Protocol Event Editor:-
- Open the Event File in the Protocol Event Editor with a reference
filter.
- Select Edit=>Protocol filter
from the main menu to display the Event Filter Editor.
- In the filter action list, double click None and
replace it with Display.
- The selection conditions can be specified by editing the action.
Value filtering
To use an action and to select all the protocol events which include
a particular value of a decoding layer field:-
- Select the action (the current one is highlighted).
- Edit the action (Events from Filter set 1 which,
by default, groups all the interfaces).
- Enter the value (Protocol events=>Value).
Examples for the following cases are given here:-
- Q921-LAPD (SAPI, TEI or extended address).
- OSI layer 3.
- Data value in the data field at any decoding level.
Q921-LAPD value
Common examples:-
- The SAPI standard values are:
| SAPI = 00 |
0 0 0 0 0 0 |
| SAPI = 16 |
0 1 0 0 0 0 |
| SAPI = 63 |
1 1 1 1 1 1 |
- The TEI standard values are:
| TEI = 000 |
0 0 0 0 0 0 0 |
| TEI = 064 |
1 0 0 0 0 0 0 |
| TEI = 127 |
1 1 1 1 1 1 1 |
- Each extended address octet uses bits b8 to b1:
| Octet 1 = 009 |
0 0 0 0 1 0 0 x |
| Octet 1 |
0 0 0 0 1 0 x x |
- This latter value represents the group of values: {8, 9, 10, 11}.
OSI layer 3 value
Binary input for a group of LCs:-
| x x x x x x x x x x x 0 |
even number LCN's, all groups. |
| 0 0 0 0 0 0 0 0 x x x x |
LC's from 0 to 15, group 0. |
| x x x x 0 0 0 0 0 0 0 1 |
LC 1, all groups. |
| x x x x x x x 1 0 0 0 0 |
LC 016, 048, 080 ...., all groups. |
Data-value in the data field
1) To select all the Q931 INFORMATION messages of any Call Reference
including the Called Party Number IE as the first IE and monitored on
a BRI interface, the protocol filter can be defined with the following
specifications as a Q921 data-field value:-
- Number of bytes: 5.
- Offset: 0.
- Mode: Fixed.
| 1rst byte |
0x08 |
(Q931 protocol identifier). |
| 2nd byte |
0x01 |
(Call Reference length for BRI). |
| 3rd byte |
xx |
(for any Call Reference). |
| 4th byte |
0x7B |
(INFO message). |
| 5th byte |
0x70 |
(Called Party Number IE). |
2a) To select all the Q931 DISCONNECT messages of any Call Reference including
the Cause IE with value 17 as the first IE and monitored on a PRI interface,
the protocol filter can be defined with the following specifications as
a Q921 data-field value:-
- Number of bytes: 5.
- Offset: 4.
- Mode: Fixed.
| 1rst byte |
0x45 |
(DISC message). |
| 2nd byte |
0x08 |
(Cause IE). |
| 3rd byte |
0x02 |
(Length). |
| 4th byte |
1xx0xxxx |
(Coding standard + Location fields). |
| 5th byte |
0x91 |
(Cause value=17=User busy). |
2b) To select all the Q931 messages of any Call Reference including the Cause
IE with value 17 as the first IE and monitored on a BRI or PRI interface,
the protocol filter can be defined with the following specifications as
a Q931 data-field value:-
- Number of bytes: 4.
- Offset: 0.
- Mode: Fixed.
| 1rst byte |
0x08 |
(Cause IE). |
| 2nd byte |
0x02 |
(Length). |
| 3rd byte |
1xx0xxxx |
(Coding standard + Location fields). |
| 4th byte |
0x91 |
(Cause value=17=User busy). |
|
