Cisco Itp in Eservglobal In: Sigtran and Itp Training

Cisco ITP in eServGlobal IN
Sigtran and ITP Training
PS and Support Internal Training

Diegem
Dennis Hagarty
Implementation Practice
31 August 2006
2003 Cisco Systems 2006 eServGlobal Ltd
Agenda
Purpose, goals and quick review
ITP anatomy, including hardware overview
Configuration of the ITP
Global parameters
Links, linksets and M2PA
Introduction to Sigtran
SCCP and SUA detailed information
Configuring ITP Sigtran and GTT Features
M3UA, SUA configuration
MTP3 routing and Global Title Translation
IP Network Design
Putting it all together into a configuration
SIGTRANandITPTraining|2|2003
Purpose
To gain experience with:
ITP integration/connection with an SS7 network
ITP as a Signalling Gateway for an SUA application
Understanding a configuration for the ITP and the HssScIf interface
Design of a IP network to support it
These specific goals:
Covers relevant topics, in detail, for an eSG typical deployment
Hands on time with a machine if possible
Learning through looking time with traces and Wireshark
Bootstrap for more advanced topics if we have time CONCEPTS!
And these specific non-goals:
ITP expert
Other possible uses for ITP, such as Wi-Fi authentication, MAP MLR
SS7: What is it? SS7 and OSI Protocol Stack
Telnet, FTP,
POP3
TCP/UDP/SCTP
IP
Ethernet
Twisted Pair
Anatomy of an ITP
Outline an ITP.
Remember, we said, an ITP is:
Cisco multifunction router
Operating system (IOS)
Port (Interface) cards
Software makes the system
So, this is why we did the overview of IOS, but before we get
onto configuration, some highlights of the ITP range
Cisco ITP Platform Overview
Dual Power /
Dual CPU
265x
Dual external
Low-End
Single CPU
7204/6 VXR
Dual Power
Low-Midrange
Single CPU
7301
Dual Power
Midrange
Single CPU
7507/13
Dual Power
High-End
Dual CPU
7600 Range
Dual Power
Mid-Top-end
Dual CPU
# of
ATM
HSL
Links
N/A
Max # of
C7 Links
4
(CPU!)
# of
T1/E1
ports
N/A
24
48
48
80-160
320-800
176
64-160
4002200
32176
SUA &
M2PA MSU
per Sec.
900
2,500
3,000
6,000
6,000
12,000
14,000
30,000
20K-110K
30K-165K
ITP Performance
2651
7200
7300*
7500
7600
M2PA MSU/Sec
2,500
6,000
12,000
28-30,000
27-150,000
M3UA MSU/Sec
1,200
6,000
12,000
20,000
30-165,000
900
3,000
6,000
14,000
20-110,000
1,000
10,000
10,000
10,000
10,000
150,000
500,000
500,000
500,000
500,000
1,000
10,000
10,000
10,000
10,000
Number of VIP/FlexWAN possible
N/A
N/A
N/A
5, 11
2, 4, 7, 11
MTP2 Links per VIP/FlexWAN
N/A
N/A
N/A
80
200
MTP2 MSU/sec per VIP/FlexWAN
N/A
N/A
N/A
6,000
14,000
SUA MSU/sec per VIP/FlexWAN
N/A
N/A
N/A
6,000
10,000
SUA MSU/Sec
Maximum Routing Table Entries
Maximum GTT Entries
Maximum M3UA/SUA Routing Keys
* = 7300 or 7200 with NPE-G1 processor

N.B. 7513 M2PA, LSL, HSL goes to 60,000 with SUA offload and High Performance licence
ITP Platforms: 2651XM
2651XM
One NM
Two WIC cards
2 Fast Ethernet
40 K PPS
64MB/128MB DRAM
16MB/48MB Flash
External redundant power
Two x Dual-Port Multiflex

E1 cards
VWIC-2MFT-E1
2651 with 2691
ITP Platforms: 7200

7204 with various cards
7204/7206 VXR
Four slots in 7204
Six slots in 7206
Up to 4/6 FE (TX) available
400 K PPS
Dual power and NEBS
NPE-400 processor
PA-MCX-8TE1 Port Cards
I/O Controller with 2 FE
NPE-G1 processor doubles

performance.
ITP Platforms: 7200 NPE-400
CPU Processor
350-MHz RM7000A RISC
4MB L3 cache
128MB/512MB DRAM
64MB/256MB Flash
ECC support
PA-MCX-8TE1-M (E1 Card)
Shared with 75xx platform
Comes as 2, 4, or 8 port version
Only support 24 LSL per 7200
NPE-400 Processor
ITP Platforms: 7301
7301
Single Slot for 8 Port E1
One RU form factor
Three FE/GE LAN ports
900 K PPS
ITP Platforms: 7507 and 7513

Route Switch
Processors (RSP)
Versatile Interface
Processors (VIP)
VIP4-80 / VIP6-80
Increase Performance
RSP8 / RSP16
Second RSP for HA (RPR+)
Port and Services
Industry Leading 70+ LAN &

WAN Adaptors To Choose From
Adaptors
Industry leading features

Scalable / high performance
Carrier-class high availability
2 Power Supplies
for Redundancy
PA-MCX-8TE1-M (LSL)
PA-A3-8E1IMA (HSL)
PA-2FE-TX (Ethernet)
ITP Platforms: 7500 VIP Cards
VIPs can take 2 port adapters with either IP or SS7 media cards
Lots of CPU intensive processing is pushed down to the VIP.
SS7 MTP2 Port Adapter and FE PA
PA-MCX-8TE1-M
Supports up to 126 MTP2

signalling links over 8 ports of
T1/E1
Minimum HW Requirements
T1/E1 SS7 Link Port Adapter for

Ciscos IP Transfer Point (ITP)
7507 or 7513: RSP8, RSP16, VIP480, or VIP6-80
7204/7206 VXR NPE 400, or G1
7301
PA-2FE-TX
Two FE Slots per PA
SS7 ATM HSL Port Adapter
PA-A3-8E1IMA
T1/E1 SS7 Link Port Adapter for

Ciscos IP Transfer Point (ITP)
Supports up to 8 ATM AAL5
signalling links over 8 ports of
T1/E1
SSCF and SSCOP run on VIP
Minimum HW Requirements
7507 or 7513: RSP16
7507 or 7513: VIP6-80
7301
7500 Architecture
Backup RSP
GTT
Primary RSP
SUA
SCCP
GTT
MTP3 Mgmt RSP
t
a
n
at poi
D k
c
e
h
C
M3UA
MTP3MTP3
MTP3
Routing
Routing
SCCPSCC
Mgmt
P
MTP3
RoutingHigh Speed DMA Memory Bus
Shared
Shared DMA Memory

MTP3/MTP3b Routing
MTP3/MTP3b Mgmt
Shared High Speed DMA Memory

VIP
MTP3/SCCP
Forwarding
MTP3 Fast Cache
MTP3/SCCP
Screening
MTP3 Acct / Filter

MTP2
MTP2
SS7 LSL
PA
SS7 LSL
PA
VIP
MTP3/SCCP
Forwarding
MTP3/SCCP
Screening
VIP
MTP3/SCCP
Forwarding
MTP3/SCCP
Screening
SSCF-NNI
M2PA
SSCOP
SCTP
ATM AAL5
IP
SS7 HSL
PA
SS7 HSL
PA
SS7 Data Flow
VIP
Ethernet
PA
SCTP
IP
Ethernet
IP PA
PA
Ethernet
PA
Sigtran Data Flow
Ethernet
PA
7600 Platform
High-end Cisco Platform
Higher performance
Higher reliability
Meant to tackle the broader STP

market as well as the signalling
gateway (i.e. Tekelec)
ITP Platforms: 7600 Series
Main processor = SUP720-3BXL

Supports basically the same port
adapters and 7300, 7500
# of Slots
Height Support
4-Slot
6-slot
9-slot
13-slot
4 (horizontal)
6 (horizontal)
9 (vertical)
13 (horizontal)
for STM-1
(PA-A3-OC3)
(MM,
SMI, and
8.75
(5RU)
12.25
(7RU)
33.5 SML)
(21 RU) and Q.703
30.15 (19RU)
adapter (PA-MCX-4TE1-Q)
coming
Bandwidth
320 Gbps
480 Gbps
720 Gbps
720 Gbps
Adds
Performance
30+ Mpps
30+ Mpps
30+ Mpps
Non Disruptive
Upgrade (NDU)
to Non-Stop
Operations30+Mpps
(NSO)
7600 Architecture
Backup SUP
Primary SUP
SCCP Mgmt
MTP3 route mgmt
MTP3 Mgmt
xUA Route mgmt
xUA Mgmt
g
a ti n
t
a n
D poi
ck
e
h
Shared High Speed switch matrix

FW2
FW2
FW2
FW2
MTP3/SCCP
Forwarding
MTP3/SCCP
Forwarding
MTP3/SCCP
Forwarding
MTP3/SCCP
Forwarding
MTP3/SCCP
Forwarding
MTP3/SCCP
Forwarding
MTP3/SCCP
Forwarding
MTP3/SCCP
Forwarding
GTT/MLR
GTT/MLR
GTT/MLR
GTT/MLR
GTT/MLR
GTT/MLR
GTT/MLR
GTT/MLR
MTP3/SCCP
Screening
MTP3/SCCP
Screening
MTP3/SCCP
Screening
MTP3/SCCP
Screening
MTP3/SCCP
Screening
MTP3/SCCP
Screening
MTP3/SCCP
Screening
MTP3/SCCP
Screening
M2PA
M3UA
SUA
M3UA
SCTP
SCTP
SCTP
SCTP
IP
IP
IP
IP
Ethernet PA
Ethernet PA
Ethernet PA
Ethernet PA
SSCF-NNI
MTP2
SSCOP
MTP2
ATM AAL5
SS7 LSL PA
SS7 HSL PA
SS7 LSL PA
SS7 Data Flow
Sigtran Data Flow
MTP2
SS7 LSL PA
ITP 7600 Performance
7604
7606
7609
7613
13
Port Adapters/FlexWAN
4/2
8/4
14/7
22/11
Low-speed TDM links
400
800
1400
2200
M2PA links
1000
1000
1000
1000
HSLs (ATM)
32
64
112
176
Low-speed TDM links MSUs/sec
28,000
56,000
98,000
154,000
HSLs (ATM) MSUs per second
40,000
80,000
140,000
220,000
M2PA MSU per second
27,000
54,000
95,000
150,000
M3UA MSUs per second
30,000
60,000
105,000
165,000
SUA MSUs per second
20,000
40,000
70,000
110,000
Slots
ITP Standards Compliance

Protocol
Specification
MTP (1, 2, 3)
ITU-T Q.701-Q.709 White 1996 (inter-works with Blue)

ANSI 2 T1.111-1996, China, Japan
SCCP
ITU-T Q.711-Q.719 White 1996 (inter-works with Blue)

ANSI T1.112-1996
TCAP
ITU-T Q771-775 (White book, June 1997)
High-speed links
(unchannelised)
ITU-T Q703 Annex A, White 1996 (inter-works with Blue)
High-speed links
(ATM)
ITU E1: Q.2140, Q.2110, Q.2210, Q.2144

ANSI T1: GR-2878, I.363, I.361 and Japan
SCTP
IETF RFC 2960: Stream Control Transmission Protocol (SCTP)

IETF RFC 3309: SCTP Checksum Change
M2PA
IETF RFC 4165: Signaling Transport SS7 (Sigtran)

MTP2-User Peer-to-Peer Adaptation (RFC or Draft 2)
M3UA
IETF RFC3332: Sigtran SS7 MTP3-User Adaptation Layer
SUA
IETF RFC 3868: Sigtran SS7 SCCP-User Adaptation Layer (SUA)
Why use ITP?
No required architecture changes ITP supports pure TDM mode. When

using SS7oIP, routing translations are the same for TDM or IP linksets
Flexibility when adding capacity for new revenue-generating service
deployment (think Excelcom banana and FDA)
Cost next generation signalling transport lowers network capital and
operational costs.
Performance next generation signalling transport increases the
performance to price ratio per rack with a reduced footprint and power
consumption
Network efficiencies next generation signalling transport leverages
investments in both TDM and IP infrastructure
Intelligent Network Gateway allows for integration between TDM and IP
networks
Application layer routing TCAP, MAP and MAP-user based routing allows
for efficient deployment of new services
Manageability IP-based network monitoring and provisioning improve
operational efficiencies
Introduction to ITP
What is it?
Does SS7 stuff!
What Functions is it used for?
Traditional STP
Next Generation Signalling Transport
SS7oIP backhaul
SS7 over High Speed Links
QoS over IP infrastructure
Signalling gateway
SMS Offload (MLR = Multi-layer Routing)
RADIUS to MAP Authentication
Why reasons would a carrier use it?
SS7oIP savings over TDM circuits
$$$$$
ITP: What is it?
Cisco multifunction router a box with CPU, memory, flash
Operating system (IOS) Ciscos Internet Operating System
Port (Interface) cards
Hardware is all traditional Cisco components
Software built into IOS makes the ITP system
ITP as an ordinary STP
Linkset
1234
SLC
SMSC
SLC
S5/
0/1
:0
4321
S5/
0/1
:1
2345
C
SL
MSC
/
S5
0:0
0/
Basic Configuration for STP
SS7 Variant (ANSI, ITU, China)
Point Code
Controllers in various slots
MTP2 encapsulation on the serial

interfaces
Define linkset
Define links in each linkset
Define Routes
Linkset
Low Speed LINK (LSL)
ITP Functions: ITP versus Traditional STP
Legacy STP
Cisco
ITP
ITP Functions: Next Generation Signalling Transport
Traditional STP
Next-Gen Signalling Transport
MTP3
SS7oIP Transport:
Low and High-Speed Links
ANSI, ITU, China, Japan, etc
High Availability:
6 Nines per 7500 Chassis
Guarantee bandwidth or latency for high

priority SS7 or IP traffic
Address Conversion:
Integrating SS7 and IP Routing
Industry Leading QoS:
SIGTRAN M2PA, M3UA, SUA
Single Box Solution
National Variants:
Full GTT, Management, Screening,

Accounting, etc
Traditional SS7 Transport:
SCCP:
Routing, Management, Screening,

Accounting
Variable length GT digit conversion (Ex:

E.164 to E.212)
Multiple Point Codes/Instances

Price / Performance Leader by an order
of magnitude
Efficient Footprint and Power
SMS Offload
ITP Functions: SS7oIP to Supplement the STP Plane

SEP Site
MSC
Classical SS7 Transport Network

STP
STP
STP
STP
AAA for
WLAN
Next Generation
Signalling Transport
SEP Site
SMSC
HLR
or
SCP
SGSN
Softswitch
Links can be:

56/64 Kbits/s
HSL Unchannelised T1/E1
VHSL Sigtran M2PA
Sigtran M3UA/SUA
SGM
ITP Next-Gen Signalling Transport: SS7 over HSL
SCCP
SCCP
GTT
GTT
MTP3 / MTP3b
MTP2
MTP2
MTP3 / MTP3b
MTP2
SSCF-NNI
SCCOP
MTP1
MTP1
T1 or E1
MTP1
AAL5
SS7 Layer
1 and 2
transport
T1 or E1
SS7 layer 2 changes with no layer 3 Changes
ITP Next-Gen Signalling Transport: SS7 over IP
MSC
SMSC
SS7
Appl
MTP3
MTP2
MTP1
SS7
IP
SS7
SCCP
SCCP
GTT
GTT
MTP3
MTP2
MTP1
M2PA
SCTP
IP
MTP3
Peer
Transport
M2PA
MTP3
MTP2
MTP2
MTP1
MTP1
SCTP
IP
SS7
Appl
Sigtran and SS7 Packets through an SG
MTP3
MSU
FISU
M2PA SG
MTP3
MSU+
User
FISU
M3UA SG
FISU
SUA SG
SCCP +
User
SEP
SS7
TDM
MTP3
MSU
SCTP
M2PA / IP
M2PA
SP
MSU M3UA
MTP3
User
SCTP
/ IP
M3UA
SEP
MSU
SCCP
User
SCTP
/ IP
SUA
SEP
SG
IP
SUA
SEP
ITP Next-Gen Signalling Transport: SS7 over IP (cont)

MTP2 TDM
M2PA/SCTP
MSU4
MSU3
SCTP Chunk Bundling Timeout

(0 ~ 10 msec configurable)
MSU2
MSU1
MSU4
MSU3
MSU2
MSU1
IP
Example: Up to 1480 bytes for Ethernet

FISUs will be terminated at ITP
FISU FISU MSU FISU
MSU FISUFISUFISU
MSU
MSU
IP
Available Bandwidth
for Other MSU Transport
0.4 Erlang
QOS in SS7oIP Networks Classify, Queue, Preserve
ITP map MSUs to IP QoS by using any combination of MSU values
Input link set (ex: link set from SMSC)
Service Indicator (ex: ISUP or SCCP)
Destination Point Code (ex: MSU destined to SMSC)
Global Title Address (ex: TT or MSIDN of SMSC)
M3UA/SUA Routing Key
IP
IP Packet Header
TOS
Protocol Type
(DSCP/ IPPrec)
Source
Address
Destination
Address
Source/Destn
Port
Core Router
SS7 / MTP
Sigtran / IP
IP Core
Network
Classification / Marking By Input Linkset

Link from MSC
T1 / E1
Link from SCP
T1 / E1
Ethernet
Interface
SCTP Links
Physical Facility
IP Prec=1
SS7 Traffic from MSC
IP Prec=3
SS7 Traffic from SMSC
IP Prec=5
SS7 Traffic from SCP
Link from SMSC
Classification / Marking By Service Indicator Classification

MSC
T1 / E1
MSC
T1 / E1
Ethernet
Interface
SCTP Links
Physical Facility
SMSC
IP Prec = 1
ISUP Traffic: SI=5
IP Prec=5
SCCP (SMS) Traffic

SI=3
ITP Functions: Signalling Gateway

SUA SG
MAP
TCAP
SCCP
MTP3
MTP2
MTP1
SEP
MAP IS-41I T
S U
TCAP U P
SCCP P
GTT
SCCP
N
I
F
MTP3
MAP
SUA
SUA
SCTP
MTP2
MTP1
TCAP
IP
Network
IP
SS7
SCTP/IP
N
I
F
IP
ASP
MAP IS-41 I T
S U
TCAP U P
SCCP P
GTT
SCCP
SCTP
MTP3
MTP3
MTP2
MTP2
SCTP
MTP1
MTP1
IP
M3UA
M3UA
IP
Network
M3UA SG
SCTP
IP
ITP Functions: SMS MLR
Route SMS-MO messages based

on a combination of
B-address or destination MSISDN
A-address or originating MSISDN
Destination SMSC
SMS Protocol Identity
Origin MSC (Called Party Address)
Distribute messages to a server

group using weighted round-robin
Servers may be connected via
TDM, HSL or SIGTRAN links
Segmented and concatenated SMS
messages are routed to same
SMSC
SMS-SUBMIT or SMS-COMMAND message

Destination SME (B-address)
Protocol Identity
MAP
User
User Data (will be considered upon request)
Destination SC
Origin SME (A-address)
MAP
BEGIN Dialogue
Invoke Component
Operation Code: MO-forward-SM
TCAP
UDT
CdPA: Destination SC address
CgPA: Origin MSC address
SCCP
ITP Uses: Save Money
Legacy Vendor
Cisco ITP
List Price per LSL
$7,500 - $10,000
$500 1500
List Price for 720

TDM-Link STP
$5.4M
Footprint: 3-6 racks?
$370k
Footprint: 34" H in 19" rack
Yearly Maintenance %age
10%
10%
Charge for routes
Purchased in bundles of 2000
Full route capacity part of product
Charge for GTT
Separate feature card required

and GTT entries sold in blocks
500k GTT capacity part of base

product
Charge for Gateway Screening
Separate feature card required
Part of base product
SS7oIP Ethernet Card Info
Price: $80k
IP B/D Links: 2
MSU/s: 2,000
Link
Utilization: 1.2Mbps
Protocol: Proprietary
Price: $25k
IP B/D Links: 1000
MSU/s: 20,000
Link Utilization: 8 Mbps
Protocol: Standard IETF Sigtran
IP routing and wide-area media

capabilities
Requires external IP router.

Currently Ethernet < 2Mbps.
Carrier-class IP routing in ITP with

wide range of WAN interfaces. Industry
leading SS7oIP QoS
Agenda
Global parameters
MTP3 Routing and Global Title Translation
IP Network Design
ITP Command Set Categories
Global Options and Commands
Configuration of a Low Speed and High Speed Link (64Kb/2Mbit)
Link and linkset commands, including M2PA linksets
M2PA commands
M3UA commands
Peer, mated SG and SGMP commands
SUA (AS and ASP) commands
MTP3 Routing
Global Titles
Debug commands
Troubleshooting
ITP Reference: Set Global Options
Variant
itp(config)# cs7 variant <ansi | itu | china>
itp(config)# cs7 variant itu
Point Codes
itp(config)# cs7 point-code format <bits1> <bits2> <bits3>
itp(config)# cs7 point-code <pc>
itp(config)# cs7 secondary-pc <pc>
itp(config)# cs7 capability-pc <pc>
ITU national options

itp(config)# cs7 national-options {TFR | multiple-congestion}
Network Indicator
itp(config)# cs7 network-indicator
{international |national | reserved | spare}
ITP Reference: Show Global Options
show cs7
itp# show cs7
Point Code
1002
SS7 Variant
ITU
Network Indicator
national
Secondary Point Code
2000
MTP3 Restart status
Completed
MTP3 Restart occurred
35 day(s), 00:52:41 ago
Total Linksets
Available Linksets
Total Links
show running-config
Link Configuration: Channelised T1/E1
Card Type
itp (config) # card type e1 slot (bay/slot on the 7500)
T1/E1 Clocking and framing/line code

itp(config)# controller e1 <slot>/<bay>/<port>
itp(config-contr)# clock source line primary/secondary
itp(config-contr)# clock source internal
For Framing
ITP(config-controller)# framing {crc4 | no-crc4}
For linecode
ITP(config-controller)# linecode {ami | hdb3}
ITP(config-controller)# cablelength long [gain26 | gain36] [0db |
-7.5db | -15db | -22.5db
Defining timeslots in an E1 for use as DS0 links

itp(config)# controller e1 <slot>/<bay>/<port>
itp(config-contr)# channel-group 0 timeslots 16
Link Configuration: SS7 over Channelised E1
MTP2 encapsulation on links

itp(config)# int s0/1/0:0 int s<slot>/<bay>/<port>:<channel-group>
itp(config-if)# encapsulation mtp2
Define Serial Clocking if needed (only on a non-E1 link)

itp(config)# interface Serial0/0
itp(config-if)# clock speed 64000 !(this is only for Serial 64K)
Link Configuration: Verify a Low Speed Link
controller (clocking, status, etc)

