ITP STANDARD INSTALLATION

PROCEDURE

Version: 1.1
Status: APPROVED
Author: Imro Landveld

Table of Contents

1.
2.
3.
4.
5.
6.
7.

Introduction......................................................................................................... 5
Cisco ITP Image.............................................................................................. 7
CMG/Cisco deployment..............................................................................9
ITP Stack Architecture...............................................................................10
GENERAL ITP SETTINGS......................................................................11
GENERAL SS7 SETTINGS....................................................................11
SS7 Layers....................................................................................................... 12

7.1
7.2
7.3

CONTOLLER AND INTERFACE CONFIGURATION (MTP1 and IP Layer)............12

DEFINING DATALINKS (MTP2 Layer)....................................................................13
DEFINING LINKSETS (MTP3 Layer)......................................................................13

8.
9.
10.
11.

Enabling an ATM Interface......................................................................14

Association CONFIGURATION (SCTP and SUA Layer).......15
GTT SELECTOR (SCCP layer).........................................................16
Multi-layer SMS Routing Triggers.....................................................17

9.3
9.4
9.5

Global Configuration............................................................................................... 17
Multi-layer SMS Routing Table................................................................................17
Destination SMSC Selection...................................................................................17

12. Monitoring the ITP.....................................................................................18

13. ITP image update.......................................................................................21
14. References.................................................................................................... 22

ii

Preface
Purpose
This document can be used as guideline to configure the Cisco ITP.
Audience
This document is intended for engineers who are expected to be familiar with the SMSC and need to
connect it to the ITP.
Scope
This document is intended to be a user guide to configure the Cisco ITP.
Organisation
This document is divided into nine chapters:

Chapter 1 Abbreviation.

Chapter 2-11 focuses on configuration of the ITP.

Chapter 12-13 handles Monitoring and Image Update.

iii

Typographic Conventions
In this document, the following typographic conventions are used.
Table P-1: Typographic conventions
Typeface or
Symbol

Courier

<courier>

Ctrl
Italic
[]
\

Meaning

Thenamesofcommands,
files,directories;computer
output
Placeholderforvariabletext;
mustbereplacedbyan
appropriatevaluewhichis
explainedinthetext
PresstheControlkeyandthe
letterfollowingit
simultaneously
Newwordsorterms
requiringemphasis
Referencetoexternal
documentation,listedin
Referenceschapter.
Usedtospecifyline
continuation;ignorethem
whenyoutypetheexample
andpressReturnonlyafter
thelastline.

Example

Thedirectorysmsc$root:
[srcref]contains
Type:
$type<file>
Where<file>isthe
configurationfile.
TypeCtrlYtocancelthe
operation.
Thenewnumberportability
isequivalentto
[REQUIREMENTS]
PML>CREATESMHEN\
SMH00/NOD=SMSC1

iv

1. Introduction
Cisco IP Transfer Point (ITP) is a hardware and software SS7-over-IP (SS7oIP) solution. ITP provides
a highly reliable, cost effective medium for migrating Signaling System 7 (SS7), the telecommunications

network signaling technology, to the mobile wireless industry IP environment.

Acronyms, and terms that may not be readily understood.

AAL5

ATM adaptation layer 5.(physical)

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

AsynchronousTransferMode

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 signaling point and subsystem number (SSN)
is determined from digits (i.e., the global title) present in the signaling message.

IS-41

ANSI standard for defining cellular radio telecommunications intersystem operation. Unless otherwise
stated, this refers to the IS-41-D specification[3].

ITP

IP Transfer Point. The term used to refer 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].

MBR

MAP-Based Routing or Multi-layer Routing.

MIN

Mobile Identification Number. The 10-digit North American Numbering Plan number assigned to mobile
users in IS-41 networks.

MO

Mobile Originated. This term is used to refer to an SMS message that is being sent from an MS to the
SMSC.

MS

Mobile Subscriber.

MT

Mobile Terminated. This term is used to refer to an SMS message that is being sent from an SMSC to an
MS.

MTP

Message Transfer Part Layers 1 (physical), 2 (data), and 3 (network) of the SS7 signaling protocol

MTP1

Level 1 of MTP, corresponding to the layer 1 of OSI model.

MTP2

Level 2 of MTP, corresponding to the layer 2 of OSI model.

MTP3

Level 3 of MTP, corresponding to the layer 3 of OSI model.

