Training ITP Training v0.20

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

Diegem
Imro Landveld
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
SIGTRAN and ITP Training | 2 | © 2003 Cisco Systems © 2006 eServGlobal

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 KIWI 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
# of
# of SUA &
Dual Power / ATM Max # of
T1/E1 M2PA MSU
Dual CPU HSL C7 Links
ports per Sec.
Links
265x Dual external 4 900

N/A 4
Low-End Single CPU (CPU!) 2,500
7204/6 VXR Dual Power 3,000

N/A 24 48
Low-Midrange Single CPU 6,000
7301 Dual Power 6,000

8 48 8
Midrange Single CPU 12,000
7507/13 Dual Power 14,000

80-160 320-800 176
High-End Dual CPU 30,000
7600 Range Dual Power 400- 32- 20K-110K

64-160
Mid-Top-end Dual CPU 2200 176 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
SUA MSU/Sec 900 3,000 6,000 14,000 20-110,000
Maximum Routing Table Entries 1,000 10,000 10,000 10,000 10,000
Maximum GTT Entries 150,000 500,000 500,000 500,000 500,000
Maximum M3UA/SUA Routing Keys 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
* = 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 2811

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
NPE-400 Processor
 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

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 Versatile Interface

Processors (RSP) Processors (VIP)
VIP4-80 / VIP6-80
RSP8 / RSP16 Increase Performance
Second RSP for HA (RPR+)
Industry Leading 70+ LAN &

Port and Services
WAN Adaptors To Choose From Adaptors
Industry leading features
Scalable / high performance
Carrier-class high availability
PA-MCX-8TE1-M (LSL)
2 Power Supplies
PA-A3-8E1IMA (HSL)
for Redundancy
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
 T1/E1 SS7 Link Port Adapter for
Cisco’s IP Transfer Point (ITP)
 Supports up to 126 MTP2
signalling links over 8 ports of
T1/E1
 Minimum HW Requirements
 7507 or 7513: RSP8, RSP16, VIP4-
80, 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
Cisco’s 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 VIP offload Architecture
Backup RSP
Primary RSP
GTT SUA
GTT SCCP MTP3 Mgmt RSP
SCCPSCCP MTP3MTP3
MTP3
Routing
Routing
Mgmt M3UA
MTP3 RoutingHigh Speed DMA Memory Bus

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

Forwarding Forwarding Forwarding
MTP3 Fast Cache
MTP3/SCCP MTP3/SCCP MTP3/SCCP
MTP3 Acct / Filter
Screening Screening Screening
MTP2
SSCF-NNI M2PA
SSCOP SCTP SCTP
MTP2 ATM AAL5 IP IP
SS7 LSL SS7 LSL SS7 HSL SS7 HSL Ethernet Ethernet Ethernet Ethernet
PA PA PA PA PA IP PA
PA PA PA
SS7 Data Flow Sigtran Data Flow

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
4-Slot 6-slot 9-slot 13-slot
# of Slots 4 (horizontal) 6 (horizontal) 9 (vertical) 13 (horizontal)

 Support
Height for STM-1 (PA-A3-OC3)
8.75” (5RU) (MM,
12.25” SMI, and
(7RU) 33.5” SML)
(21 RU) and Q.703
30.15” (19RU)
adapter (PA-MCX-4TE1-Q)
Bandwidth 320 Gbps
coming
480 Gbps 720 Gbps 720 Gbps
 Adds
Performance Non Disruptive Upgrade (NDU)
30+ Mpps to Non-Stop
30+ Mpps Operations30+Mpps
30+ Mpps (NSO)
ITP Platforms: 7600 Series Platform
SUP 720 FlexWAN
Increased port density and capacity

Add second SUP for NSO/ISSU
Port and Services

70+ service / port adapters Adaptors
Industry leading features
Scalable / high performance
2 Power Supplies
Carrier-class high availability Same adapters as the 7500 series
for Redundancy

7600 Architecture
Backup SUP
Primary SUP
SCCP Mgmt
MTP3 route mgmt MTP3 Mgmt xUA Route mgmt xUA Mgmt
Shared High Speed switch matrix
FW2 FW2 FW2 FW2

MTP3/SCCP MTP3/SCCP MTP3/SCCP MTP3/SCCP MTP3/SCCP MTP3/SCCP MTP3/SCCP MTP3/SCCP
Forwarding Forwarding Forwarding Forwarding Forwarding Forwarding Forwarding Forwarding
GTT/MLR GTT/MLR GTT/MLR GTT/MLR GTT/MLR GTT/MLR GTT/MLR GTT/MLR
MTP3/SCCP MTP3/SCCP MTP3/SCCP MTP3/SCCP MTP3/SCCP MTP3/SCCP MTP3/SCCP MTP3/SCCP

Screening Screening Screening Screening Screening Screening Screening Screening
SSCF-NNI M2PA M3UA SUA M3UA
MTP2 SSCOP MTP2 SCTP SCTP SCTP SCTP MTP2
ATM AAL5 IP IP IP IP
SS7 LSL PA SS7 HSL PA SS7 LSL PA Ethernet PA Ethernet PA Ethernet PA Ethernet PA SS7 LSL PA
SS7 Data Flow Sigtran Data Flow

ITP 7600 Performance
7604 7606 7609 7613
Slots 4 6 9 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

ITP Standards Compliance
Protocol Specification
ITU-T Q.701-Q.709 White 1996 (inter-works with Blue)

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

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

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

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

M2PA
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
 Which 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) – Cisco’s 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
 Basic Configuration for STP

Linkset  SS7 Variant (ANSI, ITU, China)
1234
 Point Code
 Controllers in various slots
SMSC 4321  MTP2 encapsulation on the serial
interfaces
ITP  Define linkset

 Define links in each linkset
2345
 Define Routes
MSC 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:
SIGTRAN M2PA, M3UA, SUA
 Routing, Management, Screening, 
Accounting  Single Box Solution

 Integrating SS7 and IP Routing
 SCCP:
 Industry Leading QoS:
 Full GTT, Management, Screening,
Guarantee bandwidth or latency for high
Accounting, etc

priority SS7 or IP traffic

 Traditional SS7 Transport:  Address Conversion:
 Low and High-Speed Links  Variable length GT digit conversion (Ex:
E.164 to E.212)
 National Variants:
 Multiple Point Codes/Instances
 ANSI, ITU, China, Japan, etc
 Price / Performance Leader by an order
 High Availability: of magnitude
 6 Nines per 7500 Chassis  Efficient Footprint and Power
 SMS Offload

