HPSG - Sip 1.0

NextGen 1.
0
HP Signaling Gateway
Installation and Configuration Guide
Document Version:
Document Status:
Document Release Date:
Template Version:
Template Date:
1.0
APPROVED
Sep 2004
1.5
06/10/2003
Copyright 2004 by LogicaCMG Wireless Networks

All rights reserved. This document is protected by copyright law and may not be reprinted, reproduced, or utilised in whole or in part by any
electronic, mechanical, or other means without the prior written consent of LogicaCMG Wireless Networks (LogicaCMG).
The information in this document is provided on an as is basis and is subject to change without further notice and cannot be construed as a
commitment by LogicaCMG. Although every precaution has been taken in the preparation of this document, LogicaCMG assumes no
responsibility or liability for any errors or omissions whatsoever that may appear in this document. Neither is any liability assumed for damages
resulting from the use of the information contained herein.
The products mentioned in this document are identified by the names, trademarks, service marks and logos of their respective companies or
organisations and may not be used in any advertising or publicity or in any other way whatsoever without the prior written consent of those
companies or organisations.
Table of Contents
Introduction...........................................................................................................3
HPSG Stack Architecture.....................................................................................4
HPSG Configuration.............................................................................................5
3.1
Introduction........................................................................................................................... 5
3.2
Example configuration.......................................................................................................... 5
3.3
Configuring HPSG................................................................................................................ 7
3.3.1
Create SS7 Platform.............................................................................................. 8
3.3.2
SUA Configuration............................................................................................... 12
3.3.3
SS7 Configuration............................................................................................... 13
3.3.4
GTT Configuration............................................................................................... 14
3.3.5
Routing key Configuration...................................................................................15
3.3.6
Startup FEP Platform the first time......................................................................16
3.4
Fail-over HPSG configuration............................................................................................. 16

3.4.1
Network configuration.......................................................................................... 18
3.4.2
Platform configuration.......................................................................................... 19
3.4.3
SUA configuration................................................................................................ 21
SNMP configure..................................................................................................23
4.1.1
4.1.2
4.1.3
4.1.4
4.2
MIB file RedHat Linux.......................................................................................... 23

MIB file Tru64...................................................................................................... 23
Configure SNMP Traps RedHat Linux.................................................................23
Configure SNMP Traps Tru64..............................................................................24
Configure trap filter............................................................................................................. 25
Trace tool.............................................................................................................26
5.1
Introduction......................................................................................................................... 26
2004 LogicaCMG Table of Contents
iv
5.2
Distribution.......................................................................................................................... 26
5.3
Package installation............................................................................................................ 26
5.3.1
Redhat Linux....................................................................................................... 26
5.3.2
Tru64 Unix........................................................................................................... 26
5.4
Trace tool configuration...................................................................................................... 28
5.5
SMSC installation............................................................................................................... 29
5.6
Using the trace tool............................................................................................................. 29

5.6.1
Command-line..................................................................................................... 29
5.6.2
Logging................................................................................................................ 30
5.6.3
Troubleshooting................................................................................................... 30
5.6.4
Example tracing commands................................................................................30
Monitoring and Tracing......................................................................................32

6.1
Introduction......................................................................................................................... 32
6.2
SS7 status.......................................................................................................................... 32
6.3
SUA status.......................................................................................................................... 32
6.4
Manual tracing using CTF................................................................................................... 34
Tru64 OS configuration......................................................................................35
7.1
Check installed software:.................................................................................................... 35
7.2
Check network configuration:............................................................................................. 35
HP Signaling Gateway Installation and Configuration Guide 2004 LogicaCMG
List of Figures
Figure 2-1: HPSG stack architecture...................................................................................................... 4

Figure 3-1: Example AS, ASP and associations.....................................................................................5
Figure 3-2: Example of network configuration........................................................................................6
Figure 3-3: Example SUA section from ss7_config.dat...........................................................................7
Figure 3-4: Distributed Platform network configuration.........................................................................18
Figure 3-5: Example /etc/hosts file from hpsg1.....................................................................................18
2004 LogicaCMG Table of Contents
List of Tables
Table P-1: Typographic conventions...................................................................................................... ix
2004 LogicaCMG List of Tables
vii
Preface
Purpose
The purpose of this document is to provide a guideline to configure the HP Signalling
Gateway (HPSG) for use in a NextGen solution.
Audience
The target audience of this document is engineers that configure the systems in a NextGen
solution.
Scope
The scope of the document is to provide the configuration needed to use the HPSG in a
NextGen solution.
Other related documents are:
[HPSG Manuals]
Manuals for the HPSG provided by HP.
Organisation
This document is organised in 7 chapters. The first chapter contains a short introduction to
the HPSG. The second chapter shows the architecture of the HPSG. The third chapter
describes how to configure the HPSG. The fourth chapter describes the configuration of
SNMP. The fifth chapter describes the installation and use of the trace tool. The sixth
chapter describes command that can be used for troubleshooting and monitoring. The
seventh chapter contains the additional configuration issues when installing a HPSG on
Tru64.
Typographic conventions
In this document, the typographic conventions listed in Table P-1 are used.
Table P-1: Typographic conventions
Typeface or Symbol
Meaning/Used for
Example
Courier
Refers to a keyboard key, system

command, label, button, filename,
window, or other computer component
or output.
The directory data contains
<courier>
Serves as a placeholder for variable

text that the user will replace as
appropriate to its context.
Use the file name <entity>.cfg for...
[]
Refers the user to external

documentation listed in the References
[ETSI 03.38]
2004 LogicaCMG Preface
Click the Close button to
ix
Typeface or Symbol
Meaning/Used for
Example
section.
italic
Emphasises a new word or term of

significance.
apply a style to the...
Denotes a Unix regular-user prompt for

C shell.
% ls
Denotes a Unix super-user prompt for

any shell.
# ls
Denotes an OpenVMS Digital

Command Language prompt.
$ dir
\ (Unix)
or
(OpenVMS)
Denotes line continuation; the