MTP3B

Level 3 of MTP, corresponding to the layer 3 of OSI model.(For ATM)

M2PA

SS7 MTP2-User Peer-to-Peer Adaptation Layer specified by the IETF SIGTRAN working group, which
provides SCTP/IP based links for MTP3.

M3UA

SS7 MTP3 User Adaptation Layer specified by IETF SIGTRAN working group for MTP3 users like ISUP.

NNI

NetworkNodeInterface.(InATMnetwork)

PVC

Permanent Virtual Channel

QSAAL

Signalling ATM Adaption Layer , specified in ITU Q.2100 "ATM Adaptation Layer for Signalling (SAAL)" that
provides reliable transport of signalling messages (Q.2931) between peer Q.2931 entities. These signalling
messages are carried over a PVC.

RR
RSP

Round Robin. A balancing algorithm that evenly distributes traffic among available servers.
Route Switch Processor . Processor board of the ITP

SCCP

Signaling Connection Control Part. As part of the SS7 signaling protocol, it provides connectionless and
connection-oriented network services above MTP Level 3.

SCCOP

Service Specific Connection Oriented Protocol

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 SigTran working group of the IETF to
transport messages reliably over IP networks. It has been specifically designed with PSTN signaling in
mind, but is meant to be a general IP transport protocol.

SG

Signaling 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 Center. Network element responsible for relaying and store-and-forwarding of short
messages.

SSCF-NNI

.SSCOPisareliabletransportsessionof
signalingmessagesexchangedbetweentwosignalingpeersoneachsideofthelink.(In
ATMnetwork)

Service Specific Coordination Function for the support of signaling at the NNI. SSCF allows the UNI

Layer to start/stop an SSCOP session and to send/receive signaling messages. (In ATM
network)
SSP

Service Switching Point. An 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
signaling.

SUA

SS7 SCCP User Adaptation Layer specified by IETF SIGTRAN for SCCP users, like GSM MAP, UMTS
RANAP, CDMA IS-41, CDMA IS-634, IN INAP, CAMEL CAP.

TCAP

Transaction Capability Application Part. The application layer of the SS7 signaling 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.

2. Cisco ITP Image

26XX
1500 MSU/sec SS7
4 links

72XX
6500 MSU/sec SS7
24 links

73XX
6000 MSU/sec SS7
126 links

75XX
30000 MSU/sec SS7
10000 MSU/sec SUA
720 links

Note: download from the Solution SIP CD, image MBxx to the ITP

A TFTP server is needed to download the image to the ITP. Use the Cisco TFTPserver toolpackage
(TFTPSERV.EXE) to install on a Windows PC.
A Cisco console cable (flat black or blue cable with a DB9 connector and RJ45 plug) is needed for a serial
connection between a PC and the ITP for first time configuration.
A Crosscable must be available for ethernet connection between PC and ITP .

Step 1: Install a TFTP Server

A Trival File Transfer Protocol (TFTP) server or a Remote Copy Protocol (RCP) server application must be
installed on a TCP/IP-ready workstation or PC. Once the application is installed, a minimal level of configuration
must be performed.
1. The TFTP application must be configured to operate as a TFTP server as opposed to a TFTP client.
2. The outbound file directory must be specified. This is the directory in which the Cisco IOS software
images are stored (see step 2 below). Most TFTP applications provide a set-up routine to assist in these
configuration tasks.
Note: A number of TFTP or RCP applications are available from independent software vendors or as
shareware from public sources on the World Wide Web.
Cisco IOS TFTP client
The Cisco IOS TFTP client requests the image several times and each time the transfer is started over, you see
state errors or other errors on your TFTP server. State errors on the TFTP server are perfectly normal. The TFTP
client checks to make sure the file is valid for that platform and that the file system it is being saved to has
enough space. The transfer is stopped to do those checks. This is transparent to the person on the router, but the
TFTP server may print errors about this. If a Failed (State Error) is reported by the TFTP server software while
upgrading the Cisco IOS software, and the Cisco IOS software file transfer is successfully completed, then this is
due to a cosmetic software bug and can be safely ignored.
If a Failed (State Error) is reported while using the Cisco TFTP server software and the Cisco IOS software file
transfer cannot be completed, the TFTP server software may be crashing. If this happens, on the TFTP server
software, go to "View" and then "Options". Unselect the "show file transfer progress" and unselect "enable
logging". Then try the file transfer again.