ITP Functions: SS7oIP to Supplement the STP Plane
SEP Site
Classical SS7 Transport Network SEP Site
MSC
STP STP
STP STP
SMSC
AAA for
WLAN HLR
or
Next Generation SCP
Signalling Transport
ITP ITP
ITP ITP SGSN
Softswitch
Links can be: SGM

• 56/64 Kbits/s
• HSL – Unchannelised T1/E1
• VHSL – Sigtran M2PA
• Sigtran M3UA/SUA

ITP Next-Gen Signalling Transport: SS7 over HSL
SCCP SCCP
GTT GTT
MTP3 / MTP3b MTP3 / MTP3b
SSCF-NNI
MTP2 MTP2 MTP2 SS7 Layer
SCCOP 1 and 2
transport
MTP1 MTP1 MTP1 AAL5
T1 or E1 T1 or E1
SS7 layer 2 changes with no layer 3 Changes

ITP Next-Gen Signalling Transport: SS7 over IP
MSC
SMSC
ITP ITP
SS7 IP SS7
SS7 SS7
SCCP SCCP
Appl GTT GTT Appl
MTP3 MTP3 MTP3 MTP3
M2PA M2PA
MTP2 MTP2 Peer MTP2 MTP2
SCTP SCTP
Transport
MTP1 MTP1 IP IP MTP1 MTP1

Sigtran and SS7 Packets through an SG
MTP3 FISU MTP3 SCTP M2PA

MSU
M2PA SG MSU
M2PA / IP
SP
MTP3
MSU+ FISU MSU M3UA M3UA
M3UA SG MTP3 SCTP
User User / IP SEP
SCCP + FISU MSU

SCCP SUA
SUA SG SUA SCTP
User User / IP SEP
IP
SEP SS7 SG SEP
TDM

ITP Next-Gen Signalling Transport: SS7 over IP (cont)
MTP2 TDM M2PA/SCTP

ITP
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 Packet Header
TOS Protocol Type Source Destination Source/Destn
IP
Address Address Port

(DSCP/ IPPrec)
Core Router
IP Core
SS7 / MTP Sigtran / IP Network
ITP

Classification / Marking – By Input Linkset

QoS Ethernet
Physical Facility Link from MSC Interface
IP Prec=1 SS7 Traffic from MSC
T1 / E1
Link from SCP IP Prec=3 SS7 Traffic from SMSC
T1 / E1 IP Prec=5 SS7 Traffic from SCP

Link from SMSC
Classification / Marking – By Service Indicator Classification

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

ITP Functions: Signalling Gateway
MAP MAP
TCAP GTT N
SCCP I SUA TCAP
SCCP F
MTP3 SUA
MTP3
SCTP IP SCTP
MTP2
MTP2 Network
MTP1 IP
MTP1 IP
SS7 SCTP/IP
SEP ITP ASP
MAP IS-41I T GTT MAP IS-41 I T

S U S U
TCAP U P TCAP U P
SCCP P
SCCP SCCP P
N
MTP3 MTP3 I
F
M3UA M3UA
MTP2 SCTP IP SCTP
MTP2
Network
MTP1 MTP1 IP IP

ITP Functions: SMS MLR
 Route SMS-MO messages based

on a combination of…
SMS-SUBMIT or SMS-COMMAND message
 B-address or destination MSISDN Destination SME (B-address)
MAP
 A-address or originating MSISDN Protocol Identity
User
User Data (will be considered upon request)
 Destination SMSC
 SMS Protocol Identity
Destination SC
 Origin MSC (Called Party Address) Origin SME (A-address) MAP
 Distribute messages to a server
group using weighted round-robin BEGIN Dialogue
Invoke Component
 Servers may be connected via TCAP
Operation Code: MO-forward-SM
TDM, HSL or SIGTRAN links
 Segmented and concatenated SMS
messages are routed to same UDT
SMSC CdPA: Destination SC address
SCCP
CgPA: Origin MSC address

ITP Uses: Save Money
Legacy Vendor Cisco ITP

List Price per LSL $7,500 - $10,000 $500 – 1500
List Price for 720 $5.4M $370k

TDM-Link STP Footprint: 3-6 racks? 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
Separate feature card required 500k GTT capacity part of base

Charge for GTT
and GTT entries sold in blocks product
Charge for Gateway Screening Separate feature card required Part of base product
Price: $80k Price: $25k

IP B/D Links: 2 IP B/D Links: 1000
SS7oIP Ethernet Card Info MSU/s: 2,000 MSU/s: 20,000
Link Utilization: 1.2Mbps Link Utilization: 8 Mbps
Protocol: Proprietary Protocol: Standard IETF Sigtran
Carrier-class IP routing in ITP with

IP routing and wide-area media Requires external IP router.
wide range of WAN interfaces. Industry
capabilities Currently Ethernet < 2Mbps.
leading SS7oIP QoS

Agenda

 MTP3 Routing and Global Title Translation

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 3
Available Linksets 1
Total Links 3
 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 T1 = 5 T2 = 30
T3 = 1 SSCOP Rec = 60 Force Proving = 10
No Credit = 2 NRP = 1 ttc = F
SSCF-NNI Dynamic Parameters:
C1 = 0 NRP count = 0
MPS = 11 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 Local Release Status= 7
Remote Proving Status= 5 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 it’s good to turn accounting on when creating linkset
ITP(config-cs7-ls)# accounting
ITP# show cs7 accounting
4904 4912
SLC 0 serial0/0:0
ITP
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 4912
SLC 0 atm4/0/0
serial5/0/0:1 ITP
MSC SLC 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
00 ATM8/1/0 avail --------- -----
lsn=M1ITP01KOLS1 apc=4416 state=avail avail/links=1/2
00 ATM4/0/1 avail --------- -----
*01 ATM8/0/0 FAILED --------- -----
lsn=M1ITP01HYDS1 apc=320 state=avail avail/links=1/2
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 apc=4904 state=avail avail/links=2/2
Local Point Code = 4912 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>
ITP
Remote
SP
ITP ITP

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.
1111 2222
10.0.0.1 20.0.0.1
ITP ITP
local-peer 7000 local-peer 7000
local-ip 10.0.0.1 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 20.0.0.1
link 0
ITP ITP
cs7 linkset ITP1-ITP2 2222 link 0 cs7 linkset ITP2-ITP1 1111

