Signal Trace Interpreter: in This Document
Signal Trace Interpreter: in This Document
Signal Trace Interpreter: in This Document
Interpreter
IN THIS DOCUMENT
Welcome
Introduction
Basic steps
Using STI
Troubleshooting
Glossary
Example
Index
February, 2001
EN/LZT 102 3050 R3A
NOTICE
Welcome...........................................................................................5
Introduction.....................................................................................5
Introduction to Signal Trace Interpreter...........................................................5
System Requirements.....................................................................................5
Capacity and Limitations.................................................................................6
What you will find in Help................................................................................6
Basic steps for using STI...............................................................7
Basic Steps for using the Signal Trace Interpreter..........................................7
Initiate signal tracing and write the signal trace to a hex file...........................7
Open hex file................................................................................................... 7
Translate the hex file.......................................................................................7
Manipulate the output file................................................................................7
Using STI..........................................................................................8
STI main window............................................................................................ 8
STI main window......................................................................................8
Source screen.......................................................................................... 9
Interpreter screen.....................................................................................9
Summary screen......................................................................................9
Changing color settings................................................................................10
Changing filter display options......................................................................10
Changing the font in the Source screen........................................................10
Changing the font in the Interpreter screen...................................................10
Changing the font in the Summary screen....................................................11
Customizing the Summary screen................................................................11
Filtering conversion results...........................................................................11
Outgoing Message Filter........................................................................12
Incoming Message Filter........................................................................12
All Messages.......................................................................................... 12
Signal Information and Hardware Related Filters...................................12
Filtering the results of an output file..............................................................13
Interpreting signal trace files.........................................................................13
Opening a trace or output file........................................................................14
Printing the Interpreter screen......................................................................14
Printing the Summary screen........................................................................14
Saving the current settings...........................................................................15
Saving an output file.....................................................................................15
Translating signal names..............................................................................16
Viewing message text...................................................................................16
SAM includes the Signal Trace Interpreter (STI), an off-line, Windows application that
interprets ISDN, DECT and IP signal traces and translates them from Hex code into English
text.
Introduction
Introduction to Signal Trace Interpreter
Signal Trace Interpreter (STI) is an off-line, Windows application that interprets signal trace
log files generated on the MD110 system and then translates the hex code to English text.
STI includes several filters to control the presentation of the output. STI displays the output on
a GUI screen, but the result can also be saved as a file on the PC. You can open multiple STI
windows and view source or output files concurrently.
STI handles ISDN, DECT and IP signals, including UUI for ISDN.
System Requirements
Your PC must meet the following minimum requirements to run STI:
Windows 95/98, Windows 2000, or Windows NT 4.0
20 MB free disk space
WinFIOL or other TTY interface
STI interprets IP, DECT and layer 3 signals for ISDN-PRI. STI supports the long signal format
in release version BC 7.2 and higher (including BC11).
Limitations:
STI must be updated and recompiled with new IE when the MD signal trace contents
change.
The signal trace file must contain only one trace session with the signal trace sequence
numbers in ascending order. For example, multiple trace files cannot be cut and pasted into
a single trace file.
Step 1 Initiate a signal trace and write the signal trace to a hex file
Initiate signal tracing and write the signal trace to a hex file
Initiate signal tracing on the MD110 using either WinFIOL or the TTY interface that is included
with the SAM toolbox. The signals are written as hex code to a trace file.
Note: The MD110 handles incoming and outgoing calls as normal. Initiating a trace on the
MD110 does not impact performance or functionality.
How to:
Open a trace file
How to:
Interpret a signal trace log file
Save an output file
How to:
Filter the results of an output file
Save an output file
How to:
Change the font in the source screen
Interpreter screen
The right-hand top portion of the STI window contains the Interpreter screen. The Interpreter
screen displays the output file, which is the converted text file generated during the translation
process. The message header is displayed in one color while the text is displayed in another.
Lines that could not be fully interpreted are highlighted. The display font and the colors used
for distinguishing between incoming and outgoing messages can be modified to suit your
preferences.
How to:
Change the color settings in the interpreter screen
Change the font in the interpreter screen
Summary screen
The right, bottom portion of the STI main window contains the Summary screen. The
Summary screen displays summary signal information about the interpreted text file
generated during the translation process. The Summary screen includes the following
information for each interpreted message:
Signal Sequence Number
Message Direction: Received (incoming) or Send (outgoing)
Signal Name
Message Name
Time Stamp
EQU
The columns displayed in this screen can be displayed, hidden, or resized to suit your
preferences. The display font can also be changed or resized.
How to:
Customize the summary screen
Change the font in the summary screen
To change the text colors in the Interpreter screen, perform the following:
1 Select Color Settings from the Options menu. The Color Settings dialog appears.
2 Click the Change color button for the incoming or outgoing signal to change the text
color for those messages.
2 Click Include all Rows to display all signals, even those not fully interpreted
3 Click Include Hex to display the Hex code as well as the interpreted text.
1 With the pointer in the Source screen, right-click to display the Source menu.
2 Click Font.
4 Click OK.
5 The Source screen now displays the information in the selected font.
1 With the pointer in the Interpreter screen, right-click to display the Interpreter menu.
2 Click Font.
4 Click OK.
5 The Interpreter screen now displays the information in the selected font.
1 With the point in the Summary screen, right-click to display the Summary menu
2 Click Font.
4 Click OK.
5 The Summary screen now displays the information in the selected font.
2 To toggle between display column and hide column modes, click the name of the column
heading from the function menu.
3 The contents of the Interpreter and Summary screens are refreshed to display the filtered
data.
All Messages
Select this filter to display all of the interpreted messages to and from the
MD110. The Interpreter and Summary screens are refreshed to display the
filtered data. Depending on the configuration settings specified in the STI.INI
file, the output file may be overwritten with the filtered results.
How to:
Filter conversion results
Change filter display options
2 Right-click within the Source screen and then select Interpret from the menu or click
from the toolbar.
Example:
This is a trace file from an IP Basic Call with gateway call. See in the back of this document.
Some files may contain inconsistencies in the naming conventions of the ISDN HW signal
names that appear in the signal traces. To modify the signal names that STI should look for
during parsing, you can translate the signal names.
1 Choose Open from the File menu or click from the toolbar.
2 From the Open dialog box, select an input file to interpret, save, print, or view.
3 Click Open.
To open a file using Drag and Drop, perform the following steps:
3 From the File menu, choose Save and then close the STI.ini file.
4 From Windows Explorer, locate the file that you want to open.
5 Using the left mouse button, click the file and drag it to the STI button on the task bar. Do
not release the mouse button.
6 When the STI window open, drag the file into the window and release the left mouse
button.
1 With the pointer in the Interpreter screen, right-click to display the Interpreter menu.
2 Click Print.
4 Click OK.
1 With the pointer in the Summary screen, right-click to display the Summary menu.
2 Click Print.
4 Click OK.
1 With the cursor in the Interpreter pane, right-click and choose Save from the drop-down
menu.
2 The Save As dialog box opens. Select the directory in which to save the file, enter the
new file name, and specify the file type.
3 Click Save.
2 From the drop-down menu, select Signal Names. The following screen appears:
3 In the Name in the signal trace region, type the name of the signal that appears in the
opened file for the corresponding signal type.
4 Click OK.
To view the message text for a specific message, perform the following:
2 Double-click the signal line or right click to display the function menu and then click Go
To. Both the Source and Interpreter screens scroll to the corresponding signal.
STI rejects all signals with unidentified header strings. Refer to the documentation for a list of
identified strings. To fix this, change the affected signal accordingly.
All call reference lengths should be 1/2/3. If a call reference length is greater than 3, the call is
rejected and STI displays this error. To fix this, change the signals call reference length
indicator accordingly.
Message type is not recognizable (check the BC version compatibility with STI). To fix this,
make changes to STI to handle the new message type.
Note: This exception occurs when the default for UUI is not HFE also.
STI rejects protocols which are not either H08/H00 (for long signals) and H40/H41 (for short
signals). To fix this, change the protocol discriminator accordingly.
A model for binary code developed by Microsoft. The Component Object Model (COM)
enables programmers to develop objects that can be accessed by any COM-compliant
application. Both OLE and ActiveX are based on COM.
This is a list of pre-identified values that are found in the trace file; i.e. H04 could mean
Bearer Capability.
Input file
Interpreter screen
The right, top portion of the STI window contains the Interpreter screen. The Interpreter
screen displays the output file, which is the converted text file generated during the translation
process. The message header is displayed in one color while the text is displayed in another.
Lines that could not be fully interpreted are highlighted. The display font used in this pane can
be modified to suit your preferences.
Output file
Also referred to as the result file, the output file is created when STI interprets a signal trace
log file. It contains the English text messages that have been interpreted from the original Hex
code messages by STI. A summary of the result file displays in the top right portion of the STI
main window. The complete file text displays in the bottom right portion of the STI main
window.
A PABX is the telephone switch that is used at small to medium-sized companies. This is the
generic name for Ericssons MD110 switch.
Result file
SLP60
Also referred to as an input file, the source file is the original signal trace log file generated
from the MD110. It contains the Hex code messages to be interpreted by STI. The source file
displays in the Source Pane of the STI main window.
Source screen
The left side of the STI main window contains the Source screen. The Source screen displays
either the input trace file or the interpreted output file.
An off-line, Windows application that interprets ISDN and DECT signal traces and translates
them from Hex code into English text
Summary screen
The right, bottom portion of the STI main window contains the Summary screen. The
Summary screen displays summary signal information about the interpreted text file
generated during the translation process. The Summary screen includes the following
information for each interpreted message:
Signal Sequence Number
Message Direction: Received (incoming) or Send (outgoing)
Signal Name
Message Name
Time Stamp
EQU
Note: The columns displayed in this screen can be displayed, hidden, or resized to suit your
preferences. The display font can also be changed or resized.
Ericsson proprietary information elements, which are identified by hex code H7E.
CMPARAM CALL TYPE IE: CMRASPARAM DEST CALL SIGNAL ADDRESS IE:
cmCallType : P2P IP Address : 136.225.43.71
Port Number : 1720
CMPARAM CALL ID IE: cmTransportType: IP
00 C0 C7 42 31 99 D2 11 8D 04 1D 5C 5D FF 49 89
TERMINALTYPE IE:
Integer Value : 60
STATUSDETERMINATIONNUMBER IE:
Integer Value : 93
IP summary screen