character should be ignored as the
user types the example, and Enter
should only be pressed after the last
line.
% grep searchforthis \
data/*.dat
Bridges two keystrokes that should be

pressed simultaneously.
If Ctrl-C does not work, use CtrlAlt-Del.
Denotes a note, a piece of text

alongside the normal text requiring
extra attention.
Note that the system is usually...
$ search [.data]*.dat searchforthis
Introduction
The HP IP STG is a hardware and software SS7-over-IP (SS7oIP) solution. It provides a

highly reliable, cost-effective medium for migrating Signalling System 7 (SS7) and the
telecommunications network signalling technology to the mobile wireless industry IP
environment.
<Product Name> <X,Y> Version 1.0
Introduction
HPSG Stack Architecture
HPSG is based on IN7 V4.1.4 or the later generation code, and can handle several SGPs.
An SGP runs in an FEP process. In the near future, more than one SGP will be running on
one node.
ASP
ASP
IP network
SCTP
SCTP
SUA
SUA
L
M
I
SCCP
L
M
I
SCCP
MTP 1/ 2/ 3
Managemen
t Process
MTP 1/ 2/ 3
FEP on
FEP on
Machine A
SUA SG
Platform
Machine B
SS7 network
SEP
SEP
Figure 2-1: HPSG stack architecture
12
DIR on
Machine C
HPSG Configuration
3.1 Introduction
The configuration of HPSG will be explained, using two single node SMSCs and two
HPSGs. Distributed HPSG configuration is explained in paragraph 3.4.
3.2 Example configuration

The following example configuration will be used for describing the configuration of HPSG.
Each HPSG has associations with both SMSC's, see Figure 3 -2. Each HPSG contains
three ASs: one for each SMSC and one global. Messages can be routed on Global Title and
Point Code. The associations are configured using multihome to provide network
redundancy, see Figure 3 -3.
SS7 network
1
SG OPC=750
SG OPC=751
SGP 1
HPSG1
SGP 1
HPSG2
ASSO 1
ASSO 1
ASSO 2
ASSO 2
ASP 1
smxxv1
ASP 2
smxxw1
ASP 1
smxxv1
ASP 2
smxxw1
RTE 1
RTE 2
RTE 1
RTE 2
RTE 1
RTE 1
RTE 2
RTE 2
DEST 1008
DEST 2008
DEST 8
AS-1
PC = 601
GT =
31654076001
AS-2
PC = 602
GT =
31654076002
AS-3
PC = 600
GT =
31654076000
DEST 1008
DEST 2008
DEST 8
AS-1
PC = 601
GT =
31654076001
AS-2
PC = 602
GT =
31654076002
AS-3
PC = 600
GT =
31654076000
Figure 3-2: Example AS, ASP and associations
2004 LogicaCMG Tru64 OS configuration
13
AS-SMSC
PLMN address = 31654076000
RemotePort to HPSG1 = 14001
RemotePort to HPSG2 = 14002
Localport may be the same,
but is not used by HPSG's
PC=600
SMXXV1
SMXXW1
AS-1
ASP 1
AS-2
ASP 2
smsc_id=2
smsc_id=1
Unique PLMN address = 31654076001
PC=601
X=10
Switch 1
Unique PLMN address = 31654076002

PC=602
X=9
10.10.1.X
10.10.2.X
HPSG 1
PC=750
2 x 32 Links
PC700
Switch 2
HPSG 2
PC=751
2 x 32 Links
PC701
PC704
PC705
SS7
Network
SS7
Network
Figure 3-3: Example of network configuration

As an example for the automated configuration tool (the GOLD script on VMS), we could
describe the HPSG1 configuration as:
HPSG1 1 local connect port 14001 and IP addresses (10.10.1.12, 10.10.2.12)
Two associations (ASS)

ASS 1 connects to ASP 1, on remote address list (10.10.1.10, 10.10.2.10), to SGP1
ASS 2 connects to ASP 2, on remote address list (10.10.1.9, 10.10.2.9), to SGP 1
Destination (DES)
DES AS 1008, with routing context 1008, is reachable via route ASP 1
DES AS 2008, with routing context 2008, is reachable via route ASP 2
DES AS 8, with routing context 8, is reachable via route ASP 1 and ASP 2
14
Routing on Point Code to PC-601, uses AS 1008

Routing on Global Title to GT-31654076001*, uses AS 1008
Routing on Global Title to GT-31654076002*, uses AS 1008
Routing on Global Title to PC-31654076000*, uses AS 8
The configuration described above can be translated to the following configuration for
generating the configuration using the GOLD scripts on VMS.
[SUA]
ALIAS,600,8,601,1008,602,2008
!
SGP, 1, 14001, (10.10.1.12, 10.10.2.12 )
!
ASP, 1, (10.10.1.10 , 10.10.2.10)
ASP, 2, (10.10.1.9, 10.10.2.9)
!
ASS, 1, 1, 1 , -1
ASS, 2, 2, 1 , -1
!
DES, 1008,1008,1,1
DES, 2008,2008,2,1
DES, 8,8,1,1,2,1
Figure 3-4: Example SUA section from ss7_config.dat
3.3 Configuring HPSG

Preparation before configuration can be started
Determine the overall system configuration (number of SMSCs, AS, ASP, link sets
and links)
Create platform configuration file with the GOLD script SS7_CREATE_STARTNEWFEP.
The following steps must be performed on each HPSG:
Create the SS7 platform with ss7configure
Add the platform configuration file that has been created with
SS7_CREATE_STARTNEWFEP.
Check and modify the gtt_rule.s7mp file
Check the sua_rk_gt.dat file
The following steps must be performed on each HPSG to run the FEP the first time:
Start the SS7 platform
15
3.3.1
Compile the routing key file
In S7MP menu, run the platform configuration script
Execute the gtt rule file in S7MP
Load the routing key
If all links and destinations are up, save the configuration in order for the platform to
startup at reboot
Create SS7 Platform

SS7 platform id's cannot be chosen freely. The trace tool expects the fixed platform id's to
be used for different SS7 flavours. The following table shows the SS7 flavours and the
corresponding platform id.
SS7 flavour
Platform Id
ccitt / ITU
ANSI
china
Configure the SS7 platform as shown below. In this example, platform_id "c "is used. Add
only the Point Code of the SGP to generate platform startup scripts. Adapt the generated
ss7_gen_xx.s7mp script or create a new one to activate SUA and SS7 settings:
hpsg3:ss7 > ss7configure
The machine from which you configure an IN7 platform is by implication
part of that platform. The following constraints exist:
- When you first create an IN7 platform configuration, This must be done
from a machine that will be part of the platform.
- When you modify an existing IN7 platform configuration, This must be
done from a machine that is already part of the platform.
Scanning platform databases...
This machine belongs to the following IN7 platform(s):

c
Enter an existing or a new platform ID [Return to exit]: c
-------------------------------------------------------------------The transport protocol to use must be specified:
1. TCP/IP
Enter the number for your choice [1]:
### SS7CONFIGURE-I-TRANSPPROTSET, Transport protocol set to TCP/IP.
16
-------------------------------------------------------------------The IN7 protocol variant to use must be specified:

1. ITU-T
Enter the number for your choice [1]:
### SS7CONFIGURE-I-CHT_PROTVARSET, Protocol variant set to ITU-T.
-------------------------------------------------------------------You are configuring IN7 for platform ID c.
1. Display current configuration
2. Remove current configuration and Exit
3. Define the machine configuration
4. Define the management configuration
5. Modify the platform characteristics
6. Apply configuration to all machines and Exit
7. Quit without making any changes
Enter the number for your choice: 3
-------------------------------------------------------------------IN7 machine configuration
The following machines are already part of the configuration of platform
c
HPSG1
Enter an existing or a new machine name [Return to go back]: HPSG1
-------------------------------------------------------------------Machine HPSG1 already belongs to platform c.
Do you want to (m)odify or to (r)emove its configuration [Return to go
back] ? m
-------------------------------------------------------------------IN7 configuration of machine HPSG1 for platform c.
1. Subsystem setup
2. Device setup
3. Change Local IP interface
Enter the number for your choice [Return to go back]: 1
-------------------------------------------------------------------IN7 machine configuration - Subsystem setup
The different types of IN7 subsystem are:
1. FEP
2. DIR
17

-------------------------------------------------------------------There is no FEP subsystem on machine HPSG1.
Do you want to add it (y|n) [y] ?
### SS7CONFIGURE-I-SUBHOST, Machine HPSG1 is now configured as hosting a
FEP subsystem.
1. FEP
2. DIR
-------------------------------------------------------------------There is no DIR subsystem on machine HPSG1.
DIR subsystem.
1. FEP
2. DIR
Enter the number for your choice [Return to go back]:
1. Subsystem setup
2. Device setup
-------------------------------------------------------------------IN7 machine configuration - Device setup
1. DNBE1-4TC
PT38A
RUNNING
18

1. Subsystem setup
2. Device setup
-------------------------------------------------------------------IN7 machine configuration
c
HPSG1
Enter an existing or a new machine name [Return to go back]:
IN7 management configuration - Platform Point Code setup
Enter the platform OPC [Return to go back]: 750
### SS7CONFIGURE-I-OPCSET, OPC of platform a set to 750.
-------------------------------------------------------------------IN7 management configuration
1.
2.
3.
4.
5.
Configure
Configure
Configure
Configure
Configure
platform Point Code

destination Point Codes
SS7 links
routing
TCP/IP connections

19

IN7 platform configuration - File generation
### SS7CONFIGURE-W-NOCFGADJ, The management configuration does not allow
any traffic: there is no configured adjacent PC.
3.3.2
SUA Configuration
The SUA settings are managed in the (generated) file *.s7mp configuration file in directory
/var/ss7/platform_<Id>/s7mp. See also the file fep_gen_1.s7mp in de appendix A.
First, the FEP is created with the Point Code of the HPSG and SMSC (for Point Code
routing to SMSCs):
CREATE FEP HPSG3 /OPC=750
ENABLE FEP HPSG3
ADD FEP HPSG3 /ALIAS_PC_LIST=(600,601,602)
The layers are configured next:

CREATE
ENABLE
CREATE
ENABLE
CREATE
ENABLE
CREATE
ENABLE
FEP
FEP
FEP
FEP
FEP
FEP
FEP
FEP
HPSG3
HPSG3
HPSG3
HPSG3
HPSG3
HPSG3
HPSG3
HPSG3
MTP2
MTP2
MTP3
MTP3
SCCP
SCCP
SUA
SUA
In this part, the SGP is configured with the ip-addresses and listen port of the node that will
be used for SUA traffic. Every node can have one or more SGP (in the near future) to handle
traffic:
CREATE FEP HPSG3 SUA SGP 1 /FEPNAME=HPSG3 /IPLIST=(10.10.1.11,
10.10.2.11) /port=14001
ENABLE FEP HPSG3 SUA SGP 1
Next, the ASP are configured with the IP-addresses of the SMSCs and their associations
with the SGP:
CREATE FEP HPSG3 SUA ASP 1 /IPLIST=(10.10.1.10, 10.10.2.10)
ENABLE FEP HPSG3 SUA ASP 1
CREATE FEP HPSG3 SUA ASP 1 ASSOCIATION 1 /SGP=1 /port=-1
20
ENABLE FEP HPSG3 SUA ASP 1 ASSOCIATION 1

CREATE
ENABLE
CREATE
ENABLE
FEP
FEP
FEP
FEP
HPSG3
HPSG3
HPSG3
HPSG3
SUA
SUA
SUA
SUA
ASP
ASP
ASP
ASP
2 /IPLIST=(10.10.1.9, 10.10.2.9)
2
2 ASSOCIATION 2 /SGP=1 /port=-1
2 ASSOCIATION 2
In this part, the AS's (destinations) are configured. If no /RC is defined then the routing
context is the same value as the SUA DESTINATION. The PC in the CPCLIST (< 100 PCs)
are to be informed when the state of a DESTINATION entity changes. If the SUA
DESTINATION is numbered (1, 2, 3 ), then the /RC must be defined (1008, 2008, 8, etc.).
The /RRW parameter can be specified to give a weight for the routing to do weighted loadbalancing.
3.3.3
CREATE
ENABLE
CREATE
ENABLE
FEP
FEP
FEP
FEP
HPSG3
HPSG3
HPSG3
HPSG3
SUA
SUA
SUA
SUA
DESTINATION
DESTINATION
DESTINATION
DESTINATION
1008 /CPCLIST=(700,701,704,705) /RC=1008

1008
1008 ROUTE 1 /RRW=1
1008 ROUTE 1
CREATE
ENABLE
CREATE
ENABLE
FEP
FEP
FEP
FEP
HPSG3
HPSG3
HPSG3
HPSG3
SUA
SUA
SUA
SUA
DESTINATION
DESTINATION
DESTINATION
DESTINATION
2008 /CPCLIST=(700,701,704,705) /RC=2008

2008
2008 ROUTE 2 /RRW=1
2008 ROUTE 2
CREATE
ENABLE
CREATE
ENABLE
CREATE
ENABLE
FEP
FEP
FEP
FEP
FEP
FEP
HPSG3
HPSG3
HPSG3
HPSG3
HPSG3
HPSG3
SUA
SUA
SUA
SUA
SUA
SUA
DESTINATION
DESTINATION
DESTINATION
DESTINATION
DESTINATION
DESTINATION
8
8
8
8
8
8
/CPCLIST=(700,701,704,705) /RC=8
ROUTE
ROUTE
ROUTE
ROUTE
1 /RRW=1
1
2 /RRW=1
2
SS7 Configuration
The SS7 settings are managed in an *.s7mp configuration file in directory
/var/ss7/platform_<Id>/s7mp. The SS7 part can also be generated using the GOLD
script on VMS. See also the file fep_gen_1.s7mp in de appendix A.
First create the trunks with the device name of the SS7 card:
!---------------------------------------------------------------!
!--------------------------- MTP2 part -------------------------!
CREATE FEP HPSG3 MTP2 TRUNK 1 /DEVNAME=PT38A0 /FEPNAME=HPSG3
ENABLE FEP HPSG3 MTP2 TRUNK 1
CREATE FEP HPSG3 MTP2 DATA_LINK 11 /FEPNAME=HPSG3 /DEVNAME=PT38A001
ENABLE FEP HPSG3 MTP2 DATA_LINK 11
Define the link sets with the right Point Code. Add the rule_id and ranks to be used:
21
!---------------------------------------------------------------!
!-------------- Adjacent DESTINATIONs and LINKSETS -------------!
CREATE FEP HPSG3 MTP3 DESTINATION 700 /RULEID=0
ENABLE FEP HPSG3 MTP3 DESTINATION 700
CREATE FEP HPSG3 MTP3 LINKSET 1 /ADJ=700
ENABLE FEP HPSG3 MTP3 LINKSET 1
CREATE FEP HPSG3 MTP3 DESTINATION 700 ROUTE 1 /RANK=0
ENABLE FEP HPSG3 MTP3 DESTINATION 700 ROUTE 1
Configure the links of all linksets:

!---------------------------------------------------------------!
!--------------------------- LINK part -------------------------!
CREATE FEP HPSG3 MTP3 LINKSET 1 LINK 0 /RANK=0 /PLN=11 /FEPNAME=HPSG3
ENABLE FEP HPSG3 MTP3 LINKSET 1 LINK 0
CREATE FEP HPSG3 MTP3 LINKSET 1 LINK 1 /RANK=1 /PLN=12 /FEPNAME=HPSG3
ENABLE FEP HPSG3 MTP3 LINKSET 1 LINK 1
Connects FEP_SUBSYSTEM to the rest of the configuration, allowing peer-to-peer

communication and wait 15 seconds before executing next command:
CONNECT FEP HPSG3
WAIT 15
Initialise all data links:

INIT_LINK FEP HPSG3 MTP2 DATA_LINK 11
INIT_LINK FEP HPSG3 MTP2 DATA_LINK 12
Activate link set:

ACTIVATE FEP HPSG3 MTP3 LINKSET 1
22
3.3.4
GTT Configuration
This GTT file can also be generated using the GOLD script on VMS. Locate this file in:
/var/cluster/members/member0/ss7/<platform_id>/s7mp. Example file:
# rules towards load generator platform c
gtt_rule_create 1
/p_rnb=0/p_gti=4/p_tt=00/p_np=1/p_nai=4/p_gtai=132143/p_match=wildc/t_ppc
=2bc/t_tt=00/t_distrib=master
gtt_rule_create 2
gtt_rule_create 3
3.3.5
Parameter
Description
P_RNB
Reserved National bit field for the GTT rule pattern.
P_GTI
Global Title Indicator field for the GTT rule pattern (NAI_ONLY, TT_ONLY,
TT_NP_ES,TT_NP_ES_NAI).
P_TT
Translation Type field for the GTT rule pattern.
P_NP
Numbering Plan field for the GTT rule pattern.
P_NAI
Nature of Address Information field for the GTT rule pattern.
P_GTAI
Address Information field for the GTT rule pattern in an odd or even number of bytes. GTAI
qualifiers in rule definitions are entered as a natural, numeric sequence.
P_MATCH
Pattern Matching Mechanism for the GTT rule pattern (EXACT / WILDCARD).
T_PPC
Primary Point Code for the GTT rule translation.
T_TT
Translation Type field for the GTT rule translation.
T_DISTRIB
Distribution Mechanism field for the GTT rule translation (LOADSHARING

/MASTERBACKUP).
Routing key Configuration

In order to route received messages to their destination, SUA-SG matches a user-defined
Routing Key in the SUA database to an IP or SS7 destination identified by a PC and SSN,
and/or a mobile network application identified by MAP parameters, and/or performs GTT
translation to identify the target AS. Example
/usr/var/ss7/<platform_id>/sua/sua_rk_gt.dat:
# igt: GTAI present in the SCCP called address of the message.
# sr : TP-DA field present in the MAP message. It is the SMS Recipient.
# so : SM-RP-OA field present in the MAP message. It is the SMS
Originator.
# sc : Replace the SM-RP-DA field in the message.
# ogt: Replace the GTAI field in the SCCP called address of the message.
# pc : PC present in the SCCP called address of the message.
# ssn: SSN present in the SCCP called address of the message.
# as : the application server onto where the message will be forwarded.
23
#
this value is the same as that of the SAU-destination in
# fep_gen_X.s7mp
#
pc=600; ssn=8; as=8;
pc=601; ssn=8; as=1008;
pc=602; ssn=8; as=2008;
igt="31654076001.*"; as=1008;
igt="31654076002.*"; as=2008;
igt="31654076000.*"; as=8;
igt="31654076000.*";sr="31655.*";as=2008;
Messages for PC 600 will be routed to destination 8 when routing on PC.

Messages for routed on GT for 31654076001 will be routed to destination 1008.
24
3.3.6
Startup FEP Platform the first time

To startup the FEP for the first time, the following commands must be execute as user SS7:
Start the FEP, dir and SNMP processes:
$ ss7startup <platform_id> fep dir snmp
Compile the routing keys:
$ sua_rk_rules_ccitt -p <platform_id> -n sua_rk_gt.dat -c
This will create a library in /usr/var/ss7/<platform_id>/sua/
Start S7MP menu for platform:
$ s7mp<platform_id>
In S7MP menu, run the platform configuration script:
S7MP_C> do ss7_gen_<platform_id>.s7mp
Execute the gtt rule:
S7MP_C> do gtt_rule.s7mp
Load the modified routing keys file in memory:
S7MP_C> load_stand_by fep * sua
S7MP_C> switch_table fep * sua
S7MP_C> copy_active fep * sua
If all links and destinations are up, save the configuration:
S7MP_C> save_config
This will create the file SS7_SAVE_CONFIG.DAT in
/usr/var/ss7/<platform_id>/save_config
After the save_config command this configuration will be used after startup or restart the
platform.
3.4 Fail-over HPSG configuration

The Distributed Platform feature allows multiple HPSG nodes to act as a single network
routing entity and are seen as single signalling point in the telecommunications network.
This can be used to implement fail-over in case SS7 links fails. In a Distributed Platform
HPSG nodes are running in a cluster with the same configuration. The platform is composed
of two servers, connected by a LAN connection.
25
SS7 network
SG OPC=750
SG OPC=750
LAN connection
SGP 1
HPSG1
SGP 1
HPSG2
ASSO 2
ASSO 2
ASSO 1
ASSO 1
ASP 1
smxxv1
ASP 2
smxxw1
RTE 1
RTE 2
RTE 1
RTE 2
26
DEST 1008
DEST 2008
DEST 8
AS-1
PC = 601
GT =
31654076001
AS-2
PC = 602
GT =
31654076002
AS-3
PC = 600
GT =
31654076000
3.4.1
Network configuration
The Distributed Platform feature requires a specific network configuration to provide
redundancy. The HPSG fail-over support processes do not support automatic recovery yet.
This requires that the network connection between the HPSG nodes needs to provide failover support. This fail-over support is configured using bonding. The redundancy support for
the SUA connections is provided using the SCTP multi-homing. The configuration is shown
in Figure 3 -5. The configuration uses three networks: One network for the O&M and failover traffic and two networks for the SUA traffic.
Figure 3-5: Distributed Platform network configuration
SMSC 1
10.10.1.9
SMSC 2
10.10.2.9
10.10.1.10
10.10.2.10
message vlan 2
10.10.1.x
mesage vlan 3
10.10.2.x
10.10.1.6
10.10.2.6
HPSG 1
10.10.1.7
10.10.2.7
HPSG 2
10.10.3.6
10.10.3.7
O&M vlan 7
10.10.3.x
Before configuring a Distributed Platform the file /etc/hosts must be modified. The file
/etc/hosts on node hpsg1 must have an entry for hpsg2 and vice versa. This is needed
because the systems use the hostname to access the other members of the cluster. The
hostnames need to be configured to use the O&M network, e.g. 10.10.3.7 for the example
shown above.
Figure 3-6: Example /etc/hosts file from hpsg1
$ cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1
localhost.localdomain localhost
10.10.1.249
defgw defgw.att.cmg.nl
10.10.3.6
hpsg1 hpsg1.att.cmg.nl hpsg11.att.cmg.nl
10.10.3.7
hpsg2 hpsg2.att.cmg.nl
27
10.10.1.6
10.10.2.6
3.4.2
Platform configuration
Please pay attention that when from hpsg2 you configure and save a distributed
platform C you loose the platform C configuration that was previously present on
hpsg1.
Adding an extra node to a Distributed Platform can be done using ss7configure from the
ss7 account
You are configuring STG for platform ID d.

-----------------------------------------------------------------------
STG machine configuration

d
HPSG1
Enter an existing or a new machine name [Return to go back]: HPSG2
----------------------------------------------------------------------Machine HPSG2 does not belong to platform d.
Do you want to add it (y|n) [y] ? y
### SS7CONFIGURE-I-MACHADD, Machine HPSG2 added to platform d.
-----------------------------------------------------------------------
STG configuration of machine HPSG2 for platform d.
28
1. Subsystem setup
2. Device setup
----------------------------------------------------------------------STG machine configuration - Subsystem setup
The different types of STG subsystem are:
1. FEP
2. DIR
----------------------------------------------------------------------There is no FEP subsystem on machine HPSG2.
FEP subsystem.
1. FEP
2. DIR
----------------------------------------------------------------------There is no DIR subsystem on machine HPSG2.
DIR subsystem.
1. FEP
2. DIR
29
-----------------------------------------------------------------------
STG configuration of machine HPSG2 for platform d.

1. Subsystem setup
2. Device setup
-----------------------------------------------------------------------
STG machine configuration

d
HPSG1 HPSG2
Enter an existing or a new machine name [Return to go back]:
----------------------------------------------------------------------You are configuring STG for platform ID d.
STG platform configuration - File generation
### SS7CONFIGURE-W-NOCFGADJ, The management configuration does not allow
any traffic: there is no configured adjacent PC.
[ss7@hpsg1 ~]$
3.4.3
SUA configuration
Below is the SUA part of SS7_CONFIG.DAT for a Distributed Platform of two nodes. For the
complete configuration, see Appendix A..
[SUA]
! ************************************
! ALIAS, ( PC, PC, ...)
! SGP, NR, PORT, ( IP , IP , ... )
! ASP, NR, ( IP , IP , ... )
30
! ASSOCIATION, NR, ASP_NR, SGP_NR, PORT

! DESTINATION, NR, RC, ROUTE ASP NR ,RRW, ROUTE ASP NR , RRW , ...
! ************************************
HPSG1
ALIAS,600,11,601,1011,602,2011
!
SGP, 1, 14002, (10.10.1.6, 10.10.2.6 )
!
ASP, 1, (10.10.1.10 , 10.10.2.10)
ASP, 2, (10.10.1.9, 10.10.2.9)
!
ASS, 1, 1, 1 , -1
ASS, 2, 2, 1 , -1
!
DES, 1011,1011,1,1
DES, 2011,2011,2,1
DES, 11, 11 , 1 , 1 , 2 ,1
!
HPSG2
SGP, 1, 14002, (10.10.1.7, 10.10.2.7 )
!
31
4.1.1
SNMP configure
MIB file RedHat Linux

The MIB file needs to be copied to an SNMP management station. The MIB is located in
/usr/var/ss7/lib/decss7.mib.
You also need the following MIB's.
/usr/share/snmp/mibs/HOST-RESOURCES-MIB.txt
/usr/share/snmp/mibs/RFC1213-MIB.txt
/usr/share/snmp/mibs/UDP-MIB.txt
/usr/share/snmp/mibs/UDP-SNMP-MIB.txt
You also need the following MIB's for SNMPv2.
/usr/share/snmp/mibs/SNMPv2-MIB.txt
4.1.2
MIB file Tru64

The MIB's are located in:
/usr/opt/STGCCITT300/bin/decss7.mib
/usr/share/sysman/mibs/pm.mib
/usr/share/sysman/mibs/svrMgt.mib
/usr/share/sysman/mibs/svrSystem.mib
/usr/share/sysman/mibs/cpqHealth.mib
/usr/share/sysman/mibs/cpqHostOs.mib
/usr/share/sysman/mibs/cpqNic.mib
/usr/share/sysman/mibs/cpqScsi.mib
/usr/share/sysman/mibs/cpqStdEquipment.mib
/usr/share/sysman/mibs/cpqSystemInfo.mib
/usr/share/sysman/mibs/cpqThreshold.mib
Copy them to a SNMP management station.
You need the SNMPv2-SMI and SNMPv2-TC MIB definition MIB's.
4.1.3
Configure SNMP Traps RedHat Linux

Edit the /etc/snmp/snmpd.conf file to modify the location of the system:
sysName
sysLocation
sysContact
32
hpsg1
Nieuwegein
LogicaCMG
# To define a read write community use

rwcommunity <community name>
Edit the /etc/snmp/snmpd.conf file to send traps to the Network Management Station
(NMS):
# Enable Send Authentication traps
snmpEnableAuthenTraps
1
# Send traps using community public SNMPv2 notifications

informsink <IP address of NMS> public
# Send traps using community public SNMPv1 Traps

trapsink <IP address of NMS> publicConfigure SNMP Traps Tru64
4.1.4
Configure SNMP Traps Tru64

Edit the /etc/snmp/snmpd.conf file to modify the location of the system:
sysName
sysLocation
sysContact
hpsg1
Nieuwegein
LogicaCMG
# Enable Send Authentication traps

snmpEnableAuthenTraps
1
# To define a read write community use

community
<community name> write
Edit the /etc/snmp/snmpd.conf file to send traps to the Network Management Station
(NMS):
# Send traps using community public SNMPv1 Traps
trap
public
<IP address of NMS>
Restart the SNMPD daemon; for example:

/etc/rc.d/init.d/snmpd restart
33
4.2 Configure trap filter

The path name of the general trap filtering file is
/usr/var/ss7/ss7_trap_filtering.dat. To stop a trap being reported, change the
value <ON> for the specified trap to <OFF> in the second column of the file. The comment
in the third column of the file indicates the name of the trap. An example of the trap filtering
file template follows, with all traps set to be reported (value = ON).
To configure or reconfigure the set of traps reported by the HPSG SNMP Agent:
Copy and/or edit the trap-filtering file.
Restart the HPSG SNMP Agent (login as ss7):
ss7startup <platform_id> snmp
or reload the file using the Agent Init object from the MIB:
snmpset 'hostname -s' public set
1.3.6.1.4.1.36.2.18.43.1.100.1.1.2.<IndexOfPlatform> -i 3
where <IndexOfPlatform> is a number, the SNMP platform index that corresponds to the
platform ID.
34
Trace tool
5.1 Introduction
This chapter describes the installation of the Unix part of the HPSG trace tool. The
installation of Tru64 is different from that of RedHat Linux. For Linux (DL380), all needed
packages are included in a single package. For Tru64 (DS15), the installation consists of
two parts: Installation of Perl packages and the installation and configuration of the tool. This
manual also shortly describes the SMSC part of the tool. This is included for reference only.
5.2 Distribution
The following packages are available on http://nl-nie-dist/:
RedHat Linux on DL380
ss7_trace-1.0.1-1.i386.rpm
Tru64 on DS15
ss7_trace-1.0.1-tru64.tar.gz
Please note that the Tru64 functionality is the same as the Linux RedHat version. The only
difference is the packaging.
5.3 Package installation

The installation of the package is different between RedHat Linux DL-380 and Tru64 DS-15.
For both systems the package needs to be installed on every HPSG node.
5.3.1
Redhat Linux
Log in as user SS7, make sure the package is available on the system and then perform the
following steps:
hpsg1$ su -c "rpm -ivh <path>/ss7_trace-1.0.1-1.i386.rpm"
password:<root password>
5.3.2
Tru64 Unix
Log in as user SS7, make sure the package is available on the system and then perform the
following steps:
Change to the home directory of the SS7 user:
hpsg:ss7> cd
Unpack the archive in the current dir
hpsg:ss7> cat <path>/ss7_trace-1.0.1-tru64.tar.gz | gunzip | tar -xf
Change to the trace tool directory:
35
hpsg:ss7> cd trace_tool
Unpack the Perl package archives:
hpsg:ss7> cat IO-Tty-1.02.tar.gz | gunzip | tar -xf hpsg:ss7> cat IO-Stty-.02.tar.gz | gunzip | tar -xf hpsg:ss7> cat Expect-1.15.tar.gz | gunzip | tar -xf
Compile the Perl Tty package:
hpsg:ss7> cd IO-Tty-1.02
hpsg:ss7> perl Makefile.PL
hpsg:ss7> make
hpsg:ss7> make test
Install the Perl Tty package as root:
hpsg:ss7> su -c make install

hpsg:ss7> cd ..
Compile the Perl Sty package:
hpsg:ss7> cd IO-Sty-.02
hpsg:ss7> make
hpsg:ss7> make test
Install the Perl Sty package as root:

hpsg:ss7> cd ..
Compile the Perl Expect package:
hpsg:ss7> cd Expect-1.15
hpsg:ss7> make
hpsg:ss7> make test
Install the Perl Expect package as root:

hpsg:ss7> cd ..
36
5.4 Trace tool configuration

After installing the software, some configuration changes must be made. The changes need
to be made on every HPSG node.
Make sure the IP addresses and hostnames of all SMSC nodes are mentioned
in /etc/hosts. If necessary, become root and add them.
Login as SS7 user and perform the following steps:
Change to the home directory of the SS7 user. For every address assigned to the
SMSC nodes, add a line like the following to the file .rhosts in the home directory
of the ss7 user. If the file does not exist, create it.
<hostname SMSC>
decss7
For example:
smcm11
smcm12
decss7
decss7
Login as root and make sure the file .rhosts in the SS7 home directory is readwrite for the owner only:
hpsg1:ss7> chmod 600 .rhosts
Verify that you can login to the HPSG from the SMSC decss7 account without typing a
password:
SMCM11:DECSS7> rsh /user=ss7 10.10.1.6
Last login: Fri Sep 3 10:22:01 from 10.10.1.6
[ss7@hpsg1 ~]$ exit
%RSH-S-REMCLOSED, Remote connection closed
SMCM11:DECSS7>
For Tru64 only: Change permissions of the CTF binary. It must be setuid root:
hpsg1:ss7> su -c chmod u+s /usr/bin/ctf_ui310
This completes the installation of the HPSG trace tool on the HPSG node.
37
5.5 SMSC installation

Besides the component on the HPSG nodes, the trace tool also contains an SMSC
(OpenVMS) component. In the directory CMG$TOOLS, the following VMS files must be
installed (or overwritten) with the versions available from http://nl-nie-dist/:
The script ss7_trace.com, that calls hpsg_trace.com when applicable
ss7_tranalyze.exe that can process HPSG trace files. This can be verified in
the help message of the tool.
The script hpsg_trace.com that actually starts and stops the tracing.
The ss7_trace.com script detects the availability of a signalling gateway by checking the
hostnames. For the HPSG the hostnames must be hpsg<n>. The hostnames needs to be
defined on the SMSC system. For each HPSG add a hostname hpsg<n>. This can be
verified by with the following command:
DECSS7> ping hpsg<n>
You also have to make sure that no hostnames itp<n> are defined.
5.6 Using the trace tool

The HPSG trace tooling consists of an SMSC part, which is comparable to the standard
SMSC trace tooling and a part that runs on the HPSG. The SMSC part is only shown as
example, as it is similar in usage to the standard SS7-trace tooling. The part of the trace tool
that runs on the HPSG consists of a Perl script that starts and stops a CTF trace process,
and an executable that analyzes of the trace output. The part that runs on the HPSG is
normally invoked from a SMSC node, but it can also be started manually on the HPSG
node.
When the Unix trace tool starts, it detects whether any trace is still running, and stops it. This
is necessary as it is not possible to run two CTF processes simultaneously. If a CTF process
is running that was not started by the trace tool (but manually, e.g. for tracing SUA for
instance), then the tool does not terminate it. In that case, the CTF trace will, not start on the
affected node.
5.6.1
Command-line
The trace tool is called ss7_trace. It takes the following command-line parameters:
ss7_trace <start|stop|abort> <itu|ansi|china> [allctf]
38
The first argument specifies the action to do:
start: starts the trace and prints 'OK' if successful, and 'Failed' if not. If another
trace is running, it is terminated first. If the optional parameter 'allctf' is given, then
any other CTF process is terminated (this is not done when started from the SMSC
ss7_trace tool).
stop: stops a running trace, and prints the filename of the result file if successful,
and 'Failed' if not. The SMSC node can then download the result file, and process it.
abort: stops a running trace, but does not analyse the result.
The second parameter <flavor> described the SS7 flavor to trace. The SS7 flavor can be
chosen from the list itu, ansi or china. Each SS7 flavor is connected to a fixed platform
id. ITU requires a platform C, ANSI requires platform D, China requires platform E.
The optional parameter 'allctf' stops any running CTF process.
5.6.2
Logging
The CTF data files and analysed files are stored in the directory /tmp/ss7_trace/.
The file /tmp/ss7trace_<uid>_<date>.log contains log messages from the SS7
trace tool for the given date and uid. The uid is that of the user who started the tool,
normally, this is the ss7 user on the HPSG node.
The file /tmp/ss7trace_<uid>_ctfdata.log contains a log of the communication with
the last CTF process that ran (or is still running). The uid is that of the user who started the
tool, normally, this is the ss7 user on the HPSG node.
5.6.3
Troubleshooting
In general, check the log file on the HPSG node (see section Logging) to see what the
failure was, and where it occurred.
When the tracing doesn't start on a node, the following commands can be tried:
5.6.4
Other CTF running:

ps ax | grep ctf_ui
CTF UI not setuid root (e.g. after upgrade):

ls -lL /usr/bin/ctf_ui350
Example tracing commands

Tracing on the SMSC
Login as user decss7
To trace ITU platform (platform id C):
> @CMG$TOOLS:SS7_TRACE W
> SS7 ctf$hpsg1.txt
39
To trace Ansi platform (platform id D):

> @CMG$TOOLS:SS7_TRACE W /A
> SS7 ctf$hpsg1.txt /A
Tracing on the HPSG

Login as user ss7
To trace ANSI platform (platform id D):
[ss7@hpsg1 ~]$ ss7_trace start ansi
OK
[ss7@hpsg1 ~]$ ss7_trace stop ansi
/tmp/ss7_trace/ss7_trace.txt
[ss7@hpsg1 ~]$ ss7_tranalyze /tmp/ss7_trace/ss7_trace.txt -a
40
Monitoring and Tracing
6.1 Introduction
This chapter describes a few commands that can be used to retrieve the status of the
HPSG. For a complete list of tracing see the Common Trace Facility and S7MP reference
manuals.
6.2 SS7 status

Login as ss7
Start s7mp menu for the platform to check
$ s7mpc
Check if all SS7 links are available:
S7MP_C> show fep * mtp3 linkset * link */stat
Check if all Point Code destinations are accessible:

S7MP_C> show fep * mtp3 dest * /stat
6.3 SUA status

Login as ss7
Start s7mp menu for the platform to check
$ s7mpc
Check if all destinations on SUA side are available (only if the SMSC has a Point Code):
S7MP_C> show fep * sua dest */stat
Check SGP:
S7MP_C> show fep * sua sgp 1 /char
41
Check ASP:
S7MP_C> show fep * sua asp */char
Check associations:
$ telnet localhost 2000
HP OpenCall SCTP protocol stack version v1.08b4 (Linux V22 09-Feb-2004
16:13:59).
Type 'help' to get information about available commands.
> stat
PID
1266
Local port
14001
Asso tag
0x11540c9c
Remote port
14001
Remote addresses
10.10.2.10
10.10.1.10
> app 1266

App 1266 > stat
Proto Asso tag
Local address
Remote address
SCTP 0x11540c9c
SCTP 0x11540c9c 10.10.2.6:14001
SCTP 0x11540c9c 10.10.1.6:14001
SCTP 0x11540c9c
10.10.2.10:14001
SCTP 0x11540c9c
10.10.1.10:14001
App 1266 > asso 0x11540c9c
App 1266 / Asso 0x11540c9c:14001 > attr
Association parameters:
Checksum:
Remote port:
Association status:
Primary destination:
Current destination:
Inbound streams:
Outbound streams:
Remote verification tag:
Association MTU:
Initial RTO (ms):
Min RTO (ms):
Max RTO (ms):
Max retransmit count:
Send buffer size (bytes):
Send buffer used (bytes):
Recv buffer size (bytes):
Recv buffer used (bytes):
CRC32c
14001
ESTABLISHED
10.10.2.10
10.10.2.10
16
16
0x2dac5ceb
1500
0
0
0
0
65535
0
65535
2055308
Association counters:
T1_EXPIRY_NB:
T2_EXPIRY_NB:
T3_EXPIRY_NB:
STALE_COOKIE_NB:
INVALID_COOKIE_NB:
BYTES_RCV_NB:
BYTES_SNT_NB:
CHNK_RCV_NB:
42
0
0
306
0
0
7954316
0
13488784
State
ESTABLISHED
IDLE
IDLE
CHNK_SNT_NB:
UNORD_CHNK_RCV_NB:
UNORD_CHNK_SNT_NB:
INIT_CHNK_RCV_NB:
INIT_CHNK_SNT_NB:
INIT_ACK_CHNK_RCV_NB:
INIT_ACK_CHNK_SNT_NB:
COOKIE_CHNK_RCV_NB:
COOKIE_CHNK_SNT_NB:
COOKIE_ACK_CHNK_RCV_NB:
COOKIE_ACK_CHNK_SNT_NB:
DATA_CHNK_IN_NB:
DATA_CHNK_RCV_NB:
DATA_CHNK_OUT_NB:
DATA_CHNK_SNT_NB:
SACK_CHNK_RCV_NB:
SACK_CHNK_SNT_NB:
HEARTBEAT_CHNK_RCV_NB:
HEARTBEAT_CHNK_SNT_NB:
HEARTBEAT_ACK_CHNK_RCV_NB:
HEARTBEAT_ACK_CHNK_SNT_NB:
ABORT_CHNK_RCV_NB:
ABORT_CHNK_SNT_NB:
SHUTDOWN_CHNK_RCV_NB:
SHUTDOWN_CHNK_SNT_NB:
SHUTDOWN_ACK_CHNK_RCV_NB:
SHUTDOWN_ACK_CHNK_SNT_NB:
ERROR_CHNK_RCV_NB:
ERROR_CHNK_SNT_NB:
0
163433
79347
0
0
0
0
0
0
0
1
39522
39522
79347
79038
52339
26368
20339
51233
51233
20339
0
0
0
0
0
0
0
0
App 1266 / Asso 0x11540c9c:14001 >
6.4 Manual tracing using CTF