itp# show controller e1
E1 0/0 is up.
Applique type is Channelized E1
Cablelength is long gain36 0db
Description: 2600a
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20010805, FPGA: 15
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
Data in current interval (455 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Interface (status, encapsulation, packets, etc)

itp# show interface serial0/0
Interface up indicates physical connectivity is good

Protocol Down indicates that the link in not available at MTP3 yet (not part of a
linkset or not activated on remote side)
Link Configuration: Verification of MTP2 Links
itp# show interface serial
For Link Down Problems (Protocol must be up and encapsulation must

be MTP2, congestion)
itp# show cs7 mtp2 state serial
The field Link State Control (LSC) should display In Service.
The field Transmission Control (TXC) should display In Service.
The field Reception Control (RC) should display In Service.
The field Layer3 link status should display Started.
itp# show cs7 mtp2 congestion serial

itp# show cs7 mtp2 statistics serial
Link Configuration: ATM on Un-channelised T1/E1
Card Type
itp (config) # interface ATM slot/port/bay (on the 7500)
For Framing
ITP (config-if)# framing {crc4adm}
For Clocking and Scrambling

ITP (config-if)# scrambling cell-payload
ITP (config-if)# clock-source {internal | line}
For NNI and ATM

ITP (config-if)# atm nni
ITP (config-if)# pvc [name] 0/5 qsaal
There are very few options here just set them and forget them
Link Configuration: SS7 over ATM HSL
This slide is intentionally left blank
We do not turn MTP on this circuit, so there is nothing to do!!
Link Configuration: Verify a High Speed Link 1/7
itp# show controller atm4/0/0

ATM4/0/0: Port adaptor specific information
Hardware is E1 (1920Kbps) port adaptor
Framer is PMC PM7344, SAR is LSI ATMIZER II
Scrambling is Enabled
linecode is HDB3
E1 Framing Mode:
crc.4 adM format
LBO (Cablelength) is long gain43 75db

Facility Alarms:
No Alarm
<snip>
Current Clock Source = LINE
This is the T1/E1 protocol level
No Alarm is a nice output to have
A LOT of counter headers have been cut from this output
itp# show interface atm4/0/0

ATM4/0/0 is up, line protocol is up
Hardware is cyBus IMA PA, address is 0013.7fdc.9a80 (bia
0013.7fdc.9a80)
MTU 4470 bytes, sub MTU 4470, BW 1920 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
Encapsulation(s): AAL5
511 maximum active VCs, 1 current VCCs
VC idle disconnect time: 300 seconds
Signalling vc = 1, vpi = 0, vci = 5
UNI Version = NNI, Link Side = user
0 carrier transitions (continued)
This is at the AAL level
Line protocol should be up as well, vpi/vci should equal 5
Carrier transitions should NOT be increasing
itp# (continued)
Last input 00:00:01, output 00:00:01, output hang never
Last clearing of "show interface" counters 6w2d
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/64 (size/max)
5 minute input rate 1000 bits/sec, 19 packets/sec
5 minute output rate 1000 bits/sec, 19 packets/sec
75070456 packets input, 758178504 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
74995770 packets output, 748549372 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
All these counters should be zero, except packets and bytes in/out
itp# show sscop atm4/0/0

SSCOP details for interface ATM4/0/0
Current State = Active,
Uni version = NNI
Send Sequence Number: Current = 209737,
Maximum = 210087
Send Sequence Number Acked = 209737

Rcv Sequence Number: Lower Edge = 281513, Upper Edge = 281513, Max
= 282537
Poll Sequence Number = 3446891, Poll Ack Sequence Number = 3446891
Vt(Pd) = 0
Vt(Sq) = 0
MaxPd = 175
Timer_IDLE = 100 - Inactive

Timer_CC = 200 - Inactive
Timer_POLL = 100 - Inactive
Timer_KEEPALIVE = 100 - Inactive
Timer_NO-RESPONSE = 1500 - Inactive (continued)
This is the SSCOP protocol level
(continued)
Current Retry Count = 0, Maximum Retry Count = 10
AckQ count = 0, RcvQ count = 0, TxQ count = 0
AckQ HWM = 43,
RcvQ HWM = 0, TxQ HWM = 94
Local connections currently pending = 0

Max local connections allowed pending = 0
Statistics Pdu's Sent = 16129, Pdu's Received = 25205, Pdu's Ignored = 0
Begin = 3/2, Begin Ack = 0/2, Begin Reject = 2/1
End = 0/0, End Ack = 0/0
Resync = 0/0, Resync Ack = 0/0
Sequenced Data = 29584/20508, Sequenced Poll Data = 0/0
Poll = 45799/15353, Stat = 15353/45799, Unsolicited Stat = 0/0
Unassured Data = 0/0, Mgmt Data = 0/0, Unknown Pdu's = 0
Error Recovery/Ack = 0/0, lack of credit 0
A LOT of Error Statistics have been cut from this output
itp# show sscf atm4/0/0

SSCF-NNI details for interface ATM4/0/0
SSCF-NNI Current State = In Service
ULP Current State = In Service
LLP Current State = Active
SSCF-NNI Configured Parameters:
N1 = 1000
T3 = 1
T1 = 5
T2 = 30
SSCOP Rec = 60
No Credit = 2
NRP = 1
Force Proving = 10
ttc = F
SSCF-NNI Dynamic Parameters:

C1 = 0
MPS = 11
NRP count = 0
UPS = 5
Congestion Level = 0
This is the SSCF-NNI protocol level
In Service and Active are nice to have
(continued)
SSCF-NNI Most Recent SSCOP-UU values:
Local Proving Status= 5
Remote Proving Status= 5
Local Release Status= 7

Remote Release Status= 1
SSCF-NNI Statistics:
MSUs Sent = 217243, MSUs Received = 291745, MSUs Ignored = 0
LSSUs Sent = 2, LSSUs Received = 2, LSSUs Ignored = 0
Bytes Sent = 3161192, Bytes Received = 5138765
Increasing MSUs signify traffic flowing

Any problems requires ATM or WAN support people, debugging
this is beyond the scope of this course!
Links and Linksets: Configuring Linksets
ITP(config)# cs7 linkset ls-name adjacent-point-code
Specifies a linkset to an adjacent node and enters linkset

configuration mode.
Tip: Usually its good to turn accounting on when creating linkset
ITP(config-cs7-ls)# accounting
ITP# show cs7 accounting
4904
4912
SLC 0
serial0/0:0
MSC
Linkset
Links and Linksets: Assigning Links to Linksets
ITP(config-cs7-ls)# link slc serial number (low speed links)

ITP(config-cs7-ls)# link slc atm number
(high speed links)
Configures an SS7 link within a linkset and enters CS7 link

configuration mode.
!!! SLC needs to be the same on both sides of the link !!!
Link and Linkset commands are the same for LSL and HSL
4904
MSC
4912
SLC 0
atm4/0/0
SLC 1
serial5/0/0:1
Linkset
Links and Linksets: Verification
ITP# show cs7 linkset
Displays the status of all interfaces with linksets and links.
lsn=M1ITP01MUMS1
apc=9024
state=avail
avail/links=1/1
SLC
Interface
Service
PeerState
Inhib
00
ATM4/0/0
avail
---------
-----
lsn=M1ITP01FDBS1
apc=5952
state=avail
avail/links=1/1
SLC
Interface
Service
PeerState
Inhib
00
ATM8/1/0
avail
---------
-----
lsn=M1ITP01KOLS1
apc=4416
state=avail
avail/links=1/2
SLC
Interface
Service
PeerState
Inhib
00
ATM4/0/1
avail
---------
-----
*01
ATM8/0/0
FAILED
---------
-----
lsn=M1ITP01HYDS1
apc=320
state=avail
avail/links=1/2
SLC
Interface
Service
PeerState
Inhib
00
ATM4/1/0
avail
---------
-----
*01
ATM8/1/1
FAILED
---------
-----
Links and Linksets: Accounting
Make sure accounting is turned on

itp# show cs7 linkset itp1-msc1 detail
lsn=itp1-msc1
Local Point Code
apc=4904
= 4912
state=avail
avail/links=2/2
Adjacent Restart Enabled
= Y
Broadcast TFP/TCP = Y
Broadcast TFA/TCA and TFR/TCR = Y
Access Group IN
= NONE
Access Group OUT
= NONE
MTP3 Accounting
= Y
GTT Accounting
= N
Rotate SLS
= Y
Input QOS Match
= NONE
Links and Linksets: Verification: cs7 ping Command
itp# cs7 ping point code

itp(config)# cs7 ping [-sls <sls> -duration <dur> ] <pc>
Sends (3) MTP3 messages to the point code.
Can be used on any type of link (MTP2, M2PA, HSL)
Only to ITPs. Other SS7 Nodes might not understand the

command (although it is part of ITU recommendations)
Links and Linksets: Inhibiting/Un-inhibiting Links
Inhibiting a link causes the link to remain available, but MTP3

routing will no longer use it for traffic.
Only allowed to inhibit last link in a linkset if it does not make a
DPC unavailable in the routing table
Link inhibition is not persistent through a reload
itp# cs7 inhibit <lsn> <slc >

itp# cs7 uninhibit <lsn> <slc>
Remote
SP
Links and Linksets: Disabling and Enabling
To enable/disable a link :
itp(config)# cs7 linkset <ls-name>
itp(config-ls)# link <slc>
itp(config-ls-link)# [no] shutdown
To disable a linkset :
itp(config-ls)# [no] shutdown
To disable a controller :
itp(config-controller)# shutdown
NOTE: These commands are persistent through a reload since

they are implemented in configuration mode.
IP Based Linkset: Configuring Local Peer
Two step process:

ITP(config)# cs7 local-peer <local-port-number>
ITP(config-cs7-lp)# local-ip <address>
Specifies the local peer and puts you in local-peer sub mode.
Configures the IP address for this local peer instance.
Additional backup IP addresses for this local end-point can be

specified for alternate routing.
2222
1111
10.0.0.1
20.0.0.1
local-peer 7000
local-ip 10.0.0.1
local-peer 7000
local-ip 20.0.0.1
IP Based Linkset: Defining the Links
ITP(config)# cs7 linkset ls-name adjacent-point-code
Specifies a linkset to an adjacent node and enters linkset

configuration mode.
Configures SS7 over IP peers for a linkset
itp(config-cs7-ls)# link slc sctp remote-ip-addr \
[backup-remote-ip-addr ...] remote-port-num
local-port-num
1111
2222
10.0.0.1
cs7 linkset ITP1-ITP2 2222

link 0 sctp 20.0.0.1 7000 7000
link 0
20.0.0.1
link 0

link 0 sctp 10.0.0.1 7000 7000
IP Based Linkset: IP Multihoming

local-peer 7000
local-ip 10.120.122.6
local-ip 10.120.123.6
link 0
local-peer 7000
local-ip 10.120.122.22
Local-ip 10.120.123.22
IP Cloud 1
3333
4444
10.120.122.22
10.120.122.6
10.120.123.6
10.120.123.22
IP Cloud 2
IP Based Linkset: Linkset with SCTP Multihoming

3333
4444
link 0

link 0 sctp 10.120.122.22 \
10.120.123.22 7000 7000
local-peer 7000
local-ip 10.120.122.6
local-ip 10.120.123.6
3333
10.120.122.6

link 0 sctp 10.120.122.6 \
10.120.123.6 7000 7000
local-peer 7000
local-ip 10.120.122.22
Local-ip 10.120.123.22
4444
link 0
link 0
10.120.123.6
10.120.122.22
10.120.123.22
ACTIVE IP CONNECTION
BACKUP IP CONNECTION
Congratulations!!
You have just configured a SIGTRAN link!!!
This is called M2PA and is the simplest form of SS7oIP
It uses SCTP which includes built-in multi-homing
We are going to look have a look at it a bit more theoretically in

the next section!
M2PA commands
M3UA commands
MTP3 Routing
Global Titles
Debug commands
Troubleshooting
Agenda
Global parameters
IP Network Design
Sigtran
What is it?
What must it do?
Reliable, fast, robust
How does it do it?
A set of IETF Standards to run signalling over IP networks
SCTP and IP
Why are we bothered with this stuff?
What does this mean to us?
Why not use DK cards?
Sigtran: What is it?
Set of standards, proposed standards, and drafts
RFC 2719 Framework Architecture for Signalling Transport
RFC 2960 Stream Control Transmission Protocol (& 3286)
IUA = RFC 3057 - ISDN Q.921-User Adaptation Layer along with:

<draft-ietf-sigtran-iua-imp-guide-02.txt>
M2UA = RFC 3331 SS7 MTP2 User Adaptation Layer
M3UA = RFC 3332 SS7 MTP3 User Adaptation Layer
SUA = SS7 SCCP-User Adaptation Layer

RFC 3868 SCCP User Adaptation Layer
M2PA = MTP2-User Peer-to-Peer Adaptation Layer
RFC 4165 MTP2 User Peer-to-Peer Adaptation Layer
LAPV5/V5.2 Adaptation Layer
<draft-ietf-sigtran-v5ua-04.txt >
Sigtran: Requirements for Signalling Network
Not more than one in 1010 of all message signal units must contain
an error that is undetected by the MTP.
Not more than one in 107 messages will be lost due to failure in
the MTP.
The availability of any signalling communication path between two
SEPs has to be at least 0.99998 corresponding to a downtime of
at most 10 minutes/year.
Not more than one in 1010 messages will be delivered out-ofsequence to the User Parts due to failure in the MTP. This value
also includes duplication of messages.
In addition there are requirements on message transfer times in
STPs, which under normal conditions are supposed to be less than
100 mSec, and implicit requirements on limits for the outgoing
queuing delays.
Message length (payload accepted from SS7 user parts)
272 bytes for narrowband SS7, 4091 bytes for broadband SS7
Sigtran: How is this achieved?
SCTP: Stream Control Transmission Protocol
Reliable datagrams and connection oriented called an association
Concept of streams
An SCTP association provides multiple uni-directional streams
Message loss on one stream does not delay messages using other
streams, no head of line blocking.
Multihoming: an SCTP endpoint can have multiple IP addresses.
Timer based retransmission, highly configurable
Primary and Standby addresses, monitored using heartbeat
Runs on top of the potentially unreliable IP
More flexible than TCP: byte oriented, strictly ordered, single homed.
UDP is connectionless and uses unreliable datagrams.
Sigtran: Used in eServGlobal applications
The following are probably the most interest to us:
M2PA = to run SS7 linksets over IP
M3UA = to run non-SCCP traffic (ISUP) over IP (V.SSP, UCA-I)
SUA = to run SCCP traffic over IP (UAS, VPU, UIP)
Sigtran: M2PA
M2PA is a peer-to-peer protocol that provides a link between remotely

located MTP3 instances it replaces the MTP2 layer beneath MTP3. The
user of M2PA is MTP3 at both ends of the connection.
M2PA provides a means for peer MTP3 layers in SGs to communicate
directly. In essence, it extends the reach of SS7 over the IP network.
M2PA is a
way to
bridge
MTP3 over
IP
Sigtran - Reliability
When SCTP Multi-homing detects unresponsiveness:
It changes the IP path used for the session by changing the source
and/or destination IP address of the session.
During this process, the SCTP session remains active and MTP3 is
unaware of the path change
SCTP initiates processes to detect the return of the primary
SCTP fails back to the primary on return of that path
SCTP sends heartbeats and retransmissions over the secondary

path to monitor its health
Peer to Peer M2PA

SSP
SSP
ISUP/SCCP/TCAP/MAP
MTP3
MTP3
M2PA
M2PA
SCTP
SCTP
IP
IP
Sigtran: M3UA
M3UA operates in a client-server way to provide an upper layer SS7 with

protocol remote access to the lower layers. M3UA operates between an
SG and an SCP or UAS.
M3UA provides a means by which an MTP3 service may be provided on an
UAS (thus, terminating the ISUP connection on the UAS) - essentially
extending the reach of SS7 into the IP network.
M3UA is for
USERS of
MTP3!!
Signalling Gateway M3UA

V.SSP
SSP
ISUP
Hughes
MTP3
M3UA
Legacy
M3UA
and
SCTP
MTP2
SCTP
MTP1
IP
Cisco ITP
Sun IP
Sigtran: SUA
SUA provides a means by which an Application part (such as TCAP) on an

IP SCP may be reached via an SG. The network architecture associated
with SUA allows for multiple IP SCPs to be reached via a single SG. The IP
SCPs do not have local MTP3 instances, and so do not require their own
SS7 point codes (MTP3, and the point code, can reside on the SG).
SUA is for
USERS of
SCCP!!
Signalling Gateway - SUA

UAS
MSC
TCAP Application Data
GTT
SCCP
SUA
MTP3
Legacy
Hughes
SUA
and
SCTP
MTP2
SCTP
MTP1
IP
Cisco ITP
Sun IP
ITP Protocol Architecture
Cisco IOS
GTT
SCCP
SUA
MTP3 / MTP3b
M3UA
M2PA
SSCF-NNI
MTP2
SCTP
SCCOP
AAL5
MTP1
IP
M3UA / SUA Advantages and Disadvantages

M3UA
Advantages
SUA
Advantages
ISUP, TUP, SCCP access
SG performs standard GTT
Disadvantages
MTP3 to M3UA mapping can be

more CPU intensive than MTP3
routing
NIF is implementation dependent
(undocumented) and could make
interoperability challenging
Designed for IP service end nodes
that do not perform STP MTP3
function
Simple for SCCP access only

IP service end node does not need
to implement a SS7 layer 3
adaptation routing protocol
Disadvantages
No ability to participate in ISUP

flows
GTT is adapted within SUA protocol
which is still being discussed in the
standards group
Sigtran: Used in eServGlobal applications
The following are probably the most interest to us:
M2PA = to run SS7 linksets over IP
M3UA = to run non-SCCP traffic (ISUP) over IP (PGW2200, UCA-I)
SUA = to run SCCP traffic over IP (UAS, VPU)
This is too complicated!
Whats wrong with SS7 cards in the UAS?
Whats better with the ITP and Sigtran?
Traditional IN Protocol Architecture

SCP
MSC
SCCP
MTP3
SCCP
SINAP, OpenSS7
DataKinetics, etc
MTP3
MTP2
MTP2
MTP1
MTP1
eServGlobal Protocol Architecture

UAS
MSC
SCCP
SCCP
GTT
SUA
MTP3 / MTP3b
M3UA
MTP3
SSCF-NNI
MTP2
M2PA
MTP2
SCTP
SCCOP
MTP1
MTP1
Hughes
xUA
and
SCTP
AAL5
IP
Cisco ITP
Sun IP
Agenda
Global parameters
IP Network Design
SCCP and SUA
SCCP and GTT/Routing
Groan
The most important thing to get out of this is:
There are UDT, XUDT packet formats (amongst others)
XUDT has HOPCOUNT and SEGMENTATION parameters
There is Class 0 and 1 connectionless traffic
The format is complicated (dont try to decode on paper)
Routing, GTT (covered more in the SUA section)
SCCP Protocol Classes
The SCCP protocol classes are defined as follows:
Protocol class 0 provides unordered transfer of SCCP-user messages in

a connectionless manner.
Protocol class 1 allows the SCCP-user to select the in-sequence
delivery of SCCP-user messages in a connectionless manner.
Protocol class 2 allows the bi-directional transfer of SCCP-user
messages by setting up a temporary or permanent signalling
connection.
Protocol class 3 allows the features of protocol class 2 with the
inclusion of flow control. Detection of message loss or mis-sequencing
is included.
Protocol classes 0 and 1 make up the SCCP connectionless

service.
Protocol classes 2 and 3 make up the SCCP connection-oriented
service.
SCCP Message Parts
A SCCP message consists of the following parts:
the message type code;
the mandatory fixed part;
the mandatory variable part;
the optional part, which may contain fixed length and variable length
fields.
SCCP Message Types

Message type
Classes
Message
Reference
Code
CR Connection request
4.2
0000 0001
CC Connection confirm
4.3
0000 0010
CREF Connection refused
4.4
0000 0011
RLSD Released
4.5
0000 0100
RLC Release complete
4.6
0000 0101
DT1 Data form 1
4.7
0000 0110
DT2 Data form 2
4.8
0000 0111
AK Data acknowledgement
4.9
0000 1000
UDT Unitdata
4.10
0000 1001
UDTS Unitdata service
X1
X1
4.11
0000 1010
X = Type of message of this protocol class.

X1 = Type of protocol class is indeterminate (absence of protocol class parameter).
SCCP Message Types

Message type
Classes
Message
Reference
Code
ED Expedited data
4.12
0000 1011
EA Expedited data acknowledgement
4.13
0000 1100
RSR Reset request
4.14
0000 1101
RSC Reset confirm
4.15
0000 1110
ERR Protocol data unit error
4.16
0000 1111
IT Inactivity test
4.17
0001 0000
XUDT Extended unitdata
4.18
0001 0001
XUDTS Extended unitdata service
X1
X1
4.19
0001 0010
LUDT Long unitdata
4.20
0001 0011
LUDTS Long unitdata service
X1
X1
4.21
0001 0100
X = Type of message of this protocol class.

X1 = Type of protocol class is indeterminate (absence of protocol class parameter).
SUA Packet Formats and Reference
Do you want to know some of the details of SUA?

Well, you are going to see more than some, but you need to see
the detail to get the big picture.
The most important thing to get out of this is
The destination and source address formats and tags.
There are CLDT and CLDR
We wont cover DUNA, DAVA, etc in much detail.
SUA Message Formats-CLDT 1/3
Connectionless Data Transfer (CLDT) message transfers data

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0006
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/
Routing Context
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0115
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Protocol Class
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0102
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/
Source Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0103
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/
Destination Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0116
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Sequence Control
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0101
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
SS7 Hop Count
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0113
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Importance
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0114
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Message Priority
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0013
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Correlation ID
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0117
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Segmentation
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x010b
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/
Data
/
\
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
A Connectionless Data Response (CLDR) is a service message
SUA Message Formats-Source/Destination Address
SUA Source Address

0
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0102
Parameter Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Routing Indicator
Address Indicator
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/
Address parameter(s)
/
\
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The following combinations of address parameters are valid:
Global Title (e.g. E.164 number) + optional PC and/or SSN, SSN may be zero, when routing is
done on Global Title
SSN (non-zero) + optional PC and/or Global Title, when routing is done on PC + SSN. The PC
is mandatory in the source address when sending from SGP to ASP, and in the destination
address when sending from ASP to SGP to reach the SS7 SEP.
Hostname + optional SSN, when routing is done by Hostname
SSN (non-zero) and optional IP address when routing is done on IP address + SSN
SUA Message Formats-S/D Address-Routing Indicator
Routing Indicator
The following values are valid for the routing indicator:
Reserved
Route on Global Title
Route on SSN + PC
Route on Hostname
Route on SSN + IP Address
The ROUTING indicator determines which address parameters are

to be used in routing the traffic to the destination.
SUA Message Formats-S/D Address-Address Indicator
Address indicator is coded as follows:
Bit 1 is used to indicate inclusion of the SSN
Do not include SSN when optional
Include SSN
Bit 2 is used to indicate inclusion of the PC
Do not include PC, regardless of the routing indicator value
Include PC
Bit 3 is used to indicate inclusion of the Global Title
Do not include GT when optional (routing indicator /= 1)
Include GT
The remaining bits are spare and SHOULD be coded zero, and
MUST be ignored by the receiver.
The ADDRESS indicator determines which address parameters
need to be present in the address parameters field.
SUA Message Formats-S/D Address-Global Title 1/5
Global Title
0
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x8001
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Reserved
GTI
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
No. Digits
| Trans. type
Num. Plan
| Nature of Add |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/
Global Title Digits
/
\
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Number of Digits:
This is the number of digits contained in the Global Title.
Global Title Indicator

0000
Reserved
0001
Nature of Address is ignored. Translation Type = Unknown

and Numbering Plan = E.164 (value 1).
0010
This is most commonly used in North American networks.

The Translation Type implicitly determines Nature of Address
and Numbering Plan. This data can be configured in the SG.
The number of digits is always even and determined by the
SCCP address length.
0011
Numbering Plan and Translation Type are taken over. It is

implicitly assumed that the Nature of Address = Unknown.
0100
This format is used in international networks and most

commonly in networks outside North America. All information
to populate the source address is present in the SCCP
Address.
Numbering Plan:
0
unknown
ISDN/telephony numbering plan (E.163 and E.164)
generic numbering plan
data numbering plan (Recommendation X.121)
telex numbering plan (Recommendation F.69)
maritime mobile numbering plan (E.210, E.211)
land mobile numbering plan (E.212)
ISDN/mobile numbering plan (E.214)
8 13
spare
14
private network or network-specific numbering plan
15 - 126 spare
127
reserved.
Translation type:
0
Unknown
1 63
International services
64 127
Spare
128 254
National network specific
255
Reserved
Nature of Address:
0
unknown
subscriber number
reserved for national use
national significant number
international number
5 255
Spare
Global Title:
Octets contain a number of address signals and possibly filler as shown:
0
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|2 addr.|1 addr.|4 addr.|3 addr.|6 addr.|5 addr.|8 addr.|7 addr.|
|
sig. | sig.
sig. | sig.
sig. | sig.
sig. | sig.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
.............
|filler |N addr.|
|if req | sig.
filler
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
All filler bits SHOULD be set to 0.
SUA Message Formats-S/D PC and SSN
Point Code
1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x8002
Length = 8
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Point Code
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Subsystem Number
1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x8003
Length = 8
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Reserved
SSN value
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SUA Message Formats-S/D-SSN Values
The Subsystem Number (SSN) identifies an SCCP user function

00
SSN not known/not used
01
SCCP management
02
reserved for ITU-T allocation
03
ISDN user part
04
OMAP (Operation, Maintenance and Administration Part)
05
MAP (Mobile Application Part)
06
HLR (Home Location Register
07
VLR (Visitor Location Register)
08
MSC (Mobile Switching Centre)
09
EIC (Equipment Identifier Centre)
0A
AUC (Authentication Centre)
0B
ISDN supplementary services
0C
reserved for international use
0D
broadband ISDN edge-to-edge applications
0E
TC test responder
0F-1F
reserved for international use
20-FE
reserved for national networks
FF
reserved for expansion of national and international SSN.
SUA Protocol Parameters
These parameters are specific to the SUA protocol:

Parameter Name
ID
Parameter Name
ID
SS7 Hop Counter
0x0101
Source Address
0x0102
Destination Address
0x0103
Source Reference No.
0x0104
Destination Reference No.
0x0105
SCCP Cause
0x0106
Sequence Number
0x0107
Receive Sequence No.
0x0108
ASP Capabilities
0x0109
Credit
0x010A
Data
0x010B
Cause / User
0x010C
Network Appearance
0x010D
Routing Key
0x010E
DRN Label
0x010F
TID Label
0x0110
Address Range
0x0111
SMI
0x0112
Importance
0x0113
Message Priority
0x0114
Protocol Class
0x0115
Sequence Control
0x0116
Segmentation
0x0117
Congestion Level
0x0118
SUA Header Output from ITP Debug 1/2
CS7 XUA PACKET SENT TO GS-UAS2-ASP: Message: Class = CONNECTIONLESS, Type = CLDT,
Length = 300
Parameter: Tag = ROUTING CONTEXT, Length = 8
Value = 0x000000C8
Parameter: Tag = PROTOCOL CLASS, Length = 8
Value = 0x00000001
Parameter: Tag = SEQUENCE CONTROL, Length = 8
Value = 0x00000007
Parameter: Tag = SOURCE ADDRESS, Length = 36
Value = 0x00010005 0x80030008 0x00000092 0x80010012
0x00000004 0x0C000104 0x19895300 0x50550000
Parameter: Tag = DESTINATION ADDRESS, Length = 44
Value = 0x00020005 0x80030008 0x00000092 0x80020008
0x000020F4 0x80010012 0x00000004 0x0C000104
0x19895300 0x42000000
Parameter: Tag = MESSAGE PRIORITY, Length = 8
Value = 0x00000000
Parameter: Tag = DATA, Length = 177
Value = 0x6281AA48 0x04D50001 0xB86B1E28 0x1C060700 (etc etc)
SUA Header Output from ITP Debug 2/2
CS7 XUA PACKET RECEIVED FROM GS-UAS2-ASP: Message: Class = CONNECTIONLESS, Type =
CLDT, Length = 320
Parameter: Tag = ROUTING CONTEXT, Length = 8
Value = 0x000000C8
Parameter: Tag = PROTOCOL CLASS, Length = 8
Value = 0x00000081
Parameter: Tag = SOURCE ADDRESS, Length = 36
Value = 0x00010005 0x80030008 0x00000092 0x80010014
0x00000004 0x0C000104 0x19895300 0x42000000
Parameter: Tag = DESTINATION ADDRESS, Length = 44
Value = 0x00010007 0x80020008 0x000020F8 0x80030008
0x00000092 0x80010014 0x00000004 0x0C000104
0x19895300 0x50550000
Parameter: Tag = SEQUENCE CONTROL, Length = 8
Value = 0x00000000
Parameter: Tag = DATA, Length = 208
Value = 0x6581C948 0x0400007F 0xD24904D5 0x0001B86B
0x2A282806 0x07001186 0x05010101 0xA01D611B (etc etc)
SCCP Message Formats-Source/Destination Address
For comparison, this is an SCCP header:
SUA is a bit longer
8
OCTET
Nat/Intnl Routing
Indicator Indicator
2
Point
Code
Indicator
Subsystem Number
Signaling Point Code
Global Title
1
Subsystem
Number
Indicator
Bit
Pos
SUA Management Message Mapping
SUA Primitive to/from ASP
MTP Primitive to/from SS7
CLDT (Payload data)
UDT/XUDT
CLDR (Payload data)
UDTS/XUDTS
DUNA (Destination Unavailable)
MTP-PAUSE (TFP) or SSP
DAVA (Destination Available)
MTP-RESUME (TFA) or SSA
SCON (Network Congestion State)
MTP-STATUS (TFC) or SSC
DUPU (Destination User Part

Unusable
MTP-STATUS (UPU)
DRST (Destination Restricted)
MTP-STATUS (TFR)
DAUD (Destination State Audit)
Link or subsystem status
SPMC* network congestion
TFC
SPMC* network unavailable
TFP
* SPMC signalling Point Management Cluster (Group of ASs sharing a single PC).
With this knowledge, were off
Agenda
Global parameters
Global Title Translation
IP Network Design
Configuring ITP Sigtran Features
M2PA commands
M3UA commands
MTP3 Routing
Global Titles
Debug commands
Troubleshooting
M2PA Overview
Defining Local Peer on each ITP
Defining Linksets to remote peer
Assigning links to linksets.
SCTP multihoming
Remember:
M2PA is peer to peer, M3UA and SUA are client-server
M2PA Linksets: Disabling and Enabling
To enable/disable a link :
itp(config-ls)# link <slc>
itp(config-ls-link)# [no] shutdown
To disable a linkset :
itp(config-ls)# [no] shutdown
To disable a controller :
itp(config-controller)# shutdown
To disable M2PA for any one instance or remove IP address:

itp(config)# cs7 local-peer <local-port-number>
itp(config-cs7-lp)# shutdown
itp(config-cs7-lp)# no local-ip <address>
IP Based Linkset: Linkset with SCTP Multihoming

3333
4444
link 0

link 0 sctp 10.120.122.22 \
10.120.123.22 7000 7000
local-peer 7000
local-ip 10.120.122.6
local-ip 10.120.123.6
3333
10.120.122.6

link 0 sctp 10.120.122.6 \
10.120.123.6 7000 7000
local-peer 7000
local-ip 10.120.122.22
Local-ip 10.120.123.22
4444
link 0
link 0
10.120.123.6
10.120.122.22
10.120.123.22
ACTIVE IP CONNECTION
BACKUP IP CONNECTION
M2PA: Useful Commands
Useful Commands
show cs7 linkset
show cs7 m2pa state <linkset-name>
show cs7 m2pa peer <linkset-name> [SLC]
show ip sctp association statistics <instance>
show ip sctp association parameters <instance>
SUA/M3UA Overview
AS and ASP
Routing Key
Traffic Modes
SUA/M3UA Point Codes
SUA/M3UA Example Scenarios
SUA/M3UA Monitoring
NB: More and more companies now provide M3UA based element
such as HLRs and SMS-Cs.
SUA/M3UA: AS and ASP
Application Server (AS)
A logical entity serving an SS7 function.
Contains one or more Application Server Processes (ASPs)
An AS serves a routing key
May be represented by a point code/SSN
Application Server Process (ASP)
A process instance of an Application Server.
Contains an SCTP end-point or association
One must be active for the AS to be available (durrr!))
Can serve multiple ASs on a single or multiple SGs.
If this is confusing, then this may help:
An AS is a SS7 entity (service) and has a Point Code/SSN
And ASP is the server destination and has IP addresses/ports
SUA/M3UA: Routing Key
Used by the SG to route SS7 messages to the appropriate AS.
Selection criteria for SS7 messages
A Routing Key maps directly to an AS
ITP (or other SGs) can use various SS7 parameters to filter SS7
messages:
DPC
OPC range
SSN (SUA or SI=SCCP only)
GTT
SI (M3UA only, for SUA it has to be SCCP)
ISUP CIC range (for M3UA only)
SUA/M3UA: Point Codes
The SG presents a set of ASs to the SS7 network
These ASs must be reachable via a Point Code, and therefore:
An AS can have its own individual Point Code
An AS can have the same Point Code as the SG
A single Point Code can be shared with a set of other ASs
An ASP can be assigned a unique Point Code by being the only ASP in
an AS
An AS may be assigned the primary or the secondary local point code
owned by the ITP SG
An AS may be assigned a capability code or alias point code of the ITP
SG. The AS is sharing the point code with the ITP SGs mated-pair.
An AS may be assigned a unique point code, different from any of the
ITP SGs point codes.
SUA/M3UA: Traffic Modes
Override
One Active ASP in an AS. One ASP takes over all traffic for an AS
(primary/backup operation), possibly overriding any currently active
ASP in the AS.
Fail-over to backup ASP.
Loadshare
Traffic shared among all Active ASPs within an AS.
Algorithm is one of:
bindings - SLS-based load share (default)
Round robin distributed equally amongst the ASP in the AS
Weighted Round Robin distributed in a weighted fashion
Broadcast
Traffic sent to all Active ASPs within an AS.
Traffic Mode Broadcast
SCCP messages to 2109

Signalling Gateway
ASPA
ACTIVE
AS BLUE
ASPB
ACTIVE
ASPC
ACTIVE
AS Blue
Routing Key = DPC 2109, SI SCCP
ASP List = ASPA, ASPB, ASPC
Traffic Mode = Broadcast
Traffic Mode Override

Signalling Gateway
ASPA
ACTIVE
AS BLUE
ASPB
INACTIVE
ASPC
INACTIVE
AS Blue
Traffic Mode = Override
CDMA Override Example
CDMA Override Example (Failure)
Traffic Mode Loadshare (Bindings)
0, 3,
Signalling Gateway
ASPA
ACTIVE
AS BLUE
1, 4,
ASPB
ACTIVE
2, 5,
ASPC
ACTIVE
AS Blue
Traffic Mode = loadshare bindings
Traffic Mode Loadshare (Round Robin)
every
Signalling Gateway
ASPA
ACTIVE
AS BLUE
third
ASPB
ACTIVE
packet
ASPC
ACTIVE
AS Blue
Traffic Mode = loadshare roundrobin
Traffic Mode Loadshare (Weighted Round Robin)
50%
Signalling Gateway
ASPA
ACTIVE
AS BLUE
30%
ASPB
ACTIVE
20%
ASPC
ACTIVE
AS Blue
Traffic Mode = loadshare roundrobin weighted
Loadshare Example
SUA/M3UA: Loadshare 1/2
Load-share bindings as a traffic type is performed as follows:
SCCP class 1 traffic: round-robin load sharing will be done with the
SLS of the MSU as the load-share seed.
ISUP traffic: round-robin load sharing will be done with the
DPC/OPC/CIC of the MSU as the load-share seed.
Load-share round robin as a traffic type is performed as follows:
SCCP class 0 traffic: basic round-robin load sharing will be done

without regard to any parameters in the MSU.

SCCP class 1 traffic: round-robin load sharing will be done with the
SLS of the MSU as the load-share seed.
SCCP Class 1 ALWAYS uses SLS values (one exception)
SUA/M3UA: Loadshare 2/2
Load-share weighted round robin as a traffic type is performed

as follows:

SCCP class 1 traffic: weighted round-robin load sharing will be done
without regard to any parameters in the MSU (this is the exception)
Load-Sharing Summary
Traffic
Mode
Other
Tools
Broadcast
SCCP
Class 0
SCCP
Class1
SCCP Distribute
Un-sequenced off
SCCP Distribute
Un-sequenced on
Always
Sequenced
N/A
Broadcast
all receive
Broadcast
all receive
Broadcast
all receive
Loadshare
Bindings
None
SLS
Round Robin
SLS
Loadshare
round robin
None
Round Robin
Round Robin
SLS
Loadshare
weighted
round robin
None
Weighted Round
Robin
Weighted Round
Robin
Weighted Round
Robin and SLS
Override
N/A
Override
no load sharing
Override
no load sharing
Override
no load sharing
SUA: Example Scenario

Signalling Gateway
ASPA
ACTIVE
ASPB
ACTIVE
ASPC
INACTIVE
AS BLUE
AS GREEN
AS Blue
Traffic Mode = Loadshare
AS Green
ASP List = ASPB, ASPC
SUA: Example Scenario

Signalling Gateway
ASPA
AS BLUE
ASPB
ACTIVE/STANDBY
ASPC
OVERRIDE
AS GREEN
AS Blue
Routing Key = DPC 2109, SI ISUP
Traffic Mode = Loadshare
AS Green
ASP List = ASPC, ASPB
Loadshare Example (Voice and SMS)
Loadshare Failover (Voice + SMS)
M3UA: Define Local Peer
Used to define the server process running in the ITP

The client in the UAS will connect to this address and port
number
Can have multiple server processes with a different unique
combination of port numbers or IP addresses
The first Local IP Address is the Primary, others are secondary
itp(config)# cs7 m3ua <local port>
itp(config-cs7-sua)# local-ip <local ip address>
itp(config-cs7-sua)# assoc-retransmit <number of retrans>
itp(config-cs7-sua)# path-retransmit <number of retrans>
itp(config-cs7-sua)# retransmit-timeout <rto-min> <rto-max>
itp(config-cs7-sua)# tx-queue-depth <queue-depth>
M3UA: Monitoring
itp# show cs7 m3ua
Sigtran M3UA RFC number: 3332
M3UA Local port: 2905
Local ip address:
State: active
Number of active M3UA peers:

Max number of inbound streams allowed:
Local receive window:
Max init retransmissions:
Max init timeout:
Unordered priority:
Extended UPU support:
Offload to VIP:
SCTP defaults for new associations
Transmit queue depth:
1000
Assoc retransmissions: 6
Minimum RTO:
500
ms
Bundle status:
on
Keep alive status:
true
Initial cwnd:
3000
Retrans cwnd rate:
50
SCTP instance handle: 1

10.20.66.23
10.20.66.151
5
17
64000
8
1000 ms
equal
disabled
No
Slot: -1
Cumulative sack timeout:

Path retransmissions:
Maximum RTO:
Bundle timeout:
Keep alive timeout:
Idle cwnd rate:
Retrans cwnd mode :
200 ms
3
1000 ms
5 ms
30000 ms
50
RFC
SUA Overview
SUA means no SCCP stack on the UAS/VPU/ASP

Other than that, equivalent to M3UA (except for ISUP CIC and SI
routing keys)
MAP IS-41
MAP IS-41
TCAP
TCAP
SCCP
SUA
MTP3
Signalling
Gateway
SCTP
IP
SUA
IP
Network
SS7
Network
MTP3
SCTP
MTP2
IP
MTP1
SCTP/IP
MTP1
SCCP
SCCP messages
ASP
MTP2
SCCP messages
SS7 SG
SS7
SEP
SUA: Define Local Peer
Used to define the server process running in the ITP

The client in the UAS will connect to this Address and Port
Number
Can have multiple server processes with a different unique
combination of port numbers or IP addresses
The first Local IP Address is the Primary, others are secondary
itp(config)# cs7 sua <local port>
itp(config-cs7-sua)# assoc-retransmit <number of retrans>
itp(config-cs7-sua)# path-retransmit <number of retrans>
itp(config-cs7-sua)# retransmit-timeout <rto-min> <rto-max>
itp(config-cs7-sua)# tx-queue-depth <queue-depth>
SUA: Monitoring
itp# show cs7 sua
Sigtran SUA RFC number: 3868
SUA Local port: 15000
Local ip address:
State: active
Number of active SUA peers:

Max number of inbound streams allowed:
Local receive window:
Max init retransmissions:
Max init timeout:
Unordered priority:
Offload to VIP:
SCTP defaults for new associations
Transmit queue depth:
1000
Assoc retransmissions: 6
Minimum RTO:
500
ms
Bundle status:
on
Keep alive status:
true
Initial cwnd:
3000
Retrans cwnd rate:
50
FastRetrans cwnd rate: 50
SCTP instance handle: 2

10.20.66.23
10.20.66.151
5
17
64000
8
1000 ms
equal
No
Slot: -1
Cumulative sack timeout:

Path retransmissions:
Maximum RTO:
Bundle timeout:
Keep alive timeout:
Idle cwnd rate:
Retrans cwnd mode :
200 ms
3
1000 ms
5 ms
30000 ms
50
RFC
M3UA and SUA Common Commands
Defining AS and ASP
Managing and ASP within an AS
SUA Loadshare
Verify status
AS and ASP Commands: Defining an ASP
To configure a CS7 ASP definition and enter ASP sub mode

itp(config)# cs7 asp asp-name <remote port> [<Local Port>] [m3ua|sua]
To define the ASP remote IP address

itp(config-cs7-asp)# remote-ip <Primary remote IP Address>
itp(config-cs7-asp)# remote-ip <Secondary remote IP Address>
Allows a new SCTP association with this ASP, but doesn't let it
become active. If block is set while the ASP is active, it is forced
inactive but the association remains up
itp(config-cs7-asp)# block
Terminates the SCTP association with this ASP. New SCTP

associations will be rejected if the ASP is in shutdown mode
itp(config)# cs7 asp asp-name
itp(config-cs7-asp)# shutdown
AS and ASP Commands: Defining an AS
To configure a CS7 AS definition and enter AS sub mode

itp(config)# cs7 as as-name [m3ua|sua]
To define the AS routing key (M3UA)

itp(config-cs7-as)# routing-key rcontext {gtt | dpc [opc pc pc-mask]
[si {isup | sccp | tup}] [[cic cic-min [cic-max]] | [ssn ssn]]}
To define the AS routing key (SUA)

itp(config-cs7-as)# routing-key rcontext {gtt | dpc [opc pc pc-mask]
[ssn ssn]}
(si sccp is implied in SUA)
To define the AS traffic mode:

itp(config-cs7-as)# traffic-mode {broadcast | loadshare [bindings |
roundrobin] | override }
AS and ASP Commands: Managing an ASP for an AS
To add the ASPs to the AS

itp(config)# cs7 as as-name
itp(config-cs7-as)# asp asp-name
itp(config-cs7-as)# asp asp-name
To remove the ASPs contained in the AS

itp(config)# cs7 as as-name
itp(config-cs7-as)# no asp asp-name
To stop any further traffic being routed to the AS

itp(config-cs7-asp)# shutdown
Note: The ASP must be previously defined
SUA: Verify Status
Verify the state of the AS:
itp# show cs7 as name AS-ubeastest detail

AS name: AS-ubeastest
State: down
Type: SUA
RoutContxt: 121
Traffic mode: loadshare roundrobin
Mate AS state: unknwn
Recovery tmout: 2000 ms
Recovery queue depth: 0
QOS Class: 0
Burst recovery tmout: 4000 ms
Routing Key:
Dest PC: 4916
Origin PC: n/a
Origin PC mask: n/a
SI: n/a
SSN: n/a
ASP Name
ASP-ASP1
ASP-SCP2
ASP-SCP1
CIC min: n/a

GTT: n/a
AS Name
State
AS-ubeastest
down
AS-ubeastest
down
AS-ubeastest
down
CIC max: n/a

