3.2. System Environment Configuration (system.txt)

The DataKinetics system environment configuration is defined by the system.txt file. This file is used by the GCTLOAD program to create message queues and spawn appropriate child processes.

The DataKinetics system uses the concept of modules that send messages to each other. Each module has a unique module ID, which must be specified by other modules in order to exchange messages to each other. The module IDs that exist on the host system must be defined using LOCAL commands in the system.txt file. Many module IDs are predefined and the lines that specify these modules in the system.txt file should be left unchanged.

Some Intel® Dialogic SS7 software components require module IDs that must be defined in the system.txt file. For example, the default configuration of the Intel® Dialogic SS7 software requires that the following lines be present in the system.txt file:

    LOCAL 0x4d * Dialogic SS7 Service 
    LOCAL 0x5d * Dialogic GC/SS7 Application #1 
    LOCAL 0x6d * Dialogic GC/SS7 Application #2  

The first line defines the module ID (and corresponding message queue) of the SS7 server. The other two lines define the module IDs reserved for two applications that can use Global Call to control calls on SS7 telephony circuits.

Notes:

1. The LOCAL command by itself does not specify the intended usage of the defined module ID, it just declares one. For Global Call SS7 to operate properly, there must be at least 2 module IDs declared and left available for its use (one for the SS7 server, and at least one for an application process).
2. In the system.txt file, comments are denoted by the asterisk (*) symbol, as indicated in the above example.

Other command types that are found in the system.txt file are:

• REDIRECT commands. These commands force the DataKinetics runtime system to redirect messages intended for a specific destination module to a different module. For example, in an Intel® NetStructure™ SS7 board system, this is used to redirect messages for the ISUP module to the module that interfaces with the board (ISUP is running on the board and not on the host).

  Besides normal redirections for proper operation of the software (see sample configuration files and the DataKinetics documentation), a system configured for Global Call SS7 should redirect status and management messages to the SS7 server.

  In an Intel® NetStructure™ SS7 board system, this is done using the following lines (assuming the SS7 server uses module ID 0x4d, the default value):

  REDIRECT 0xdf 0x4d * LIU/MTP2 status messages         

In an SIU based system, the command is:

REDIRECT 0xcf 0x4d * management messages 

• FORK_PROCESS commands that tell the GCTLOAD program to spawn child processes. For example, in an Intel® NetStructure™ SS7 ISA (PCCS6) board system, this is used to start the SSD module (or the SSDS module for Intel® NetStructure™ SS7 CompactPCI and PCI boards) that interfaces with the board, and to start the timer modules. On SIU host systems, it can be used to launch the RSI module that is responsible for the TCP/IP communication with the SIU units. A FORK_PROCESS command can also be used to automatically start S7_LOG, a message logging tool that displays system status messages.

  This tool is most useful when proving or debugging a configuration because it provides a visual indication of the PCM trunk status, the link status, and so on. However, it should not be used in parallel with Global Call SS7 because it would intercept some important messages. See Chapter 6, Troubleshooting for more information.

  On SIU systems, FORK_PROCESS should only be used to start the RSI module. It should not be used to issue the RSI link activation commands (RSICMD) because these are sent automatically by the SS7 server.

Note: The Intel® Dialogic SS7 software does not require any special FORK_PROCESS commands.

It is possible to configure the SS7 server to launch the GCTLOAD program automatically. See Section 3.4.2, Using DCM for General Intel® NetStructure™ SS7 Board Configuration for more information. In Intel® NetStructure™ SS7 board systems, it is necessary to add the -i option to the S7_MGT program in order to complete the startup sequence.

For example:

        FORK PROCESS S7 MGT -i0x4d    * notify Dialogic SS7 service 

Note: The module ID specified in the example shown should be that of the SS7 server.

Click here to contact Telecom Support Resources