Host SIU

Installation Guide

__________________

October 2013
Contents
1. Introduction ........................................................................................................................ 3
2. Concepts ................................................................................................................................ 4
2.1. Environment................................................................................................................. 4
2.2. Resilient Architecture ............................................................................................. 4
2.3. Dual MTP3 Concepts ................................................................................................ 4
2.4. Dual M3UA Concepts................................................................................................ 4
2.5. Dual SCCP Concepts ................................................................................................. 4
3. Installation........................................................................................................................... 5
3.1. Installing Dialogic® DSI ........................................................................................ 5
3.2. Installing Host SIU ................................................................................................... 5
4. Configuration and Operation ...................................................................................... 6
4.1. IP Network Configuration ..................................................................................... 6
4.2. MTP3/M3UA Configuration................................................................................... 6
4.3. SCCP Configuration .................................................................................................. 7
4.4. DTS Configuration ..................................................................................................... 7
4.5. SIU Service Console Configuration .................................................................. 7
4.6. Inter-chassis Communication Configuration .............................................. 8
4.7. Host Links Configuration ....................................................................................... 9
5. Example Configuration Files...................................................................................... 10
5.1. Example system.txt System Configuration file for Host A ................. 10
5.2. Example system.txt System Configuration file for Host B ................. 12
5.3. Example config.txt Protocol Configuration File for Host A ................ 14
5.4. Example config.txt Protocol Configuration File for Host B ................ 16
References ..................................................................................................................................... 18
1. Introduction

Host Signaling Interface Unit (Host SIU) is supplementary software, providing

connectivity between single or dual instance of Dialogic® DSI Protocol Stack and
multiple distributed application server. Host SIU provides Distribution Transaction
Server capabilities, supports DSI Protocol Stack run-time configuration and
comprehensive tracing facilities. The Host SIU can enable System Integrator to
deploy signaling solution quickly and cost-effectively using his own hardware
platform and Dialogic® DSI Protocol Stack. Host SIU does not depend on low-level
protocols and works with both TDM and SIGTRAN links .

Figure 1. System Architecture

2. Concepts

2.1. Environment

SIU Host is designed to work as an ordinary component of DSI Software

Environment. For basic concepts like Modules, Messages and System
Initialization see [1], chapter 2.

2.2. Resilient Architecture

For production system it is recommended that two different hardware
components (server etc.) are used in order to achieve resilient Active-Active
configuration. Implementing an SS7 node over more than one chassis isolates
one hardware protocol engine from the failure of another, allowing the overall
system to continue service following a complete failure of one component or
chassis. SS7 signaling takes a 2N approach and provides architecture for
splitting a point code over two active SS7 protocol engines. This allows links
in SS7 link sets to be spread between two separate chassis.
It is also recommended to utilize SIGTRAN resilience features such as multi-
homing, to protect each chassis from loose connection with SG/IPSP in case of
physical channel failure.
Furthermore, chassis operation system’s features should be utilized to provide
network connectivity reliability (like NIC teaming/bonding).

2.3. Dual MTP3 Concepts

When MTP3 is used as a lower stack level in dual chassis configuration, it is
required to provide state information sharing and messages exchanging
between instances of MTP3 acting as a single point code. This is implemented
by so called inter-chassis link. Under normal condition, each MTP3 instance
sends messages to the network through SS7 links connected directly to this
MTP3 instance. But in case of SS7 link failure between MTP3 and the network,
the instance reroute all the message received from upper level to another
MTP3 instance (which is on another chassis) through inter-chassis link,
providing system survival.

2.4. Dual M3UA Concepts

With M3UA things become easier. Resilient MTP Management (RMM) module
allows outbound messages to be forward to the partner M3UA module via RSI
link, providing resilience if the local route become unavailable.

2.5. Dual SCCP Concepts

SCCP instances on both chassis behave as the same point code. Upper and
lower protocol stack levels can exchange messages through any of SCCP
instance. SCCP implement broadcasting messages to exchange subsystem
status information and appropriate settings must be done to allow this
mechanism work in a correct way.
3. Installation

3.1. Installing Dialogic® DSI

Install Dialogic® Development Package as described in [1] chapter 3. Installation
must be done on both chassis. Later in this manual it’s assumed that Development
package is installed into /opt/DSI (for Linux) or C:\DSI (for Windows).

