WISUPDecode Help

Benjamin Cassan-de Gorostarzu

Product: WISUPDecode
Version: 3.1.0

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".


Table of Contents

1. Introduction
1.1. Purpose
1.2. Features
1.3. Acknowledgements
2. Installation
2.1. WISUPDecode
2.1.1. From binary
2.1.2. From sources
2.2. Decoder
2.2.1. From binary
2.2.2. From sources
3. Getting Started
3.1. Selecting a decoder
3.2. Decoding a message
4. Interface
4.1. Menu Bar
4.1.1. File Menu
4.1.2. Decode Menu
4.1.3. Options Menu
4.1.4. Help Menu
4.2. Status Bar
4.3. Main Panel
4.3.1. Raw data
4.3.2. Decoded data
4.4. Dump Panel
4.5. Dialog Boxes
4.5.1. About Dialog Box
4.5.2. Message Selection Dialog Box
A. Supported messages and parameters
A.1. ETSI decoder
A.1.1. Messages
A.1.2. Parameters
A.2. ANSI decoder
A.2.1. Messages
A.2.2. Parameters
A.3. BELLCORE decoder
A.3.1. Messages
A.3.2. Parameters
B. GNU Free Documentation License
B.1. PREAMBLE
B.2. APPLICABILITY AND DEFINITIONS
B.3. VERBATIM COPYING
B.4. COPYING IN QUANTITY
B.5. MODIFICATIONS
B.6. COMBINING DOCUMENTS
B.7. COLLECTIONS OF DOCUMENTS
B.8. AGGREGATION WITH INDEPENDENT WORKS
B.9. TRANSLATION
B.10. TERMINATION
B.11. FUTURE REVISIONS OF THIS LICENSE
B.12. ADDENDUM: How to use this License for your documents
Index

List of Tables

3.1. Hexa dump fields colors
4.1. Menu entries
4.2. File menu entries
4.3. Decode menu entries
4.4. Options menu entries
4.5. Content menu entries
4.6. Font size menu entries
4.7. Help menu entries

Chapter 1. Introduction

Table of Contents

1.1. Purpose
1.2. Features
1.3. Acknowledgements

1.1. Purpose

WISUPDecode is a graphical Java decoder for the SS7 ISUP protocol, under GPL license. Given an hexadecimal dump of a message, it tries to decode it according to a selected decoder.

[Warning]Warning

This application is not a validator. It can successfully decode invalid messages. This is mainly a tool for reading (and also writing) dumps of messages. Main things that are not checked:

  • Consistency of messages and parameters, message structure (pointers, length, etc.). Few errors can be reported, but WISUPDecode does not try to check if messages and parameters are valid.

  • Parameters inside a message: ISUP standards define for each message the list of allowed parameters. This is not check by WISUPDecode. Even if according to the standard, a parameter should not be found in a message, the decoder will decode it without warning.

1.2. Features

Some features:

  • Support for several decoders, dynamically managed. New decoders can easily be integrated.

  • Portability (Java application).

  • Several possible languages for the interface (currently two, but anybody can add a new language).

  • Three decoders supported:

    • ETSI [ETS 300 356-1 [ITU Q.761 to Q.764 (1993) modified]],

    • ANSI [ANSI T1.113-1995],

    • BELLCORE [GR-CORE-317 (1994 issue)] and [GR-CORE-394 (1994 issue)].

  • Under GPL license :-)

See the list of supported messages and parameters for each ISUP variant.

1.3. Acknowledgements

Thanks to Joe Ratterman, who wrote two of the current decoders ANSI and BELLCORE), and who updated the old applet code for the three decoders. His web site is running the three applets.


Chapter 2. Installation

Table of Contents

2.1. WISUPDecode
2.1.1. From binary
2.1.2. From sources
2.2. Decoder
2.2.1. From binary
2.2.2. From sources