Figure 1 TFTP Server example

.Step 2: Download the Cisco IOS Software Image
Make shure that the image is in the TFTP server root directory.
Download the Cisco IOS Software images from the PC to the ITP with the command:
# copy tftp: image_name
Use IP-address of the PC if the tool request for a host name

3. CMG/Cisco deployment

E.164 = 31654077000
Global Address

SCTP
association
SS7 link

AS-SMSC1
E.164 = 31654075000
Unique Address

FEP1

10.10.10.111
Linkset mgts-hlr PC 600

ITP1

10.10.10.50

SS7

PC = 750
Linkset mgts-msc PC 700

AS-SMSC2
E.164 = 31654076000
Unique Address

10.10.10.211

FEP2
10.10.10.51

Figure 2- CMG/Cisco deployment

Figure 2 shows the CMG SMSC with two FEPs and one ITP. The SMSC is communicating with a Mobile Switching Center
(MSC) via the ITP.
The SMSC is addressed by the MSC using the global E.164 address. Each FEP can also individually be addressed via its
own unique E.164 address.
In the ITP configuration each FEP is represented by an ASP (named FEPx). The SMSC is represented in this example by two
ASes. One AS can consist of one or more ASPs for load balancing new TCAP transactions between the FEPs. Each FEP is
represented in this example by an AS (named AS-SMSCx) for the direct routing of messages associated with existing TCAP
transactions.
In the ITP configuration, AS-SMSCx is defined with a routing key comprised an SS7 point code (PC) and subsystem number
(SSN) and includes one or more FEP ASPs. The ITP will have a global title translation (GTT) table entry that maps E.164
address to PC and SSN. Representing the SMSC with a PC+SSN allows the ITP to advertise the SMSC state to other
network nodes (concerned point codes).
The definition of each FEP AS will have a routing key of global title and will only include that FEPs ASP. There will be a GTT
table entry that maps each FEP E.164 address to the FEPs AS name.
Below is a step-by-step configuration of the ITP associated with the scenario described above:

4. ITP Stack Architecture

Multi Layer Routing
Send back to SCCP for Routing
Route Determination
MO SMS Parsing
MAP Parsing
TCAP Parsing

SCCP

SUA
GTT

TRIGGER

M3UA

MTP3 / MTP3b
SSCF-NNI

MTP2

M2PA
SCTP

SCCOP
AAL5

MTP1

IP

MTP3b Stack

SoIP Stacks
SS7 Stack

Figure 3 - ITP Stack Architecture

The layers in Figure 3 - ITP Stack Architecture will be used to explain the configuration of the ITP. First a summary of the
basic input information is given, followed by layer configuration, starting with hardware (AAL5, MTP1 and IP).

The following informations are needed to configure the ITP:

SMSC
Number of SMSCs and IP7 entities, to determine the number of ASs and ASPs.
Local port and address of the SMSC, needed for association setup with ITP.
Remote port and address of the ITP, needed for association setup with ITP.
Global SMSC address, for Global Title Translation (GTT).
Unique SMSC address, for GTT incase more then one SMSC is involve.
ITP
ITP model (2651, 7204/6, 7507/13), for controller and interface
SS7 flavor, (ANSI, ITU, CHINA)
Name of ITP to be configured
Location of the hardware Interfaces and Controllers in the cabinet
Point code(s) of the ITP (Primary, Secondary, and incase of mated pair also Capability PC)
IP addresses of the ITP
Local/Destination SUA ports to be used (value between 1024 and 65535)
SS7
Dependent on the capacity planning the following is needed:
Number of links
Number of linksets
Adjacent STP Point codes (Needed for defining routes)
Destination Point codes
The commands in the diagrams below are the same as entered in the configuration mode.
To enter the configuration mode, type conf term at the prompt.
To exit a sub mode, type, exit

10

The question mark (?) may be used for help on commands.

5. GENERAL ITP SETTINGS

In this section, settings are described that are needed to manage the ITP.
Once this configuration is done, via the Console port, telnet sessions can be made to manage the ITP.

service timestamps debug datetime msec localtime