3.2. Installing Host SIU

The following steps should be done in order to add Host SIU support to installed
Development Package:
1) Copy dts.exe binary into DSI/HSTBIN folder.
2) Copy suisc.exe binary into DSI folder.
3) Create siudata subfolder inside DSI folder:
cd /opt/DSI
mkdir siudata

4) Copy Host SIU license file into DSI/siudata folder.

4. Configuration and Operation

4.1. IP Network Configuration

To achieve SIGTRAN link tolerance to IP network failure it is recommended to
implement multi-homing. Each chassis should be connected with the remote peer via
two different IP cores using separate NIC for each core and separate local IP
address. Static routing settings should be done if chassis and remote peer are not in
the same network.

Example of static routing configuration (MS Windows):

route ADD –p <Peer_IP1_Core1> MASK 255.255.255.0 <GW_Core1>

route ADD –p <Peer_IP2_Core1> MASK 255.255.255.0 <GW_Core1>
route ADD –p <Peer_IP1_Core2> MASK 255.255.255.0 <GW_Core2>
route ADD –p <Peer_IP2_Core2> MASK 255.255.255.0 <GW_Core2>

In case when any peer IP addresses can be accessible through any of IP core,
additional routing settings are recommended:

route ADD –p <Peer_IP1_Core1> MASK 255.255.255.0 <GW_Core2> METRIC 2

route ADD –p <Peer_IP2_Core1> MASK 255.255.255.0 <GW_Core2> METRIC 2
route ADD –p <Peer_IP1_Core2> MASK 255.255.255.0 <GW_Core1> METRIC 2
route ADD –p <Peer_IP2_Core2> MASK 255.255.255.0 <GW_Core1> METRIC 2

4.2. MTP3/M3UA Configuration

MTP3/M3UA configuration should be done as it explained in [1] chapter 8.4 and 8.15.
Pay attention, that when use MTP3, inter-chassis link set and backup route should be
configured.
When use M3UA, dual-resilient configuration system setting must be done as
explained in [1] chapter 8.15. Also use multi-homing when possible.

Example of System Settings on Host A:

CNSYS:IPADDR=LocalIP1,IPADDR2=LocalIP2,PER=0,DUAL=A,AUTOACT=Y;

Example of System Settings on Host B:

CNSYS:IPADDR=LocalIP1,IPADDR2=LocalIP2,PER=0,DUAL=B,AUTOACT=Y;

Example of SIGTRAN link configuration with multi-homing feature:

SNSLI:SNLINK=1,IPADDR=Peer_IP1_Core1,IPADDR2=Peer_IP1_Core2,…
4.3. SCCP Configuration
Do SCCP level configuration as explained in [1] chapter 8.8 (SCCP Configuration
Commands). To achieve dual-resilience between SCCP instances, apply the next
instructions:
- Use <sccp_instance> parameter and set it to unique value on each chassis
- Set SCPF_SMB bit in <options> parameter.
- Set <partner_id> parameter.
- Use REDIRECT statement to route messages intended for partner SCCP to
partner chassis (see 4.6).

Example of SCCP Configuration Command on Host A:

SCCP_CONFIG 200 0x08 0x102 0x00000000 0x53 0

Example of SCCP Configuration Command on Host B:

SCCP_CONFIG 200 0x08 0x102 0x00000000 0x43 1

4.4. DTS Configuration

DTS module does not require any configuration commends but require environment
settings in system.txt file only. Module ID must be allocated and DTS execution
command must be present. Recommended DTS module ID is 0x30.

Example of DTS settings in system.txt:

LOCAL 0x30 * DTS

FORK_PROCESS ./HSTBIN/dts.exe -m0x30

4.5. SIU Service Console Configuration

SIU Service Console module does not require any configuration commends but
require environment settings in system.txt file only. Module ID must be allocated and
DTS execution command must be present. Recommended SIU Service Console
module ID is 0xed.

Example of DTS settings in system.txt:

LOCAL 0xed * SIUSC

FORK_PROCESS siusc.exe
4.6. Inter-chassis Communication Configuration
Inter-chassis communication is provided by RSI links. The link uses TCP/IP sockets,
one side acting as a server, the other as a client. Configuration of RSI links should be
done in system.txt.