The example below uses ccitt/ITU. For ANSI, or China replace ccitt with the correct SS7
flavour:
Login as ss7
Start Common Trace Facility (CTF) tool
$ ss7ctf_ui_start_ccitt -l
To trace SS7 traffic:
CTF> start ss7 fep c mtp3 layer_itf mtp2 /type=live
To trace matched routing key:
CTF> start ss7 fep c sua routing match /type=live
To stop tracing:
CTF> stop
To analyse the trace file (without using "/type=live"):
CTF> analyse /output=test.trc
43
Tru64 OS configuration
7.1 Check installed software:

HPSG4:root > setld -i | grep -e FMK -e STG -e SS7 -e SCT -e SUA | grep -v
not
STGCCITTPRD300
installed
STGCCITTRN300
installed
Notes
STGDBCHECK300
installed
Checking Tool
STGHEADERS300
installed
STGIVP300
installed
Verification Procedure
STGSTARTUP300
installed
Configure/Startup Procedures
IP-STG V3.0-0 CCITT Product

IP-STG V3.0-0 CCITT Release
FMKCTF300
installed
FMKLIC140
installed
V140
FMKTBX300
installed
Toolbox Library Version v3.00b3
HP OpenCall CTF v3.00

HP OpenCall FMK Licensing
SS7DNBDRIVER040300
SS7DNBTOOLS040300
installed
installed
HP Opencall DNB Driver v4.03