service timestamps log datetime msec localtime
no service password-encryption
no service single-slot-reload-enable
!
hostname ITP7507
(example of hostname)
!
boot system flash disk0:rsp-itpv-mz.030313 (Load a given ITP image)
no logging console
(Do not log to console)
enable password secret
(Management password)
!
ip subnet-zero
ip cef
ip classless
ip route 0.0.0.0 0.0.0.0 10.132.15.1
(IP default gateway,if needed)
no ip http server
ip pim bidir-enable
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
exec-timeout 0 0
password secret
login
!
!
no ip domain-lookup

Figure 4 - ITP General information

6. GENERAL SS7 SETTINGS

In this section, the SS7 flavor and related items are configured.
Once this is done, this router behaves as an ITP.
The secondary-pc is only needed if the ITP, and also the SMSC, should be reachable via two Point Codes.
In case of mated pair, there should be a capability-pc

!
cs7 variant ITU
cs7 network-name LogicaCMG SS7oIP
cs7 point-code format 14
cs7 point-code 750
! cs7 secondary-pc 751
! cs7 capability-pc 850

(ANSI,ITU,CHINA)
(14 for ITU
(Point code
(If needed,
(In case of

, 24 for ANSI)
of ITP)
a secondary-pc may be configured)
mated pair)

Figure 5 - General SS7 settings

11

7. SS7 Layers
To put a link in service, the following steps must be followed:
1 Controller and Interface configuration
1.1
Low Speed Link Serial or Channelized
(MTP2 Encapsulation)
1.2
High speed Link ATM Unchannelized
(QSAAL Encapsulation)
2 Defining Links
3 Defining Linksets
4 Assigning Links to to Linksets

7.1 CONTOLLER AND INTERFACE CONFIGURATION (MTP1 and IP Layer)

This section describes the configuration of E1 controllers and Ethernet interfaces.
One E1 controller consists of 8 ports. The example shows one E1 in a Cisco 7507 controller with the numbering format
slot/Bay/Port. The 7301 has the format Slot/Port
In case of the Cisco 2651 the numbering can be fond on the rear of the node.
Channel groups are defined and a timeslot assigned to each.
For each configured channel-group, a (logical) Serial interface is generated which correspond with an SS7 Link. see Figure 7 ITP serial configuration

!For the 7507

card type E1 1 0

!for

(Assign slot 1 bay 0 to controller E1)

the 7301

card type E1 1
(Assign slot 1
to controller E1)
!
!-------- MTP1 or AAL5-----------!
controller E1 1/0/0
(Slot 1, PA Bay 0, E1 controller port 0)
framing NO-CRC4
clock source internal
channel-group 0 timeslots 1
(timeslot 1 )
channel-group 1 timeslots 2
!......upto and including.........
channel-group 15 timeslots 16
!
!
controller E1 1/0/1
(Slot 1, PA Bay 0, E1 controller port 1)
framing NO-CRC4
clock source internal
channel-group 0 timeslots 1
(group for timeslot 1 needed for assigning to a link)
channel-group 1 timeslots 2
!......upto and including.........
channel-group 15 timeslots 16
!
!
!-------- IP -------------!
interface FastEthernet1/1/0
(Slot 1, PA Bay 1, FastEthernet Interface port 0)
ip address 10.10.10.111 255.255.225.128
full-duplex
!
!
interface FastEthernet4/0/0
(Slot 4, PA Bay 0, FastEthernet Interface port 0)
ip address 10.10.10.211 255.255.255.128
full-duplex
!

Figure 6 - ITP hardware configuration

12

7.2 DEFINING DATALINKS (MTP2 Layer)

The ITP supports SS7 links over serial interfaces on the router. MTP2 encapsulation must be set on the
entire serial interface. Each serial interface corresponds with a SS7 Link.
The example below show the configuration of 16 Serial Interfaces per E1 port on the Cisco 7507.
If all eight ports of this E1 are configured (Figure 6 - ITP hardware configuration), there should also be eight sets of Serial
Interfaces.
interface Serial1/0/0:0

(Serial interface for timeslot 1 on controller E1 1/0/0

generated at the configuration of channel-group 0)

no ip address
encapsulation mtp2
!
interface Serial1/0/0:1
no ip address
encapsulation mtp2
!....upto and including......
interface Serial1/0/0:15

(Serial interface for timeslot 15 of controller E1 1/0/0

generated at the configuration of channel-group 15)