Example of Inter-chassis configuration on Host A:

LOCAL 0xc0 * RSI for Remote chassis

REDIRECT 0x52 0xc0 * RMM to unit B
REDIRECT 0x12 0xc0 * M3UA to unit B
REDIRECT 0x53 0xc0 * SCCP to unit B
REDIRECT 0x42 0x32 * RMM from unit B
REDIRECT 0x02 0xd2 * M3UA from unit B
REDIRECT 0x43 0x33 * SCCP from unit B
FORK_PROCESS rsi.exe -r./rsi_lnk.exe -l1 -m0xc0 -nl
FORK_PROCESS rsicmd.exe 0 0x32 0 <Partner_IP> 9064 0xc0

Example of Inter-chassis configuration on Host A:

LOCAL 0xc0 * RSI for Remote chassis

REDIRECT 0x42 0xc0 * RMM to unit A
REDIRECT 0x02 0xc0 * M3UA to unit A
REDIRECT 0x43 0xc0 * SCCP to unit A
REDIRECT 0x52 0x32 * RMM from unit A
REDIRECT 0x12 0xd2 * M3UA from unit A
REDIRECT 0x53 0x33 * SCCP from unit A
FORK_PROCESS rsi.exe -r./rsi_lnk.exe -l1 -m0xc0 -nl
FORK_PROCESS rsicmd.exe 0 0x32 1 <Local_IP> 9064 0xc0
4.7. Host Links Configuration
Communication with application hosts is provided by RSI links. Amount of external
application hosts able to interact with SIU is equal to number of configured hosts RSI
links.

Example of host link configuration:

LOCAL 0xb0 * RSI for Hosts

REDIRECT 0x0d 0xb0 * Application 0

REDIRECT 0x1d 0xb0 * Application 1
REDIRECT 0x2d 0xb0 * Application 2
REDIRECT 0x3d 0xb0 * Application 3
REDIRECT 0x4d 0xb0 * Application 4
REDIRECT 0x5d 0xb0 * Application 5
REDIRECT 0x6d 0xb0 * Application 6
REDIRECT 0x7d 0xb0 * Application 7
REDIRECT 0x8d 0xb0 * Application 8
REDIRECT 0x9d 0xb0 * Application 9
REDIRECT 0xad 0xb0 * Application 10
REDIRECT 0xbd 0xb0 * Application 11
REDIRECT 0xcd 0xb0 * Application 12
REDIRECT 0xdd 0xb0 * Application 13

FORK_PROCESS rsi.exe -r./rsi_lnk.exe -l1 -m0xb0 -nl

FORK_PROCESS rsicmd.exe 0 0x30 1 <LocalIP> 9000 0xb0
FORK_PROCESS rsicmd.exe 1 0x30 1 <LocalIP> 9001 0xb0
FORK_PROCESS rsicmd.exe 2 0x30 1 <LocalIP> 9002 0xb0
FORK_PROCESS rsicmd.exe 3 0x30 1 <LocalIP> 9003 0xb0
FORK_PROCESS rsicmd.exe 4 0x30 1 <LocalIP> 9004 0xb0
FORK_PROCESS rsicmd.exe 5 0x30 1 <LocalIP> 9005 0xb0
FORK_PROCESS rsicmd.exe 6 0x30 1 <LocalIP> 9006 0xb0
FORK_PROCESS rsicmd.exe 7 0x30 1 <LocalIP> 9007 0xb0
FORK_PROCESS rsicmd.exe 8 0x30 1 <LocalIP> 9008 0xb0
FORK_PROCESS rsicmd.exe 9 0x30 1 <LocalIP> 9009 0xb0
FORK_PROCESS rsicmd.exe 10 0x30 1 <LocalIP> 9010 0xb0
FORK_PROCESS rsicmd.exe 11 0x30 1 <LocalIP> 9011 0xb0
FORK_PROCESS rsicmd.exe 12 0x30 1 <LocalIP> 9012 0xb0
FORK_PROCESS rsicmd.exe 13 0x30 1 <LocalIP> 9013 0xb0
FORK_PROCESS rsicmd.exe 14 0x30 1 <LocalIP> 9014 0xb0
FORK_PROCESS rsicmd.exe 15 0x30 1 <LocalIP> 9015 0xb0
5. Example Configuration Files