link 0 sctp 20.0.0.1 7000 7000 link 0 sctp 10.0.0.1 7000 7000

IP Based Linkset: IP Multihoming

link 0
local-ip 10.120.122.6 local-ip 10.120.122.22
local-ip 10.120.123.6 Local-ip 10.120.123.22
3333 IP Cloud 1
4444
10.120.122.6 10.120.122.22
ITP 10.120.123.6
ITP
10.120.123.22
IP Cloud 2

IP Based Linkset: Linkset with SCTP Multihoming
3333 4444
link 0
ITP ITP
cs7 linkset ITP1-ITP2 4444 cs7 linkset ITP2-ITP1 3333
link 0 sctp 10.120.122.22 \ link 0 sctp 10.120.122.6 \
10.120.123.22 7000 7000 10.120.123.6 7000 7000

link 0
local-ip 10.120.122.6 local-ip 10.120.122.22
local-ip 10.120.123.6 Local-ip 10.120.123.22
3333 4444
10.120.122.6 link 0 10.120.122.22
ITP ITP
10.120.123.6 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
Peer, mated SG and SGMP commands

 MTP3 Routing
 Global Titles
 Debug commands
 Troubleshooting

Agenda


Sigtran

Introduction to Sigtran
 What is it?
 A set of
 Standards to run signalling over IP networks
 What must it do?

 Reliable, fast, robust
 How does it do it?

 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-of-
sequence 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
SSP V.SSP
ISUP
KIWI
MTP3 M3UA
Legacy M3UA
and
MTP2 SCTP
SCTP
MTP1 IP Sun IP
Cisco ITP

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
MSC UAS
TCAP Application Data
SCCP
GTT
Hughes
MTP3 SUA
SUA
Legacy
and
MTP2 SCTP
SCTP
MTP1 IP Sun IP
Cisco ITP

ITP Protocol Architecture
Cisco IOS
SCCP
GTT
MTP3 / MTP3b SUA

M3UA
M2PA
SSCF-NNI
MTP2
SCTP
SCCOP
AAL5 MTP1 IP

M3UA / SUA Advantages and Disadvantages
M3UA SUA
 Advantages  Advantages
 ISUP, TUP, SCCP access  Simple for SCCP access only
 SG performs standard GTT  IP service end node does not need
to implement a SS7 layer 3
 Disadvantages adaptation routing protocol
 MTP3 to M3UA mapping can be
more CPU intensive than MTP3  Disadvantages
routing  No ability to participate in ISUP
 NIF is implementation dependent flows
(undocumented) and could make  GTT is adapted within SUA protocol
interoperability challenging which is still being discussed in the
 Designed for IP service end nodes standards group
that do not perform STP MTP3
function

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!

 What’s wrong with SS7 cards in the UAS?
 What’s better with the ITP and Sigtran?

Traditional IN Protocol Architecture
MSC SCP
SCCP SCCP
MTP3 SINAP, OpenSS7 MTP3

DataKinetics, etc
MTP2 MTP2
MTP1 MTP1

eServGlobal Protocol Architecture
MSC UAS
SCCP
SCCP GTT
SUA KIWI
MTP3 / MTP3b
xUA
MTP3 M3UA
and
M2PA
SSCF-NNI SCTP
MTP2
MTP2
SCTP
SCCOP
MTP1 MTP1 AAL5 IP Sun IP
Cisco ITP

Agenda


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 (don’t 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
0 1 2 3 Code
CR Connection request X X 4.2 0000 0001
CC Connection confirm X X 4.3 0000 0010
CREF Connection refused X X 4.4 0000 0011
RLSD Released X X 4.5 0000 0100
RLC Release complete X X 4.6 0000 0101
DT1 Data form 1 X 4.7 0000 0110
DT2 Data form 2 X 4.8 0000 0111
AK Data acknowledgement X 4.9 0000 1000
UDT Unitdata X X 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
0 1 2 3 Code
ED Expedited data X 4.12 0000 1011
EA Expedited data acknowledgement X 4.13 0000 1100
RSR Reset request X 4.14 0000 1101
RSC Reset confirm X 4.15 0000 1110
ERR Protocol data unit error X X 4.16 0000 1111
IT Inactivity test X X 4.17 0001 0000
XUDT Extended unitdata X X 4.18 0001 0001
XUDTS Extended unitdata service X1 X1 4.19 0001 0010
LUDT Long unitdata X X 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 won’t 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 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Protocol Class |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Source Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Destination Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Control |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SS7 Hop Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Segmentation |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010b | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 A Connectionless Data Response (CLDR) is a “service” message

SUA Message Formats-Source/Destination Address
 SUA Source Address

0 1 2 3
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 0
 Route on Global Title 1
 Route on SSN + PC 2
 Route on Hostname 3
 Route on SSN + IP Address 4
 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
 0 Do not include SSN when optional
 1 Include SSN
 Bit 2 is used to indicate inclusion of the PC
 0 Do not include PC, regardless of the routing indicator value
 1 Include PC
 Bit 3 is used to indicate inclusion of the Global Title

 0 Do not include GT when optional (routing indicator /= 1)
 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 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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
1 ISDN/telephony numbering plan (E.163 and E.164)
2 generic numbering plan
3 data numbering plan (Recommendation X.121)
4 telex numbering plan (Recommendation F.69)
5 maritime mobile numbering plan (E.210, E.211)
6 land mobile numbering plan (E.212)
7 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
1 subscriber number
2 reserved for national use
3 national significant number
4 international number
5 – 255 Spare
 Global Title:
Octets contain a number of address signals and possibly filler as shown:
0 1 2 3
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.| filler |
| |if req | sig. | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
All filler bits SHOULD be set to 0.
SUA Message Formats-S/D PC and SSN
 Point Code
0 1 2 3
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
0 1 2 3
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 7 6 5 4 3 2 1
Nat/Intnl Routing Point Subsystem
Indicator Indicator Global Title Indicator Code Number Bit
Indicator Indicator
OCTET Pos
Subsystem Number
Signaling Point Code
Global Title
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 AS’s sharing a single PC).
With this knowledge, we’re off…
Agenda

 Global Title Translation
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
ITP ITP
cs7 linkset ITP1-ITP2 4444 cs7 linkset ITP2-ITP1 3333
link 0 sctp 10.120.122.22 \ link 0 sctp 10.120.122.6 \
10.120.123.22 7000 7000 10.120.123.6 7000 7000

