To understand the configuration, let’s take below example of two signalling nodes integrated using SIGTRAN interface. One node will act as Server listening for connections, the peer node will act as client connecting to the server.
Below two main configuration files are used –
• /opt/aculab/cfg/ss7.cfg
This is the main configuration file where details on the SIGTRAN nodes such as Point code, SIGTRAN association details are configured. This file is passed as an argument while starting Aculab services.
• /opt/aculab/cfg/ gt_translate.cfg
This is the GT translation rule configuration file where GT mapping and translation rules are defined for each GT used in the application. The path is referenced inside ss7.cfg to load the GT rules defined.
Sample Aculab Server configuration
Sample SS7.cfg file
include "/opt/aculab/cfg/gt_translate.cfg" # to include the GT rules applicable
[SP]
NI = 2 # Network indicator.
LocalPC = 1000 # Local point code
[TCAP]
[EndTCAP]
[SCCP] # SCCP specific
xudt=never
GT_TABLE = Node1 # Use the rules defined in GT table under name Node1
[EndSCCP]
[M3UA] # M3UA specific
msg_burst=y
[ROUTING_KEY] # Routing key configuration
Routing_context = 3 # Routing key
[ADDRESS]
RemotePC = 2000 # Peer node point code
SI = 3 # Allow only SCCP traffic
[EndAddress]
[EndROUTING_KEY]
[IPSP_SERVER] # Indicates config is Server mode
NAME = Server-1 # Name of the server
Port = 6020
Local_ipaddresses = 10.0.20.30:6020 #IP address , listen port on which client connects
Routing_key = 3 # Routing key applicable for this association
encode_route_ctx=y
max_data_streams=16
[EndIPSP_SERVER]
[EndM3UA]
[EndSP]
Sample Aculab Client configuration
include "/opt/aculab/cfg/gt_translate.cfg"
[SP]
NI = 2 # Network indicator
LocalPC = 2000 # Local point code
[TCAP]
[EndTCAP]
[SCCP]
xudt=never
GT_TABLE=Table1
[EndSCCP]
[M3UA]
msg_burst=y
[ROUTING_KEY]
Routing_context = 3
[ADDRESS]
RemotePC = 1000 # Remote point code
SI = 3
[EndAddress]
[EndROUTING_KEY]
[IPSP_CLIENT] # Client node
Name = Client1 # Name of the client
port = 6020 # Remote server connection port
HOST = 10.0.20.35 # Remove server connection IP
Local_ipaddresses = 10.0.20.30:6020 # Local IP and port for application
ASP_id = 2 # Association ID
max_data_streams=16
Routing_key = 3 # Routing context for this association
encode_route_ctx=n
rfc3332_compat=y
heartbeat=y # Enable heartbeat messages
t_beat=1
auto_activate=y # On startup or link down , should client retry connection
[EndIPSP_CLIENT]
[EndM3UA]
[EndSP]
Sample gt_translate.cfg configuration file
GT Tables are defined within GT_Table tags . Multiple GT Tables can be defined using similar GT table tags.
[GT_Table]
Name = Table1
tt = 0
nai = 4
np = 1
es = bcd # binary coded decimal, match on es=1 and es=2
[Rule] # For each GT translation one rule to be included
gtdigits =919000012345 # GT address
[ROUTE_GT]
# ssn = 8 # Sub system number associated with GT
destination=1000 # Destination point code to route if GT matches
[EndROUTE_GT]
[EndRule]
[Rule]
gtdigits=default # Default rule which applies if no other rule matches
[Route_GT]
# tt = 0
# loadshare = auto
destination = 2000 # send to RemotePC bbbbb
# backup_destination = 5000
[EndRoute_GT]
[EndRule]
[EndGT_Table]