no ip address
encapsulation mtp2
!
!-------------------------------!
interface Serial1/0/1:0
(Serial interface for timeslot 1 of controller E1 1/0/1)
no ip address
encapsulation mtp2
!
interface Serial1/0/1:1
no ip address
encapsulation mtp2
!....upto and including.....
interface Serial1/0/1:15
(Serial interface for timeslot 15 of controller E1 1/0/1)
no ip address
encapsulation mtp2
!

Figure 7 - ITP serial configuration

7.3 DEFINING LINKSETS (MTP3 Layer)

Dependent on capacity planning, the number of linksets should be configured.
This example shows two linksets with up to 16 links.
Each link in a linkset is assigned to one (logical) Serial Interface (Figure 7 - ITP serial configuration).
cs7 linkset mgts-msc 700

(Linkset, named mgts-msc with pointcode 700)

accounting
link 0 Serial1/0/0:0
(Timeslot 1 is assigned to link 0)
link 1 Serial1/0/0:1
!......upto and including.....
link 15 Serial1/0/0:15
(Timeslot 16 is assigned to link 15)
!
!------------------------------!
cs7 linkset mgts-hlr 600
accounting
link 0 Serial1/0/1:0
link 1 Serial1/0/1:1
!......upto and including.....
link 15 Serial1/0/1:15
!

Figure 8 - Linkset configuration

See Figure 15 monitoring SS7 links how to monitor SS7 links
13

8. Enabling an ATM Interface

To enable an ATM interface for HSL, use the following commands, beginning in global configuration mode:

!
interface atm Slot/Bay/Port
no shutdown
framing esfadm
framing crc4adm

(T1 only)
(E1 only)

clock source internal

pvc name 0/5 qsaal

atm nni
!
!
cs7 linkset LINKSETNAME
link 0 atm-name Slot/Bay/Port

Figure 9 ATM Interface configuration

14

9. Association CONFIGURATION (SCTP and SUA Layer)

For the SMSC to be able to setup an association, a SUA port on the ITP must be configured. Figure
An Application Server (AS) is a logical entity serving a specific application instance. The AS contains a set of one or
more unique Application Server Processes (ASP), of which one or more is normally actively processing traffic. An AS could be
an SMSC an ASP the IP7 entity.
An ASP is a process instance of an Application Server. Serves as an active or standby process of an AS. An ASP
contains an SCTP end-point. The AS use a routing key to route SS7 messages to the appropriate AS. Within the ASP, the
remote-ip address should be defined. For the remote process, this is the IP-Address of the ITP.(Figure 2- CMG/Cisco
deployment)
The routing key consist of:
Routing-Context (mandotory) with
DPC (mandatory)
OPC (range)
SI SCCP (mandatory)
SSN
or
Routing-Context (mandotory) with
GTT
The Traffic-mode is set to loadshare traffic between the ASPs.

cs7 sua 7501

(SUA Local Port)
local-ip 10.10.10.111
(SUA Localip address)
cumulative-sack 500
(Cumulative selective acknowledgment time-out value, in milliseconds.)
tx-queue-depth 10000
(Number of packets to be queued.)
!
cs7 sua 7502
local-ip 10.10.10.211
cumulative-sack 500
tx-queue-depth 10000
!
!------------- ASP -------------!
cs7 asp FEP1 7501 7501 sua
(ASP with Local and Remote port)
remote-ip 10.10.10.50
(Remote-ip of ASP)
!
cs7 asp FEP2 7502 7502 sua
remote-ip 10.10.10.51
!
!------------- AS --------------!
cs7 as AS-SMSC sua
(Applicatio Server)
!routing-key 100 500 si sccp ssn 8
(key to route to SMSC with PC 500)
routing-key 100 gtt
(Loadshare to all SMSCs)
asp FEP1
asp FEP2
traffic-mode loadshare roundrobin
!
!

Figure 10 - SUA Port, ASP, AS

See also Figure 13 monitoring AS and ASP and Figure 14 monitoring
ASP and associations.

how to monitor ASs,

The whole configuration can be checked by typing, on the ITP, the command:

sho running-config
This config must be saved for the ITP to bootup the next time with these new settings:

Copy running-config startup-config

or

write memory

15

10.

GTT SELECTOR (SCCP layer)

