Guest

Cisco PGW 2200 Softswitch

Cisco PGW 2200 Signaling Mode Design Guide

  • Viewing Options

  • PDF (925.1 KB)
  • Feedback
Cisco PGW 2200 Signaling Mode Design Guide

Table Of Contents

Cisco PGW 2200 Signaling Mode Design Guide

Provisioning Outline

Provisioning Worksheet

Starting the Provisioning Session

MML Tips

Provisioning SS7 Signaling Routes

Adding the OPC

Verifying the Added OPC

Adding the DPC

Verifying the Added DPC

Adding the APCs

Verifying the Added APCs

Adding Linksets

Verifying the Added Linksets

Adding SS7 Routes

Verifying the Added SS7 Routes

Adding the SS7 Subsystem

Verifying the Added SS7 Subsystem

Adding the SS7 Signaling Service

Verifying the Added SS7 Signaling Service

Provisioning Signaling Links

Adding ITP-L External Nodes

Verifying the Added ITP-L External Nodes

Adding IP Routes to Cisco ITP-Ls (Optional)

Verifying the Added IP Routes to Cisco ITP-Ls

Adding Sessionsets for PGW-ITP-L Communication

Verifying the Added Sessionsets

Adding C7 IP Links to Cisco ITP-Ls

Verifying the Added C7 IP Links

Provisioning NAS Links

Adding NAS External Nodes

Verifying the Added NAS External Nodes

Adding NAS Signaling Services

Verifying the Added NAS Signaling Services

Adding IP Links

Verifying the Added IP Links

Provisioning Trunks

Using a Text File to Add Trunks

Provisioning the Added Trunks

Verifying the Added Trunks

Adding a Nailed Trunk

Provisioning the Dial Plan/Number Analysis

Provisioning White and Black List Screening

Deploying the Session

Deployment Procedure

Deployment Verification

Creating and Processing an MML Batch File for Provisioning

Creating the File

Processing the File

Verifying the Deployment


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.

Figure 1 shows an overview of Cisco PGW 2200 signaling mode solution.

Figure 1 PGW 2200 Signaling Mode Solution

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 

Add the OPC1 in your network.

Adding the OPC

Step 2 

Add the DPC2 to identify the destination switch.

Adding the DPC

Step 3 

Add the APCs3 to identify the STPs4 with which the signaling controller communicates signaling information.

Adding the APCs

Step 4 

Add linksets to connect the Cisco ITP-Ls5 to the STPs.

Adding Linksets

Step 5 

Add the SS7 subsystem to identify the mated STPs.

Adding the SS7 Subsystem

Step 6 

Add the SS7 routes for each signaling path from the signaling controller to the destination switch.

Adding the SS7 Signaling Service

Step 7 

Add the SS7 signaling service from the PGW to the destination switch.

Adding the SS7 Signaling Service

Provision signaling links

Step 1 

Add the external nodes for Cisco ITP-Ls.

Adding ITP-L External Nodes

Step 2 

(Optional) Add IP routes.

Adding IP Routes to Cisco ITP-Ls (Optional)

Step 3 

Add sessionsets for PGW-ITP-L communication.

Adding Sessionsets for PGW-ITP-L Communication

Step 4 

Add C7 IP Links to Cisco ITP-Ls

Adding C7 IP Links to Cisco ITP-Ls

Provision NAS6 links

Step 1 

Add external nodes for the NASes in your network.

Adding NAS External Nodes

Step 2 

Add NAS signaling services for each NAS.

Adding NAS Signaling Services

Step 3 

Add IP links for each NAS to PGW.

Adding IP Links

Provision trunks

Step 1 

Create the trunk file and add trunks from each NAS to the signaling controller.

Using a Text File to Add Trunks

Step 2 

Import the trunk file.

Using a Text File to Add Trunks

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.

Table 1 Provisioning Worksheet 

Component
MML Name
Description
Parameters

OPC

opc

Origination point code

netaddr: 171.1.4

netind: 2 (national network)

type:trueopc

DPC

dpc1

DPC of PSTN Switch A

netaddr: 171.1.3

netind: 2 (national network)

APC

apc1

APC for STP A

netaddr: 171.16.1