link 0
local-ip 10.120.122.6 local-ip 10.120.122.22
local-ip 10.120.123.6 Local-ip 10.120.123.22
3333 4444
10.120.122.6 link 0 10.120.122.22
ITP ITP
10.120.123.6 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 ASP’s 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 ASP’s within an AS.
Traffic Mode Broadcast
SCCP messages to 2109

Signalling Gateway
ASPA
ACTIVE STP
AS BLUE
ASPB
STP
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 STP
AS BLUE
ASPB
STP
INACTIVE
ASPC
INACTIVE
AS Blue
Traffic Mode = Override
CDMA Override Example
CDMA-Prod-01
Faisalabad STP Prod-ITP1

PC = 5952 PC = 8439 (A c tive)
A S1 -PC1
U
e)
PC 2 ( Inactiv ve)
UAS1-
STP M1ITP01FDBS1 i
ct e) Primary PC = 8431
(A it v Secondary PC = 8432
1 c
S1 P C
( Ina
UM 1- 2 SSN = 14
ITP02-ITP01
S
0 1M U
A -PC
1 ITP
A S1
M UUA
M S2
1I UA -P
TP
02 S2 C1
FD -P (In
B S1 C2 ac
(A tiv
c e)
UAS2-P tiv
STP M1ITP02MUMS1 C1 (Ina CDMA-Prod-02
ctive) e)
U AS 2
Prod-ITP2 -PC2
Mumbai STP ( Activ
PC = 8440 e)
PC = 9024
FW-UAS03
Primary PC = 8432
Secondary PC = 8431
SSN = 14
CDMA Override Example (Failure)
CDMA-Prod-01
Faisalabad STP Prod-ITP1 )

PC = 5952 PC = 8439 1 ( Inactive
- PC
UAS1
e) )
PC 2 (Inactiv ive
UAS1-
STP M1ITP01FDBS1
a ct e) Primary PC = 8431
n iv
(I t Secondary PC = 8432
1 ac
S1 C (In
UM 1 -P 2 SSN = 14
ITP02-ITP01
1M AS C
0 U 1 -P
TP
1 I AS
M UUA
M S2
1I UA
TP -P
02 S2 C1
FD -P (A
B S1 C2 ct
(A iv
c e)
UAS2-P tiv CDMA-Prod-02
STP M1ITP02MUMS1 C1 (Ac
tive) e)
U AS 2
Prod-ITP2 -PC2
Mumbai STP ( Activ
PC = 8440 e)
PC = 9024
FW-UAS03
Primary PC = 8432
Secondary PC = 8431
SSN = 14
Traffic Mode Loadshare (Bindings)

0, 3, Signalling Gateway
ASPA
ACTIVE STP
AS BLUE
1, 4,
ASPB
STP
ACTIVE
2, 5,
ASPC
ACTIVE
AS Blue
Traffic Mode = loadshare bindings
Traffic Mode Loadshare (Round Robin)

every
Signalling Gateway
ASPA
ACTIVE STP
AS BLUE
third
ASPB
ACTIVE STP
packet
ASPC
ACTIVE
AS Blue
Traffic Mode = loadshare roundrobin
Traffic Mode Loadshare (Weighted Round Robin)

50% Signalling Gateway
ASPA
ACTIVE STP
AS BLUE
30%
ASPB
STP
ACTIVE
20%
ASPC
ACTIVE
AS Blue
Traffic Mode = loadshare roundrobin weighted
Loadshare Example
GS-UAS01
Kolkata STP Prod-ITP1

tive)
PC = 4416 PC = 8439 1 (A c
GS - U AS
e )
STP M1ITP01KOLS1 iv
c t Voice/SMS/USSD
(A PC = 8435
1
D S1 AS
U
HY S-
ITP02-ITP01
P01 G
1I
T G
M S- Camel Voice
UA
M S2 SSN = 146
1I
TP (A
02 ct
KO iv
LS e)
1
GS-UA GS-UAS02
STP M1ITP02HYDS1 S2 (Ac
tive)
Hyderabad STP Prod-ITP2

PC = 320 PC = 8440
FW-UAS03
Voice/SMS/USSD
PC = 8435
SUA/M3UA: Loadshare 1/2
 Load-share bindings 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.
 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 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
SCCP SCCP
Class 0 Class1
Traffic Other
Mode Tools
SCCP Distribute SCCP Distribute Always
Un-sequenced off Un-sequenced on Sequenced
Broadcast Broadcast Broadcast

Broadcast N/A
all receive all receive all receive
Loadshare
None SLS Round Robin SLS
Bindings
Loadshare
None Round Robin Round Robin SLS
round robin
Loadshare
Weighted Round Weighted Round Weighted Round
weighted None
Robin Robin Robin and SLS
round robin
Override Override Override

Override N/A
no load sharing no load sharing no load sharing
SUA: Example Scenario

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

Signalling Gateway
ASPA
STP
AS BLUE
ASPB AS GREEN
ACTIVE/STANDBY STP
AS Blue
Routing Key = DPC 2109, SI ISUP
ASPC ASP List = ASPA, ASPB, ASPC
OVERRIDE Traffic Mode = Loadshare
AS Green
ASP List = ASPC, ASPB
Loadshare Example (Voice and SMS)
GS-UAS01

PC = 8439 c tive)
PC = 4416
- U A S1 (A
GS
S 1 (A ctive) e)
STP M1ITP01KOLS1 GS-SM ct
iv
) Voice/SMS/USSD
(A tive PC = 8435
1 c
AS
1 (A
DS U 1
Y
S-
ITP02-ITP01
H S
01 G S M Camel Voice
TP G -
1I S- GS SSN = 146
M UA
M S2
1I
TP (A MAP SMS
02 ct
KO iv SSN = 8
G e)
LS S-
1 SM
GS-UAS S
STP M1ITP02HYDS1 2 (Activ 2 (A GS-UAS02
e) c
tiv
GS-S e)
Prod-ITP2 MS2
Hyderabad STP (Acti
PC = 8440 ve )
PC = 320
FW-UAS03
Voice/SMS/USSD
PC = 8435
Loadshare Failover (Voice + SMS)
GS-UAS01

n)
PC = 4416 PC = 8439
AS 1 (dow
GS-U
)
M S1 (down n)
STP M1ITP01KOLS1 GS- S
dow n)
Voice/SMS/USSD
( w PC = 8435
1 o
DS
1 AS (d
Y S-
U S1
ITP02-ITP01
H M
P01 G
G -S Camel Voice
1I
T S- GS SSN = 146
M UA
M S2
1I
TP (A MAP SMS
02 ct
KO iv SSN = 8
G e)
LS S-
1 SM
GS-UAS S
STP M1ITP02HYDS1 2 (Activ 2 (A GS-UAS02
e) c
tiv
GS-S e)
Prod-ITP2 MS2
Hyderabad STP (Acti
PC = 8440 ve )
PC = 320
FW-UAS03
Voice/SMS/USSD
PC = 8435
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 State: active SCTP instance handle: 1

Local ip address: 10.20.66.23
10.20.66.151
Number of active M3UA peers: 5
Max number of inbound streams allowed: 17
Local receive window: 64000
Max init retransmissions: 8
Max init timeout: 1000 ms
Unordered priority: equal
Extended UPU support: disabled
Offload to VIP: No Slot: -1
SCTP defaults for new associations
Transmit queue depth: 1000 Cumulative sack timeout: 200 ms
Assoc retransmissions: 6 Path retransmissions: 3
Minimum RTO: 500 ms Maximum RTO: 1000 ms
Bundle status: on Bundle timeout: 5 ms
Keep alive status: true Keep alive timeout: 30000 ms
Initial cwnd: 3000 Idle cwnd rate: 50
Retrans cwnd rate: 50 Retrans cwnd mode : 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
SCTP Signalling MTP2
IP Gateway MTP1
SCCP
SUA
IP MTP3 SS7
Network Network
SCTP MTP2
IP MTP1
SCCP messages SCCP messages
ASP SS7 SG SEP

SCTP/IP SS7
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 State: active SCTP instance handle: 2

Local ip address: 10.20.66.23
10.20.66.151
Number of active SUA peers: 5
Max number of inbound streams allowed: 17
Local receive window: 64000
Max init retransmissions: 8
Max init timeout: 1000 ms
Unordered priority: equal
Offload to VIP: No Slot: -1
SCTP defaults for new associations
Transmit queue depth: 1000 Cumulative sack timeout: 200 ms
Assoc retransmissions: 6 Path retransmissions: 3
Minimum RTO: 500 ms Maximum RTO: 1000 ms
Bundle status: on Bundle timeout: 5 ms
Keep alive status: true Keep alive timeout: 30000 ms
Initial cwnd: 3000 Idle cwnd rate: 50
Retrans cwnd rate: 50 Retrans cwnd mode : RFC
FastRetrans cwnd rate: 50
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 CIC min: n/a CIC max: n/a
SSN: n/a GTT: n/a
ASP Name AS Name State Type Rmt Port Remote IP Addr
ASP-ASP1 AS-ubeastest down SUA 14001 172.18.24.39
ASP-SCP2 AS-ubeastest down SUA 14000 172.18.24.40
ASP-SCP1 AS-ubeastest down SUA 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


 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 RESTR 1 itp1-msc1 UNAVAIL
5 itp1-itp2 avail
4905/14 acces 1 itp1-msc2 avail
5 itp1-itp2 UNAVAIL
4700/14 acces 1 itp1-msc1 avail
5 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 Input Output
Point Code Point Code Indicator Packets Bytes Packets Bytes
----------- ----------- ---------- ---------- ---------- ---------- ----------
4904 4912 8 1 25 0 0
Linkset = ‘itp1-msc2’
----------- ----------- ---------- ---------- ---------- ---------- ----------
4905 4912 8 0 0 1 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'
----------- ----------- ---------- ---------- ---------- ---------- ----------
----------- ----------- ---------- ---------- ---------- ---------- ----------
4913 4912 0 24254 291031 0 0
4904 4912 2 72694 872328 0 0
4913 4904 0 0 0 25 271
4904 4913 2 0 0 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
MTP2
Service
Information
Signalling Information Field MTP2
MSU
Serv. Sub- Called Calling

SLS Message Protocol
Indic. serv OPC DPC Party Party Data
(SCCP) Field (5 Bits) Type Class Address Address
3 3 1 1 3 2 2 252
^
^
# of Bytes 1
^
^
1 n
Routing Label
Global Title: Called Party Address
 Remember, this is the SCCP Called Party Address!
8 7 6 5 4 3 2 1
Nat/Intnl Routing Point Subsystem
Indicator Indicator Global Title Indicator Code Number Bit
Indicator Indicator
OCTET Pos
Subsystem Number
Signalling Point Code
Global Title
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
Intermediate Final
GTT DPC = ITP2 GTT DPC = UAS
DPC = ITP1
RI = GT RI = GT RI = PC/SSN
MSC
UAS
ITP ITP
Global Title Indicator
 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
 Numbering Plan:
0 unknown
1 ISDN/telephony numbering plan (E.163 and E.164)
2 generic numbering plan
3 data numbering plan (Recommendation X.121)
4 telex numbering plan (Recommendation F.69)
5 maritime mobile numbering plan (E.210, E.211)
6 land mobile numbering plan (E.212)
7 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
1 subscriber number
2 reserved for national use
3 national significant number
4 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)# gta 919824 pcssn 9240 gt
 Add a GTA Final entry
>cs7-gtt-selector)# 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:
ITP
Incoming Traffic GTT
Final
1 Point Code 1
C o st =
STP MTP3 Linkset
C o st
=2
Point Code 2
 Intermediate:
ITP
Intermediate STP MTP
3 Li
Co st = 1 nks
e t
MTP3 Linkset
PC 1
STP Cost = 2
set
3 Link
MTP
STP
PC 2
Application Groups: Multiplicity Share
 This is how cost based load sharing works:

 Final:
ITP
Final
Point Code 1
50 %
STP MTP3 Linkset
50%
Point Code 2
 Intermediate:
ITP
Intermediate STP MTP
3 Li
50% nks
e t
MTP3 Linkset
PC 1
STP 50% set
3 Link
MTP
STP
PC 2
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
!
cs7 gtt application-group GSM-SMS-1
multiplicity share
pc 8436 1 pcssn
pc 8437 2 pcssn
Load-Sharing Summary
SCCP SCCP
Class 0 Class1
Traffic Other
Mode Tools
SCCP Distribute SCCP Distribute Always
Un-sequenced off Un-sequenced on Sequenced
Broadcast Broadcast Broadcast

Broadcast N/A
all receive all receive all receive
Loadshare
None SLS Round Robin SLS
Bindings
Loadshare
None Round Robin Round Robin SLS
round robin
Loadshare
Weighted Round Weighted Round Weighted Round
weighted None
Robin Robin Robin and SLS
round robin
Override Override Override

Override N/A
no load sharing no load sharing 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
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 BPC BSSN ConPCLst RRC ADJ Ref
4154 12 sol ----------- --- off no 1
5424 12 sol ----------- --- off no 1
5552 12 sol ----------- --- off no 1
 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 gtt map 82 7 sol