A Selector is a set of specific values of parameters within the MSU that is used to decide which GTT table to use for the
translation. Only one Selector is allowed
The selector consist of:
Translation Type (TT)
Global Title Indicator (GTI)
Numbering Plan (NP)
Nature of Address Indicator (NAI)
In Figure 2- CMG/Cisco deployment GTAs are defined to the point code 600 and 700.
For messages to the SMSCs, there is one GTA to the Global SMSC Address. The ITP will loadshre between the AS-SMSCx
defined in the application group.
For acknowledgement and dedicated messages, GTAs are defined to both ASs.
Note: Save the gtt-table (localy or on a tftp-node) for auto load when it boots up:
CS7 SAVE GTT-TABLE DISK0:/GTT-TABLE

SS7oIP(config)# (configuration mode)

cs7 gtt selector E164SEL tt 0 gti 4 np 1 nai 4 (first time ITU configuration)
!cs7 gtt selector ANSISEL tt 10 gti 2
(example of ANSI configuration)
!
cs7 gtt selector E164SEL
(when updating ITU selector)
!
gta 31123456789 pcssn
600 gt
(GTT to pointcoide )
gta 319876
pcssn
700 gt
(using wild card)
!
gta 31654075000 asname
AS-SMSC gt
(GTT to asname)
gta 31654076000 asname
AS-SMSC gt
!
gta 31654077000 app-grp
LOADSHARE
(GTT to application group)
example how to configure applicationgroup:
ITP2651(config)#cs7 gtt app LOADSHARE
ITP26(config-cs7-gtt-app-grp)#asname AS-SMSC1 2 gt
ITP26(config-cs7-gtt-app-grp)#asname AS-SMSC2 1 gt
!Auto load of GTT Table
!*****************************************************
cs7 gtt load disk0:/config/gtt-table execute
!

Figure 11 - GTT Table

The example below shows how to load a GTT-Table and how to create routes to a destination node.
Pointcode 801 is reachable via linkset mgts_msc
Pointcode 601 is reachable via linkset mgts_hlr
The number 14 in 801/14 correspond with the point-code format of ITU. In case of ANSI, this would be
24.
Note: Save the route-table (localy or on a tftp-node) for auto load when it boots up:
CS7 SAVE ROUTE-TABLE DISK0:/ROUTE-TABLE
!*****************************************************
!Auto load of Route Table
!*****************************************************
cs7 route-table system
update route 801/14 linkset mgts_msc
update route 601/14 linkset mgts_hlr
load disk0:/route-table
!

16

11.

Multi-layer SMS Routing Triggers

High performance routing of legacy SS7 traffic is required to run in conjunction with the Multi-layer SMS routing
feature. In order to achieve this, a mechanism is needed which restricts parsing of packets to the TCAP, MAP and
MAP-user layers to only those packets requiring Multi-layer SMS routing. Routing triggers, or keys, identify SS7
networking layer (e.g., SCCP) parameters that can be quickly accessed to determine if further Multi-layer SMS
routing is required.
Figure 3 - ITP Stack Architecture, depicts the SCCP interception point for all SMS MO traffic received into the ITP.
Once triggered, the remainder of the packet will be parsed and the SMS routing table access performed.

9.3

Global Configuration

All traffic received will be checked for Multi-layer SMS routing, provided that a routing table is defined.

9.4

Multi-layer SMS Routing Table

The multi-layer SMS routing table contains the information necessary to efficiently route GSM SMS-MO messages.
The table contains a set of triggers, which identify the SCCP-network layer parameters. Each specified trigger
contains a set of rules that identify a set of input SMS-MO messages, and identify the resulting destination SMSC
that will process the message. The rules specify all the SMS-MO routing parameters found above the network layer.

9.5

Destination SMSC Selection

A match in the multi-layer routing table will map to one of the following:

A single point-code.
A global title address. Upon selection, the SCCP global title translation function will be invoked for the
specified address. This address may then map to an application group consisting of multiple destinations.
An M3UA or SUA application server name. Upon selection, the message is routed to the AS which may be
composed of multiple ASPs.
A multi-layer result table. This table will provide the set of possible results along with the associated
algorithm used to select among the results. This table is independent of the global title translation function,
but uses PC and SSN state to route to available destinations.

A weighted round-robin (WRR) distribution algorithm will be implemented in order to properly balance SMS workload to
servers of varying capacity. Each server within a result group (i.e., application group or multi-layer result table) is assigned a
server weight from 0 to 10. The value of 0 indicates that the server is a backup, and should only be used when all of the
servers in the group with a non-zero weight have failed.