netind: 2 (national network)

APC

apc2

APC for STP B

netaddr: 171.16.2

netind: 2 (national network)

Linkset

ls01

Linkset from signaling controller to STP A

apc: apc1

type: IP

proto: SS7-ANSI

Linkset

ls02

Linkset from signaling controller to STP B

apc: apc2

type: IP

proto: SS7-ANSI

SS7 route

ss7route1

Route 1 to PSTN Switch A through LS1

opc: opc

dpc: dpc1

lnkset: ls01

pri: 1

SS7 route

ss7route2

Route 2 to PSTN Switch A through LS2

opc: opc

dpc: dpc1

lnkset: ls02

pri: 1

SS7 subsystem

subsys1

Mate STP A to STP B

svc: apc1

matedapc: apc2

proto: SS7-ANSI

pri: 3

opc: opc

SS7 subsystem

subsys2

Mate STP B to STP A

svc: apc2

matedapc: apc1

proto: SS7-ANSI

pri: 3

opc: opc

SS7 signaling service

ss7sigsvc

SS7 signaling path to PSTN Switch A

mdo: ANSISS7_STANDARD

opc: opc

dpc: dpc1

custgrpid: d125

ITP-L external node

itp-l-1

External node ITP-L-1

type: SLT

isdnsigtype: N/A

group: 0

ITP-L external node

itp-l-2

External node ITP-L-2

type: SLT

isdnsigtype: N/A

group: 0

(Optional) ITP-L IP route

iproute-1-to-itp-l-1

IP route 1 from PGW to 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 IP route

iproute-2-to-itp-l-1

IP route 2 from PGW to 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 IP route

iproute-1-to-itp-l-2

IP route 1 from PGW to 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

(Optional) ITP-L IP route

iproute-2-to-itp-l-2

IP route 2 from PGW to 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

sessionset-1

Sessionset for itp-l-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

Sessionset

sessionset-2

Sessionset for itp-l-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

C7 IP link

c7iplink1

Link 1 in Linkset 1

pri: 1

slc: 0

lnkset: ls01

sessionset: sessionset-1

timeslot: 0

C7 IP link

c7iplink2

Link 2 in Linkset 1

pri: 1

slc: 1

lnkset: ls01

sessionset: sessionset-2

timeslot: 0

C7 IP link

c7iplink3

Link 1 in Linkset 2

pri: 1

slc: 0

lnkset: ls02

sessionset: sessionset-1

timeslot: 0

C7 IP link

c7iplink4

Link 2 in Linkset 2

pri: 1

slc: 1

lnkset: ls02

sessioinset: sessionset-2

timeslot: 0

NAS external node

nas1

NAS 1

type: AS5300

isdnsigtype: N/A

group: 0

NAS external node

nas2

NAS 2

type: AS5300

isdnsigtype: N/A

group: 0

NAS external node

nas3

NAS 3

type: AS5300

isdnsigtype: N/A

group: 0

NAS signaling service

nassvc1

Signaling service for
NAS 1

extnode: nas1

MDO: BELL_1268_C2

NAS signaling service

nassvc2

Signaling service for
NAS 2

extnode: nas2

MDO: BELL_1268_C2

NAS signaling service

nassvc3

Signaling service for
NAS 3

extnode: nas3

MDO: BELL_1268_C2

IP link

nas1link1

IP link 1 for NAS 1

svc: nassvc1

ipaddr: IP_Addr1

port: 3001

peeraddr: 209.165.200.225

peerport: 3001

pri: 1

IP link

nas1link2

IP link 2 for NAS 1

svc: nassvc1

ipaddr: IP_Addr2

port: 3001

peeraddr: 209.165.201.1

peerport: 3001

pri: 1

IP link

nas2link1

IP link 1 for NAS 2

svc: nassvc2

ipaddr: IP_Addr1

port: 3001

peeraddr: 209.165.200.226

peerport: 3001

pri: 1

IP link

nas2link2

IP link 2 for NAS 2

svc: nassvc2

ipaddr: IP_Addr2

port: 3001

peeraddr: 209.165.201.2

peerport: 3001

pri: 1

IP link

nas3link1

IP link 1 for NAS 3

