The information in this document was created from the devices in a
specific lab environment. All of the devices used in this document started with
a cleared (default) configuration. If your network is live, make sure that you
understand the potential impact of any command.

A Cisco PGW 2200 can support up to six True OPCs. However, there are
some configuration steps you must follow in order to deploy this configuration.
Each OPC is bound to a single SS7 Input Output Channel Controller (IOCC)
instance within the PGW 2200 where each IOCC is bound to a unique UDP port.
Each unique port is identified when you configure the SESSIONSET that is used
by the C7IPLNK in the PGW 2200 configuration. One problem that arises when you
configure multiple OPCs is that linksets cannot be shared between IOCCs. As a
result, you need to configure multiple entries for your adjacent point codes
(APCs) with unique MML names. This allows you to have a unique entry to
associate with the LNKSET for each IOCC.

The Cisco SLT functions as an SS7 front-end processor for the Cisco PGW
2200 node. The Cisco SLT is responsible for terminating the Message Transfer
Part Level 1 (MTP1) and MTP2 layers of the SS7 protocol stack. The Cisco SLT
transports the upper layers of the SS7 signaling (MTP3 and later) to and from
the PGW 2200 over an IP network that uses Reliable User Datagram Protocol
(RUDP). Prior to Cisco IOS Software Release 12.2(15)T, the SLT was only capable
of having a single Active RUDP session between itself and the PGW 2200. The
result was that you had to have a different SLT for each IOCC or OPC
configured. This limitation was removed with the introduction of Cisco IOS
Software Release 12.2(15)T which can now have active RUDP sessions with up to
four IOCC's (see Note).

Note: The Cisco 2611XM SLT can only create two RUDP sessions to a Cisco PGW
2200 as opposed to four on the 2651XM, AS5350, or AS5400.