WISUPDecode is distributed in binary and sources packages. You also need at least one decoder. Like the application, decoders are distributed in binary or sources packages. You can find installation information in the readme.txt file in the package.

[Note]Note

Sometimes it is not recommended to install a new version over an older one. See the readme file with the package about this.

2.1. WISUPDecode

2.1.1. From binary

The binary package is named WISUPDecode_X-X-X.zip or WISUPDecode_X-X-X.tgz. Just uncompress it in a directory. You must now have this:

install_dir/readme.txt
           /changes
           /Todo
           /license
           /COPYRIGHT
           /wisup.jar
           /wisup/
                 /module.jar
                 /protocol.jar
                 /speakers.jar
                 /conf/
                      /modules.properties
                 /lang/
                      /string.properties
                      /string_en.properties
                      /string_fr.properties
                 /isup/

WISUPDecode is now installed. To launch it, you must install at least a decoder. See the decoder installation for that.

To launch WISUPDecode, just execute the wisup.jar file with Java:

java -jar wisup.jar

According to the OS and the configuration, it can be possible to directly execute jar files.

When you start WISUPDecode for the first time, a configuration file, WISUPDecode.cfg, is created. Currently this text file is the only way to change the interface language. A property, named language, is set to the desired language. The default is en (English). You can set it to any ISO language code (see [ISO 639]), as en for English, fr for French, etc. There must be a matching string_<language-code>.properties file in the wisup/lang directory.

2.1.2. From sources

The source package is named WISUPDecode_X-X-X_src.jar. Uncompress it in a directory. You must now have this:

source_dir/readme.txt
          /changes
          /Todo
          /license
          /COPYRIGHT
          /ansiapplet.html
          /bellapplet.html
          /etsiapplet.html
          /main.mf
          /module.mf
          /protocol.mf
          /speakers.mf
          /WISUPDecode_src.mf
          /makefile
          /WISUPDecode.dox
          /WISUPDecode.xml
          /wisup/
                /conf/
                     /modules.properties
                /isup/
                /lang/
                     /string.properties
                     /string_en.properties
                     /string_fr.properties
                /main/
                     /*.java
                     /*.form
                /module/
                       /*.java
                /protocol/
                         /*.java
                /speakers/
                         /*.java

The applet files (java and html) are not supported. It was written for a modified version 2.1.0 of WISUPDecode. It is provided for those who wants to hack the code. The makefile is part of this code, and probably do not work with the current code.

You need a Java 2 JDK for compiling the code. I currently use a 1.3.x JDK.

For developing I use NetBeans, a Java OpenSource IDE. The *.form files are XML files used by NetBeans for designing the GUIs of the application. I use ANT for building WISUPDecode. The ANT makefile is WISUPDecode.xml. It defines all the required targets, for WISUPDecode and for the decoders. I strongly suggest to use ANT instead of trying to build everything directly with javac.

[Note]Note

Some targets need the decoders sources.

If you want to build the Doxygen documentation, you can use the WISUPDecode.dox file. Look at the documentation of Doxygen about the options defined in the dox file (created with the GUI packaged with Doxygen).

2.2. Decoder

The three current decoders are installed in the same way. The installation is detailed for the ETSI decoder.

2.2.1. From binary

The binary package is named ets300_356_1_X-X.zip or ets300_356_X-X.tgz. You can install it where you want, but the preferred solution is in wisup/isup directory. After decompression, you must now have this:

install_dir/wisup/isup/
                      /ets300_356_1.jar
                      /ets300_356_1/
                                   /changes
                                   /COPYRIGHT
                                   /license
                                   /readme.txt

You now need to modify the wisup/conf/modules.properties. The file provided with WISUPDecode is already set up for the three decoders located in wisup/isup/ directory. If you installed your decoder somewhere else, or if you need to change the configuration, follow these steps:

  1. Each decoder is associated with an index. The first decoder has index 0, the second the index 1, etc. According to the current configuration, select the first available index. Lets say index 0.

  2. You must set the two following variables:

    VariableDescriptionValue
    decoder.0Package name of the decoderwisup.isup.ets300_356_1
    decoder.0.pathPath of the packagewisup/isup/ets300_356_1.jar

    These values should be provided by the readme file of the decoder. The path can be set according to the current classpath. The location of the wisup.jar file is automatically added to the classpath, so the value wisup/isup/ets300_356_1.jar for the decoder path can be used. You can also use an URL for the path.

When the modules.properties file is modified, you can launch WISUPDecode. The application checks if the decoders can be loaded at start-up, so you can see if the configuration is valid.

2.2.2. From sources

[Important]Important

You need the WISUPDecode sources for building the decoders.

The source package is named ets300_356_1_X-X_src.jar. Uncompress it in the wisup/isup/ directory. You must now have this:

source_dir/wisup/isup/
                     /ets300_356_1/
                                  /changes
                                  /COPYRIGHT
                                  /license
                                  /readme.txt
                                  /ets300_356_1.mf
                                  /ets300_356_1_src.mf
                                  /*.java

Now refer to the WISUPDecode source installation for building the decoder. Some ANT makefile targets are defined for building each decoder.


Chapter 3. Getting Started

Table of Contents

3.1. Selecting a decoder
3.2. Decoding a message

This chapter will help you to quickly use WISUPDecode for decoding your ISUP messages.

3.1. Selecting a decoder

There is several decoders available for decoding messages. Three are currently available on the WISUPDecode web site:

  • ETSI decoder [ETS 300 356-1 [ITU Q.761 to Q.764 (1993) modified]],

  • ANSI decoder [ANSI T1.113-1995],

  • BELLCORE decoder [GR-CORE-317 (1994 issue)] and [GR-CORE-394 (1994 issue)].

It is not require to install all the decoders. At least one is required for starting the application. If you want to select another decoder than the default one, use the menu Options >> Decoder.

3.2. Decoding a message

Before decoding a message, you have to configure the kind of data at the beginning of the message. A message is represented by hexadecimal bytes (2 characters), separated by spaces. Example of an IAM message (ETSI): 01 00 33 02 0A 06 02 00 05 81 00 33 55 F9.

The message content can be preceded by two fields:

  • The CIC, 2 bytes long. You have to select it if it is at the beginning of your data (see Options >> Content). Note that you can also remove this 2 bytes from the data.

  • The message tag, 1 byte long.

You can paste the message dump in the main panel of the application. There is no cut/copy/paste menu yet. You can also open a text file with the data.

Then, if the message tag is provided, just use the menu Decode >> Decode message for decoding the message. If the message tag is not in the data, the menu Decode >> Select message will display the message selection dialog box, for selecting the message to decode.

The main panel displays the decoded message, each recognized field described. The hexa dump panel displays the original dump message with specific fields highlighted:

Table 3.1. Hexa dump fields colors

ColorField type
redidentifier
bluelength
greypointer

You can save the decoded message in a file. Note that the content of the dump panel is not saved.


Chapter 4. Interface

This chapter describes the graphical interface of the application.

4.1. Menu Bar

Table 4.1. Menu entries

FileMenu for opening/saving data.
EditNot available.
DecodeMenu for decoding functions.
OptionsMenu for changing options.
HelpMenu for the help.

4.1.1. File Menu

Table 4.2. File menu entries

NewCreate an empty file. Data can then be pasted in the main panel.
Open...Open an existing file. This file can contains raw data to decode.
SaveSave the current opened file. If there is no file associated with the current data, the Save as... dialog box is displayed.
Save as...Prompt you for saving the current data in a file.
File historyA list of the last opened files.
QuitQuit the application.
[Warning]Warning

There is no check on the modification state of the current data. That means the application will not prompt you if you want to quit with unsaved data.

4.1.2. Decode Menu

Table 4.3. Decode menu entries

Clean dataRemove from the current data all characters that are not hexadecimal (others than [0-9a-fA-F], group values for having a list of bytes values (xx xx xx xx).
Clean and reverse bytesSame as Clean data, but also reverse bytes: 01 02 becomes 02 01.
Decode messageDecode the current data. Only available if the message tag is part of the data (see the menu Options >> Content).
[Warning]Warning

The current file is closed and a new file is created for the decoded data. There is no check on the modification state of the current data. That means the application will not prompt you if you start decoding with unsaved data.

Select messageLaunch the Message selection dialog box. Only available if the message tag is not part of the data (see the menu Options >> Content). When the message is selected, the data are decoded according to the message selection.
[Warning]Warning

The current file is closed and a new file is created for the decoded data. There is no check on the modification state of the current data. That means the application will not prompt you if you start decoding with unsaved data.

4.1.3. Options Menu

Table 4.4. Options menu entries

DecoderMenu for the decoder selection.
ContentMenu for selecting specific fields in the raw data.
Font sizeMenu for changing the font size.

4.1.3.1. Decoder Menu

This menu lists the available decoders. You can select the decoder you want to use. There is at least one decoder in the list. See the decoder installation for installing decoders.

4.1.3.2. Content Menu

Table 4.5. Content menu entries

CICSelect it if the CIC is at the beginning of the data. The CIC is supposed to be the 2 first bytes of the data.
Message typeSelect it if the message tag is in the data. If selected, the decoder will read it for selecting the type of the message to decode. If not selected, the Message Selection Dialog Box will ask the message type to use for decoding.

4.1.3.3. Font size Menu

Table 4.6. Font size menu entries

BiggerIncrement the font size.
SmallerDecrement the font size.

4.1.4. Help Menu

Table 4.7. Help menu entries

ContentsNot available (will be this help)
About...Call the About dialog box.

4.2. Status Bar

The status bar is separated in 2 parts:

  • The left part is used for displaying messages, mainly error messages or warnings.

  • The right part displays the active decoder.

4.3. Main Panel

The main panel is used for displaying the raw data to decode and the decoded data. The content can be freely modified by the user. The content can come from a text file, and can be saved.

4.3.1. Raw data

Raw data is represented by hexadecimal bytes (2 characters), separated by spaces. This is probably the most common representation. The message content can start with the CIC and the message tag byte.

It is not require to have a "clean" dump of the message. Extra characters that are not hexadecimal are removed before decoding.

[Warning]Warning

There is no check on the modification state of the current data. That means the application will not prompt you if you want to quit with unsaved data.

4.3.2. Decoded data

The decoded data is in text format, with simple visual formatting:

CIC : 00 00 (0)
IAM (Initial Address Message) (1) [ (71) 00 22 00 FF 03 02 09 08 83 20 12 44 ... 55 00 00  ]
Mandatory fixed parameters :
  Octet  0  Nature of connection ind. (6) [ (1) 00  ]
    ......00     no satellite circuit in the connection (0)
    ....00..     continuity check not required (0)
    ...0....     outgoing half echo control device not included (0)
  Octet  1  Forward call ind. (7) [ (2) 22 00  ]
    .......0     national call (0)
    .....01.     pass along method available (1)
    ....0...     no interworking encountered (SS7 all the way) (0)
    ...0....     no end-to-end information available (0)
    ..1.....     ISUP used all the way (1)
    00......     ISUP preferred all the way (0)
    .......0     originating access non-ISDN (0)
    .....00.     no indication (0)
  Octet  3  Calling party's category (9) [ (1) FF  ]
    ........     spare/reserved for national used (-1)
  Octet  4  Transmission medium requirement (2) [ (1) 03  ]
    00000011     3.1 kHz audio (3)
    00000010 --> + 2
    00001001 --> + 9
Mandatory variable parameters :
  Octet  7  Called party number (4) [ (8) 83 20 12 44 42 21 21 0F  ]
    00001000    length 8
    1.......     odd number of address signals (1)
    .0000011     national (significant) number (3)
    0.......     routing to internal network number allowed (0)
    .010....     spare (2)
                 Called number : 21 44 24 12 12 ST
ERROR : bad optional part pointer (9 instead of 10)
Optional parameters :
  Octet 16  Called party number (4) [ (4) 87 70 21 43  ]
    00000100   Called party number
    00000100    length 4
    1.......     odd number of address signals (1)
    ........     spare/reserved for national use (-1)
    0.......     routing to internal network number allowed (0)
    .111....     spare (7)
                 Called number : 12 3
[Note]Note

The example used for describing the formatting is an ETSI message.

There is several parts in the decoded data:

  • The header, with the CIC and the message information.

  • The pointers.

  • The mandatory fixed parameters.

  • The mandatory variable parameters.

  • The optional parameters.

4.3.2.1. Header

There is two parts:

  • The CIC, if it has been set in . The two bytes are displayed, with the decimal value in parenthesis

    CIC : 00 00 (0)

  • The message information:

    IAM (Initial Address Message) (1) [ (71) 00 22 00 FF 03 02 09 08 83 20 12 44 42 ...  ]
    • The acronym of the message.

    • The name of the message, in parenthesis.

    • The decimal identifier of the message.

    • The raw content of the message, in brackets (the first value, in parenthesis, is the length of the message).

4.3.2.2. Pointer

A pointer has a simple layout:

00000010 --> + 2
  • The byte of the pointer.

  • The decimal value of the pointer.

4.3.2.3. Mandatory fixed parameters

For each parameter, the following information is displayed:

  • The parameter information:

      Octet  1  Forward call ind. (7) [ (2) 22 00  ]
    • The byte index. The index starts at 0.

    • The parameter name.

    • The decimal identifier of the parameter.

    • The raw content of the parameter, in brackets (the first value, in parenthesis, is the length of the parameter).

  • Each meaningful bits field of the parameter is displayed on a line:

        .......0     national call (0)
        .....01.     pass along method available (1)
        ....0...     no interworking encountered (SS7 all the way) (0)
        ...0....     no end-to-end information available (0)
        ..1.....     ISUP used all the way (1)
        00......     ISUP preferred all the way (0)
        .......0     originating access non-ISDN (0)
        .....00.     no indication (0)
    • The value of the bit(s).

    • The meaning of the value.

    • The decimal value of the bits-field, in parenthesis.

[Note]Note

For parameters with multi-bytes field, as called numbers, etc., the values of the bits are not displayed, only the meaning of the field (as the number):

Called number : 21 44 24 12 12 ST
[Note]Note

Sometimes the same decoding is used for different messages. The meaning for each message is given, and the reading must be done according to the message type:

.......1     blocking (CGB) / blocking ack. (CGBA) / unblocking (CGU) / unblocking ack. (CGUA) / blocked for maintenance reasons (GRA) (1)

4.3.2.4. Mandatory variable parameters

The layout is the same than mandatory parameter, but with the length between the parameter information and the fields description:

00001000    length 8
  • The byte of the length.

  • The decimal value of the length.

4.3.2.5. Optional parameters

The layout is the same than mandatory variable parameter, but with the parameter byte between the parameter information and the length:

00000100   Called party number
  • The byte of the parameter header.

  • The parameter name.

4.4. Dump Panel

This panel displays the original message, with specific bytes highlighted:

  • In red, the identifiers (of message, of optional parameters).

  • In gray, the pointers.

  • In blue, the lengths.

This display is useful for a quick overview of the message structure.

4.5. Dialog Boxes

4.5.1. About Dialog Box

Access

This dialog is opened with the menu Help >> About.

Description

This dialog box provides information about the application:

  • The version,

  • The copyright,

  • The list of available decoders, with the version and the authors.

Sample

4.5.2. Message Selection Dialog Box

Access

This dialog is opened with the menu Decode >> Select Message - . This is available only if the message tag is not provided for the message (see the menu Options >> Content - for the message tag configuration).

Description

If the message tag is not in the data, you have to select the type of the message to decode. This dialog box displays all recognized messages for the current decoder. The decoding will be done according to your selection.

Sample

Appendix A. Supported messages and parameters

Table of Contents

A.1. ETSI decoder
A.1.1. Messages
A.1.2. Parameters
A.2. ANSI decoder
A.2.1. Messages
A.2.2. Parameters
A.3. BELLCORE decoder
A.3.1. Messages
A.3.2. Parameters

A.1. ETSI decoder

This decoder is based on [ETS 300 356-1 [ITU Q.761 to Q.764 (1993) modified]]. It was the first decoder written for WISUPDecode.

A.1.1. Messages

List of supported messages: ACM, ANM, CFN, CGB, CGBA, CGU, CGUA, CON, COT, CPG, CQM, CQR, GRA, GRS, IAM, INF, INR, REL, RLC, SAM, all the messages without parameters (BLO, BLA, etc.)

A.1.2. Parameters

List of supported parameters: transmission medium requirement, called party number, subsequent number, nature of connection ind., forward call ind., optional forward call ind., calling party's category, calling party number, redirecting number, information request ind., information ind., continuity ind., backward call ind., cause ind., redirection information, circuit group supervision msg type ind., range and status, transit network selection, event information, circuit state ind., original called number, optional backward call ind., generic number

A.2. ANSI decoder

This decoder is based on [ANSI T1.113-1995]. It has been written by Joseph Ratterman.

A.2.1. Messages

List of supported messages: ACM, ANM, CFN, CGB, CGBA, CGU, CGUA, COT, CPG, CQM, CQR, CRA, CRM, CVR, CVT, EXM, FAC, FOT, GRA, GRS, IAM, INF, INR, LPA, PAM, REL, RES, RLC, SUS, all the messages without parameters (BLO, BLA, etc.)

A.2.2. Parameters

List of supported parameters: Access transport, Called party number, Nature of connection ind., Forward call ind., Calling party's category, Calling party number, Redirecting number, Information request ind., Information ind., Continuity ind., Backward call ind., Cause ind., Redirection information, Circuit group supervision msg type ind., Range and status, User service information, User-to-user information, Suspend / Resume ind., Transit network selection, Event information, Circuit Assignment Map, Circuit state ind., Automatic congestion level, Original called number, Optional backward call ind., User-to-user ind., Service activation, MLPP precedence, Hop counter, Generic number, Generic digits, Carrier Identification, Business Group, Geographical Location, Jurisdiction Information, Generic Name, Notification Indicator, Circuit Group Characteristic Indicators, Circuit Validation Response Indicator, Outgoing Trunk Group Number, Circuit Identification Name, Common Language Location Identification, Originating Line Information, Charge Number, Carrier Selection Information, Network Transport

A.3. BELLCORE decoder

This decoder is based on [GR-CORE-317 (1994 issue)] and [GR-CORE-394 (1994 issue)]. It has been written by Joseph Ratterman.

A.3.1. Messages

List of supported messages: ACM, ANM, CFN, CGB, CGBA, CGU, CGUA, COT, CPG, CQM, CQR, CRA, CRM, CVR, CVT, EXM, FAC, GRA, GRS, IAM, LPA, PAM, REL, RES, RLC, SUS, all the messages without parameters (BLO, BLA, etc.)

A.3.2. Parameters

List of supported parameters: Access transport, Called party number, Nature of connection ind., Forward call ind., Calling party's category, Calling party number, Redirecting number, Information request ind., Information ind., Continuity ind., Backward call ind., Cause ind., Redirection information, Circuit group supervision msg type ind., Range and status, User service information, User-to-user information, Suspend / Resume ind., Transit network selection, Event information, Circuit Assignment Map, Circuit state ind., Automatic congestion level, Original called number, Optional backward call ind., User-to-user ind., Service activation, MLPP precedence, Hop counter, Generic number, Generic digits, Carrier Identification, Business Group, Geographical Location, Jurisdiction Information, Generic Name, Notification Indicator, Circuit Group Characteristic Indicators, Circuit Validation Response Indicator, Outgoing Trunk Group Number, Circuit Identification Name, Common Language Location Identification, Originating Line Information, Charge Number, Carrier Selection Information, Network Transport

Appendix B. GNU Free Documentation License

Version 1.2, November 2002

Copyright (C) 2000,2001,2002 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

B.1. PREAMBLE

The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

B.2. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.

The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.

B.3. VERBATIM COPYING

You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

B.4. COPYING IN QUANTITY

If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

B.5. MODIFICATIONS

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

  1. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.
  2. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.
  3. State on the Title page the name of the publisher of the Modified Version, as the publisher.
  4. Preserve all the copyright notices of the Document.
  5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
  6. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.
  7. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.
  8. Include an unaltered copy of this License.
  9. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
  10. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
  11. For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.
  12. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.
  13. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.
  14. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.
  15. Preserve any Warranty Disclaimers.

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.

You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

B.6. COMBINING DOCUMENTS

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".

B.7. COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

B.8. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.

B.9. TRANSLATION

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.

If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.

B.10. TERMINATION

You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

B.11. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.

B.12. ADDENDUM: How to use this License for your documents

To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:

Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with...Texts." line with this:

with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.

Index

A

About, About Dialog Box
ANSI (see Decoders)
Applets, From sources

B

BELLCORE (see Decoders)

C

CIC, Decoding a message
Compiling
WISUPDecode, From sources
Configuration
Decoders, From binary
Language settings, From binary

D

Decoded message, Decoded data
Decoders
ANSI
ansi_X-X.tgz, From binary
ansi_X-X.zip, From binary
ansi_X-X_src.jar, From sources
Messages, Messages
Parameters, Parameters
BELLCORE
bellcore_X-X.tgz, From binary
bellcore_X-X.zip, From binary
bellcore_X-X_src.jar, From sources
Messages, Messages
Parameters, Parameters
Configuration, From binary
Decoded message, Decoded data
Header, Header
Mandatory fixed parameters, Mandatory fixed parameters
Mandatory variable parameters, Mandatory variable parameters
Optional parameters, Optional parameters
Pointer, Pointer
Decoding, Decoding a message
ETSI
ets300_356_1_X-X.tgz, From binary
ets300_356_1_X-X.zip, From binary
ets300_356_1_X-X_src.jar, From sources
Messages, Messages
Parameters, Parameters
Installation, Decoder
From binary, From binary
From sources, From sources
Selection, Selecting a decoder
Decoding, Decoding a message
Dialog boxes
About, About Dialog Box
Message selection, Message Selection Dialog Box
Documentation generation, From sources
Doxygen, From sources
Dump panel, Dump Panel

E

ETSI (see Decoders)
Execution, From binary

F

Features, Features

H

Hexa dump, Decoding a message

I

Installation, Installation
Decoders (see Decoders)
WISUPDecode (see WISUPDecode)

L

Language settings, From binary

M

Menus, Menu Bar
Message dump, Raw data
Message selection, Message Selection Dialog Box
Message tag, Decoding a message
Messages
Format
Decoded, Decoded data
(see also Decoders)
Raw, Raw data
modules.properties, From binary

R

readme.txt, Installation

S

Selecting a decoder, Selecting a decoder

W

WISUPDecode
Compiling, From sources
Execution, From binary
Installation, WISUPDecode
From binary, From binary
From sources, From sources
WISUPDecode_X-X-X.tgz, From binary
WISUPDecode_X-X-X.zip, From binary
WISUPDecode_X-X-X_src.jar, From sources