!
cs7 gtt map 8433 14 cpclist CPC-LIST-1 sol
cs7 gtt map 8434 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
 We’ll cover more on this a bit later

 We have to be VERY careful with DEBUG
 DON’T EVER, EVER, EVER turn it on in production
Agenda

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
Enables access to Facility Machines
Function
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
External Access/OSS External Access/OSS
Q Q
Billing/Replication F F Billing/Replication
E E
0 1
Cluster MB Cluster
Sigtran A Sigtran B
Alarm Backup Alarm
Example Server Port Allocation
Server 1st QFE Quad LAN Card 2nd QFE Quad LAN Card
Port ce0 ce1 ce2 ce3 ce4 ce5 ce6 ce7
Billing/ Billing/
USMS Extern
Rep.
Cluster Alarm Extern
Rep.
Cluster Alarm
Billing/ Sigtran Billing/ Sigtran

UAS Extern
Rep. A
Alarm Extern
Rep. B
Alarm
Billing/ Billing/
UBE Extern
Rep.
Alarm Extern
Rep.
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
97.253.108.0/26 97.253.108.0/26
Switch Switch
97.253.108.12
97.253.108.10 Sun s
SD
97.253.108.11
UAS1
97.253.108.15
97.253.108.13 Sun s
SD
97.253.108.14
UAS2
97.253.108.18
97.253.108.16 Sun s
SD
97.253.108.17
LAN 2
LAN 1
UAS3
97.253.108.21
97.253.108.19 Sun s
SD
97.253.108.20
UAS4
Not Connected Not Connected

ITP 1

ITP 2
97.253.108.24
97.253.108.22 Sun s
SD
97.253.108.23
U-SMS
Example Signalling Network Design
97.253.108.128/26 97.253.108.192/26
Switch Switch
97.253.108.140 Sun s
SD
97.253.108.204
UAS1
97.253.108.150 Sun s
SD
97.253.108.214
UAS2
97.253.108.160 Sun s
SD
97.253.108.224
LAN 2
LAN 1
UAS3
97.253.108.170 Sun s
SD
97.253.108.234
UAS4
97.253.108.134 97.253.108.198
ITP 1
97.253.108.135 97.253.108.199
ITP 2

SD
Sun s
U-SMS
External Network Design – Limited Redundancy
97.253.109.0/27
Switch
97.253.109.10
Not Connected
SD
Sun s
NTP Server UAS1

97.253.25.106
97.253.109.11
Not Connected
SD
Sun s
syslog Server UAS2

97.253.1.49
97.253.109.12
Not Connected
SD
Sun s
LAN 1
UAS3
SNMP Server
97.254.0.56 97.253.109.13
Not Connected
SD
Sun s
UAS4
SNMP Server
97.253.109.20
97.253.0.179 Not Connected
ITP 1
97.253.109.21
Not Connected
ITP 2
97.253.109.17
97.253.109.19
SD
Sun s
97.253.109.18 U-SMS
Agenda

Some Example Traffic Flows
Initial Trigger
MSC
DPC = 8439 or 8440
GTA = Common Single GT PC = 4177
RI = GT SSN = 146
MSC = 91988300 0555
STP The MSC will trigger the subscriber based

PC = 320 on one of the four SCP ISDN’s that it has
or 4415 been provisioned for.
There will be no SSN in the SCCP header.
ATM Link The MTP3 DPC will be loadshared to the
two ITP point codes, and failover to the
M1ITP01KOLS1 or other if the primary fails.
M1ITP02KOLS1
DPC = 8439 or 8440

GTA = one of 4 SCP ISDN 2
RI = GT
2 gta 9198xx002400 app-grp GSM-MOX-ALL
cs7 gtt application-group GSM-MOX-ALL

multiplicity share
pc 8436 ssn 146 2 pcssn 3 Assume the round robin selects UAS1
cs7 gtt map 8435 146 solitary 4
cs7 as GS-UAS1-AS sua

routing-key 100 8435 si sccp ssn 146 5
asp GS-UAS1-ASP UAS
PC = 8435
cs7 asp GS-UAS1-ASP 14001 15010 sua SUA Association SSN = 146
remote-ip 97.32.12.76
6 remote-ip 92.37.12.140
GTA = 919827002400
7 exec ../bin/hssSccpTcapInterface \
-pc 8435 -ssns 146 -rcbase 100 -rcstep 10 \
8 -port 14001 -stps 8439,8440 \
-netaddr 97.32.12.76 -secondary_netaddr 92.37.12.140
Initial Response
DPC = 4417 MSC
SSN = 146
GTA = 919883xxxxxx PC = 4177
RI = GT SSN = 146
MSC = 919883xxxxxx
STP
PC = 320
or 4415
ATM Link
M1ITP01KOLS1
DPC = 4417
SSN = 146
GTA = 919883xxxxxx
RI = GT
Assume the traffic is returned via ITP01

5 cs7 linkset M1ITP01KOLS1 4416
4
update route 4177 16383 linkset M1ITP01KOLS1 priority 4
cs7 gtt selector UAS-MSC tt 0 gti 4 np 1 nai 4

gta 919883 pcssn 4177 gt UAS
PC = 8435
3 SUA Association SSN = 146
GTA = 919827002400
2 #!/bin/sh
exec ../bin/hssSccpTcapInterface \
1 -pc 8435 -ssns 146 -rcbase 100 -rcstep 10 \
-port 14001 -stps 8439,8440 \
-netaddr 97.32.12.76 -secondary_netaddr 92.37.12.140
MSC
DPC = 8439 or 8440
GTA = one of 4 SCP ISDN PC = 4177
SSN = 146
Subsequent
RI = GT
MSC = 919883xxxxxx
1
STP
PC = 320
or 4415
ATM Link
M1ITP01KOLS1 or
M1ITP02KOLS1
DPC = 8439 or 8440

GTA = one of 4 SCP ISDN 2
RI = GT UAS1
PC = 8435
SSN = 146
7
3 gta 919827002400 app-grp GSM-MOX-GT1 GTA = 919827002400
#!/bin/sh
cs7 gtt application-group GSM-MOX-GT1 exec ../bin/hssSccpTcapInterface \
multiplicity cost -pc 8435 -ssns 146 -rcbase 100 -rcstep 10 \
-port 14001 -stps 8439,8440 \
pc 8435 ssn 146 1 pcssn 4 -netaddr 97.32.12.76 -secondary_netaddr 92.37.12.140