HP Opencall DNB Tools v4.03
SCTDOC150
Documentation Set
SCTEXAMPLE150
Application Examples
SCTHEADERS150
Files
SCTPRD150
installed
HP OpenCall SCTP V1.0
installed
HP OpenCall SCTP V1.0
installed
HP OpenCall SCTP V1.0 Header
installed
HP OpenCall SCTP V1.0 Product
IP-STG V3.0-0 MTP3 Database

IP-STG V3.0-0 Header Files
IP-STG V3.0-0 Installation
IP-STG V3.0-0
HP OpenCall Portability
7.2 Check network configuration:

# lan_config Usage: lan_config -i[interface] [-option]
Options:
-a[auto]
-m[media]
-s[speed]
-x[duplex]
Enable(1)/Disable(0) Auto Sense/Negotiation

Media Type: (aui, bnc, utp, fiber)
Media Speed: (10, 20, 100, 200, 1000, 10000)
Enable(1)/Disable(0) Full Duplex Mode
Set the speed to 100Mbit Full duplex

# rcmgr get IFCONFIG_0
10.10.1.11 netmask 255.255.255.0
44
# rcmgr set IFCONFIG_0 10.10.1.11 netmask 255.255.255.0 speed

200
# rcmgr get IFCONFIG_1
10.10.2.11 netmask 255.255.255.0
# rcmgr set IFCONFIG_1 10.10.2.11 netmask 255.255.255.0 speed
200
45
Appendix A. Example configuration files
Example fep_gen_c.s7mp for single node platform

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! This file is generated on Mon Jun 14 11:38:23 2004
!!
!!
Using the startnewfep creator Jun 14 2004
!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! SMSC point code
: 750
!!
!! National use indicator : 2
!!
!! ALIAS point code
: 600,601,602 !!
!! Applications (ssn)
:
8
!!
!! SGP 1
IP : (10.10.1.6, 10.10.2.6 ) PORT 14001
!!
!! ASP 1
IP : (10.10.1.10 , 10.10.2.10)
!!
!!
ASSOCIATION 1
SGP 1
!!
!! ASP 2
IP : (10.10.1.9, 10.10.2.9)
!!
!!
ASSOCIATION 2
SGP 1
!!
!! DESTINATION AS : 1008 ASP 1
RRW 1
!!
RRW 1
!!
!! DESTINATION AS : 8
ASP 1
RRW 1 ASP 2
RRW 1
!!
!!
!!
!! Node
: HPSG1 has 2 trunkboards
!!
!!
node
device
remote slc !!
!! Datalink
: HPSG1 PT38A001 700
0
!!
!! Datalink
: HPSG1 PT38A002 700
1
!!
!! Datalink
: HPSG1 PT38A003 700
2
!!
!! Datalink
: HPSG1 PT38A004 700
3
!!
!! Datalink
: HPSG1 PT38A005 700
4
!!
!! Datalink
: HPSG1 PT38A006 700
5
!!
!! Datalink
: HPSG1 PT38A007 700
6
!!
!! Datalink
: HPSG1 PT38A008 700
7
!!
!! Datalink
: HPSG1 PT38A009 700
8
!!
!! Datalink
: HPSG1 PT38A010 700
9
!!
!! Datalink
: HPSG1 PT38A011 700
10
!!
!! Datalink
: HPSG1 PT38A012 700
11
!!
!! Datalink
: HPSG1 PT38A013 700
12
!!
!! Datalink
: HPSG1 PT38A014 700
13
!!
!! Datalink
: HPSG1 PT38A015 700
14
!!
!! Datalink
: HPSG1 PT38A016 700
15
!!
!! Datalink
: HPSG1 PT38A101 701
0
!!
!! Datalink
: HPSG1 PT38A102 701
1
!!
!! Datalink
: HPSG1 PT38A103 701
2
!!
!! Datalink
: HPSG1 PT38A104 701
3
!!
!! Datalink
: HPSG1 PT38A105 701
4
!!
!! Datalink
: HPSG1 PT38A106 701
5
!!
!! Datalink
: HPSG1 PT38A107 701
6
!!
!! Datalink
: HPSG1 PT38A108 701
7
!!
!! Datalink
: HPSG1 PT38A109 701
8
!!
!! Datalink
: HPSG1 PT38A110 701
9
!!
!! Datalink
: HPSG1 PT38A111 701
10
!!
!! Datalink
: HPSG1 PT38A112 701
11
!!
!! Datalink
: HPSG1 PT38A113 701
12
!!
!! Datalink
: HPSG1 PT38A114 701
13
!!
!! Datalink
: HPSG1 PT38A115 701
14
!!
!! Datalink
: HPSG1 PT38A116 701
15
!!
46
!! Adjacent point codes