Type
SUA
SUA
SUA
Rmt Port Remote IP Addr

14001
172.18.24.39
14000
172.18.24.40
14002
172.18.25.39
Mated SG and SGMP Overview
Mated-pair SG
ASP can have Active association with multiple SGs.

If an ASP has an Active association with an SG it is assumed to be
available for traffic.
Can be primary/backup model or load-share model.
Signalling Gateway Mate Protocol (SGMP) allows SGs to establish

an association to a mated SG with an equivalent configuration
Mated pair SGs load share or backup each other
Mated-pair SGs must have equivalent SG configuration (same AS
and AS Route Table routing-key)
The local point code of each SG must be unique and each AS in
its own SG must have a different point code from the equivalent
AS in the mated SG
Mated SG and SGMP Commands
To enable SGMP and specify the SGMP local port

itp(config)# cs7 sgmp local-port
To configure a local IP address for use by SGMP.

itp(config-cs7-sgmp)# local-ip ip-address
To define mated SG and enable CS7 mated-sg sub mode

itp(config)# cs7 mated-sg mate-name remote-port [passive]
To specify the remote IP address of the mate

itp(config-cs7-mated-sg) remote-ip remote-ip
To define the QoS class for the SG mated pair

itp(config-cs7-mated-sg) qos-class class
Agenda
Global parameters
IP Network Design
M2PA commands
M3UA commands
MTP3 Routing
Global Titles
Debug commands
Troubleshooting
MTP3 Routing
Routes are based on DPC (Destination Point Code) and are used to choose
which linkset the MSU is forwarded out via system routing table
Routes have priorities 1 through 9 (priority 1 is most preferred)
Complete support for all ITU, ANSI, China MTP3 Routing & Traffic
Management Procedures
TFR/TFA/TFP/TFC
Forced and Controlled Rerouting
Change-Over and Change-Back
MTP3 Gateway Screening
rules can be built on DPC, OPC, SI, Hex Pattern + Offset
Detailed rules can be built to restrict or permit very specific traffic flows
MTP3 Accounting
Per Linkset measurements inbound & outbound (Total MSUs & Total Bytes)
Recorded based on DPC, OPC & SI (gateway screening accounting also)
MTP3 Routing (continued)
Summary Routing
Allows summarization of large scale routing tables based on a point code

hierarchy
Basically allows you to route all point codes that begin with common
numbers to a given destination
Comparable to variable length subnet masking (VLSM) in the IP world
Dual-Point Codes
Allows ITP to be assigned a secondary point code for establishment of an

additional linkset between the ITP & an adjacent node
Doubles the capacity between edge node & ITP from 16 links (SS7
limitation) to 32 links.
One method of working around bandwidth limitations to SEP nodes (ITP
provides several methods: HSL, M3UA, SUA)
MTP3 Routing: Route Commands
To add a route to the Cisco ITP route table, use the following
command in global configuration mode:
itp(config)# cs7 route-table system
itp(config-cs7-rt)# update route point-code [mask | length] linkset
ls-name [priority priority-value 1 ] [qos-class class]
Note. The smaller the number, the higher the priority.
itp# show cs7 route (or show cs7 route detail or show cs7 route P/C)
Routing table = system
Destination
Prio Linkset Name
Route
-------------------- ---- ------------------- ------4904/14

4905/14
4700/14
RESTR
acces
acces
itp1-msc1
UNAVAIL
itp1-itp2
avail
itp1-msc2
avail
itp1-itp2
UNAVAIL
itp1-msc1
avail
itp1-itp2
avail
MTP3 Rerouting with Sigtran Reliability

Resilience Hierarchy
MTP
SCTP Multi-Homing
IP Routing
IP Routing
Level 0: Data Link Layer

Level 1: IP
IP routing protocols can detect path outages and re-route (e.g. HSRP, etc).
Level 2: SCTP
When SCTP Multi-homing detects unresponsiveness in the current IP path, it changes
the IP path used for the session by changing the source and/or destination IP address
of the session. During this process, the SCTP session remains active and MTP3 is
unaware of the path change.
Level 3: MTP
If SCTP/IP can not correct the issue, MTP3 is notified to initiate standard MTP3
rerouting procedures
MTP3 Accounting
auckland-itp1# show cs7 accounting

Linkset = itp1-msc1'
Destination Originating Service
Point Code
Point Code
Indicator
Input
Packets
Output
Bytes
Packets
Bytes
----------- ----------- ---------- ---------- ---------- ---------- ---------4904
4912
25
Linkset = itp1-msc2
Point Code
Point Code
Indicator
Input
Packets
Output
Bytes
Packets
Bytes
----------- ----------- ---------- ---------- ---------- ---------- ---------4905
4912
25
MTP3 Checkpoint Accounting
itp(config)# cs7 accounting checkpoint-interval 5

Checkpoint Interval = 5 min
itp# show cs7 accounting checkpoint
Checkpoint Interval = 5 min
Linkset = 'itp1-msc1'
Point Code
Point Code
Indicator
Input
Output
Packets
Bytes
Packets
Bytes
----------- ----------- ---------- ---------- ---------- ---------- ---------Destination Originating Service

Point Code
Point Code
Indicator
Input
Output
Packets
Bytes
Packets
Bytes
----------- ----------- ---------- ---------- ---------- ---------- ---------4913
4912
24254
291031
4904
4912
72694
872328
4913
4904
25
271
4904
4913
72694
872328
Configuring SCCP and GTT
Global Title Commands
GTT based Routing
Called Party Address
Intermediate versus Final translation
Global Title Addresses
Global Title commands
Global Title file commands
Global Title monitoring
SCCP versus MTP3 Routing Headers
Serv. SubSLS
Indic. serv
(SCCP) Field (5 Bits)
DPC
3
Routing Label
MTP2
Called
Calling
Message Protocol
Party
Party
Type
Class
Address Address
# of Bytes
OPC
Signalling Information Field
Data
2
252
^
^
MSU
Service
Information
MTP2
Global Title: Called Party Address
Remember, this is the SCCP Called Party Address!
8
OCTET
Nat/Intnl Routing
Indicator Indicator
2
Point
Code
Indicator
Subsystem Number
Signalling Point Code
Global Title
1
Subsystem
Number
Indicator
Bit
Pos
Global Title: Intermediate versus Final
Final GTT is a translation in which the DPC that is inserted into

the MSU is the final destination
Result is usually a Signaling End Point (SEP)

Routing indicator (RI) bit is set. RI == Route on PC/SSN
Intermediate GTT is a translation in which a DPC is inserted into

the MSU for an intermediate hop that will again perform GTT on
that MSU
Result is another node which will perform GTT

Routing indicator (RI) bit is cleared. RI == Route on GT
DPC = ITP1
RI = GT
Intermediate
GTT
DPC = ITP2
RI = GT
Final
GTT
MSC
DPC = UAS
RI = PC/SSN
UAS

