Cisco PGW 2200 Signaling Mode Design Guide
This guide describes how to provision a signaling-mode PGW 2200 and other related devices (shown in
Figure 1). The document describes a sample configuration (for illustration purposes only). Your
configuration will vary and depend on your own network.
This guide presents two ways of provisioning with MML:
•
Using MML commands individually to provision your system. (This can be time consuming if you
have a large configuration.)
•
Creating a simple MML batch file in ASCII format and processing it with MML.
To skip directly to the MML batch file used to provision the sample configuration, see the “Creating and
Processing an MML Batch File for Provisioning” section on page 51.
Figure 1 shows an overview of Cisco PGW 2200 signaling mode solution.
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
© 2008 Cisco Systems, Inc. All rights reserved.
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Outline
Figure 1
PGW 2200 Signaling Mode Solution
LAN
switches
Cisco ITP-L
STP
IMTs
PSTN
switch
IMTs
IMTs
Cisco ITP-L
PGW 2200
Cisco AS5X00
Cisco AS5X00
QoS packet
network
Cisco AS5X00
Telephone
exchange
Gateway router
280713
STP
IMT = InterMachine Trunk
Caution
Do not use the sample values in this document to provision your system. You must research your network
and obtain your own values for the network addresses, point codes, and other parameters used in your
solution. If you use the sample values presented here, your configuration will not work.
Provisioning Outline
Perform the following steps to provision the sample Cisco SS7 Interconnect for Access Servers Solution.
Step
Section and Page
Provision SS7 signaling routes
Step 1
Step 2
Add the OPC1 in your network.
Add the DPC to identify the destination switch.
3
Adding the DPC, page 14
4
Step 3
Add the APCs to identify the STPs with which the Adding the APCs, page 16
signaling controller communicates signaling
information.
Step 4
Add linksets to connect the Cisco ITP-Ls5 to the
STPs.
Cisco PGW 2200 Signaling Mode Design Guide
2
Adding the OPC, page 12
2
Adding Linksets, page 18
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Worksheet
Step
Section and Page
Step 5
Add the SS7 subsystem to identify the mated STPs. Adding the SS7 Subsystem, page 22
Step 6
Add the SS7 routes for each signaling path from the Adding the SS7 Signaling Service, page 24
signaling controller to the destination switch.
Step 7
Add the SS7 signaling service from the PGW to the Adding the SS7 Signaling Service, page 24
destination switch.
Provision signaling links
Step 1
Add the external nodes for Cisco ITP-Ls.
Adding ITP-L External Nodes, page 26
Step 2
(Optional) Add IP routes.
Adding IP Routes to Cisco ITP-Ls (Optional),
page 28
Step 3
Add sessionsets for PGW-ITP-L communication.
Adding Sessionsets for PGW-ITP-L
Communication, page 30
Step 4
Add C7 IP Links to Cisco ITP-Ls
Adding C7 IP Links to Cisco ITP-Ls, page 32
Provision NAS6 links
Step 1
Add external nodes for the NASes in your network. Adding NAS External Nodes, page 35
Step 2
Add NAS signaling services for each NAS.
Adding NAS Signaling Services, page 37
Step 3
Add IP links for each NAS to PGW.
Adding IP Links, page 39
Provision trunks
Step 1
Create the trunk file and add trunks from each NAS Using a Text File to Add Trunks, page 42
to the signaling controller.
Step 2
Import the trunk file.
Using a Text File to Add Trunks, page 42
Deploy the session
1. OPC = origination point code
2. DPC = destination point code
3. APCs = adjacent point codes
4. STPs = Signal Transfer Points
5. Cisco ITP-Ls = Cisco IP Transfer Point - LinkExtender (previously named Cisco Signaling Link Terminal (SLT))
6. NAS = network access server
Note
Trunk groups and trunk routing are not used in the Cisco SS7 Interconnect for Access Servers Solution.
This solution uses nailed trunks between the NASs and the PSTN switch. The signaling controller does
not perform trunk group selection in this solution.
Provisioning Worksheet
Table 1 shows a provisioning worksheet for the sample configuration shown in the document. The
parameter values in the Parameters column are for illustration purposes only. Use the real parameter
values to replace them when you perform the configuration.
Cisco PGW 2200 Signaling Mode Design Guide
3
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Worksheet
Table 1
Provisioning Worksheet
Component
MML Name
Description
OPC
opc
Origination point code
DPC
APC
APC
Linkset
Linkset
SS7 route
SS7 route
SS7 subsystem
SS7 subsystem
dpc1
apc1
apc2
ls01
ls02
ss7route1
ss7route2
subsys1
subsys2
Cisco PGW 2200 Signaling Mode Design Guide
4
DPC of PSTN Switch A
APC for STP A
APC for STP B
Linkset from signaling
controller to STP A
Linkset from signaling
controller to STP B
Route 1 to PSTN Switch A
through LS1
Route 2 to PSTN Switch A
through LS2
Mate STP A to STP B
Mate STP B to STP A
Parameters
•
netaddr: 171.1.4
•
netind: 2 (national network)
•
type:trueopc
•
netaddr: 171.1.3
•
netind: 2 (national network)
•
netaddr: 171.16.1
•
netind: 2 (national network)
•
netaddr: 171.16.2
•
netind: 2 (national network)
•
apc: apc1
•
type: IP
•
proto: SS7-ANSI
•
apc: apc2
•
type: IP
•
proto: SS7-ANSI
•
opc: opc
•
dpc: dpc1
•
lnkset: ls01
•
pri: 1
•
opc: opc
•
dpc: dpc1
•
lnkset: ls02
•
pri: 1
•
svc: apc1
•
matedapc: apc2
•
proto: SS7-ANSI
•
pri: 3
•
opc: opc
•
svc: apc2
•
matedapc: apc1
•
proto: SS7-ANSI
•
pri: 3
•
opc: opc
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Worksheet
Table 1
Provisioning Worksheet (continued)
Component
MML Name
Description
Parameters
SS7 signaling
service
ss7sigsvc
SS7 signaling path to
PSTN Switch A
•
mdo: ANSISS7_STANDARD
•
opc: opc
•
dpc: dpc1
•
custgrpid: d125
•
type: SLT
•
isdnsigtype: N/A
•
group: 0
•
type: SLT
•
isdnsigtype: N/A
•
group: 0
(Optional) ITP-L iproute-1-to- IP route 1 from PGW to
IP route
itp-l-1
ITP-L-1. The ITP-L IP
route is required when the
PGW and Cisco ITP-Ls
are not in the same subnet.
The PGW communicates
with the ITP-L with the
help of a gateway
provisioned in the nexthop
parameter.
•
dest: 209.165.200.230
•
nexthop: 209.165.200.240 (in the
same subnet with IP_Addr1)
•
ipaddr: IP_Addr1
•
pri: 1
(Optional) ITP-L iproute-2-to- IP route 2 from PGW to
IP route
itp-l-1
ITP-L-1. The ITP-L IP
route is required when the
PGW and Cisco ITP-Ls
are not in the same subnet.
The PGW communicates
with the ITP-L with the
help of a gateway
provisioned in nexthop
parameter.
•
dest: 209.165.201.6
•
nexthop: 209.165.201.20 (in the
same subnet with IP_Addr2)
•
ipaddr: IP_Addr2
•
pri: 1
(Optional) ITP-L iproute-1-to- IP route 1 from PGW to
IP route
itp-l-2
ITP-L-2. The ITP-L IP
route is required when
PGW and Cisco ITP-Ls
are not in the same subnet.
The PGW communicates
with the ITP-L with the
help of a gateway
provisioned in nexthop
parameter.
•
dest: 209.165.200.231
•
nexthop: 209.165.200.240 (in the
same subnet with IP_Addr1)
•
ipaddr: IP_Addr1
•
pri: 1
ITP-L external
node
ITP-L external
node
itp-l-1
itp-l-2
External node ITP-L-1
External node ITP-L-2
Cisco PGW 2200 Signaling Mode Design Guide
5
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Worksheet
Table 1
Component
Provisioning Worksheet (continued)
MML Name
Parameters
(Optional) ITP-L iproute-2-to- IP route 2 from PGW to
IP route
itp-l-2
ITP-L-2. The ITP-L IP
route is required when the
PGW and Cisco ITP-Ls
are not in the same subnet.
The PGW communicates
with the ITP-L with the
help of a gateway
provisioned in nexthop
parameter.
•
dest: 209.165.201.7
•
nexthop: 209.165.201.20 (in the
same subnet with IP_Addr2)
•
ipaddr: IP_Addr2
•
pri: 1
Sessionset
•
port: 7000
•
peerAddr1 = 209.165.200.230
•
peerAddr2 = 209.165.201.6
•
peerport: 7000
•
ipAddr1: IP_Addr1
•
ipAddr2: IP_Addr2
•
ipRoute1:iproute-1-to-itp-l-1
•
ipRoute2:iproute-2-to-itp-l-1
•
extnode: itp-l-1
•
type: BSMV0
•
port: 7000
•
peerAddr1 = 209.165.200.231
•
peerAddr2 = 209.165.201.7
•
peerport: 7000
•
ipAddr1: IP_Addr1
•
ipAddr2: IP_Addr2
•
ipRoute1:iproute-1-to-itp-l-2
•
ipRoute2:iproute-2-to-itp-l-2
•
extnode: itp-l-2
•
type: BSMV0
•
pri: 1
•
slc: 0
•
lnkset: ls01
•
sessionset: sessionset-1
•
timeslot: 0
Sessionset
C7 IP link
sessionset-1
sessionset-2
c7iplink1
Cisco PGW 2200 Signaling Mode Design Guide
6
Description
Sessionset for itp-l-1
Sessionset for itp-l-2
Link 1 in Linkset 1
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Worksheet
Table 1
Provisioning Worksheet (continued)
Component
MML Name
Description
C7 IP link
c7iplink2
Link 2 in Linkset 1
C7 IP link
C7 IP link
NAS external
node
NAS external
node
NAS external
node
c7iplink3
c7iplink4
nas1
nas2
nas3
NAS signaling
service
nassvc1
NAS signaling
service
nassvc2
NAS signaling
service
nassvc3
Parameters
•
pri: 1
•
slc: 1
•
lnkset: ls01
•
sessionset: sessionset-2
•
timeslot: 0
•
pri: 1
•
slc: 0
•
lnkset: ls02
•
sessionset: sessionset-1
•
timeslot: 0
•
pri: 1
•
slc: 1
•
lnkset: ls02
•
sessioinset: sessionset-2
•
timeslot: 0
•
type: AS5300
•
isdnsigtype: N/A
•
group: 0
•
type: AS5300
•
isdnsigtype: N/A
•
group: 0
•
type: AS5300
•
isdnsigtype: N/A
•
group: 0
Signaling service for
NAS 1
•
extnode: nas1
•
MDO: BELL_1268_C2
Signaling service for
NAS 2
•
extnode: nas2
•
MDO: BELL_1268_C2
Signaling service for
NAS 3
•
extnode: nas3
•
MDO: BELL_1268_C2
Link 1 in Linkset 2
Link 2 in Linkset 2
NAS 1
NAS 2
NAS 3
Cisco PGW 2200 Signaling Mode Design Guide
7
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Worksheet
Table 1
Provisioning Worksheet (continued)
Component
MML Name
Description
IP link
nas1link1
IP link 1 for NAS 1
IP link
IP link
IP link
nas1link2
nas2link1
nas2link2
Cisco PGW 2200 Signaling Mode Design Guide
8
IP link 2 for NAS 1
IP link 1 for NAS 2
IP link 2 for NAS 2
Parameters
•
svc: nassvc1
•
ipaddr: IP_Addr1
•
port: 3001
•
peeraddr: 209.165.200.225
•
peerport: 3001
•
pri: 1
•
svc: nassvc1
•
ipaddr: IP_Addr2
•
port: 3001
•
peeraddr: 209.165.201.1
•
peerport: 3001
•
pri: 1
•
svc: nassvc2
•
ipaddr: IP_Addr1
•
port: 3001
•
peeraddr: 209.165.200.226
•
peerport: 3001
•
pri: 1
•
svc: nassvc2
•
ipaddr: IP_Addr2
•
port: 3001
•
peeraddr: 209.165.201.2
•
peerport: 3001
•
pri: 1
Cisco PGW 2200 Signaling Mode Design Guide
Starting the Provisioning Session
Table 1
Provisioning Worksheet (continued)
Component
MML Name
Description
IP link
nas3link1
IP link 1 for NAS 3
IP link
nas3link2
Parameters
IP link 2 for NAS 3
•
svc: nassvc3
•
ipaddr: IP_Addr1
•
port: 3001
•
peeraddr: 209.165.200.227
•
peerport: 3001
•
pri: 1
•
svc: nassvc3
•
ipaddr: IP_Addr2
•
port: 3001
•
peeraddr: 209.165.201.3
•
peerport: 3001
•
pri: 1
Starting the Provisioning Session
Log in to the PGW and start an MML session. For more information on MML commands, see the
Cisco Media Gateway Controller Software Release 9 MML Command Reference at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/command/reference/mmlref_1.html.
Caution
Do not log in as root when starting MML. If you log in as root, you cannot start an MML session.
To start an MML session:
Step 1
Log in to the signaling controller as a user who is a member of the mgcgrp group.
Step 2
Enter mml:
machine-name% mml
copyright © 1998-2002, Cisco Systems, Inc.
machine-name mml>
You can still log in if another session is running:
machine-name% mml
copyright © 1998-2002, Cisco Systems, Inc.
Session 1 is in use, using session 2
machine-name mml>
Step 3
Start a provisioning session by entering the prov-sta::srcver="new",dstver="ver1" command:
machine-name mml> prov-sta::srcver="new",dstver="ver1"
Cisco PGW 2200 Signaling Mode Design Guide
9
Cisco PGW 2200 Signaling Mode Design Guide
MML Tips
Media Gateway Controller 2007-04-04 15:00:57
COMPLD
"PROV-STA"
;
machine-name mml>
M
This starts a new provisioning session (“new”), names it CFG_ver1, and saves the configuration files in
/opt/CiscoMGC/etc/CONFIG_LIB/CFG_ver1.
Note
To modify an existing configuration and save it as another version, use the prov-sta command.
prov-sta::srcver=”ver1”, dstver=”ver2”.
This command starts a provisioning session, opens the existing configuration named ver1, and saves the
configuration as ver2.
Tip
If another provisioning session is running, you cannot start a provisioning session. You receive an error
message like the one shown in Example 1.
Example 1
Provisioning Session Error
machine-name mml> prov-sta::srcver="new",dstver="ver1"
Media Gateway Controller 2007-04-04 15:02:42
M DENY
SROF
"PROV-STA: POM session is already in use by mml2"
/* Status, Requested Operation Failed on the component */
;
To see if another provisioning session is running, enter the prov-rtrv:session command:
machine-name mml> prov-rtrv:session
Media Gateway Controller 2007-04-04 15:03:07
M RTRV
"session=ver1:session"
/*
Session ID = mml2
SRCVER = new
DSTVER = ver1
*/
;
This example shows that an active provisioning session named ver1 is in use.
See the Cisco Media Gateway Controller Software Release 9 Provisioning Guide for more information
on provisioning with MML and general provisioning steps. The Provisioning Guide is at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/provisioning/guide/prvgde.html.
MML Tips
MML commands use the following syntax:
command_name:[target][, target][, target. . .][:Parameter_List][;comments]
Cisco PGW 2200 Signaling Mode Design Guide
10
Cisco PGW 2200 Signaling Mode Design Guide
MML Tips
When entering MML commands, remember the following:
•
In general, MML commands are not case sensitive. However, file names are case sensitive when
used as arguments in MML commands (for example, TKGFile, BCFile, RoutingFile).
•
Use only one MML command on each line.
•
Anything entered after a semicolon (;) is treated as a comment (this is primarily useful for MML
command scripts).
•
Do not use punctuation (such as the period character) for target names; for example, do not use
test.log as a logging destination.
•
After you start a provisioning session, MML displays COMPLD, indicating success. The COMPLD
message is displayed after successful commands. For failed commands, MML displays DENY.
•
If the session continues without activity for 5 more minutes, it terminates:
/* POM session is idle, the session will be closed in 5 min. if it continues to be idle */
•
If a session is inactive for 35 minutes, this warning is displayed:
/* POM session has been closed as it was idle for 35 min. */
•
As many as 12 MML sessions can exist at any given time; however, only one provisioning session
is allowed.
•
You can create an ASCII text file for batch processing of provisioning commands.
•
You can create batch files for individual segments of provisioned data.
•
During batch file execution, each MML command response echoes to the terminal. You can log
command responses for later review so that the file can run unattended.
•
Place quotation marks around all value strings in your commands. For example, card="Interface1".
The keyword card does not have to be enclosed in quotation marks. The value Interface1 is being
assigned to keyword card and must be enclosed in quotations.
•
Press Tab key when you are typing an MML command to get the hints and the tips for the command.
To obtain on-line help in an MML session, enter help at the command prompt. For more information on
MML commands, see the Cisco Media Gateway Controller Software Release 9 MML Command
Reference at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/command/reference/mmlref_1.html.
Tip
To repeat the last MML command you entered, use the up arrow. To scroll through all previously entered
MML commands, continue to use the up arrow. To modify and reenter a previously entered command,
use the up arrow to display the command and then the left- and right-arrows, Backspace, Delete, and
alphanumeric keys to edit the command. Press Enter to reenter the command.
Note
Many procedures in this document refer to sections in Cisco Media Gateway Controller Software
Release 9 Provisioning Guide. Keep that book handy when performing the procedures in this chapter.
Cisco PGW 2200 Signaling Mode Design Guide
11
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning SS7 Signaling Routes
Provisioning SS7 Signaling Routes
The SS7 signaling route is the path from the Cisco MGC host to a service switching point (SSP) through
the Cisco ITP-Ls and signal transfer points (STPs). In the sample configuration in this chapter, the SSP
is the PSTN switch. When you provision the SS7 signaling routes, you add the following components:
•
OPC—Origination point code or the point code of the Cisco MGC in your network
•
DPC—Destination point code or the point code of the PSTN switch A to which you are connecting
•
APCs—Adjacent point codes or the point codes of the adjacent STPs
•
Linksets
•
SS7 subsystems (to identify mated STPs)
•
SS7 routes
•
SS7 signaling services
For more information on configuring SS7 signaling routes, see the Cisco Media Gateway Controller
Software Release 9 Provisioning Guide at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/provisioning/guide/prvgde.html.
Adding the OPC
A point code is an SS7 network address that identifies an SS7 network node, such as an STP or an SSP.
Note
ITU point codes contain 14 bits, and North American point codes contain 24 bits. Use the correct format
when you add the origination point code (OPC).
Use the following command to add the point code for the PGW shown in the shaded area in Figure 2.
Cisco PGW 2200 Signaling Mode Design Guide
12
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning SS7 Signaling Routes
Figure 2
Adding the OPC
LAN
switches
STP A 171.16.1
209.165.200.230
171.1.4
STP
Cisco ITP-Ls
PSTN
switch
A
171.1.3
PGW 2200
209.165.201.7
IMTs
NAS1
IMTs
NAS2
IMTs
NAS3
QoS packet
network
Telephone
exchange
Gateway
router
Step 1
280711
STP
STP B 171.16.2
Command/Action
Purpose
machine-name mml> prov-add:opc:name="opc",
netaddr="171.1.4",netind=2,type="trueopc",de
sc="origination point code"
Media Gateway Controller 2007-04-04
15:04:48
M COMPLD
"opc"
;
Adds a point code and assigns the name opc to
the PGW 171.1.4.
Verifying the Added OPC
To verify that you have added the OPC, use the prov-rtrv:opc command:
machine-name mml> prov-rtrv:opc:name="opc"
Media Gateway Controller 2007-04-04 15:05:44
M RTRV
"session=ver1:opc"
/*
NAME = opc
DESC = origination point code
Cisco PGW 2200 Signaling Mode Design Guide
13
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning SS7 Signaling Routes
NETADDR = 171.1.4
NETIND = 2
TYPE = TRUEOPC
*/
;
You can retrieve all the OPCs by using the prov-rtrv:opc:"all" command, as shown in Example 2.
Example 2
Retrieving All OPCs
machine-name mml> prov-rtrv:opc:"all"
Media Gateway Controller 2007-04-04 15:05:32
M RTRV
"session=ver1:opc"
/*
NAME
NETADDR
NETIND
TYPE
TRUEOPC
-----------------------opc
171.1.4
2
TRUEOPC
*/
;
Adding the DPC
Use the following command to add the point code for the PSTN switch A, shown in the shaded area in
Figure 3.
Cisco PGW 2200 Signaling Mode Design Guide
14
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning SS7 Signaling Routes
Figure 3
Adding the DPC
LAN
switches
STP A 171.16.1
209.165.200.230
171.1.4
STP
Cisco ITP-Ls
PSTN
switch
A
171.1.3
PGW 2200
209.165.201.7
IMTs
NAS1
IMTs
NAS2
IMTs
NAS3
QoS packet
network
Telephone
exchange
Gateway
router
Step 1
280705
STP
STP B 171.16.2
Command/Action
Purpose
machine-name mml> prov-add:dpc:name="dpc1",
netaddr="171.1.3",netind=2,desc="DPC of PSTN
Switch A"
Media Gateway Controller 2007-04-04
15:08:41
M COMPLD
"dpc"
;
Adds a point code and assigns the name dpc1 to
switch 171.1.3.
Verifying the Added DPC
To verify that you have added the DPC, use the prov-rtrv:dpc command:
machine-name mml> prov-rtrv:dpc:name="dpc1"
Media Gateway Controller 2007-04-04 15:09:25
M RTRV
"session=ver1:dpc"
/*
NAME = dpc1
DESC = DPC of PSTN Switch A
Cisco PGW 2200 Signaling Mode Design Guide
15
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning SS7 Signaling Routes
NETADDR = 171.1.3
NETIND = 2
*/
;
You can retrieve all the DPCs by using the prov-rtrv:dpc:"all" command, as shown in Example 3.
Example 3
Retrieving All DPCs
machine-name mml> prov-rtrv:dpc:"all"
Media Gateway Controller 2007-04-04 15:10:47
M RTRV
"session=ver1:dpc"
/*
NAME
NETADDR
NETIND
--------------dpc1
171.1.3
2
*/
;
Adding the APCs
Use the following procedure to add the adjacent point codes (APCs) for the STPs shown in the shaded
area in Figure 4.
Note
The sample configuration in this chapter uses A-links from the STPs for signaling to the Cisco ITP-Ls.
If you have a configuration where F-links come directly from the SSP to the Cisco ITP-Ls, you do not
need to add APCs.
Cisco PGW 2200 Signaling Mode Design Guide
16
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning SS7 Signaling Routes
Figure 4
Adding the APCs
LAN
switches
STP A 171.16.1
209.165.200.230
171.1.4
STP
Cisco ITP-Ls
PSTN
switch
A
171.1.3
PGW 2200
209.165.201.7
IMTs
NAS1
IMTs
NAS2
IMTs
NAS3
QoS packet
network
Telephone
exchange
Gateway
router
280703
STP
STP B 171.16.2
Command/Action
Purpose
Step 1
machine-name mml> prov-add:apc:name="apc1",
netaddr="171.16.1",netind=2,desc="APC for STP A"
Media Gateway Controller 2007-04-04 15:11:51
M COMPLD
"apc"
;
Adds a point code and assigns the name
apc1 to STP A, 171.16.1.
Step 2
machine-name mml> prov-add:apc:name="apc2",
netaddr="171.16.2",netind=2,desc="APC for STP B"
Media Gateway Controller 2007-04-04 15:12:36
M COMPLD
"apc"
;
Adds a point code and assigns the name
apc2 to STP B, 171.16.2.
Verifying the Added APCs
To verify that you have entered the APCs, use the prov-rtrv:apc command for each APC. For example,
to verify that the first APC was added:
machine-name mml> prov-rtrv:apc:name="apc1"
Media Gateway Controller 2007-04-04 15:13:54
Cisco PGW 2200 Signaling Mode Design Guide
17
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning SS7 Signaling Routes
M
RTRV
"session=ver1:apc"
/*
NAME = apc1
DESC = APC for STP A
NETADDR = 171.16.1
NETIND = 2
*/
;
You can retrieve all the APCs by using the prov-rtrv:apc:"all" command, as shown in Example 4.
Example 4
Retrieving All APCs
machine-name mml> prov-rtrv:apc:"all"
Media Gateway Controller 2007-04-04 10:45:12
M RTRV
"session=ver1:apc"
/*
NAME
NETADDR
NETIND
--------------apc1
171.16.1
2
apc2
171.16.2
2
*/
;
Adding Linksets
A linkset is a logical set of one or more links originating from an SS7 node (STP) and connecting to an
adjacent node. In the example used in this section, the linkset contains communication links that connect
from the signaling controller to an adjacent STP.
You must provision one linkset for each connection through the STP to the signaling controller. The
shaded area in Figure 5 shows the linksets you provision in this example.
Cisco PGW 2200 Signaling Mode Design Guide
18
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning SS7 Signaling Routes
Figure 5
Adding Linksets
LAN
switches
STP A 171.16.1
209.165.200.230
171.1.4
STP
Cisco ITP-Ls
PSTN
switch
A
171.1.3
PGW 2200
209.165.201.7
IMTs
NAS1
IMTs
NAS2
IMTs
NAS3
QoS packet
network
Telephone
exchange
Gateway
router
Command/Action
Purpose
Step 1
machine-name mml> prov-add:lnkset:name="ls01",
apc="apc1",type="IP",proto="SS7-ANSI",desc="Li
nkset from PGW to STP A"
Media Gateway Controller 2007-04-04
15:16:42
M COMPLD
"lnkset"
;
Defines a linkset ls01 to STP A.
Step 2
machine-name mml> prov-add:lnkset:name="ls02",
apc="apc2",type="IP",proto="SS7-ANSI",desc="Li
nkset from PGW to STP B"
Media Gateway Controller 2007-04-04
15:17:16
M COMPLD
"lnkset"
;
Defines a linkset ls02 to STP B.
280706
STP
STP B 171.16.2
Cisco PGW 2200 Signaling Mode Design Guide
19
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning SS7 Signaling Routes
Verifying the Added Linksets
To verify that you have entered the linksets, use the prov-rtrv:lnkset command for each linkset. For
example, to verify that the first linkset was added:
machine-name mml> prov-rtrv:lnkset:name="ls01"
Media Gateway Controller 2007-04-04 15:18:40
M RTRV
"session=ver1:lnkset"
/*
NAME = ls01
DESC = Linkset from PGW to STP A
APC = apc1
PROTO = SS7-ANSI
TYPE = IP
*/
;
You can retrieve all linksets by using the prov-rtrv:lnkset:“all” command, as shown in Example 5.
Example 5
Retrieving All Linksets
machine-name mml> prov-rtrv:lnkset:"all"
Media Gateway Controller 2007-04-04 15:20:43
M RTRV
"session=ver1:lnkset"
/*
NAME
APC
PROTO
---------ls01
apc1
SS7-ANSI
ls02
apc2
SS7-ANSI
*/
;
Note
TYPE
---IP
IP
After creating the linksets, you must create the C7 IP links for each linkset. See the “Adding C7 IP Links
to Cisco ITP-Ls” section on page 32.
Adding SS7 Routes
An SS7 route is a path through a linkset between the PGW and another PGW or TDM switch. In this
example, the SS7 routes indicate the linksets that carry SS7 signals between the PGW and the PSTN
switch A.
You must add an SS7 route for each signaling path from the PGW to the PSTN switch A. You provision
a route for each linkset. The shaded area in Figure 6 shows the SS7 routes that you provision for the
example that follows.
Cisco PGW 2200 Signaling Mode Design Guide
20
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning SS7 Signaling Routes
Figure 6
Adding SS7 Routes
LAN
switches
209.165.200.230
STP
171.1.4
Cisco ITP-Ls
STP
STP B 171.16.2
PSTN
switch
A
171.1.3
IMTs
NAS1
IMTs
NAS2
IMTs
PGW 2200
209.165.201.7
NAS3
QoS packet
network
Telephone
exchange
Gateway
router
280714
STP A 171.16.1
Command/Action
Purpose
Step 1
machine-name mml> prov-add:ss7route:name=
"ss7route1",opc="opc",dpc="dpc1",lnkset="l
s01",pri=1,desc="Route 1 to PSTN Switch A
through LS01"
Media Gateway Controller 2007-04-04
15:24:14
M COMPLD
"ss7route"
;
Defines an SS7 route from the PGW (opc) to
PSTN Switch A through the previously defined
linkset through STP A (ls01).
Step 2
machine-name mml> prov-add:ss7route:name=
"ss7route2",opc="opc",dpc="dpc1",lnkset="l
s02",pri=1,desc="Route 2 to PSTN Switch A
through LS02"
Media Gateway Controller 2007-04-04
15:25:44
M COMPLD
"ss7route"
;
Defines an SS7 route from the PGW (opc) to
PSTN Switch A through the previously defined
linkset through STP B (ls02).
Cisco PGW 2200 Signaling Mode Design Guide
21
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning SS7 Signaling Routes
Verifying the Added SS7 Routes
To verify that you have entered the SS7 routes, use the prov-rtrv:ss7route command for each SS7 route.
For example, to verify that the first SS7 route was added:
machine-name mml> prov-rtrv:ss7route:name="ss7route1"
Media Gateway Controller 2007-04-04 15:32:21
M RTRV
"session=ver1:ss7route"
/*
NAME = ss7route1
DESC = Route 1 to PSTN Switch A through LS01
OPC = opc
DPC = dpc1
LNKSET = ls01
PRI = 1
*/
;
You can retrieve all SS7 routes by using the prov-rtrv:ss7route:“all” command, as shown in
Example 6.
Example 6
Retrieving All SS7 Routes
machine-name mml> prov-rtrv:ss7route:"all"
Media Gateway Controller 2007-04-04 11:01:18
M RTRV
"session=ver1:ss7route"
/*
NAME
OPC
DPC
LINKSET PRI
--------------ss7route1
opc
dpc1 ls01
1
ss7route2
opc
dpc1 ls02
1
*/
;
Adding the SS7 Subsystem
You must add an SS7 subsystem that identifies each pair of mated STPs. This allows the PGW to route
traffic over the C-links between the STPs in case of a failure between one of the STPs and an endpoint.
The shaded area in Figure 7 shows the STPs you must connect (STP A and STP B).
Cisco PGW 2200 Signaling Mode Design Guide
22
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning SS7 Signaling Routes
Figure 7
Adding the SS7 Subsystem
LAN
switches
STP A 171.16.1
209.165.200.230
171.1.4
STP
Cisco ITP-Ls
STP B 171.16.2
PSTN
switch
A
171.1.3
PGW 2200
209.165.201.7
IMTs
NAS1
IMTs
NAS2
IMTs
NAS3
QoS packet
network
Telephone
exchange
Gateway
router
280716
STP
Command/Action
Purpose
Step 1
machine-name mml>prov-add:ss7subsys:name=
"subsys1",desc="Mate STP A to STP B",
svc="apc1",proto="SS7-ANSI",matedapc="apc2",
pri=3,opc=”opc”
Media Gateway Controller 2007-04-04
15:21:56
M COMPLD
"ss7subsys"
;
Defines a mated STP subsystem from STP A
to STP B.
Step 2
machine-name mml>prov-add:ss7subsys:name=
"subsys2",desc="Mate STP B to STP A",
svc="apc2",proto="SS7-ANSI",matedapc="apc1",
pri=3,opc=”opc”
Media Gateway Controller 2007-04-04
15:21:56
M COMPLD
"ss7subsys"
;
Defines a mated STP subsystem from STP B
to STP A.
Cisco PGW 2200 Signaling Mode Design Guide
23
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning SS7 Signaling Routes
Verifying the Added SS7 Subsystem
To verify that you have added the SS7 subsystem, use the prov-rtrv:ss7subsys command:
machine-name mml> prov-rtrv:ss7subsys:name="subsys1"
Media Gateway Controller 2007-04-04 15:22:44
M RTRV
"session=ver1:ss7subsys"
/*
NAME = subsys1
DESC = Mate STP A to STP B
SVC = apc1
PRI = 3
MATEDAPC = apc2
SSN = 0
PROTO = SS7-ANSI
STPSCPIND = 0
TRANSPROTO = SCCP
OPC = opc
SUAKEY =
REMOTESSN = 0
*/
;
You can retrieve all SS7 subsystems by entering the prov-rtrv:ss7subsys:"all" command, as shown in
Example 7.
Example 7
Retrieving All SS7 Subsystems
machine-name mml> prov-rtrv:ss7subsys:"all"
Media Gateway Controller 2007-04-04 11:01:18
M RTRV
"session=ver1:ss7subsys"
/*
NAME
SVC PRI MATEDAPC LOCALSSN PROTO
STPSCPIND
------ --- -------- -------- ------------subsys1 apc1 3
apc2
0
SS7-ANSI 0
subsys2 apc2 3
apc1
0
SS7-ANSI 0
*/
;
TRANSPROTO
---------SCCP
SCCP
OPC SUAKEY REMOTESSN
--- ------ --------opc
0
opc
0
Adding the SS7 Signaling Service
The SS7 signaling service specifies the path and the protocol variant that the PGW uses to communicate
with a remote switch (SSP) that sends bearer traffic to the NASs.
You must add an SS7 signaling service from the PGW to the PSTN switch. The shaded area in Figure 8
shows the signaling service you are adding.
Cisco PGW 2200 Signaling Mode Design Guide
24
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning SS7 Signaling Routes
Figure 8
Adding the SS7 Signaling Service
LAN
switches
STP A 171.16.1
209.165.200.230
171.1.4
STP
Cisco ITP-Ls
STP B 171.16.2
PSTN
switch
A
171.1.3
PGW 2200
209.165.201.7
IMTs
NAS1
IMTs
NAS2
IMTs
NAS3
QoS packet
network
Telephone
exchange
Gateway
router
Step 1
280715
STP
Command/Action
Purpose
machine-name mml>prov-add:ss7path:name=
"ss7sigsvc",mdo="ANSISS7_STANDARD",opc=”opc”,
dpc="dpc1",custgrpid="d125",desc="SS7 signaling
path to PSTN Switch A"
Media Gateway Controller 2007-03-03 14:21:04
M COMPLD
"ss7path"
;
Defines the SS7 path and protocol
between the PGW and PSTN Switch A.
Note
We recommend that you provision a customer group ID for your SS7 signaling service, even if
you are not planning on currently using the screening tools. This is because once the SS7
signaling service is placed in service, you would have to take it out-of-service to add a customer
group ID.
Cisco PGW 2200 Signaling Mode Design Guide
25
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Signaling Links
Verifying the Added SS7 Signaling Service
To verify that you have added the SS7 signaling service, use the prov-rtrv:ss7path command:
mml> prov-rtrv:ss7path:name="ss7sigsvc"
Media Gateway Controller 2007-03-03 14:22:12
M RTRV
"session=ver1:ss7path"
/*
NAME = ss7sigsvc
DESC = SS7 signaling path to PSTN Switch A
MDO = ANSISS7_STANDARD
CUSTGRPID = d125
SIDE = network
DPC = dpc1
OPC = opc
M3UAKEY =
ORIGLABEL =
TERMLABEL =
*/
;
Provisioning Signaling Links
You must provision links for all physical connections bearing signals that enter and exit the PGW. This
includes SS7 signals from the SSP (PSTN Switch A) and signals to the NASs. You must add the
following components:
•
ITP-L external node
•
IP Routes to the Cisco ITP-Ls
•
Sessionsets for PGW-ITP-L communication
•
C7 IP links to the Cisco ITP-Ls
Adding ITP-L External Nodes
You must add an ITP-L external node for each ITP-L in your network. The shaded areas in Figure 9 show
the ITP-L external nodes you are adding. In this configuration there are two ITP-Ls.
Cisco PGW 2200 Signaling Mode Design Guide
26
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Signaling Links
Figure 9
Adding ITP-L External Nodes
LAN
switches
STP A 171.16.1
209.165.200.230
171.1.4
STP
Cisco ITP-Ls
PSTN
switch
A
171.1.3
PGW 2200
209.165.201.7
IMTs
NAS1
IMTs
NAS2
IMTs
NAS3
QoS packet
network
Telephone
exchange
Gateway
router
280706
STP
STP B 171.16.2
Command/Action
Purpose
Step 1
machine-name mml>prov-add:extnode:name=
"itp-l-1",desc="External Node ITP-L-1",
type="SLT",isdnsigtype="N/A",group=0
Media Gateway Controller 2007-03-03 14:21:04
M COMPLD
"extnode"
;
Adds an ITP-L external node itp-l-1.
Step 2
machine-name mml>prov-add:extnode:name=
"itp-l-2",desc="External Node ITP-L-2",
type="SLT",isdnsigtype="N/A",group=0
Media Gateway Controller 2007-03-03 14:21:04
M COMPLD
"extnode"
;
Adds an ITP-L external node itp-l-1.
Verifying the Added ITP-L External Nodes
To verify that you have added the ITP-L external nodes, use the prov-rtrv:extnode command. For
example, to verify that you have added the first ITP-L node:
Cisco PGW 2200 Signaling Mode Design Guide
27
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Signaling Links
mml> prov-rtrv:extnode:name="itp-l-1"
Media Gateway Controller 2007-03-03 14:22:12
M RTRV
"session=ver1:extnode"
/*
NAME = itp-l-1
DESC = External Node itp-l-1
TYPE = SLT
ISDNSIGTYPE = N/A
GROUP = 0
*/
;
You can retrieve all the external nodes using the prov-rtrv:extnode:"all" command, as shown in
Example 8.
Example 8
Retrieving All External Nodes
machine-name mml> prov-rtrv:extnode:"all"
Media Gateway Controller 2007-04-04 11:01:18
M RTRV
"session=ver1:extnode"
/*
NAME
TYPE
ISDNSIGTYPE
----------------itp-l-1
SLT
N/A
itp-l-2
SLT
N/A
*/
;
GROUP
----0
0
Adding IP Routes to Cisco ITP-Ls (Optional)
The IP route component specifies a set of static routes that PGW uses to deliver packets to nondirect
devices. IP routes are used when ITP-Ls are not in the same subnet with PGW. PGW communicates with
Cisco ITP-Ls with the help of a nexthop gateway. You can ignore this section if your ITP-Ls are in the
same subnets with PGWs.
Command/Action
Purpose
Step 1
machine-name mml>prov-add:iproute:name=
"iproute-1-to-itp-l-1", desc="First IP Route to
itp-l-1",dest="209.165.200.230",netmask="255.255
.255.224",ipAddr="IP_Addr1",pri=1,
nexthop="209.165.200.240"
Media Gateway Controller 2007-03-03 14:21:04
M COMPLD
"iproute"
;
Adds the first IP route to the external
node itp-l-1. Nexthop and IP_Addr1 must
be in the same subnet.
Step 2
machine-name mml> prov-add:iproute:name=
"iproute-2-to-itp-l-1", desc="Second IP Route to
itp-l-1",dest="209.165.201.6",netmask="255.255.2
55.224",ipAddr="IP_Addr2",pri=1,
nexthop="209.165.201.20"
Media Gateway Controller 2007-03-03 14:21:04
M COMPLD
"iproute"
;
Adds the second IP route to the external
node itp-l-1. Nexthop and IP_Addr2 must
be in the same subnet.
Cisco PGW 2200 Signaling Mode Design Guide
28
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Signaling Links
Command/Action
Purpose
Step 3
machine-name mml>prov-add:iproute:name=
"iproute-1-to-itp-l-2", desc="First IP Route to
itp-l-2",dest="209.165.200.231",netmask="255.255
.255.224",ipAddr="IP_Addr1",pri=1,
nexthop="209.165.200.240"
Media Gateway Controller 2007-03-03 14:21:04
M COMPLD
"iproute"
;
Adds the first IP route to the external
node itp-l-2. Nexthop and IP_Addr1 must
be in the same subnet.
Step 4
machine-name mml>prov-add:iproute:name=
"iproute-2-to-itp-l-2", desc="Second IP Route to
itp-l-2",dest="209.165.201.7",netmask="255.255.2
55.224",ipAddr="IP_Addr2",pri=1,
nexthop="209.165.201.20"
Media Gateway Controller 2007-03-03 14:21:04
M COMPLD
"iproute"
;
Adds the second IP route to the external
node itp-l-2. Nexthop and IP_Addr2 must
be in the same subnet.
Note
The IP address of the nexthop parameter should be on the same subnet with the IP address of the ipAddr
parameter. IP_Addr1 and IP_Addr2 are configured in the XECfgParm.dat file in the fold
/opt/CiscoMGC/etc. For more information on how to configure XECfgParm.dat, see “Configuring the
Execution Environment” section in Chapter 4 of the Cisco Media Gateway Controller Software
Installation and Configuration (Release 9.7) at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/installation/software/SW1/3ins_cfg.html.
Verifying the Added IP Routes to Cisco ITP-Ls
To verify that you have added the IP routes to Cisco ITP-Ls, use the prov-rtrv:iproute command. For
example, to verify that you have added the IP route to itp-l-1:
mml> prov-rtrv:iproute:name="iproute-1-to-itp-l-1"
Media Gateway Controller 2007-03-03 14:22:12
M RTRV
"session=ver1:iproute"
/*
NAME = iproute-1-to-itp-l-1
DESC = First IP route to itp-l-1
DEST = 209.165.200.230
NETMASK = 255.255.255.224
NEXTHOP = 209.165.200.240
IPADDR = IP_Addr1
PRI= 1
*/
;
You can retrieve all the IP routes using the prov-rtrv:iproute:"all" command, as shown in Example 9.
Example 9
Retrieving All IP Routes
machine-name mml> prov-rtrv:iproute:"all"
Media Gateway Controller 2007-04-04 11:01:18
M RTRV
Cisco PGW 2200 Signaling Mode Design Guide
29
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Signaling Links
"session=ver1:iproute"
/*
NAME
DEST
-----------------iproute-1-to-itp-l-1 209.165.200.230
iproute-1-to-itp-l-2 209.165.200.231
iproute-2-to-itp-l-1 209.165.201.6
iproute-2-to-itp-l-2 209.165.201.7
*/
;
NETMASk
--------------255.255.255.224
255.255.255.224
255.255.255.224
255.255.255.224
NEXTHOP
----------209.165.200.240
209.165.200.240
209.165.201.20
209.165.201.20
IPADDR
------IP_Addr1
IP_Addr1
IP_Addr2
IP_Addr2
PRIORITY
-------1
1
1
1
Adding Sessionsets for PGW-ITP-L Communication
In order to communicate with ITP-L, the PGW must set up sessions with ITP-Ls. Use the sessionset
component (a set of sessions) to define one sessionset for each of the two ITP-Ls. The shaded areas in
Figure 10 show the sessionsets you are adding for PGW-ITP-L communication.
Figure 10
Adding Sessionsets for PGW-ITP-L Communication
LAN
switches
209.30.200.250
209.30.201.15
STP A 171.16.1
209.165.200.230
STP
STP
STP B 171.16.2
PSTN
switch
A
171.1.3
209.165.201.7
IMTs
NAS1
IMTs
NAS2
IMTs
171.1.4
PGW 2200
NAS3
QoS packet
network
Telephone
exchange
Gateway
router
Cisco PGW 2200 Signaling Mode Design Guide
30
280712
Cisco ITP-Ls
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Signaling Links
Command/Action
Purpose
Step 1
machine-name mml>prov-add:sessionset:name=
"sessionset-1",port=7000,peerAddr1="209.165.200.
230", peerAddr2="209.165.201.6",peerport=7000,
ipAddr1="IP_Addr1",ipAddr2="IP_Addr2",
[ipRoute1="iproute-1-to-itp-l-1",
ipRoute2="iproute-2-to-itp-l-1",]
extnode="itp-l-1",type="BSMV0"
Media Gateway Controller 2007-03-03 14:21:04
M COMPLD
"sessionset"
;
Adds a sessionset for the external node
itp-l-1. In this configuration, IPRoute1
and IPRoute2 are optional. They are
required when PGW and Cisco ITP-Ls
are not in the same subnet.
Step 2
machine-name mml>prov-add:sessionset:name=
"sessionset-2",port=7000,peerAddr1="209.165.200.
231", peerAddr2="209.165.201.7",peerport=7000,
ipAddr1="IP_Addr1",ipAddr2="IP_Addr2",
[ipRoute1="iproute-1-to-itp-l-2",
ipRoute2="iproute-2-to-itp-l-2",]
extnode="itp-l-2",type="BSMV0"
Media Gateway Controller 2007-03-03 14:21:04
M COMPLD
"sessionset"
;
Adds a sessionset for the external node
itp-l-2. In this configuration, IPRoute1
and IPRoute2 are optional. They are
required when PGW and Cisco ITP-Ls
are not in the same subnet.
Verifying the Added Sessionsets
To verify that you have added the IP routes to Cisco ITP-Ls, use the prov-rtrv:sessionset command. For
example, to verify that the sessionset of itp-l-1 was added:
mml> prov-rtrv:sessionset:name:"sessionset-1"
Media Gateway Controller 2007-04-04 11:01:18
M RTRV
"session=ver1:sessionset"
/*
NAME = sessionset-1-1
DESC = Session Set sessionset-1 Backhaul Link 1
EXTERNAL NODE = itp-l-1
IPADDR = IP_Addr1
PORT = 7000
PEERADDR = 209.165.200.230
PEERPORT = 7000
TYPE = BSMV0
IPROUTE = [iproute-1-to-itp-l-1]
NAME = sessionset-1-2
DESC = Session Set sessionset-1 Backhaul Link 2
EXTERNAL NODE = itp-l-1
IPADDR = IP_Addr2
PORT = 7000
PEERADDR = 209.165.201.6
PEERPORT = 7000
TYPE = BSMV0
IPROUTE = [iproute-2-to-itp-l-1]
*/
;
You can retrieve all the sessionsets using the prov-rtrv:sessionset:"all" command, as shown in
Example 10.
Cisco PGW 2200 Signaling Mode Design Guide
31
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Signaling Links
Example 10
Retrieving All Sessionsets
machine-name mml> prov-rtrv:sessionset:"all"
Media Gateway Controller 2007-04-04 11:01:18
M RTRV
"session=ver1:sessionset"
/*
NAME
BACKHAUL LINK
EXTNODE IPADDR
PORT
---------------------- ------------------sessionset-1 sessionset-1-1 itp-l-1 IP_Addr1 7000
[iproute-1-to-itp-l-1]
sessionset-1 sessionset-1-2 itp-l-1 IP_Addr2 7000
[iproute-2-to-itp-l-1]
sessionset-2 sessionset-2-1 itp-l-2 IP_Addr1 7000
[iproute-1-to-itp-l-2]
sessionset-2 sessionset-2-2 itp-l-2 IP_Addr2 7000
[iproute-2-to-itp-l-2]
*/
;
PEERADDR
----------
PEERPORT TYPE
-------- ----
209.165.200.230 7000
BSMV0
209.165.201.6
7000
BSMV0
209.165.200.231 7000
BSMV0
209.165.201.7
BSMV0
7000
IPROUTE
Adding C7 IP Links to Cisco ITP-Ls
A C7 IP link component identifies a link between the Cisco ITP-L IP address and port, and an SSP or an
STP in the SS7 network. The C7 IP link identifies one of the links within a linkset.
Note
Use C7 IP links only when your configuration has Cisco ITP-Ls that carry SS7 signaling to the signaling
controller over IP. If your configuration does not include Cisco ITP-Ls and your links terminate from the
STPs directly into TDM cards in the signaling controller, you must provision TDM links. For example,
the Cisco SS7 Dial Access Solution Release 2.0 uses TDM cards and TDM links.
You must add a C7 IP link for each physical SS7 link that is connected to the SS7 network through the
Cisco ITP-L. These links correspond to the linksets you created in the “Adding Linksets” section on
page 18. The shaded area in Figure 11 shows the C7 IP links you provision in this example.
Cisco PGW 2200 Signaling Mode Design Guide
32
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Signaling Links
Figure 11
Adding C7 IP Links
LAN
switches
STP A 171.16.1
209.165.200.230
171.1.4
STP
Cisco ITP-Ls
PSTN
switch
A
171.1.3
IMTs
IMTs
IMTs
209.165.201.7
PGW 2200
NAS1
NAS2
QoS packet
network
NAS3
Telephone
exchange
Gateway
router
280704
STP
STP B 171.16.2
You must add two links for linkset 1 and two links for linkset 2.
Command/Action
Purpose
Step 1
machine-name mml>prov-add:c7iplnk:name="c7iplink1",
desc="C7IPlink-1 in ls 1",pri=1,slc=0,lnkset="ls01",
sessionset="sessionset-1",timeslot=0
Media Gateway Controller 2007-03-03 21:05:46
M COMPLD
"c7iplnk"
;
Defines an SS7 link from the PGW
through Cisco ITP-L 1
(209.165.200.230) to STP A. Uses the
ls01 linkset.
Step 2
machine-name mml>prov-add:c7iplnk:name="c7iplink2",
desc="C7IPlink-2 in ls 1",pri=1,slc=1,lnkset="ls01",
sessionset="sessionset-2",timeslot=0
Media Gateway Controller 2007-03-03 21:07:15
M COMPLD
"c7iplnk"
;¸
Defines an SS7 link from the PGW
through Cisco ITP-L 2 (209.165.201.7)
to STP A. Uses the ls01 linkset.
Cisco PGW 2200 Signaling Mode Design Guide
33
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Signaling Links
Command/Action
Purpose
Step 3
machine-name mml> prov-add:c7iplnk:name="c7iplink3",
desc="C7IPlink-3 in ls 2",pri=1,slc=0,lnkset="ls02",
sessionset="sessionset-1",timeslot=0
Media Gateway Controller 2007-03-03 21:08:51
M COMPLD
"c7iplnk"
;
Defines an SS7 link from the PGW
through Cisco ITP-L 1
(209.165.200.230) to STP B. Uses the
ls02 linkset.
Step 4
machine-name mml> prov-add:c7iplnk:name="c7iplink4",
desc="C7IPlink-4 in ls 2",pri=1,slc=1,lnkset="ls02",
sessionset="sessionset-2",timeslot=0
Media Gateway Controller 2007-03-03 21:10:52
M COMPLD
"c7iplnk"
;
Defines an SS7 link from the PGW
through Cisco ITP-L 2 (209.165.201.7)
to STP B. Uses the ls02 linkset.
Verifying the Added C7 IP Links
To verify that you have entered the C7 IP links, use the prov-rtrv:c7iplnk command. For example, to
verify that the first C7 IP link was added:
machine-name mml> prov-rtrv:c7iplnk:name="c7iplink1"
Media Gateway Controller 2007-03-03 21:12:47
M RTRV
"session=ver1:c7iplnk"
/*
NAME = c7iplink1
DESC = C7IPlink-1 in ls 1
LNKSET = ls01
SLC = 0
PRI = 1
TIMESLOT/SLOT = 0
SESSIONSET = sessionset-1
*/
;
You can retrieve all the C7 IP links using the prov-rtrv:c7iplnk:"all" command, as shown in
Example 11.
Example 11
Retrieving All C7 IP Links
machine-name mml> prov-rtrv:c7iplnk:"all"
Media Gateway Controller 2007-04-04 11:40:17
M RTRV
"session=ver1:c7iplnk"
/*
NAME
LNKSET PRI
SLC
--------- ----c7iplink1
ls01
1
0
c7iplink2
ls01
1
1
c7iplink3
ls02
1
0
c7iplink4
ls02
1
1
*/
;
Cisco PGW 2200 Signaling Mode Design Guide
34
TIMESLOT
-------0
0
0
0
SESSIONSET
---------sessionset-1
sessionset-2
sessionset-1
sessionset-2
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning NAS Links
Provisioning NAS Links
NAS links indicate the communication path the PGW uses to control the bearer traffic that passes
through each NAS.
To add links to the NASs in your network, you must add the following components:
•
NAS external node
•
NAS signaling service
•
IP links
Adding NAS External Nodes
You must add a NAS external node for each NAS in your network. The shaded areas in Figure 12 show
the NAS external nodes.
Figure 12
Adding NAS External Nodes
LAN
switches
STP A 171.16.1
209.165.200.230
171.1.4
STP
Cisco ITP-Ls
STP B 171.16.2
PSTN
switch
A
171.1.3
PGW 2200
209.165.201.7
IMTs
NAS1
IMTs
NAS2
IMTs
NAS3
QoS packet
network
Telephone
exchange
Gateway
router
280708
STP
Cisco PGW 2200 Signaling Mode Design Guide
35
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning NAS Links
Command/Action
Purpose
Step 1
machine-name mml> prov-add:extnode:name="nas1",
desc="NAS 1",type="AS5300",isdnsigtype="N/A",group=0
Media Gateway Controller 2007-03-04 11:36:07
M COMPLD
"extnode"
;
Defines network access server NAS 1
as an external node.
Step 2
machine-name mml> prov-add:extnode:name="nas2",
desc="NAS 2",type="AS5300",isdnsigtype="N/A",group=0
Media Gateway Controller 2007-03-04 11:36:21
M COMPLD
"extnode"
;
Defines network access server NAS 2
as an external node.
Step 3
machine-name mml> prov-add:extnode:name="nas3",
desc="NAS 3",type="AS5300",isdnsigtype="N/A",group=0
Media Gateway Controller 2007-03-04 11:36:31
M COMPLD
"extnode"
;
Defines network access server NAS 3
as an external node.
Verifying the Added NAS External Nodes
To verify that you have entered the NASs, use the prov-rtrv:extnode command. For example, to verify
that you have added the first NAS:
machine-name mml> prov-rtrv:extnode:name="nas1"
Media Gateway Controller 2007-03-04 11:36:46
M RTRV
"session=ver1:extnode"
/*
NAME = nas1
DESC = NAS 1
TYPE = AS5300
ISDNSIGTYPE = N/A
GROUP = 0
*/
;
You can retrieve all the NAS external nodes using the prov-rtrv:extnode:"all" command, as shown in
Example 12.
Example 12
Retrieving All External Nodes
machine-name mml> prov-rtrv:extnode:"all"
Media Gateway Controller 2007-04-04 11:44:41
M RTRV
"session=ver1:extnode"
/*
NAME
TYPE
ISDNSIGTYPE
----------------itp-l-1
SLT
N/A
itp-l-2
SLT
N/A
nas1
AS5300
N/A
nas2
AS5300
N/A
nas3
AS5300
N/A
*/
Cisco PGW 2200 Signaling Mode Design Guide
36
GROUP
----0
0
0
0
0
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning NAS Links
;
Adding NAS Signaling Services
You must add a NAS signaling service for each NAS you created in the “Adding NAS External Nodes”
section on page 35. The NAS signaling service indicates the Q.931 protocol path between the PGW and
the NASs.
The shaded area in Figure 13 shows the NAS signaling services.
Figure 13
Adding NAS Signaling Services
LAN
switches
STP A 171.16.1
209.165.200.230
STP
STP
STP B 171.16.2
PSTN
switch
A
171.1.3
209.165.201.7
IMTs
NAS1
IMTs
NAS2
IMTs
171.1.4
PGW 2200
NAS3
QoS packet
network
Telephone
exchange
Gateway
router
280710
Cisco ITP-Ls
Cisco PGW 2200 Signaling Mode Design Guide
37
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning NAS Links
Command/Action
Purpose
Step 1
machine-name mml> prov-add:naspath:name="nassvc1",
extnode="nas1",desc="Signaling service for NAS
1",custgrpid="0000",sigslot=0,sigport=0
Media Gateway Controller 2007-03-04 11:40:11
M COMPLD
"naspath"
;
Adds the communications path
between the PGW and network access
server nas1.
Step 2
machine-name mml> prov-add:naspath:name="nassvc2",
extnode="nas2",desc="Signaling service for NAS
2",custgrpid="0000",sigslot=0,sigport=0
Media Gateway Controller 2007-03-04 11:41:07
M COMPLD
"naspath"
;
Adds the communications path
between the PGW and network access
server nas2.
Step 3
machine-name mml> prov-add:naspath:name="nassvc3",
extnode="nas3",desc="Signaling service for NAS
3",custgrpid="0000",sigslot=0,sigport=0
Media Gateway Controller 2007-03-04 11:41:49
M COMPLD
"naspath"
;
Adds the communications path
between the PGW and network access
server nas3.
Verifying the Added NAS Signaling Services
To verify that you have entered the NAS signaling services, use the prov-rtrv:naspath command. For
example, to verify that the first NAS signaling service was added:
va-testing mml> prov-rtrv:naspath:name="nassvc1"
Media Gateway Controller 2007-03-04 11:42:36
M RTRV
"session=ver1:naspath"
/*
NAME = nassvc1
DESC = Signaling service for NAS 1
EXTNODE = nas1
MDO = BELL_1268_C2
CUSTGRPID = 0000
SIGSLOT = 0
SIGPORT = 0
*/
;
You can retrieve all the NAS signaling services using the prov-rtrv:naspath:"all" command, as shown
in Example 13.
Example 13
Retrieving All the NAS Signaling Services
machine-name mml> prov-rtrv:naspath:"all"
Media Gateway Controller 2007-04-04 11:49:02
M RTRV
"session=ver1:naspath"
/*
NAME
EXTNODE
MDO
-----------nassvc1
nas1
BELL_1268_C2
nassvc2
nas2
BELL_1268_C2
Cisco PGW 2200 Signaling Mode Design Guide
38
CUSTGRPID
--------0000
0000
SIGSLOT
------0
0
SIGPORT
------0
0
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning NAS Links
nassvc3
*/
;
nas3
BELL_1268_C2
0000
0
0
Adding IP Links
You must add an IP link from each NAS to PGW. In this example, you provision the following IP links:
NAS 1 to PGW
•
NAS 2 to PGW
•
NAS 3 to PGW
If you are provisioning two links from the PGW to the same NAS, you need two different Ethernet IP
addresses on both the PGW and the NAS, for a total of four new addresses.
The shaded area in Figure 14 shows the links you are adding in this example.
Figure 14
Adding IP Links
LAN
switches
STP A 171.16.1
209.30.200.250
209.30.201.15
209.165.200.230
STP
Cisco ITP-Ls
STP
STP B 171.16.2
PSTN
switch
A
171.1.3
209.165.201.7
IMTs
NAS1
IMTs
NAS2
IMTs
171.1.4
PGW 2200
NAS3
QoS packet
network
Telephone
exchange
Gateway
router
280709
Note
•
Cisco PGW 2200 Signaling Mode Design Guide
39
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning NAS Links
Command/Action
Purpose
Step 1
machine-name mml> prov-add:iplnk:name="nas1link1",
ipaddr="IP_Addr1",port=3001,peeraddr="209.165.200.22
5",peerport=3001,svc="nassvc1",desc="IP link for NAS
1 to PGW"
Media Gateway Controller 2007-03-04 11:48:54
M COMPLD
"iplnk"
;
Defines IP link nas1link1 between the
PGW and network access server nas1
for the previously defined NAS
signaling service nassvc1.
Step 2
machine-name mml> prov-add:iplnk:name="nas1link2",
ipaddr="IP_Addr2",port=3001,peeraddr="209.165.201.1"
,peerport=3001,svc="nassvc2",desc="IP link 2 for NAS
1 to PGW"
Media Gateway Controller 2007-03-04 11:50:24
M COMPLD
"iplnk"
;
Defines IP link nas1link2 between the
PGW and network access server nas1
for the previously defined NAS
signaling service nassvc1.
Step 3
machine-name mml> prov-add:iplnk:name="nas2link1",
ipaddr="IP_Addr1",port=3001,peeraddr="209.165.200.22
6",peerport=3001,svc="nassvc2",desc="IP link 1 for
NAS 2 to PGW"
Media Gateway Controller 2007-03-04 11:51:35
M COMPLD
"iplnk"
;
Defines IP link nas2link1 between the
PGW and network access server nas2
for the previously defined NAS
signaling service nassvc2.
Step 4
machine-name mml> prov-add:iplnk:name="nas2link2",
ipaddr="IP_Addr2",port=3001,peeraddr="209.165.201.2"
,peerport=3001,svc="nassvc2",desc="IP link 2 for NAS
2 to PGW"
Media Gateway Controller 2007-03-04 11:53:17
M COMPLD
"iplnk"
;
Defines IP link nas2link2 between the
PGW and network access server nas2
for the previously defined NAS
signaling service nassvc2.
Step 5
machine-name mml> prov-add:iplnk:name="nas3link1",
ipaddr="IP_Addr1",port=3001,peeraddr="209.165.200.22
7",peerport=3001,svc="nassvc3",desc="IP link 1 for
NAS 3 to PGW"
Media Gateway Controller 2007-03-04 11:54:20
M COMPLD
"iplnk"
;
Defines IP link nas3link1 between the
PGW and network access server nas3
for the previously defined NAS
signaling service nassvc3.
Step 6
machine-name mml> prov-add:iplnk:name="nas3link2",
ipaddr="IP_Addr2",port=3001,peeraddr="209.165.201.3"
,peerport=3001,svc="nassvc3",desc="IP link 2 for NAS
3 to PGW"
Media Gateway Controller 2007-03-04 11:55:33
M COMPLD
"iplnk"
;
Defines IP link nas3link2 between the
PGW and network access server nas3
for the previously defined NAS
signaling service nassvc3.
Verifying the Added IP Links
To verify that you have entered the IP links, use the prov-rtrv:iplnk command:
va-testing mml> prov-rtrv:iplnk:name="nas1link1"
Media Gateway Controller 2007-03-04 12:01:23
M RTRV
Cisco PGW 2200 Signaling Mode Design Guide
40
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Trunks
"session=ver1:iplnk"
/*
NAME = nas1link1
DESC = IP link for NAS 1 to PGW
SVC = nassvc1
IPADDR = IP_Addr1
PORT = 3001
PEERADDR = 209.165.200.225
PEERPORT = 3001
PRI = 1
IPROUTE = 0
*/
;
You can retrieve all the IP links by entering the prov-rtrv:iplnk:"all" command, as shown in
Example 14.
Example 14
Retrieving All the IP Links
machine-name mml> prov-rtrv:iplnk:"all"
Media Gateway Controller 2007-04-04 12:05:43
M RTRV
"session=ver1:iplnk"
/*
NAME
SVC
IPADDR
PORT
PEERADDR
PEERPORT
---------------------------nas1link1
nassvc1 IP_Addr1 3001
209.165.200.225 3001
nas1link2
nassvc1 IP_Addr2 3001
209.165.201.1 3001
nas2link1
nassvc2 IP_Addr1 3001
209.165.200.226 3001
nas2link2
nassvc2 IP_Addr2 3001
209.165.201.2 3001
nas3link1
nassvc3 IP_Addr1 3001
209.165.200.227 3001
nas3link2
nassvc3 IP_Addr2 3001
209.165.201.3 3001
*/
;
PRI
---
IPROUTE
------1
1
1
1
1
1
Provisioning Trunks
You must add trunks for each connection between the NAS and the PSTN switch. The shaded area in
Figure 15 shows the T1 lines from the NAS to the PSTN switch that terminate bearer traffic. NAS 1 has
four T1 lines, NAS 2 has four T1 lines, and NAS 3 has three T1 lines. Each T1 contains 24 trunks, or
DS0s. For the examples in this section, you must provision 264 trunks (96 for NAS1, 96 for NAS2, and
72 for NAS3).
Note
If you have already provisioned the spans on the NAS to be associated with these trunks, use the
shutdown command to remove these spans from service on the NAS before you provision the trunks on
the Cisco PGW 2200.
Cisco PGW 2200 Signaling Mode Design Guide
41
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Trunks
Figure 15
Adding Trunks
LAN
switches
STP A 171.16.1
209.165.200.230
171.1.4
STP
Cisco ITP-Ls
STP B 171.16.2
PSTN
switch
A
171.1.3
PGW 2200
209.165.201.7
IMTs
NAS1
IMTs
NAS2
IMTs
NAS3
QoS packet
network
Telephone
exchange
Gateway
router
280717
STP
You can add trunks using any of the following methods:
Tip
•
Importing a text file you create that contains all of your trunks
•
Adding trunks individually with an MML command
•
Adding up to 24 trunks for T1 lines or 31 trunks for E1 lines with an MML command
If you have a large number of trunks, use the text file method for adding trunks.
Using a Text File to Add Trunks
Using a text file to add trunks requires you to create a text file that contains the following fields:
•
Trunk ID—A unique identifier that maps to NAME (trunk ID).
•
Source Service Name—The signaling service that you created in the “Adding the SS7 Signaling
Service” section on page 24; it is used to look up SRCSVC.
•
Source Span ID—Maps to SRCSPAN. (The value in the field is converted from decimal to
hexadecimal except when the value is ffff.)
Cisco PGW 2200 Signaling Mode Design Guide
42
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Trunks
Note
Note
For nailed trunks in the PGW, this value is always ffff.
•
Source Time Slot—Identifies the time slot on the T1 at the destination (PSTN switch). Maps to
SRCTIMESLOT. (The value in this field is converted from decimal to hexadecimal except when the
value is ffff.)
•
Destination Service Name—The signaling service for the NAS you created in the “Adding NAS
Signaling Services” section on page 37. It is used to look up DSTSVC.
•
Destination Span ID—The appropriate T1 line and T1 controller on the NAS. This value is the
nfas_int value that is set in IOS on the NAS. Maps to DSTSPAN. (The field in this column converted
from decimal to hex except when the value is ffff.)
The values used for destination span in the following examples are sample values. The real values for
this parameter would match whichever PRI port number the T1 is connected to on the NAS. Valid values
are 0 through 3.
•
Destination Time Slot—Identifies the time slot on the T1 that terminates at the NAS. Maps to
DSTTIMESLOT (converted from decimal to hexadecimal except when value is ffff)
The following example shows the trunk text file for the sample configuration in this chapter. The fields
in the text file correspond to the fields described above.
Example 15
Trunk Text File
#format2
100 ss7sigsvc
101 ss7sigsvc
102 ss7sigsvc
103 ss7sigsvc
104 ss7sigsvc
105 ss7sigsvc
106 ss7sigsvc
107 ss7sigsvc
108 ss7sigsvc
109 ss7sigsvc
110 ss7sigsvc
111 ss7sigsvc
112 ss7sigsvc
113 ss7sigsvc
114 ss7sigsvc
115 ss7sigsvc
116 ss7sigsvc
117 ss7sigsvc
118 ss7sigsvc
119 ss7sigsvc
120 ss7sigsvc
121 ss7sigsvc
122 ss7sigsvc
123 ss7sigsvc
124 ss7sigsvc
125 ss7sigsvc
126 ss7sigsvc
127 ss7sigsvc
128 ss7sigsvc
129 ss7sigsvc
130 ss7sigsvc
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
1 nassvc1 1 1
2 nassvc1 1 2
3 nassvc1 1 3
4 nassvc1 1 4
5 nassvc1 1 5
6 nassvc1 1 6
7 nassvc1 1 7
8 nassvc1 1 8
9 nassvc1 1 9
10 nassvc1 1 10
11 nassvc1 1 11
12 nassvc1 1 12
13 nassvc1 1 13
14 nassvc1 1 14
15 nassvc1 1 15
16 nassvc1 1 16
17 nassvc1 1 17
18 nassvc1 1 18
19 nassvc1 1 19
20 nassvc1 1 20
21 nassvc1 1 21
22 nassvc1 1 22
23 nassvc1 1 23
24 nassvc1 1 24
25 nassvc1 1 25
26 nassvc1 1 26
27 nassvc1 1 27
28 nassvc1 1 28
29 nassvc1 1 29
30 nassvc1 1 30
31 nassvc1 1 31
Cisco PGW 2200 Signaling Mode Design Guide
43
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Trunks
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc1
nassvc2
nassvc2
Cisco PGW 2200 Signaling Mode Design Guide
44
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
4
4
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
1
2
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Trunks
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
96 nassvc2 4 3
97 nassvc2 4 4
98 nassvc2 4 5
99 nassvc2 4 6
100 nassvc2 4 7
101 nassvc2 4 8
102 nassvc2 4 9
103 nassvc2 4 10
104 nassvc2 4 11
105 nassvc2 4 12
106 nassvc2 4 13
107 nassvc2 4 14
108 nassvc2 4 15
109 nassvc2 4 16
110 nassvc2 4 17
111 nassvc2 4 18
112 nassvc2 4 19
113 nassvc2 4 20
114 nassvc2 4 21
115 nassvc2 4 22
116 nassvc2 4 23
117 nassvc2 4 24
118 nassvc2 4 25
119 nassvc2 4 26
120 nassvc2 4 27
121 nassvc2 4 28
122 nassvc2 4 29
123 nassvc2 4 30
124 nassvc2 4 31
125 nassvc2 5 1
126 nassvc2 5 2
127 nassvc2 5 3
128 nassvc2 5 4
129 nassvc2 5 5
130 nassvc2 5 6
131 nassvc2 5 7
132 nassvc2 5 8
133 nassvc2 5 9
134 nassvc2 5 10
135 nassvc2 5 11
136 nassvc2 5 12
137 nassvc2 5 13
138 nassvc2 5 14
139 nassvc2 5 15
140 nassvc2 5 16
141 nassvc2 5 17
142 nassvc2 5 18
143 nassvc2 5 19
144 nassvc2 5 20
145 nassvc2 5 21
146 nassvc2 5 22
147 nassvc2 5 23
148 nassvc2 5 24
149 nassvc2 5 25
150 nassvc2 5 26
151 nassvc2 5 27
152 nassvc2 5 28
153 nassvc2 5 29
154 nassvc2 5 30
155 nassvc2 5 31
156 nassvc2 6 1
157 nassvc2 6 2
158 nassvc2 6 3
159 nassvc2 6 4
Cisco PGW 2200 Signaling Mode Design Guide
45
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Trunks
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc2
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
Cisco PGW 2200 Signaling Mode Design Guide
46
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
8
8
8
8
8
8
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
1
2
3
4
5
6
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Trunks
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ss7sigsvc
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
ffff
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
nassvc3
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
When your file is complete, save it in the /opt/CiscoMGC/etc/cust_specific directory using
filename.extension (for example, trunks.txt). Then use the prov-add:files command to load the table.
Caution
When you import a trunk file, all the existing bearer channels are replaced by the bearer channels that
you import.
Provisioning the Added Trunks
Use the following procedure to provision the trunks that you have added.
Command/Action
Purpose
Step 1
Use a text editor to create the trunk text file.
Provisions the fields needed for
creation of trunks.
Step 2
Save the file in /opt/CiscoMGC/etc/cust_specific.
Puts the file in the correct directory.
Step 3
Start a provisioning session. (See the “Starting the
Provisioning Session” section on page 9.)
Begins the session.
Step 4
Enter the prov-add:files command:
Imports a trunk or bearer channel file
(BCFile) called trunks.txt from the
machine-name mml>
prov-add:files:name="BCFile",file="trunks.txt",actio /opt/CiscoMGC/etc/cust_specific
n="import"
directory.
M
Media Gateway Controller 2007-03-04 13:16:43
COMPLD
"files"
;
Cisco PGW 2200 Signaling Mode Design Guide
47
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning Trunks
Verifying the Added Trunks
To verify that you have added the trunks, exit MML and change to the
/opt/CiscoMGC/etc/CONFIG_LIB/CFG_ver1 directory.
View the bearChan.dat file to ensure that it contains the trunk information from the trunks.txt file you
imported. The following example shows part of the bearChan.dat file:
machine-name% cd /opt/CiscoMGC/etc/CONFIG_LIB/CFG_ver1
machine-name% more bearChan.dat
100 00130002 ffff 1 00140001 2 1
101 00130002 ffff 2 00140001 2 2
102 00130002 ffff 3 00140001 2 3
103 00130002 ffff 4 00140001 2 4
104 00130002 ffff 5 00140001 2 5
105 00130002 ffff 6 00140001 2 6
106 00130002 ffff 7 00140001 2 7
107 00130002 ffff 8 00140001 2 8
108 00130002 ffff 9 00140001 2 9
109 00130002 ffff a 00140001 2 a
110 00130002 ffff b 00140001 2 b
111 00130002 ffff c 00140001 2 c
112 00130002 ffff d 00140001 2 d
113 00130002 ffff e 00140001 2 e
114 00130002 ffff f 00140001 2 f
115 00130002 ffff 10 00140001 2 10
116 00130002 ffff 11 00140001 2 11
117 00130002 ffff 12 00140001 2 12
118 00130002 ffff 13 00140001 2 13
119 00130002 ffff 14 00140001 2 14
120 00130002 ffff 15 00140001 2 15
<Press ‘SPACE’ for next page, ‘Enter’ for next line or ‘q’ to quit this output>
You can retrieve all the trunks using the prov-rtrv:nailedtrnk:"all" command:
machine-name mml> prov-rtrv:nailedtrnk:"all"
Media Gateway Controller 2007-04-04 16:55:03
M RTRV
"session=active:nailedtrnk"
/*
NAME
SRCSVC
SRCSPAN SRCTIMESLOT(CIC) DSTSVC
-------------- ---------------- -----100
ss7sigsvc ffff
1
nassvc1
101
ss7sigsvc ffff
2
nassvc1
102
ss7sigsvc ffff
3
nassvc1
103
ss7sigsvc ffff
4
nassvc1
104
ss7sigsvc ffff
5
nassvc1
105
ss7sigsvc ffff
6
nassvc1
106
ss7sigsvc ffff
7
nassvc1
107
ss7sigsvc ffff
8
nassvc1
108
ss7sigsvc ffff
9
nassvc1
109
ss7sigsvc ffff
10
nassvc1
110
ss7sigsvc ffff
11
nassvc1
111
ss7sigsvc ffff
12
nassvc1
112
ss7sigsvc ffff
13
nassvc1
113
ss7sigsvc ffff
14
nassvc1
114
ss7sigsvc ffff
15
nassvc1
DSTSPAN
------2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
DSTTIMESLOT(CIC)
--------------1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
<Press ‘SPACE’ for next page, ‘Enter’ for next line or ‘q’ to quit this output>
*/
;
Cisco PGW 2200 Signaling Mode Design Guide
48
Cisco PGW 2200 Signaling Mode Design Guide
Provisioning the Dial Plan/Number Analysis
Adding a Nailed Trunk
Although you can add individual trunks with MML, doing so is not recommended if you have a large
number of trunks to add. Using MML to add trunks requires that you enter the command to add
individual trunks for each of the 264 trunks that you need to provision.
You can add multiple trunks for a T1 or E1. See the following procedures for more information.
To add individual trunks:
Command/Action
Purpose
Step 1
mml>prov-add:nailedtrnk:name="100",
srcsvc="ss7sigsvc1",srctimeslot="1",
dstsvc="nassvc1",dstspan="2",dsttimeslot="1"
Adds a nailed trunk named “100” whose source
and destination services are both defined at the
NAS.
Note
Adding individual trunks using this command requires that you perform this action 24 times for each T1.
To add multiple trunks:
Command/Action
Purpose
Step 1
mml>prov-add:nailedtrnk:name="100",
srcsvc="ss7svc1",srctimeslot="1",
dstsvc="nassvc1",dstspan="2",dsttimeslot="1"
,spansize=24
Adds 24 nailed trunks starting from “100”
whose source and destination services are both
defined at the NAS. For an E1, use a spansize
value of 31.
Note
If you have already provisioned the spans on the NAS to be associated with these trunks, you can now
return those spans to service on the NAS using the no shutdown command.
Provisioning the Dial Plan/Number Analysis
The PGW enables you to create a dial plan to perform number analysis on both the A (calling) number
and B (called) number. You can set up dial plans to perform routing, send calls to announcement servers,
modify dialed digits, and perform other analyses.
You do not use the advanced features in the dial plan for the Cisco SS7 Interconnect for Access Servers
Solution and the Cisco SS7 Interconnect for Voice Gateways Solution. In these solutions, the PGW
routes calls directly over the IP network and does not perform routing or switching to trunk groups.
Provisioning White and Black List Screening
In the Cisco SS7 Interconnect for Access Servers Solution, you might want to perform white and black
list screening to include or exclude calls from certain numbers. You can provision white lists that specify
allowed A-numbers (calling numbers) or B-numbers (called numbers). Black lists block specified
A-numbers (calling numbers) or B-numbers (called numbers).
Cisco PGW 2200 Signaling Mode Design Guide
49
Cisco PGW 2200 Signaling Mode Design Guide
Deploying the Session
For information on using MML to provision black and white list screening, see Chapter 5, “Adding
System Components with MML,” in the Cisco Media Gateway Controller Software Release 9
Provisioning Guide at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/provisioning/guide/R9MMLChg.html.
Deploying the Session
The configuration example used in this document features a continuous-service SC node. You must
deploy the session to save it to the machine you are provisioning. The system then copies the files to the
standby PGW.
Tip
If you receive an error while trying to deploy, your connection between the active and standby PGWs
might be configured improperly. The communication between the active and standby PGWs is
configured in the XECfgParm.dat file on each machine. See the “Configuring the Execution
Environment” section in Chapter 4 of the Cisco Media Gateway Controller Software Installation and
Configuration (Release 9.7) for more information. That document is located at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/installation/software/SW1/3ins_cfg.html.
Deployment Procedure
Command/Action
Purpose
Step 1
machine-name mml> prov-dply
Media Gateway Controller - VSC-01 2007-03-04
13:48:19
M COMPLD
"PROV-DPLY"
;
Saves the provisioning session as active
and copies it to the standby PGW.
Note
Restart the standby PGW after reconfiguration to apply changes.
Note
Use the command prov-cpy to deploy the configuration if your PGW is standalone. This command
makes the provisioning session active and automatically stops the provisioning session.
Deployment Verification
To verify that you have deployed the configuration, use the prov-rtrv:all command and verify that the
active configuration shown is the one you provisioned. Here is the system output for the configuration
example used in this document.
machine-name mml> prov-rtrv:all
Media Gateway Controller - VSC-01 2007-03-04 13:50:06
M RTRV
"session=active:all"
/*
NAME
COMPID
Parent Name TID
Cisco PGW 2200 Signaling Mode Design Guide
50
Description
Cisco PGW 2200 Signaling Mode Design Guide
Creating and Processing an MML Batch File for Provisioning
---"ls01"
"ls02"
"nas1link1"
"nas1link2"
"nas2link1"
"nas2link2"
"nas3link1"
"nas3link2"
"ss7route1"
through LS01"
"ss7route2"
through LS02"
"opc"
"dpc1"
"nassvc1"
"nassvc2"
-------00080001
00080002
00100001
00100002
00100003
00100004
00100005
00100006
00110001
----------"apc1"
"apc2"
"nassvc1"
"nassvc1"
"nassvc2"
"nassvc2"
"nassvc3"
"nassvc3"
"mgc-01"
--LNKSET
LNKSET
IPLNK
IPLNK
IPLNK
IPLNK
IPLNK
IPLNK
SS7ROUTE
----------"Linkset from PGW to STP A"
"Linkset from PGW to STP B"
"IP link 1 to NAS 1"
"IP link 2 to NAS 1"
"IP link 1 to NAS 2"
"IP link 2 to NAS 2"
"IP link 1 to NAS 3"
"IP link 2 to NAS 3"
"Route 1 to PSTN Switch A
00110002
"mgc-01"
SS7ROUTE
"Route 1 to PSTN Switch A
00130001
00130002
00140001
00140002
"mgc-01"
"mgc-01"
"nas1"
"nas2"
OPC
DPC
NASPATH
NASPATH
"origination point code"
"DPC of PSTN Switch A"
Signaling service for NAS 1"
Signaling service for NAS 2"
<Press 'SPACE' for next page, 'Enter' for next line or 'q' to quit this output>
"nassvc3"
00140003 "nas3"
NASPATH
"Signaling service for NAS 3"
"ss7sigsvc"
00150001 "dpc1"
SS7PATH
"SS7 Signaling Patch to PSTN
Switch A"
"itp-l-1"
00160001 "mgc-01"
EXTNODE
"External Node itp-l-1"
"itp-l-2"
00160002 "mgc-01"
EXTNODE
"External Node itp-l-2
"nas1"
00160003 "mgc-01"
EXTNODE
"NAS 1"
"nas2"
00160004 "mgc-01"
EXTNODE
"NAS 2"
"nas3"
00160005 "mgc-01"
EXTNODE
"NAS 3"
"c7iplink1"
001d0001 "ls01"
C7IPLNK
"C7IPlink-1 in ls 1"
"c7iplink2"
001d0002 "ls01"
C7IPLNK
"C7IPlink-2 in ls 1"
"c7iplink3"
001d0003 "ls02"
C7IPLNK
"C7IPlink-3 in ls 2"
"c7iplink4"
001d0004 "ls02"
C7IPLNK
"C7IPlink-4 in ls 2"
"apc1"
001e0001 "mgc-01"
APC
"APC for STP A"
"apc2"
001e0002 "mgc-01"
APC
"APC for STP B"
"subsys1"
001f0001 "mgc-01"
SS7SUBSYS
"Mating STP A to STP B"
"subsys2"
001f0002 "mgc-01"
SS7SUBSYS
"Mating STP B and STP A"
"sessionset-1-1"
00480001 "itp-l-1"
SESSIONSET
"Session Set sessionset-1
Backhaul Link 1"
"sessionset-1-2"
00480002 "itp-l-1"
SESSIONSET
"Session Set sessionset-1
Backhaul Link 2"
"sessionset-2-1"
00480003 "itp-l-2"
SESSIONSET
"Session Set sessionset-2
Backhaul Link 1"
"sessionset-2-2"
00480004 "itp-l-2"
SESSIONSET
"Session Set sessionset-2
Backhaul Link 2"
"iproute-1-to-itp-l-1" 004b0001 "mgc-01"
IPROUTE
"First IP route to itp-l-1"
<Press 'SPACE' for next
"iproute-1-to-itp-l-2"
"iproute-2-to-itp-l-1"
"iproute-2-to-itp-l-2"
*/
;
page, 'Enter' for next
004b0002 "mgc-01"
004b0003 "mgc-01"
004b0004 "mgc-01"
line or 'q' to quit this output>
IPROUTE
"First IP route to itp-l-2"
IPROUTE
"Second IP route to itp-l-1"
IPROUTE
"Second IP route to itp-l-2"
Creating and Processing an MML Batch File for Provisioning
You can create a file of MML provisioning commands for use as a batch file. All commands are in a
single ASCII text file; when they are read by MML, the commands are executed sequentially.
Cisco PGW 2200 Signaling Mode Design Guide
51
Cisco PGW 2200 Signaling Mode Design Guide
Creating and Processing an MML Batch File for Provisioning
Note
It is important that the MML provisioning commands be in the correct provisioning sequence. That
sequence is dictated by component dependencies. For example, you need to add the OPC, the DPC, and
APCs before you add linksets.
If you use an MML batch file, you can cut and paste commands, and you can use the batch files
repeatedly to “reprovision” the PGW or to quickly provision multiple PGWs. However, if you intend to
run the batch file multiple times on the same host, plan the source and destination directories carefully.
Tip
You can create batch files to define complete systems or modify parts of an existing system.
Creating the File
To create a batch file, use an ASCII text editor to create a new file with one MML command on each
line, ending with a carriage return. You can use any name for the file (follow UNIX file naming
conventions), and you can store it in any location. However, the file must be accessible to the machine
where you run MML sessions. The following example shows a sample MML batch file for the
configuration in this chapter.
Example 16
Sample MML Provisioning Batch File
prov-sta::srcver=”new”,dstver=”ver1”
prov-add:opc:name=”opc”,netaddr=”171.1.4”,netind=2,type=”trueopc”,desc="origination point
code"
prov-add:dpc:name=”dpc1”,netaddr=”171.1.3”,netind=2,desc=”DPC of PSTN Switch A”
prov-add:apc:name="apc1",netaddr="171.16.1",desc="APC for STP A"
prov-add:apc:name="apc2",netaddr="171.16.2",desc="APC for STP B"
prov-add:lnkset:name="ls01",apc="apc1",type="IP",proto="SS7-ANSI",desc="Linkset from PGW
to STP A"
prov-add:lnkset:name="ls02",apc="apc2",type="IP",proto="SS7-ANSI",desc="Linkset from PGW
to STP B"
prov-add:ss7route:name="ss7route1",opc="opc",dpc="dpc1",lnkset="ls01",pri=1,desc="Route 1
to PSTN Switch A through LS1"
prov-add:ss7route:name="ss7route2",opc="opc",dpc="dpc1",lnkset="ls02",pri=1,desc="Route 2
to PSTN Switch A through LS2"
prov-add:ss7subsys:name="subsys1",desc="Mate STP A to STP B", svc=”apc1”,proto=”SS7-ANSI”,
matedapc=”apc2”,pri=3,opc=”opc”
prov-add:ss7subsys:name="subsys2",desc="Mate STP B to STP A", svc=”apc2”,proto=”SS7-ANSI”,
matedapc=”apc1”,pri=3,opc=”opc”
prov-add:ss7path:name="ss7sigsvc",mdo="ANSISS7_STANDARD",opc=”opc”,dpc="dpc1",custgrpid=”d
125”,desc="SS7 signaling path to PSTN Switch A"
prov-add:extnode:name="itp-l-1",desc="External Node itp-l-1",type=”SLT”,
isdnsigtype=”N/A”, group=0
prov-add:extnode:name="itp-l-2",desc="External Node itp-l-2",type=”SLT”,
isdnsigtype=”N/A”, group=0
prov-add:iproute:name="iproute-1-to-itp-l-1",desc="First IP Route to itp-l-1",
dest="209.165.200.230",netmask="255.255.255.224",ipAddr="IP_Addr1",pri=1,
nexthop=”209.165.200.240”
prov-add:iproute:name="iproute-2-to-itp-l-1",desc=”Second IP Route to itp-l-1”,
dest="209.165.201.6",netmask="255.255.255.224",ipAddr="IP_Addr2",pri=1,
nexthop=”209.165.201.20”
prov-add:iproute:name="iproute-1-to-itp-l-2",desc="First IP Route to itp-l-2",
dest="209.165.200.231",netmask="255.255.255.224”,ipAddr="IP_Addr1",pri=1,
nexthop=”209.165.200.240”
prov-add:iproute:name="iproute-2-to-itp-l-2",desc="Second IP Route to itp-l-2",
dest="209.165.201.7",netmask="255.255.255.224”,ipAddr="IP_Addr2",pri=1,
Cisco PGW 2200 Signaling Mode Design Guide
52
Cisco PGW 2200 Signaling Mode Design Guide
Creating and Processing an MML Batch File for Provisioning
nexthop=”209.165.201.20”
prov-add:sessionset:name="sessionset-1",port=7000,peerAddr1=”209.165.200.230”,
peerAddr2=”209.165.201.6”,peerport=7000,ipAddr1=”IP_Addr1”,ipAddr2=”IP_Addr2”,
ipRoute1=”iproute-1-to-itp-l-1”,ipRoute2=”iproute-2-to-itp-l-1”,extnode=”itp-l-1”,type=”BS
MV0”
prov-add:sessionset:name="sessionset-2",port=7000,peerAddr1=”209.165.200.231”,
peerAddr2=”209.165.201.7”,peerport=7000,ipAddr1=”IP_Addr1”,ipAddr2=”IP_Addr2”,
ipRoute1=”iproute-1-to-itp-l-2”, ipRoute2=”iproute-2-to-itp-l-2”,
extnode=”itp-l-2”,type=”BSMV0”
prov-add:c7iplnk:name="c7iplink1",desc=”C7IPlink-1 in ls 1”,pri=1,slc=0,lnkset=”ls01”,
sessionset=”sessionset-1”,timeslot=0
prov-add:c7iplnk:name="c7iplink2",desc=”C7IPlink-2 in ls 1”,pri=1,slc=1,lnkset=”ls01”,
sessionset=”sessionset-2”,timeslot=0
prov-add:c7iplnk:name="c7iplink3",desc=”C7IPlink-3 in ls 2”,pri=1,slc=0,lnkset=”ls02”,
sessionset=”sessionset-1”,timeslot=0
prov-add:c7iplnk:name="c7iplink4",desc=”C7IPlink-4 in ls 2”,pri=1,slc=1,lnkset=”ls02”,
sessionset=”sessionset-2”,timeslot=0
prov-add:extnode:name="nas1",desc="NAS 1",type=”AS5300”,isdnsigtype=”N/A”,group=0
prov-add:extnode:name="nas2",desc="NAS 2",type=”AS5300”,isdnsigtype=”N/A”,group=0
prov-add:extnode:name="nas3",desc="NAS 3",type=”AS5300”,isdnsigtype=”N/A”,group=0
prov-add:naspath:name="nassvc1",extnode="nas1",desc=”Signaling service for NAS
1”,custgrpid=”0000”,sigslot=0,sigport=0
prov-add:naspath:name="nassvc2",extnode="nas2",desc="Signaling service for NAS
2",custgrpid=”0000”,sigslot=0,sigport=0
prov-add:naspath:name="nassvc3",extnode="nas3",desc="Signaling service for NAS
3",custgrpid=”0000”,sigslot=0,sigport=0
prov-add:iplnk:name="nas1link1",ipaddr="IP_Addr1",port=3001,peeraddr="209.165.200.225",pee
rport=3001, svc="nassvc1",desc="IP link 1 for NAS 1 to PGW"
prov-add:iplnk:name="nas1link2",ipaddr="IP_Addr2",port=3001,peeraddr="209.165.201.1",peerp
ort=3001, svc="nassvc1",desc="IP link 2 for NAS 1 to PGW"
prov-add:iplnk:name="nas2link1",ipaddr="IP_Addr1",port=3001,peeraddr="209.165.200.226",pee
rport=3001, svc="nassvc2",desc="IP link 1 for NAS 2 to PGW"
prov-add:iplnk:name="nas2link2",ipaddr="IP_Addr2",port=3001,peeraddr="209.165.201.2",peerp
ort=3001, svc="nassvc2",desc="IP link 2 for NAS 2 to PGW"
prov-add:iplnk:name="nas3link1",ipaddr="IP_Addr1",port=3001,peeraddr="209.165.200.227",pee
rport=3001, svc="nassvc3",desc="IP link 1 for NAS 3 to PGW"
prov-add:iplnk:name="nas3link2",ipaddr="IP_Addr2",port=3001,peeraddr="209.165.201.3",peerp
ort=3001, svc="nassvc3",desc="IP link 2 for NAS 3 to PGW"
numan-add:dialplan:custgrpid="t778"
numan-add:awhite:custgrpid="t778",cli="7034843000"
numan-dlt:awhite:custgrpid="t778",cli="7034843001"
prov-cpy
The first command starts a provisioning session, and the last command terminates and commits the
provisioning session. If you are not ready to commit a session, use the prov-stp command to save and
stop the provisioning session.
The prov-cpy or prov-dply command makes the provisioning session active and automatically stops the
provisioning session. The prov-dply command also copies it to the standby PGW.
Processing the File
To process the batch file, use the mml -b path/filename UNIX command.
Cisco PGW 2200 Signaling Mode Design Guide
53
Cisco PGW 2200 Signaling Mode Design Guide
Creating and Processing an MML Batch File for Provisioning
Step 1
Command/Action
Purpose
mml -b path/filename
Processes the MML commands in the batch file.
Use the absolute path to the file as the path
parameter, and use the filename of the batch file
containing the provisioning commands as the
filename parameter. Be sure to include the file
extension; for example, dial1.txt.
Verifying the Deployment
After you enter the command, MML displays the result of each command as it is executed. When the
batch file is done, the MML session is closed.
To verify that you have deployed the configuration, log in and begin an MML session. Enter the
prov-rtrv:all command and verify that the active configuration shown is the one you provisioned.
Tip
MML provides a log function that records the MML commands and responses for you in a log file. If
you start this function before you start the provisioning session and stop it after you stop the provisioning
session, you can let the batch file run unattended and then check the log file later for any error messages.
The log command is diaglog. For more information on using this command, see the Cisco Media
Gateway Controller Software Release 9 MML Command Reference at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/command/reference/mmlref_1.html.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are
trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To
You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS,
Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch,
Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo,
iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers,
Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert,
StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of
Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply
a partnership relationship between Cisco and any other company. (0805R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and
figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and
coincidental.
© 2008 Cisco Systems, Inc. All rights reserved.
Cisco PGW 2200 Signaling Mode Design Guide
54