UAS2
SUA Association
5 cs7 as UAS1-AS1 sua
routing-key 100 8435 si sccp ssn 146 UAS3
asp UAS1-ASP1 6
cs7 asp UAS1-ASP1 14001 15010 sua
remote-ip 97.32.12.76
remote-ip 92.37.12.140 UAS4
Practical Implementation Example
Building Working Configuration
 Boy, I’m 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 KIWI configuration for the following scenario:
ITP1
PC = 4912 MS
C
MSC
SD
Sun s
PC = 4904
UAS
PC = 4916
SD
Sun s
UAS
PC = 4917
MS
C
MSC
ITP2
PC = 4913 PC = 4905
Configuration: General Parameters
Global Parameter Value Notes

IOS Version 12.2 ITP Release 3
Boot Code 25SW1 Release 12.2(25)SW1 for 2651XM
IN-MODEL-ITP1
Host Names IP short name
IN-MODEL-ITP2
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
Subnet - 172.18.24.0/24 Subnet - 172.18.25.0/24
172.18.24.xxx
USMS - (herring)
172.18.24.39 172.18.25.39
UAS - (ube)
172.18.24.31 172.18.25.31
M2PA ITP1 M2PA
172.18.24.32 172.18.25.32
ITP2
W.A.N
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
service internal This is the name of the box.
!
hostname ITP1 The image to load
!
boot system flash c2600-itp-mz.122-25.SW1.bin
logging buffered 500000 debugging This password becomes encrypted when it is
logging history size 500 configured onto the ITP and then it will be
enable secret 0 <TBD> shown as “secret 5” followed by a 30 digit base
64 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.
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
!
cs7 variant ITU
cs7 point-code delimiter dash
cs7 point-code format 14 descriptor decimal
cs7 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
This GT will need final
ITP2 4913 N/A translation to PC 4916
SCP/UAS 4916 4526102044

MSC 4904 N/A
!
cs7 point-code 4912 !ITP1 is PC 4912=2.102.0
!
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

See Section
GT Translation Type 0-255 0=Unknown §3.10.2.3 Global Title
in the IETF Sigtran
Global Title Indicator 0, 1, 2, 3, 4 4=ITU SUA RFC for further
information on GTT
Nature of Address Indicator 0, 1, 2, 3, 4 4 fields.
Numbering Plan 0, 1, 2 1
Name for Selector Any Value GLOBAL
Name for GTT Table Any Value gttdata.txt
!
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 doesn’t match a particular prefix.
 This is INTERMEDIATE Global Title Translation
!
! Create the application group
!
cs7 gtt application-group MSC
multiplicity share RI=GT i.e. intermediate
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/0
shutdown
 Controller E1 0/3 !
controller E1 0/1
 Controller E1 0/4 shutdown
!
controller E1 0/2
shutdown
!
controller E1 0/3
shutdown
Configuration: Defining the links
 We have one INAP connection to controller E1 0/0

the controller E1 0/0 clock source line
framing CRC4
 The “channel-group” command channel-group 0 timeslots 1
creates a serial interface known channel-group 1 timeslots 2
no shutdown
as “serial 0/0:0” !
controller E1 0/1
This channel group
shutdown
number creates this
! interface device.
controller E1 0/2
shutdown
Physical Parameter INAP Connection !
controller E1 0/3
Interface Type Channelised E1
shutdown
ITP Terminating host ITP1 !
interface Serial0/0:0
Port on ITP Port 0 on Card 0 no ip address
Clock Source Line encapsulation mtp2
no shutdown
Framing crc4 !
Linecode hdb3 interface Serial0/0:1
no ip address
Timeslot 1, 2 encapsulation mtp2
no shutdown
!
Configuration: MTP3 Parameters
Timer Description
slt-t01 Link Test T1 (Link test acknowledgement timer)
Don’t play with these unless you have to!

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)
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 (ITP1) IP address on one subnet
local-ip 172.18.25.31 !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
Here is the PC of the MSC

cs7 linkset itp1-msc1 4904
accounting
link 0 Serial0/0:0
link 1 Serial0/0:1
!
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
Q? Why do we set up this ITP-ITP linkset?
 25.32 on the other.
 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
cs7 linkset ITP1-ITP2 4913 Here is the PC of ITP2

accounting
link 0 sctp 172.18.24.32 172.18.25.32 7000 7000
!
This number corresponds

Q? What is the big benefit here? 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
!
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
!
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
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 (VSSP1) IP address on one subnet
remote-ip 172.18.25.xxx !Remote (VSSP1) IP address on the other subnet
!
cs7 asp ITP-VSSP2-ASP 2905 2905 m3ua
remote-ip 172.18.24.yyy !Remote (VSSP2) IP address on one subnet
remote-ip 172.18.25.yyy !Remote (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 PC’s are 100 and 200)
 Service Indicator (ISUP in this case)
 We now allocate the two ASP’s to the two AS

!
cs7 as ITP-VSSP1-AS m3ua
routing-key 100 100 si isup !100 is the routing key, 100 is the PC of VSSP1
asp ITP-VSSP1-ASP !This ASP is where the service is available
!
cs7 as ITP-VSSP2-AS m3ua
routing-key 200 200 si isup !200 is the routing key, 200 is the PC of VSSP2
asp ITP-VSSP2-ASP !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
!
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 si sccp
asp ITP-UAS-ASP !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 !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
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
 (no) logging console
 Aux
 Forget about it
!
line con 0
session-timeout 120 This password becomes encrypted when it
exec-timeout 60 0 is configured onto the ITP and then it will
password 0 <TBD> be shown as “secret 7” followed by a 10
login digit hex number. This is a simple
Vigenere cipher, and not very secure.
!
line aux 0
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 This password becomes encrypted when it
session-timeout 120 is configured onto the ITP and then it will
exec-timeout 60 0 be shown as “secret 7” followed by a 10
password 0 <TBD> digit hex number. This is a simple
Vigenere cipher, and not very secure.
login
Configuration: Other IP Stuff
 The Rest?
 Don’t 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 (don’t stick to Class A, B, C)
 Don’t run the HTTP configuration server
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 !Virtual address for default G/W Subnet 1
ip route 0.0.0.0 0.0.0.0 172.18.25.1 !Virtual address for default G/W Subnet 2
no ip http server
Configuration: One More Thing
 Don’t 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