5.1. Example system.txt System Configuration file for Host A

********************************************************************
*
* Example System Configuration file for use with Host SIU. Host A.
*
********************************************************************
*
* Essential modules running on host:
*
LOCAL 0x00 * tim_nt - Timer task
LOCAL 0xcf * s7_mgt - Management/config task
LOCAL 0xef * s7_log - Display and logging utility
LOCAL 0x32 * RMM
LOCAL 0xb0 * RSI for Hosts
LOCAL 0xc0 * RSI for Remote SGW
LOCAL 0xfd * rsicmd
LOCAL 0xd0 * SCTPD module
LOCAL 0xd1 * SCTP module
LOCAL 0xd2 * M3UA module
LOCAL 0x33 * SCCP / SCCP-capable User App
LOCAL 0x30 * DTS
LOCAL 0xed * SIUSC

REDIRECT 0xdf 0xef

REDIRECT 0x22 0xd2 * MTP3 -> M3UA
REDIRECT 0xc2 0xd2 * MBM -> M3UA
*
REDIRECT 0x52 0xc0 * RMM to unit B
REDIRECT 0x12 0xc0 * M3UA to unit B
REDIRECT 0x53 0xc0 * SCCP to unit B
*
REDIRECT 0x42 0x32 * RMM from unit B
REDIRECT 0x02 0xd2 * M3UA from unit B
REDIRECT 0x43 0x33 * SCCP from unit B
*
REDIRECT 0x0d 0xb0 * Application 0
REDIRECT 0x1d 0xb0 * Application 1
REDIRECT 0x2d 0xb0 * Application 2
REDIRECT 0x3d 0xb0 * Application 3
REDIRECT 0x4d 0xb0 * Application 4
REDIRECT 0x5d 0xb0 * Application 5
REDIRECT 0x6d 0xb0 * Application 6
REDIRECT 0x7d 0xb0 * Application 7
REDIRECT 0x8d 0xb0 * Application 8
REDIRECT 0x9d 0xb0 * Application 9
REDIRECT 0xad 0xb0 * Application 10
REDIRECT 0xbd 0xb0 * Application 11
REDIRECT 0xcd 0xb0 * Application 12
REDIRECT 0xdd 0xb0 * Application 13
*
*
NUM_MSGS 5000
NUM_LMSGS 5000
*
*
FORK_PROCESS tim.exe
FORK_PROCESS tick.exe
FORK_PROCESS s7_log.exe
FORK_PROCESS s7_mgt.exe
FORK_PROCESS sctp.exe
FORK_PROCESS sctpd.exe
FORK_PROCESS siusc.exe
FORK_PROCESS ./HSTBIN/m3ua.exe
FORK_PROCESS ./HSTBIN/sccp.exe
FORK_PROCESS ./HSTBIN/dts.exe -m0x30
FORK_PROCESS rmm.exe -m0x32 -d
*
FORK_PROCESS rsi.exe -r./rsi_lnk.exe -l1 -m0xc0 -nl
FORK_PROCESS rsicmd.exe 0 0x32 0 <IP address of Host B> 9064 0xc0
*
FORK_PROCESS rsi.exe -r./rsi_lnk.exe -l1 -m0xb0 -nl
FORK_PROCESS rsicmd.exe 0 0x30 1 <Local IP> 9000 0xb0
FORK_PROCESS rsicmd.exe 1 0x30 1 <Local IP> 9001 0xb0
FORK_PROCESS rsicmd.exe 2 0x30 1 <Local IP> 9002 0xb0
FORK_PROCESS rsicmd.exe 3 0x30 1 <Local IP> 9003 0xb0
FORK_PROCESS rsicmd.exe 4 0x30 1 <Local IP> 9004 0xb0
FORK_PROCESS rsicmd.exe 5 0x30 1 <Local IP> 9005 0xb0
FORK_PROCESS rsicmd.exe 6 0x30 1 <Local IP> 9006 0xb0
FORK_PROCESS rsicmd.exe 7 0x30 1 <Local IP> 9007 0xb0
FORK_PROCESS rsicmd.exe 8 0x30 1 <Local IP> 9008 0xb0
FORK_PROCESS rsicmd.exe 9 0x30 1 <Local IP> 9009 0xb0
FORK_PROCESS rsicmd.exe 10 0x30 1 <Local IP> 9010 0xb0
FORK_PROCESS rsicmd.exe 11 0x30 1 <Local IP> 9011 0xb0
FORK_PROCESS rsicmd.exe 12 0x30 1 <Local IP> 9012 0xb0
FORK_PROCESS rsicmd.exe 13 0x30 1 <Local IP> 9013 0xb0
FORK_PROCESS rsicmd.exe 14 0x30 1 <Local IP> 9014 0xb0
FORK_PROCESS rsicmd.exe 15 0x30 1 <Local IP> 9015 0xb0
*
********************************************************************************
 5.2. Example system.txt System Configuration file for Host B