cs7 mlr result as-group

(Result group)
asname AS-SMSC1 weight 10
asname AS-SMSC2 weight 2
!
cs7 mlr ruleset load-share
(Set of rules)
rule 1 sms-mo default
result group as-group
!
cs7 mlr table sms-router
trigger cdpa gt 31654076000 tt 0 gti 4 np 1 nai 4 ruleset load-share
Figure 12 MLR example

17

12.

Monitoring the ITP

After configuring SUA on the ITP, associations can be setup towards it.
This figure shows the state of the ASPs and some detailed information of one of them.
The numbers 3 and 4 in the SCTP column are the associations ID.
ITP7507#sho cs7 asp
ASP Name
-----------FEP1
FEP1

AS Name
-----------AS-SMSC1
AS-SMSC2

State
-------------active
inactive

Type
---SUA
SUA

Effect Primary
Rmt Port Remote IP Addr SCTP
-------- --------------- ---7501
10.10.10.50
4
8001
10.10.10.51
3

ITP7507#sho cs7 as
AS Name
-----------AS-SMSC1
AS-SMSC2

Routing
State
Context
------ ---------active 100
down
400

ITP7507#sho cs7 sua 7501

Sigtran SUA draft version: 14
SUA Local port: 7501
State: active
SCTP instance handle: 2
Local ip address:
10.10.10.111
Number of active SUA peers:
1
Max number of inbound streams allowed:
17
Local receive window:
64000
Max init retransmissions:
8
Max init timeout:
1000 ms
Unordered priority:
equal
SCTP defaults for new associations
Transmit queue depth:
10000
Cumulative sack timeout:
500 ms
Assoc retransmissions: 10
Path retransmissions:
4
Minimum RTO:
1000 ms
Maximum RTO:
1000 ms
Bundle status:
on
Bundle timeout:
5 ms
Keep alive status:
true
Keep alive timeout:
30000 ms

Figure 13 monitoring AS and ASP

18

Execute the following commands for more detail on associations

ITP7507#sho ip sctp assoc list
** SCTP Association List count: 2
AssocID: 3, SourceID: 3 Instance ID: 5
Current state: ESTABLISHED Uptime: 21:11:30.632
Local port: 8001, Addrs: 10.10.10.111
Remote port: 8001, Addrs: 10.10.10.51
AssocID: 4, SourceID: 4 Instance ID: 2
Current state: ESTABLISHED Uptime: 21:11:29.028
Local port: 7501, Addrs: 10.10.10.111
Remote port: 7501, Addrs: 10.10.10.50

ITP7507#sho ip sctp assoc param 4

** SCTP Association Parameters **
AssocID: 4, SourceID: 4 Instance ID: 2
Assoc state: ESTABLISHED Context: 1654684580 Uptime: 21:11:33.900
Local port: 7501
Local addresses: 10.10.10.111
Remote port: 7501
Primary dest addr: 10.10.10.50
Effective primary dest addr: 10.10.10.50
Destination addresses:
10.10.10.50
State: ACTIVE
Heartbeats: Enabled
Timeout: 30000 ms
RTO/RTT/SRTT: 1000/0/0 ms
TOS: 0 MTU: 1500
cwnd: 3032 ssthresh: 64000 outstand: 0
Num retrans: 0 Max retrans: 4 Num times failed: 0
10.10.10.111 retrans: 0
Local vertag: 6895F72E Remote vertag: 1468DA8A
Num inbound streams: 17 outbound streams: 2
Max assoc retrans: 10 Max init retrans: 8
CumSack timeout: 500 ms Bundle timeout: 5 ms
Min RTO: 1000 ms Max RTO: 1000 ms
LocalRwnd: 64000 Low: 63984
RemoteRwnd: 64000 Low: 63976
Congest levels: 4 current level: 0 high mark: 3 cksum type: crc32

Figure 14 monitoring associations

19

To check the state and traffic on SS7 links, execute the commands in Figure 15 monitoring
SS7 links
ITP7507#show cs7 linkset
lsn=smlg22
apc=701
SLC Interface
00
Serial1/0/1:0
01
Serial1/0/1:1

state=avail
Service
PeerState
avail
--------avail
---------

avail/links=16/16
Inhib
---------