:
700
701
!!
!! Remote point codes
:
700
701
!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
create fep HPSG1 /opc=750 /nbbuff=10000
enable fep HPSG1
add fep HPSG1 /alias_pc_list=(600,601,602)
create fep HPSG1 mtp2
enable fep HPSG1 mtp2
create fep HPSG1 sccp
enable fep HPSG1 sccp
create fep HPSG1 sua
enable fep HPSG1 sua
!
create fep HPSG1 sua sgp 1 /fepname=HPSG1 /iplist=(10.10.1.6, 10.10.2.6 )
/port=14001
enable fep HPSG1 sua sgp 1
!
create fep HPSG1 sua asp 1 /iplist=(10.10.1.10 , 10.10.2.10)
enable fep HPSG1 sua asp 1
create fep HPSG1 sua asp 1 association 1 /sgp=1 /port=-1
enable fep HPSG1 sua asp 1 association 1
!
create fep HPSG1 sua asp 2 /iplist=(10.10.1.9, 10.10.2.9)
!
create fep HPSG1 sua destination 1008 /cpclist=(700,701) /rc=1008
enable fep HPSG1 sua destination 1008
create fep HPSG1 sua destination 1008 route 1 /rrw=1
enable fep HPSG1 sua destination 1008 route 1
!
!
!
!
create fep HPSG1 mtp2 trunk 1 /dev=PT38A0 /fep=HPSG1
enable fep HPSG1 mtp2 trunk 1
create fep HPSG1 mtp2 trunk 2 /dev=PT38A1 /fep=HPSG1 /E1CRC4=ON
enable fep HPSG1 mtp2 trunk 2
!
create fep HPSG1 mtp2 data_link 11 /dev=PT38A001 /fep=HPSG1
enable fep HPSG1 mtp2 data_link 11
47
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
!
create
enable
create
enable
create
enable
create
enable
48
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
16 /dev=PT38A006 /fep=HPSG1
16
17
18
19
110
111
112
113
114
115
116
21
22
23
24
25
26
27
28
29
210
211
212
213
214
215
216
fep
fep
fep
fep
fep
fep
fep
fep
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
destination 700 /ruleid=0

destination 700
linkset 1 /adj=700
linkset 1
linkset 1 link 0 /pln=11 /fep=HPSG1 /rank=0
linkset 1 link 0
linkset 1 link 1
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
!
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
linkset
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
link
link
link
link
link
link
link
link
link
link
link
link
link
link
link
link
link
link
link
link
link
link
link
link
link
link
link
link
2 /pln=13 /fep=HPSG1 /rank=2

2
3
4
5
6
7
8
9
10
11
12
13
14
15
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3