channel-group 0 timeslots 1
channel-group 1 timeslots 2
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

!
cs7 linkset ITP1-ITP2 4913
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
!
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.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 !Default G/W Subnet 1
ip route 0.0.0.0 0.0.0.0 172.18.25.1 !Default G/W Subnet 2
no ip http server
end
!
! Note that the following command is an EXEC command,
! and not in configuration mode. Always save the GTT!!
!
Configuration: UAS KIWI Stack
 Configuration items are specified at start up.
 For the UAS the following information is needed:
 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
 This table describes the main components in the SUA version of the SIGTRAN TCAP
Interface.
Configuration: UAS KIWI Stack
 This table describes the main components in the M3UA version of the SIGTRAN TCAP
Interface.
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 Line Protocol

Potential Cause
Status status
cabling (loopback, BERT)
interface shutdown
down down serial: DTE/DCE mismatch
T1/E1: framing/linecode mismatch
T1/E1: controller shutdown
Haven’t started linkset on bloody DK card
Link not configured as part of a linkset on ITP
Link/linkset administratively down
up 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 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
Remote
SP
SLTM
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 = Abate
CongestionTxInd = Abate (Level0)
CongestionTxOnset Level1 = 250 ( 50% of xmitQ maxDepth)

CongestionTxOnset Level4 = 500 (100% of xmitQ maxDepth)
XmitQ depth (max-used) = 2

XmitQ depth (max-allowed) = 500
Troubleshooting M2PA Connectivity
M2PA: Troubleshooting Links
Link Status Potential Cause (either side of connection)

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

Down physical interface down
Unreachable via IP address (ping and traceroute)
SLT errors: NI, Adjacent or SLC mismatch

IP route instability
Toggling
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
London 172.16.33.5
172.16.12.3
Paris
York 172.16.16.2
York# trace ROME

Type escape to abort.
Tracing the route to ROME (172.16.33.5)
1 LONDON (172.16.12.3) 1000 msec 8 msec 4 msec
2 PARIS (172.16.16.2) 8 msec 8 msec 8 msec
3 ROME (172.16.33.5) 8 msec 8 msec 4 msec
York#
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 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
I 131.108.33.0 [100/180771] via 131.108.16.2, 0:01:29, Ethernet1
C 131.108.12.0 is directly connected, Ethernet0
C 131.108.16.0 is directly connected, Ethernet1
I 218.100.103.0 [100/1200] via 133.3.32.2, 0:00:22, Ethernet1
M2PA: Useful Commands
 Useful Commands
 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 Tüxen
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
European Telecommunications
ETSI IETF Internet Engineering Task Force
Standardisation Institute
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
That’s all Folks!
Who’s Hungry?
Planning is Essential!

Training ITP Training v0.20

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Training ITP Training v0.20

Încărcat de

Drepturi de autor:

Formate disponibile

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

SIGTRAN and ITP Training | 2 | © 2003 Cisco Systems © 2006 eServGlobal

 To gain experience with:

SIGTRAN and ITP Training | 3 | © 2003 Cisco Systems © 2006 eServGlobal

SIGTRAN and ITP Training | 4 | © 2003 Cisco Systems © 2006 eServGlobal

SIGTRAN and ITP Training | 5 | © 2003 Cisco Systems © 2006 eServGlobal

265x Dual external 4 900

7204/6 VXR Dual Power 3,000

7301 Dual Power 6,000

7507/13 Dual Power 14,000

7600 Range Dual Power 400- 32- 20K-110K

SIGTRAN and ITP Training | 6 | © 2003 Cisco Systems © 2006 eServGlobal

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

SUA MSU/Sec 900 3,000 6,000 14,000 20-110,000

Maximum Routing Table Entries 1,000 10,000 10,000 10,000 10,000

Maximum GTT Entries 150,000 500,000 500,000 500,000 500,000

Maximum M3UA/SUA Routing Keys 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

* = 7300 or 7200 with NPE-G1 processor

2651 with 2811

SIGTRAN and ITP Training | 8 | © 2003 Cisco Systems © 2006 eServGlobal

7204 with various cards

 NPE-G1 processor doubles

SIGTRAN and ITP Training | 9 | © 2003 Cisco Systems © 2006 eServGlobal

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

SIGTRAN and ITP Training | 10 | © 2003 Cisco Systems © 2006 eServGlobal

SIGTRAN and ITP Training | 11 | © 2003 Cisco Systems © 2006 eServGlobal

Route Switch Versatile Interface

Industry Leading 70+ LAN &

SIGTRAN and ITP Training | 13 | © 2003 Cisco Systems © 2006 eServGlobal

SIGTRAN and ITP Training | 14 | © 2003 Cisco Systems © 2006 eServGlobal

SIGTRAN and ITP Training | 15 | © 2003 Cisco Systems © 2006 eServGlobal

MTP3 RoutingHigh Speed DMA Memory Bus

Shared High Speed DMA Memory

VIP MTP3/SCCP VIP MTP3/SCCP VIP MTP3/SCCP VIP

SS7 Data Flow Sigtran Data Flow

 High-end Cisco Platform

SIGTRAN and ITP Training | 17 | © 2003 Cisco Systems © 2006 eServGlobal

 Main processor = SUP720-3BXL

4-Slot 6-slot 9-slot 13-slot

# of Slots 4 (horizontal) 6 (horizontal) 9 (vertical) 13 (horizontal)

SUP 720 FlexWAN

Increased port density and capacity

Port and Services

SIGTRAN and ITP Training | 19 | © 2003 Cisco Systems © 2006 eServGlobal

Shared High Speed switch matrix

FW2 FW2 FW2 FW2

GTT/MLR GTT/MLR GTT/MLR GTT/MLR GTT/MLR GTT/MLR GTT/MLR GTT/MLR

MTP3/SCCP MTP3/SCCP MTP3/SCCP MTP3/SCCP MTP3/SCCP MTP3/SCCP MTP3/SCCP MTP3/SCCP

SSCF-NNI M2PA M3UA SUA M3UA

MTP2 SSCOP MTP2 SCTP SCTP SCTP SCTP MTP2

SS7 Data Flow Sigtran Data Flow

7604 7606 7609 7613

Port Adapters/FlexWAN 4/2 8/4 14/7 22/11

Low-speed TDM links 400 800 1400 2200