lsn=ITP2651
SLC Interface
00
Serial1/0/4:1

state=avail
Service
PeerState
avail
---------

avail/links=1/1
Inhib
-----

apc=850

ITP7507#sho cs7 linkset brief

lsn=smlg22
apc=701
lsn=ITP2651
apc=850

state=avail
state=avail

avail/links=16/16
avail/links=1/1

ITP7507#show cs7 link utilization

lsn=smlg21
apc=700
state=avail
avail/links=1/1
Link Utilization Thresholds Plan-capacity
Kbps
SLC Rec Sent
Rec Sent Rec
Sent
Rec
Sent
0
5
5
40
40
64
64
3
3
0
all
5
5
--- --64
64
3
3 --ITP7507#sho cs7 linkset routes
lsn=ITP2651
apc=850

state=avail

avail/links=1/1

Destination
Cong Prio QoS Route
Route Table
-------------------- ---- ---- --- ------- ------------------700/24
RESTR
5
avail
system
850/24
acces
1
avail
system

Figure 15 monitoring SS7 links

For SS7 monitoring of the ITP at a glance, perform the command in Figure 16 SS7 monitoring
ITP7507#sho cs7
Point Code
SS7 Variant
Network Indicator
Network Name
GTT Load URL

750
ITU
national
'LogicaCMG SS7oIP'
disk0:/gtt-table

MTP3 Restart status

Total Linksets
Available Linksets
Total Links

Completed
2
2
2

Figure 16 SS7 monitoring at a glance

20

13.

ITP image update

11.1 Check Redundancy

ITP7507#show redundancy
Operating mode is simplex
redundancy mode hsa
Active in slot 2
Standby in slot 3
The system total uptime since last reboot is 3 hours 56 minutes.
The system has experienced 0 switchovers.
11.2 Configuring RSP Redundancy (RPR+)
Specifying the Redundancy Mode
itp(config)# redundancy
itp(config-red)# rpr-plus
Specifiying the image name for primary and seconary
itp(config)# hw-module slot 2 image slot0:<image-name>
itp(config)# hw-module slot 3 image slot0:<image-name>
11.3 Check Redundancy
itp#sh redundancy
Operating mode is rpr-plus
redundancy mode rpr-plus
hw-module slot 2 image slot0:rsp-itpv-mz.122-4.MB10
hw-module slot 3 image slot0:rsp-itpv-mz.122-4.MB10
Active in slot 2
Standby in slot 3
The system total uptime since last reboot is 3 hours 56 minutes.
The system has experienced 0 switchovers.
11.4 Image replacement of Secondary RSP
a. Check what RSP is currently active
itp# show redundancy
b. Replace the non active RSP Images on both master and slave flashes need to be the same
itp# dir slot0:
itp# dir slaveslot0:
itp# copy slot0:image_name slaveslot0: image_name
c. Make sure the ITP boots on the right file on Flash
itp(config)# hw-module slot 3 image slot0:rsp-itpv-mz.122-4.MB10
itp# copy running-config startup-config
d. Reset the slave RSP
itp# hw-module sec-cpu reset
e.

Switch control to secondary RSP

itp# redundancy force-switchover

f. Reset the primary RSP
itp# hw-module prim-cpu reset

21

14.

References

[1]CiscoITPownershipdirectory.\\nlattp1sfs3\sys\project\smsc\intern\SMSCOwnership\Areasof
Expertise\hardware\Cisco_ITP

[2]Ciscosite.http://www.cisco.com
[3]SS7oIPdirectory.\\nlattp1sfs3\sys\project\smsc\intern\teamsouth\ProjectSS7OverIP\08.project
deliverables\03.approveddocuments
[4]ITPDataSheet,http://www.cisco.com/warp/public/cc/pd/witc/itp/prodlit/ttip_ds.htm

22

Version History
Version

Date

Details of Changes

Author(s)

0.1
0.2
0.3

09-Mar-2003
15Mar2003
18Apr2003

Imro Landveld
ImroLandveld
ImroLandveld

1.0

22Apr2003

Initial version
Updatedversion
Finalversionfollowingreviewform
Backoffice.
Versionchangeforbaseline

GertjanBoks

Review History
Version
1.1

Date

Reviewer

04-Sep-2003 ECR3039

ISSUE reference
AddITP7301

Approval Record
Version

Date

Approved by

Signature

23