destination 701
linkset 2 /adj=701
linkset 2
linkset 2 link 0
linkset 2 link 1
linkset 2 link 2
linkset 2 link 3
linkset 2 link 4
linkset 2 link 5
linkset 2 link 6
linkset 2 link 7
linkset 2 link 8
linkset 2 link 9
linkset 2 link 10
linkset 2 link 11
linkset 2 link 12
linkset 2 link 13
linkset 2 link 14
49
create fep HPSG1 mtp3 linkset 2 link 15 /pln=216 /fep=HPSG1 /rank=15

enable fep HPSG1 mtp3 linkset 2 link 15
!
! Adjacent destinations
!
create fep HPSG1 mtp3 destination 700 route 1 /rank=0
enable fep HPSG1 mtp3 destination 700 route 1
!
!
! Remote destinations
!
do enaevt.s7mp
!
connect fep HPSG1
!
wait 15
!
init_link fep HPSG1 mtp2 data_link 11
!
activate fep HPSG1 mtp3 linkset 1
!
save_config
!
50
Example sua_rk.dat
###########################################################
## This file is generated on Mon Jun 14 11:38:23 2004
##
##
Using the startnewfep creator Jun 14 2004
##
pc=600; ssn=8; as=8;
pc=601; ssn=8; as=1008;
pc=602; ssn=8; as=2008;
igt="31654076001.*"; as=1008;
igt="31654076002.*"; as=2008;igt="31654076000.*"; as=8;
51
Example SS7_CONFIG.DAT for Distributed Platform on HSPG 1 & HPSG 2

[GIW_MSC_SGSN_ADDR]
! <smsc_gt>, <gt/pc>, <pc>, <nat_use>, <map_version>, <map_fllbck>, <tt>
31654076001,
GT,
601,
0,
2
31654076002,
GT,
602,
0,
2
31654076000,
GT,
600,
0,
2
0,
PC,
0,
0,
2
1,
PC,
0,
0,
2
2,
PC,
0,
0,
2
3,
PC,
0,
0,
2
4,
PC,
0,
0,
2
5,
PC,
0,
0,
2
6,
PC,
0,
0,
2
7,
PC,
0,
0,
2
8,
PC,
0,
0,
2
9,
PC,
0,
0,
2
!
[GIW_HLR_ADDR]
! <smsc_gt>, <gt/pc>, <pc>, <nat_use>, <map_version>, <map_fllbck>, <tt>
31654076001,
GT,
601,
0,
2
31654076002,
GT,
602,
0,
2
31654076000,
GT,
600,
0,
2
0,
PC,
0,
0,
2
1,
PC,
0,
0,
2
2,
PC,
0,
0,
2
3,
PC,
0,
0,
2
4,
PC,
0,
0,
2
5,
PC,
0,
0,
2
6,
PC,
0,
0,
2
7,
PC,
0,
0,
2
8,
PC,
0,
0,
2
9,
PC,
0,
0,
2
!
[GTT_RULES]
! Global title with(out) *, [GT] , PC1, [PC2]
!* 31653123*
, , 300 ! Service Center main address (VSMSC used)
!* 31653123456
, , 300 ! Service Center main address (no VSMSC used)
!31654008* , , 10
31653131* , , 266
31663131* , , 266, , , , , RGT
31673131* , , 266, , , , , RPC
!
[PLATFORM]
SMSC_PC, 750
! Mandatory
STACK_TYPE, ANSI
! IF ANSI then specify ANSI
E1CRC4,NO
! CRC check for DNB1/DNBT1 boards
APPLICATION,11
!
[SUA]
! ************************************
! ALIAS, ( PC, PC, ...)
! SGP, NR, PORT, ( IP , IP , ... )
! ASP, NR, ( IP , IP , ... )
! ASSOCIATION, NR, ASP_NR, SGP_NR, PORT
! DESTINATION, NR, RC, ROUTE ASP NR ,RRW, ROUTE ASP NR , RRW , ...
! ************************************
HPSG1
ALIAS,600,11,601,1011,602,2011
!
SGP, 1, 14002, (10.10.1.6, 10.10.2.6 )
!
ASP, 1, (10.10.1.10 , 10.10.2.10)
2004 LogicaCMG Preface
53
ASP, 2, (10.10.1.9, 10.10.2.9)

!
ASS, 1, 1, 1 , -1
ASS, 2, 2, 1 , -1
!
DES, 1011,1011,1,1
DES, 2011,2011,2,1
DES, 11, 11 , 1 , 1 , 2 ,1
!
HPSG2
SGP, 1, 14002, (10.10.1.7, 10.10.2.7 )
!
[DATA_LINK]
! Definition of all physical links
! <FEP name>, <Device name>, <Adjacent PointCode>, <SLC>
! SMXX13, SJA0, 9020, 0
! SMXX13, PT37A1, 9020 ,0
HPSG1, PT38A2,NODIV
HPSG1, PT38A201, 702, 0
HPSG1, PT38A202, 702, 1
HPSG1, PT38A203, 702, 2
HPSG1, PT38A204, 702, 3
HPSG1, PT38A205, 702, 4
HPSG1, PT38A206, 702, 5
HPSG1, PT38A207, 702, 6
HPSG1, PT38A208, 702, 7
!
HPSG2, PT38A2,NODIV
HPSG2, PT38A209, 702, 8
HPSG2, PT38A210, 702, 9
HPSG2, PT38A211, 702, 10
HPSG2, PT38A212, 702, 11
HPSG2, PT38A213, 702, 12
HPSG2, PT38A214, 702, 13
HPSG2, PT38A215, 702, 14
HPSG2, PT38A216, 702, 15
!
[REMOTE]
! All remote (not adjacent) PointCodes
! PC, rule, Adj (rank 0), Adj (rank 1)
702, 0, 702
Example fep_gen_c.s7mp for Distributed Platform on HSPG 1 & HPSG 2

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! This file is generated on Fri Aug 20 18:27:43 2004
!!
!!
Using the startnewfep creator Aug 20 2004
!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! SMSC point code
: 750
!!
!! National use indicator : 2
!!
!! ALIAS point code
: 600,601,602 !!
!! Applications (ssn)
: 11
!!
!! SGP 1
IP : (10.10.1.6, 10.10.2.6 ) PORT 14002
!!
!! ASP 1
IP : (10.10.1.10 , 10.10.2.10)
!!
!!
ASSOCIATION 1
SGP 1
!!
!! ASP 2
IP : (10.10.1.9, 10.10.2.9)
!!
!!
ASSOCIATION 2
SGP 1
!!
RRW 1
!!
RRW 1
!!
54
!! DESTINATION AS : 11
ASP 1
RRW 1 ASP 2
RRW 1
!!
!!
!!
!! Node
!!
!! Node
!!
!!
node
device
remote slc !!
!! Datalink
: HPSG1 PT38A201 702
0
!!
!! Datalink
: HPSG1 PT38A202 702
1
!!
!! Datalink
: HPSG1 PT38A203 702
2
!!
!! Datalink
: HPSG1 PT38A204 702
3
!!
!! Datalink
: HPSG1 PT38A205 702
4
!!
!! Datalink
: HPSG1 PT38A206 702
5
!!
!! Datalink
: HPSG1 PT38A207 702
6
!!
!! Datalink
: HPSG1 PT38A208 702
7
!!
!! Datalink
: HPSG2 PT38A209 702
8
!!
!! Datalink
: HPSG2 PT38A210 702
9
!!
!! Datalink
: HPSG2 PT38A211 702
10
!!
!! Datalink
: HPSG2 PT38A212 702
11
!!
!! Datalink
: HPSG2 PT38A213 702
12
!!
!! Datalink
: HPSG2 PT38A214 702
13
!!
!! Datalink
: HPSG2 PT38A215 702
14
!!
!! Datalink
: HPSG2 PT38A216 702
15
!!
!! Adjacent point codes
:
702
!!
!! Remote point codes
:
702
!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
enable fep HPSG1
!
create fep HPSG1 sua sgp 1 /fepname=HPSG1 /iplist=(10.10.1.6, 10.10.2.6 )
/port=14002
enable fep HPSG1 sua sgp 1
!
create fep HPSG1 sua asp 1 /iplist=(10.10.1.10 , 10.10.2.10)
!
create fep HPSG1 sua asp 2 /iplist=(10.10.1.9, 10.10.2.9)
!
create fep HPSG1 sua destination 1011 /cpclist=(702) /rc=1011
!
!
2004 LogicaCMG References
55
create
enable
create
enable
!
!
create
enable
create
enable
!
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
!
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
enable
create
56
fep
fep
fep
fep
HPSG1
HPSG1
HPSG1
HPSG1
sua
sua
sua
sua
destination
destination
destination
destination
11
11
11
11
route
route
route
route
1 /rrw=1
1
2 /rrw=1
2
fep
fep
fep
fep
HPSG1
HPSG1
HPSG1
HPSG1
mtp2
mtp2
mtp2
mtp2
trunk
trunk
trunk
trunk
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
fep
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
HPSG1
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3
mtp3

destination 702
linkset 1 /adj=702
linkset 1
linkset 1 link 0 /pln=31 /fep=HPSG1
linkset 1 link 0
linkset 1 link 1
linkset 1 link 2
linkset 1 link 3
linkset 1 link 4
linkset 1 link 5
linkset 1 link 6
1
2
31
32
33
34
35
36
37
38
39
310
311
312
313
314
315
316
/rank=0
/rank=1
/rank=2
/rank=3
/rank=4
/rank=5
/rank=6
/rank=7