svc: nassvc3

ipaddr: IP_Addr1

port: 3001

peeraddr: 209.165.200.227

peerport: 3001

pri: 1

IP link

nas3link2

IP link 2 for NAS 3

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"
   Media Gateway Controller 2007-04-04 15:00:57
M  COMPLD
   "PROV-STA"
   ;
machine-name mml> 

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]

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.


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.

Figure 2 Adding the OPC

 
Command/Action
Purpose

Step 1 

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
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.

Figure 3 Adding the DPC

 
Command/Action
Purpose

Step 1 

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
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.


Figure 4 Adding the APCs

 
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
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.

Figure 5 Adding Linksets

 
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.

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       TYPE
----                  ---                   -----       ----
ls01                  apc1                  SS7-ANSI    IP
ls02                  apc2                  SS7-ANSI    IP
   */
   ; 


Note 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.


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.

Figure 6 Adding SS7 Routes

 
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).

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).

Figure 7 Adding the SS7 Subsystem

 
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.

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 TRANSPROTO OPC SUAKEY REMOTESSN
----    ---  --- -------- -------- -----    --------- ---------- --- ------ ---------
subsys1 apc1 3   apc2     0        SS7-ANSI 0         SCCP       opc        0
subsys2 apc2 3   apc1     0        SS7-ANSI 0         SCCP       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.

Figure 8 Adding the SS7 Signaling Service

 
Command/Action
Purpose

Step 1 

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.


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.

Figure 9 Adding ITP-L External Nodes

 
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:

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       GROUP
----                  ----         -----------       -----
itp-l-1               SLT          N/A               0
itp-l-2               SLT          N/A               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.

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
   "session=ver1:iproute"
   /* 
NAME                  DEST            NETMASk         NEXTHOP          IPADDR   PRIORITY 
----                  --------------- --------------- -----------      -------  --------
iproute-1-to-itp-l-1  209.165.200.230 255.255.255.224 209.165.200.240  IP_Addr1 1
iproute-1-to-itp-l-2  209.165.200.231 255.255.255.224 209.165.200.240  IP_Addr1 1
iproute-2-to-itp-l-1  209.165.201.6   255.255.255.224 209.165.201.20   IP_Addr2 1
iproute-2-to-itp-l-2  209.165.201.7   255.255.255.224 209.165.201.20   IP_Addr2 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

 
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.

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 PEERADDR        PEERPORT TYPE  IPROUTE
----         -------------   ------- ------   ---- ----------      -------- ----  
----------- 
sessionset-1 sessionset-1-1  itp-l-1 IP_Addr1 7000 209.165.200.230 7000     BSMV0 
[iproute-1-to-itp-l-1]
sessionset-1 sessionset-1-2  itp-l-1 IP_Addr2 7000 209.165.201.6   7000     BSMV0 
[iproute-2-to-itp-l-1]
sessionset-2 sessionset-2-1  itp-l-2 IP_Addr1 7000 209.165.200.231 7000     BSMV0 
[iproute-1-to-itp-l-2]
sessionset-2 sessionset-2-2  itp-l-2 IP_Addr2 7000 209.165.201.7   7000     BSMV0 
[iproute-2-to-itp-l-2]
   */
   ;

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. The shaded area in Figure 11 shows the C7 IP links you provision in this example.

Figure 11 Adding C7 IP Links

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.

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         TIMESLOT  SESSIONSET
----                  ------ ---         ---         --------  ----------
c7iplink1             ls01   1           0           0         sessionset-1
c7iplink2             ls01   1           1           0         sessionset-2
c7iplink3             ls02   1           0           0         sessionset-1
c7iplink4             ls02   1           1           0         sessionset-2
   */
   ;

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

 
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       GROUP
----                  ----         -----------       -----
itp-l-1               SLT          N/A               0
itp-l-2               SLT          N/A               0
nas1                  AS5300       N/A               0
nas2                  AS5300       N/A               0
nas3                  AS5300       N/A               0
   */
   ;

Adding NAS Signaling Services