********************************************************************
*
* Example System Configuration file for use with Host SIU. Host B.
*
********************************************************************
*
* Essential modules running on host:
*
LOCAL 0x00 * tim_nt - Timer task
LOCAL 0xcf * s7_mgt - Management/config task
LOCAL 0xef * s7_log - Display and logging utility
LOCAL 0x32 * RMM
LOCAL 0xb0 * RSI for Hosts
LOCAL 0xc0 * RSI for Remote SGW
LOCAL 0xfd * rsicmd
LOCAL 0xd0 * SCTPD module
LOCAL 0xd1 * SCTP module
LOCAL 0xd2 * M3UA module
LOCAL 0x33 * SCCP / SCCP-capable User App
LOCAL 0x30 * DTS
LOCAL 0xed * SIUSC

REDIRECT 0xdf 0xef

REDIRECT 0x22 0xd2 * MTP3 -> M3UA
REDIRECT 0xc2 0xd2 * MBM -> M3UA
*
REDIRECT 0x42 0xc0 * RMM to unit B
REDIRECT 0x02 0xc0 * M3UA to unit B
REDIRECT 0x43 0xc0 * SCCP to unit B
*
REDIRECT 0x52 0x32 * RMM from unit B
REDIRECT 0x12 0xd2 * M3UA from unit B
REDIRECT 0x53 0x33 * SCCP from unit B
*
REDIRECT 0x0d 0xb0 * Application 0
REDIRECT 0x1d 0xb0 * Application 1
REDIRECT 0x2d 0xb0 * Application 2
REDIRECT 0x3d 0xb0 * Application 3
REDIRECT 0x4d 0xb0 * Application 4
REDIRECT 0x5d 0xb0 * Application 5
REDIRECT 0x6d 0xb0 * Application 6
REDIRECT 0x7d 0xb0 * Application 7
REDIRECT 0x8d 0xb0 * Application 8
REDIRECT 0x9d 0xb0 * Application 9
REDIRECT 0xad 0xb0 * Application 10
REDIRECT 0xbd 0xb0 * Application 11
REDIRECT 0xcd 0xb0 * Application 12
REDIRECT 0xdd 0xb0 * Application 13
*
*
NUM_MSGS 5000
NUM_LMSGS 5000
*
*
FORK_PROCESS tim.exe
FORK_PROCESS tick.exe
FORK_PROCESS s7_log.exe
FORK_PROCESS s7_mgt.exe
FORK_PROCESS sctp.exe
FORK_PROCESS sctpd.exe
FORK_PROCESS siusc.exe
FORK_PROCESS ./HSTBIN/m3ua.exe
FORK_PROCESS ./HSTBIN/sccp.exe
FORK_PROCESS ./HSTBIN/dts.exe -m0x30
FORK_PROCESS rmm.exe -m0x32 -d
*
FORK_PROCESS rsi.exe -r./rsi_lnk.exe -l1 -m0xc0 -nl
FORK_PROCESS rsicmd.exe 0 0x32 1 <Local IP> 9064 0xc0
*
FORK_PROCESS rsi.exe -r./rsi_lnk.exe -l1 -m0xb0 -nl
FORK_PROCESS rsicmd.exe 0 0x30 1 <Local IP> 9000 0xb0
FORK_PROCESS rsicmd.exe 1 0x30 1 <Local IP> 9001 0xb0
FORK_PROCESS rsicmd.exe 2 0x30 1 <Local IP> 9002 0xb0
FORK_PROCESS rsicmd.exe 3 0x30 1 <Local IP> 9003 0xb0
FORK_PROCESS rsicmd.exe 4 0x30 1 <Local IP> 9004 0xb0
FORK_PROCESS rsicmd.exe 5 0x30 1 <Local IP> 9005 0xb0
FORK_PROCESS rsicmd.exe 6 0x30 1 <Local IP> 9006 0xb0
FORK_PROCESS rsicmd.exe 7 0x30 1 <Local IP> 9007 0xb0
FORK_PROCESS rsicmd.exe 8 0x30 1 <Local IP> 9008 0xb0
FORK_PROCESS rsicmd.exe 9 0x30 1 <Local IP> 9009 0xb0
FORK_PROCESS rsicmd.exe 10 0x30 1 <Local IP> 9010 0xb0
FORK_PROCESS rsicmd.exe 11 0x30 1 <Local IP> 9011 0xb0
FORK_PROCESS rsicmd.exe 12 0x30 1 <Local IP> 9012 0xb0
FORK_PROCESS rsicmd.exe 13 0x30 1 <Local IP> 9013 0xb0
FORK_PROCESS rsicmd.exe 14 0x30 1 <Local IP> 9014 0xb0
FORK_PROCESS rsicmd.exe 15 0x30 1 <Local IP> 9015 0xb0
*
********************************************************************************
 5.3. Example config.txt Protocol Configuration File for Host A