0000
Reserved
0001
Nature of Address is ignored. Translation Type = Unknown

and Numbering Plan = E.164 (value 1).
0010
This is most commonly used in North American networks.

The Translation Type implicitly determines Nature of Address
and Numbering Plan. This data can be configured in the SG.
The number of digits is always even and determined by the
SCCP address length.
0011
Numbering Plan and Translation Type are taken over. It is

implicitly assumed that the Nature of Address = Unknown.
0100
This format is used in international networks and most

commonly in networks outside North America. All information
to populate the source address is present in the SCCP
Address.
Numbering Plan
Numbering Plan:
0
unknown
ISDN/telephony numbering plan (E.163 and E.164)
generic numbering plan
data numbering plan (Recommendation X.121)
telex numbering plan (Recommendation F.69)
maritime mobile numbering plan (E.210, E.211)
land mobile numbering plan (E.212)
ISDN/mobile numbering plan (E.214)
8 13
spare
14
private network or network-specific numbering plan
15 - 126 spare
127
reserved.
Translation Type and Nature of Address
Translation type:
0
Unknown
1 63
International services
64 127
Spare
128 254
National network specific
255
Reserved
Nature of Address Indicator:

0
unknown
subscriber number
reserved for national use
national significant number
international number
5 255
Spare
NOTE: NAI in SCCP HEADER IS NOT THE SAME AS IN MAP or TON!!
Global Title: What is a GTA?
A GTA is a string of address digits which is used to match the CgPA or

CdPA digits
The GTA entry provides what to match & what action to perform on a
match
1 to 15 digits are supported at variable lengths
Result can be Intermediate or Final GTT
Support for replacing the PC/SSN/TT/RI
Result can be PC/SSN, MAP, Application Group
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.
Translation Type (TT)
Global Title Indicator (GTI)
Numbering Plan (NP)
Nature of Address Indicator (NAI)
Global Title: Commands
GTT selector configuration

itp(config)# cs7 gtt selector <selector-name> tt <tt> gti <gti> np
<np> nai <nai>
itp(config)# cs7 gtt selector NP tt 0 gti 4
GTT selector configuration
Add a GTA entry

itp(config-cs7-gtt-selector)# gta <gta digits> pcssn <point code>
<routing indicator> ssn <ssn> or ntt <ntt>
Add a GTA Intermediate entry

itp(config-cs7-gtt-selector)#
pcssn 9240 gt
Add a GTA Final entry

>cs7-gtt-selector)#
gta 919824
gta 919827002402 pcssn 8435 pcssn ssn 12
For final GTT, the ITP NEEDS to be aware of the status of the PC
and SSN that results from the GTT (we cover this soon)
Global Title: File Commands
GTT database is loaded from a file unlike other IOS configurations

that are stored in NVRAM
GTT database can be loaded or stored from/to any onboard, local
file system or external server connected via IP
Specify the location to load the GTT database
itp(config)# cs7 gtt load <url> [execute]
itp(config)# cs7 gtt load flash:gttdata.txt execute
Specifying the execute immediately loads and executes the GTT.

Omitting the execute simply changes the configuration for next
reload
The URL can be any supported system URL
After any changes, update master database on file

itp# cs7 save gtt <url>
itp# cs7 save gtt flash:gttdata.txt
Global Title: Monitoring
To display the selectors defined

itp# show cs7 gtt gta selector_name
To display the gta under a specific selector

itp# show cs7 gtt selector
To display the gtt performed by selector

itp# show cs7 gtt measurements selector
To display the gtt performed (system wide)

itp# show cs7 gtt measurements
Global Title: Application Groups
An Application Group is a method to share traffic SENT to a GT

between a number of point codes
It can share the traffic via a number of separate modes called
multiplicity:
multiplicity cost
multiplicity share
multiplicity cgpa
multiplicity cost: use the destination with the least cost if

available.
multiplicity share: share equally between all destinations.
multiplicity cgpa: use the SCCP calling party address (CGPA) field,
which results in a weighted factor selection number for choosing
the next destination from the available items in the application
group.
Application Groups: Multiplicity Cost
This is how cost based load sharing works:
Final:
Intermediate:
Application Groups: Multiplicity Share
This is how cost based load sharing works:
Final:
Intermediate:
Global Title: Load Share Application Groups
To define an application group

itp(config)# cs7 gtt application-group <App-Group name>
Set the multiplicity (the method the traffic will use to share)
itp(config)# multiplicity {cost | share | cgpa}
Use the application group name in final GTT translation

itp(config)# pc pc [ssn ssn] [cost cost] pcssn
Use the application group name in intermediate GTT translation

itp(config)# pc pc [ssn ssn] [cost cost] gt
cs7 gtt application-group GSM-MOX-GT1
multiplicity cost
pc 8435 ssn 146 1 pcssn
pc 8436 ssn 146 2 pcssn
!
cs7 gtt application-group GSM-SMS-1
multiplicity share
pc 8436 1 pcssn
pc 8437 2 pcssn
Load-Sharing Summary
Traffic
Mode
Other
Tools
Broadcast
SCCP
Class 0
SCCP
Class1
SCCP Distribute
Un-sequenced off
SCCP Distribute
Un-sequenced on
Always
Sequenced
N/A
Broadcast
all receive
Broadcast
all receive
Broadcast
all receive
Loadshare
Bindings
None
SLS
Round Robin
SLS
Loadshare
round robin
None
Round Robin
Round Robin
SLS
Loadshare
weighted
round robin
None
Weighted Round
Robin
Weighted Round
Robin
Weighted Round
Robin and SLS
Override
N/A
Override
no load sharing
Override
no load sharing
Override
no load sharing
Global Title: Monitoring GTT Application Groups
To display application group entries

ITP# show cs7 gtt application-group
Application Group Name: group1
Multiplicity : share
Ref Count : 1
Application Identifier RI Cost
---------------------- ----- ---PC=1.1.1 SSN=10 gt 1
PC=1.1.2 SSN=10 gt 2
PC=1.1.3 SSN=10 gt 3
Application Group Name: group2
Multiplicity : share
Ref Count : 1
Application Identifier RI Cost
---------------------- ----- ---PC=2.2.2 SSN=10 pcssn 1
PC=2.2.3 SSN=10 pcssn 2
PC=2.2.4 SSN=10 pcssn 3
Global Title: Mated Application Entries
An MAP entry is a way of tracking status of PC and SSN that are

the target of FINAL GTT Translations
It can define the target in a number of multiplicities:
solitary - use a single PC, no alternate if PC and/or SSN is not

available.
share - load share equally across the primary PC/SSN and backup
PC/SSN.
dominant - always translate to primary PC/SSN if available, and only
translate to backup if primary is unavailable.
It can take one of the following flags:
adj - Mark ppc/pssn as adjacent
csplist name - Specifies a concerned point code list name.
rrc - Reroute if congested
Global Title: Mated Application Commands
Define a MAP entry
itp# cs7 gtt map ppc pssn [flags] mult [bpc] [bssn]
Display MAP entries
ITP# show cs7 gtt map

PPC
PSSN
MULT
4154
12
sol
-----------
---
off
no 1
5424
12
sol
-----------
---
off
no 1
5552
12
sol
-----------
---
off
no 1
BPC
BSSN ConPCLst RRC ADJ Ref
Display MAP entries
ITP# show cs7 gtt map statistics

PC
SSN
PCST
SST
CONGESTED
668
250
UNAVL
avail
---------
1008
250
avail
UNAVL
---------
2020
250
avail
avail
level 2
Global Title: Mated Application Entries
We need ONE of these entries for each GTT FINAL translation
In general, we only use solitary:

cs7
cs7
cs7
cs7
!
cs7
cs7
cs7
cs7
gtt
gtt
gtt
gtt
map
map
map
map
82 7 sol
82 8 sol
589 7 sol
589 8 sol
gtt
gtt
gtt
gtt
map
map
map
map
8431
8432
8433
8434
14 sol
14 sol
14 cpclist CPC-LIST-1 sol
14 cpclist CPC-LIST-1 sol
The concerned PC list will show which machines will get updates
on the change in status of the destination point code:
cs7 gtt concern-pclist CPC-LIST-1 320
Global Title: Monitoring Statistics
To display the selectors defined

itp# show cs7 gtt gta selector_name
To display the gta under a specific selector

itp# show cs7 gtt selector
To display the gtt performed by selector

itp# show cs7 gtt measurements selector
To display the gtt performed (system wide)

itp# show cs7 gtt measurements
To display measurements kept on a GTT application group basis

show cs7 gtt measurements app-grp [app-grp]
To display measurements kept on a GTT MAP basis

show cs7 gtt measurements map
M2PA commands
M3UA commands
MTP3 Routing
Global Titles
Debug commands
Troubleshooting
Debug Commands
Well cover more on this a bit later
We have to be VERY careful with DEBUG
DONT EVER, EVER, EVER turn it on in production
Agenda
Global parameters
IP Network Design
Network Designs
Network Design to Support eSG IN
We need to design a solid, reliable network to support the IN
It must be redundant, fast and (mostly) dedicated

Network
Function
Enables access to
Facility
Machines
External Access
NTP, SNMP, syslog, Users
FWT
All
Replication
Service Data (IN Internal)
Both
All non ITP
Billing
IN Billing elements
GSM
UAS, USMS, UBE
Sigtran
IP Signalling elements
Both
UAS and ITP
Cluster
Private Cluster I/C
GSM
USMS
Alarm
NTP, SNMP, syslog, Users
GSM
All
Backup
Path to backup server
FWT
UAS, USMS
UAS and USMS Connectivity
Example Server Port Allocation

Server
Port
1st QFE Quad LAN Card

ce0
ce1
ce2
Extern
Billing/
Rep.
Cluster
UAS
Extern
Billing/
Rep.
UBE
Extern
USMS
Billing/
Rep.
Sigtran
ce3
Alarm
Alarm
2nd QFE Quad LAN Card

ce4
ce5
ce6
Extern
Billing/
Rep.
Cluster
Extern
Billing/
Rep.
A
Alarm
Extern
Billing/
Rep.
Sigtran
ce7
Alarm
Alarm
B
Alarm
Any single board or switch failure can be tolerated
Each cable on the same network uses a different IP switch
Any two port/cable failures can be tolerated (not on the same

net on the same machine i.e. ce0 and ce2 above on the one
machine can be tolerated, but not ce0 and ce4)
Example Replication Network Design
Example Signalling Network Design
External Network Design Limited Redundancy
Agenda
Global parameters
IP Network Design
Some Example Traffic Flows
Initial Trigger
Initial Response
Subsequent
Practical Implementation Example
Building Working Configuration
Boy, Im confused? How do we put all this together?

We are going to use our points of knowledge towards building a
configuration:
Look at the logical and physical design
Look at the network
Understand the flow of messages around the network
Work up the configuration
Look at the Global Title Translation
Developing a Configuration
Problem: ITP and HssScIf configuration for the following scenario:
Configuration: General Parameters

Global Parameter
Value
Notes
IOS Version
12.2
ITP Release 3
Boot Code
25SW1 Release
12.2(25)SW1 for 2651XM
Host Names
IN-MODEL-ITP1
IN-MODEL-ITP2
IP short name
Debug Timestamps
Local time with mSecs and TZ
mSecs gives good resolution
Log Timestamps
Local time with mSecs and TZ
mSecs gives good resolution
Service Password
encrypted
Log File
512000 bytes with debug logging
Enable Password
root
Time Zone
CET, 1 hours from UTC
We use CET for this example
Time Server
172.25.1.8
NTP Server
Global Title Table file name
flash:gttdata.txt
flash: is the disk device
Logging History Size
5000
Banner
Something Nasty
Warn intending hackers.
Proposed Example Network Design
Configuration: Prologue entries
version 12.2
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
service password-encryption
This is the name of the box.
service internal
!
hostname ITP1
The image to load
!
boot system flash c2600-itp-mz.122-25.SW1.bin
This password becomes encrypted when it is
logging buffered 500000 debugging
configured onto the ITP and then it will be shown
logging history size 500
as secret 5 followed by a 30 digit base 64
enable secret 0 <TBD>
number to represent the actual password as a
!
180 bit long hash value in MD5.
clock timezone GMT 0
ntp server 172.25.1.8
This GTT table will be created
cs7 gtt load flash:gttdata.txt execute
later on in the configuration
!
banner login _
***********************************************************************
***
WARNING!!
This service is for authorised users only
***
***********************************************************************
_
Configuration: Variant
The following describes the SS7 Signalling parameters that are defined on
a global level for the whole network.
!
cs7
cs7
cs7
cs7
!
Global SS7 Parameter
Possibilities
Value
SS7 Variant
ANSI or ITU
ITU
SS7 Routing
PC/SSN or Global Title
PC/SSN
Point Code Delimiter
. or -
Dash
Point Code format
Decimal digits
14
Network Indicator
Int, Nat, Reserved
Reserved
variant ITU
point-code delimiter dash
point-code format 14 descriptor decimal
network-indicator reserved
Configuration: Points Codes and GTAs
Each node that communicates over the SS7 network uses one of:
INAP/SCCP over SCTP/IP as a Sigtran SUA association (SCP/UAS, UMS VPU);
ISUP/MTP3 over SCTP/IP as a Sigtran M3UA association (PGW2200);
Legacy SS7 over MTP2 (MSC, STP);
All of the above, M3UA, SUA and MTP2 (ITP Signalling gateway).
Component
Point Code 1
Global Title
ITP1
4912
N/A
ITP2
4913
N/A
SCP/UAS
4916
4526102044
MSC
4904
N/A
!
cs7 point-code 4912
!
!ITP1 is PC 4912=2.102.0
This GT will need final

translation to PC 4916
Configuration: Global Title Addresses 1/3
The following describes the Global Title Translation parameters

that are used on a global level for the whole environment.
Global Title Parameter
Possibilities
Value
GT Translation Type
0-255
0=Unknown
0, 1, 2, 3, 4
4=ITU
Nature of Address Indicator
0, 1, 2, 3, 4
Numbering Plan
0, 1, 2
Name for Selector
Any Value
GLOBAL
Name for GTT Table
Any Value
gttdata.txt
See Section
3.10.2.3 Global Title
in the IETF Sigtran
SUA RFC for further
information on GTT
fields.
!
cs7 gtt selector GLOBAL tt 0 gti 4 np 1 nai 4
!Creates a selector
!
! Note that the following command is an EXEC command, and not in config mode
!
cs7 save gtt-table flash:gttdata.txt
!
This GTT table will be loaded in
the configuration during startup
The following lines are added to the ITP Global Title table to reflect the
translation of Global Title Addresses to point code.
The Global Title Selector GLOBAL is updated with the addition of the
GTA for the SCP.
The GTA 4526102044, is translated to its associated Point Code (4916)
and then sent on its way with routing now changed to be on PC/SSN.
This is FINAL Global Title Translation
RI=PCSSN
i.e. FINAL
!
cs7 gtt selector GLOBAL
!Add to the selector defined above
gta 4526102044 pcssn 4916 pcssn
!UAS is PC 4916
!
!
!
The following lines are added to the ITP Global Title table to deal with any
other GT based traffic that it may receive.
To facilitate possible future load-sharing, we will define an application
group that contains the PC (4904) of the MSC (we can add to it later)
The Global Title Selector GLOBAL is updated with the addition of the
GTA for any other GTA that doesnt match a particular prefix.
This is INTERMEDIATE Global Title Translation
!
! Create the application group
!
cs7 gtt application-group MSC
RI=GT i.e. intermediate
multiplicity share
pc 4904 1 gt
!
! Add the default GT
!
cs7 gtt selector GLOBAL
!Add to the selector defined above
gta default
app-grp MSC
!Send all other GT to the MSC
!
!
Configuration: Physical Connections on the ITP
There are the three major physical interconnects between the