You must add a NAS signaling service for each NAS you created in the "Adding NAS External Nodes" section. 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

 
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           CUSTGRPID  SIGSLOT  SIGPORT
----                  -------               ---           ---------  -------  -------
nassvc1               nas1                  BELL_1268_C2  0000       0        0
nassvc2               nas2                  BELL_1268_C2  0000       0        0
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


Note 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

 
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
   "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   PRI  IPROUTE
----        ---      ------    ----   --------      --------   ---  -------
nas1link1   nassvc1  IP_Addr1  3001   209.165.200.225  3001       1    
nas1link2   nassvc1  IP_Addr2  3001   209.165.201.1  3001       1    
nas2link1   nassvc2  IP_Addr1  3001   209.165.200.226  3001       1    
nas2link2   nassvc2  IP_Addr2  3001   209.165.201.2  3001       1 
nas3link1   nassvc3  IP_Addr1  3001   209.165.200.227  3001       1    
nas3link2   nassvc3  IP_Addr2  3001   209.165.201.3  3001       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.


Figure 15 Adding Trunks

You can add trunks using any of the following methods:

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


Tip 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; 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.)


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. 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.)


Note 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 ffff 1 nassvc1 1 1
101 ss7sigsvc ffff 2 nassvc1 1 2
102 ss7sigsvc ffff 3 nassvc1 1 3
103 ss7sigsvc ffff 4 nassvc1 1 4
104 ss7sigsvc ffff 5 nassvc1 1 5
105 ss7sigsvc ffff 6 nassvc1 1 6
106 ss7sigsvc ffff 7 nassvc1 1 7
107 ss7sigsvc ffff 8 nassvc1 1 8
108 ss7sigsvc ffff 9 nassvc1 1 9
109 ss7sigsvc ffff 10 nassvc1 1 10
110 ss7sigsvc ffff 11 nassvc1 1 11
111 ss7sigsvc ffff 12 nassvc1 1 12
112 ss7sigsvc ffff 13 nassvc1 1 13
113 ss7sigsvc ffff 14 nassvc1 1 14
114 ss7sigsvc ffff 15 nassvc1 1 15
115 ss7sigsvc ffff 16 nassvc1 1 16
116 ss7sigsvc ffff 17 nassvc1 1 17
117 ss7sigsvc ffff 18 nassvc1 1 18
118 ss7sigsvc ffff 19 nassvc1 1 19
119 ss7sigsvc ffff 20 nassvc1 1 20
120 ss7sigsvc ffff 21 nassvc1 1 21
121 ss7sigsvc ffff 22 nassvc1 1 22
122 ss7sigsvc ffff 23 nassvc1 1 23
123 ss7sigsvc ffff 24 nassvc1 1 24
124 ss7sigsvc ffff 25 nassvc1 1 25
125 ss7sigsvc ffff 26 nassvc1 1 26
126 ss7sigsvc ffff 27 nassvc1 1 27
127 ss7sigsvc ffff 28 nassvc1 1 28
128 ss7sigsvc ffff 29 nassvc1 1 29
129 ss7sigsvc ffff 30 nassvc1 1 30
130 ss7sigsvc ffff 31 nassvc1 1 31
131 ss7sigsvc ffff 32 nassvc1 2 1
132 ss7sigsvc ffff 33 nassvc1 2 2
133 ss7sigsvc ffff 34 nassvc1 2 3
134 ss7sigsvc ffff 35 nassvc1 2 4
135 ss7sigsvc ffff 36 nassvc1 2 5
136 ss7sigsvc ffff 37 nassvc1 2 6
137 ss7sigsvc ffff 38 nassvc1 2 7
138 ss7sigsvc ffff 39 nassvc1 2 8
139 ss7sigsvc ffff 40 nassvc1 2 9
140 ss7sigsvc ffff 41 nassvc1 2 10
141 ss7sigsvc ffff 42 nassvc1 2 11
142 ss7sigsvc ffff 43 nassvc1 2 12
143 ss7sigsvc ffff 44 nassvc1 2 13
144 ss7sigsvc ffff 45 nassvc1 2 14
145 ss7sigsvc ffff 46 nassvc1 2 15
146 ss7sigsvc ffff 47 nassvc1 2 16
147 ss7sigsvc ffff 48 nassvc1 2 17
148 ss7sigsvc ffff 49 nassvc1 2 18
149 ss7sigsvc ffff 50 nassvc1 2 19
150 ss7sigsvc ffff 51 nassvc1 2 20
151 ss7sigsvc ffff 52 nassvc1 2 21
152 ss7sigsvc ffff 53 nassvc1 2 22
153 ss7sigsvc ffff 54 nassvc1 2 23
154 ss7sigsvc ffff 55 nassvc1 2 24
155 ss7sigsvc ffff 56 nassvc1 2 25
156 ss7sigsvc ffff 57 nassvc1 2 26
157 ss7sigsvc ffff 58 nassvc1 2 27
158 ss7sigsvc ffff 59 nassvc1 2 28
159 ss7sigsvc ffff 60 nassvc1 2 29
160 ss7sigsvc ffff 61 nassvc1 2 30
161 ss7sigsvc ffff 62 nassvc1 2 31
162 ss7sigsvc ffff 63 nassvc1 3 1
163 ss7sigsvc ffff 64 nassvc1 3 2
164 ss7sigsvc ffff 65 nassvc1 3 3
165 ss7sigsvc ffff 66 nassvc1 3 4
166 ss7sigsvc ffff 67 nassvc1 3 5
167 ss7sigsvc ffff 68 nassvc1 3 6
168 ss7sigsvc ffff 69 nassvc1 3 7
169 ss7sigsvc ffff 70 nassvc1 3 8
170 ss7sigsvc ffff 71 nassvc1 3 9
171 ss7sigsvc ffff 72 nassvc1 3 10
172 ss7sigsvc ffff 73 nassvc1 3 11
173 ss7sigsvc ffff 74 nassvc1 3 12
174 ss7sigsvc ffff 75 nassvc1 3 13
175 ss7sigsvc ffff 76 nassvc1 3 14
176 ss7sigsvc ffff 77 nassvc1 3 15
177 ss7sigsvc ffff 78 nassvc1 3 16
178 ss7sigsvc ffff 79 nassvc1 3 17
179 ss7sigsvc ffff 80 nassvc1 3 18
180 ss7sigsvc ffff 81 nassvc1 3 19
181 ss7sigsvc ffff 82 nassvc1 3 20
182 ss7sigsvc ffff 83 nassvc1 3 21
183 ss7sigsvc ffff 84 nassvc1 3 22
184 ss7sigsvc ffff 85 nassvc1 3 23
185 ss7sigsvc ffff 86 nassvc1 3 24
186 ss7sigsvc ffff 87 nassvc1 3 25
187 ss7sigsvc ffff 88 nassvc1 3 26
188 ss7sigsvc ffff 89 nassvc1 3 27
189 ss7sigsvc ffff 90 nassvc1 3 28
190 ss7sigsvc ffff 91 nassvc1 3 29
191 ss7sigsvc ffff 92 nassvc1 3 30
192 ss7sigsvc ffff 93 nassvc1 3 31
193 ss7sigsvc ffff 94 nassvc2 4 1
194 ss7sigsvc ffff 95 nassvc2 4 2
195 ss7sigsvc ffff 96 nassvc2 4 3
196 ss7sigsvc ffff 97 nassvc2 4 4
197 ss7sigsvc ffff 98 nassvc2 4 5
198 ss7sigsvc ffff 99 nassvc2 4 6
199 ss7sigsvc ffff 100 nassvc2 4 7
200 ss7sigsvc ffff 101 nassvc2 4 8
201 ss7sigsvc ffff 102 nassvc2 4 9
202 ss7sigsvc ffff 103 nassvc2 4 10
203 ss7sigsvc ffff 104 nassvc2 4 11
204 ss7sigsvc ffff 105 nassvc2 4 12
205 ss7sigsvc ffff 106 nassvc2 4 13
206 ss7sigsvc ffff 107 nassvc2 4 14
207 ss7sigsvc ffff 108 nassvc2 4 15
208 ss7sigsvc ffff 109 nassvc2 4 16
209 ss7sigsvc ffff 110 nassvc2 4 17
210 ss7sigsvc ffff 111 nassvc2 4 18
211 ss7sigsvc ffff 112 nassvc2 4 19
212 ss7sigsvc ffff 113 nassvc2 4 20
213 ss7sigsvc ffff 114 nassvc2 4 21
214 ss7sigsvc ffff 115 nassvc2 4 22
215 ss7sigsvc ffff 116 nassvc2 4 23
216 ss7sigsvc ffff 117 nassvc2 4 24
217 ss7sigsvc ffff 118 nassvc2 4 25
218 ss7sigsvc ffff 119 nassvc2 4 26
219 ss7sigsvc ffff 120 nassvc2 4 27
220 ss7sigsvc ffff 121 nassvc2 4 28
221 ss7sigsvc ffff 122 nassvc2 4 29
222 ss7sigsvc ffff 123 nassvc2 4 30
223 ss7sigsvc ffff 124 nassvc2 4 31
224 ss7sigsvc ffff 125 nassvc2 5 1
225 ss7sigsvc ffff 126 nassvc2 5 2
226 ss7sigsvc ffff 127 nassvc2 5 3
227 ss7sigsvc ffff 128 nassvc2 5 4
228 ss7sigsvc ffff 129 nassvc2 5 5
229 ss7sigsvc ffff 130 nassvc2 5 6
230 ss7sigsvc ffff 131 nassvc2 5 7
231 ss7sigsvc ffff 132 nassvc2 5 8
232 ss7sigsvc ffff 133 nassvc2 5 9
233 ss7sigsvc ffff 134 nassvc2 5 10
234 ss7sigsvc ffff 135 nassvc2 5 11
235 ss7sigsvc ffff 136 nassvc2 5 12
236 ss7sigsvc ffff 137 nassvc2 5 13
237 ss7sigsvc ffff 138 nassvc2 5 14
238 ss7sigsvc ffff 139 nassvc2 5 15
239 ss7sigsvc ffff 140 nassvc2 5 16
240 ss7sigsvc ffff 141 nassvc2 5 17
241 ss7sigsvc ffff 142 nassvc2 5 18
242 ss7sigsvc ffff 143 nassvc2 5 19
243 ss7sigsvc ffff 144 nassvc2 5 20
244 ss7sigsvc ffff 145 nassvc2 5 21
245 ss7sigsvc ffff 146 nassvc2 5 22
246 ss7sigsvc ffff 147 nassvc2 5 23
247 ss7sigsvc ffff 148 nassvc2 5 24
248 ss7sigsvc ffff 149 nassvc2 5 25
249 ss7sigsvc ffff 150 nassvc2 5 26
250 ss7sigsvc ffff 151 nassvc2 5 27
251 ss7sigsvc ffff 152 nassvc2 5 28
252 ss7sigsvc ffff 153 nassvc2 5 29
253 ss7sigsvc ffff 154 nassvc2 5 30
254 ss7sigsvc ffff 155 nassvc2 5 31
255 ss7sigsvc ffff 156 nassvc2 6 1
256 ss7sigsvc ffff 157 nassvc2 6 2
257 ss7sigsvc ffff 158 nassvc2 6 3
258 ss7sigsvc ffff 159 nassvc2 6 4
259 ss7sigsvc ffff 160 nassvc2 6 5
260 ss7sigsvc ffff 161 nassvc2 6 6
261 ss7sigsvc ffff 162 nassvc2 6 7
262 ss7sigsvc ffff 163 nassvc2 6 8
263 ss7sigsvc ffff 164 nassvc2 6 9
264 ss7sigsvc ffff 165 nassvc2 6 10
265 ss7sigsvc ffff 166 nassvc2 6 11
266 ss7sigsvc ffff 167 nassvc2 6 12
267 ss7sigsvc ffff 168 nassvc2 6 13
268 ss7sigsvc ffff 169 nassvc2 6 14
269 ss7sigsvc ffff 170 nassvc2 6 15
270 ss7sigsvc ffff 171 nassvc2 6 16
271 ss7sigsvc ffff 172 nassvc2 6 17
272 ss7sigsvc ffff 173 nassvc2 6 18
273 ss7sigsvc ffff 174 nassvc2 6 19
274 ss7sigsvc ffff 175 nassvc2 6 20
275 ss7sigsvc ffff 176 nassvc2 6 21
276 ss7sigsvc ffff 177 nassvc2 6 22
277 ss7sigsvc ffff 178 nassvc2 6 23
278 ss7sigsvc ffff 179 nassvc2 6 24
279 ss7sigsvc ffff 180 nassvc2 6 25
280 ss7sigsvc ffff 181 nassvc2 6 26
281 ss7sigsvc ffff 182 nassvc2 6 27
282 ss7sigsvc ffff 183 nassvc2 6 28
283 ss7sigsvc ffff 184 nassvc2 6 29
284 ss7sigsvc ffff 185 nassvc2 6 30
285 ss7sigsvc ffff 186 nassvc2 6 31
286 ss7sigsvc ffff 187 nassvc3 7 1
287 ss7sigsvc ffff 188 nassvc3 7 2
288 ss7sigsvc ffff 189 nassvc3 7 3
289 ss7sigsvc ffff 190 nassvc3 7 4
290 ss7sigsvc ffff 191 nassvc3 7 5
291 ss7sigsvc ffff 192 nassvc3 7 6
292 ss7sigsvc ffff 193 nassvc3 7 7
293 ss7sigsvc ffff 194 nassvc3 7 8
294 ss7sigsvc ffff 195 nassvc3 7 9
295 ss7sigsvc ffff 196 nassvc3 7 10
296 ss7sigsvc ffff 197 nassvc3 7 11
297 ss7sigsvc ffff 198 nassvc3 7 12
298 ss7sigsvc ffff 199 nassvc3 7 13
299 ss7sigsvc ffff 200 nassvc3 7 14
300 ss7sigsvc ffff 201 nassvc3 7 15
301 ss7sigsvc ffff 202 nassvc3 7 16
302 ss7sigsvc ffff 203 nassvc3 7 17
303 ss7sigsvc ffff 204 nassvc3 7 18
304 ss7sigsvc ffff 205 nassvc3 7 19
305 ss7sigsvc ffff 206 nassvc3 7 20
306 ss7sigsvc ffff 207 nassvc3 7 21
307 ss7sigsvc ffff 208 nassvc3 7 22
308 ss7sigsvc ffff 209 nassvc3 7 23
309 ss7sigsvc ffff 210 nassvc3 7 24
310 ss7sigsvc ffff 211 nassvc3 7 25
311 ss7sigsvc ffff 212 nassvc3 7 26
312 ss7sigsvc ffff 213 nassvc3 7 27
313 ss7sigsvc ffff 214 nassvc3 7 28
314 ss7sigsvc ffff 215 nassvc3 7 29
315 ss7sigsvc ffff 216 nassvc3 7 30
316 ss7sigsvc ffff 217 nassvc3 7 31
317 ss7sigsvc ffff 218 nassvc3 8 1
318 ss7sigsvc ffff 219 nassvc3 8 2
319 ss7sigsvc ffff 220 nassvc3 8 3
320 ss7sigsvc ffff 221 nassvc3 8 4
321 ss7sigsvc ffff 222 nassvc3 8 5
322 ss7sigsvc ffff 223 nassvc3 8 6
323 ss7sigsvc ffff 224 nassvc3 8 7
324 ss7sigsvc ffff 225 nassvc3 8 8
325 ss7sigsvc ffff 226 nassvc3 8 9
326 ss7sigsvc ffff 227 nassvc3 8 10
327 ss7sigsvc ffff 228 nassvc3 8 11
328 ss7sigsvc ffff 229 nassvc3 8 12
329 ss7sigsvc ffff 230 nassvc3 8 13
330 ss7sigsvc ffff 231 nassvc3 8 14
331 ss7sigsvc ffff 232 nassvc3 8 15
332 ss7sigsvc ffff 233 nassvc3 8 16
333 ss7sigsvc ffff 234 nassvc3 8 17
334 ss7sigsvc ffff 235 nassvc3 8 18
335 ss7sigsvc ffff 236 nassvc3 8 19
336 ss7sigsvc ffff 237 nassvc3 8 20
337 ss7sigsvc ffff 238 nassvc3 8 21
338 ss7sigsvc ffff 239 nassvc3 8 22
339 ss7sigsvc ffff 240 nassvc3 8 23
340 ss7sigsvc ffff 241 nassvc3 8 24
341 ss7sigsvc ffff 242 nassvc3 8 25
342 ss7sigsvc ffff 243 nassvc3 8 26
343 ss7sigsvc ffff 244 nassvc3 8 27
344 ss7sigsvc ffff 245 nassvc3 8 28
345 ss7sigsvc ffff 246 nassvc3 8 29
346 ss7sigsvc ffff 247 nassvc3 8 30
347 ss7sigsvc ffff 248 nassvc3 8 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.)