!
!
!
!
do enaevt
!
connect fep HPSG1
!
wait 15
!
!
!
save_config
!
enable fep HPSG2
57
!
create fep HPSG2
/port=14002
enable fep HPSG2
!
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
!
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
!
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
!
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
!
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
!
!
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
!
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
create fep HPSG2
enable fep HPSG2
create fep HPSG2
58
sua sgp 1 /fepname=HPSG2 /iplist=(10.10.1.7, 10.10.2.7 )

sua sgp 1
sua
sua
sua
sua
asp
asp
asp
asp
1 /iplist=(10.10.1.10 , 10.10.2.10)
1
1 association 1 /sgp=1 /port=-1
1 association 1
sua
sua
sua
sua
asp
asp
asp
asp
2 /iplist=(10.10.1.9, 10.10.2.9)
2
2 association 2 /sgp=1 /port=-1
2 association 2
sua
sua
sua
sua
destination
destination
destination
destination
1011 /cpclist=(702) /rc=1011

1011
1011 route 1 /rrw=1
1011 route 1
sua
sua
sua
sua
destination
destination
destination
destination
2011 /cpclist=(702) /rc=2011

2011
2011 route 2 /rrw=1
2011 route 2
sua
sua
sua
sua
sua
sua
destination
destination
destination
destination
destination
destination
11
11
11
11
11
11
mtp2
mtp2
mtp2
mtp2
trunk
trunk
trunk
trunk
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
mtp2
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
data_link
/cpclist=(702) /rc=11
route
route
route
route
1 /rrw=1
1
2 /rrw=1
2
1
2
31
32
33
34
35
36
37
38
39
310
311
312

!
create fep HPSG2 mtp3 destination 702 /ruleid=0
enable fep HPSG2 mtp3 destination 702
create fep HPSG2 mtp3 linkset 1 /adj=702
enable fep HPSG2 mtp3 linkset 1
!
!
!
!
do enaevt.s7mp
!
connect fep HPSG2
!
wait 15
!
59
init_link fep HPSG2 mtp2 data_link

!
!
save_config
!
60
36
37
38
39
310
311
312
313
314
315
316
Abbreviations
AS
An Application Server (AS) is a logical entity, serving a specific

Routing Key.
ASP
An Application Server Process (ASP) is an IP-based instance of an

application server, such as Call Agents, HLRs, SMSCs, etc. An ASP
may implement more than one AS.
ATM
Asynchronous Transfer Mode
CdPA
The SCCP Called Party Address field.
CgPA
The SCCP Calling Party Address field.
GSM
ITU standard for defining the global system for mobile

communications.
GTT
Global Title Translation: A function normally performed in an STP.

GTT is the procedure by which the destination signalling point and
subsystem number (SSN) is determined from digits (i.e., the Global
Title) present in the signalling message.
IP-STG
IP STP Gateway of Hewlett Packard
IS-41
ANSI is a standard for defining the cellular radio telecommunications

intersystem operation. Unless otherwise stated, this refers to the IS41-D specification[3].
ITP
IP Transfer Point refers to the SS7 over IP routers, developed under

the Topsail Beach program and subsequent releases.
MAP
SS7 Mobile Application Part: This layer provides mobility procedures

to SS7 network applications. MAP is generically used to refer to both
GSM-MAP[2] and the IS-41-D MAP Protocol [3].
MO
Mobile Originated refer to an SMS being sent from an MS to the

SMSC.
MS
Mobile Subscriber.
MT
Mobile Terminated refers to an SMS being sent from an SMSC to an

MS.
MTP
Message Transfer Part - Layers 1 (physical), 2 (data), and 3 (network)

of the SS7 signalling protocol
MTP1
Level 1 of MTP, corresponding to the layer 1 of OSI model.
MTP2
MTP3
MTP3B
Level 3 of MTP, corresponding to the layer 3 of OSI model.(For ATM)
61
62
SCCP
Signalling Connection Control Part:. As part of the SS7 signalling

protocol, it provides connectionless and connection-oriented network
services above MTP Level 3.
SCP
Service Control Point: An element of an SS7-based Intelligent

Network, which performs various service functions, such as number
translation, call setup and tear down, etc.
SCTP
Stream Control Transmission Protocol: A protocol designed by the

Sitar working group of the IETF to transport messages reliably over IP
networks. It has been specifically designed with PSTN signalling in
mind, but is meant to be a general IP transport protocol.
SG
Signalling Gateway.
SME
Short Message Entity: An entity that may send or receive Short

Messages, and may be fixed or mobile.
SMS
Short Message Service, as defined in GSM[4] and IS-41-D[3]
SMSC
Short Message Service Centre: A Network element responsible for

relaying and store-and-forwarding of Short Messages.
SSP
Service Switching Point: Ann element of an SS7-based Intelligent

Network that performs call origination, termination or tandem
switching.
STP
Signal Transfer Point: An element of an SS7-based Intelligent

Network that performs routing of the SS7 signalling.
SUA
SS7 SCCP User Adaptation Layer specified by IETF SIGTRAN for

SCCP users, like GSM MAP, UMTS RANAP, CDMA IS-41, CDMA IS634, IN INAP and CAMEL CAP.
TCAP
Transaction Capability Application Part is the application layer of the

SS7 signalling protocol.
WRR
Weighted Round Robin: A variation of the round robin algorithm that

uses server weights to allow uneven distribution of traffic among a set
of available servers.
References
[HPSG Manual]
SUA SG v3.10 Documentation, March 2004
63
Version History
Version
Status
Date
Details of Changes
Author(s)
0.1
DRAFT
18 Dec 2003
Initial version
Imro Landveld
0.7
DRAFT
14 May 2004
Added trace tool
Rogier Goossens
0.8
DRAFT
27 May 2004
Added configuration tool
Ton Dennenbroek
0.9
DRAFT
14 Jul 2004
New template. Updated with

current HPSG BL2
configuration
Peter Vreman
0.10
DRAFT
15 Jul 2004
Technical Writers Review
Abdelkader Habri
0.11
Draft
30 July 2004
SNMP update
Ton Dennenbroek
0.12
proposed
1 aug 2004
GS reviewed
Ton Dennenbroek
0.13
proposed
17 aug 2004
Distributed configuration
Ton Dennenbroek
0.14
PROPOSED
2 sep 2004
Update after reviews by Imro

and Oscar vd Berg
Peter Vreman
1.0
APPROVED
3 sep 2004
Approved
Peter Vreman
Approval
Version
Date
Approved by
1.0
3 sep 2004
Peter Vreman
Signature

HPSG - Sip 1.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HPSG - Sip 1.0

Uploaded by

Copyright:

Available Formats

NextGen 1.

Installation and Configuration Guide

Copyright 2004 by LogicaCMG Wireless Networks

HPSG Stack Architecture.....................................................................................4

Fail-over HPSG configuration............................................................................................. 16

MIB file RedHat Linux.......................................................................................... 23

Configure trap filter............................................................................................................. 25

2004 LogicaCMG Table of Contents

Trace tool configuration...................................................................................................... 28

Using the trace tool............................................................................................................. 29

Monitoring and Tracing......................................................................................32

Manual tracing using CTF................................................................................................... 34

Check installed software:.................................................................................................... 35

Check network configuration:............................................................................................. 35

HP Signaling Gateway Installation and Configuration Guide 2004 LogicaCMG

Figure 2-1: HPSG stack architecture...................................................................................................... 4

2004 LogicaCMG Table of Contents

Table P-1: Typographic conventions...................................................................................................... ix

2004 LogicaCMG List of Tables

Manuals for the HPSG provided by HP.

Refers to a keyboard key, system

The directory data contains

Serves as a placeholder for variable

Use the file name <entity>.cfg for...

Refers the user to external

2004 LogicaCMG Preface

Click the Close button to

Emphasises a new word or term of

apply a style to the...

Denotes a Unix regular-user prompt for

Denotes a Unix super-user prompt for

Denotes an OpenVMS Digital

Denotes line continuation; the

Bridges two keystrokes that should be

If Ctrl-C does not work, use CtrlAlt-Del.

Denotes a note, a piece of text

Note that the system is usually...

$ search [.data]*.dat searchforthis

HP Signaling Gateway Installation and Configuration Guide 2004 LogicaCMG

The HP IP STG is a hardware and software SS7-over-IP (SS7oIP) solution. It provides a

<Product Name> <X,Y> Version 1.0

HPSG Stack Architecture

Figure 2-1: HPSG stack architecture

HP Signaling Gateway Installation and Configuration Guide 2004 LogicaCMG

3.2 Example configuration

Figure 3-2: Example AS, ASP and associations

2004 LogicaCMG Tru64 OS configuration

Unique PLMN address = 31654076002

Figure 3-3: Example of network configuration

Two associations (ASS)

HP Signaling Gateway Installation and Configuration Guide 2004 LogicaCMG

Routing on Point Code to PC-601, uses AS 1008

Figure 3-4: Example SUA section from ss7_config.dat

3.3 Configuring HPSG

Create platform configuration file with the GOLD script SS7_CREATE_STARTNEWFEP.

The following steps must be performed on each HPSG:

Create the SS7 platform with ss7configure

Check and modify the gtt_rule.s7mp file

Check the sua_rk_gt.dat file

Start the SS7 platform

2004 LogicaCMG Tru64 OS configuration

Compile the routing key file

In S7MP menu, run the platform configuration script