PSTN and the eServGlobal platforms.
INAP Signalling link
ISUP Signalling link (the subject of another discussion)
Voice Trunks (the subject of another discussion)
The 2651 has FOUR possible E1 interfaces, they are:
Controller E1 0/1
Controller E1 0/2
Controller E1 0/3
Controller E1 0/4
!
controller
shutdown
!
controller
shutdown
!
controller
shutdown
!
controller
shutdown
E1 0/0
E1 0/1
E1 0/2
E1 0/3
Configuration: Defining the links
We have one INAP connection to

the controller E1 0/0
The channel-group command
creates a serial interface known
as serial 0/0:0
Physical Parameter
INAP Connection
Interface Type
Channelised E1
ITP Terminating host
ITP1
Port on ITP
Port 0 on Card 0
Clock Source
Line
Framing
crc4
Linecode
hdb3
Timeslot
1, 2
controller E1 0/0
clock source line
framing CRC4
channel-group 0 timeslots 1
no shutdown
!
controller E1 0/1
This channel group
shutdown
number creates this
!
interface device.
controller E1 0/2
shutdown
!
controller E1 0/3
shutdown
!
interface Serial0/0:0
no ip address
encapsulation mtp2
no shutdown
!
no ip address
encapsulation mtp2
no shutdown
!
Configuration: MTP3 Parameters

Timer
Description
Link Test T1 (Link test acknowledgement timer)
slt-t02
Link Test T2 (Interval timer for sending test msgs.)
t01
T1 (Delay to Avoid message mis-sequencing)
t02
T2 (Wait for Changeover acknowledgement)
t03
T3 (Delay to avoid mis-sequencing in changeback)
t04
T4 (Wait for Changeback acknowledgement 1st attempt)
t05
T5 (Wait for Changeback acknowledgement 2nd attempt)
t12
T12 (Wait for uninhibited acknowledgement)
t13
T13 (Wait for force uninhibited)
t14
T14 (Wait for inhibition acknowledgement)
T17
T17 (oscillation of alignment failure and link restart )
T19
T19 (failed link craft referral timer)
T20
T20 (Wait to repeat local inhibit test)
T21
T21 (Wait to repeat remote inhibit test)
t31
T31 (false link congestion timer)
t32
T32 (Link oscillation timer - Procedure A)
retry
Link Retry (Link activation retry timer)
Dont play with these unless you have to!
slt-t01
Configuration: Ethernet Interfaces
This ITP is on two networks:
178.18.24.31/24 address is 31
178.18.25.31/24 address is 31
interface FastEthernet0/0
ip address 178.18.24.31 255.255.255.0
speed 100
full-duplex
no cdp enable
no shutdown
!
!
ip address 178.18.25.31 255.255.255.0
speed 100
full-duplex
no cdp enable
no shutdown
Configuration: SCTP M2PA Peers
For SCTP connections for M2PA, we need to define the IP

addresses and port numbers for SCTP to use on ITP1. This is
done with a cs7 local-peer command.
As we saw from the Ethernet configuration, we have two IP
addresses, and we therefore declare both of them to be available
to handle M2PA linksets.
We use port number 7000 locally.
!
cs7 local-peer 7000
local-ip 172.18.24.31
local-ip 172.18.25.31
!Local (ITP1) IP address on one subnet

!Local (ITP1) IP address on the other subnet
Configuration: TDM Linksets
We have defined two MTP2 links on the E1 0/0 controller with the
following interfaces:
Serial 0/0:0
Serial 0/0:1
Now to make them part of a linkset. To do this, we need:
the PC of the end point, which is the MSC, 4904
The SLC of the two links, 0 and 1
cs7 linkset itp1-msc1 4904

accounting
link 0 Serial0/0:0
link 1 Serial0/0:1
!
Here is the PC of the MSC
This number corresponds

to the SLC for this link of
the linkset.
Configuration: SIGTRAN Linksets
Now we set up a linkset between the ITPs as well. This is a

linkset over SCTP (Sigtran!!).
Q? This is therefore a <what> Link?
We have two redundant IP addresses to ITP2
24.32 on one subnet

25.32 on the other.
Q? Why do we set up this ITP-ITP linkset?
4913 is the PC of the remote ITP2.
The port number for the local-peer on the remote ITP is 7000
The port number for the local-peer on our ITP is also 7000
accounting
link 0 sctp 172.18.24.32 172.18.25.32 7000 7000
!
Q? What is the big benefit here?
Here is the PC of ITP2
This number corresponds

to the SLC for this link of
the linkset.
Configuration: Mated Signalling Gateways
For SGMP connections for Mated Signalling Gateways, we need to

define the IP addresses and port numbers for SGMP to use on
ITP1. This is done with a cs7 sgmp command.
As we saw from the Ethernet configuration, we have two IP
addresses, and we therefore declare both of them to be available
to handle SGMP communications.
We use port number 15001 locally.
We then declare that our mate (ITP2) has two IP addresses on
the same port number on the other ITP (that number coming
from its own cs7 sgmp command).
!
cs7 sgmp 15001
local-ip 172.18.24.31
local-ip 172.18.25.31
!
cs7 mated-sg ITP2 15001
remote-ip 172.18.24.32
remote-ip 172.18.25.32
!

!Remote (ITP2) IP address on one subnet
!Remote (ITP2) IP address on the other subnet
Configuration: Local M3UA Definitions for V.SSP (ISUP)
For M3UA connections for non-SCCP applications (eg ISUP

signalling for the V.SSP), we need to define the IP addresses and
port numbers, for M3UA to use LOCALLY on ITP1.
This is done with a cs7 m3ua command.
We use port number 2905 locally for both IP addresses for ITP1.
Transaction Queue Depth can be adjusted, as in this case.

Q? Why should we NOT do this?
!
cs7 m3ua 2905
local-ip 172.18.24.31
local-ip 172.18.25.31
tx-queue-depth 2000
!

Configuration: Defining M3UA ASPs
Simply,
ASP is the location (machines) where the service runs
AS is the application (service) that is available to run
For M3UA associations with ASPs we need to define:
ASP (locations) with cs7 asp xxxxxxx port-r port-l m3ua
We use port number 2905 remotely for two IP addresses for:
Two VSSP machines, both running in load-share and redundant
Called VSSP1 and VSSP2
cs7 asp ITP-VSSP1-ASP 2905 2905 m3ua

remote-ip 172.18.24.xxx
!Remote
remote-ip 172.18.25.xxx
!Remote
!
cs7 asp ITP-VSSP2-ASP 2905 2905 m3ua
remote-ip 172.18.24.yyy
!Remote
remote-ip 172.18.25.yyy
!Remote
!
(VSSP1) IP address on one subnet

(VSSP1) IP address on the other subnet
(VSSP2) IP address on one subnet
(VSSP2) IP address on the other subnet
Configuration: Defining M3UA ASs
For M3UA associations with ASs we need to define:
AS (services) with cs7 as xxxxxxx m3ua and the ASPs they are at.
Need to define the traffic method, broadcast or loadshare or override
We need for the Service:
Routing Keys (lets make it 100 and 200)
Point Codes (for this service, the PCs are 100 and 200)
Service Indicator (ISUP in this case)
We now allocate the two ASPs to the two AS

!
cs7 as ITP-VSSP1-AS m3ua
routing-key 100 100 si isup
asp ITP-VSSP1-ASP
!
cs7 as ITP-VSSP2-AS m3ua
routing-key 200 200 si isup
asp ITP-VSSP2-ASP
!100 is the routing key, 100 is the PC of VSSP1

!This ASP is where the service is available
!200 is the routing key, 200 is the PC of VSSP2
!This ASP is where the service is available
Configuration: Local SUA Definitions for SCCP Apps.
For SUA connections for SCCP applications (eg INAP or CS-1), we

need to define the IP addresses and port numbers, for SUA to use
LOCALLY on ITP1.
We use port number 15000 locally for both IP addresses for ITP1.
!
cs7 sua 15000
local-ip 172.18.24.31
local-ip 172.18.25.31
!

Configuration: Defining SUA ASPs
Simply,
ASP is the location (machines) where the service runs
AS is the application (service) that is available to run
For SUA associations with ASPs we need to define:
ASP (locations) with cs7 asp xxxxxxx port-r port-l sua
We use port number 14001 remotely for each IP address pair for:
UAS
Any other ASP
!
cs7 asp ITP-UAS-ASP 14001 15000 sua
remote-ip 172.31.71.176
!Remote (UAS) IP address on one subnet
remote-ip 172.31.71.208
!Remote (UAS) IP address on the other subnet
Configuration: Defining SUA ASs
For SUA associations with ASs we need to define:
AS (services) with cs7 as xxxxxxx sua and ASPs where they can be
located.
No need to define the traffic method, only one ASP for each service.
We need for these services:
Routing Key (lets make it 121)
Point Code (4916 for UAS)
Service Indicator (SCCP in both cases)
SSN for SCCP INAP service (optional)
!
cs7 as ITP-UAS-AS sua
routing-key 121 4916
asp ITP-UAS-ASP
si
sccp
!This service is available on the UAS
Configuration: Define SS7 Routes
We need to statically route traffic to any other SEP (we are only
connected to the MSC with this one TDM linkset).
We assume a PC of 5200 for this SEP
If we need to talk to that SEP, we need to send the packets on
to an interim destination towards the SEP.
The STP is also connected to our mated ITP, therefore another
route is via that path. To be used in event of failure, therefore of
a lower priority.
The default route table is system
BE CAREFUL TO AVOID LOOPING!

cs7 route-table system
update route 5200/14 linkset itp1-msc1 priority 3
update route 4904/14 linkset itp1-itp2 priority 5
update route 5200/14 linkset itp1-itp2 priority 7
!SEP via MSC

!MSC via ITP2
!via ITP2
Configuration: Console and Auxiliary Lines
Console
Set a timeout of 120 minutes
Set a timeout of 60 minutes for exec mode
Set a login password
Aux
Forget about it
!
line con 0
session-timeout 120
exec-timeout 60 0
password 0 <TBD>
login
!
line aux 0
This password becomes encrypted when it

is configured onto the ITP and then it will
be shown as secret 7 followed by a 10
digit hex number. This is a simple Vigenere
cipher, and not very secure.
Configuration: Virtual Lines
Virtual Lines
Define five of them, 0-4
Set a timeout of 120 minutes
Set a timeout of 60 minutes for exec mode
Set a login password
!
line vty 0 4
session-timeout 120
exec-timeout 60 0
password 0 <TBD>
login
This password becomes encrypted when it

is configured onto the ITP and then it will
be shown as secret 7 followed by a 10
digit hex number. This is a simple Vigenere
cipher, and not very secure.
Configuration: Other IP Stuff
The Rest?
Dont use DNS lookup.
Turn off Cisco Discovery Protocol (CDP) and IP Routing
Allow subnet-zero (or not)
Set up the Default Route (s)
Use classless IP (dont stick to Class A, B, C)
Dont run the HTTP configuration server
no
no
no
ip
!
ip
ip
ip
no
ip domain-lookup
ip routing
cdp run
subnet-zero
classless
route 0.0.0.0 0.0.0.0 172.18.24.1
route 0.0.0.0 0.0.0.0 172.18.25.1
ip http server
!Virtual address for default G/W Subnet 1

!Virtual address for default G/W Subnet 2
Configuration: One More Thing
Dont specify ntp clock-period

The value is calculated from the clock.
Done! Now the Hughes interface
But first, what does it all look like in one file?
Configuration: ITP1 Configuration 1/8
version 12.2
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
service password-encryption
service internal
!
hostname ITP1
!
boot system flash c2600-itp-mz.122-25.SW1.bin
logging buffered 500000 debugging
logging history size 5000
enable secret 0 <TBD>
!
clock timezone GMT 0
ntp server 172.25.1.8
cs7 gtt load flash:gttdata.txt execute
!
banner login _
***********************************************************************
***
WARNING!!
This service is for authorised users only
***
***********************************************************************
_
!
cs7 variant ITU
cs7 point-code delimiter dash
cs7 point-code format 14 descriptor decimal
cs7 network-indicator reserved
!
!
cs7 point-code 4912
!ITP1 is PC 4912=2.102.0
!
! Create an application group
!
cs7 gtt application-group MSC
multiplicity share
pc 4904 1 gt
!
cs7 gtt selector GLOBAL tt 0 gti 4 np 1 nai 4
!Creates a selector
gta 4526102044 pcssn 4916 pcssn
!UAS is PC 4916
!
! Add the default GT
!
gta default
app-grp MSC
!Send all other GT to the MSC
!
controller E1 0/0
clock source line
framing CRC4
no shutdown
!
controller E1 0/1
shutdown
!
controller E1 0/2
shutdown
!
controller E1 0/3
shutdown
!
no ip address
encapsulation mtp2
no shutdown
!
no ip address
encapsulation mtp2
no shutdown
!
ip address 178.18.24.31 255.255.255.0
speed 100
full-duplex
no cdp enable
no shutdown
!
ip address 178.18.25.31 255.255.255.0
speed 100
full-duplex
no cdp enable
no shutdown
!
cs7 local-peer 7000