Begins the session.

Step 4 

Enter the prov-add:files command:

machine-name mml> 
prov-add:files:name="BCFile",file="trunks.txt",actio
n="import"
   Media Gateway Controller 2007-03-04 13:16:43
M  COMPLD
   "files"
   ;

Imports a trunk or bearer channel file (BCFile) called trunks.txt from the /opt/CiscoMGC/etc/cust_specific directory.

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    DSTSPAN   DSTTIMESLOT(CIC)
----    ------     ------  ----------------  ------    -------   ---------------
100     ss7sigsvc  ffff    1                 nassvc1   2         1
101     ss7sigsvc  ffff    2                 nassvc1   2         2
102     ss7sigsvc  ffff    3                 nassvc1   2         3
103     ss7sigsvc  ffff    4                 nassvc1   2         4
104     ss7sigsvc  ffff    5                 nassvc1   2         5
105     ss7sigsvc  ffff    6                 nassvc1   2         6
106     ss7sigsvc  ffff    7                 nassvc1   2         7
107     ss7sigsvc  ffff    8                 nassvc1   2         8
108     ss7sigsvc  ffff    9                 nassvc1   2         9
109     ss7sigsvc  ffff    10                nassvc1   2         10
110     ss7sigsvc  ffff    11                nassvc1   2         11
111     ss7sigsvc  ffff    12                nassvc1   2         12
112     ss7sigsvc  ffff    13                nassvc1   2         13
113     ss7sigsvc  ffff    14                nassvc1   2         14
114     ss7sigsvc  ffff    15                nassvc1   2         15