********************************************************************************
*
* Example Protocol Configuration File (config.txt)
*
********************************************************************************
*
*
CNSYS:IPADDR=xx1.xx1.xx1.xx1,IPADDR2=xx2.xx2.xx2.xx2,PER=0,DUAL=A,AUTOACT=Y;
*
* -------------------------------------
* SNSLI - SIGTRAN Signaling Link Initiate
*
SNSLI:SNLINK=1,IPADDR=ww1.ww1.ww1.ww1,IPADDR2=ww2.ww2.ww2.ww2,HIPADDR=yy1.yy1.yy1.yy1,HIPADDR
2=yy2.yy2.yy2.yy2,HPORT=xxxx,PPORT=xxxx,SNEND=C,SNTYPE=M3UA,M3UAHBT=Y;
SNSLI:SNLINK=2,IPADDR=zz1.zz1.zz1.zz1,IPADDR2=zz2.zz2.zz2.zz2,HIPADDR=yy2.yy2.yy2.yy2,HIPADDR
2=yy1.yy1.yy1.yy1,HPORT=xxxx,PPORT=xxxx,SNEND=C,SNTYPE=M3UA,M3UAHBT=Y;
*
* -------------------------------------
* SNAPI - SIGTRAN Local Application Server Initiate
*
SNAPI:AS=1,OPC=200,RC=1,TRMD=ls;
*
*--------------------------------------
* SNRAI - SIGTRAN Remote Application Server Initiate
*
SNRAI:RAS=1,DPC=100;
*
* -------------------------------------
* SNALI - SIGTRAN Application Server List Initiate
*
SNALI:SNAL=1,RAS=1,SNLINK=1;
SNALI:SNAL=2,RAS=1,SNLINK=2;
*
*
* -------------------------------------
* SNLBI - SIGTRAN Application Server Bind Initiate
*
SNLBI:SNLB=1,AS=1,RAS=1;
*
*=====================================================================
*
* SCCP
*
*=====================================================================
*
* Set SCCP operating parameters :
* SCCP_CONFIG <local_spc> <ssf> <options>
*
SCCP_CONFIG 200 0x0c 0x0102 0x00000001 0x53 0
*
* Define SCCP Remote signalling points :
* SCCP_SSR [<nc_id>] <ssr_id> RSP <remote_spc> <rsp_flags> [<pc_mask>]
*
SCCP_SSR 1 RSP 100 0x00 0x00
*
* Define all local sub-systems :
* SCCP_SSR [<nc_id>] <ssr_id> LSS <local_ssn> <module_id> <lss_flags>
* <protocol>
*
SCCP_SSR 100 LSS 0x08 0x30 0x0000 SCCP
*
* Define all remote sub-systems :
* SCCP_SSR [<nc_id>] <ssr_id> RSS <remote_spc> <remote_ssn> <rss_flags>
*
SCCP_SSR 201 RSS 100 0x08 0x00

