Overview: Dialogic provides sample applications that demonstrate the basic functions for implementing an IS-41 based Message Center for SMS messages. Running the IS-41 sample requires 2 servers, one for the SMS sending application and one for the SMS receiving application. This article describes the configuration settings needed and provides sample config.txt and system.txt files for both the ISTR (receiver) and ISTU (sender) servers.. This example uses a Dialogic® Distributed Signaling Interface (DSI) SPCI4 Network Interface Board for the ISTU sending application and a Dialogic® DSI SS7HD Network Interface Board for the ISTR receiving application. Note that you will need to modify all the supplied sample configuration files to match your specific configuration and requirements. ISTU Sending server config.txt system.txt ISTR Receiving server config.txt system.txt Config.txt Description This is the file loaded when the gctload environment is started. The following is a brief explanation of the configuration settings most relevant to the running of the IS-41 applications. SEPTELPCI_BOARD 0 0x0043 ss7.dc3 MTP2 – loads the SS7 driver on the Dialogic DSI SPCI4 Network Interface Board and runs the MTP2 protocol on the board. SS7_BOARD 0 SS7HDP 0x0042 ss7.dc4 MTP2 – loads the SS7 driver for the Dialogic DSI SS7HD Network Interface Board and also runs the MTP2 protocol on the board. Note the flag settings of 0x0043 and 0x0042 which are used to define clocking synchronization between the servers. LIU_CONFIG 0 2 4 2 4 1 – Defines the line interface unit into which the T1 cable is plugged. Parameters 3 – 6 (liu_type, line_code, frame_format, crc_mode) define the signaling trunk parameters for T1 operation. These parameters are identical on both servers. MTP_CONFIG 0 0 0x0f00 – Like LIU_CONFIG, the options flags in the MTP_CONFIG line define the trunk as T1. This line is identical in both configurations. MTP_LINK 0 0 0 0 0 0 3 24 0x0006 – Identifies that the T1 cable is plugged into the last LIU on the Dialogic® DSI SS7 Board and that channel 24 carries SS7 messgaes. The LIU used is the only difference between the config.txt files. MTP_ROUTE 2 0 0x0008 – This is configured to route signaling messages received to the IS-41 protocol layer as specified via the 0x0008 parameter. Note: the parameter value could contain an 'anded' value if signaling messages are to be delivered to multiple protocol layers. SCCP_CONFIG 1 8 0x0ff2 1 – The options value of 0x0ff2 is for demo applications using a T1 trunk. A detailed breakdown of this option flag can be found in the Dialogic® DSI SCCP Protocol Developer's Manual. The last parameter, 1, brings the SCCP subsystem into a running state. The sample application will not function without the subsystem running. SCCP_SSR 1 LSS 0x0a 0x2d 0 IS41 – This line both identifies the application id of 0x2d as well as IS41 as the protocol used above the SCCP layer. SCCP_SSR 2 RSP 2 0 0 and SCCP_SSR 3 RSS 2 0x0a 0 – It is important to make sure the remote Service Point Code values are properly set to match the point code values at the corresponding servers. Failure to properly set the point codes will result in routing failure messages. More in-depth information regarding the configuration settings used in the IS-41 sample applications can be found in the Dialogic® DSI SS7HD Programmer’s Manual and the relevant signaling protocols developer manuals. System.txt Description The system.txt file is used to identify the sub systems to be loaded and where they will run, either on the host server or on the DSI SS7 Board. Normally, all protocols are run on the host server for large scale signaling solutions. In addition to the s7_mgt and s7_log modules, the system.txt file identifies the IS-41 application IDs; these are the same for both the ISTR and ISTU applications. LOCAL 0x2d * ISTU/ISTR application - entry defining the Application ID. The protocol layers to be run on the host server are then forked or started. These protocols layers are:
FORK_PROCESS MTP_NT.exe -t FORK_PROCESS sccp_nt.exe -t FORK_PROCESS tcp_nt.exe -t FORK_PROCESS is41_nt.exe –t
Product List The techniques defined apply to Dialogic® Distribuited Signaling Interface (DSI) SS7 Boards, including Dialogic® DSI SS7HDC (compact PCI), DSI SS7HDP (PCI), SPCI2 and SPCI4 Network Interface Boards. Glossary of Acronyms / Terms SMS – Short Message Service SMSC – Short Message Service Center known as a Message Center in IS-41 environments. Related Documentation Dialogic® DSI SS7HD Programmer's Manual Dialogic® DSI SCCP Programmer’s Manual Dialogic® DSI MTP Programmer’s Manual
Share