<Press `SPACE' for next page, `Enter' for next line or `q' to quit this output> 

   */
   ;

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).

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          Description
----                  --------  -----------  ---          -----------
"ls01"                00080001  "apc1"       LNKSET       "Linkset from PGW to STP A"
"ls02"                00080002  "apc2"       LNKSET       "Linkset from PGW to STP B"
"nas1link1"           00100001  "nassvc1"    IPLNK        "IP link 1 to NAS 1"
"nas1link2"           00100002  "nassvc1"    IPLNK        "IP link 2 to NAS 1"
"nas2link1"           00100003  "nassvc2"    IPLNK        "IP link 1 to NAS 2"
"nas2link2"           00100004  "nassvc2"    IPLNK        "IP link 2 to NAS 2"
"nas3link1"           00100005  "nassvc3"    IPLNK        "IP link 1 to NAS 3"
"nas3link2"           00100006  "nassvc3"    IPLNK        "IP link 2 to NAS 3"
"ss7route1"           00110001  "mgc-01"     SS7ROUTE     "Route 1 to PSTN Switch A 
through LS01"
"ss7route2"           00110002  "mgc-01"     SS7ROUTE     "Route 1 to PSTN Switch A 
through LS02"
"opc"                 00130001  "mgc-01"     OPC          "origination point code"
"dpc1"                00130002  "mgc-01"     DPC          "DPC of PSTN Switch A"
"nassvc1"             00140001  "nas1"       NASPATH      Signaling service for NAS 1"
"nassvc2"             00140002  "nas2"       NASPATH      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 page, 'Enter' for next line or 'q' to quit this output>
"iproute-1-to-itp-l-2"  004b0002  "mgc-01"     IPROUTE      "First IP route to itp-l-2"
"iproute-2-to-itp-l-1"  004b0003  "mgc-01"     IPROUTE      "Second IP route to itp-l-1"
"iproute-2-to-itp-l-2"  004b0004  "mgc-01"     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.


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,
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.

 
Command/Action
Purpose

Step 1 

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.