!--- Two unique point codes are defined for the PGW 2200.
prov-add:OPC:NAME="opc-1",DESC="Originating Point Code 1",
NETADDR="10.20.1",NETIND=2,TYPE="TRUEOPC"
prov-add:OPC:NAME="opc-2",
DESC="Originating Point Code 2",NETADDR="10.20.2",NETIND=2,TYPE="TRUEOPC"
!--- Destination point codes are defined for the SSPs
!--- that you connect to. For point code 20.20.1 there are duplicate entries.
!--- Each one is associated to a different IOCC that represents each OPC.
prov-add:DPC:NAME="dpc-simplex",DESC="Destination Point Code for BTS Simplex(650)",
NETADDR="20.20.1",NETIND=2
prov-add:DPC:NAME="dpc-simplex-opc2",DESC="Destination Point Code for BTS
Simplex(650)from opc2",NETADDR="20.20.1",NETIND=2
!--- The SS7 variant is defined that is used between you and
!--- the destination SSP.
prov-add:SS7PATH:NAME="ss7p-simplex",DESC="SS7 Signaling Service to
BTS Simplex via opc-1",MDO="ANSISS7_STANDARD",CUSTGRPID="0000",SIDE="network",
DPC="dpc-simplex",OPC="opc-1"
prov-add:SS7PATH:NAME="ss7p-simplex-opc2",
DESC="SS7 Signaling Service to BTS Simplex via opc-2",MDO="ANSISS7_STANDARD",
CUSTGRPID="0000",SIDE="network",DPC="dpc-simplex-opc2",OPC="opc-2"
!--- The SLTs are defined and gateways that are part of
!--- the PGW 2200 solution.
prov-add:EXTNODE:NAME="slt-1",DESC="SLT-1-2651XM",TYPE="SLT"
prov-add:EXTNODE:NAME="slt-2",DESC="SLT-2-2651XM",TYPE="SLT"prov-add:EXTNODE:
NAME="as5300-2",DESC="AS5300-2 Gateway",TYPE="AS5300"
!--- The RUDP connections are defined between
!--- the PGW 2200 and the two SLTs.
!--- Note that you need to define duplicate entries for the sessionset.
!--- Each one is associated to a different IOCC that represents each OPC.
prov-add:SESSIONSET:NAME="sset-slt1",EXTNODE="slt-1",IPADDR1="IP_Addr1",
PEERADDR1="172.16.20.14",PORT=7000,PEERPORT=7000,NEXTHOP1="0.0.0.0",
NETMASK1="255.255.255.255",TYPE="BSMV0"
prov-add:SESSIONSET:NAME="sset-slt1-opc2",EXTNODE="slt-1",IPADDR1=
"IP_Addr1",PEERADDR1="172.16.20.14",PORT=7002,PEERPORT=7002,NEXTHOP1=
"0.0.0.0",NETMASK1="255.255.255.255",TYPE="BSMV0"
prov-add:SESSIONSET:NAME="sset-slt2",EXTNODE="slt-2",IPADDR1="IP_Addr1",
PEERADDR1="172.16.20.15",PORT=7000,PEERPORT=7000,NEXTHOP1="0.0.0.0",
NETMASK1="255.255.255.255",TYPE="BSMV0"
prov-add:SESSIONSET:NAME="sset-slt2-opc2",EXTNODE="slt-2",IPADDR1=
"IP_Addr1",PEERADDR1="172.16.20.15",PORT=7002,PEERPORT=7002,NEXTHOP1=
"0.0.0.0",NETMASK1="255.255.255.255",TYPE="BSMV0"
!--- The point codes of the STPs are defined that you connect to.
!--- Note that you need to define duplicate entries for the APCs.
!--- Each one is associated to a different IOCC that represents each OPC.
prov-add:APC:NAME="itp-1",DESC="Adjacent Point Code for ITP1(100-1-1)
",NETADDR="100.1.1",NETIND=2
prov-add:APC:NAME="itp-2",DESC="Adjacent Point Code for ITP2 (100-1-2)
",NETADDR="100.1.2",NETIND=2
prov-add:APC:NAME="itp-1-opc2",DESC="Adjacent Point Code for ITP1 (100-1-1)
for opc-2",NETADDR="100.1.1",NETIND=2
prov-add:APC:NAME="itp-2-opc2",DESC="Adjacent Point Code for ITP2 (100-1-2)
for opc-2",NETADDR="100.1.2",NETIND=2
!--- Define the SS7 links between the PGW 2200 and the STP.
!--- You need to define duplicate entries for the LNKSET.
!--- Each duplicate entry is associated to a different IOCC that
!--- represents each OPC.
prov-add:LNKSET:NAME="lnkset-itp1",DESC="From 2651XM-1 Lnkset to ITP1
",APC="itp-1",PROTO="SS7-ANSI",TYPE="IP"
prov-add:LNKSET:NAME="lnkset-itp2
",DESC="From 2651XM-1 Lnkset to ITP2",APC="itp-2",PROTO="SS7-ANSI",TYPE=
"IP"
prov-add:LNKSET:NAME="lnkset-itp1-opc2",DESC="From 2651XM-1 Lnkset to
ITP1 for opc-2",APC="itp-1-opc2",PROTO="SS7-ANSI",TYPE="IP"
prov-add:
LNKSET:NAME="lnkset-itp2-opc2",DESC="From 2651XM-1 Lnkset to ITP2 for
opc-2",APC="itp-2-opc2",PROTO="SS7-ANSI",TYPE="IP"
!--- Define routes to the destination point code via each SLT.
!--- Also, define the routes to the STPs. You need to
!--- define duplicate entries for the SS7ROUTE.
!--- Each duplicate entry is associated to a different
!--- IOCC that represents each OPC.
prov-add:SS7ROUTE:NAME="ss7r-simplex-1",DESC="SS7 Route to BTS Simplex
via ITP1",OPC="opc-1",DPC="dpc-simplex",LNKSET="lnkset-itp1", PRI=1
prov-add:SS7ROUTE:NAME="ss7r-simplex-2",DESC="SS7 Route to BTS Simplex
via ITP2",OPC="opc-1",DPC="dpc-simplex",LNKSET="lnkset-itp2", PRI=1
prov-add:SS7ROUTE:NAME="ss7r-simplex-1-opc2",DESC="SS7 Route to BTS
Simplex via ITP1 using opc-2",OPC="opc-2",DPC="dpc-simplex-opc2",
LNKSET="lnkset-itp1-opc2",PRI=1
prov-add:SS7ROUTE:NAME="ss7r-simplex-2-opc2",DESC="SS7 Route to
BTS Simplex via ITP2 using opc-2",OPC="opc-2",DPC="dpc-simplex-opc2
",LNKSET="lnkset-itp2-opc2",PRI=1
prov-add:SS7ROUTE:NAME="ss7r-itp1-opc2",DESC="SS7 Route to ITP1
via opc-2",OPC="opc-2",DPC="itp-1-opc2",LNKSET="lnkset-itp1-opc2",PR I=1
prov-add:SS7ROUTE:NAME="ss7r-itp2-opc2",DESC="SS7 Route to ITP2 via
opc-2",OPC="opc-2",DPC="itp-2-opc2",LNKSET="lnkset-itp2-opc2",PR I=1
prov-add:SS7ROUTE:NAME="ss7r-itp1",DESC="SS7 Route to ITP1 via opc-1
",OPC="opc-1",DPC="itp-1",LNKSET="lnkset-itp1",PRI=1
prov-add:SS7ROUTE:NAME="ss7r-itp2",DESC="SS7 Route to ITP2 via opc-1
",OPC="opc-1",DPC="itp-2",LNKSET="lnkset-itp2",PRI=1
!--- Define the IP link between the PGW 2200 and the SLT.
!--- You need to create duplicate entries for the C7IPLNK.
!--- Each duplicate entry is associated to a different
!--- IOCC that represents each OPC.
prov-add:C7IPLNK:NAME="c7ip-itp1-0",DESC="C7Iplink to ITP1 SLC 0 via
SLT1",LNKSET="lnkset-itp1",SLC=0,PRI=1,TIMESLOT=0,SESSIONSET="s set-slt1"
prov-add:C7IPLNK:NAME="c7ip-itp2-1",DESC="C7Iplink to ITP2 SLC 1 via
SLT2",LNKSET="lnkset-itp2",SLC=1,PRI=1,TIMESLOT=1,SESSIONSET=" sset-slt2"
prov-add:C7IPLNK:NAME="c7ip-itp1-1-opc2",DESC="C7Iplink to ITP1 SLC 1
via SLT-2 for opc-2",LNKSET="lnkset-itp1-opc2",SLC=1,PRI=1,TIMESLOT=0,
SESSIONSET="sset-slt2-opc2"
prov-add:C7IPLNK:NAME="c7ip-itp2-0-opc2",DESC="C7Iplink to ITP2 SLC 0
via SLT-1 for opc-2",LNKSET="lnkset-itp2-opc2",SLC=0,PRI=1,TIMESLOT=1,
SESSIONSET="sset-slt1-opc2"
!--- Define the SS7 Subsystems which allow you to route
!--- traffic via the C links. Note that you need to create duplicate
!--- entries for the SS7SUBSYS. Each duplicate entry is
!--- associated to a different IOCC that representis each OPC.
prov-add:SS7SUBSYS:NAME="subsys-itp1-itp2",DESC="notSet",SVC="itp-1",
PRI=2,MATEDAPC="itp-2",SSN=0,PROTO="SS7-ANSI",STPSCPIND=0,TRANSPROTO="SCCP"
prov-add:SS7SUBSYS:NAME="subsys-itp2-itp1",DESC="notSet",SVC="itp-2",
PRI=2,MATEDAPC="itp-1",SSN=0,PROTO="SS7-ANSI",STPSCPIND=0,TRANSPROTO="SCCP"
prov-add:SS7SUBSYS:NAME="subsys-itp1-itp2-2",DESC="notSet",SVC="itp-1-opc2",
PRI=2,MATEDAPC="itp-2-opc2",SSN=0,PROTO="SS7-ANSI",STPSCPIND=0,TRANSPROTO="SCCP"
prov-add:SS7SUBSYS:NAME="subsys-itp2-itp1-2",DESC="notSet",SVC="itp-2-opc2",
PRI=2,MATEDAPC="itp-1-opc2",SSN=0,PROTO="SS7-ANSI",STPSCPIND=0,TRANSPROTO="SCCP"

From the PGW 2200, verify that all SS7 links are up and in service.
This output represents some commands that you can run on the PGW 2200 that
provide the status of various components of the configuration.