local-ip 172.18.24.31
local-ip 172.18.25.31
!
accounting
link 0 sctp 172.18.24.32 172.18.25.32 7000 7000
!
cs7 linkset itp1-msc1 4904
accounting
link 0 Serial0/0:0
link 1 Serial0/0:1
!
cs7 sgmp 15001
local-ip 172.18.24.31
local-ip 172.18.25.31
!
cs7 mated-sg ITP2 15001
remote-ip 172.18.24.32
!Remote (ITP2) IP address on one subnet
remote-ip 172.18.25.32
!Remote (ITP2) IP address on the other subnet
!
cs7 sua 15000
local-ip 172.18.24.31
local-ip 172.18.25.31
!Local (ITP1) IP address on the other
subnet
!
cs7 asp ITP-UAS-ASP 14001 15000 sua
remote-ip 172.31.71.176
!Remote (UAS) IP address on one subnet
remote-ip 172.31.71.208
!Remote (UAS) IP address on the other
subnet
!
cs7 as ITP-UAS-AS sua
routing-key 121 4916 si sccp
asp ITP-UAS-ASP
!This service is available on the UAS
!
cs7 route-table system
update route 5200/14 linkset itp1-msc1 priority 3 !SEP via MSC
update route 4904/14 linkset itp1-itp2 priority 5 !MSC via ITP2
update route 5200/14 linkset itp1-itp2 priority 7 !via ITP2
!
line con 0
session-timeout 120
exec-timeout 60 0
password 0 <TBD>
login
!
line aux 0
!
line vty 0 4
session-timeout 120
exec-timeout 60 0
password 0 <TBD>
login
!
no ip domain-lookup
no ip routing
no cdp run
ip subnet-zero
!
ip classless
ip route 0.0.0.0 0.0.0.0 172.18.24.1
ip route 0.0.0.0 0.0.0.0 172.18.25.1
no ip http server
end
!Default G/W Subnet 1

!Default G/W Subnet 2
!
! Note that the following command is an EXEC command,
! and not in configuration mode. Always save the GTT!!
!
Configuration: UAS Hughes Stack
Configuration items are specified at start up. One file defines the
signalling gateways, and is called peers.conf.
The other file is called hssScIf.sh. They must reflect the
parameters specified in the ITP configuration.
For the UAS
SG PCs are 4912; 4913
The port number on the ITP is 15000
The IP addresses .31 & .32 in both the 172.18.24 and 172.18.25 nets
Primary address is the first address
peers.conf (usually same on each UAS)

peers
peer ( 2 SG 2 4912 15000 172.18.24.31 172.18.25.31) # ITP1
peer ( 3 SG 3 4913 15000 172.18.24.32 172.18.25.32) # ITP2
dummy 2:
Configuration: UAS Hughes Stack
The other file is called HssScIf.sh. They must reflect the

parameters specified in the ITP configuration.
For the UAS
SG PCs are 4912; 4913 (the IP addresses taken from peers.conf)
UAS point code is 4916, Routing Context is 121
UAS GT is 4526102044
IP addresses are: 172.18.24.39; 172.18.25.39, port number is 14001
SSN for service is 12 ?
hssScIf.sh
#!/bin/sh
exec ../bin/hssSccpTcapInterface \
-pc 4916 -ssns 12 -rcbase 121 -port 14001 -stps 4912,4913 \
-netaddr 172.18.24.39 -secondary_netaddr 172.18.25.39 \
-defaultgt 4526102044 -sendorigaddr true \
-proto ANY -sleekey 0x1 -inapssns 12
-maxdids 132000 -tx_buffers 2048 -rx_buffers 2048 \
-rto_init 125 -rto_max 250 -rto_min 100 -hb_interval 2 \
-assoc_max_retrans 6 -path_max_retrans 3 -maxSctpModeRetry 10
Configuration: Success!
Check a couple of commands to show the associations
show cs7 asp and show cs7 as
We can trace the SCTP traffic using snoop and Ethereal
Maybe a quick demo?
Troubleshooting Low Speed Links
Troubleshooting Low Speed Links
Remote
SP
STP
STP
Once configuration is complete, a bottom

up approach is recommended for
troubleshooting legacy links
MTP3
MTP2
MTP1/Physical
Troubleshooting LSL: Interface

I/F
Status
Line Protocol
status
Potential Cause
cabling (loopback, BERT)
interface shutdown
down
down
serial: DTE/DCE mismatch

T1/E1: framing/linecode mismatch
T1/E1: controller shutdown
Havent started linkset on bloody DK card
Link not configured as part of a linkset on ITP
up
down
Link/linkset administratively down

Link not activated on the remote end
Serial: clock rate not set
T1/E1: timeslot mismatch
SLT errors: NI, adjacent PC or SLC mismatch
up
toggling
dirty line, check interface counters or T1/E1 controller
Troubleshooting LSL: Commands
Useful Commands:
show cs7 linkset
show cs7 linkset statistic
show controller <interface>
show interface <interface>
Troubleshooting: PC Mismatch Example
1-119-3
SLTM
1-118-82
SLTM
Incorrect Adjacent Point codes, SLC will generate SLT error

messages
MISMATCHED OPC:
Received Invalid SLT Message - OPC = 1.118.82 SLC = 0 on link SP 0
MISMATCHED SLC:
Received Invalid SLT Message - OPC = 1.118.82 SLC = 0 on link SP 1
Troubleshooting: Loopback Error Example
SLTM
Remote
SP
SLTM
DS0 Loopback: putting the local side in loopback will allow the
remote side to align, but when SLT messages are sent, they will
be duplicated & thus an SLT error will occur.
This is one way to verify data path
Troubleshooting: LSL Congestion Monitoring
itp-a#show cs7 mtp2 congestion s0/1

CS7 MTP2 congestion status for interface Serial0/1
Protocol version for interface Serial0/1 is ITU-T Q.703 (1996) (White Book)
Layer3 congestion status
= Abate
CongestionRxInd
CongestionTxInd
= Abate
= Abate (Level0)
CongestionTxOnset
CongestionTxOnset
CongestionTxOnset
CongestionTxOnset
Level1
Level2
Level3
Level4
XmitQ depth (max-used)

XmitQ depth (max-allowed)
=
=
=
=
250
350
450
500
( 50%
( 70%
( 90%
(100%
of
of
of
of
xmitQ
xmitQ
xmitQ
xmitQ
= 2
= 500
maxDepth)
maxDepth)
maxDepth)
maxDepth)
Troubleshooting M2PA Connectivity
M2PA: Troubleshooting Links
Link Status
Potential Cause (either side of connection)

IP address, local or remote port mismatch
Consistently
Down
link/linkset administratively down

physical interface down
Unreachable via IP address (ping and traceroute)
SLT errors: NI, Adjacent or SLC mismatch
Toggling
IP route instability
Round-trip time greater than SCTP configuration
Retransmissions: show ip sctp association statistics
Test Application Layer Using telnet
Can the remote router be accessed?
Paris>
Application
York
Paris
Telnet
Testing with the ping Command
Are protocol packets being routed?
Network Layer
Echo Request
Echo Reply
eSG-ITP> ping 172.16.1.5

Type escape sequence to abort.
Sending 5, 100 byte ICMP Echos to 172.16.1.5, timeout is 2 seconds:
.!!!!
Success rate is 80 percent, round-trip min/avg/max = 1/3/4 ms
eSG-ITP>
Testing with the trace Command
What path are packets taking?
Network Layer
Rome
172.16.33.5
London
172.16.12.3
York
York# trace
Type escape
Tracing the
1
2
3
York#
Paris
172.16.16.2
ROME
to abort.
route to ROME (172.16.33.5)
LONDON (172.16.12.3) 1000 msec 8 msec 4 msec
PARIS (172.16.16.2) 8 msec 8 msec 8 msec
ROME (172.16.33.5) 8 msec 8 msec 4 msec
Using the show ip route Command
Does an entry exist in the routing table?
Network Layer
Paris# show ip route

Codes: I - IGRP derived, R - RIP derived, O - OSPF derived
C - connected, S - static, E - EGP derived, B - BGP derived
i - IS-IS derived, D - EIGRP derived
* - candidate default route, IA - OSPF inter area route
E1 - OSPF external type 1 route, E2 - OSPF external type 2 route
L1 - IS-IS level-1 route, L2 - IS-IS level-2 route
EX - EIGRP external route
Gateway of last resort is not set
I
I
C
C
I
144.253.0.0 [100/1300] via 133.3.32.2 0:00:22 Ethernet1

131.108.0.0 is subnetted (mask is 255.255.255.0), 3 subnets
131.108.33.0 [100/180771] via 131.108.16.2, 0:01:29, Ethernet1
131.108.12.0 is directly connected, Ethernet0
131.108.16.0 is directly connected, Ethernet1
218.100.103.0 [100/1200] via 133.3.32.2, 0:00:22, Ethernet1
M2PA: Useful Commands
Useful Commands
show cs7 linkset
show cs7 m2pa state <linkset-name>
show cs7 m2pa peer <linkset-name> [SLC]
show ip sctp association statistics <instance>
show ip sctp association parameters <instance>
Troubleshooting High Speed Links
Link Configuration: Troubleshooting a High Speed Link 1/4
itp# show controller atm8/1/1

ATM8/1/1: Port adaptor specific information
Hardware is E1 (1920Kbps) port adaptor
Framer is PMC PM7344, SAR is LSI ATMIZER II
Scrambling is Enabled
linecode is HDB3
E1 Framing Mode:
crc.4 adM format
LBO (Cablelength) is long gain43 75db

Facility Alarms:
Loss of Signal
Transmitting yellow
This is a failed ATM circuit at the E1 level
Loss of Signal is a NOT nice output to have
itp# show interface atm8/1/1

ATM8/1/1 is down, line protocol is down
Hardware is cyBus IMA PA, address is 0013.7fdc.9b09 (bia
0013.7fdc.9b09)
MTU 4470 bytes, sub MTU 4470, BW 1920 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
Encapsulation(s): AAL5
511 maximum active VCs, 0 current VCCs
VC idle disconnect time: 300 seconds
Signalling vc = 1, vpi = 0, vci = 5
UNI Version = NNI, Link Side = user
0 carrier transitions
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
ATM/Line protocol is down = same physical problem
itp# show sccop atm8/1/1

SSCOP details for interface ATM8/1/1
Current State = Idle,
Uni version = NNI
Send Sequence Number: Current = 0,
Maximum = 1024
Send Sequence Number Acked = 0

Rcv Sequence Number: Lower Edge = 0, Upper Edge = 0,
Max = 1024
Poll Sequence Number = 0, Poll Ack Sequence Number = 1
Vt(Pd) = 0
Vt(Sq) = 0
MaxPd = 10
Note Current State = Idle, it should be Active
itp# show sccf atm8/1/1

SSCF-NNI details for interface ATM8/1/1
SSCF-NNI Current State = Out of Service
ULP Current State = Alignment
LLP Current State = Idle
<snip>
SSCF-NNI Statistics:
MSUs Sent = 0, MSUs Received = 0, MSUs Ignored = 0
LSSUs Sent = 0, LSSUs Received = 0, LSSUs Ignored = 0
Bytes Sent = 0, Bytes Received = 0
Note SSCF-NNI State = Out of Service, not In Service
Statistics are all zero
References 1/2
Tutorials and External References

http://www.pt.com/tutorials/ss7/
Signaling transport over IP-based networks using IETF standards
Klaus D. Gradischnig and Michael Txen
RFC 3286 An Introduction to the Stream Control Transmission Protocol (SCTP)
Signaling System #7 by Travis Russell
SCCP standard is Q.713
http://www.itu.int/itudoc/itu-t/rec/q/q500-999/q713_23786.html
Cisco ITP documentation

http://www.cisco.com/en/US/products/sw/wirelssw/ps1862/index.html
Cisco IOS documentation

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/ffun_
c/fcfbook.pdf
References 2/2
Implementation Plan
Describes all the implementation details of a customer implementation
Sections on SS7, IP and SCCP routing
Glossary
ETSI
European Telecommunications
Standardisation Institute
IETF
Internet Engineering Task Force
GTT
Global Title Translation
HDLC
High Level Data Link Control
IP
Internet Protocol
ISUP
ISDN User Part
ITU
International Telecommunications Union
IUA
ISDN User Adaptation layer
M2PA
MTP2 Peer-to-peer user Adaptation layer
M2UA
MTP2 User Adaptation layer
M3UA
MTP3 User Adaptation layer
MEGACO
Media Gateway Control (IETF WG)
MG
Media Gateway
MGC
Media Gateway Controller
MGCP
Media Gateway Control Protocol
MTP
Message Transfer Part
PSTN
Public Switched Telephone Network
RTP
Real Time Protocol
SCCP
Signalling Connection Control Part
SCP
Service Control Point
SCTP
Stream Control Transport Protocol
SG
Signalling Gateway
Sigtran
Signalling transport (IETF Working Group)
SIP
Session Initiation Protocol (IETF WG)
SP
SS7 Signalling Point
SS7
Signalling System No. 7
SSN
Sub-System Number
SSP
Service Switching Point
STP
Signalling Transfer Point
TCAP
Transaction Capabilities Application Part
UA
User Adaptation layer
V5UA
V5.2-User Adaptation layer
Thats all Folks!
Whos Hungry?
Planning is Essential!

Cisco Itp in Eservglobal In: Sigtran and Itp Training

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

Cisco Itp in Eservglobal In: Sigtran and Itp Training

Uploaded by

Copyright:

Available Formats

Cisco ITP in eServGlobal IN

Sigtran and ITP Training

PS and Support Internal Training

2003 Cisco Systems 2006 eServGlobal Ltd

Purpose, goals and quick review

ITP anatomy, including hardware overview

Configuration of the ITP

Links, linksets and M2PA

SCCP and SUA detailed information

Configuring ITP Sigtran and GTT Features

M3UA, SUA configuration

MTP3 routing and Global Title Translation

Putting it all together into a configuration

To gain experience with:

ITP integration/connection with an SS7 network

ITP as a Signalling Gateway for an SUA application

Understanding a configuration for the ITP and the HssScIf interface

Design of a IP network to support it

These specific goals:

Covers relevant topics, in detail, for an eSG typical deployment

Hands on time with a machine if possible

Learning through looking time with traces and Wireshark

Bootstrap for more advanced topics if we have time CONCEPTS!

And these specific non-goals:

SS7: What is it? SS7 and OSI Protocol Stack

Remember, we said, an ITP is:

Cisco multifunction router

Operating system (IOS)

Port (Interface) cards

Software makes the system

Cisco ITP Platform Overview

Number of VIP/FlexWAN possible

MTP2 Links per VIP/FlexWAN

MTP2 MSU/sec per VIP/FlexWAN

SUA MSU/sec per VIP/FlexWAN

* = 7300 or 7200 with NPE-G1 processor

ITP Platforms: 2651XM

Two WIC cards

External redundant power

Two x Dual-Port Multiflex

ITP Platforms: 7200

Four slots in 7204

Six slots in 7206

Up to 4/6 FE (TX) available

Dual power and NEBS

PA-MCX-8TE1 Port Cards

I/O Controller with 2 FE

NPE-G1 processor doubles

ITP Platforms: 7200 NPE-400

350-MHz RM7000A RISC

PA-MCX-8TE1-M (E1 Card)

Shared with 75xx platform

Comes as 2, 4, or 8 port version

Only support 24 LSL per 7200

ITP Platforms: 7301

Single Slot for 8 Port E1

One RU form factor

Three FE/GE LAN ports

ITP Platforms: 7507 and 7513

Port and Services

Industry Leading 70+ LAN &

Industry leading features

ITP Platforms: 7500 VIP Cards