*
* Define Global Title pattern
* SCCP_GTT_PATTERN [<NC_id>] <pattern_id> <addr_indicator> <pc> <ssn> <global_title>
[<gtai_pattern>]
*
*
* Define Global Title Address
* SCCP_GTT_ADDRESS [<NC_id>] <address_id> <addr_indicator> <pc> <ssn> <global_title>
[<gtai_replacement>]
*
*
* Add entry in GTT table
* SCCP_GTT [<nc_id> ]<pattern_id> <mask> <primary_address_id> [<backup_address_id>]
*
*
********************************************************************************
 5.4. Example config.txt Protocol Configuration File for Host B

********************************************************************************
*
* Example Protocol Configuration File (config.txt)
*
********************************************************************************
*
*
CNSYS:IPADDR=yy1.yy1.yy1.yy1,IPADDR2=yy2.yy2.yy2.yy2,PER=0,DUAL=B,AUTOACT=Y;
*
* -------------------------------------
* SNSLI - SIGTRAN Signaling Link Initiate
*
SNSLI:SNLINK=1,IPADDR=ww1.ww1.ww1.ww1,IPADDR2=ww2.ww2.ww2.ww2,HIPADDR=yy1.yy1.yy1.yy1,HIPADDR
2=yy2.yy2.yy2.yy2,HPORT=xxxx,PPORT=xxxx,SNEND=C,SNTYPE=M3UA,M3UAHBT=Y;
SNSLI:SNLINK=2,IPADDR=zz1.zz1.zz1.zz1,IPADDR2=zz2.zz2.zz2.zz2,HIPADDR=yy2.yy2.yy2.yy2,HIPADDR
2=yy1.yy1.yy1.yy1,HPORT=xxxx,PPORT=xxxx,SNEND=C,SNTYPE=M3UA,M3UAHBT=Y;
*
* -------------------------------------
* SNAPI - SIGTRAN Local Application Server Initiate
*
SNAPI:AS=1,OPC=200,RC=1,TRMD=ls;
*
*--------------------------------------
* SNRAI - SIGTRAN Remote Application Server Initiate
*
SNRAI:RAS=1,DPC=100;
*
* -------------------------------------
* SNALI - SIGTRAN Application Server List Initiate
*
SNALI:SNAL=1,RAS=1,SNLINK=1;
SNALI:SNAL=2,RAS=1,SNLINK=2;
*
*
* -------------------------------------
* SNLBI - SIGTRAN Application Server Bind Initiate
*
SNLBI:SNLB=1,AS=1,RAS=1;
*
*=====================================================================
*
* SCCP
*
*=====================================================================
*
* Set SCCP operating parameters :
* SCCP_CONFIG <local_spc> <ssf> <options>
*
SCCP_CONFIG 200 0x0c 0x0102 0x00000001 0x43 1
*
* Define SCCP Remote signalling points :
* SCCP_SSR [<nc_id>] <ssr_id> RSP <remote_spc> <rsp_flags> [<pc_mask>]
*
SCCP_SSR 1 RSP 100 0x00 0x00
*
* Define all local sub-systems :
* SCCP_SSR [<nc_id>] <ssr_id> LSS <local_ssn> <module_id> <lss_flags>
* <protocol>
*
SCCP_SSR 100 LSS 0x08 0x30 0x0000 SCCP
*
* Define all remote sub-systems :
* SCCP_SSR [<nc_id>] <ssr_id> RSS <remote_spc> <remote_ssn> <rss_flags>
*
SCCP_SSR 201 RSS 100 0x08 0x00

*
* Define Global Title pattern
* SCCP_GTT_PATTERN [<NC_id>] <pattern_id> <addr_indicator> <pc> <ssn> <global_title>
[<gtai_pattern>]
*
*
* Define Global Title Address
* SCCP_GTT_ADDRESS [<NC_id>] <address_id> <addr_indicator> <pc> <ssn> <global_title>
[<gtai_replacement>]
*
*
* Add entry in GTT table
* SCCP_GTT [<nc_id> ]<pattern_id> <mask> <primary_address_id> [<backup_address_id>]
*
*
********************************************************************************
References

[1] Dialogic® Distributed Signaling Interface Components – Software

Environment Programmer’s Manual
[2] DTS User Guide