Dialogic DSI SS7MD manual Generating the system.txt Configuration File

4 Dialogic® DSI SS7MD Board Configuration and Operation

NUM_MSGS 1000 * Number of standard size messages

*

*Optional Modules that run on the host:

* LOCAL 0x23	* ISUP module
* LOCAL 0x4a	* TUP module
* LOCAL 0x33	* SCCP module
* LOCAL 0x14	* TCAP module
* LOCAL 0x22	* MTP3 module
*
*

*Redirection of status indications:

REDIRECT 0xdf 0x2d * LIU/MTP2 status messages -> upe REDIRECT 0xef 0x2d * Other indications -> upe

*Start-up all local tasks:

*

FORK_PROCESS ./ssdm FORK_PROCESS ./tim_lnx FORK_PROCESS ./tick_lnx FORK_PROCESS ./s7_mgt FORK_PROCESS ./upe

*

********************************************************************************

4.4.2Generating the system.txt Configuration File

This section describes the procedure for generating a system.txt configuration file and details any operating system specific differences in behavior among the development packages.

First, the file must contain LOCAL declarations for all modules that are to run on the host computer. At a minimum, this must include the ssdm module and the timer module. Hence, the following declarations must exist:

LOCAL	0x20	*	ssdm - Board interface task
LOCAL	0x00	*	tim_xxx - Timer task

LOCAL declarations are also required for any optional modules running on the host. Typically, this includes the s7_mgt protocol configuration utility and the user's own application module. It may also include any host- based protocol modules and the s7_log utility. For example:

LOCAL	0xcf	* s7_mgt -		Management/config task
LOCAL	0x2d	* upe - Example user part task
LOCAL	0x3d	*	s7_log -	Prints messages to screen/file
LOCAL	0x22	*	MTP3 module

Once all the LOCAL declarations are in place, REDIRECT commands should be added for all modules that are logically running on the board so that any messages destined for these modules are transported via the ssdm module (module_id = 0x20).

The following REDIRECT commands are always required:

REDIRECT	0x71	0x20	* MTP2 module_id
REDIRECT	0x10	0x20	*	LIU module
REDIRECT	0x8e 0x20		*	onboard management module

If ATM support is required, then the following REDIRECT commands are also required:

REDIRECT	0x31	0x20 *	ATM Module
REDIRECT	0x41	0x20 *	Q.SAAL Module

Having ensured that all modules running on the board are accessible, it is then necessary to ensure that any status indications issued from the board successfully arrive at a module running on the host. If this does not happen, the system quickly runs out of available messages for inter-process communication.

Two module_ids (0xdf and 0xef) require redirection to a suitable process running on the host; initially these messages should be redirected to the s7_log utility that prints out a line for each message received. Ultimately, the user's own application should deal with these notifications.

REDIRECT	0xdf	0x3d*	LIU/MTP2 status messages ->	s7_log
REDIRECT	0xef	0x3d*	Other indications -> s7_log

30