Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public
domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase,
Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip
Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work,
Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and
Access Registrar, Aironet, AllTouch, 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 Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity,
Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the
IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY,
PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are
registered trademarks of Cisco 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. (1002R)
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
20012010 Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface
xvii
xvii
Document Objective
Audience
xvii
xvii
Document Organization
xviii
Document Conventions
xix
Syntax Conventions
xix
CHAPTER
Provisioning Overview
Before You Begin
1-1
1-1
xxiii
xxiii
CHAPTER
xxii
1-2
1-2
1-3
1-3
2-2
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
iii
Contents
2-34
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
iv
OL-1110-23
Contents
2-52
CHAPTER
2-91
2-87
3-1
3-1
3-2
3-2
3-3
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
Contents
3-53
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
vi
OL-1110-23
Contents
vii
Contents
3-153
3-153
3-159
3-160
3-162
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
viii
OL-1110-23
Contents
CHAPTER
MML Basics
4-1
4-1
4-3
CHAPTER
4-30
5-1
ix
Contents
5-8
OL-1110-23
Contents
5-26
xi
Contents
5-51
5-56
5-59
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
xii
OL-1110-23
Contents
5-64
5-74
5-73
5-77
5-82
5-82
5-83
5-84
DPNSS Service Interworking with Cisco CallManager Over QSIG Tunneling 5-84
Provisioning Route Optimization Transit 5-85
Provisioning Route Optimization Initiated by the Cisco PGW 2200 Softswitch 5-87
Provisioning Route Optimization Responded by the Cisco PGW 2200 Softswitch 5-89
Provisioning Call Completion 5-89
Provisioning Message Waiting Indicator (with no QSIG Tunneling) 5-90
Provisioning Message Waiting Indicator (with QSIG Tunneling) 5-92
Provisioning a Customer VPN ID in a Trunk Group 5-93
Provisioning a Customer VPN ID in the Dial Plan 5-93
Provisioning Feature Transparency on QSIG Trunk Groups or sigPaths 5-94
Provisioning an H.323 EISUP Trunk Group or sigPaths for Transparent Annex M1 (Tunneled
QSIG) 5-94
Enhanced Local Number Portability and Dial Plan Selection
5-95
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
xiii
Contents
5-96
5-96
5-96
5-101
5-108
5-109
5-110
5-111
SIP and ISUP Interworking for Call Hold and Terminal Portability
SIP Overlap Signaling
5-112
5-113
APPENDIX
5-112
5-115
5-116
5-118
A-1
Components A-1
Network Element Components A-1
Adapter Card A-2
Adjacent Point Code A-2
Association A-3
AXL Server A-7
ISDN BRI Signaling Service A-8
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
xiv
OL-1110-23
Contents
C7 IP Link A-9
Charge A-10
Charge Holiday A-10
CTI Manager A-11
CTI Path A-12
Destination Point Code A-13
D Channel A-13
DNS Parameters A-14
DPNSS Signaling Service A-15
EISUP Signaling Service (sigpath) A-16
Ethernet Interface A-17
External Node A-18
FAS Signaling Service (sigpath) A-19
Files A-19
Intelligent Network Service (INSERVICE) Table A-20
IPFAS Transport Service (previously PRI Signaling Backhaul)
IPINMAPPING A-22
IP Link A-23
IP Route A-25
LABEL A-26
LineXlate A-27
Linkset A-28
Linkset Property A-28
M3UA Key A-33
M3UA Route A-34
MGCP Signaling Service A-35
Multiple IPFAS Services (sigpath) A-35
Multiple Trunk Groups and Trunks A-36
Nailed Trunk (Bearer Channel) A-39
NAS Signaling Service (sigpath) A-40
Originating Point Code A-41
Profile A-42
RASERVER A-59
Routing A-60
Session Set A-64
SGP A-66
SIP IP Link A-66
SIP Signaling Service A-67
SS7 Route A-68
SS7 Signaling Service Properties A-68
A-21
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
xv
Contents
A-98
Properties
A-99
APPENDIX
Planning Worksheets
A-100
A-103
A-106
A-109
B-1
INDEX
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
xvi
OL-1110-23
Preface
Revised: February 25, 2010, OL-1110-23
Document Objective
This document describes the information you need to provision your Cisco PGW 2200 Softswitch. The
document contains tables and worksheets for you to use for provisioning your system.
Audience
The primary audience for this document is network operators and administrators who have experience
in the following areas:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
xvii
Preface
Telecommunications hardware
Network designers
Document Organization
This document contains the chapters listed in Table 1.
Table 1
Document Organization
Chapter
Title
Description
Chapter 1
Provisioning Overview
Chapter 2
Chapter 3
Chapter 4
MML Basics
Chapter 5
Appendix A
Appendix B
Planning Worksheets
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
xviii
OL-1110-23
Preface
Document Conventions
Caution
Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Note
Means reader take note. Notes contain helpful suggestions or references to materials not contained in
this manual.
Tip
Timesaver
Means the described action saves time. You can save time by performing the action described in the
paragraph.
Syntax Conventions
In Chapter 4, MML Basics and in Chapter 5, Adding Components with MML, the same command
syntax conventions are used as those shown by MML itself when the MML command HELP is entered
within MML. For MML commands, the Backus-Naur conventions are used. For additional information
on the MML command syntax, refer to the Cisco PGW 2200 Softswitch Release 9 MML Command
Reference.
Conventions used throughout this guide are shown in Table 2.
Table 2
Conventions
Convention
Meaning
Description / Comments
Boldface
offset-list
Italics
Square brackets ([ ])
Optional elements.
command [abc]
abc is optional (not required), but you
can choose it.
Vertical bars ( | )
Separated alternative
elements.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
xix
Preface
Table 2
Conventions (continued)
Convention
Meaning
Description / Comments
Braces ({ })
Required choices.
Control key.
A nonquoted set of
characters
A string.
System prompts
Denotes interactive
sessions, indicates that the
user enters commands at the
prompt.
Screen
font
A comment line.
Conventions used in the Cisco PGW 2200 Softswitch system (such as in MML commands) are shown in
Table 3.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
xx
OL-1110-23
Preface
Table 3
Data Types
Data Type
Definition
Example
Integer
Signed
integer
This data type has the same basic format as the integer 123
but can be either positive or negative. When negative, it
-000123
is preceded by the sign character (-). As with the integer
data type, this data type can be as many as ten digits in -2100000000l
length, not including the sign character. The value of this
type has a range of 0 minus 2147483647 through
2147483647.
EntityID
A series of alphanumeric characters from the ASCII
character set, where defined. Tab, space, and double
LineSES_Threshold999
quote ( ) characters cannot be used. Text can be as
many as 255 characters; however, it is recommended that
you limit the text to no more than 32 characters for
readability.
String
This is a descriptive
A series of alphanumeric characters and white-space
characters. A string is surrounded by double quotes ( ). string.
Strings can be as many as 255 characters; however, it is
recommended that you limit the strings to no more than
80 characters for readability.
Hexadecimal and integer fields in files may have different widths (number of characters) for column
alignment.
Documentation Roadmap
You can find the Cisco PGW 2200 Softswitch Documentation Map at the following URL:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
xxi
Preface
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/products_documentation_roadmaps_list.ht
ml
Hardware Documentation
Regulatory Compliance and Safety Information for Cisco Media Gateway Controller Hardware
Cisco Media Gateway Controller Software Installation and Configuration (Release 9.7)
Cisco PGW 2200 Softswitch Release 9 Dial Plan Guide (through Release 9.7)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide
Gateway Documentation
Cisco DAS and H.323 VoIP Gateway Installation and Configuration Guide
Terminology
The following terms are used in this document:
Cisco PGW 2200 Softswitch hostA Sun host server running Cisco PGW 2200 Softswitch
software.
Cisco PGW 2200 Softswitch nodeAn active and standby Cisco PGW 2200 Softswitch.
Simplex Cisco PGW 2200 Softswitch nodeA node that uses a single Cisco PGW 2200 Softswitch
host. Typically, such nodes are used for solution evaluation tests or for small installations. In this
configuration, any loss of service in the Cisco PGW 2200 Softswitch host disrupts all call traffic.
Continuous-service Cisco PGW 2200 Softswitch nodeA node that uses two
Cisco PGW 2200 Softswitch hosts to prevent system downtime caused by failure of a single host.
Calls in progress are maintained when one Cisco PGW 2200 Softswitch host fails.
Continuous-service nodes use ITP-Ls to preprocess SS7 signaling and distribute signaling to both
Cisco PGW 2200 Softswitch hosts. If a failover occurs, all stable calls are maintained. A
continuous-service node may also be referred to as a fault-tolerant node or an active-standby PGW
pair.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
xxii
OL-1110-23
Preface
Subject
Provisioning
procedures for
PGW-to-ITP routing
with MAP query
Change Summary
Added the Optimizing PGW-to-ITP Routing with MAP
Query section on page 64 in Chapter 5, Adding Components
with MML.
Provisioning
OL-1110-22, January 29, 2010
procedures for features
Replaced property
OL-1110-21, December 17, 2009
tables with a reference
to another book
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
xxiii
Preface
Table 4
Subject
Added clarifications
Change Summary
Added a Tip to the Routing section on page 5-28 to provide
a link to detailed descriptions of the parameters that are used
with the rttrnkgrp, rttrnk, and rtlist components.
Updated the product name to Cisco PGW 2200 Softswitch
throughout the document.
Added feature
information and
updated product name
Added feature
information
Added feature
information
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
xxiv
OL-1110-23
Preface
Table 4
Subject
Added feature
information
Change Summary
Updated the descriptions for the property RedirMax in
Chapter 2, Planning for Provisioning, and Appendix A
Components and Properties.
Corrected the descriptions for the trunk group parameters
TYPE and SELSEQ in Chapter 2, Planning for
Provisioning, and Chapter 3, Provisioning with the Cisco
Voice Services Provisioning Tool.
Corrected the capacity OPC information for the point code
TYPE parameter in Chapter 2, Planning for Provisioning.
Corrected the description for the property gnInclude in
Chapter 2, Planning for Provisioning, and Appendix A
Components and Properties.
Updated Chapter 4, MML BasicsDeleted the Carrier
Selection table.
Updated Chapter 4, MML Basics to clarify the use of
migrateTKGfile script.
Updated Chapter 4, MML Basics, and Appendix A,
Components and Properties, to add the property
SipSatelliteIndEnable.
Clarified the information for suppressing caller ID in a SIP
environment in Chapter 5, Adding Components with MML.
Added the property *.isdnNSF in Appendix A Components
and Properties.
Added the property *.mgcpDomainNameLocal in
Appendix A Components and Properties.
Corrected OPC information in Chapter 2, Planning for
Provisioning, to indicate there can be up to eight capability
OPCs for each true OPC.
Removed references to Tekelec in Chapter 2, Planning for
Provisioning, and Chapter 5, Adding Components with
MML.
Added feature
information
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
xxv
Preface
Table 4
Subject
Change Summary
Added feature
information
Added feature
information
Added feature
information
Added feature
information
Added feature
information
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
xxvi
OL-1110-23
Preface
Table 4
Subject
Added feature
information
Added feature
information
Change Summary
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
xxvii
Preface
Table 4
Subject
Added feature
information
Added feature
information
Provisioning changes
Change Summary
VSPT changes
Added properties
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
xxviii
OL-1110-23
Preface
Table 4
Subject
Provisioning rules
MML names
re-ordered for routing
Change Summary
Parameter values
Initial release
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
xxix
Preface
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
xxx
OL-1110-23
CH A P T E R
Provisioning Overview
Revised: February 25, 2010, OL-1110-23
This chapter provides an overview of the Cisco PGW 2200 Softswitch provisioning process and tools. It
includes the following sections:
The remaining chapters in this guide describe how to develop a provisioning plan and to provision your
system using the tools provided with your Cisco PGW 2200 Softswitch software.
The provisioning process described in this document applies to all solutions running
Cisco PGW 2200 Softswitch software Release 9.
Note
This document does not include instructions for dial plan provisioning. For dial plan information, refer
to the Cisco PGW 2200 Softswitch Release 9 Dial Plan Guide (through Release 9.7).
Thoroughly plan your network configuration. A detailed network diagram is helpful when
provisioning. For more information, refer to your solutions overview document.
Set up your system hardware and install all required software. For more information, refer to the
following documents:
Cisco Media Gateway Controller Hardware Installation Guide
Cisco Media Gateway Controller Software Release 8 Installation and Configuration Guide
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-1
Chapter 1
Provisioning Overview
Note
Most of the links shown Figure 1-1 represent multiple connections between devices.
Figure 1-1
SS7
STP
PSTN
Cisco ITP-Ls
Control
signaling
network
STP
STP
Cisco PGW 2200
Softswitch
Cisco
PGW 2200
Softswitch
Cisco ITP-Ls
Media
gateway
Control
signaling
network
33066
QoS packet
network
Media gateway
Provisioning prepares the Cisco PGW 2200 Softswitch software to communicate with the SS7 network
and with the media gateways. To provision your Cisco PGW 2200 Softswitch , you must:
Configure communications between the Cisco PGW 2200 Softswitch and external SS7 signaling
points (SPs), such as STPs
Configure connections between the Cisco PGW 2200 Softswitch and the media gateways
You establish these connections by specifying parameter values for each of the entities illustrated in
Figure 1-1 (Cisco PGW 2200 Softswitch hosts, ITP-Ls, STPs, media gateways, and all their associated
links).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-2
OL-1110-23
Chapter 1
Provisioning Overview
Cisco PGW 2200 Softswitch Provisioning Rules
Add linksets
Add IP links
Enable the Cisco PGW 2200 Softswitch software on the active host.
Configure the Cisco PGW 2200 Softswitch software for the active host.
Only one active provisioning session is permitted.
Provisioning is only permitted on the active Cisco PGW 2200 Softswitch.
If you have a standby host, set the pom.dataSync to true (in the XECfgParm.dat file) so that when started,
the standby host synchronizes with the active host.
Note
If the preceding rules are not followed the standby host will not be synchronized with the active host. As
a result, a forced switchover may cause the switchover to fail.
Refer to the Cisco Media Gateway Controller Software Release 9 Installation and Configuration
(Release 9.7) for information about installing the host software and the Cisco PGW 2200 Softswitch
software.
The Voice Services Provisioning Tool Version 2.3, (VSPT) graphical user interface (GUI)
application.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-3
Chapter 1
Provisioning Overview
Note
The Voice Services Provisioning Tool replaces the TCM and CMM provisioning tools of previous
software releases.
The Cisco VSPT provides a GUI for the creation, modification, and execution of signaling connections,
as well as trunk groups, trunks, routes, and dial plans. It also allows users to import existing
configurations for modification and to download modified configurations to the same or different
devices. To simplify operator tasks such as trunk group provisioning, the Cisco VSPT employs a series
of wizard-style templates combined with a user interface that is tailored for provisioning the
Cisco PGW 2200 Softswitch. Users can automatically generate the MML commands necessary to
configure the appropriate network elements. Because much of the operator input information is common
to the media gateways and the Cisco PGW 2200 Softswitch, the Cisco VSPT ensures that the
information is entered once and then used to create the required MML commands. The resulting batch
files are sent to the Cisco PGW 2200 Softswitch, updating the appropriate configuration records.
The VSPT is useful when initially provisioning your Cisco PGW 2200 Softswitch. An example of the
Cisco VSPT GUI is shown in Figure 1-2. A comparison of the VSPT and MML features is included in
Table 1-1.
Note
The Cisco VSPT application may be deployed as an integrated component of the Cisco MGC Node
Manager or as a standalone application. When integrated with Cisco MGC Node Manager, the VSPT
application is launched directly from within Cisco MGC Node Manager.
For instructions on using the VSPT, see Chapter 3, Provisioning with the Cisco Voice Services
Provisioning Tool.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-4
OL-1110-23
Chapter 1
Provisioning Overview
Cisco PGW 2200 Softswitch Provisioning Tools
Figure 1-2
You can also provision your Cisco PGW 2200 Softswitch by creating the MML command batch file
manually without the aid of the VSPT. Although provisioning using this method requires more
keystrokes, simple provisioning updates can sometimes be accomplished more quickly, because you do
not have to go through the process of launching the VSPT. When you enter MML commands manually
into a batch file, you can copy and paste repetitive commands to speed data entry. You can also copy and
modify existing MML scripts (lists of MML commands) to provision additional devices. An example of
an MML command script is included in Example 1-1.
Provisioning using MML commands is recommended for more-experienced users. A comparison of the
VSPT and MML features is included in Table 1-1.
For information on provisioning with MML, refer to Chapter 4, MML Basics.
Example 1-1
prov-sta::srcver="new",dstver="oldyella"
prov-add:opc:name="opc1",netaddr="111.111.666",netind=1,desc="opc1",type=trueopc
prov-add:dpc:name="dpc1",netaddr="444.777.444",netind=1,desc="TDM Switch dpc1"
prov-add:dpc:name="dpc2",netaddr="555.333.555",netind=3,desc="Host Node dpc2"
prov-add:apc:name="apc1",netaddr="666.222.222",desc="STP 1 APC pointcode",netind=1
prov-add:apc:name="apc2",netaddr="777.333.333",desc="STP 2 APC pointcode",netind=2
prov-add:apc:name="apc3",netaddr="888.777.777",desc="STP 3 APC pointcode",netind=3
prov-stp
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-5
Chapter 1
Provisioning Overview
Note
You can use both Voice Services Provisioning Tool and MML to provision the
Cisco PGW 2200 Softswitch; however, only a single configuration session can be supported at one time.
Table 1-1
Specifications/Features
MML
System Basics
System
Hardware/Software
Requirements
Runs on the
Cisco PGW 2200 Softswitch host
server.
Note
No
Yes
Modifying an existing
configuration.
Modifying configurations.
Troubleshooting.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-6
OL-1110-23
CH A P T E R
Note
We recommend that you use two Cisco PGW 2200 Softswitch hosts for maximum availability. The
differences in the active and standby hosts are defined in the XECfgParm.dat file, which is configured
during software installation. The configuration planned in this chapter applies to both of the
Cisco MGCs. You create one configuration for one primary or active node (The standby node cannot be
provisioned.) and apply that configuration to both nodes.
Tip
This chapter provides worksheets you can use to plan the configuration components. While some tables
provide room to define many components, other tables allow you to plan just one component. Before you
start your planning, copy the tables and write on the copies. This way, you can make additional copies
later if you need them.
Device addresses
External nodes
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-1
Chapter 2
Note
Cisco IP Transfer Point - LinkExtender (ITP-L) is the new name for Cisco Signaling Link Terminal
(SLT). Over time, Cisco ITP-L will replace Cisco SLT in publications and the product.
Type
Description
Table B-16 serves as a form you can use to plan for each external node.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-2
OL-1110-23
Chapter 2
Note
Card
Type Designation
Description
Ethernet interface
card
EN
Service type
Name
Description
Customer Group ID
This SS7 signaling service link information can be listed in Table B-21, which serves as a form you can
use to record signaling service information.
Service type
Device
Description
Protocol service
Side
This MGW signaling service link information can be listed in Table B-21.
Point code
Type of component
Name
Description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-3
Chapter 2
IP transport type
Description
Linkset name
Linkset type
Linkset rate
IP address
Peer IP address
Port number
IP route
Type
Description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-4
OL-1110-23
Chapter 2
Linkset
Sessionset
SLC
Priority
Time slot (the physical slot (serial port) information on the Cisco ITP-L)
Description
Line interface
IP address
Port number
Priority
Peer IP address
Service
Next hop
Net mask
Name
Description
Signal DPC
Linkset
OPC
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-5
Chapter 2
Component description
Protocol family
Priority
Trunk ID (name)
Source span
Destination span
Span size
To save space, you might want to specify ranges of trunk IDs for each E1 or T1 connection. For large
installations, you might want to make copies of this table or create your own worksheet with these
columns.
The circuit identification code (CIC) is the SS7 value representing the trunk and must match the CIC
value defined at the remote switch.
The destination span ID and destination time slot must match the trunk configuration values defined
during Cisco PGW 2200 Softswitch configuration. The destination span ID is defined when configuring
T1 and E1 controllers and must match the value of the nfas_int parameter. T1 spans use time slots
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-6
OL-1110-23
Chapter 2
(channels) 1-24 and E1 spans use time slots 0-31. For more information on gateway configuration, see
the Cisco SS7 Interconnect for Access Servers and Voice Gateways Solutions Media Gateway
Installation and Configuration Guide.
Note
Configure the Cisco PGW 2200 Softswitch first and then configure the MGW. When you configure the
Cisco PGW 2200 Softswitch first, enter the Cisco PGW 2200 Softswitch configuration parameters in
Table B-13, then use these values when configuring the MGW.
Span
Coding unit
End point
Span size
To save space, you might want to specify ranges of trunk IDs for each E1 or T1 connection. For large
installations, you might want to make copies of this table or create your own worksheet with these
columns.
The circuit identification code (CIC) is the SS7 value representing the trunk and must match the CIC
value defined at the remote switch.
Note
Configure the Cisco PGW 2200 Softswitch first and then configure the MGW. When you configure the
Cisco PGW 2200 Softswitch first, enter the Cisco PGW 2200 Softswitch configuration parameters in
Table B-14, then use these values when configuring the MGW.
MML name
Component description
Customer group ID
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-7
Chapter 2
Note
If you are using the ETS_300_102 or Q931 protocol files, call reference should be set to 1.
If you are using the ETS_300_172 protocol file, call reference should be set to 2.
You can define the parameters for your QSIG/Q.931 over BRI Backhaul signaling services in Table B-8.
MML name
Local IP address
Destination IP address
You can define the parameters for your Backhaul TCP links in Table B-24.
IP route name
Component description
Local IP address
Priority
MML name
Component description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-8
OL-1110-23
Chapter 2
Customer group ID
A-B flag
Component description
Customer group ID
Component description
Associated OPC
Service indicator
Component description
Associated DPC
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-9
Chapter 2
Associated OPC
MML name
Signaling type
Priority
Local subunit
Signaling Type
Maximum number of retransmissions over all destination address before the association is declared
failed (optional)
Maximum time after a datagram is received before a SCPT SACK is sent (optional)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-10
OL-1110-23
Chapter 2
Maximum time SCTP waits for other outgoing datagrams for bundling (optional)
Time between heartbeats. The heartbeat is this value plus the current retransmission timeout value
(optional)
Internet Protocol Precedence. This value is placed in the IP PRECEDENCE portion of the Type Of
Service field for outgoing SCTP datagrams (optional)
Differential Service Code Point. This value is placed in the DSCP portion of the Type Of Service
field for outgoing SCTP datagrams (optional)
Component description
The SS7 signaling gateway process component structure is shown in Table B-35.
Component description
Customer group ID
Component description
Associated OPC
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-11
Chapter 2
Component description
Associated APC
Associated OPC
Component description
Priority
Define the point codes (SS7 network addresses) of devices along the signaling route.
2.
Define linksets.
3.
4.
5.
6.
7.
Figure 2-1 shows the relationship of these components. Figure 2-2 shows the order in which these
components are to be configured.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-12
OL-1110-23
Chapter 2
Figure 2-1
External switch
Route A
SS7
signaling
service
Destination
point
code
(DPC)
Figure 2-2
Origination
point
code
(OPC)
DPC
OPC
Linkset
SS7
signaling
service
Linkset
properties
33068
SS7
signaling
service
properties
33067
Route A
SS7 route
Note
When provisioning, fully define all components (see Figure 2-2) before deploying a configuration.
Note
For properties not described in this chapter, refer to Appendix A, Components and Properties.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-13
Chapter 2
Cisco PGW 2200 SoftswitchWithin the Cisco MGC software, the Cisco PGW 2200 Softswitch
point code is called the OPC. Use Table B-4 to plan the OPC configuration for your
Cisco PGW 2200 Softswitch.
STPWithin the Cisco PGW 2200 Softswitch software, the point code for each STP with which the
controller communicates is called the APC. Use Table B-7 to plan the APCs for your
Cisco PGW 2200 Softswitch.
Destination switchWithin the Cisco PGW 2200 Softswitch, a remote devices point code is called
a DPC. You need a point code for each remote switch with which the MGC node will communicate.
Use Table B-5 to plan the DPCs for your Cisco PGW 2200 Softswitch.
When configuring a Cisco PGW 2200 Softswitch, you must enter a point code and a point code type for
each Cisco PGW 2200 Softswitch, along with the network address and the network indicator. The point
code type is OPC and the point code address is a value in the form of x.x.x. For example, 8.232.72. The
two periods separating the three numeric labels are required, and the numeric labels must be entered in
decimal values. If your service provider issues these numbers using binary or hexadecimal values, you
must convert them to decimal.
Note
The point code examples used in this document follow the ANSI SS7 (8bits.8bits.8bits) point code
format. However, the Cisco PGW 2200 Softswitch can also support ITU point codes.
For configuring point codes for remote switches, the point code type is DPC. Each point code for an STP
is an APC, and the STP point code type is APC. The point code values for DPCs and APCs use the same
format (x.x.x) as for OPCs.
To define SS7 network addresses, use the following components:
Table 2-2
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
MML name
Unique name for this point code. Enter as many as 20 alphanumeric characters and
enclose in straight quotes. Hyphens (-) can be used.
NETADDR
Network
address
NETIND
Network
indicator
The network indicator assigned by the network administrator. Value range: 0 (default)
through 3. Where 0 is for international networks, 1 is for spare, 2 is for national networks,
and 3 is reserved for national use.
DESC
Description
Text description of this point code. Enter as many as 128 characters and enclose in straight
quotes.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-14
OL-1110-23
Chapter 2
Table 2-2
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
TYPE
Type
Type of the OPC. Values are: TRUEOPC or CAPOPC. A maximum of six true OPCs are
supported, and for each true OPC a maximum of eight capability OPCs are supported per
Cisco PGW 2200 Softswitch.
TRUEOPC
True OPC
MML name of the true OPC with which the capability OPC is associated. The MML name
of previously defined true OPC. It only applies to the capability OPC.
Planning Linksets
After you determine the point codes for your network devices, you must define the linksets that connect
each MGC node directly to a remote switch or indirectly to the remote switch through an STP. A linkset
is the group of all communication links connecting an MGC node to a specific SSP or STP. When two
STPs are defined as mates within the Cisco PGW 2200 Softswitch, the Cisco PGW 2200 Softswitch can
use either linkset to connect to the SS7 signaling network.
Table 2-3 lists the configuration parameters you define for each linkset during provisioning. Table B-9
serves as a form that you can use to plan the linksets.
To define linksets, use the following component:
Note
When configuring linksets for STP connections, you will usually configure two linksets for each pair of
STPs.
Table 2-3
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
MML name
Unique name for this linkset. Enter as many as 20 alphanumeric characters and enclose in
straight quotes. Hyphens (-) can be used.
APC
Adjacent point
code/point
code
Adjacent point code or destination point code. For linksets that connect directly to an SSP,
enter the MML name of a previously defined destination point code. For linksets that
connect to a Cisco ITP-L, enter the MML name of a previously defined adjacent point
code.
TYPE
Transport type
Enter TDM for linksets that connect directly to an SSP, or enter IP for linksets that
connect to Cisco ITP-Ls. The default is TDM.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-15
Chapter 2
Table 2-3
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
PROTO
DESC
Description
SS7-ANSI
SS7-ITU
SS7-China
SS7-Japan
SS7-UK
Text description of this linkset. Enter as many as 128 characters and enclose in straight
quotes.
Table 2-4
Default Value
Unit
Description
mtp2LssuLen
Octets
mtp2MaxAlignRetries
Attempts
272
Octets
mtp2MaxOutsFrames
Frames
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-16
OL-1110-23
Chapter 2
Table 2-4
Default Value
Unit
Description
mtp2ProvingEmgT4
Tenths of a
second
mtp2ProvingNormalT4
Tenths of a
second
mtp2SuermThr
mtp2T1
SS7-ANSI=130
SS7-UK=450
SS7-CHINA=450
SS7-ITU=450
SS7-JAPAN=150
Tenths of a
second
mtp2T2
SS7-ANSI=115
SS7-UK=250
SS7-CHINA=250
SS7-ITU=250
SS7-JAPAN=50
Tenths of a
second
mtp2T3
SS7-ANSI=115
SS7-UK=20
SS7-CHINA=20
SS7-ITU=20
SS7-JAPAN=30
Tenths of a
second
mtp2T5
mtp2T6
SS7-ANSI=30
SS7-UK=60
SS7-CHINA=60
SS7-ITU=60
SS7-JAPAN=30
Tenths of a
second
mtp2T7
Tenths of a
second
mtp3ApcMtpRstrtT28
SS7-ANSI=10
Tenths of a
second
mtp3DlnkConnAckT7
Tenths of a
second
mtp3FrcUnhT13
Tenths of a
second
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-17
Chapter 2
Table 2-4
Default Value
Unit
Description
mtp3InhAckT14
Tenths of a
second
mtp3LocInhTstT20
SS7-ANSI=900
Tenths of a
second
mtp3MaxSltTries
Messages
mtp3MsgPriority
SS7-ANSI=2
SS7-UK=1
SS7-CHINA=1
SS7-ITU=2
SS7-JAPAN=2
mtp3MtpRstrtT20
SS7-UK=640
SS7-CHINA=10
SS7-ITU=640
SS7-JAPAN=0
Tenths of a
second
mtp3LocInhTstT22
Tenths of a
second
mtp3MtpRstrtT24
SS7-ANSI=60
Tenths of a
second
Overall MTP restart timer for local MTP restart. Value range
is network-dependent.
mtp3RepeatRstrtT26
SS7-ANSI=150
Tenths of a
second
mtp3TfrUsed
false
mtp3TraSnT29
SS7-ANSI=600
Tenths of a
second
mtp3tstSltmT1
SS7-ANSI=60
SS7-UK=50
SS7-CHINA=50
SS7-ITU=50
SS7-JAPAN=0
Tenths of a
second
mtp3tstSltmT2
SS7-ANSI=600
SS7-UK=300
SS7-CHINA=300
SS7-ITU=300
SS7-JAPAN=0
Tenths of a
second
mtp3ApcMtpRstrtT21
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-18
OL-1110-23
Chapter 2
Table 2-4
Default Value
Unit
Description
mtp3UnhAckTl2
Tenths of a
second
mtp3T0
SS7-JAPAN=200
Tenths of a
second
Not used.
mtp3T7
SS7- JAPAN=20
Tenths of a
second
mtp3T12
SS7-JAPAN=0
Tenths of a
second
mtp3T13
SS7-JAPAN=0
Tenths of a
second
Same as mtp3FrcUnhT13.
mtp3T14
SS7-JAPAN=0
Tenths of a
second
Same as mtp3InhAckT14.
mtp3T20
SS7-JAPAN=0
Tenths of a
second
Same as mtp3MtpRstrtT20.
mtp3T21
SS7-JAPAN=0
Tenths of a
second
Same as mtp3ApcMtpRstrtT21.
mtp3T22
SS7-JAPAN=0
Tenths of a
second
Same as mtp3LocInhTstT22
reference
SS7-ANSI=ANSI9
2
SS7-UK=ITU92
SS7-CHINA=ITU9
2
SS7-ITU=ITU92
SS7-JAPAN=Japan
rudpAck
enable
Not used.
rudpKeepAlives
enable
Not used.
rudpNumRetx
rudpWindowSz
32
rudpRetxTimer
rudpSdm
enable
Tenths of a
second
1. The mtp2 parameters are used with directly connected SS7 signaling links.
2. All timer values are expressed in tenths of a second. For example, 130 = 13 seconds.
3. SIB = Status indication busy
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-19
Chapter 2
Note
You must define one SS7 subsystem for each STP to which the Cisco PGW 2200 Softswitch software
connects.
To define an SS7 subsystem, use the following component:
For mated STPs, the subsystem defined for each STP defines the other STP as the mate using the
MATEDAPC parameter.
Table 2-5
MML Parameter
Name
Voice
Services
Provisioning
Tool
Parameter
Name
NAME
MML name
Unique name for this subsystem. Enter as many as 20 alphanumeric characters and
enclose in straight quotes. Hyphens (-) can be used.
DESC
Description
Text description of this component. Enter as many as 128 characters and enclose in
straight quotes.
LOCALSSN
Local SSN
Subsystem number. Enter an integer from 0 to 255. When mating STPs, SSN = 0. When
using Intelligent Network (IN) services, SS7-ANSI, SS7-ETSI, or SS7-ITU, Local SSN
can be set to a value greater than 0.
Default = 0.
MATEDAPC
Mated
adjacent
point code
Adjacent point code for an STP mate. Enter the MML name of previously defined APC.
Only used when mating STPs, not when creating AIN subsystems.
OPC
Originating
PC
Priority
Priority. Enter an integer that is greater than 0 and less than 4. One (1) is the highest
priority level. When two subsystems share the same priority level, traffic is shared by both
subsystems. Not used when mating STPs.
(formerly SSN)
PRI
Description
Default = 1.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-20
OL-1110-23
Chapter 2
Table 2-5
MML Parameter
Name
PROTO
Voice
Services
Provisioning
Tool
Parameter
Name
Protocol
family
Description
Protocol family. When mating STPs, only the SS7 variant is allowed.
If the SVC is an APC, SCCP should not be used (SCCP is not used when mating STP
pairs. If the SVC is a TCAPoverIP service, then TCPIP should be used
REMOTE SSN
Remote SSN
Integer from 2 through 254;(0). Can be set to non-zero only for SS7-ANSI, SS7-ETSI, or
SS7-ITU. If set to 0, the subsystem is used for mating two STPs. Use LOCALSSN if not
specified.
Can only be set to non-zero for SS7-ANSI, SS7-ETSI, or SS7-ITU.
STPSCPIND
STP-SCP
index
STP/SCP index. Enter an integer greater than 0. When mating STPs = 0. Default = 0. Not
used when mating STPs.
SUAKEY
SVC
Adjacent
point code
Adjacent point code for an STP. The MML name or index of the APC if TRANSPROTO
is SCCP. Or the MML name or index of TCAPOverIP service for IN trigger services if
TRANSPROTO is TCPIP. Enter the MML name of a previously defined APC.
TRANSPROTO
Transport
protocol
Transport protocol. Enter the transport protocol of this subsystem. When mating STPs =
SCCP. Values: SCCP or TCPIP. Not used when mating STPs.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-21
Chapter 2
Table 2-6
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
MML name
Unique name for this route. Enter as many as 20 alphanumeric characters and enclose in
straight quotes. Hyphens (-) can be used.
OPC
Originating
point code
Originating point code (must be a true OPC). Enter the MML name of a previously
defined originating point code for this MGC node.
DPC
Destination
point code
Destination point code. Enter the MML name of a previously defined destination point
code for a remote switch.
LNKSET
Link set
Linkset that leads to the destination device. Enter the MML name of a previously defined
linkset.
PRI
Priority
SS7 route priority. Enter an integer that is greater than 0. One (1) is the highest priority
level. When two SS7 routes share the same priority level, traffic is shared by both routes.
Default = 1.
DESC
Description
Text description of this route. Enter as many as 128 characters and enclose in straight
quotes.
Table 2-7
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
MML name
DESC
Description
SIDE
Side
Q.931 call model side. Enter user for user side or network for network
side. (Used only for IP FAS transport service.)
DPC
Point code
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-22
OL-1110-23
Chapter 2
Table 2-7
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
MDO
MDO file name Message definition object file name. Choose a valid protocol name.
Refer to the release notes for the Cisco MGC software Release 9 for a
current list of MDO file names.
CUSTGRPID
Customer
group ID
OPC
Originating
Point Code
Table 2-8
Default Value
Description
adjDestinations
16
AInternationalPrefix
NULL
ANationalPrefix
NULL
BInternationalPrefix
NULL
BNationalPrefix
NULL
BothwayWorking
Set to 0 to disable both way release / circuit free handling for BTNUP
protocol. Value range: 0 or 1.
CGBA2
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-23
Chapter 2
Table 2-8
Default Value
Description
CLIDefaultAllowed
false
CLIPEss
COLDefaultAllowed
false
CotInTone
2000 20
Receive tone for continuity test (COT) hardware. The tone to listen for
when doing a COT. Enter value in Hz.
Value: 1780 or 2010.
CotOutTone
2000 20
Transmit tone for COT hardware. The tone that is produced. Enter value
in Hz. Value: 1780 or 2010.
CotPercentage
dialogRange
ForwardCLIinIAM
ForwardSegmentedNEED
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-24
OL-1110-23
Chapter 2
Table 2-8
Default Value
Description
GLARE
Note
Note
Note
Note
GRA2
GRSEnabled
false
This property is assigned to an SS7 point code type signal path. Enables
Group Reset and Blocking procedure at point code initialization.
Synchronizes the Cisco PGW 2200 Softswitch bearer channel blocking
state with that of the end office.
If true, GRS messages are sent for all CICs associated with the point
code.
If false, GRS messages are not sent.
GRSonSSCEnabled
false
When the far end receives the GRS message, any active calls are
released on the point code, as per ITU-T Recommendation
Q.764.
If true, the GRS message is sent to the far end point code for all CICs
associated with the point code after the point code was put in-service
again.
If false, the GRS message is not sent.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-25
Chapter 2
Table 2-8
Default Value
Description
hopCount
layerRetries
layerTimer
10
Time (in tenths of a second) to wait for a response from adjacent layer
(SS7 controller, TCAP to SCCP); tailor when layers are not resident on
same processor. Value range: 0 through 10.
0 = Disabled, 10 = 1 second.
maxMessageLength
250
NatureOfAddrHandling
NFASImplicitInterfaceId
65535
Normalization
OD32DigitSupport
Allows 32 digits and overdecadic digits support for the ANSI, Q.761,
and Q.767 protocol variants for the ANSI, SS7-ITU, SS7-China,
SS7-Japan, and SS7-UK protocol families. Values are: 0 (disabled) and
1 (enabled).
This property is added in software Release 9.4(1).
OMaxDigits
24
OMinDigits
OmitCgPnFromUnavailabl
e
Determines if mapping between the SIP From header to the IAM calling
party number is enabled when the SIP message header From is
unavailable. Values are: 0 (enabled) or 1 (disabled).
This property is added in software Release 9.5(2).
OOverlap
Set to 1 to enable overlap signaling for call origination from this traffic
path.
Value range: 0 through system maximum.
OverlapDigitTime
Overlap interdigit timer. The time to wait for the rest of the digits.
Value range: 0 through 60.
Note
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-26
OL-1110-23
Chapter 2
Table 2-8
Default Value
Description
OwnClli
na
RedirMax
0:
Note
restartTimer
10
RoutePref
SdpXmitToH323Trigger
5= IP Preferred
1 = ATM Essential
6 = IP Excluded
2 = ATM Preferred
7 = TDM Essential
3 = ATM Excluded
8 = TDM Preferred
4 = IP Essential
9 = TDM Excluded
Indicates the point in a call when the Cisco PGW 2200 Softswitch sends
the Session Destination Protocol (SDP) from the terminating call leg to
the H.323 Signaling Interface (HSI). Value range: 0 through 3.
0 = terminating seizure, 1 = Address complete, 2 = Alerting or Inband
information available, or 3 = Answer.
This property is added in software Release 9.4(1).
sendAfterRestart
SS7-ANSI=16
Number of queued messages to send (in one group) to MTP3 after restart
end. This value, combined with the sendTimer, controls the amount of
data sent to MTP3 after restart ends. If too much data is sent to MTP3
after restart, MTP3 could be flooded. Value range: 0 through 256.
slsTimer
SS7-ANSI=300
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-27
Chapter 2
Table 2-8
Default Value
Description
srtTimer
SS7-ANSI=300
sstTimer
SS7-ANSI=300
standard
SS7-ANSI=ANSI9
6,
SS7-ITU=ITU96,
ANSI96,
ITU96,
ANSI92,
ITU92
TMaxDigits
24
TMinDigits
TOverlap
variant
SS7-ANSI=SS7-A
NSI, SS7-ITU
VOIPPrefix
A numeric string.
1.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-28
OL-1110-23
Chapter 2
2.
Create linkset
3.
4.
Create adapter
5.
Create interface
6.
It is best to plan SS7 routes before you configure links, because you define APCs and linksets when
defining routes, and these components must be planned and configured before you can configure links.
Because the planning of these components is described in the Planning SS7 Signaling Routes section,
these procedures are not repeated here. This section describes how to plan for provisioning the following
components:
Links
The following sections describe how to plan for each of these components.
Note
In the MGC node, the same cards and interfaces can be used for communication with the Cisco ITP-Ls
and media gateways. When this type of configuration is used, separate links are assigned for the
Cisco ITP-L and media gateway communications.
All Cisco MGCs will have at least one Ethernet interface card installed. When configuring the
Cisco PGW 2200 Softswitch you need to enter the card name, type, slot number, and IP address
information. The IP address information is entered by entering or selecting a system variable name,
which is associated with an IP address in the XECfgParm.dat file. You configure the IP addresses and
assign them to variables using the procedures in Cisco Media Gateway Controller Software Release 8
Installation and Configuration Guide.
Table 2-9 lists the Cisco PGW 2200 Softswitch interface card parameter definitions. Table B-1 serves as
a form you can use to enter the configuration information for the network interface cards installed in
your Cisco PGW 2200 Softswitch. For Ethernet cards, the system variable is required for configuration,
but the IP address and card slot are not required. The IP address column is provided for convenience.
To provision network cards, use the following component:
Note
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-29
Chapter 2
Table 2-9
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
SLOT
Slot
None
TYPE
Type
None
Description
DESC
Description
None
EN
Note
In the MGC node, the same cards and interfaces can be used for communication with the Cisco ITP-Ls
and media gateways. When configured this way, separate links are assigned for the Cisco ITP-L and
media gateway communications.
To provision Ethernet interfaces, use the following component:
Note
Table 2-10
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
MML name
Unique name for this interface. Enter as many as 20 alphanumeric characters and enclose
in straight quotes. Hyphens (-) can be used.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-30
OL-1110-23
Chapter 2
Table 2-10
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
CARD
Ethernet
adapter
Identifies the card that supports this interface. Set this to the MML name of a card that
has already been defined.
DESC
Description
Text description of this interface. Enter as many as 128 characters and enclose in straight
quotes.
Note
In the Cisco PGW 2200 Softswitch node, the same cards and interfaces can be used for communication
with the Cisco ITP-Ls and media gateways. When configured this way, separate links are assigned for
the Cisco ITP-L and media gateway communications.
Note
Table 2-11 lists and describes the configuration parameters that define the TDM interface. Table B-25
serves as a form you can use to plan a TDM interface.
Table 2-11
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
CARD
TDM line
interface
None
Identifies the card that supports this interface. Set this to the MML name
of a card that has already been defined.
LIFNUM
Line interface
number
RESIST
Resistance
75
Selects the line resistance, in ohms. Choose 75 (T1) or 120 (E1) for an
ITK card; otherwise, choose 0.
DATARATE
Data rate
64
Selects the data rate for only the V.35 card. Choose 48, 56, or 64 (kbps).
Description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-31
Chapter 2
Table 2-11
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
CLOCK
Clock
EXT
Selects the clock source for only the V.35 card. Choose EXT (external)
or INT (internal).
DTEDCE
DTE or DCE
DTE
Selects the device type for only the V.35 card. Choose DTE (data
terminal equipment) or DCE (data communications equipment).
CODING
Coding
B8ZS
Selects the line coding type on the link. Choose either AMI (alternate
mark inversion) or B8ZS (bipolar with 8 zero substitution) for T1.
Choose HDB3 (high-density bipolar with 3 zero replacement) for E1.
FORMAT
Format
ESF
SIGTYPE
Signal type
T1
Selects the type of signaling on the link. Choose T1 for ANSI (American
National Standards Institute) DS1 (digital signal level 1). Choose CEPT
(Conference Europeenne des Postes et des Telecommunications) for E1.
Choose V.35 for 64 kbps digital.
HDLC
Control
HDLC
Selects the HDLC (High-Level Data Link Control) for the ITU link layer
protocol standard. Choose IHDLC (Inverted HDLC) for an ITK card;
otherwise HDLC (not used).
DESC
Description
None
Note
Description
To prevent a single point of failure in a dual-homed Cisco PGW 2200 Softswitch configuration
connected to a VISM in a Cisco MGX8850 (with one IP address), establish IP redundancy by:
Configuring NEXTHOP and NETMASK for all signaling links and session sets.
The external node must be the MGX8850
The hosts must be on different subnets.
At the Cisco PGW 2200 Softswitch end of each link, the link is associated with an Ethernet
interface, an IP address, and a UDP port.
At the Cisco ITP-L end of each link, the Cisco ITP-L is identified with an IP address and a UDP
port.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-32
OL-1110-23
Chapter 2
Tip
The portion of the link between the Cisco ITP-L and the STP is identified by the TIMESLOT
configuration parameter. The TIMESLOT configuration parameter identifies the physical port on the
Cisco ITP-L.
To provision the Cisco ITP-L links, use the following component:
Note
When provisioning, fully define all components (see Figure 2-2) before deploying a configuration.
Table 2-12 describes the C7 IP link configuration parameters that define each link. Table B-10 serves as
a form you can use to plan a single C7 IP link.
Table 2-12
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
DESC
Description
None
PRI
Priority
SS7 route priority. Enter an integer that is greater than 0. One (1) is the
highest priority level.
SESSIONSET
Session set
None
LNKSET
Link set
None
Linkset to which this link belongs. Enter the MML name of a previously
defined linkset.
SLC
Link code
TIMESLOT
Time slot
Time slot field for the C7 IP link. Identifies the physical WAN interface
card (WIC) slot, that is the SS7 serial port, of the Cisco ITP-L.
Value range: 0 through 3.
Description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-33
Chapter 2
Tip
Links are logical connections between a Cisco PGW 2200 Softswitch physical interface and another
device. You can assign multiple links to any interface. When assigning links, be sure to consider fault
tolerance. For example, placing all four links between the Cisco PGW 2200 Softswitch and one MGW
on the same interface results in a useless MGW if that interface fails.
This section describes how to plan for provisioning the following component types:
External nodes
IP links
The following sections describe how to plan for each of these components.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-34
OL-1110-23
Chapter 2
Note
If you are configuring a redundant system, you must define two redundant link manager links between
each Cisco PGW 2200 Softswitch and MGW. Each redundant link manager group must be associated
with a different port number and a different NASPATH, but the same EXTNODE.
Table 2-13 describes the external node configuration parameters. Table B-16 serves as a form you can
use to plan for each media gateway.
Table 2-13
MML Parameter
Name
Voice
Services
Provisioning
Tool
Parameter
Name
Default Value
Description
NAME
MML name
None
DESC
Description
None
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-35
Chapter 2
Table 2-13
MML Parameter
Name
Voice
Services
Provisioning
Tool
Parameter
Name
TYPE
Default Value
Description
None
Identifies the type of external node in the left column. Acceptable values
are shown in the left column. See Table 2-14 for a list of Type values for
Cisco PGW 2200 Softswitch software Release 9.6(1). The right
columns show the associated signaling type:
AS3600MGCPSGCPIPFASNASIUA
AS3660MGCPSGCPIPFASNASIUA
AS5200IPFASNAS
AS5300MGCPSGCPIPFASNASIUA
AS5350MGCPSGCPIPFASNASBSMV0IUA
AS5400MGCPSGCPIPFASNASBSMV0IUA
AS5800IPFASNAS
AS5850IPFASNAS
AS7200MGCPSGCPIPFASNAS
CAT8510MGCPSGCP
CAT8540MGCPSGCP
C2600MGCPSGCP IUA
H323EISUP
ITPM3UASUA
LS1010MGCPSGCP
MC3810MGCPIPFAS
MGCEISUP
MGX8260MGCPIPFASNAS
MGX8850MGCPSGCPIPFAS
RACLUSTER
SCPTCAPIP
SLTBSMV0
UNKNOWNUNKNOWN
ISDNSIGTYPE
ISDN Sig
Type
GROUP
Group
N/A
ISDN signaling type. Valid values are IUA or N/A (default is N/A). This
parameter is added in software Release 9.4(1).
M3UA/SUA group number. Value range: 0 for nodes that do not support
M3UA or SUA, or 1 through 100 for M3UA or SUA nodes. This
parameter is added in software Release 9.4(1).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-36
OL-1110-23
Chapter 2
Table 2-14
ExtNode
MML Type
External Node Types for Cisco PGW 2200 Softswitch Software Release 9.6(1)
SGCP
MGCP
AS5200
IPFAS
IUA
BRI
IPFAS
NAS
MGCP
ANNO
MGCP
IVR
SUA
Other
NAS
AS5300
SGCP
MGCP
IPFAS
IUA
NAS
MGCP
ANNO
MGCP
IVR
AS5350
SGCP
MGCP
IPFAS
IUA
NAS
MGCP
ANNO
MGCP
IVR
BSMV0
AS5400
SGCP
MGCP
IPFAS
IUA
NAS
MGCP
ANNO
MGCP
IVR
BSMV0
NAS
MGCP
ANNO
NAS
MGCP
ANNO
AS5800
IPFAS
AS5850
MGCP
IPFAS
MGCP
IPFAS
C1751
MGCP
IPFAS
IUA
BRI
C1760
MGCP
IPFAS
IUA
BRI
MGCP
IPFAS
IUA
BRI
C2610XM
MGCP
IPFAS
IUA
BRI
C2611XM
MGCP
IPFAS
IUA
BRI
C2620XM
MGCP
IPFAS
IUA
BRI
C2621XM
MGCP
IPFAS
IUA
BRI
C2650XM
MGCP
IPFAS
IUA
BRI
C2651XM
MGCP
IPFAS
IUA
BRI
C2691
MGCP
IPFAS
IUA
BRI
C2801
MGCP
IPFAS
IUA
BRI
C2811
MGCP
IPFAS
IUA
BRI
C2821
MGCP
IPFAS
IUA
BRI
C2851
MGCP
IPFAS
IUA
BRI
MGCP
IPFAS
IUA
C3640
MGCP
IPFAS
IUA
BRI
C3640A
MGCP
IPFAS
IUA
BRI
MGCP
IPFAS
IUA
BRI
C3725
MGCP
IPFAS
IUA
BRI
C3745
MGCP
IPFAS
IUA
BRI
C3825
MGCP
IPFAS
IUA
BRI
C3845
MGCP
IPFAS
IUA
BRI
AS7200
C2600
C3600
C3660
SGCP
SGCP
SGCP
SGCP
CAT8510
SGCP
MGCP
CAT8540
SGCP
MGCP
IUA
MGCP
IVR
NAS
NAS
NAS
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-37
Chapter 2
Table 2-14
ExtNode
MML Type
External Node Types for Cisco PGW 2200 Softswitch Software Release 9.6(1) (continued)
SGCP
MGCP
IPFAS
IUA
BRI
NAS
MGCP
ANNO
MGCP
IVR
SUA
Other
CCMCLUS
TER
N/A
H323
EISUP
ITP
SUA
LIMD
LS1010
LI
SGCP
MC3810
MGCP
MGCP
IPFAS
MGC
EISUP
MGX8260
MGX8850
M3UA
SGCP
MGCP
IPFAS
MGCP
IPFAS
NAS
SCP
TCAPIP
SLT
BSMV0
UNKNOW
N
UNKNOW
N
VISM
SGCP
MGCP
IPFAS
VXSM
SGCP
MGCP
IPFAS
IUA
MGCP
ANNO
M3UA,
H248
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-38
OL-1110-23
Chapter 2
Table 2-15
Voice Services
Provisioning
MML Parameter Tool Parameter
Name
Default Value
Name
Description
NAME
MML name
None
MDO
Enter a valid message definition object (MDO) file protocol name from
either the ISDNPRI or DPNSS protocol family.
EXTNODE
External node
None
Enter the external node name assigned to the media gateway you are
configuring.
SIDE
Side
network
Q.931 call model side. Enter user for user side or network for network
side. (Used only for IP FAS transport service.)
CUSTGRPID
Customer
group ID
0000
CUSTGRPTBL Customer
group table
0101
ABFLAG
A/B flag
CRLEN
Call reference
length
Call reference length. Enter 0 for DPNSS, 1 for one-byte call reference,
or 2 for two-byte call reference. (Used only for IP FAS transport
service.)
PATHSIZE
Path size
SESSIONSET
Session set
SIGSLOT
Signal slot
Signal slot. Physical slot on the MGW where the T1/E1 interface is
installed. (Used only for IPFAS.) Value range: 0 through 63.
SIGPORT
Signal port
Signal port. Physical port on the MGW of the T1/E1 interface on the
interface slot. (Used only for IPFAS.) Value range: 0 through 167.
SIGPORTSKIP
Signal ports
skipped
BACKUP
Backup
NO
Tip
When configuring your network, keep in mind that the naming convention and description you use need
to uniquely identify and thoroughly describe not only the component but also its source and destination.
Even though the name parameter is limited, use a description that will allow someone else to understand
the network well enough to scale or troubleshoot it.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-39
Chapter 2
Note
In the MGC node system, the same cards and interfaces can be used for communication with
Cisco ITP-Ls and media gateways. When configured this way, separate links are assigned for
Cisco ITP-L and media gateway communications.
Note
Table 2-16 describes configuration parameters you can use to configure network cards. Table B-1 serves
as a form you can use to plan network card configurations.
Table 2-16
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
SLOT
Slot
None
TYPE
Type
None
Description
DESC
Description
None
EN
Note
In the MGC node, the same cards and interfaces can be used for communication with Cisco ITP-Ls and
media gateways. When configured this way, separate links are assigned for Cisco ITP-L and media
gateway communications.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-40
OL-1110-23
Chapter 2
Note
Table 2-17
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
CARD
Ethernet
adapter
None
Identifies the card that supports this interface. Set this to the MML name
of a card that has already been defined.
DESC
Description
None
Description
Planning IP Links
The last step in planning media gateway control links is the planning of the links themselves. You must
identify each end of each link as follows:
At the Cisco PGW 2200 Softswitch end of each link, the link is associated with an Ethernet
interface, an IP address, and an IP port.
At the media gateway end of each link, the Cisco ITP-L is identified with an IP address and port.
Table 2-18 lists and describes the configuration parameters that define each link. Table B-23 serves as a
form you can use to plan a single IP link.
Table 2-18
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
DESC
Description
None
Description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-41
Chapter 2
Table 2-18
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
Description
IF
Enet line
interface
None
Ethernet interface to which this link connects. Enter the MML name of
a previously defined Ethernet interface, or the index of the Ethernet
interface for SNMP.
PORT
Port
None
Local port number of link interface on the Cisco PGW 2200 Softswitch.
Enter any valid IP port number greater than 1024. (For MGCP and
SGCP, the recommended setting is 2427.)
PRI
Priority
PEERADDR
Peer address
0.0.0.0
PEERPORT
Peer port
IPADDR
IP address
None
SVC
IP signaling
Services
None
NEXTHOP
Next hop
0.0.0.0
NETMASK
Net mask
255.255.255.
255
The four-octet value defining the part of the PEERADDR (in dot
notation) that is treated as the network address. The upper 28 bits are the
network address and the lower 4 bits are the host address. Value range:
128.0.0.0 through 255.255.255.255.
Note
NEXTHOP and NETMASK are used only if the Cisco PGW 2200 Softswitch is on a different subnet
than the Cisco PGW 2200 Softswitch and ITP-L are located. However, if the local IP address and peer
IP address are on the same subnet, set NEXTHOP to 0.0.0.0.
Note
For proper operation of redundant IP links (using MGCP signaling) connected to an IP media gateway,
configure the IP gateway with the IP address of the VISM card on the IP media gateway. Both of these
IP addresses are typically the default network gateway for each VLAN. Ensure the IP netmask matches
the VISM card netmask of the IP links connecting to the IP media gateway and is not the netmask of the
default gateway.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-42
OL-1110-23
Chapter 2
MML NameTCPLINK
Parameter MML
Name
Parameter Description
NAME
Unique component
name used in MML
commands
DESC
Component description
TYPE
IPADDR
Local IP address
PORT
Port number
PEERADDR
Highest priority
destination address
PEERPORT
EXTNODE
IPROUTE
NAME
EXTNODE
The following rules apply when you are creating or editing QSIG/Q.931 Over BRI Backhaul signaling
services:
You must define the TYPE parameter as PRI. If the TYPE parameter is not defined as PRI when the
TCPLINK is added/edited, a warning is issued. If the TYPE parameter is not defined as PRI when
the provisioning session is copied or deployed, an error message is generated and the copy or
deployment is stopped.
You must define the TCPLINK parameter with the same EXTNODE attribute that its associated
BRIPATH has. If the TCPLNK is not defined when the BRIPATH is added/edited, a warning is
issued. If the TCPLINK is not defined when the provisioning session is copied or deployed, an error
message is generated and the copy or deployment is stopped.
If the TCPLINK with the same EXTNODE value as the BRIPATH is deleted, a warning message is
issued to inform you that the BRIPATH must also be deleted. If the BRIPATH is not deleted when
the provisioning session is copied or deployed, an error message is generated and the copy or
deployment is stopped.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-43
Chapter 2
Only two combinations of local IP address and port number can be used per
Cisco PGW 2200 Softswitch. Once you have identified two unique local IP address and port number
combinations, all subsequent Backhaul TCP links must use one of those combinations.
MML NameBRIPATH
The QSIG/Q.931 Over BRI Backhaul signaling service component structure is shown in Table 2-20.
Table 2-20
Parameter MML
Name
Parameter Description
NAME
Unique component
name used in MML
commands
DESC
Component description
EXTNODE
MDO
ETS_300_102
Q931
ETS_300_172
SIDE
CUSTGRPID
VNET ID
CRLEN
Note
NAME
EXTNODE
The following rules apply when you are creating or editing QSIG/Q.931 Over BRI Backhaul signaling
services:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-44
OL-1110-23
Chapter 2
You must define the TCPLINK parameter with the same EXTNODE attribute that its associated
BRIPATH has. If the TCPLNK is not defined when the BRIPATH is added/edited, a warning is
issued. If the TCPLINK is not defined when the provisioning session is copied or deployed, an error
message is generated and the copy or deployment is stopped.
If the TCPLINK with the same EXTNODE value as the BRIPATH is deleted, a warning message is
issued to inform you that the BRIPATH must also be deleted. If the BRIPATH is not deleted when
the provisioning session is copied or deployed, an error message is generated and the copy or
deployment is stopped.
A maximum of 2000 BRIPATHs can be provisioned on your Cisco PGW 2200 Softswitch.
At the Cisco PGW 2200 Softswitch end of each link, the link is associated with a port, an IP address,
and a peer address.
The PEERPORT and PEERADDRESS must be unique for each backhaul IP link created.
This command will generate a session set, which is one or two (if IPADDR2 and PEERADDR2 are
specified) backhaul IP links. The names are NAME-1 and NAME-2. The DESCRIPTIONs are
Session Set NAME Backhaul Link 1 and Session Set NAME Backhaul Link 2.
All commands (add, edit, delete, and retrieve) are performed against the pair by only specifying the
NAME. Retrieving a session set displays the backhaul IP links (there may only be one) for the
session set. Retrieving all session sets displays all backhaul IP links.
The session set TYPE must be IPFAS for IPFAS session sets.
IP Addresses cannot be split across session sets. For example if SET 1 has IP_Addr1 and IP_Addr2,
then SET 2 cannot have IP_Addr1 and IP_Addr3.
If IPADDR2 or PEERADDR2 is specified, then they must both be specified. You cannot have one
local address and two remote addresses or two local addresses and one remote address.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-45
Chapter 2
PEERADDR1 and PEERADDR2 must be different, except when the EXTNODE is a VISM
(MGX8850).
The PORT attribute cannot be set to the same value as the PORT attribute of any ASSOCIATION,
IPLNK, or SIPLNK.
The PORT attribute cannot be set to the same value as the PORT attribute of another SESSIONSET
with a different TYPE value. That is, the PORT value of a BSMV0 SESSIONSET cannot be the
same as the PORT value of an IPFAS SESSIONSET.
When IPROUTE1 or IPROUTE2 is specified, the IP address value from the PEERADDR1 or
PEERADDR2 attribute must be the same as the DESTINATION and NETMASK attributes to ensure
the IPROUTE is valid.
When IPROUTE1 is specified, the IPADDR must match the IPADDR1 of the session set.
Similarly, when IPROUTE2 is specified, the IPADDR must match the IPADDR2 of the session set.
When IPROUTE1 or IPROUTE2 is not specified, the IP address value for the PEERADDR1 or
PEERADDR2 attribute must match the defined IPROUTES to ensure it should not be assigned to
one of the IPROUTEs. If the PEERADDR is on the same subnet as an IPROUTE, then the link
should use that IPROUTE.
Another IPLNK, SESSIONSET, or ASSOCIATION with a different EXTNODE cannot use the same
PEERADDR value.
Table 2-21 lists and describes the configuration parameters that define each session set. Table B-27
serves as a form you can use to plan a single session set.
Table 2-21
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
IPADDR1
IP address 1
None
IPADDR2
IP address 2
None
PORT
Port
None
PEERADDR1
Peer address 1
0.0.0.0
PEERADDR2
Peer address 2
0.0.0.0
PEERPORT
Peer port
Description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-46
OL-1110-23
Chapter 2
Table 2-21
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
EXTNODE
External node
None
NEXTHOP1
Next hop 1
0.0.0.0
NETMASK1
Net mask
NEXTHOP2
Next hop 2
0.0.0.0
NETMASK2
Net mask 2
TYPE
Type
Description
Table 2-22
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
DESC
Description
None
PRI
Priority
SVC
IP signaling
Services
None
SESSIONSET
Session set
None
TCPLINK
TCP Link
None
Description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-47
Chapter 2
Table 2-22
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
SIGSLOT
Signal slot
Description
Signal slot. Physical slot on the MGW where the T1/E1 interface is
installed. Value range: 0 through 63.
Note
SIGPORT
Signal port
Signal port. Physical port on the MGW of the T1/E1 interface on the
interface slot. (Used only for IPFAS.) Value range: 0 through 167.
Note
SUBUNIT
Sub unit
This parameter identifies the subunit value on the external node when
you create a trunk with a VISM or IOS gateway endpoint. When you
create a BRI trunk, this parameter identifies the subunit of the slot.
Values are: 0, 1, 2, 3, 99.
Note
Note
The following rules apply when you are creating or editing D-channels:
Backup D-channels for QSIG/Q.931 Over BRI Backhaul signaling services are not supported.
The priority for QSIG/Q.931 Over BRI Backhaul D-channels should be set to 1.
TCP links are used only in support of QSIG/Q.931 Over BRI Backhaul D-channels.
Up to 1000 D-channels can be provisioned against a single IP address and port combination used by
your Backhaul TCP links. Since the Cisco PGW 2200 Softswitch supports a maximum of two IP
address and port combinations, you can provision a maximum of 1000 D-channels for a QSIG/Q.931
Over BRI Backhaul signaling service.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-48
OL-1110-23
Chapter 2
Table 2-23
MML
Parameter
Name
Parameter Description
NAME
DESC
Component description
SVC
PARAMETER
DIRECTION
1 = NOA
NUMBER
INTNOA
EXTNOA
The value of the NOA field in the Any 7-bit value, 0 through 127, no
protocol message.
restrictions.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-49
Chapter 2
Table 2-24
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
DESC
Description
None
BEARERCAP
Bearer
Capability
Name
None
Description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-50
OL-1110-23
Chapter 2
Table 2-25 lists the nailed trunk MML command parameter definitions and their associated values.
Table 2-25
MML Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
Name
Trunk group ID. A numeric identifier for the trunk group. Value range: an integer
from 1 through 65535.
SRCSVC
Source service
Used to look up the source service component ID. The MML name of a previously
defined signaling service.
SRCSPAN
Source span ID Corresponds to the source span ID. Value range: an integer from 1 through 65535 or
ffff (default). This value is converted from decimal to hexadecimal, except when the
value is ffff.
SRCTIMESLOT
Source time
slot
Corresponds to the source time slot. Value range: an integer from 0 through 16384.
This value is converted from decimal to hexadecimal, except when the value is ffff.
DSTSVC
Destination
service name
Used to look up the destination service component ID. The MML name of a
previously defined signaling service.
DSTSPAN
Destination
span ID
Corresponds to the destination span ID. Value range: an integer from 1 through 65535
or ffff (default). This value is converted from decimal to hexadecimal, except when
the value is ffff.
DSTTIMESLOT
Destination
time slot
Corresponds to the destination time slot. Value range: an integer from 0 through
16384. This value is converted from decimal to hexadecimal, except when the value
is ffff.
SPANSIZE
Span size
Span size. Indicates the number of trunks per span. Value: 1 (default) through 24 for
T1, or 1 through 31 for E1.
The MML command format used to import a customer-created nailed trunk file is:
prov-add:files:name="BCFile",file="trunkCust.dat",action="import"
This imports the customer-created file that uses #format2. The imported file format would appear as:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-51
Chapter 2
1
3
The #format2 fields are Trunk ID, Source Service CompId, Source Span, Source Time slot, Destination
Service CompId, Destination Span, and Destination Time slot.
Configuring Profiles
Profiles allow one or more property values to be overridden and then applied as a customized group
called a profile. Two profile types exist:
For example, a property that belongs to a profile can be added to a single trunk group or repeatedly to
many trunk groups without having to provision all the parameters for each trunk group.
Table 2-26 lists the profile MML command parameter definitions and their associated values.
Table 2-26
MML Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
Name
Unique name for this profile name. Enter as many as 20 alphanumeric characters and
enclose in straight quotes. Hyphens (-) can be used.
TYPE
Profile Type
VARIANT
Variant
Variant name, as many as 20 alphanumeric characters (only used for ISUP timer
profiles), listed in Appendix A, Protocol Variants.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-52
OL-1110-23
Chapter 2
Table 2-27
MML Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
allowCRMCRA
allowCRMCR
A
Indicates whether or not to allow using the Circuit Reservation Message (CRM) and
Circuit Reservation Acknowledgement message (CRA). Acceptable values are: 0 for
no, or 1 (default) for yes.
allowEXM
allowEXM
Indicates whether or not to allow using the Exit Message (EXM). Acceptable values
are: 0 for no, or 1 (default) for yes.
atpInclude
atpInclude
Indicates whether or not to include the Access Transport Parameter in the IAM.
Acceptable values are: 0 (default) for no, or 1 for yes.
carrierSelectInclude carrierSelectIn
clude
Indicates whether or not to include the carrier selection information parameter in the
IAM. Acceptable values are: 0 (default) for no, or 1 for yes.
cgpnInclude
cgpnInclude
Indicates whether or not to include the called party number (CgPN) in the IAM on the
originating trunk group. Acceptable values are: 0 for no, or 1 (default) for yes.
cgpnPres
cgpnPres
chnNonGeo
chnNonGeo
Indicates whether or not to include the Charge Number in the IAM on all calls to
non-geographic numbers. The geographic nature of a number is determined by the
Address Class analysis result value. Acceptable values are: 0 (default) for no, or 1 for
yes.
chnOlipInclude
chnOlipInclude Indicates whether or not to include the pair of Charge Number and Originating Line
Information Parameters as a pair in the IAM. Acceptable values are: 0 (default) for
no, or 1 for yes.
cipInclude
cipInclude
Indicates whether or not to include the Carrier Identification parameter (CIP) in the
IAM. Acceptable values are: 0 (default) for no, or 1 for yes.
cipNonGeo
cipNonGeo
Indicates whether or not to include the CIP in the IAM on all calls to non-geographic
numbers. Acceptable values are: 0 (default) for no, or 1 for yes.
confusion
confusion
Flag indicating whether or not to send the confusion message when an unrecognized
message type is received. Acceptable values are: 0 (default) for no, or 1 for yes.
congProc
congProc
Indicates the procedure to follow when there is congestion on ISUP circuits; choices
are: alternate routing or blocking. This value is taken from the originating trunk group
and used when re-attempting occurs. Acceptable values are: BLK (default) for
blocking, or ALTRTE for alternate routing.
defaultBC
defaultBC
Indicates the default bearer capability; which pertains to incoming SS7 trunk groups.
Used to code the User Service Information parameter in the outgoing IAM message.
Acceptable values are: SPEECH (default), or 3_1_KHZ.
gapInclude
gapInclude
Indicates whether or not to allow using the Generic Address Parameter in the IAM.
Acceptable values are: 0 (default) for no, or 1 for yes.
gnInclude
gnInclude
Indicates whether or not to include the Generic Name in the IAM. Acceptable values
are: 0 (default) for no, or 1 for yes.
Note
This property applies to ANSI SS7 only. The applicable MDO files are
ANSISS7_2K, ANSISS7_92, ANSISS7_C2, ANSISS7_C3, ANSISS7_E1,
ANSISS7_STANDARD, and GR317.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-53
Chapter 2
Table 2-27
MML Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
hopOn
hopOn
Flag indicating whether or not to turn the hop counter on. Acceptable values are: 0
for no, or 1 (default) for yes.
jipDefault
jipDefault
jipInclude
jipInclude
Indicates whether or not to include the Jurisdiction Information Parameter (JIP) in the
IAM. Acceptable values are: 0 (default) for no, or 1 for yes.
notificationInclude
notificationIncl Indicates whether or not to include the notification parameter in the Call Progress
ude
(CPG) message. Acceptable values are: 0 (default) for no, or 1 for yes.
ocnInclude
ocnInclude
redirCapInclude
redirCapInclud Indicates whether or not to include the Redirect Capability in the IAM. Acceptable
e
values are: 0 (default) for no, or 1 for yes.
Indicates whether or not to include the Original Called Number in the IAM.
Acceptable values are: 0 (default) for no, or 1 for yes.
redirCounterInclude redirCounterIn Indicates whether or not to include the Redirect Counter in the IAM. Acceptable
clude
values are: 0 (default) for no, or 1 for yes.
redirInfoInclude
redirInfoInclud Indicates whether or not to include the Redirection Info in the IAM. Acceptable
e
values are: 0 (default) for no, or 1 for yes.
rnInclude
rnInclude
serviceCodeInclude
serviceCodeInc Indicates whether or not to include the Service Code parameter in the IAM.
lude
Acceptable values are: 0 (default) for no, or 1 for yes.
transReqInclude
transReqInclud Indicates whether or not to include the transaction request parameter in the IAM.
e
Acceptable values are: 0 (default) for no, or 1 for yes.
unavailProc
unavailProc
Indicates whether or not to include the Redirecting Number in the IAM. Acceptable
values are: 0 (default) for no, or 1 for yes.
Indicates the procedure to follow when there are no available ISUP circuits; choices
are: alternate routing or blocking. This value is taken from the originating trunk group
and used when re-attempting occurs. Acceptable values are: BLK (default) for
blocking, or ALTRTE for alternate routing.
The following is an MML command format used to attach a profile to a trunk group:
prov-add:trnkgrpprof:name="1000",grprofile="profile1"
Note
A profile must be created before a trunk group can be associated with the profile.
Table 2-28 lists the profile MML command parameter definitions and their associated values.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-54
OL-1110-23
Chapter 2
Table 2-28
MML Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
Name
Unique name for this profile name. Enter as many as 20 alphanumeric characters and
enclose in straight quotes. Hyphens (-) can be used.
Unique profile type name, as many as 20 alphanumeric characters.
Note
A profile must be created before a signaling service can be associated with the profile.
AtmConnectionType
The trunk group property AtmConnectionType populates the connection type parameter (ct:) in local
connection option parameters. This property is read for both originating and terminating legs of all
ATM-switched calls.
Applying Cisco PGW 2200 Softswitch influence, that is, bias, in the profile negotiation process is
hierarchical and is applied through using the GWDefaultATMProfile property at the trunk group level,
and then by analysis results in A-number or B-number analysis.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-55
Chapter 2
Note
ATM profile negotiation can work over Extended ISUP (EISUP) too.
Valid values: 1 (AAL1), 2 (AAL1_SDT), 3 (AAL1_UDT), 4 (AAL2), 5 (AAL 3/4), 6 (AAL5)
Default value: 4 (AAL2)
Level 0
At level 0, nothing is defined on the Cisco PGW 2200 Softswitch. That is, no trunk group properties and
no analysis results are defined. This means that the decision for the profile used for the call is made at
the gateway level. However, the Cisco PGW 2200 Softswitch, using MGCP messages, negotiates
between ingress and egress gateway. This is the only role of the Cisco PGW 2200 Softswitch at this
level.
Level 1
At level 1, the Cisco PGW 2200 Softswitch can influence the profile negotiation by the trunk group
property GWDefaultATMProfile configuration on the originating side and even on the terminating side.
With GWDefaultATMProfile configured on the originating side, the Cisco PGW 2200 Softswitch offers
to the originating gateway the profile list extracted from this property within the CreateConnection
(CRCX) request. The originating gateway then matches this received list with its own ActiveProfileList
to produce a new list composed of the matched profiles. This list is returned by the gateway to the
Cisco PGW 2200 Softswitch in the SDP information returned in the CRCX Acknowledgement.
If the terminating side trunk group has this property configured, the retrieved profile list is sent along
with the SDP profile list (received previously from the originating side) to the terminating-side gateway.
If no terminating trunk group property is configured, then only the originating-side SDP information is
sent.
Note
With regard to the terminating side, the trunk group property profile list is read only in the absence of
any level 2 results from A-number or B-number analysis.
The Cisco PGW 2200 Softswitch passes the originating SDP and any retrieved terminating profile list
to the terminating-side gateway in another CRCX message. The egress gateway then matches the
received list with its own ActiveProfileList to develop a final list. The egress gateway then chooses from
this resultant final profile list, which is transported back to the Cisco PGW 2200 Softswitch in the
CRCX Acknowledgement message.
Finally, the Cisco PGW 2200 Softswitch passes this profile choice to the originating gateway in an
MDCX message. Once this exchange has been carried out, only one profile exists for both the ingress
and egress gateways, which is the result of profile negotiation (influenced by the
Cisco PGW 2200 Softswitch applying a bias for the SLA between those gateways).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-56
OL-1110-23
Chapter 2
Level 2
At level 2, the Cisco PGW 2200 Softswitch can apply another layer of SLA bias to profile negotiation.
This additional layer provides the capability of provisioning ATM_ORIG_PROFILE and
ATM_TERM_PROFILE results within the Cisco PGW 2200 Softswitch A-number and B-number
analysis functions. These results contain the same data words and both results deliver a profile list to
bias negotiation on either the ingress or egress gateway.
Dataword2 in the result type provides a mandatory or preferred indication for the profile list, which
determines the actions that must take place. If dataword2 is set to mandatory, then the profile list from
the previous stages is ignored and the egress gateway supports a profile from the list identified by
dataword1. If dataword2 is set to preferred, then the profile list identified by dataword1 is retrieved and
the existing list (from previous stages, if collected) is appended to the profile list, thus forming a new
list to forward to the gateway.
Note
If results are collected from A-number analysis and then from B-number analysis, B-number analysis
can further adjust or overwrite the existing profile list created by the A-number analysis. This provides
the possibility for there being two sublevels within the level 2 capability.
GWDefaultATMProfile
When the Cisco PGW 2200 Softswitch is acting as a Call Agent making ATM voice connections
between two gateways, it must provide the capability to influence the profile negotiation between the
two sides to the gateway.
To accomplish this profile negotiation, a list of profiles supported by the code image on the gateway, but
is refined by configuration according to the prevailing network Service Level Agreement (SLA). The
Cisco PGW 2200 Softswitch applies the SLA changes or refinements to the profile list rather than apply
them as configuration changes on the gateways. Thus, the gateways contain a list of profiles that their
respective code images can support. The Cisco PGW 2200 Softswitch retrieves a provisioned profile list
from the GWDefaultATMProfile trunk group property or as the ATM_ORIG_PROFILE or
ATM_TERM_PROFILE result delivered from A-number (Calling number) or B-number (Called
number) analysis. This list is then passed over MGCP to the gateway to bias profile negotiation.
While establishing the connection between two gateways, the originating gateway profile list is refined
by ANDing with a new profile sent from the Cisco PGW 2200 Softswitch in the originating side CRCX
message. The resultant profile list is passed in the Session Description Protocol (SDP) to the terminating
gateway. Also, the Cisco PGW 2200 Softswitch can optionally produce another profile choice to bias the
profile on the terminating gateway according to the SLA. This profile accompanies other data sent in the
CRCX message to the terminating gateway. Upon receiving this profile, the terminating gateway ANDs
the SDP profile with any existing received profiles and then ANDs the profile list with the existing
gateway ActiveProfileList to produce a resultant profile list. From the resultant profile list, the gateway
chooses a profile entry and passes back the profile list to the originating side.
The Cisco PGW 2200 Softswitch produces a profile choice list (ProfileList1) that is sent to the
originating gateway in the first CRCX command. The originating gateway forms a new list by ANDing
the received profile with its own ActiveProfileList and generates ProfileList2, which consists only of the
profile choices that were present in both lists. This profile information is embedded in the SDP that is
sent back to the Cisco PGW 2200 Softswitch in the CRCX Acknowledgement.
If the Cisco PGW 2200 Softswitch also has an SLA profile for the terminating gateway (ProfileList3),
it is added to the profile list in the SDP and both profiles are sent to the terminating gateway in another
CRCX message. Upon receiving this profile, the terminating gateway ANDs all three lists to produce a
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-57
Chapter 2
single profile list that is refined by the SLA conditions from both sides. The terminating gateway makes
a choice from the final profile list that is then sent to the Cisco PGW 2200 Softswitch in the CRCX
Acknowledgement message and the profile is then sent to the originating gateway in an MDCX message.
Once this process has been carried out, a single profile exists for both the originating and terminating
gateway, which is the result of profile negotiation between the two gateways by the
Cisco PGW 2200 Softswitch and application of the prevailing SLAs.
The trunk group property GWDefaultATMProfile provides, on a per trunk group basis, an initial list of
profiles for use in ATM gateway profile negotiation. This property contains a list of profile choices
separated by semi-colons, that influences ATM gateway profile negotiation. If GWDefaultATMProfile
is set to NULL (default), then there is no profile list negotiation bias applied from the trunk group level.
Valid values: NULL, <Profile1>;<Profile2>;<ProfileN>
Default value: NULL
Note
This property is added in propSet.xml.dat for provisioning, added in properties.mod for migration, and
added in tpTrunkgroup for importing and exporting.
Trunk group fileUsed to define the trunk group and the signal path controlling the trunk group
Trunk fileUsed to define the trunks (also called bearer channels) associated with a trunk group.
The trunk file is a switched trunk.
You can either use MML commands to import a trunk group file or you can use the following MML
command to populate a trunk group one line at a time.
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
Name
Trunk group name. A numeric identifier for the trunk group. An integer from 1 through
9999.
CLLI
CLLI
Common language location identifier that identifies the trunk group. This can be up to 11
alphanumerical digits.
SVC
Signal service
The MML name of the signaling service associated with or controlling the trunk group.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-58
OL-1110-23
Chapter 2
Table 2-29
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
TYPE
Type
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-59
Chapter 2
Table 2-29
MML
Parameter
Name
SELSEQ
Voice Services
Provisioning
Tool Parameter
Name
Description
Selection
sequence
Specifies the trunk selection sequence. The Cisco PGW 2200 Softswitch uses the CICs
within a trunk group according to the sequence specified by the SELSEQ value. You can
provision this value to reduce the chance of glare when the system selects a trunk.
ASC = Ascending. The system selects the available CICs in ascending order starting from
the lowest CIC number (for example, 1, 2, 3 ...).
CASC = Cyclic ascending. The system selects the next available CIC in ascending order
based on the most recently selected CIC. For example, if the most recently selected CIC is
CIC 5, the system selects CIC 6, even if CIC 1 is available.
CDESC = Cyclic descending. Similar to CASC, but in descending order based on the most
recently selected CIC. For example, if the last selected CIC is number 18, the system selects
CIC 17, even if CIC 31 is available.
DESC = Descending. Similar to ASC, but in descending order starting from the highest CIC
number (for example, 31, 30, 29 ...).
EASC = Even ascending, then odd ascending. The system selects the first available even CIC
in ascending order (for example, 2, 4, 6 ...). If no even CIC is available in the trunk group,
the system selects the first available odd CIC in ascending order (for example, 1, 3, 5 ...).
EDECS = Even descending, then odd descending. Similar to EASC, but in descending order.
The system selects the first available even CIC in descending order (for example, 30, 28,
26 ...). If no even CIC is available in the trunk group, the system selects the first available
odd CIC in descending order (for example, 31, 29, 27 ...).
ITU2 = ITU method 2. The system selects the trunk according to the procedure in ITU-T
Recommendation Q.764, paragraph 2.9.1.3 Method 2.
LIDL = Least idle (default). The system selects the least idle (most recently used) CIC.
MIDL = Most idle. The system selects the most idle (least recently used) CIC.
OASC = Odd ascending, then even ascending. The system selects the first available odd CIC
in ascending order (for example, 1, 3, 5 ...). If no odd CIC is available in the trunk group,
the system selects the first available even CIC in ascending order (for example, 2, 4, 6...).
ODESC = Odd descending, then even descending. Similar to OASC, but in descending order.
The system selects the first available odd CIC in descending order (for example, 31, 29,
27 ...). If no odd CIC is available in the trunk group, the system selects the first available
even CIC in descending order (for example, 30, 28, 26 ...).
RDM = Random. The system selects a CIC at random.
Caution
When the trunk selection sequence (SELSEQ) is set to its default value, LIDL
(least idle), there is a risk that the Cisco PGW 2200 Softswitch will select a
significant number of temporarily unavailable trunks, which causes calls to fail.
This kind of call failure can happen when an overloaded media gateway responds
to the Cisco PGW 2200 Softswitch with a temporary MGCP error (400 to 499),
or the Cisco PGW 2200 Softswitch does not receive a response from the media
gateway in time. We recommend that you set SELSEQ to a value other than LIDL.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-60
OL-1110-23
Chapter 2
Table 2-29
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
QABLE
Queuable
Determines if queuing is used on the trunk during call processing. Value range: Y for yes or
N for no (default).
In addition to the trunk group parameters listed in Table 2-29, additional properties can be set or changed
in the text file. To add multiple trunk groups, refer to the Adding Multiple Trunk Groups and Bearer
Channels section on page 5-41. Table 2-30 lists the trunk group property MML parameter definitions
and their associated values. For a description and provisioning order in which they appear in the VSPT
Configuration Editor, see Table 3-18 in Chapter 3, Provisioning with the Cisco Voice Services
Provisioning Tool.
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
NAME
Trunk Group
Name
Unique number (up to seven digits) assigned to each trunk group that is used by
route analysis. (The string tg- is pre-pended to this number to create the MML
name of the trunk group used in components.dat yielding an MML name of no more
than 10 characters.)
CLLI
CLLI
Common language location identifier that identifies the trunk group. Any 11 or
fewer alphanumeric characters.
SVC
Signaling
Service
The MML name of a previously defined SS7, IPFAS, or FAS signaling service
associated with or controlling the trunk group.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-61
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
TYPE
Trunk Type
QABLE
Queuable Type Determines if queuing is used on the trunk during call processing. Value range: Y
for yes or N for no (default).
RingNoAnswer
Ring No
Answer
Ring no answer. Indicates the time, in seconds, ringing is allowed to occur. Value
range: 0 through 600, in seconds. The default setting is 255.
Note
With patch CSCOnn015 installed, this property becomes the TO-02 (Time
Out 02) timer for the BTNUP protocol variant. The TO-02 timer is for
non-receipt of the Answer message and starts upon receipt of the Answer
Complete message. The TO-02 timer interval is the time, in seconds, before
the call is released. Value range: is 1 to 12 minutes (180 seconds is the
default value). The TO-02 timer is cancelled upon receipt of the Answer
message, Clear message, or Release message.
GLARE
Glare control
Glare control. Glare is a collision that occurs when two network nodes
simultaneously attempt to reserve the same channel. Values are: 0 (no handling)
(default), 1 (always), 2 (even/odd), or 3 (no control).
CotPercentage
COT
percentage
Determines the percentage of calls on the trunk upon which a continuity test is
performed. Value range: 0 through 100.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-62
OL-1110-23
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
Selseq
Select
Sequence
Specifies the trunk selection sequence. The Cisco PGW 2200 Softswitch uses the
CICs within a trunk group according to the sequence specified by the SELSEQ
value. You can provision this value to reduce the chance of glare when the system
selects a trunk.
ASC = Ascending. The system selects the available CICs in ascending order starting
from the lowest CIC number (for example, 1, 2, 3 ...).
CASC = Cyclic ascending. The system selects the next available CIC in ascending
order based on the most recently selected CIC. For example, if the most recently
selected CIC is CIC 5, the system selects CIC 6, even if CIC 1 is available.
CDESC = Cyclic descending. Similar to CASC, but in descending order based on
the most recently selected CIC. For example, if the last selected CIC is number 18,
the system selects CIC 17, even if CIC 31 is available.
DESC = Descending. Similar to ASC, but in descending order starting from the
highest CIC number (for example, 31, 30, 29 ...).
EASC = Even ascending, then odd ascending. The system selects the first available
even CIC in ascending order (for example, 2, 4, 6 ...). If no even CIC is available in
the trunk group, the system selects the first available odd CIC in ascending order
(for example, 1, 3, 5 ...).
EDECS = Even descending, then odd descending. Similar to EASC, but in
descending order. The system selects the first available even CIC in descending
order (for example, 30, 28, 26 ...). If no even CIC is available in the trunk group,
the system selects the first available odd CIC in descending order (for example, 31,
29, 27 ...).
ITU2 = ITU method 2. The system selects the trunk according to the procedure in
ITU-T Recommendation Q.764, paragraph 2.9.1.3 Method 2.
continued ...
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-63
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
Selseq
Select
Sequence
... continued:
LIDL = Least idle (default). The system selects the least idle (most recently used)
CIC.
MIDL = Most idle. The system selects the most idle (least recently used) CIC.
OASC = Odd ascending, then even ascending. The system selects the first available
odd CIC in ascending order (for example, 1, 3, 5 ...). If no odd CIC is available in
the trunk group, the system selects the first available even CIC in ascending order
(for example, 2, 4, 6...).
ODESC = Odd descending, then even descending. Similar to OASC, but in
descending order. The system selects the first available odd CIC in descending
order (for example, 31, 29, 27 ...). If no odd CIC is available in the trunk group, the
system selects the first available even CIC in descending order (for example, 30, 28,
26 ...).
RDM = Random. The system selects a CIC at random.
Caution
When the trunk selection sequence (SELSEQ) is set to its default value,
LIDL (least idle), there is a risk that the Cisco PGW 2200 Softswitch will
select a significant number of temporarily unavailable trunks, which
causes calls to fail. This kind of call failure can happen when an
overloaded media gateway responds to the Cisco PGW 2200 Softswitch
with a temporary MGCP error (400 to 499), or the Cisco PGW 2200
Softswitch does not receive a response from the media gateway in time.
We recommend that you set SELSEQ to a value other than LIDL.
VSF
VSF Priority
Virtual switch fabric priority. Determines if the gateway attempts to find a trunk on
the same gateway as the incoming trunk or on any available trunk. Values are: 0 (no)
(default) or 1 (yes).
SatelliteInd
Satellite
Satellite indicator. Indicates if the trunk is going over a satellite. Values are 0 (no)
(default) or 1 (yes).
Npa
Numbering
Plan Area
Numbering Plan Area. Indicates the NPA code associated with the incoming trunk
group. Value range: 0 (none) (default), or a 3-digit code from 200 through 999.
CustGrpId
Customer
group ID
Customer group ID. The ID of the customer associated with this trunk group. Value
range: 0 (if not defined) or any 4-character alphanumeric string.
CompressionType
Compression
Type
Compression type. Identifies the G.711 compression type used on the trunk. After
the fax or modem tone has been detected by the MGW, select the proper
compression type. Values are: 0 (none), 1 (mu-law) (default), 2 (A-law), or 3 (clear
channel).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-64
OL-1110-23
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
EchoCanRequired
Echo Canceller Echo Canceller Required. Specifies whether to send a modify-connection message
Required
(MDCX) for echo control. Enter a value of 0 or 1 for EchoCanRequired on the trunk
group or sigpath.
The Cisco PGW 2200 Softswitch follows the following procedure for an SS7
terminated call after the call is answered. If the Cisco PGW 2200 Softswitch
receives a call-in-progress message (CPG) with backward call indicators (BCI)
from the SS7 side, it takes the specified action.
If EchoCanRequired=1:
If the echo device indicator = 0 in BCI, send MDCX with e: on
If the echo device indicator = 1 in BCI, send MDCX with e: off
If EchoCanRequired=0 (default):
Do not send an MDCX for echo control
ExtCOT
External COT
External continuity test. Indicates the type of COT handling for the specified
destination. Values are: 0no COT, loop (default), or transponder.
DetectFaxModemTon
e
Detect Fax
Modem Tone
Detect Fax modem tone. Indicates if Fax modem tone is to be detected. Used for
MGCP connection protocol. Values are: 0 (no tone detection notification) or 1
(request fax or modem tone detection from the MGW.
MaxACL
Maximum
ACL
Maximum automatic congestion level. The Cisco PGW 2200 Softswitch indicates
its congestion level (if it is greater than 0) in the ISUP release message. Values: 0,
2, or 3 (default).
ACLDuration
ACL Duration
Automatic congestion level duration. When the Cisco PGW 2200 Softswitch
receives ACL indication from a linked switch, the Cisco PGW 2200 Softswitch
assumes ACL is in effect for the duration specified (in seconds). Value range: Any
value greater than 0 (5 is the default).
ACCRespCntlInhibit
ACL Response Automatic congestion control response inhibit. Enables or disables the ACC
Control Inhibit control procedures based on the ACL value received by the
Cisco PGW 2200 Softswitch from a linked switch. Values are: 0 (default) or 1.
IsupTransparencyDisa ISUP
bled
Transparency
Disabled
AOCEnabled
AOC Enabled
Advice of charge (AOC). Determines whether or not AOC handling is applied to the
current call. Values are: 0 (AOC not enabled) (default) or 1 (AOC enabled).
CarrierScreening
Carrier
Screening
OrigCarrierId
Originating
Carrier ID
Originating carrier ID. Supports the Carrier Screening capability as handled in the
protocol. This property supplies the CarrierID digit string for the trunk group that
can be referenced to any CarrierID received in the incoming message. Value range
is: 0 through 99999 (00 is the default).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-65
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
NotifySetupComplete Notify Setup
Complete
NetworkType
Network Type
Notify setup complete. Used for notifying the Asynchronous Notification task.
When the Cisco PGW 2200 Softswitch detects that the property
NotifySetupComplete is set to true, it then waits for both ChanSeized and
ChanNotify on the terminating side before sending ChanSeizeAck to the internal
call manager. Values are: 0 (default) or 1.
In software Release 9.5(2), NotifySetupComplete changed to NetworkType.
NetworkType populates the network type parameter (nt:) in local connection
parameters. This property is read for both originating and terminating legs of all
calls. Based on this property, the Cisco PGW 2200 Softswitch software determines
if the underlying network is ATM or IP. Based on the network type retrieved,
various network-specific parameters (for example, for ATM networks, profiles are
sent down) are sent down to gateways. Valid values: 0 (IP), 1 (ATM), or 2 (IN)
Default value: 0 (IP)
PackageType
Package Type
Package type. Determines MDL MGCP message handling according to the CAS
trunk group package. Value range: any alphabetical string.
Default: BL
ACCRespCatName
ACC Response Automatic congestion control response category name. Specifies the ACC
Category
Response Controls listed in the ACC Response Category table. Value range: any
character string. Default: default
DefaultCARIDNatNet Default Carrier Default Carrier Identification national network identification plan. Values are: 0
IdPlan
ID NatNet ID (NOTUSED) (default),
1 (NATIONAL_NETWORK_ID_NATIONAL CARRIER_ACCESS_CODE),
Plan
2 (NATIONAL_NETWORK_ID_PLAN_2_DIGIT),
3 (NATIONAL_NETWORK_ID_PLAN_3_DIGIT), or
4 (NATIONAL_NETWORK_ID_PLAN_4_DIGIT).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-66
OL-1110-23
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
Default originating line information. Maps to trunk group property DefaultOLI.
Values: 0 (NOTUSED) (default),
1 (OLI_POTS),
2 (OLI_MULTIPARTY_LINE),
3 (OLI_ANI_FAILURE),
4 (OLI_STATION_LEVEL_RATING),
5 (OLI_SPECIAL_OPERATOR_REQ),
6 (OLI_AIOD),
7 (OLI_COIN_DATABASE),
8 (OLI_800_SERVICE_CALL),
9 (OLI_COIN),
10 (OLI_PRISON_INMATE_SERVICE),
11 (OLI_INTERCEPT_BLANK),
12 (OLI_INTERCEPT_TROUBLE),
13 (OLI_INTERCEPT_REGULAR),
14 (OLI_TELCO_OPERATOR_CALL),
15 (OLI_OUTWATS),
16 (OLI_TRS_1),
17 (OLI_TRS_2),
18 (OLI_TRS_3),
19 (OLI_CELLULAR_SVC_1),
20 (OLI_CELLULAR_SVC_2),
21 (OLI_CELLULAR_SVC_ROAMING),
22 (OLI_PRIVATE_PAYSTATIONS),
23 (OLI_ACCESS_FOR_VPN_TYPES_OF_SVC),
24 (OLI_INTERLATA_RESTRICTED),
25 (OLI_TESTCALL),
26 (OLI_TOLLFREE_FROM_PAYSTATIO),
27 (OLI_CUSTOMER_SPECIFIC_1),
28 (OLI_CUSTOMER_SPECIFIC_2),
29 (OLI_INTERLATA_RESTRICTED_HOTEL), or
30 (OLI_INTERLATA_RESTRICTED_COINLESS)
DefaultOLI
Default
Originating
Line
Information
DefaultCHG
Default Charge Default charge number. Values are: 1 to 16 digits or NULL. Default: 0
Number
DefaultCHGNOA
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-67
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
DefaultCHGNPI
Default Charge Default charge number NPI. Values are: 0 (NOTUSED) (default),
Number NPI
1 (NPI_NONE),
2 (NPI_E164),
3 (NPI_DATA),
4 (NPI_TELEX),
5 (NPI_PNP),
6 (NPI_NATIONAL),
7 (NPI_TELEPHONY),
8 (NPI_MARITIME_MOBILE),
9 (NPI_LAND_MOBILE), or
10 (NPI_ISDN_MOBILE)
DefaultDN
Default
Directory
Number
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-68
OL-1110-23
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
DefaultDNNOA
Default
Directory
Number NOA
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-69
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
DefaultDNNPI
Default
Directory
Number NPI
DefaultDNPresI
Default
Directory
Presentation
Indicator
Default
Directory
Screening
Indicator
DefaultDNSI
1 (PRES_NO_INDICATION),
2 (PRES_ALLOWED),
3 (PRES_RESTRICT), or
4 (PRES_UNAVAIL)
200 (SI_NONE),
201 (SI_USER_PROVIDED_NOT_VERIFIED),
202 (SI_USER_PROVIDED_VERIFIED_PASSED),
203 (SI_USER_PROVIDED_VERIFIED_FAILED), or
204 (SI_NETWORK_PROVIDED)
DefaultCARIDNetID
Default Carrier Default carrier identifier network identifier. Values are: a 2 to 4 digit string, or
NULL (default).
Identifier
Network
Identifier
DefaultCARIDNetTy
pe
Default Carrier Default carrier identifier network type. Values are: 0 (NOTUSED) (default),
Identifier
1 (NETWORK_USER_SPECIFIED),
Network Type 2 (NETWORK_NATIONAL),
3 (NETWORK_INTERNATIONAL), or
4 (NETWORK_CCITT)
MGCdomain
MGC Domain
Name
MGC domain name. Indicates the MGC domain name used in SIP messages. Value
range: Any valid domain name or NULL (default).
MGCSipVersion
MGC SIP
Version
MGC SIP version. The version of SIP protocol supported by the MGC. Value range:
Any valid SIP version.
Default: 2.0
Note
For MGC software earlier than Release 9.7, set this value to SIP/2.0.
LocalPort
Local port. Indicates the UDP port used by MGC to send or receive SIP messages.
Valid range: any valid port number greater than 1024. Default: 5060
InviteTimerT1
Invite Timer T1 Invite T1 timer. Indicates the T1 timer (in milliseconds) for the INVITE message, as
specified for SIP. Value range: any value greater than 0. Default: 1000
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-70
OL-1110-23
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
GenTimerT1
Gen Timer T1
Generic timer T1. The T1 timer value (in milliseconds) for SIP messages other than
INVITE. Value range: any value greater than 0. Default: 500
GenTimerT2
Gen Timer T2
Generic timer T2. The T2 timer value (in milliseconds) for SIP messages other than
INVITE. Value range: any value greater than 0. Default: 4000
MaxRedirectCnt
Maximum
Redirection
Count
Maximum redirect count. Indicates the maximum number of SIP message redirections
allowed. Value range: any value greater than 0.
Support183
Support 183
Support 183. Indicates if the Cisco PGW 2200 Softswitch supports 183 response
code. Valid values: 0 (not supported), 3 (supported) (default), or 4 (always send).
FromField
From Field
From field. Displays the name used in the SIP From field when the calling party
number is marked private. Value range: any alphanumeric string. Default:
anonymous
InSessionTimer
In Session
Timer
In session timer. Indicates the maximum session time (in milliseconds) allowed for a
SIP call that originated by the Cisco PGW 2200 Softswitch. Maps to trunk group
property InSessionTimer. This value may require being increased to 1800000 to reduce
performance impact. Value range: any value greater than 0. Default: 1800000
OutSessionTimer
Out Session
Timer
Out session timer. The maximum session time (in milliseconds) allowed for a SIP
call terminated by the Cisco PGW 2200 Softswitch. This value may require being
increased to reduce performance impact. Valid range: any value greater than 0.
Default: 1800000
HoldTimer
Hold Timer
Hold timer. Indicates the maximum time length (in milliseconds) a SIP call can be put
on hold. Value range: any value greater than 0. Default: 300000
ExpiresTimer
Expires Timer
Expires timer. The timer value (in milliseconds) used in the Expire header of SIP
messages. Value range: any value greater than 0. Default: 60000
SupportReliable100
Support
Reliable 100
Support reliable 100. Indicates if the Cisco PGW 2200 Softswitch supports
reliable100 response code. Values are: TRUE (default) or FALSE.
RetryAfterTimer
Retry After
Timer
MaxForwards
Max. Forwards Maximum forwards. Indicates the maximum number of SIP forwards allowed. Value
range: any value greater than 0. Default: 70.
GatewayRBToneSupp Gateway
ort
RBTone
Support
Default: 5
Gateway ring back tone support. Indicates the support or non-support of ringback
tone application within the gateway that hosts the trunk group and the connection
method that is applied. Values are: 0 (No local tone application support) (default),
1 (Local tone application support using MDCX connection method), or
2 (Local tone application support using RQNT connection method)
Note
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-71
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
WaitAnswerTimer
Wait Answer
Timer
Wait answer timer. This timer is started when the Cisco PGW 2200 Softswitch
instructs the Media Gateway to apply ring back tone upon the receipt of Alerting.
This timer is stopped when the Cisco PGW 2200 Softswitch receives the Answer
message. Values are: 0 through 300 (in seconds). Default: 65
WaitOrigSDPTimer
Wait OrigSDP
Timer
WaitTermSDPTimer
Wait TermSDP Wait for terminating SDP timer. On H.323 terminated calls, the
Timer
Cisco PGW 2200 Softswitch transits the answer message and starts this timer when
the terminating SDP information has not been received. Value range: 0 to 50 (in
seconds).
ChargeOrigin
Charge Origin
Charge origin. The charge origin value may be defaulted (0) when the charging
tariff rates are not origin dependent. The craftperson decides what value of charge
origin is to be used, up to a 4-digit integer value. Value range: 0 (default) through
9999.
SendAddressnCgpn
Send Address
in Cgpn
Send address in the calling party number. Determines if the CLI digits are sent in
the outgoing calling party number parameter. Value is 0 (False) for do not include
address digits in calling party number parameter, or 1 (True) (default) for including
address digits in calling party number parameter.
CgpnPresRes
AInternationalPrefix
AInternational
Prefix
A-number international prefix. Determines the prefix for outgoing calling numbers
when NOA is set to International. Value range: NULL (default) or digit string.
ANationalPrefix
ANationalPrefi A-number national prefix. Determines the prefix for outgoing calling numbers
x
when Nature of Address (NOA) is set to National. Value range: NULL (default) or
digit string.
BInternationalPrefix
BInternational
Prefix
BNationalPrefix
BNationalPrefi B-number national prefix. Determines the prefix for outgoing called numbers when
x
Nature of Address (NOA) is set to National. Value range: NULL (default) or digit
string.
ADigitCCPrefix
ADigitCCPrefi A-digit country code prefix. Controls functionality that applies a country code
x
prefix to the calling party number before sending the call forward. Values are: 0
(default) or 1, where 0 means disabled and 1 means enabled.
BDigitCCPrefix
BDigitCCPrefi B-digit country code prefix. Controls functionality that applies a country code
x
prefix to the called party number before sending the call forward. Values are 0
(default) or 1, where 0 means disabled and 1 means enabled.
B-number international prefix. Determines the prefix for outgoing called numbers
when NOA is set to International. Value range: NULL (default) or digit string.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-72
OL-1110-23
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
BDigitCCrm
BDigitCCrm
Country code remove. Provides a country code digit string to which the called party
number leading digits can be compared, and if matched have those digits removed
from the front of the number. This modification is made before sending the call
forward. Values are: NULL (default) or null, or a maximum 5-digit string.
CCOrigin
CCOrigin
Country code origin. Provides against the origin trunk group of a call the country
code digits, which if needed can be prefixed on a number before sending the call
forward. Only required when the property domain is SigPath or LinkSet. Values:
NULL (default) or a maximum 5 digit string.
Ta1TimePeriod
Ta1TimePeriod Ta1 time period. Indicates the value for the time period Ta1, in seconds. Value
range: 1 through 180. Default: 20
Ta2TimePeriod
Ta2TimePeriod Ta2 time period. Indicates the value for the time period Ta2, in seconds. Value
range: 1 through 180. Default: 30
Ta3TimePeriod
Ta3TimePeriod Ta3 time period. Indicates the value for the time period Ta3, in seconds. Value
range: 1 through 180. Default: 3
ExpiryWarnToneType ExpiryWarnTo
neType
String defining the tone to be applied to warn that the assigned call duration is
almost expired. Value range: Any valid MGCP event name. Default: NULL
ExpiryWarnToneDur
ExpiryWarnTo
neDuration
CLISelect
CLISelect
Calling line identification. Determines whether or not the additional calling party
number is presented in the incoming IAM. Values are: GENERICNUM (the
additional calling party number is presented in the incoming IAM as generic
number and the additional calling party number is used as the CLI and is passed to
the access network) or CLI (additional calling party number is not presented in the
incoming IAM). Default: CLI
GWDefault
CodecString
GW Default
Codec String
Gateway default codec string. Enables the IOCC-MGCP to send the ordered series
of codec choices separated by semicolons. Refer to your gateway documentation for
a list of supported codec names. The following values represent some of the more
common codec names.
Values: NULL, G.711a, G.711u, G.729, G.729a, and G.729b
Default: NULL
AllowH323Hairpin
Allow H323
Hairpin
Allow H.323 hairpinning. Allows the Cisco PGW 2200 Softswitch to interconnect
H.323-originated and H.323-terminated calls by the HSI component. Valid values:
0 (not allowed) or 1 (allowed). Default: 0
H323AdjunctLink
H.323 adjunct
link
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-73
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
FAXSupport
FAX support
FAX support. Indicates if T.38 FAX calls are supported on the trunk group. This
property must be enabled on the incoming and outgoing trunk groups for T.38 fax
calls to be successfully routed. Valid values: 0 (no FAX support) or 1 (T.38 FAX
support). Default: 0
SubscribeNotifySupp
ort
Subscribe
SIP Subscribe/Notify methods. Determines if the SIP Subscribe/Notify methods for
Notify Support solicited notification of SIP DTMF digits is enabled or disabled. Valid Values: 0 =
Subscribe/Notify methods disabled or 1 = Subscribe/Notify methods enabled.
Default: 0
This property is added in software Release 9.4(1).
UnsolicitedNotifyMet Unsolicited
Unsolicited Notify method. Determines if the unsolicited Notify method for
hod
Notify Method unsolicited notification of SIP DTMF digit is enabled or disabled.
Valid Values: 0 = Unsolicited Notify method disabled, 1 = Unsolicited Notify
method enabled, 2 = Unsolicited Info method enabled.
Default: 0
This property is added in software Release 9.4(1).
Option 2 is added in software Release 9.7(3) and later.
MinEventSubscribeD
uration
Min Event
Subscribe
Duration
MaxSubscriptionDura Max
tion
Subscription
Duration
Maximum subscription duration. Defines the maximum duration (in seconds) for
which a subscription can be made. Value range: 0 through 3600.
Default: 0
This property is added in software Release 9.4(1).
OD32DigitSupport
OD 32 Digit
Support
Overdecadic 32 digit support. Allows 32 digits and overdecadic digits support for
the ANSI, Q.761, and Q.767 protocol variants. Values are: 0 (disabled) and 1
(enabled).
Default: 0
This property is added in software Release 9.4(1).
populateSDPInfoIn
CDR
Populate SDP
Info In CDR
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-74
OL-1110-23
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
Anumnormalise
A Number
Normalise
The actions apply only if the NOA of the number (as listed above, in addition to
CgPn) is set to UNKNOWN or SUBSCRIBER. If so, then check the initial digits of
the number to see if they are 0 or 00. The following applies:
If the leading digit is 0, remove the zero and set the NOA to NATIONAL.
If the leading digits are 00, remove both zeros and set the NOA to
INTERNATIONAL.
This property is added in software Release 9.4(1) and is a European feature only.
Bnumnormalise
B Number
Normalise
If the leading digit is 0, remove the zero and set the NOA to NATIONAL.
If the leading digits are 00, remove both zeros and set the NOA to
INTERNATIONAL.
This property is added in software Release 9.4(1) and is a European feature only.
GtdCapTypeProp
GTD Cap Type This property is used by the Cisco PGW 2200 Softswitch as a pointer to the subset
Properties
of GTD parameters that the user desires to support. Value range: t0 (no GTD
support) to any string of 1 through 20 characters that identifies a GTD parameter
string.
Default: t0
GtdMsgFmt
GTD Message
Format
Indicates the GTD message format mode. The format can be only compact mode.
Compact mode is the short format and the field names are not passed in the GTD
parameter string. Valid value: c (compact).
Default: c
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-75
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
IsupTransEarlyBackw ISUP
ardDisabled
Transparency
Early
Backward
Disabled
Default: 1
Default Value: 0
This property is added in software Release 9.4(1).
EnableIPScreening
Enable IP
Screening
Enables the incoming trunk group to select a dial plan based on the IP address,
source ID, and CLI prefix tables. Valid values: 0 (no dial plan lookup) or 1 (require
dial plan lookup).
Default Value: 0
This property is added in software Release 9.4(1).
SipIPSource
SIP IP Source
Indicates for the Cisco PGW 2200 Softswitch to use the IP packet source address
or IP address from Session Description Protocol (SDP) in the INVITE message to
make the dial plan selection for SIP calls. Valid values: 0 (use the IP packet source
address) or 1 (use the IP address from SDP).
Default Value: 0
This property is added in software Release 9.4(1).
DefaultPN
Default PN
Enables the incoming trunk group to have a default PN if the incoming call does not
have one, overdecadic digits are supported. Valid values: overdecadic digit string
from 1 through 20 digits in length.
Default Value: NULL
This property is added in software Release 9.4(1).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-76
OL-1110-23
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
DefaultPNNOA
Default PN
NOA
Enables the default Presentation Number NOA value. Valid values: 0 through 53.
Values are: 0 (NOT USED) - default,
1 (NOA_NONE), 2 (NOA_UNKNOWN),
3 (NOA_SUBSCRIBER),4 (NOA_NATIONAL),
5 (NOA_INTERNATIONAL),6 (NOA_NETWORK),
7 (NOA_MERIDIAN),8 (NOA_ABBR),
9 (NOA_UNIQUE_3DIG_NAT_NUM),10 (NOA_ANI),
11 (NOA_NO_ANI_RECD),
12 (NOA_NON_UNIQUE_SUBSCRIBER),
13 (NOA_NON_UNIQUE_NATIONAL),
14 (NOA_NON_UNIQUE_INTERNATIONAL),
15 (NOA_OPRREQ_TREATED),16 (NOA_OPRREQ_SUBSCRIBER),
17 (NOA_OPRREQ_NATIONAL),
18 (NOA_OPRREQ_INTERNATIONAL),
19 (NOA_OPRREQ_NO_NUM),20 (NOA_CARRIER_NO_NUM),
21 (NOA_950_CALL),22 (NOA_TEST_LINE_CODE),
23 (NOA_INT_INBOUND),
24 (NOA_NAT_OR_INTL_CARRIER_ACC_CODE_INC),
25 (NOA_CELL_GLOBAL_ID_GSM),
26 (NOA_CELL_GLOBAL_ID_NMT_900),
27 (NOA_CELL_GLOBAL_ID_NMT_450),
28 (NOA_CELL_GLOBAL_ID_AUTONET),
29 (NOA_PORTED_NUMBER),30 (NOA_PISN_SPECIFIC_NUMBER),
31 (NOA_UK_SPECIFIC_ADDRESS),32 (NOA_SPARE),
33 (NOA_MCI_VNET),
34 (NOA_INTERNATIONAL_OPR_TO_OPR_OUTSIDE_WZI),
35 (NOA_INTERNATIONAL_OPR_TO_OPR_INSIDE_WZI),
36 (NOA_DIRECT_TERMINATION_OVERFLOW),
37 (NOA_ISN_EXTENDED_INTERNATIONAL_TERMINATION),
38 (NOA_TRANSFER_ISN_TO_ISN),39 (NOA_CREDIT_CARD),
40 (NOA_DEFINED_IN_SSUTR),41 (NOA_DEFINED_IN_SSUTR2),
42 (RESERVED),43 (NOA_DISCARDED),
44 NOA_NETWORK_RN_CONCAT_WITH_CDPN,
45 NOA_NAT_NUM_WITH_SELECT_OF_CARR,
46 NOA_INT_NUM_WITH_SELECT_OF_CARR,
47 NOA_NATIONAL_SPARE_2,
48 NOA_PORTED_NUMBER_OR_SCREENED_FOR_PORTING,
49 NOA_SPECIAL_NUMBER,
50 NOA_NATL_NUM_TRANSIT_NETWORK_SELECT,
51 NOA_INTL_NUM_TRANSIT_NETWORK_SELECT,
52 NOA_SPAIN,
53 NOA_PARTIAL_CALLING_LINE_ID,
54 NOA_NETWORK_RN_NSN_FORMAT , or
55 NOA_NETWORK_RN_NETWORK_SPECIFIC_FORMAT
Default: 0
This property is added in software Release 9.4(1).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-77
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
DefaultPNNPI
Default PN
NPI
Displays the default Presentation Number NPI value. Valid values: 0 through 10.
0 (NOTUSED) (default),
1 (NPI_NONE),
2 (NPI_E164),
3 (NPI_DATA),
4 (NPI_TELEX),
5 (NPI_PNP),
6 (NPI_NATIONAL),
7 (NPI_TELEPHONY),
8 (NPI_MARITIME_MOBILE),
9 (NPI_LAND_MOBILE), or
10 (NPI_ISDN_MOBILE)
Default Value: 0
This property is added in software Release 9.4(1).
DefaultPNPres
Default PN
Pres
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-78
OL-1110-23
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
CustomerVPNOnNet
TblNum
Customer VPN Allows assignment of a VPN on-net profile table index to a particular trunk group.
OnNet Table
Value range: 1 through 8
Num
1 (Indicates that completely transparent operation is required or the call will not
complete.)
2 (Sets to feature transparency preferred by a nontransparent destination can be
used if necessary to complete the call.)
3 (Sets to feature transparency preferred by a nontransparent destination can be
used if necessary to complete the call.)
4 (Sets to feature transparency preferred by a nontransparent destination can be
used if necessary to complete the call.)
5 (Sets to indicate that the attempted feature will be removed from the onward
routed call, and the indicator is informed of this.)
6 (Sets to release a feature call.)
7 (Sets to release a feature call.)
8 (Sets to remove the feature string and continue.)
Default Value: 5
This property is added in software Release 9.4(1). The range changed to 1-8 and the
default changed to 5 in software Release 9.6(1).
CustomerVPNid
Customer VPN Assigns a VPN ID to a trunk group or system. Valid values: 1 through 8
ID
alphanumeric character string.
Default Value: 00000000
This property is added in software Release 9.4(1).
CustomerVPNOffNet
TblNum
Customer VPN Allows assignment of a VPN off-net profile table index to a particular trunk group.
Off Net Table Value range: 1 through 8
Num
1 (Indicates that completely transparent operation is required or the call will not
complete.)
2 (Sets to feature transparency preferred by a nontransparent destination can be
used if necessary to complete the call.)
3 (Sets to feature transparency preferred by a nontransparent destination can be
used if necessary to complete the call.)
4 (Sets to feature transparency preferred by a nontransparent destination can be
used if necessary to complete the call.)
5 (Sets to indicate that the attempted feature will be removed from the onward
routed call, and the indicator is informed of this.)
6 (Sets to release a feature call.)
7 (Sets to release a feature call.)
8 (Sets to remove the feature string and continue.)
Default Value: 0
This property is added in software Release 9.4(1). The range changed to 1-8 and the
default changed to 5 in software Release 9.6(1)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-79
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
FeatureTransparency
Disabled
Feature
Transparency
Disabled
Disables QSIG Feature Transparency for all calls on the PGW. Valid values: 0
(Feature Transparency enabled) or 1 (Feature Transparency disabled).
Default Value: 0
This property is added in software Release 9.4(1).
SdpXmitToH323Trig
ger
SDP transmit
SDP transmit to H.323 trigger. Indicates the point in a call when the
to H323 trigger Cisco PGW 2200 Softswitch sends the Session Destination Protocol (SDP) from
the terminating call leg to the H.323 Signaling Interface (HSI). Value range: 0
through 3.
0 = terminating seizure, 1 = Address complete, 2 = Alerting or Inband information
available, or 3 = Answer.
This property is added in software Release 9.4(1).
GWDefaultATMProfil GW Default
e
ATM Profile
Provides, on a per trunk group basis, an initial list of profiles for use in ATM
gateway profile negotiation. This property contains a list of profile choices
separated by semi-colons, that influences ATM gateway profile negotiation. If
GWDefaultATMProfile is set to NULL (default), then there is no profile list
negotiation bias applied from the trunk group level. Valid values: NULL,
<Profile1>;<Profile2>;<ProfileN>, where the string is 1 (minimum) to 140
(maximum) characters.
Default value: NULL
This property is added in software Release 9.5(2)
PlayAnnouncement
Play
Enables, on a per trunk group basis, playing an early announcement. This property
Announcement can either contain an Integer Announcement Identity, or, if it is set to 0 (default),
the announcement function is considered disabled at the trunk group level. Valid
values: any integer value greater than 0.
Default value: 0
This property is added in software Release 9.5(2)
AtmConnectionType
Atm.
Connection
Type
BTechPrefix
B Tech Prefix
Provides a digit string to be used as a Tech Prefix to the B-number when sending
the call forward. Valid values: any integer.string from one digit (minimum) through
16 (maximum) digits. The Tech Prefix uses overdecadic digits B and C and maps
them to * and # respectively. The Tech Prefix and a separator are appended to the
beginning of the B-number.
This property is added in software Release 9.5(2)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-80
OL-1110-23
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
LoopAvoidanceSuppo Loop
rt
Avoidance
Support
Enables the support of the loop avoidance feature in DPNSS protocol. Valid values:
0 (disable) or 1 (enable).
Default value: 0
This property is added in software Release 9.5(2)
LoopAvoidanceCount Loop
er
Avoidance
Counter
Enables the support of the loop avoidance feature in DPNSS protocol. Valid values:
0 through 25.
Default value: 0
This property is added in software Release 9.5(2)
MwiStringON
MWI String On Enables the support of MWI to the DPNSS protocol to light the MWI lamp on a
particular extension when this string is encoded in message. Valid values: Digit
string from 1 (minimum) through 32 (maximum) digits.
Default value: NULL
Note
Ensure the digit string provisioned is the same MWI string provisioned in
Cisco CallManager.
MWI String
Off
Enables the support of MWI to the DPNSS protocol to extinguish the MWI lamp on
a particular extension when this string is encoded in message. Valid values: Digit
string from 1 (minimum) through 32 (maximum) digits.
Default value: NULL
Note
Ensure the digit string provisioned is the same MWI string provisioned in
Cisco CallManager.
Enables or disables inhibit incoming calling name display in DPNSS and EISUP
(HSI) protocols. Valid values: 0 (enable) or 1 (disable).
Default value: 0
This property is added in software Release 9.5(2)
InhibitOutgoingCallin Inhibit
gNameDisplay
Outgoing
Calling Name
Display
Enables or disables inhibit outgoing calling name display in DPNSS and EISUP
(HSI) protocols. Valid values: 0 (enable) or 1 (disable).
Default value: 0
This property is added in software Release 9.5(2)
InhibitIncomingConn
ectedNameDisplay
Inhibit
Incoming
Connected
Name Display
Enables or disables inhibit incoming connected name display in DPNSS and EISUP
(HSI) protocols. Valid values: 0 (enable) or 1 (disable).
Default value: 0
This property is added in software Release 9.5(2)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-81
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
InhibitIncomingConn
ectedNumberDisplay
Inhibit
Incoming
Connected
Number
Display
MidCallCPInterval
Mid Call CP
Interval
Enable s or disables mid-call checkpointing. When enabled, you can specify the
interval (in minutes) between checkpointing events in the connected state. Valid
values: 0 (disabled) (default) through 60.
Default value: 0
This property is added in software Release 9.5(2)
CliSelectionForCode
OfPractice3
Cli Selection
For Code Of
Practice 3
Provisions, on a per trunk group basis, the level of CLI selection used when sending
the calling line identities (such as Calling Party Number or Generic Number
parameter) to the succeeding exchange. Valid range: 0 through 2. Valid values:
0Indicates no specific CLI selection (default), 1Indicates single CLI selection,
which sends only the CLI, or 2Indicates dual CLI selection, which ends the CLI;
or the CLI and the PN.
Default value: 0
This property is added in software Release 9.5(2)
InhibitOutgoingConn
ectedNameDisplay
Inhibit
Outgoing
Connected
Name Display
Enables or disables inhibit outgoing connected name display in DPNSS and EISUP
(HSI) protocols. Valid values: 0 (enable) or 1 (disable).
Default value: 0
This property is added in software Release 9.5(2)
InhibitOutgoingConn
ectedNumberDisplay
AOCInvokeType
Inhibit
Outgoing
Connected
Number
Display
AOC Invoke
Type
Default value: 0
This property is added in software Release 9.5(2)
Default value: 1
This property is added in software Release 9.5(2)
AOCDefaultTariffId
AOC Default
Tariff Id
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-82
OL-1110-23
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
MML Parameter Name Name
oLocLabel
Originating
Local Label
tLocLabel
Terminating
Local Label
RejectOfferForResour RejectOfferFor Specifies how the Cisco PGW 2200 Softswitch treats new offers when the resource
cePending
ResourcePendi is temporarily unavailable.
ng
Valid values:
0Buffer the new offer
1Reject the new offer
Default value: 1
UseGtdCalledPartyNu UseGtdCalledP Enables the Cisco PGW 2200 Softswitch to use embedded calledPartyNumber field
mber
artyNumber
of GTD in the invite message instead of url/number contained in the request line.
Valid values: 0disable, 1enable.
InhibitPasson
Inhibit Passon
Default: 0
After you have populated the trunk group file, if you want to change any properties in that file, make the
property changes using the text editor. Then use the MML add command to add the trunk group file and
the bearer channel file, even though you have not made any changes to the bearer channel file.
The customer trunk group file for software Release 9.2 has 69 columns, software Release 9.3(1) has 74
columns, and software Release 9.3(2) has 79 columns of the following parameters in the order listed:
The fields are: Trunk Group Number, CLLI, Signaling Service MML Name, Trunk Group Type,
Queueable, Ring No Answer, Glare, COT percentage, Select Sequence, VSF Priority, Satellite Indicator,
NPA, Customer Group ID, Compression Type, Echo Cancellation, External COT, Detect Fax Modem
Tone, Max ACL, ACL Duration, ACC Response Control Inhibit, ISUP Transparency Disabled, AOC
Enabled, Carrier Screening, Originating Carrier ID, Notify Setup Complete, Package Type, ACC
Response Category Name, Default Carrier ID National Network ID, Default OLI, Default CHG, Default
CHG NOA, Default CHG NPI, Default DN, Default DN NOA, Default DN NPI, Default DN Pres,
Default DN SI, Default Carrier ID Net ID, Default Carrier ID Net Type, MGC Domain, MGC SIP
Version, Local Port, Invite Timer T1, Gen Timer T1, Gen Timer T2, Max Redirect Count, Support 183,
From Field, In Session Timer, Out Session Timer, Hold Timer, Expires Timer, Support Reliable 100,
Retry After Timer, Max Forwards, Gateway RB Tone Support, Wait for Answer Timer, Wait for
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-83
Chapter 2
Originating SDP Timer, Wait for Terminating SDP Timer, Charge Origin, Send Address in CGPN,
CGPN Presentation Restricted, AInternationalPrefix, ANationalPrefix, BInternationalPrefix,
BNationalPrefix, ADigitCCPrefix, BDigitCCPrefix, BDigitCCrm CCOrigin, Ta1TimePeriod,
Ta2TimePeriod, Ta3TimePeriod, ExpiryWarnToneType, ExpiryWarnToneDur, CLISelect,
GWDefaultCodecString, AllowH323Hairpin, H323AdjunctLink, and FAXsupport.
The following are examples of a trunk group file #format3 text formats:
#format3 9.3001
1000
TTTT-SS-BB ss7svc1 TDM_ISUP
N
5 0 10 LIDL 1 0 703 7777 1 0 Loop 0 3 5 1 1 1 1 1111 0 ABC 0 0 0
703 0 0 301 0 0 0 0 202 0 vsc1 SIP2.0 5555 2000 800 6000 2 1 mgcusr 600000 300000 600000 30000 FALSE 90000 10
0 65 10 10 0 1 0 NULL NULL NULL NULL 0 0 NULL NULL 20 30 3 NULL 1
#format3 9.3002
2000
TTTT-SS-BB ss7svc1 TDM_ISUP
N
5 0 10 LIDL 1 0 703 7777 1 0 Loop 0 3 5 1 1 1 1 1111 0 ABC 0 0 0
703 0 0 301 0 0 0 0 202 0 vsc1 SIP2.0 5555 2000 800 6000 2 1 mgcusr 600000 300000 600000 30000 FALSE 90000 10
0 65 10 10 0 1 0 NULL NULL NULL NULL 0 0 NULL NULL 20 30 3 NULL 1 CLI NULL 0 0 0
The customer trunk group file for version 9.4001 has the following parameters in this particular order
(104 columns)
The fields are: Trunk Group Number, CLLI, Signaling Service MML Name, Trunk Group Type,
Queueable, Ring No Answer, Glare, COT percentage, Select Sequence, VSF Priority, Satellite Indicator,
NPA, Customer Group ID, Compression Type, Echo Cancellation, External COT, Detect Fax Modem
Tone, Max ACL, ACL Duration, ACC Response Control Inhibit, ISUP Transparency Disabled, AOC
Enabled, Carrier Screening, Originating Carrier ID, Notify Setup Complete, Package Type, ACC
Response Category Name, Default Carrier ID National Network ID, Default OLI, Default CHG, Default
CHG NOA, Default CHG NPI, Default DN, Default DN NOA, Default DN NPI, Default DN Pres,
Default DN SI, Default Carrier ID Net ID, Default Carrier ID Net Type, MGC Domain, MGC SIP
Version, Local Port, Invite Timer T1, Gen Timer T1, Gen Timer T2, Max Redirect Count, Support 183,
From Field, In Session Timer, Out Session Timer, Hold Timer, Expires Timer, Support Reliable 100,
Retry After Timer, Max Forwards, Gateway RB Tone Support, Wait for Answer Timer, Wait for
Originating SDP Timer, Wait for Terminating SDP Timer, Charge Origin, Send Address in CGPN,
CGPN Presentation Restricted, AInternationalPrefix, ANationalPrefix, BInternationalPrefix,
BNationalPrefix, ADigitCCPrefix, BDigitCCPrefix, BDigitCCrm, CCOrigin,Ta1TimePeriod,
Ta2TimePeriod,Ta3TimePeriod, ExpiryWarnToneType, ExpiryWarnToneDur, CLISelect,
GWDefaultCodecString, AllowH323Hairpin, H323AdjunctLink, FAXsupport, SubscribeNotifySupport,
UnsolicitedNotifyMethod, MinEventSubscribeDuration, MaxSubscriptionDuration,
populateSDPInfoInCDR, OD32DigitSupport, Anumnormalise, Bnumnormalise, GtdCapTypeProp,
GtdMsgFmt, IsupTransEarlyBackwardDisabled, sipMimeBodySupport, EnableIPScreening,
SipIPSource, DefaultPN, DefaultPNNOA, DefaultPNNPI, DefaultPNPres,
CallForwardRerouteDisabled, CustomerVPNOnNetTblNum, CustomerVPNid,
CustomerVPNOffNetTblNum, FeatureTransparencyDisabled, SdpXmitToH323Trigger.
The customer trunk group file for version 9.5001 has the following parameters in this particular order
(122 columns)
The fields are: Trunk Group Number, CLLI, Signaling Service MML Name, Trunk Group Type,
Queueable, Ring No Answer, Glare, COT percentage, Select Sequence, VSF Priority, Satellite Indicator,
NPA, Customer Group ID, Compression Type, Echo Cancellation, External COT, Detect Fax Modem
Tone, Max ACL, ACL Duration, ACC Response Control Inhibit, ISUP Transparency Disabled, AOC
Enabled, Carrier Screening, Originating Carrier ID, NetworkType, Package Type, ACC Response
Category Name, Default Carrier ID National Network ID, Default OLI, Default CHG, Default CHG
NOA, Default CHG NPI, Default DN, Default DN NOA, Default DN NPI, Default DN Pres, Default DN
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-84
OL-1110-23
Chapter 2
SI, Default Carrier ID Net ID, Default Carrier ID Net Type, MGC Domain, MGC SIP Version, Local
Port, Invite Timer T1, Gen Timer T1, Gen Timer T2, Max Redirect Count, Support 183, From Field, In
Session Timer, Out Session Timer, Hold Timer, Expires Timer, Support Reliable 100, Retry After Timer,
Max Forwards, Gateway RB Tone Support, Wait for Answer Timer, Wait for Originating SDP Timer,
Wait for Terminating SDP Timer, Charge Origin, Send Address in CGPN, CGPN Presentation
Restricted, AInternationalPrefix, ANationalPrefix, BInternationalPrefix, BNationalPrefix,
ADigitCCPrefix, BDigitCCPrefix, BDigitCCrm, CCOrigin, Ta1TimePeriod, Ta2TimePeriod,
Ta3TimePeriod, ExpiryWarnToneType, ExpiryWarnToneDur, CLISelect, GWDefaultCodecString,
AllowH323Hairpin, H323AdjunctLink, FAXsupport, SubscribeNotifySupport,
UnsolicitedNotifyMethod, MinEventSubscribeDuration, MaxSubscriptionDuration,
populateSDPInfoInCDR, OD32DigitSupport, Anumnormalise, Bnumnormalise, GtdCapTypeProp,
GtdMsgFmt, IsupTransEarlyBackwardDisabled, sipMimeBodySupport, EnableIPScreening,
SipIPSource, DefaultPN, DefaultPNNOA, DefaultPNNPI, DefaultPNPres,
CallForwardRerouteDisabled, CustomerVPNOnNetTblNum, CustomerVPNid,
CustomerVPNOffNetTblNum, FeatureTransparencyDisabled, SdpXmitToH323Trigger,
GWDefaultATMProfile, PlayAnnouncement, AtmConnectionType, BTechPrefix,
LoopAvoidanceSupport, LoopAvoidanceCounter, MwiStringOFF, MwiStringON,
InhibitIncomingCallingNameDisplay, InhibitOutgoingCallingNameDisplay,
InhibitIncomingConnectedNameDisplay, InhibitIncomingConnectedNumberDisplay,
AOCDefaultTariffId, AOCInvokeType, MidCallCPInterval, CliSelectionForCodeOfPractice3,
InhibitOutgoingConnectedNameDisplay, InhibitOutgoingConnectedNumberDisplay
The customer trunk group file for version 9.6001 will have the following parameters in this particular
order (124 columns)
The fields are: Trunk Group Number, CLLI, Signaling Service MML Name, Trunk Group Type,
Queueable, Ring No Answer, Glare, COT percentage, Select Sequence, VSF Priority, Satellite Indicator,
NPA, Customer Group ID, Compression Type, Echo Cancellation, External COT, Detect Fax Modem
Tone, Max ACL, ACL Duration, ACC Response Control Inhibit, ISUP Transparency Disabled, AOC
Enabled, Carrier Screening, Originating Carrier ID, NetworkType, Package Type, ACC Response
Category Name, Default Carrier ID National Network ID, Default OLI, Default CHG, Default CHG
NOA, Default CHG NPI, Default DN, Default DN NOA, Default DN NPI, Default DN Pres, Default DN
SI, Default Carrier ID Net ID, Default Carrier ID Net Type, MGC Domain, MGC SIP Version, Local
Port, Invite Timer T1, Gen Timer T1, Gen Timer T2, Max Redirect Count, Support 183, From Field, In
Session Timer, Out Session Timer, Hold Timer, Expires Timer, Support Reliable 100, Retry After Timer,
Max Forwards, Gateway RB Tone Support, Wait for Answer Timer, Wait for Originating SDP Timer,
Wait for Terminating SDP Timer, Charge Origin, Send Address in CGPN, CGPN Presentation
Restricted, AInternationalPrefix, AnationalPrefix, BInternationalPrefix, BnationalPrefix,
ADigitCCPrefix, BDigitCCPrefix, BDigitCCrm,CCOrigin,Ta1TimePeriod,Ta2TimePeriod,
Ta3TimePeriod, ExpiryWarnToneType, ExpiryWarnToneDur, CLISelect, GWDefaultCodecString,
AllowH323Hairpin, H323AdjunctLink, FAXsupport, SubscribeNotifySupport,
UnsolicitedNotifyMethod, MinEventSubscribeDuration, MaxSubscriptionDuration,
populateSDPInfoInCDR, OD32DigitSupport, Anumnormalise, Bnumnormalise, GtdCapTypeProp,
GtdMsgFmt, IsupTransEarlyBackwardDisabled, sipMimeBodySupport, EnableIPScreening,
SipIPSource, DefaultPN, DefaultPNNOA, DefaultPNNPI, DefaultPNPres,
CallForwardRerouteDisabled, CustomerVPNOnNetTblNum, CustomerVPNid,
CustomerVPNOffNetTblNum, FeatureTransparencyDisabled, SdpXmitToH323Trigger,
GWDefaultATMProfile, PlayAnnouncement, AtmConnectionType, BTechPrefix,
LoopAvoidanceSupport, LoopAvoidanceCounter, MwiStringOFF, MwiStringON,
InhibitIncomingCallingNameDisplay, InhibitOutgoingCallingNameDisplay,
InhibitIncomingConnectedNameDisplay, InhibitIncomingConnectedNumberDisplay,
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-85
Chapter 2
N
5 0 10 LIDL 1 0 703 7777 1 0 Loop 0 3 5 1 1 1
202 0 MGC1 SIP2.1 5555 2000 800 6000 2 1 mgcusr
10 0 65 10 10 0 1 0 NULL NULL NULL NULL 0 0 NULL
40 0 0 1 0 0 t0 c 1 0 0 0 NULL 0 0 0 0 0 00000000 0
#format3 9.5001
1000
TTTT-SS-BB ss7svc1 TDM_ISUP
N
5 0 10 LIDL 1 0 703 7777 1 0 Loop 0 3 5 1 1 1
1 1111 0 ABC 0 0 0 703 0 0 301 0 0 0 0 202 0 MGC1 SIP2.1 5555 2000 800 6000 2 1 mgcusr
600000 300000 600000 30000 FALSE 90000 10 0 65 10 10 0 1 0 NULL NULL NULL NULL 0 0 NULL
NULL 20 30 3 NULL 1 CLI NULL 0 0 0 0 0 40 0 0 1 0 0 t0 c 1 0 0 0 NULL 0 0 0 0 0 00000000 0
0 0 NULL 0 4 NULL 0 0 NULL NULL 0 0 0 0 1 1 0 0 0 0
#format3 9.6001
1000
TTTT-SS-BB ss7svc1 TDM_ISUP
N
5 0 10 LIDL 1 0 703 7777 1 0 Loop 0 3 5 1 1 1
1 1111 0 ABC 0 0 0 703 0 0 301 0 0 0 0 202 0 MGC1 SIP2.1 5555 2000 800 6000 2 1 mgcusr
600000 300000 600000 30000 FALSE 90000 10 0 65 10 10 0 1 0 NULL NULL NULL NULL 0 0 NULL
NULL 20 30 3 NULL 1 CLI NULL 0 0 0 0 0 40 0 0 1 0 0 t0 c 1 0 0 0 NULL 0 0 0 0 0 00000000 0
0 0 NULL 0 4 NULL 0 0 NULL NULL 0 0 0 0 1 1 0 0 0 0 0 0
MML Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
Trunk group
member
number
Identifies the trunk group member number. A numeric identifier for the trunk group
member. An integer from 1 through 9999.
TRNKGRPNUM
Trunk group
number
Identifies the trunk group number. Value range: an integer from 1 through 65535. Not
used for ISDN.
SPAN
Span ID
Identifies the span. Value range: an integer from 1 through 65535 or ffff. (Not
required for TDM.)
CIC
Circuit
identifier code
Identifies the trunk time slot or circuit identification code. Value range: an integer
from 1 through 65535.
CU
Coding unit
Identifies the coding unit MML name that was previously defined for the VISM card
(this is the external node created for MGCP or SGCP).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-86
OL-1110-23
Chapter 2
Table 2-31
MML Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
ENDPOINT
End point
Text description of the trunk end point (typically a VISM card). Enter as many as 128
characters and enclose in straight quotes.
SPANSIZE
Span size
0
0
0
0
0
1
2
3
4
5
as5300-33
as5300-33
as5300-33
as5300-33
as5300-33
S0/DS1-0/1@as5300-33
S0/DS1-0/2@as5300-33
S0/DS1-0/3@as5300-33
S0/DS1-0/4@as5300-33
S0/DS1-0/5@as5300-33
Route Analysis
Routing analysis is necessary to identify the path for bearer traffic from the Cisco PGW 2200 Softswitch
to the adjacent switch.
Table 2-32 lists the routing trunk group MML command parameter definitions and their associated
values.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-87
Chapter 2
Route Analysis
Table 2-32
MML Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
Name
Unique name for this routing trunk group number. Enter as many as 20 alphanumeric
characters and enclose in straight quotes. Hyphens (-) can be used.
TYPE
Type
REATTEMPTS
Reattempts
Identifies the number of times the system reattempts to select the same trunk group
due to congestion. If, after the specified number of reattempts, a trunk group is not
selected, the call is released.
Value range: 0 (default) through 5.
QUEUING
Queuing
Identifies the duration (in seconds) the call will be queued when circuit selection on
a trunk group has failed. The value specified is the time (in seconds) the call is queued
and waits for a circuit to become free. If a circuit becomes free before the time
interval expires, the call is completed. If no circuit becomes available before the
elapsed time, the call is released.
Value range: 0 (default) through 120.
CUTTHROUGH
Cutthrough
Identifies the point in the call process where the trunk is seized from end point to end
point. Value range: 0 (default) through 3.
0 = Undefined
2 = ACM
3 = Answer
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-88
OL-1110-23
Chapter 2
Table 2-32
Voice Services
Provisioning
Tool Parameter
Name
Description
MML Parameter
Name
RESINCPERC
Reserve
Incoming
Percentage
BEARERCAPNA
ME
Bearer
Capability
Name
Unique name for this bearer capability (NULL). Enter as many as 20 alphanumeric
characters and enclose in straight quotes. Hyphens (-) can be used.
Table 2-33 lists the route trunk MML command parameter definitions.
Table 2-33
MML Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
Name
Unique name for this routing trunk group. Enter as many as 20 alphanumeric
characters and enclose in straight quotes. Hyphens (-) can be used.
TRNKGRPNUM
Trunk group
number
NEXTTRKGRP
Next trunk
group
Each line entry in the route trunk file is one entry in the route list file.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-89
Chapter 2
Route Analysis
If weighted trunk group based routing is enabled at the route trunk level, any route list that it is
connected to must have distribution enabled to ensure that the random algorithm is used.
If weighted trunk group based routing is enabled at the route trunk level, then the same route trunk
group can be added to the route trunk multiple times.
If weighted trunk group based routing is disabled at the route trunk, then the same route trunk group
cannot be added to the rttrnk multiple times.
If the route trunk has the same route trunk group connected to it more than once, the weighted trunk
group based routing cannot be changed to disabled.
If the route list is connected to an route trunk that has weighted trunk group based routing enabled,
the distribution parameter for the route list cannot be changed from on to off.
If the route trunk has weighted trunk group based routing as enabled, then the nexttrkgrp parameter
is not supported.
When the user deletes the route trunk group from an route trunk that has multiple route trunk group
of the same value, it only deletes the first route trunk group in the list.
For weighted trunk group based routing, you add the same route trunk group to the route trunk multiple
times for it to be weighted trunk group based routing.
There following MML example creates the routing data with 25% of the calls on trunk group 1111 and
75% of the data on trunk group 2222 for the route trunk called route1.
prov-sta::srcver="new",dstver="test",confirm
prov-add:rttrnkgrp:name="1111",type=0
prov-add:rttrnkgrp:name="2222",type=0,reattempts=5,queuing=2,cutthrough=3
prov-add:rttrnkgrp:name="3333",type=0,reattempts=1,queuing=1,cutthrough=1
prov-add:rttrnk:name="route1",trnkgrpnum=1111,weightedtg="ON"
prov-ed:rttrnk:name="route1",trnkgrpnum=2222,weightedtg="ON"
prov-ed:rttrnk:name="route1",trnkgrpnum=2222
prov-ed:rttrnk:name="route1",trnkgrpnum=2222
prov-add:rttrnk:name="route2",trnkgrpnum=3333,weightedtg="OFF"
prov-add:rttrnk:name="route3",trnkgrpnum=2222,weightedtg="OFF"
prov-add:rtlist:name="one",rtname="route2",distrib="OFF"
prov-add:rtlist:name="two",rtname="route1",distrib="ON"
prov-add:rtlist:name="three",rtname="route3",distrib="OFF"
prov-stp
Note
Additional trnkgrpnums can be added to the rttrnk with or without enabling the weightedtg parameter.
If the second weightedtg had been set to OFF, then the whole rttrnk would not allow weighted trunk
group based routing. Route1 must be connected to an rtlist with distrib ON since the weighted trunk
group was set to ON.
Table 2-34 lists the route list MML command parameter definitions and their associated values.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-90
OL-1110-23
Chapter 2
Table 2-34
MML Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
Name
Unique name for this route trunk. Enter as many as 20 alphanumeric characters and
enclose in straight quotes. Hyphens (-) can be used.
RTNAME
Route name
NEXTRTNAME
DISTRIB
Sequential distribution. Values are: Off (default) to use sequential selection to choose
the trunk group in the route; or On to use random selection.
Note
What is called route list in MML is called a route group in Voice Services Provisioning Tool.
SIP link
You must create a SIP routing trunk group. You can use either the MML command to create a SIP routing
trunk group or use the Voice Services Provisioning Tool to import a routing file.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
2-91
Chapter 2
Table 2-35
MML Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
Name
Trunk group ID. A numeric identifier for the trunk group. Value range: an integer
from 1 through 9999.
URL
SIP URL
SIP proxy service address in the format of IP address, host name, or DNS name.
PORTNUM
Port number
VERSION
SIP version
CUTTHROUGH
Cut through
EXTSUPPORT
Extension
support
This property is reserved for future use and is not currently implemented.
SIPPROXYPORT
SIP Proxy Port UDP port number used by the SIP proxy server. Value range: 1025 through 65535.
Default: 5060.
BEARERCAPNA
ME
Bearer
Capability
Name
Unique name for this bearer capability (NULL). Enter as many as 20 alphanumeric
characters and enclose in straight quotes. Hyphens (-) can be used.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
2-92
OL-1110-23
CH A P T E R
This chapter shows you how to use the Cisco Voice Services Provisioning Tool (VSPT), Release 2.7(3)
to provision a Cisco PGW 2200 Softswitch and the Cisco Billing and Measurements Server (BAMS).
Depending on the Cisco VSPT software release you are using, the windows you see may not appear
exactly as the window examples in this chapter.
Tip
Note
Before you begin provisioning, have a list of the components you want to provision, including
component names, IP addresses, properties, and other parameters. These can be created using the
worksheets provided in Appendix B, Planning Worksheets. Descriptions of the properties and values
contained in the Cisco VSPT are also included in Appendix B and in this chapter. Review this
information before you begin provisioning and keep it available for reference.
The provisioning procedures described in this chapter follow the sequence for provisioning a typical
Cisco PGW 2200 Softswitch configuration described in Chapter 1, Provisioning Overview.
In this chapter, the Cisco PGW 2200 Softswitch is typically referred to by its legacy name,
Cisco MGC. This name is used in most of the VSPT dialog screens.
Cisco IP Transfer Point - LinkExtender (ITP-L) is the new name for Cisco Signaling Link Terminal
(SLT). Over time, Cisco ITP-L will replace Cisco SLT in publications and the product.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-1
Chapter 3
T1 or E1 line
IP address
IP route
Configuring communications between the MGC and external SS7 signaling points (SPs), such as
Signaling Transfer Points (STPs) or IP Transfer Points (ITPs)
Configuring call control links between the MGC, Cisco ITP-L, and the media gateways
The provisioning procedures presented in this chapter follow the provisioning sequence for a typical
MGC configuration.
Note
The components in your solution might differ from those described in this chapter. For additional
provisioning procedures, see the other chapters in this guide.
The following sections provide information on using the Cisco VSPT to provision a MGC:
Note
Provisioning or changing some properties requires a restart for the change to take effect. When you add
or edit a property, Cisco VSPT notifies you if a restart is required. See Table 4-4 on page 4-18 for a list
of properties and restart information.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-2
OL-1110-23
Chapter 3
Note
Before you begin provisioning the MGC using Cisco VSPT, be sure the MGC software is properly
configured for your network. See the Cisco Media Gateway Controller Software Installation and
Configuration (Release 9.7) at the following URL,
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/installation/software/SW1/97.html
or the Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1
through 9.6) at the following URL,
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/installation/software/SW2/pre97inst.html
MGC Properties
Field Name
Description
Default
Valid Values
MGC Hostname
None
User defined
Login / Password
None
User defined
Protocol
SSH
SSH None
(Telnet)
PGW Mode
Depends on
PGW
Switched
Nailed
BAMS Version
Bams V3
Bams V3
BAMS Config
<UNSET>
xxxx
IP Addr:1
None
x.x.x.x
IP Addr:2
None
x.x.x.x
IP Addr:3
x.x.x.x
IP Addr:4
x.x.x.x
Failover
None
No, Yes
Failover IP
Addr:1
None
x.x.x.x
Failover IP
Addr:2
None
x.x.x.x
Failover IP
Addr:3
None
x.x.x.x
Failover IP
Addr:4
IP address of the fourth interface for signaling on the standby MGC None
(if included)
x.x.x.x
Perform the following steps to add an MGC host and a standby host, if applicable. Refer to Table 3-1 for
property values.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-3
Chapter 3
Note
If you are adding a MGC host in a fault-tolerant mode, set pom.datasync to false and
SysConnectDataAccess to true in XECfgParm.dat file. By doing that, the standby MGC is not
automatically synchronizing the provision from the active MGC.
Step 1
Step 2
Choose File->New in the menu bar and enter the name for the new configuration.
A window similar to the one in Figure 3-1 displays.
Figure 3-1
Step 3
If you want to import the configuration from an existing MGC, select Import from MGC. If you want
to do a manual configuration, select Perform manual configuration and after you click the OK button
go to Step 6.
Step 4
Enter the hostname or IP address and the log in information for the existing MGC. Select the SSH or
None radio button.
Step 5
Click the Select button and select the configuration from the existing MGC to import.
A window similar to the one in Figure 3-2 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-4
OL-1110-23
Chapter 3
Figure 3-2
Configuration Chooser
Step 6
Step 7
Click Unknown MGC in the left pane of the main VSPT window. A window similar to the one in
Figure 3-3 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-5
Chapter 3
Figure 3-3
Step 8
Enter the IP address or hostname of the MGC in the MGCHostname field (for example, 172.16.145.38).
Step 9
Step 10
Select the radio button to specify the protocol for connecting to the MGC.
Step 11
Select the radio button that corresponds to the PGW Mode you want to provision.
Step 12
Enter the network addresses (IP Addr: 1 and IP Addr: 2) in dotted notation (for example, 172.16.145.3),
or click Import Settings to import the network addresses.
Step 13
Indicate whether the MGC has a failover MGC, and if it does, enter the network addresses (Failover
IP Addr: 1 and Failover IP Addr: 2).
Step 14
Click Modify. The hierarchical tree display changes from Unknown MGC to the MGC host name you
entered in Step 8 (see Figure 3-4), and Modification complete displays briefly on the bottom left
portion of the window.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-6
OL-1110-23
Chapter 3
Figure 3-4
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-7
Chapter 3
Note
Point codes provide the addressing scheme for the SS7 network. ITU point codes contain 14 bits, and
ANSI point codes contain 24 bits.
Step 2
Click Point Codes > OPCs. A window similar to the one shown in Figure 3-5 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-8
OL-1110-23
Chapter 3
Figure 3-5
Step 3
Enter a name.
Step 4
Step 5
Step 6
National networkUsed if the node routes calls through the national network.
Step 7
Step 8
Select the name of the previously defined true OPC. This parameter applies only to the capability OPC.
Step 9
Click Add. The hierarchical tree changes to reflect the origination point code added.
Note
In a redundant configuration, the MGCs share the same OPC but have different IP addresses.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-9
Chapter 3
APC Properties
Property
MML
Parameter
Name
Description
Default
Valid Values
Name
name
STP-x
Up to 20 alphanumeric
characters
Description
desc
Adjacent
Point
Code
Up to 128 alphanumeric
characters
NetAddr
netaddr
0.0.0
User defined
NetIndicator
netind
National
International
National
Reserved for international use
Reserved for national use
Use the following procedure to add the APCs for STPs. Refer to Table 3-2 for property values.
Step 1
Step 2
Click Point Codes > APCs. A window similar to the one shown in Figure 3-6 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-10
OL-1110-23
Chapter 3
Figure 3-6
Step 3
Step 4
Step 5
Step 6
Step 7
National networkUsed if the node routes call through the national network.
Click Add. The hierarchical tree changes to reflect the APC added (STP-1).
Step 2
Click Point Codes > DPCs. A window similar to the one shown in Figure 3-7 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-11
Chapter 3
Figure 3-7
Step 3
Enter a name.
Step 4
Step 5
Step 6
Step 7
Step 8
ANSI
ETSI
In the NetIndicator drop-down menu, select one of the following network indicators:
National networkUsed if the node routes calls through the national network.
Click Add. The hierarchical tree changes to reflect the DPC added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-12
OL-1110-23
Chapter 3
Parameter Description
NAME
DESC
Component description
Up to 128 characters.
OPC
Associated OPC
DPC
ROUTING CONTEXT
SI
Service indicator
NETWORK APPEARNCE
The following rules apply when you are creating M3UA keys:
OPC and DPC cannot be deleted if it is being used by an SS7 signaling service.
Two M3UA keys or SUA keys cannot have the same routing context value.
Step 2
Click Routing Keys > M3UAs. A window similar to the one shown in Figure 3-8 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-13
Chapter 3
Figure 3-8
Step 3
Enter a name.
Step 4
Step 5
Step 6
In the Dest. Point Code drop-down menu, select the DPC. This parameter is optional.
Step 7
Step 8
Select the Service Indicator. Choices are ISUP, N/A, and TUP.
Step 9
Step 10
Click Add. The hierarchical tree changes to reflect the M3UA routing keys added.
Step 2
Click Routing Keys > SUAs. A window similar to the one shown in Figure 3-9 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-14
OL-1110-23
Chapter 3
Figure 3-9
Step 3
Enter a name.
Step 4
Step 5
Step 6
In the Adj. Point Code drop-down menu, select the APC. This parameter is optional.
Step 7
Enter the Local Simple Security Network (SSN); for example, 2-254.
Step 8
Enter the Routing Context. To use the routing context, its value must be set to any integer other than 0
(0 indicates that there is no routing context). The routing context value for each routing key you create
must be unique (for example, 0-2147483647).
Step 9
Enter the Network Appearance. This value must match the network appearance value set in your Cisco
ITP (for example, 0-32767).
Step 10
Click Add. The hierarchical tree changes to reflect the SUA routing keys added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-15
Chapter 3
Step 2
Click Location Label. A window similar to the one shown in Figure 3-10 displays.
Figure 3-10
Step 3
Enter a name.
Step 4
Step 5
Enter the Call Limiting value (for example, 0-2147483647 or 9999999, which allows all calls).
Step 6
Click Add. The hierarchical tree changes to reflect the location labels added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-16
OL-1110-23
Chapter 3
Adding Linksets
A linkset is a logical group of links that transport SS7 signals to the MGC. Linksets can consist of the
following:
Links from the MGC (OPC) to a destination (a DPC acting as an APC if there is no STP)
Table 3-4 lists linkset properties. Use the values in this table as you add linksets to your MGC.
Table 3-4
Linkset Properties
Property
MML Parameter
Description
Default
Valid Values
Name
name
Lnkset-x
Up to 20
alphanumeric
characters
Description desc
Lnkset
Up to 128
alphanumeric
characters
Point Code
apc
Protocol
proto
SS7-ANSI SS7-ANSI
SS7-China
SS7-ITU
SS7-Japan
SS7-UK
Type
type
IP
IP
TDM
Use the following procedure to add the linksets between the MGC node and the STPs. Refer to Table 3-4
for property values.
Step 1
Click LinkSets in the left pane of the main VSPT window. A window similar to the one shown in
Figure 3-11 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-17
Chapter 3
Figure 3-11
Adding Linksets
Step 2
Step 3
Step 4
In the Point Code drop-down menu, select the desired APC or DPC component for this linkset (for
example, STP-1).
Step 5
SS7-ANSI
SS7-China
SS7-ITU
SS7-Japan
SS7-UK
Step 6
Step 7
Click Add. The hierarchical tree changes to reflect the linkset added.
Note
After creating the linksets, you must create the links in each linkset by adding C7 IP Links. See
the Adding C7 IP Links section on page 3-93.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-18
OL-1110-23
Chapter 3
Highlight the appropriate linkset in the left pane of the main Cisco VSPT window.
Step 2
Click Properties to display the list of properties. A window similar to the one shown in Figure 3-12
displays.
Figure 3-12
Step 3
Step 4
Click Add. A window similar to the one shown in Figure 3-13 displays with the property added. After a
property has been added, it can be modified.
Figure 3-13
Step 5
Step 6
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-19
Chapter 3
Step 7
Click Modify.
Step 8
Note
You cannot modify properties until you have created the linkset.
Property
MML Parameter
Description
Default
Valid Values
Name
name
Ss7ss-1
Up to 20
alphanumeric
characters
Description
desc
SS7 Subsystem
Up to 128
alphanumeric
characters
None
Mating APCs
AIN Services
Subsystem
Type
TCAPIP or
APC
svc
<UNSET>
User defined
Priority
pri
1 through 16
Subsystem
number
ssn
x.x.x.x
0 through 99
Transport
Protocol
transproto
Protocol
Family
proto
<UNSET>
SCCP
TCP/IP
SS7-ANSI
SS7-China
SS7-ITU
SS7-Japan
SS7-UK
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-20
OL-1110-23
Chapter 3
To provision SS7 subsystems, use the steps provided in the subsections below.
Click SS7 Subsystems in the left pane of the main Cisco VSPT window. A window similar to the one
shown in Figure 3-14 displays.
Figure 3-14
Step 2
Enter a name.
Step 3
Step 4
Step 5
Step 6
In the APC drop-down menu, select the APC used for queries.
Step 7
In the Mated APC drop-down menu, select the APC of the second STP.
Step 8
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-21
Chapter 3
Step 9
Click Add. The hierarchical tree changes to reflect the SS7 Subsystems added.
Click SS7 Subsystems in the left pane of the main Cisco VSPT window. A window similar to the one
shown in Figure 3-15 displays.
Figure 3-15
Step 2
Enter a name.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-22
OL-1110-23
Chapter 3
Step 10
Step 11
Step 12
Step 13
Step 14
Click Add. The hierarchical tree changes to reflect the SS7 Subsystems added.
Note
If you have multiple linksets to an STP that use different protocol families, you must also have multiple
SS7 subsystems; one for each linkset that uses a specific protocol.
Step 2
Click ISUP Timer Profile in the left pane of the main VSPT window.
Step 3
Click Add. A window similar to the one shown in Figure 3-16 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-23
Chapter 3
Figure 3-16
Step 4
Enter a name.
Step 5
Step 6
Step 7
Click OK. The ISUP timer profile window changes to reflect the ISUP timer profile added.
Step 8
Select the appropriate ISUP timer profile in the ISUP timer profile.
Step 9
Step 10
Step 11
Click Add. The ISUP timer profile properties window changes to reflect the properties added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-24
OL-1110-23
Chapter 3
Table 3-6
Parameter MML
Name
Parameter
Description
NAME
SKORTCV
Service key
GTORSSN
Global title or
subsystem number
MSNAME
Message Sending
Name
Global title format (GTFORMAT) must be set to NOGT if the GTORSSN parameter is set to
ROUTEBYSSN. Otherwise, GTFORMAT must be set to a value other that NOGT.
Only one entry can exist in the INSERVICE table for each MSNAME.
Step 2
Click Inservice in the left pane of the main VSPT window. A window similar to the one shown in
Figure 3-17 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-25
Chapter 3
Figure 3-17
Step 3
Enter a name.
Step 4
Step 5
In the Global Title drop-down menu, select one of the following global titles:
Step 6
ROUTEBYGT
ROUTEBYSSN
In the Global Title Format drop-down menu, select one of the following global title formats:
GTONLY
GTTNBRENC
GTTT
NOGT
UNKNOWN
Step 7
Step 8
Click Add. The hierarchical tree changes to reflect the Inservice added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-26
OL-1110-23
Chapter 3
Property
MML Parameter
Description
Default
Valid Values
Name
name
None
Up to 20 alphanumeric
characters
Description
desc
None
Up to 128
alphanumeric
characters
Orig. Point
Code
opc
<UNSET>
User defined
Dest. Point
Code
dpc
<UNSET>
User defined
M3UAKey
m3uakey
m3uakey
M3UA Key
None
Side
side
network
network
user
MDO
mdo
Customer
Group ID
custgrpid
0009999; can be up to
4-digit alphanumeric
characters.
ISUP Timer
Profile
sigpathProf->isu
ptmrprofile
None
Origination
Label
origlabel
None
'Termination
Label
termlabel
None
Use the following procedure to add SS7 signaling service paths to the switch (identified by the DPC). If
you have a signaling service that extends from the MGC to a PSTN switch, use the SS7 path component
to add the service to your configuration. Refer to Table 3-7 for property values.
Step 1
Click SS7 Paths in the left pane of the main Cisco VSPT window. A window similar to the one shown
in Figure 3-18 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-27
Chapter 3
Figure 3-18
Step 2
Step 3
Step 4
In the Orig. Point Code drop-down menu, select the originating point code (the point code of the MGC)
for this signaling service.
Step 5
In the Dest. Point Code drop-down menu, select the destination point code (the point code of the PSTN
switch) for this signaling service.
Step 6
In the M3UAKey drop-down menu, select the M3UA routing key for this route.
Step 7
In the Side drop-down menu, select the side (Q.931 call model side):
Network
User
Step 8
In the MDO drop-down menu, select the protocol for this signaling service; for example,
ANSISS7_STANDARD.
Step 9
Step 10
In the ISUP Timer Profile drop-down menu, select the ISUP Timer Profile for this signaling service.
Step 11
In the Origination Label drop-down menu, select the Origination Location Label for this service.
Step 12
In the Termination Label drop-down menu, select the Termination Location Label for this service.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-28
OL-1110-23
Chapter 3
Step 13
Click Add. The hierarchical tree changes to reflect the SS7 path added.
Select the appropriate SS7 path in the left pane of the main Cisco VSPT window.
Step 2
Click Properties to display the list of properties. A window similar to the one shown in Figure 3-19
displays.
Figure 3-19
Step 3
Step 4
Enter a value.
Step 5
Click Add. A window similar to the one shown inFigure 3-20 displays with the property added. After a
property has been added, it can be modified.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-29
Chapter 3
Figure 3-20
Property Added
Step 6
Step 7
Step 8
Click Modify.
Step 9
Note
You cannot modify properties until you have created the SS7 path.
Property
MML Parameter
Description
Default
Valid Values
Name
name
Ss7r-1
Up to 20
alphanumeric
characters
Description
desc
SS7 Route
Up to 128
alphanumeric
characters
Originating PC
opc
<UNSET>
User defined
Destination PC
dpc
<UNSET>
User defined
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-30
OL-1110-23
Chapter 3
Table 3-8
Property
MML Parameter
Description
Default
Valid Values
Linkset
lnkset
<UNSET>
User defined
Priority
pri
1 through 4
You must add an SS7 route for each signaling path from the MGC to the PSTN switch through the
linksets you created to the STPs.
You should create two routes to the PSTN switch, with each route passing through a different STP of a
mated pair.
Use the following procedure to add SS7 routes to the MGC. Refer to Table 3-8 for property values.
Step 1
Click SS7 Routes in the left pane of the main Cisco VSPT window. A window similar to the one shown
in Figure 3-21 displays.
Figure 3-21
Step 2
Enter a name.
Step 3
Step 4
In the Originating PC drop-down menu, select the origination point code for this route.
Step 5
In the Destination PC drop-down menu, select the signal destination point code of the PSTN switch.
Step 6
In the Linkset drop-down menu, select the linkset for this route.
Step 7
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-31
Chapter 3
Note
Step 8
Routes can share signaling traffic. You can set load sharing by assigning the same priority to
each route.
Click Add. The hierarchical tree changes to reflect the SS7 route added.
Configuring IPRoutes
The IP route component is used to set the means for getting a message to a particular destination using IP.
Use the following procedure to add an IPRoute:
Step 1
Click IPRoute in the left pane of the main Cisco VSPT window. A window similar to the one shown in
Figure 3-22 displays.
Figure 3-22
Adding IPRoutes
Step 2
Enter a name.
Step 3
Step 4
IP Addr1
IP Addr2
IP Addr3
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-32
OL-1110-23
Chapter 3
IP Addr4
Step 5
Step 6
Step 7
Step 8
In the Priority drop-down menu, select a priority. Value range: 1 through 16. 1 is the highest priority.
Step 9
Click Add. The hierarchical tree changes to reflect the SS7 route added.
Parameter MML
Name
Parameter
Description
NAME
DESC
Component
description
Up to 128 characters.
DPC
Associated DPC
EXTNODE
OPC
Associated OPC
The following rules apply when you are creating and editing M3UA routes:
The associated DPC must have an SS7 signaling service with an M3UA key defined (matches DPC
attribute). If an M3UA key does not exist when the M3UA route is added or edited, a warning is
issued. If an M3UA key is still not defined when the provisioning session is copied or deployed, an
error message is generated and the copy or deployment is stopped.
Multiple DPCs with the same NETADDR cannot be routed to the same OPC.
For a given OPC/DPC, only one route can be defined through a given external node.
M3UA routes for the same OPC-DPC pair must have external nodes in the same group.
When the provisioning session is saved and activated, there must be an ASSOCIATION of type
M3UA using an SGP that is using the EXTNODE of each M3UAROUTE.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-33
Chapter 3
Step 1
Click M3UA Routes in the left pane of the main Cisco VSPT window. A window similar to the one
shown in Figure 3-23 displays.
Figure 3-23
Step 2
Enter a name.
Step 3
Step 4
In the Originating PC drop-down menu, select the origination point code for this route.
Step 5
In the Adjacent PC drop-down menu, select the signal destination point code of the PSTN switch.
Step 6
In the External Node drop-down menu, select the provisioned Cisco ITP external node for this route.
Step 7
Step 8
Click Add. The hierarchical tree changes to reflect the M3UA route added.
Click SUA Routes in the left pane of the main Cisco VSPT window. A window similar to the one shown
in Figure 3-24 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-34
OL-1110-23
Chapter 3
Figure 3-24
Step 2
Enter a name.
Step 3
Step 4
In the Originating PC drop-down menu, select the origination point code for this route.
Step 5
In the Adjacent PC drop-down menu, select the signal adjacent point code of the PSTN switch.
Step 6
In the External Node drop-down menu, select the provisioned Cisco ITP external node for this route.
Step 7
Step 8
Click Add. The hierarchical tree changes to reflect the SUA route added.
Highlight the appropriate sigpath in the left pane of the main Cisco VSPT window.
Step 2
Click Properties to display the list of properties. A window similar to the one shown in Figure 3-25
displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-35
Chapter 3
Figure 3-25
Step 3
Step 4
Click Add. A window similar to the one shown in Figure 3-26 displays with the property added. After a
property has been added, it can be modified.
Figure 3-26
Step 5
Step 6
Step 7
Click Modify.
Step 8
Note
You cannot modify properties until you have created the sigpath.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-36
OL-1110-23
Chapter 3
Step 1
Step 2
Click Line Number Translation in the left pane of the main VSPT window. A window similar to the
one shown in Figure 3-27 displays.
Figure 3-27
Step 3
Enter a name.
Step 4
Step 5
Step 6
Step 7
Called
Calling
Generic
Original called
Redirecting
Redirection
Step 8
Step 9
Step 10
Click Add. The hierarchical tree changes to reflect the Line Number Translation added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-37
Chapter 3
SIP Properties
Field Name
Description
Default
Valid Values
Name
Description
None
MDO
UNSET
UNSET
IETF_DCS
IETF_SIP
Up to 20 alphanumeric characters;
the name should begin with an
alphabetic character. - is the only
special character permitted.
In the left pane of the main Cisco VSPT window, click SIP > DNS. A window similar to the one shown
in Figure 3-28 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-38
OL-1110-23
Chapter 3
Figure 3-28
Step 2
Step 3
Step 4
Enter the Cache size, which is the maximum number of cache entries used to hold the DNS cache (for
example, 1999).
Step 5
Enter the TTL, which is the time-to-live interval for DNS entries, expressed in seconds (for example,
010800).
Step 6
In the Policy drop-down menu, click HIERARCHY or ROUND-ROBIN to indicate the policy type used
for selecting DNS entries.
Step 7
Enter the Query Timeout, which is the timeout interval for DNS queries, expressed in milliseconds (for
example, 10030000).
Step 8
Enter the Keepalive, which is the time interval to determine whether the DNS server is responding,
expressed in seconds (for example, 130).
Step 9
Click Add. The hierarchical tree changes to reflect the DNS added.
Click SIP in the left pane of the main Cisco VSPT window. A window similar to the one shown in
Figure 3-29 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-39
Chapter 3
Figure 3-29
Step 2
Enter a name.
Step 3
Step 4
In the MDO drop-down menu, select the protocol for this signaling service (for example, IETF_SIP).
Step 5
Step 6
Step 7
Click Add. The hierarchical tree changes to reflect the new SIP signaling path added.
Note
To add and change SIP signaling properties after it is created, see the Adding and Changing SIP
Signaling Properties section on page 3-40
Select the appropriate SIP signaling path in the left pane of the main Cisco VSPT window.
Step 2
Click Properties to display the list of properties. A window similar to the one shown in Figure 3-30
displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-40
OL-1110-23
Chapter 3
Figure 3-30
Step 3
Step 4
Click Add. A window similar to the one shown in Figure 3-31 displays with the property added. A
property can be modified after it is added.
Figure 3-31
Step 5
Step 6
Step 7
Click Modify.
Step 8
Note
Properties cannot be modified until you have created the SIP signaling path.
To add a SIP IP link for the SIP signaling path, see the Adding a SIP IP Link section on page 3-41.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-41
Chapter 3
Step 1
Click SIP > SIP path > Links in the left pane of the main Cisco VSPT window. A window similar to
the one shown in Figure 3-32 displays.
Figure 3-32
Step 2
Enter a name.
Step 3
Step 4
IP Addr1
IP Addr2
IP Addr3
IP Addr4
Virtual IP Addr1
Virtual IP Addr2
Step 5
Step 6
In the Priority drop-down menu, select a priority. Value range: 1 through 16. 1 is the highest priority.
Step 7
Click Add. The hierarchical tree changes to reflect the new SIP IP link added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-42
OL-1110-23
Chapter 3
In the left pane of the main Cisco VSPT window, click Auto Congestion Ctrl > Response Category. A
window similar to the one shown in Figure 3-33 displays.
Figure 3-33
Response Category
Step 2
Step 3
Enter values, in percentages, for load control types for ACL1, ACL2, and ACL3.
Step 4
Click Add. The hierarchical tree changes to reflect the response category added.
Step 5
Click MCL Thresholds. A window similar to the one shown in Figure 3-34 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-43
Chapter 3
Figure 3-34
Step 6
MCL Thresholds
Select the Machine Congestion Level (MCL) threshold name from the drop-down menu. MCLs can
be set for
Callrate
CPU
memoryaddress
queuelen
virtualmemory
Step 7
Enter MCL onset and abatement threshold values, in percentages for MCL1, MCL2, and MCL3.
Step 8
Click Add. The hierarchical tree changes to reflect the MCL threshold added.
Step 9
Click MCL Callreject. A window similar to the one shown in Figure 3-35 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-44
OL-1110-23
Chapter 3
Figure 3-35
Step 10
Step 11
Step 12
Click Add. The hierarchical tree changes to reflect the call reject rate added.
Configuring a Holiday
Use the following procedure to configure a holiday on the MGC:
Step 1
In the left pane of the main Cisco VSPT window, click Advice of Charge> Holiday. A window similar
to the one shown in Figure 3-36 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-45
Chapter 3
Figure 3-36
Step 2
Enter a date for the holiday by clicking the name in the drop-down list for the desired month.
Step 3
Step 4
Step 5
Step 6
UNSET
HOL1
HOL2
HOL3
Click Add to add the holiday date. The hierarchical tree changes to reflect the holiday added using a
yy.mm.dd format (for example, 02.12.25).
Configuring a Charge
Use the following procedure to configure a charge on the MGC:
Step 1
In the left pane of the main Cisco VSPT window, click Advice of Charge> Charge. A window similar
to the one shown in Figure 3-37 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-46
OL-1110-23
Chapter 3
Figure 3-37
Step 2
Step 3
Step 4
Step 5
Step 6
Click Add to add the charge. The hierarchical tree changes to reflect the charge added using an
xx-yy-day format (for example, 1-100-Sunday).
Configuring a Tariff
Use the following procedure to configure a tariff on the MGC:
Step 1
In the left pane of the main Cisco VSPT window, click Advice of Charge> Tariff. A window similar to
the one shown in Figure 3-38 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-47
Chapter 3
Figure 3-38
Step 2
Step 3
Step 4
Step 5
Click Add to add the tariff. The hierarchical tree changes to reflect the tariff added using the tariff ID as
the format (for example, 1).
In the left pane of the main Cisco VSPT window, click Advice of Charge> Meter Tariff. A window
similar to the one shown in Figure 3-39 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-48
OL-1110-23
Chapter 3
Figure 3-39
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Click Add to add the tariff. The hierarchical tree changes to reflect the meter tariff added using the tariff
ID as the format (for example, 1).
Configuring a Pritariff
Use the following procedure to configure a Pritariff on the MGC:
Step 1
In the left pane of the main Cisco VSPT window, click Advice of Charge > Pritariff. A window similar
to the one shown in Figure 3-40 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-49
Chapter 3
Figure 3-40
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
Step 17
Step 18
Step 19
Step 20
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-50
OL-1110-23
Chapter 3
Step 21
Step 22
Click Add to add the tariff. The hierarchical tree changes to reflect the pritariff added using the tariff ID
as the format (for example, 1).
Configuring a Pricharge
Use the following procedure to configure a tariff on the MGC:
Step 1
In the left pane of the main Cisco VSPT window, click Advice of Charge > Pricharge. A window
similar to the one shown in Figure 3-41 displays.
Figure 3-41
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Click Add to add the pricharge. The hierarchical tree changes to reflect the pricharge in an xx-yy-day
format (for example, 1-100-Sunday).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-51
Chapter 3
Step 2
Click GTD Parameters in the left pane of the main VSPT window. A window similar to the one shown
in Figure 3-42 displays.
Figure 3-42
Step 3
Enter a name.
Step 4
Step 5
Step 6
Click Add. The hierarchical tree changes to reflect the GTD Parameters added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-52
OL-1110-23
Chapter 3
Configuring TOS
The type-of-service (TOS) component is used to set a global dscp value to signaling traffic. To provision
TOS, use the following steps:
Step 1
Step 2
Click TOS in the left pane of the main VSPT window. A window similar to the one shown in Figure 3-43
displays.
Figure 3-43
Configuring TOS
Step 3
Step 4
Click Modify. The hierarchical tree changes to reflect the TOS configured.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-53
Chapter 3
Field Name
MML Parameter
Description
Default
Valid Values
Name
name
External-1
Up to 20
alphanumeric
characters;
cannot start
with a number
Description
desc
External Node
Up to 128
alphanumeric
characters
Type
type
<UNSET>
See the
drop-down list
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-54
OL-1110-23
Chapter 3
Use the external node component to add Cisco MGWs. You must create an external node for each Cisco
MGW.
Use the following procedure to add an external node to the MGC. Refer to Table 3-11 for property
values.
Step 1
Click External Node in the left pane of the main Cisco VSPT window. A window similar to the one
shown in Figure 3-44 displays.
Figure 3-44
Step 2
Enter a name.
Step 3
Step 4
In the Type drop-down menu, select the type of external node (for example, click MGX8850, and then
click Add). The hierarchical tree changes to reflect the external node added (for example, Cisco MGX
8850).
Step 5
In the ISDNSigType drop-down menu, select the ISDNSigtype. Choices are N/A and IUA.
Step 6
Step 7
Click Add. The hierarchical tree changes to reflect the External Nodes added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-55
Chapter 3
Use the following procedure to configure the external node as a Cisco MGW.
Step 1
Click the external node (added in the prior procedure) in the left pane of the main Cisco VSPT window.
A window similar to the one shown in Figure 3-45 displays.
Figure 3-45
Step 2
Step 3
Step 4
Step 5
Step 6
Click Modify. The hierarchical tree changes to reflect the Cisco MGW added.
Note
Specific components and steps to provision them vary depending on the type of external node you are
provisioning.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-56
OL-1110-23
Chapter 3
Field Name
Description
Default
Valid Values
Name
None
Up to 20 alphanumeric
characters; the name should
begin with an alphabetic
character. - is the only special
character permitted.
IPAddr1
IP_Addr1
IPAddr2
IP_Addr2
Port
None
102565535.
PeerAddr1
Remote IP address 1
None
PeerAddr2
Remote IP address 2
None
IPRoute 1
IP Route 1 Name
None
IPRoute 2
IP Route 2 Name
None
PeerPort
None
102565535.
Extnode
None
Type
IPFAS
Use the following procedure to add a session set to the MGC. Refer to Table 3-12 for property values.
Step 1
Click SESSIONSET in the left pane of the main Cisco VSPT window. A window similar to the one
shown in Figure 3-46 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-57
Chapter 3
Figure 3-46
Step 2
Enter a name.
Step 3
In the IP Addr 1 and IP Addr2 drop-down menus, select the appropriate IP address.
Step 4
Step 5
From the Peer Address 1 and Peer Address 2 drop-down menus, select the IP address of the peer gateway,
if applicable.
Step 6
In the IP Route 1 and IPRoute 2 drop-down menus, select the appropriate IPRoute.
Step 7
Step 8
In the Type drop-down menu, select the session set type. Choices are IPFAS and BSMV0.
Step 9
Click Add. The hierarchical tree changes to reflect the session set added (see Figure 3-46).
Select the appropriate sessionset in the left pane of the main Cisco VSPT window.
Step 2
Click Properties to display the list of properties. A window similar to the one shown in Figure 3-47
displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-58
OL-1110-23
Chapter 3
Figure 3-47
Step 3
Step 4
Click Add.
Step 5
Step 6
Step 7
Click Modify.
Step 8
Note
You cannot modify properties until you have created the sessionset.
Property
MML Parameter
Description
Default
Valid Values
Name
name
Ipfas-1
Up to 20
alphanumeric
characters.
Description
desc
Ipfaspath
signaling service
Up to 128
alphanumeric
characters.
External
Node
extnode
None
User defined.
Up to 20
alphanumeric
characters;
cannot start with
a number.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-59
Chapter 3
Table 3-13
Property
MML Parameter
Description
Default
Side
side
Valid Values
Network,
User.
MDO
mdo
Bell_1268
See list.
Customer
Group ID
custgrpid
0000
00009999.
A/B Flag
abflag
A side.
B side.
BNA.
crlen
Originating
Label
origlabel
None
See the
drop-down list in
Figure 3-51.
Termination
Label
termlabel
None
See the
drop-down list in
Figure 3-51.
Use the following procedure to add the ipfaspaths from the media gateway. The MML component name
is IPFASPath. Refer to Table 3-13 for property values.
Step 1
Click IPFAS in the left pane of the main Cisco VSPT window, and click Add in the right pane. A
window similar to the one shown in Figure 3-48 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-60
OL-1110-23
Chapter 3
Figure 3-48
Step 2
Enter a name.
Step 3
Step 4
In the Side drop-down menu, select the side (Q.931 call model side):
Network
User
Step 5
In the MDO File Name drop-down menu, select the protocol for this signaling service; for example,
ATT_41459.
Step 6
Step 7
Step 8
Step 9
In the Originating Label and Termination Label drop-down menus, select the appropriate value.
Step 10
In the Session Set drop-down menu, select the name of a session set.
Step 11
Step 12
Step 13
Step 14
Step 15
Note
You cannot have more than 168 IP links using the same UDP connection (same local port, local
IP address, remote port, and remote address).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-61
Chapter 3
Step 16
Click Add. The top portion of the window changes to reflect the IPFAS signaling service added, and the
D channel for the IPFAS signal path is displayed in the lower portion of the window (similar to the
window shown in Figure 3-49).
Note
Each FAS PRI defined in the Cisco MGW requires its own IPFASPath. Define an IPFASPath for
each PRI D channel on the Cisco MGW.
Figure 3-49
Step 17
To add more D channels to an IPFAS signaling path, highlight the IPFAS signaling path in the top pane
of the window, and click Add. A window similar to the one shown in Figure 3-50 displays.
Figure 3-50
Step 18
Add a D Channel
Enter a name.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-62
OL-1110-23
Chapter 3
Step 19
Step 20
Step 21
Step 22
Step 23
Step 24
Click Add. The new D channel for the IPFAS signaling path displays in the lower portion of the window.
Step 25
In the window shown in Figure 3-49, select an IPFAS signaling service from the top portion of the
window and click Modify. A window similar to the one shown in Figure 3-51 displays.
Figure 3-51
Step 2
To modify the IPFAS path configuration, click Properties. A window similar to the one shown in
Figure 3-52 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-63
Chapter 3
Figure 3-52
Step 3
Step 4
Step 5
Click Add. The new property and value appear in the top portion of the window.
Step 6
Step 7
Step 8
Click Modify.
Step 9
Note
You cannot modify properties until you have created the IPFAS signaling service.
Property
MML Parameter
Description
Default
Valid Values
Name
name
Up to 20
alphanumeric
characters
Description
desc
Mgcppath
Signaling Service
Up to 128
alphanumeric
characters
External
Node
extnode
None
User defined
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-64
OL-1110-23
Chapter 3
Note
Set the mgcpDomainNameRemote and mgcpHeartbeatInterval properties for all MGCP Signaling
Services defined in your Cisco MGC. For more information, see the Adding and Changing MGCP
Signaling Service Properties section on page 3-65.
Use the following procedure to add MGCP signaling service paths to the media gateway. Refer to
Table 3-14 for property values.
Step 1
Click MGCP in the left pane of the main Cisco VSPT window. A window similar to the one shown in
Figure 3-53 displays.
Figure 3-53
Step 2
Enter a name.
Step 3
Step 4
Click Add. The hierarchical tree changes to reflect the MGCP signaling service link added.
mgcpDomainNameRemoteA valid endpoint of the gateway (for example, a VISM card in a media
gateway with a domain name of mgx88501.vism01 would be vism/t1-1/1@mgx88501.vism01).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-65
Chapter 3
The media gateway MGCP domain name is a property of the media gateway object. You can derive
this from the MGCP path object, because each MGCP path object refers to an external node and each
external node refers to a media gateway.
mgcpHeartbeatInterval1.
Use the following procedure to add or change MGCP signaling service properties:
Step 1
Click Properties to display the list of properties. A window similar to the one shown in Figure 3-54
displays.
Figure 3-54
Step 2
To add a property, select the property name from the drop-down menu and enter the value, and click Add.
A window similar to the one shown in Figure 3-55 displays with the property added.
Figure 3-55
Step 3
Step 4
Step 5
Click Modify.
Step 6
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-66
OL-1110-23
Chapter 3
Note
You cannot modify properties until you have created the MGCP signaling service.
Click DPNSS in the left pane of the main Cisco VSPT window. A window similar to the one shown in
Figure 3-56 displays.
Figure 3-56
Step 2
Enter a name.
Step 3
Step 4
Step 5
Step 6
Step 7
In the Origination Label and Termination Label drop-down menu, select the appropriate location label.
Step 8
Click Add. The hierarchical tree changes to reflect the DPNSS path added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-67
Chapter 3
Click Properties to display the list of properties. A window similar to the one shown in Figure 3-57
displays.
Figure 3-57
Step 2
Step 3
Click Add. A window similar to the one shown in Figure 3-58 displays with the property added.
Figure 3-58
Step 4
Step 5
Step 6
Click Modify.
Step 7
Note
You cannot modify properties until you have created the DPNSS path.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-68
OL-1110-23
Chapter 3
Click H248 in the left pane of the main Cisco VSPT window. A window similar to the one shown in
Figure 3-59 displays.
Figure 3-59
Step 2
Enter a name.
Step 3
Step 4
Click Add. The hierarchical tree changes to reflect the H248 signaling service added.
Click Properties to display the list of properties. A window similar to the one shown in Figure 3-60
displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-69
Chapter 3
Figure 3-60
Step 2
Step 3
Click Add. A window similar to the one shown in Figure 3-61 displays with the property added.
Figure 3-61
Step 4
Step 5
Step 6
Click Modify.
Step 7
Note
You cannot modify properties until you have created the H248 signaling service.
Click EISUP in the left pane of the main Cisco VSPT window. A window similar to the one shown in
Figure 3-62 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-70
OL-1110-23
Chapter 3
Figure 3-62
Step 2
Enter a name.
Step 3
Step 4
Step 5
In the Origination Label and Termination Label drop-down menus, select the appropriate location label.
Step 6
Click Add. The hierarchical tree changes to reflect the EISUP signaling service added.
Click Properties to display the list of properties. A window similar to the one shown in Figure 3-63
displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-71
Chapter 3
Figure 3-63
Step 2
Step 3
Click Add. A window similar to the one shown in Figure 3-64 displays with the property added.
Figure 3-64
Step 4
Step 5
Step 6
Click Modify.
Step 7
Note
You cannot modify properties until you have created the EISUP signaling service.
Click LI in the left pane of the main Cisco VSPT window. A window similar to the one shown in
Figure 3-65 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-72
OL-1110-23
Chapter 3
Figure 3-65
Step 2
Enter a name.
Step 3
Step 4
Click Add. The hierarchical tree changes to reflect the LIpath signaling service added.
Click Properties to display the list of properties. A window similar to the one shown in Figure 3-66
displays.
Figure 3-66
Step 2
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-73
Chapter 3
Step 3
Click Add. A window similar to the one shown in Figure 3-67 displays with the property added.
Figure 3-67
Step 4
Step 5
Step 6
Click Modify.
Step 7
Note
You cannot modify properties until you have created the LI signaling service.
Click NAS in the left pane of the main Cisco VSPT window. A window similar to the one shown in
Figure 3-681 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-74
OL-1110-23
Chapter 3
Figure 3-68
Step 2
Enter a name.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Click Add. The hierarchical tree changes to reflect the EISUP signaling service added.
Click Properties to display the list of properties. A window similar to the one shown in Figure 3-69
displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-75
Chapter 3
Figure 3-69
Step 2
Step 3
Click Add. A window similar to the one shown in Figure 3-70 displays with the property added.
Figure 3-70
Step 4
Step 5
Step 6
Click Modify.
Step 7
Note
You cannot modify properties until you have created the NAS signaling service.
Click CTI in the left pane of the main Cisco VSPT window. A window similar to the one shown in
Figure 3-71 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-76
OL-1110-23
Chapter 3
Figure 3-71
Step 2
Enter a name.
Step 3
Step 4
Step 5
Click Add. The hierarchical tree changes to reflect the EISUP signaling service added.
Click Properties to display the list of properties. A window similar to the one shown in Figure 3-72
displays.
Figure 3-72
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-77
Chapter 3
Step 2
Step 3
Click Add. A window similar to the one shown in Figure 3-73 displays with the property added.
Figure 3-73
Step 4
Step 5
Step 6
Click Modify.
Step 7
Note
You cannot modify properties until you have created the CTI signaling service.
Click SGP in the left pane of the main Cisco VSPT window. A window similar to the one shown in
Figure 3-74 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-78
OL-1110-23
Chapter 3
Figure 3-74
Step 2
Step 3
Step 4
Click Add. The hierarchical tree changes to reflect the SS7 SGP added.
Adding a TCPLNK
Use the following procedure to add a TCPLNK:
Step 1
Click TCPLNK in the left pane of the main Cisco VSPT window. A window similar to the one shown
in Figure 3-75 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-79
Chapter 3
Figure 3-75
Adding a TCPLNK
Step 2
Enter a name.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Click Add. The hierarchical tree changes to reflect the Tcplnk added.
Select the appropriate Tcplnk in the left pane of the main Cisco VSPT window.
Step 2
Click Properties to display the list of properties. A window similar to the one shown in Figure 3-76
displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-80
OL-1110-23
Chapter 3
Figure 3-76
Step 3
Step 4
Click Add.
Step 5
Step 6
Step 7
Click Modify.
Step 8
Note
You cannot modify properties until you have created the Tcplnk.
Click BRI in the left pane of the main Cisco VSPT window.
Step 2
Click Add. A window similar to the one shown in Figure 3-77 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-81
Chapter 3
Figure 3-77
Step 3
Enter a name.
Step 4
Step 5
In the Side drop-down menu, select one of the following sides (Q.931 call model side):
Network
User
Step 6
In the MDO drop-down menu, select the protocol for this signaling service (for example, ATT_41459).
Step 7
Step 8
In the Call Reference Length drop-down menu, select 0, 1, or 2 (0- DPNSS, 1 - 1 byte, 2 - 2 bytes).
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
Click Add. The top portion of the window changes to reflect the BRI signaling service added, and the
D channel for the BRI signal path is displayed in the lower portion of the window (similar to the window
shown in Figure 3-78).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-82
OL-1110-23
Chapter 3
Figure 3-78
Step 15
To modify D channels in a BRI signaling path, select the BRI signaling path in the top pane of the
window, and click Add. A window similar to the one shown in Figure 3-79 displays.
Figure 3-79
Modify a D Channel
Step 16
Enter a name.
Step 17
Enter a description.
Step 18
Step 19
Step 20
Step 21
Select a Tcplnk.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-83
Chapter 3
Step 22
Click OK. The D channel for the BRI signaling path displays in the lower portion of the window.
Adding a RAPATH
Use the following procedure to define a communication path to a RADIUS accounting server cluster.
Each cluster is made up of one or multiple RADIUS servers.
Step 1
Click RAPATH in the left pane of the main Cisco VSPT window. A window similar to the one shown
in Figure 3-80 displays.
Figure 3-80
Adding a RAPATH
Step 2
Enter a name.
Step 3
Step 4
Click Add. The hierarchical tree changes to reflect the RAPATH added.
Click the icon next to RAPATH in the left pane of the main Cisco VSPT window to expand the tree, and
click RASERVER. A window similar to the one shown in Figure 3-81 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-84
OL-1110-23
Chapter 3
Figure 3-81
Adding RASERVER
Step 2
Enter a name.
Step 3
Step 4
Note
IP Addr1
IP Addr2
IP Addr3
IP Addr4
The numbered address for this value is found in the XECfgParm.dat file set during your initial system
configuration. See the Cisco Media Gateway Controller Software Installation and Configuration
(Release 9.7) for more information.
Step 5
Enter a number for the UDP port on the MGC. You can use any unused UDP port number, but you should
not use 1 through 1024; these are reserved for other applications.
Step 6
Step 7
Step 8
Step 9
Step 10
Click Add. The hierarchical tree changes to reflect the RASERVER added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-85
Chapter 3
Configuring IP Links
The last step in adding Cisco MGW control links is the configuration of the IP links. You must identify
each end of each link:
At the MGC node end of each link, associate the link with an Ethernet interface, an IP address, and
an IP port.
At the media gateway end of each link, identify the signaling link terminal by specifying an IP
address and port.
Click the icon next to MGCP in the left pane of the main Cisco VSPT window to expand the tree, and
click Links. A window similar to the one shown in Figure 3-82 displays.
Figure 3-82
Step 2
Enter a name.
Step 3
Step 4
IP Addr1
IP Addr2
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-86
OL-1110-23
Chapter 3
IP Addr3
IP Addr4
Note
The numbered IP address is found in the XECfgParm.dat file set during your initial system
configuration. See the Cisco Media Gateway Controller Software Installation and Configuration
(Release 9.7) for more information.
Step 5
Step 6
Enter a number of the UDP port on the MGC. You can enter any unused UDP port number (2427 is
recommended for MGCP), but you should not use 1 through 1024; these are reserved for other
applications.
Step 7
In the Priority drop-down menu, select a priority. Value range: 1 through 4. 1 is the highest priority.
Step 8
Step 9
Step 10
Click Add. The hierarchical tree changes to reflect the MGCP IP link added (see Figure 3-82).
Click the icon next to H248 in the left pane of the main Cisco VSPT window to expand the tree, and click
Links. A window similar to the one shown in Figure 3-83 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-87
Chapter 3
Figure 3-83
Step 2
Enter a name.
Step 3
Step 4
Note
IP Addr1
IP Addr2
IP Addr3
IP Addr4
The numbered IP address for this value is found in the XECfgParm.dat file set during your initial system
configuration. See the Cisco Media Gateway Controller Software Installation and Configuration
(Release 9.7) for more information.
Step 5
Step 6
Enter a number of the UDP port on the MGC. You can enter any unused UDP port number (2944 is
recommended for H248), but you should not use 1 through 1024; these are reserved for other
applications.
Step 7
In the Priority drop-down menu, select a priority. Value range: 1 through 4. 1 is the highest priority.
Step 8
Step 9
Step 10
Click Add. The hierarchical tree changes to reflect the H248 IP link added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-88
OL-1110-23
Chapter 3
Click the icon next to EISUP in the left pane of the main Cisco VSPT window to expand the tree, and
click Links. A window similar to the one shown in Figure 3-84 displays.
Figure 3-84
Step 2
Enter a name.
Step 3
Step 4
Note
Step 5
IP Addr1
IP Addr2
IP Addr3
IP Addr4
The numbered IP address for this value is found in the XECfgParm.dat file set during your initial system
configuration. See the Cisco Media Gateway Controller Software Installation and Configuration
(Release 9.7) for more information.
In the IP Route drop-down menu, select the appropriate IP route.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-89
Chapter 3
Step 6
Enter a number of the UDP port on the MGC. You can enter any unused UDP port number (5001 is
recommended for EISUP), but you should not use 1 through 1024; these are reserved for other
applications.
Step 7
In the Priority drop-down menu, select a priority. Value range: 1 through 4. 1 is the highest priority.
Step 8
Step 9
Step 10
Click Add. The hierarchical tree changes to reflect the EISUP IP link added.
Click the icon next to LI in the left pane of the main Cisco VSPT window to expand the tree, and click
Links. A window similar to the one shown in Figure 3-85 displays.
Figure 3-85
Adding LI IP Links
Step 2
Enter a name.
Step 3
Step 4
IP Addr1
IP Addr2
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-90
OL-1110-23
Chapter 3
Note
IP Addr3
IP Addr4
The numbered IP address for this value is found in the XECfgParm.dat file set during your initial system
configuration. See the Cisco Media Gateway Controller Software Installation and Configuration
(Release 9.7) for more information.
Step 5
Step 6
Enter a number of the UDP port on the MGC. You can enter any unused UDP port number (2047 is
recommended for LI), but you should not use 1 through 1024; these are reserved for other applications.
Step 7
In the Priority drop-down menu, select a priority. Value range: 1 through 4. 1 is the highest priority.
Step 8
Step 9
Step 10
Click Add. The hierarchical tree changes to reflect the LI IP link added.
Click the icon next to NAS in the left pane of the main Cisco VSPT window to expand the tree, and click
Links. A window similar to the one shown in Figure 3-86 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-91
Chapter 3
Figure 3-86
Step 2
Enter a name.
Step 3
Step 4
Note
IP Addr1
IP Addr2
IP Addr3
IP Addr4
The numbered IP address for this value is found in the XECfgParm.dat file set during your initial system
configuration. See the Cisco Media Gateway Controller Software Installation and Configuration
(Release 9.7) for more information.
Step 5
Step 6
Enter a number of the UDP port on the MGC. You can use any unused UDP port number (3001 is
recommended for NAS), but you should not use 1 through 1024; these are reserved for other
applications.
Step 7
In the Priority drop-down menu, select a priority. Value range: 1 through 4. 1 is the highest priority.
Step 8
Step 9
Step 10
Click Add. The hierarchical tree changes to reflect the NAS IP link added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-92
OL-1110-23
Chapter 3
Adding C7 IP Links
Use the following procedure to add C7 IP links.
Step 1
Click C7 in the left pane of the main Cisco VSPT window. A window similar to the one shown in
Figure 3-87 displays.
Figure 3-87
Adding a C7 IP Link
Step 2
Enter a name.
Step 3
Step 4
Step 5
In the Linkset drop-down menu, select the linkset for this link.
Note
Step 6
In the SLC drop-down menu, select the SLC. This is the SLC for the line between the Cisco ITP-L and
the STP. The SLC can be any integer from 0 through 15.
Step 7
In the SLT Port drop-down menu, select the time slot. This is the physical port on the Cisco ITP-L.
Note
The time slot identifies the port number on the Cisco ITP-L. The time slot number must be
unique for a link on a particular Cisco ITP-L. For example, if you have a 2T WAN interface card
(WIC) in slot 0 of the Cisco ITP-L, you can use time slot value 0 for the first link you configure.
The second link on the WIC uses the time slot value 1.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-93
Chapter 3
Step 8
In the Session Set drop-down menu, select the session set for this link.
Step 9
Click Add. The hierarchical tree changes to reflect the C7 IP link added.
Adding an ASSOCIATION
Use the following procedure to add an association:
Step 1
Click ASSOCIATION in the left pane of the main Cisco VSPT window. A window similar to the one
shown in Figure 3-88 displays.
Figure 3-88
Step 2
Enter a name.
Step 3
Step 4
In the Type drop-down menu, select the appropriate type. Choices are H248, IUA, M3UA, and SUA.
Step 5
In the IP Addr 1 and IP Addr 2 drop-down menu, select the appropriate ip addr.
Step 6
Step 7
In the Peer Address 1 and Peer Address 2 drop-down menu, select the appropriate peer ip addr.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-94
OL-1110-23
Chapter 3
Step 8
Step 9
In the IPRoute1 and IPRoute 2 drop-down menus, select the appropriate iproute.
Step 10
Step 11
Step 12
Step 13
Step 14
Enter the Max Time for datagram (valid value range: 100 to 500).
Step 15
Enter the SCTP Max Wait Time (valid value range: 100 to 600).
Step 16
Enter the Retrans Time Min Val (valid value range: 300 to 3000).
Step 17
Enter the Retrans Time Max Val (valid value range: 10003000).
Step 18
Enter the Retrans Time Out (valid value range: 0 or a value from 300 to 10000).
Step 19
In the Internet Protocol Precedence drop-down menu, select the appropriate ip precedence.
Step 20
In the Differential Service Code Point drop-down menu, select the appropriate dscp.
Step 21
Step 22
Click Add. The hierarchical tree changes to reflect the association added.
Click CTI Manager in the left pane of the main Cisco VSPT window. A window similar to the one
shown in Figure 3-89 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-95
Chapter 3
Figure 3-89
Step 2
Enter a name.
Step 3
Step 4
In the IP Addr 1 and IP Addr 2 drop-down menus, select the appropriate ip addr.
Step 5
Step 6
Step 7
Step 8
In the Peer Address 1 and Peer Address 2 drop-down menus, select the appropriate peer ip addr.
Step 9
Step 10
In the IPRoute 1 and IPRoute 2 drop-down menus, select the appropriate iproute.
Step 11
Step 12
Click Add. The hierarchical tree changes to reflect the CTI Manager added.
Click AXL Server in the left pane of the main Cisco VSPT window. A window similar to the one shown
in Figure 3-90 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-96
OL-1110-23
Chapter 3
Figure 3-90
Step 2
Step 3
Step 4
In the IP Addr 1 and IP Addr 2 drop-down menus, select the appropriate ip addr.
Step 5
Step 6
Step 7
Step 8
In the Peer Address 1 and Peer Address 2 drop-down menus, select the appropriate peer ip addr.
Step 9
Step 10
In the IPRoute 1 and IPRoute 2 drop-down menus, select the appropriate iproute.
Step 11
Step 12
Click Add. The hierarchical tree changes to reflect the AXL Server added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-97
Chapter 3
The two main scenarios you are likely to follow when setting up the MGC node for call routing are
described in Table 3-15.
Table 3-15
Modify an existing
configuration
Add all of the trunk groups, one by one, using the instructions in the
Adding Trunk Groups section on page 3-102.
Add all of the trunks to the configured trunk groups, trunk group by
trunk group, using the instructions in the Adding Trunks section
on page 3-139.
Add all of the route groups, one by one, using the instructions in the
Adding Routes section on page 3-147.
Caution
SS7 components must be provisioned before you provision the PRI components. When trunk groups are
provisioned by the importing of customer trunk group files, all of the existing trunk groups and trunks
are deleted. PRI trunk groups and trunks are provisioned by the use of individual MML commands,
which do not delete all of the existing trunk groups and trunks. If the PRI components are provisioned
before SS7 components, all PRI trunk groups and trunks are deleted.
To configure bearer traffic, use the steps provided in the sections below.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-98
OL-1110-23
Chapter 3
Tip
The trunk file must contain all trunks, also know as Circuit Identification Codes (CICs), in a trunk group.
Perform the following steps to import a trunk group or trunk:
Step 1
Select File > Import. A window similar to the one shown in Figure 3-91 displays.
Figure 3-91
Step 2
Importing Files
Click From File, and In the File type drop-down menu, select the type of file you want to import (see
Figure 3-92).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-99
Chapter 3
Figure 3-92
Step 3
Enter the name of the file you want to import. If you do not know the name of the file, click Select. A
window similar to the one shown in Figure 3-93 displays.
Figure 3-93
Step 4
Select the file you want to import, and click Open. A window similar to the one shown in Figure 3-92
displays again, and the full path name of the file you selected displays in the file name box.
Step 5
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-100
OL-1110-23
Chapter 3
Select the Traffic radio button in the top portion of the main Cisco VSPT window.
Step 2
Step 3
Click Add.
Step 4
Enter the name, and click OK. A window similar to the one shown in Figure 3-94 displays.
Figure 3-94
Step 5
To add or modify a profile property, select the profile name in the top pane of the window.
Step 6
Select a property in the name drop-down list, and enter the value.
Step 7
Click Add. The new property and value are displayed in the lower pane of the window.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-101
Chapter 3
Tip
For information about importing the trunk group file, see the Importing Trunk Groups and Trunks
section on page 3-99. For a list of trunk group parameters, see Table 3-16 on page 3-104.
Use the following procedure to add a trunk group:
Step 1
Select the Traffic radio button in the top portion of the main Cisco VSPT window.
Step 2
Step 3
Click Add. A window similar to the one shown in Figure 3-95 displays.
Figure 3-95
Step 4
Step 5
Enter the Common Language Location Identification (CLLI). This can be up to 11 alphanumerical digits.
Step 6
In the Signaling Service drop-down menu, select the type of signal service.
Step 7
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-102
OL-1110-23
Chapter 3
Step 8
In the Queueable Type drop-down menu, indicate whether or not the trunk group can be queued.
Step 9
Step 10
Step 11
Step 12
Step 13
Click the Prop-1 tab. A window similar to the one shown in Figure 3-96 displays.
Figure 3-96
Step 14
Step 15
Step 16
Step 17
Step 18
Step 19
Step 20
Step 21
Step 22
Step 23
Select whether trunks detect fax modem tones, and then select Yes or No.
Step 24
Step 25
Step 26
Note
Additional properties can be configured from the property tabs depending on the signaling service type
selected. See Table 3-16 on page 3-104 for a list of trunk group parameters.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-103
Chapter 3
Step 27
Click OK. A window similar to the one shown in Figure 3-97 displays with the trunk group added.
Figure 3-97
Note
After you have added a trunk group, it cannot be deleted it if there are still trunks defined in the trunk
group or if there are existing route groups that refer to the trunk group. To maintain the integrity of the
data in the traffic configuration branch, you have to first delete all trunks in the trunk group and remove
any references from the route groups before you can delete the trunk group.
MML Parameter
Name
Description
TrunkGroup Tab
Trunk Group Number
Name
Unique number (up to seven digits) assigned to each trunk group that is used
by route analysis. (The string tg- is pre-pended to this number to create the
MML name of the trunk group used in components.dat yielding an MML
name of no more than 10 characters.)
CLLI
CLLI
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-104
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
Signaling Service
Signal Service
Trunk Type
Type
Description
TDM_GEN-Used with SS7 signaling services with switch types not equal to
0, 5, 20, 23, or 40.
TDM_ISUP-Used with SS7 signaling services with switch types of 0, 20, 23,
or 40.
TDM_CAS-Currently not supported.
TDM_TUP-Used with SS7 signaling services with switch type of 5.
IP-Used with EISUP signaling service.
ATM-Used with VSI path signaling service.
TDM_DPNSS-Used with DPNSS protocol family signaling services
TDM_ PRI-Used with ISDN PRI protocol family signaling services.
TDM_BTNUP-Used with SS7 signaling services with switch type of
5.
IP_SIP-Used for SIP signaling services at the terminating side.
SIP_IN-Used for SIP signaling services at the originating side (only one such
trunk group can be configured on each MGC node).
CTI-Used with CTI signaling services.
Switch type values are:
0 = No switch-specific logic 23 = SS7 ANSI
for the signaling path.26 = DPNSS
5 = BTNUP27 = NET5
10 = SS7 Japan29 = QSIG MASTER
17 = 5ESS30 = QSIG SLAVE
20 = SS7 Clear40 = SS7 ITU
22 = NI2.
Queueable Type
QABLE
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-105
Chapter 3
Table 3-16
MML Parameter
Name
Select Sequence
selseq
Description
Specifies the trunk selection sequence. The Cisco PGW 2200 Softswitch uses
the CICs within a trunk group according to the sequence specified by the
SELSEQ value. You can provision this value to reduce the chance of glare
when the system selects a trunk.
ASC = Ascending. The system selects the available CICs in ascending order
starting from the lowest CIC number (for example, 1, 2, 3 ...).
CASC = Cyclic ascending. The system selects the next available CIC in
ascending order based on the most recently selected CIC. For example, if the
most recently selected CIC is CIC 5, the system selects CIC 6, even if CIC 1
is available.
CDESC = Cyclic descending. Similar to CASC, but in descending order
based on the most recently selected CIC. For example, if the last selected CIC
is number 18, the system selects CIC 17, even if CIC 31 is available.
DESC = Descending. Similar to ASC, but in descending order starting from
the highest CIC number (for example, 31, 30, 29 ...).
EASC = Even ascending, then odd ascending. The system selects the first
available even CIC in ascending order (for example, 2, 4, 6 ...). If no even CIC
is available in the trunk group, the system selects the first available odd CIC
in ascending order (for example, 1, 3, 5 ...).
EDECS = Even descending, then odd descending. Similar to EASC, but in
descending order. The system selects the first available even CIC in
descending order (for example, 30, 28, 26 ...). If no even CIC is available in
the trunk group, the system selects the first available odd CIC in descending
order (for example, 31, 29, 27 ...).
ITU2 = ITU method 2. The system selects the trunk according to the
procedure in ITU-T Recommendation Q.764, paragraph 2.9.1.3 Method 2.
continued ....
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-106
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
Description
selseq
... continued:
LIDL = Least idle (default). The system selects the least idle (most recently
used) CIC.
MIDL = Most idle. The system selects the most idle (least recently used) CIC.
OASC = Odd ascending, then even ascending. The system selects the first
available odd CIC in ascending order (for example, 1, 3, 5 ...). If no odd CIC
is available in the trunk group, the system selects the first available even CIC
in ascending order (for example, 2, 4, 6...).
ODESC = Odd descending, then even descending. Similar to OASC, but in
descending order. The system selects the first available odd CIC in
descending order (for example, 31, 29, 27 ...). If no odd CIC is available in
the trunk group, the system selects the first available even CIC in descending
order (for example, 30, 28, 26 ...).
RDM = Random. The system selects a CIC at random.
Caution
VSF Priority
VSF
Originating Location
Label
OrigLabel
This property defines the originating label for the trunk group.
Terminating Location
Label
TermLabel
This property inhibit the terminating label for the trunk group
Default
Default
This parameter dictates whether the trunk group is the default IP incoming
trunk group of the SIP/EISUP path. The value 1 means this trunk group is the
default IP incoming trunk of the SIP/EISUP path.
Profile
Profile
This property indicates the trunk group profile for the trunk group.
Reattempts
Reattempts
Queuing
Queuing
Routing Property
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-107
Chapter 3
Table 3-16
MML Parameter
Name
Description
Cutthrough
ResIncoming
Perc
ResIncPerc
BearerCap
BearerCap
Name
Defines the bearer capability of a trunk group in the route to which the
Cisco PGW 2200 Softswitch can preferentially route calls with a specific
bearer capability.
Ring No Answer
RingNoAnswer
Glare
GLARE
Glare control. Glare is a collision that occurs when two network nodes
simultaneously attempt to reserve the same channel. Values are: 1 (always),
2 (even/odd), or 3 (never) (default).
COT percentage
CotPercentage
Determines the percentage of calls on the trunk upon which a continuity test
is performed. Value range: 0 through 100.
Satellite
SatelliteInd
Satellite indicator. Indicates if the trunk is going over a satellite. Values are 0
(no) (default) or 1 (yes).
Npa
Numbering Plan Area. Indicates the NPA code associated with the incoming
trunk group. Value range: 0 (none) (default), or a 3-digit code from 200
through 999.
Customer group ID
CustGrpId
Customer group ID. The ID of the customer associated with this trunk group.
Value range: 0 (if not defined) or any 4-character alphanumeric string.
Compression Type
CompressionType
Compression type. Identifies the G.711 compression type used on the trunk.
After the fax or modem tone has been detected by the Cisco MGW, select the
proper compression type. Values are: 0 (none), 1 (mu-law) (default), 2
(A-law), or 3 (clear channel).
Echo Canceller
Required
EchoCanRequired
Prop-1 tab
The Cisco PGW 2200 Softswitch follows the following procedure for an SS7
terminated call after the call is answered. If the Cisco PGW 2200 Softswitch
receives a call-in-progress message (CPG) with backward call indicators
(BCI) from the SS7 side, it takes the specified action.
If EchoCanRequired=1:
If the echo device indicator = 0 in BCI, send MDCX with e: on
If the echo device indicator = 1 in BCI, send MDCX with e: off
If EchoCanRequired=0 (default):
Do not send an MDCX for echo control
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-108
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
External COT
ExtCOT
DetectFaxModemT Detect Fax modem tone. Indicates if Fax modem tone is to be detected. Used
one
for MGCP connection protocol. Values are: 0 (no tone detection notification)
or 1 (request fax or modem tone detection from the Cisco MGW.
WaitOrigSDPTimer Wait for originating SDP timer. On H.323 originated calls, the MGC transits
the answer message and starts this timer when the originating SDP
information has not been received. Value range: 0 to 50 (in seconds).
WaitTermSDPTime Wait for terminating SDP timer. On H.323 terminated calls, the MGC transits
r
the answer message and starts this timer when the terminating SDP
information has not been received. Value range: 0 to 50 (in seconds).
SendAddressnCgpn Send address in the calling party number. Determines if the CLI digits are
sent in the outgoing calling party number parameter. Value is 0 (False) for do
not include address digits in calling party number parameter, or 1 (True)
(default) for including address digits in calling party number parameter.
Description
External continuity test. Indicates the type of COT handling for the specified
destination. Values are: 0-no COT, loop (default), or transponder.
Prop-2
Maximum ACL
MaxACL
ACL Duration
ACLDuration-
ACCRespCntlInhib Automatic congestion control response inhibit. Enables or disables the ACC
it
control procedures based on the ACL value received by MGC from a linked
switch. Values are: 0 (default) or 1.
ISUP Transparency
Disabled
IsupTransparencyD ISUP transparency disable function. Permits disabling the ISUP transparency
isabled
feature for a specified trunk group. Values are: 0 (ISUP transparency
enabled), or 1 (ISUP transparency disabled) (default).
AOC Enabled
AOCEnabled
Carrier Screening
CarrierScreening
Originating Carrier ID
OrigCarrierId
NotifySetupCompl
ete
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-109
Chapter 3
Table 3-16
MML Parameter
Name
Signaling Service
Signal Service
Trunk Type
Type
Description
TDM_GEN-Used with SS7 signaling services with switch types not equal to
0, 5, 20, 23, or 40.
TDM_ISUP-Used with SS7 signaling services with switch types of 0, 20, 23,
or 40.
TDM_CAS-Currently not supported.
TDM_TUP-Used with SS7 signaling services with switch type of 5.
IP-Used with EISUP signaling service.
ATM-Used with VSI path signaling service.
TDM_DPNSS-Used with DPNSS protocol family signaling services
TDM_ PRI-Used with ISDN PRI protocol family signaling services.
TDM_BTNUP-Used with SS7 signaling services with switch type of
5.
IP_SIP-Used for SIP signaling services at the terminating side.
SIP_IN-Used for SIP signaling services at the originating side (only one such
trunk group can be configured on each MGC node).
CTI-Used with CTI signaling services.
Switch type values are:
0 = No switch-specific logic 23 = SS7 ANSI
for the signaling path.26 = DPNSS
5 = BTNUP27 = NET5
10 = SS7 Japan29 = QSIG MASTER
17 = 5ESS30 = QSIG SLAVE
20 = SS7 Clear40 = SS7 ITU
22 = NI2.
Queueable Type
QABLE
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-110
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
Select Sequence
selseq
Description
Specifies the trunk selection sequence. The Cisco PGW 2200 Softswitch uses
the CICs within a trunk group according to the sequence specified by the
SELSEQ value. You can provision this value to reduce the chance of glare
when the system selects a trunk.
ASC = Ascending. The system selects the available CICs in ascending order
starting from the lowest CIC number (for example, 1, 2, 3 ...).
CASC = Cyclic ascending. The system selects the next available CIC in
ascending order based on the most recently selected CIC. For example, if the
most recently selected CIC is CIC 5, the system selects CIC 6, even if CIC 1
is available.
CDESC = Cyclic descending. Similar to CASC, but in descending order
based on the most recently selected CIC. For example, if the last selected CIC
is number 18, the system selects CIC 17, even if CIC 31 is available.
DESC = Descending. Similar to ASC, but in descending order starting from
the highest CIC number (for example, 31, 30, 29 ...).
EASC = Even ascending, then odd ascending. The system selects the first
available even CIC in ascending order (for example, 2, 4, 6 ...). If no even CIC
is available in the trunk group, the system selects the first available odd CIC
in ascending order (for example, 1, 3, 5 ...).
EDECS = Even descending, then odd descending. Similar to EASC, but in
descending order. The system selects the first available even CIC in
descending order (for example, 30, 28, 26 ...). If no even CIC is available in
the trunk group, the system selects the first available odd CIC in descending
order (for example, 31, 29, 27 ...).
ITU2 = ITU method 2. The system selects the trunk according to the
procedure in ITU-T Recommendation Q.764, paragraph 2.9.1.3 Method 2.
continued ....
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-111
Chapter 3
Table 3-16
MML Parameter
Name
Description
selseq
... continued:
LIDL = Least idle (default). The system selects the least idle (most recently
used) CIC.
MIDL = Most idle. The system selects the most idle (least recently used) CIC.
OASC = Odd ascending, then even ascending. The system selects the first
available odd CIC in ascending order (for example, 1, 3, 5 ...). If no odd CIC
is available in the trunk group, the system selects the first available even CIC
in ascending order (for example, 2, 4, 6...).
ODESC = Odd descending, then even descending. Similar to OASC, but in
descending order. The system selects the first available odd CIC in
descending order (for example, 31, 29, 27 ...). If no odd CIC is available in
the trunk group, the system selects the first available even CIC in descending
order (for example, 30, 28, 26 ...).
RDM = Random. The system selects a CIC at random.
Caution
VSF Priority
VSF
Originating Location
Label
OrigLabel
This property defines the originating label for the trunk group.
Terminating Location
Label
TermLabel
This property inhibit the terminating label for the trunk group
Default
Default
This parameter dictates whether the trunk group is the default IP incoming
trunk group of the SIP/EISUP path. The value 1 means this trunk group is the
default IP incoming trunk of the SIP/EISUP path.
Profile
Profile
This property indicates the trunk group profile for the trunk group.
Reattempts
Reattempts
Queuing
Queuing
Routing Property
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-112
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
Description
Cutthrough
ResIncoming
Perc
ResIncPerc
BearerCap
BearerCap
Name
Defines the bearer capability of a trunk group in the route to which the
Cisco PGW 2200 Softswitch can preferentially route calls with a specific
bearer capability.
Ring No Answer
RingNoAnswer
Glare
GLARE
Glare control. Glare is a collision that occurs when two network nodes
simultaneously attempt to reserve the same channel. Values are: 1 (always),
2 (even/odd), or 3 (never) (default).
COT percentage
CotPercentage
Determines the percentage of calls on the trunk upon which a continuity test
is performed. Value range: 0 through 100.
Satellite
SatelliteInd
Satellite indicator. Indicates if the trunk is going over a satellite. Values are 0
(no) (default) or 1 (yes).
Npa
Numbering Plan Area. Indicates the NPA code associated with the incoming
trunk group. Value range: 0 (none) (default), or a 3-digit code from 200
through 999.
Customer group ID
CustGrpId
Customer group ID. The ID of the customer associated with this trunk group.
Value range: 0 (if not defined) or any 4-character alphanumeric string.
Compression Type
CompressionType
Compression type. Identifies the G.711 compression type used on the trunk.
After the fax or modem tone has been detected by the Cisco MGW, select the
proper compression type. Values are: 0 (none), 1 (mu-law) (default), 2
(A-law), or 3 (clear channel).
Echo Canceller
Required
EchoCanRequired
Prop-1 tab
The Cisco PGW 2200 Softswitch follows the following procedure for an SS7
terminated call after the call is answered. If the Cisco PGW 2200 Softswitch
receives a call-in-progress message (CPG) with backward call indicators
(BCI) from the SS7 side, it takes the specified action.
If EchoCanRequired=1:
If the echo device indicator = 0 in BCI, send MDCX with e: on
If the echo device indicator = 1 in BCI, send MDCX with e: off
If EchoCanRequired=0 (default):
Do not send an MDCX for echo control
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-113
Chapter 3
Table 3-16
MML Parameter
Name
External COT
ExtCOT
DetectFaxModemT Detect Fax modem tone. Indicates if Fax modem tone is to be detected. Used
one
for MGCP connection protocol. Values are: 0 (no tone detection notification)
or 1 (request fax or modem tone detection from the Cisco MGW.
WaitOrigSDPTimer Wait for originating SDP timer. On H.323 originated calls, the MGC transits
the answer message and starts this timer when the originating SDP
information has not been received. Value range: 0 to 50 (in seconds).
WaitTermSDPTime Wait for terminating SDP timer. On H.323 terminated calls, the MGC transits
r
the answer message and starts this timer when the terminating SDP
information has not been received. Value range: 0 to 50 (in seconds).
SendAddressnCgpn Send address in the calling party number. Determines if the CLI digits are
sent in the outgoing calling party number parameter. Value is 0 (False) for do
not include address digits in calling party number parameter, or 1 (True)
(default) for including address digits in calling party number parameter.
Description
External continuity test. Indicates the type of COT handling for the specified
destination. Values are: 0-no COT, loop (default), or transponder.
Prop-2
Maximum ACL
MaxACL
ACL Duration
ACLDuration-
ACCRespCntlInhib Automatic congestion control response inhibit. Enables or disables the ACC
it
control procedures based on the ACL value received by MGC from a linked
switch. Values are: 0 (default) or 1.
ISUP Transparency
Disabled
IsupTransparencyD ISUP transparency disable function. Permits disabling the ISUP transparency
isabled
feature for a specified trunk group. Values are: 0 (ISUP transparency
enabled), or 1 (ISUP transparency disabled) (default).
AOC Enabled
AOCEnabled
Carrier Screening
CarrierScreening
Originating Carrier ID
OrigCarrierId
NotifySetupCompl
ete
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-114
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
Package Type
PackageType
Description
Package type. Determines MDL MGCP message handling according to the
CAS trunk group package. Value range: any alphabetical string.
Default: BL
ACC Response
Category
ACCRespCatName
Default Carrier ID
NatNet ID Plan
DefaultCARIDNat
NetIdPlan
Default Originating
Line Information
DefaultOLI
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-115
Chapter 3
Table 3-16
MML Parameter
Name
CgpnPresRes
CgpnPresRes
Description
Calling party number restricted Determines if the incoming called number
presentation indication is to be overridden. Value range: 0 (False) (default)
for leave as-is, or 1 (True) for set to presentation restricted.
Prop-3 tab
Default Directory
Number
DefaultDN
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-116
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
Default Directory
Number NOA
Default
DNNOA
Description
Default directory number NOA. Values are
0 (NOTUSED (default))
1 (NOA_NONE)
2 (NOA_UNKNOWN)
3 (NOA_SUBSCRIBER)
4 (NOA_NATIONAL)
5 (NOA_INTERNATIONAL)
6 (NOA_NETWORK)
7 (NOA_MERIDIAN)
8 (NOA_ABBR)
9 (NOA_UNIQUE_3DIG_NAT_NUM), 10 (NOA_ANI)
11 (NOA_NO_ANI_RECD)
12 (NOA_NON_UNIQUE_SUBSCRIBER)
13 (NOA_NON_UNIQUE_NATIONAL)
14 (NOA_NON_UNIQUE_INTERNATIONAL)
15 (NOA_OPRREQ_TREATED)
16 (NOA_OPRREQ_SUBSCRIBER)
17 (NOA_OPRREQ_NATIONAL)
18 (NOA_OPRREQ_INTERNATIONAL)
19 (NOA_OPRREQ_NO_NUM)
20 (NOA_CARRIER_NO_NUM)
21 (NOA_950_CALL)
22 (NOA_TEST_LINE_CODE)
23 (NOA_INT_INBOUND)
24 (NOA_NAT_OR_INTL_CARRIER_ACC_CODE_INC)
25 (NOA_CELL_GLOBAL_ID_GSM)
26 (NOA_CELL_GLOBAL_ID_NMT_900)
27 (NOA_CELL_GLOBAL_ID_NMT_450)
28 (NOA_CELL_GLOBAL_ID_AUTONET)
29 (NOA_PORTED_NUMBER)
30 (NOA_PISN_SPECIFIC_NUMBER)
31 (NOA_UK_SPECIFIC_ADDRESS)
32 (NOA_SPARE), 33 (NOA_MCI_VNET)
34 (NOA_INTERNATIONAL_OPR_TO_OPR_OUTSIDE_WZI)
35 (NOA_INTERNATIONAL_OPR_TO_OPR_INSIDE_WZI)
36 (NOA_DIRECT_TERMINATION_OVERFLOW)
37 (NOA_ISN_EXTENDED_INTERNATIONAL_TERMINATION)
38 (NOA_TRANSFER_ISN_TO_ISN)
39 (NOA_CREDIT_CARD)
40 (NOA_DEFINED_IN_SSUTR)
41 (NOA_DEFINED_IN_SSUTR2)
42 (RESERVED)
43 (NOA_DISCARDED)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-117
Chapter 3
Table 3-16
MML Parameter
Name
Description
Default Directory
Number NPI
DefaultDNNPI
Default Directory
Presentation Indicator
DefaultDNPres
Default Directory
Screening Indicator
DefaultDNSI
1 (PRES_NO_INDICATION),
2 (PRES_ALLOWED),
3 (PRES_RESTRICT), or
4 (PRES_UNAVAIL)
Default directory screening indicator (SI). Values are: 0 (NOTUSED)
(default),
200 (SI_NONE),
201 (SI_USER_PROVIDED_NOT_VERIFIED),
202 (SI_USER_PROVIDED_VERIFIED_PASSED),
203 (SI_USER_PROVIDED_VERIFIED_FAILED), or
204 (SI_NETWORK_PROVIDED)
Default Carrier
Identifier Network
Identifier
DefaultCARIDNetI Default carrier identifier network identifier. Values are: a 2 to 4 digit string,
D
or NULL (default).
Default Carrier
DefaultCARIDNet
Identifier Network Type Type
Gateway RB Tone
Support
GatewayRBToneSu Gateway ring back tone support. Indicates the support or non-support of
pport
ringback tone application within the gateway that hosts the trunk group and
the connection method that is applied. Values are: 0 (No local tone
application support) (default),
1 (Local tone application support using MDCX connection method), or
2 (Local tone application support using RQNT connection method)
Note
WaitAnswerTimer
Wait answer timer. This timer is started when the MGC instructs the Media
Gateway to apply ring back tone upon the receipt of Alerting. This timer is
stopped when the MGC receives the Answer message. Values are: 0 through
300 (in seconds). Default: 65.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-118
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
Charge Origin
ChargeOrigin
AInternationalPrefix
AInternationalPrefi A-number international prefix. Determines the prefix of the outgoing calling
x
number when NOA is set to International. Value range: NULL (default) or a
numeric string.
ANationalPrefix
ANationalPrefix
BInternationalPrefix
BInternationalPrefi
x
BNationalPrefix
BNationalPrefix
B-number national prefix. Determines the prefix for outgoing called numbers
when Nature of Address (NOA) is set to National. Value range: NULL
(default) or digit string.
ADigitCCPrefix
ADigitCCPrefix
BDigitCCPrefix
BDigitCCPrefix
BDigConnecteditCCrm
BDigitCCrm
Country code remove. Provides a country code digit string to which the called
party Number leading digits can be compared, and if matched have those
digits removed from the front of the number. This modification is made
before sending the call forward. Values are: NULL (default) or null, or a
maximum 5-digit string.
CCOrigin
CCOrigin
Country code origin. Provides against the origin trunk group of a call the
country code digits, which if needed can be prefixed on a number before
sending the call forward. Only required when the property domain is SigPath
or LinkSet. Values: NULL (default) or a maximum 5 digit string.
Ta1TimePeriod
Ta1TimePeriod
Ta1 time period. Indicates the value for the time period Ta1, in seconds. Value
range: 1 through 180. Default: 20.
Ta2TimePeriod
Ta2TimePeriod
Ta2 time period. Indicates the value for the time period Ta2, in seconds. Value
range: 1 through 180. Default: 30.
Ta3TimePeriod
Ta3TimePeriod
Ta3 time period. Indicates the value for the time period Ta3, in seconds. Value
range: 1 through 180. Default: 3.
ExpiryWarnToneType
ExpiryWarnToneTy String defining the tone to be applied to warn that the assigned call duration
pe
is almost expired. Value range: Any valid MGCP event name. Default:
NULL.
ExpiryWarnToneDurati
on
ExpiryWarnToneD
ur
Description
Charge origin. The charge origin value may be defaulted (0) when the
charging tariff rates are not origin dependent. The craftperson decides what
value of charge origin is to be used, up to a 4-digit integer value. Value range:
0 (default) through 9999.
Prop-4
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-119
Chapter 3
Table 3-16
MML Parameter
Name
CLISelect
CLISelect
GWDefaultCodecString GWDefault
CodecString
Description
Calling line identification. Determines whether or not the additional calling
party number is presented in the incoming IAM. Values are: GENERICNUM
(the additional calling party number is presented in the incoming IAM as
generic number and the additional calling party number is used as the CLI
and is passed to the access network) or CLI (additional calling party number
is not presented in the incoming IAM). Default: CLI.
Gateway default codec string. Enables the IOCC-MGCP to send the ordered
series of codec choices separated by semicolons. Refer to your gateway
documentation for a list of supported codec names. The following values
represent some of the more common codec names.
Values: NULL, G.711a, G.711u, G.729, G.729a, and G.729b
Default: NULL
AllowH323Hairpin
AllowH323Hairpin
H323AdjunctLink
FAXSupport
FAX support. Indicates if T.38 FAX calls are supported on the trunk group.
This property must be enabled on the incoming and outgoing trunk groups for
T.38 fax calls to be successfully routed. Valid values: 0 (no FAX support) or
1 (T.38 FAX support). Default: 0.
SubscribeNotifySu
pport
Prop-5 tab
Subscribe Notify
Support
Default: 0
This property is added in software Release 9.4(1).
Unsolicited Notify
Method
UnsolicitedNotify
Method
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-120
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
Description
MinEventSubscribe Minimum event subscribe duration. Defines the minimum duration (in
Duration
milliseconds) for which a telephony event can be subscribed. Value range: 40
through 3600.
Default: 40
This property is added in software Release 9.4(1).
Max Subscription
Duration
MaxSubscriptionD
uration
PopulateSDPInfo
InCDR
PopulateSDP
InfoInCDR
OD32Digit
Support
OD32Digit
Support
OD 32 Digit Support. Allows 32 digit and overdecadic digit support for the
ANSI, Q.761, and Q.767 protocol variants for the ANSI, SS7-ITU,
SS7-China, SS7-Japan, and SS7-UK protocol families. Values are 0
(disabled) and 1 (enabled).
This property is added in software Release 9.4(1).
Anumnormalise
Anumnormalise
Redirecting number (or all redirecting numbers if there is more than one)
The actions apply only if the NOA of the number is set to UNKNOWN or
SUBSCRIBER. If if is, check the initial digits of the number to see if they are
0 or 00. The following applies:
If the leading digit is 0, remove the 0 and set the NOA to NATIONAL.
If the leading digits are 00, remove both 0s and set the NOA to
INTERNATIONAL.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-121
Chapter 3
Table 3-16
MML Parameter
Name
Bnumnormalise
Bnumnormalise
Description
B Number Normalise. Bnumnormalise indicates that called party number
(B-number) normalization is appropriate based on the NOA value and the
leading digits of the B-number. Leading digits 0 or 00 are the only accepted
digits. Valid values: 0 (disabled) or 1 (enabled).
Default: 0
The actions apply only if the NOA of the number is set to UNKNOWN or
SUBSCRIBER. If it is, check the initial digits of the number to see if they are
0 or 00. The following applies:
If the leading digit is 0, remove the 0 and set the NOA to NATIONAL.
If the leading digits are 00, remove both 0s and set the NOA to
INTERNATIONAL.
GtdCapType
Prop
GTD Cap Type Properties. The Cisco PGW 2200 Softswitch uses this
parameter as a pointer to the subset of GTD parameters that the user desires
to support. Values are t0 (no GTD support) (default) or any GTD parameter
string from 1 to 20 characters.
GtdMsgFmt
GtdMsgFmt
GTD Message Format. Indicates the GTD message format mode. The format
can be only compact mode. Compact mode is the short format and the field
names are not passed in the GTD parameter string. Valid value: c (compact)
or v (verbose). Default: c
IsupTransEarly
BackwardDisabled
IsupTransEarlyBac
kwardDisabled
sipMimeBodySupport
sipMimeBodySupp
ort
Enable IP Screening
EnableIPScreening
Enables the incoming trunk group to select a dial plan based on the IP
address, source ID, and CLI prefix tables. Valid values: 0 (no dial plan
lookup) or 1 (require dial plan lookup).
Default Value: 0
This property is added in software Release 9.4(1).
SIP IP Source
SipIPSource
Indicates for the Cisco PGW 2200 Softswitch to use the IP packet source
address or IP address from Session Description Protocol (SDP) in the
INVITE message to make the dial plan selection for SIP calls. Valid values:
0 (use the IP packet source address) or 1 (use the IP address from SDP).
Default Value: 0
This property is added in software Release 9.4(1).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-122
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
Description
Prop-6 tab
Default PN
DefaultPN
Enables the incoming trunk group to have a default PN if the incoming call
does not have one; overdecadic digits are supported. Valid values:
overdecadic digit string of 1 to 20 characters. Default Value: NULL
This property is added in software Release 9.4(1).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-123
Chapter 3
Table 3-16
MML Parameter
Name
Default Presentation
Number NOA
DefaultPN
NOA
Description
Enables the default Presentation Number NOA value. Valid values: 0 through
43. Values are
0 (NOT USED) default
1 (NOA_NONE)
2 (NOA_UNKNOWN)
3 (NOA_SUBSCRIBER)
4 (NOA_NATIONAL)
5 (NOA_INTERNATIONAL)
6 (NOA_NETWORK)
7 (NOA_MERIDIAN)
8 (NOA_ABBR)
9 (NOA_UNIQUE_3DIG_NAT_NUM)
10 (NOA_ANI)
11 (NOA_NO_ANI_RECD)
12 (NOA_NON_UNIQUE_SUBSCRIBER)
13 (NOA_NON_UNIQUE_NATIONAL)
14 (NOA_NON_UNIQUE_INTERNATIONAL)
15 (NOA_OPRREQ_TREATED)
16 (NOA_OPRREQ_SUBSCRIBER)
17 (NOA_OPRREQ_NATIONAL)
18 (NOA_OPRREQ_INTERNATIONAL)
19 (NOA_OPRREQ_NO_NUM)
20 (NOA_CARRIER_NO_NUM)
21 (NOA_950_CALL)
22 (NOA_TEST_LINE_CODE)
23 (NOA_INT_INBOUND)
24 (NOA_NAT_OR_INTL_CARRIER_ACC_CODE_INC)
25 (NOA_CELL_GLOBAL_ID_GSM)
26 (NOA_CELL_GLOBAL_ID_NMT_900)
27 (NOA_CELL_GLOBAL_ID_NMT_450)
28 (NOA_CELL_GLOBAL_ID_AUTONET)
29 (NOA_PORTED_NUMBER)
30 (NOA_PISN_SPECIFIC_NUMBER)
31 (NOA_UK_SPECIFIC_ADDRESS)
32 (NOA_SPARE)
33 (NOA_MCI_VNET)
34 (NOA_INTERNATIONAL_OPR_TO_OPR_OUTSIDE_WZI)
35 (NOA_INTERNATIONAL_OPR_TO_OPR_INSIDE_WZI)
36 (NOA_DIRECT_TERMINATION_OVERFLOW)
37 (NOA_ISN_EXTENDED_INTERNATIONAL_TERMINATION)
38 (NOA_TRANSFER_ISN_TO_ISN)
39 (NOA_CREDIT_CARD)
40 (NOA_DEFINED_IN_SSUTR)
41 (NOA_DEFINED_IN_SSUTR2)
42 (RESERVED)
43 (NOA_DISCARDED)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-124
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
DefaultPNNPI
Description
Displays the default Presentation Number NPI value. Valid values: 0 through
10.
0 (NOTUSED)
1 (NPI_NONE)
2 (NPI_E164)
3 (NPI_DATA)
4 (NPI_TELEX)
5 (NPI_PNP)
6 (NPI_NATIONAL)
7 (NPI_TELEPHONY)
8 (NPI_MARITIME_MOBILE)
9 (NPI_LAND_MOBILE)
10 (NPI_ISDN_MOBILE)
Default value: 0.
This property is added in software Release 9.4(1).
Default Presentation
Number Indicator
DefaultPNPres
CallForwardRerouteDis CallForwardRerout Disables Call Forwarding rerouting for all calls on the
abled
e
Cisco PGW 2200 Softswitch. Valid values: 0 (reroute enabled) or 1 (reroute
Disabled
disabled).
Default value: 0.
This property is added in software Release 9.4(1).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-125
Chapter 3
Table 3-16
MML Parameter
Name
Description
CustomerVPNOnNetTb CustomerVPNOnN Allows assignment of a VPN on-net profile table index to a particular trunk
lNum
etTblNum
group. Value range: 1 through 8.
1Completely transparent operation is required for the call to complete.
2The Cisco PGW 2200 Softswitch can use feature transparency preferred
by a nontransparent destination if necessary to complete the call.
3The Cisco PGW 2200 Softswitch can use feature transparency preferred
by a nontransparent destination if necessary to complete the call.
4The Cisco PGW 2200 Softswitch can use feature transparency preferred
by a nontransparent destination if necessary to complete the call.
5The Cisco PGW 2200 Softswitch removed the attempted feature from the
onward-routed call and informs the indicator of the change.
6The Cisco PGW 2200 Softswitch releases a feature call.
7The Cisco PGW 2200 Softswitch releases a feature call.
8The Cisco PGW 2200 Softswitch removes the feature string and
continues.
Default value: 5.
This property is added in software Release 9.4(1). The range changed to 18
and the default changed to 5 in software Release 9.6(1).
CustomerVPNid
CustomerVPN
id
CustomerVPNOffNetT
blNum
CustomerVPNOffN Allows assignment of a VPN off-net profile table index to a particular trunk
et
group. Value range: 1 through 8.
TblNum
1Completely transparent operation is required for the call to complete.
2The Cisco PGW 2200 Softswitch can use feature transparency preferred
by a nontransparent destination if necessary to complete the call.
3The Cisco PGW 2200 Softswitch can use feature transparency preferred
by a nontransparent destination if necessary to complete the call.
4The Cisco PGW 2200 Softswitch can use feature transparency preferred
by a nontransparent destination if necessary to complete the call.
5The Cisco PGW 2200 Softswitch removed the attempted feature from the
onward-routed call and informs the indicator of the change.
6The Cisco PGW 2200 Softswitch releases a feature call.
7The Cisco PGW 2200 Softswitch releases a feature call.
8The Cisco PGW 2200 Softswitch removes the feature string and
continues.
Default value: 0.
This property is added in software Release 9.4(1). The range changed to 18
and the default changed to 5 in software Release 9.6(1)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-126
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
Description
Feature
Transparency
Disabled
Feature
Transparency
Disabled
SdpXmitToH323
Trigger
SdpXmitTo
H323Trigger
SDP transmit to H.323 trigger. Indicates the point in a call when the
Cisco PGW 2200 Softswitch sends the SDP from the terminating call leg to
the H.323 Signaling Interface (HSI). Value range: 0 through 3.
0 = terminating seizure
1 = Address complete
2 = Alerting or inband information available
3 = Answer
This property is added in software Release 9.4(1).
GWDefaultATM
Profile
GWDefault
ATMProfile
Defines an initial list of profiles that the Cisco PGW 2200 Softswitch uses to
control ATM profile negotiation between two MGWs.
When setting up an ATM voice connection, the originating and terminating
MGWs communicate via the Cisco PGW 2200 Softswitch. The MGWs must
negotiate to establish what ATM profiles to use for the connection.
When you set the GWDefaultATMProfile properties, the
Cisco PGW 2200 Softswitch sends the list of supported profiles to the MGW
via MGCP. The MGW then combines these values with its list of supported
profiles to produce a list of profiles supported by both the MGW and the
Cisco PGW 2200 Softswitch. The MGW sends the profile list to the
terminating MGW via SDP. Thus, the GWDefaultATMProfile values control
the profiles that the MGWs can negotiate for an ATM voice connection.
Valid values:
NULL
PlayAnnouncement Enables, on a per trunk group basis, the playing of an early announcement.
This property can either contain an integer announcement identity, or, if it is
set to 0 (default), the announcement function is considered disabled at the
trunk group level. Valid values: any integer value.
Default value: 0.
This property is added in software Release 9.5(2).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-127
Chapter 3
Table 3-16
MML Parameter
Name
Atm
Connection
Type
Description
Populates the connection type parameter (ct:) in local connection option
parameters. This property is read for both originating and terminating legs of
all ATM-switched calls. Valid values: 1 (AAL1), 2 (AAL1_SDT), 3
(AAL1_UDT), 4 (AAL2), 5 (AAL 3/4), or 6 (AAL5).
Default value: 4 (AAL2)
This property is added in software Release 9.5(2).
BTechPrefix
BTechPrefix
Provides a digit string that the Cisco PGW 2200 Softswitch uses as a Tech
Prefix to the B-number when sending the call forward. Valid values: any
integer.string from one digit (minimum) through 16 (maximum) digits. The
Tech Prefix uses overdecadic digits B and C and maps them to * and #
respectively. The Tech Prefix and a separator are appended to the beginning
of the B-number.
This property is added in software Release 9.5(2).
Prop-7 tab
Loop Avoidance
Support
LoopAvoidance
Support
Loop Avoidance
Counter
LoopAvoidance
Counter
MwiStringOFF
Ensure that the digit string provisioned is the same MWI string
provisioned in Cisco CallManager.
MwiStringON
Ensure that the digit string provisioned is the same MWI string
provisioned in Cisco CallManager.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-128
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
Description
InhibitIncomingCalling InhibitIncomingCal Enables or disables the inhibiting of the incoming calling name display in
NameDisplay
lingNameDisplay
DPNSS and EISUP (HSI) protocols. Valid values: 0 (enable) or 1 (disable).
Default value: 0.
This property is added in software Release 9.5(2).
InhibitOutgoingCalling InhibitOutgoingCal Enables or disables the inhibiting of the outgoing calling name display in
NameDisplay
lingNameDisplay
DPNSS and EISUP (HSI) protocols. Valid values: 0 (enable) or 1 (disable).
Default value: 0.
This property is added in software Release 9.5(2).
InhibitIncomingConnec InhibitIncomingCo
tedNameDisplay
nnectedNameDispl
ay
InhibitIncomingConnec InhibitIncomingCo Enables or disables the support of incoming connected number display in
tedNumberDisplay
nnectedNumberDis DPNSS and EISUP (HSI) protocols. Valid values: 1 (inhibit incoming
play
connected number display) or 0 (enable incoming connected number
display).
Default value: 0
This property is added in software Release 9.5(2).
AOC Default Tariff Id
AOCDefaultTariffI
d
AOCInvokeType
MidCallCPInterval
MidCallCPInterval
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-129
Chapter 3
Table 3-16
MML Parameter
Name
CliSelection
ForCodeOf
Practice3
Description
Provisions, on a per trunk group basis, the level of CLI selection that the
Cisco PGW 2200 Softswitch uses when sending the calling line identities
(such as Calling Party Number or Generic Number parameter) to the
succeeding exchange. Valid range: 0 through 2.
Valid values:
0No specific CLI selection (default).
1Single CLI selection, which sends only the CLI.
2Dual CLI selection, which sends the CLI; or the CLI and the PN.
Default value: 0
This property is added in software Release 9.5(2).
InhibitOutgoingConnec InhibitOutgoingCo
tedNameDisplay
nnectedNameDispl
ay
InhibitOutgoingConnec InhibitOutgoingCo Enables or disables inhibit outgoing connected number display in DPNSS
tedNumberDisplay
nnectedNumberDis and EISUP (HSI) protocols. Valid values: 0 (enable) or 1 (disable).
play
Default value: 0
This property is added in software Release 9.5(2).
H323 Destination
H323Destination
Identifies the primary and alternative IP Address and Port of the H323
destination.
Valid Values:
The primary and the alternative IP address and port of the H323
destination, in the format xxx.xxx.xxx.xxx[:port][xxx.xxx.xxx.xxx:port]
Default value:
NULL
This value indicates the Non-RAS feature is inactive on this trunk group.
ADigitCCrm
Prop-8 tab
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-130
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
OwnRouting
Number
Description
Defines the routing or network number of the PGW in a PBX network that
requires Route Optimization or Path Replacement capabilities. The presence
or absence of this property indicates if this service is enabled or disabled for
a signalling path.
Valid range: Alphanumeric string up to 32 characters.
Default: NULL
This property was added in software Release 9.6(1).
QSIGTunnelVariant Controls the QSIG tunnel capability across outbound EISUP (HSI) interfaces
and specifies which protocol variant is used.
Valid Values:
Default Value: 0
Disable QSIG Release
Method
DisableQSIGRelea
seMethod
Default Value: 0
DPNSS RO
DpnssRORoutingN For DPNSS-QSIG PR ROO interworking, the DPNSS RO routing number
RoutingNumber Length umberLength
and call reference are concatenated and in QSIG they are separate fields. An
indication of where the divide point is between the fields is an optional
parameter in the DPNSS specification. It is therefore necessary to provide a
configurable definition of how to split these two fields.
Valid values: 210
Default value: 4
Enable CCBS Path
Reservation
EnableCCBSpathR
eservation
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-131
Chapter 3
Table 3-16
MML Parameter
Name
TrunkGroupTag
Label
TrunkGroup
TagLabel
Description
This property gives the name of the trunk group from which a call comes.
Value: A string of 163 characters.
Default: Null
Dynamically Reconfigurable: Yes
This property does not support some special characters like #, >, and
white space. MML does not allow you to use these characters for the
TrunkGroupTagLabel.
Note
TrunkGrpTagLabel
TransEnable
TrunkGrpTagLabel
TransEnable
Indicates how the PGW handles the ingress trunk group tag label (if present)
in the outgoing SIP INVITE message. This property is dynamically
reconfigurable.
Values:
0: The PGW does not send the ingress trunk group tag label
1: The PGW sends the ingress trunk group tag label in the x-route-tag
parameter
2: The PGW sends the ingress trunk group tag label in the tsp parameter
Default: 0
Dynamically Reconfigurable: Yes
H248Gateway
ReserveValue
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-132
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
MapRNMethod
MapRNMethod
Description
Determines the mappings between the EISUP or ISUP RN and the SIP
message headers or EISUP RN.
Valid Values:
0Do not map the RN to the SIP header. Do not map the RN to the
EISUP RN parameter.
Default Value: 1
Itp Action Request
ItpActionRequest
TOverlap
TOverlap
Set to 1 to enable overlap signaling for call termination to this traffic path.
Values are 0 or 1.
Default: 0
TMinDigits
TMinDigits
TMaxDigits
TMaxDigits
Prop-9 tab
OOverlap
OOverlap
Set to 1 to enable overlap signaling for call origination from this traffic path.
Value range: 0 through system maximum.
Default: 0
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-133
Chapter 3
Table 3-16
MML Parameter
Name
OMinDigits
OMinDigits
Description
Specifies minimum number of digits to receive for overlap digit processing
for call origination from this traffic path. Value range: 0 through system
maximum.
Default: 0
OMaxDigits
OMaxDigits
OverlapDigitTime
OverlapDigitTime
Overlap interdigit timer. The time to wait for the rest of the digits.
Value range: 0 through 60, in seconds.
Default: 6
DTMF Capability
DtmfCap
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-134
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
Description
MapCLItoSipHead
er
Determines the mappings from the ISUP calling party number to the outgoing
SIP message.
Valid Values:
0The calling party number is put in the outgoing SIP From header if
number presentation is allowed. If the calling party number presentation
is restricted, then the SIP outgoing From header is also controlled by the
cgpnInclude property.
anonymous setting by not passing the CLI to the SIP end point, the
From header has URI as Anonymous <sip:CGPN@PGW_HOST>
1The calling party number is mapped to the remote party ID, with
screen and privacy values. If an additional calling party number is present
in the generic number, it is mapped to the SIP From header.
Note
Default Value: 0
Note
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-135
Chapter 3
Table 3-16
MML Parameter
Name
InhibitSipFrom
Mapping
InhibitSipFrom
Mapping
Description
Determines the mapping from the incoming SIP message to the ISUP CLI.
If the remote party ID or P-Asserted-ID header is present and the
InhibitSipFromMapping property = 1, then disable mapping the SIP From
header to the generic number. If the remote party ID or P-Asserted-ID header
is not present and the InhibitSipFromMapping property = 1, then disable
mapping the SIP From header to the calling party number.
Valid Values:
Note
Default Value: 0
ReferRedirecting
NOA
Refer
Redirecting
NOA
NOA value of redirection number in ITU SS7 REL message for blind transfer
by SIP REFER. Use internal NOA value.
Value range:
1NOA_NONE
2NOA_UNKNOWN
3NOA_SUBSCRIBER
4NOA_NATIONAL
5NOA_INTERNATIONAL
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-136
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
Description
ReferRedirecting
Ind
Refer
RedirectingInd
SipDtmfContentType
SipDtmfContentTy
pe
This property determines the Content-Type header and the SDP content of
INFO requests PGW sends out.
Valid values:
Default value: 0
RejectOfferForResourc
ePending
RejectOfferForRes
ourcePending
Specifies how the Cisco PGW 2200 Softswitch treats new offers when the
resource is temporarily unavailable.
Valid values:
Default value: 1
IsdnNSF
IsdnNSF
Default: 256.
This property is added in software release 9.7(3) S22P22.
MidCallCodecSelect
UseGtdCalledPartyNu
mber
MidCallCodecSele
ct
SIP-1 tab
MGCdomain
MGC domain name. Indicates the MGC domain name used in SIP messages.
Value range: Any valid domain name or NULL (default).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-137
Chapter 3
Table 3-16
MML Parameter
Name
MGCSipVersion
Description
MGC SIP version. The version of SIP protocol supported by the MGC. Value
range: Any valid SIP version.
Default: 2.0
Note
For MGC software earlier than Release 9.7, set this value to SIP/2.0.
LocalPort
Local port. Indicates the UDP port used by MGC to send or receive SIP
messages. Valid range: any valid port number greater than 1024. Default:
5060.
Invite Timer T1
InviteTimerT1
Invite T1 timer. Indicates the T1 timer (in milliseconds) for the INVITE message,
as specified for SIP. Value range: any value greater than 0. Default: 1000
Gen Timer T1
GenTimerT1
Generic timer T1. The T1 timer value (in milliseconds) for SIP messages
other than INVITE. Value range: any value greater than 0. Default: 500.
Gen Timer T2
GenTimerT2
Generic timer T2. The T2 timer value (in milliseconds) for SIP messages
other than INVITE. Value range: any value greater than 0. Default: 4000.
Maximum Redirection
Count
MaxRedirectCnt
Support 183
Support183
Support 183. Indicates if the MGC supports 183 response code. Valid values:
0 (not supported), 3 (supported) (default), or 4 (always send).
From Field
FromField
From field. Displays the name used in the SIP From field when the calling
party number is marked private. Value range: any alphanumeric string.
Default: anonymous.
In Session Timer
InSessionTimer
In session timer. Indicates the maximum session time (in milliseconds) allowed
for a SIP call that originated by the MGC. Maps to trunk group property
InSessionTimer. This value may require being increased to 1800000 to reduce
performance impact. Value range: any value greater than 0. Default: 1800000.
OutSessionTimer
Out session timer. The maximum session time (in milliseconds) allowed for
a SIP call terminated by the MGC. This value may require being increased to
reduce performance impact. Valid range: any value greater than 0. Default:
1800000.
Hold Timer
HoldTimer
Hold timer. Indicates the maximum time length (in milliseconds) a SIP call can
be put on hold. Value range: any value greater than 0. Default: 300000.
Expires Timer
ExpiresTimer
Expires timer. The timer value (in milliseconds) used in the Expire header of
SIP messages. Value range: any value greater than 0. Default: 60000.
SupportReliable100 Support reliable 100. Indicates if the MGC support reliable100 response
code. Values are: TRUE (default) or FALSE.
RetryAfterTimer
Retry after timer. Indicates the time (in milliseconds) the MGC waits before
successfully retrying a SIP call. Value range: any value greater than 0.
Default: 90000.
Max. Forwards
MaxForwards
SIP-2 tab
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-138
OL-1110-23
Chapter 3
Table 3-16
MML Parameter
Name
Description
MidCallServiceCus This is a 4-character, alphanumeric string that indicates which dial plan is
tID
used for mid-call service analysis. If this property value is 0000, no mid-call
service is supported. Valid range: 0000 or any 4-character alphanumeric
string.
Valid Values: 0000 or any 4-character alphanumeric string.
Default: 0000
Invite Attempts
InviteAttempts
Specifies the transmission times for SIP INVITE request. Value range: from
1 to 15. Default: 7.
Response Attempts
ResponseAttempts
Specifies the transmission times for SIP response.Value range: from 1 to 15.
Default: 11.
Retrans Method
RetransMethod
InviteWaitTimer
Specifies the timer value (in milliseconds) for SIP waiting for final response
of INVITE request.Value range: from 10000 to 500000. Default: 200000.
sipEgressRoutingC
ontrol
Adding Trunks
Use the following procedure to add trunks to a trunk group:
Step 1
Click Trunks in the left pane of the main Cisco VSPT window. A window similar to the one shown
in Figure 3-98 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-139
Chapter 3
Figure 3-98
Step 2
Trunk Window
Click Add. A window similar to the one shown in Figure 3-99 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-140
OL-1110-23
Chapter 3
Figure 3-99
Adding a Trunk
Step 3
In the Trunk Group Number drop-down menu, select the number of the trunk groups you are configuring.
Step 4
In the Media Gateway Name drop-down menu, select the gateway (external node). This step might not
be required if the gateway can be determined by trunk group signaling.
Step 5
Step 6
Step 7
Step 8
Step 9
In the Subunit Number drop-down menu, select the subunit where you want to add trunks.
Step 10
Step 11
Step 12
Step 13
Select SS7, PRI FAS, or PRI NFAS and enter the appropriate properties:
PRI FAS or PRI NFASEnter the number of trunk members and the number of the DS1 with the
D channel.
Note
Step 14
For PRI, one channel is reserved for signaling (D channel). For FAS, it is channel 24. For NFAS,
it is channel 24, but on only one DS1.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-141
Chapter 3
Step 15
Step 16
When you are done adding trunks to trunk groups, click Finish. You are asked if you want to overwrite
the trunks in the existing trunk groups, and a window similar to the one shown in Figure 3-100 displays.
Figure 3-100
Trunks Added
In the Trunk window (similar to the one shown in Figure 3-100) select from the Trunk Group Number
drop-down menu the trunk group where you want to delete trunks.
Step 2
Step 3
To select a range of trunks, click on the first trunk in the range, hold down the Shift key, and click
the last trunk in the range.
To select nonsequential trunks, hold down the Control key, and click each trunk.
When you have finished selecting trunks, click Delete to delete the selected trunks. A window similar
to the one shown in Figure 3-101.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-142
OL-1110-23
Chapter 3
Figure 3-101
Trunks Deleted
Adding a CodecString
Use the following procedure to add a CodecString:
Step 1
Click CodecString in the left pane of the main Cisco VSPT window.
Step 2
Click Add. A window similar to the one shown in Figure 3-102 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-143
Chapter 3
Figure 3-102
Adding a CodecString
Step 3
Enter a name.
Step 4
Step 5
Click Finish. A window similar to the one shown in Figure 3-103 displays.
Figure 3-103
CodecString Added
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-144
OL-1110-23
Chapter 3
Adding a BearerCap
Use the following procedure to add a BearerCap:
Step 1
Click BearerCap in the left pane of the main Cisco VSPT window.
Step 2
Click Add. A window similar to the one shown in Figure 3-104 displays.
Figure 3-104
Adding a BearerCap
Step 3
Enter a name.
Step 4
Step 5
Click Finish. A window similar to the one shown in Figure 3-105 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-145
Chapter 3
Figure 3-105
BearerCap Added
Adding an ATMProfile
Use the following procedure to add an ATMProfile:
Step 1
Click ATMProfile in the left pane of the main Cisco VSPT window.
Step 2
Click Add. A window similar to the one shown in Figure Figure 3-106 displays.
Figure 3-106
Adding an ATMProfile
Step 3
Enter a name.
Step 4
Step 5
Click OK. A window similar to the one shown in Figure Figure 3-107 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-146
OL-1110-23
Chapter 3
Figure 3-107
ATMProfile Added
Adding Routes
A route is a collection of trunk groups associated with the same set of dialed digits. Use the following
procedure to add a route and associate a trunk group with the route added:
Step 1
Click Routing > Routes in the left pane of the main Cisco VSPT window.
Step 2
Click Add. A window similar to the one shown in Figure 3-108 displays.
Figure 3-108
Adding a Route
Step 3
Step 4
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-147
Chapter 3
Step 5
Tip
Step 6
To associate the route with a previously defined trunk group, select a group in the Available box, and
click Select >>.
To select more than one trunk group, hold down the Control key while selecting each group.
When you are done adding trunk groups, click OK. A window similar to the one shown in Figure 3-109
displays with the routes added.
Figure 3-109
Click Route Lists in the left pane of the main Cisco VSPT window.
Step 2
Click Add. A window similar to the one shown in Figure 3-110 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-148
OL-1110-23
Chapter 3
Figure 3-110
Step 3
Step 4
To associate the route with a route group, select a route in the Available box.
Step 5
Tip
Step 6
To select more than one route group, hold down the Control key while selecting each group.
When you are done adding routes to the route group, click OK. A window similar to the one shown in
Figure 3-111 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-149
Chapter 3
Figure 3-111
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-150
OL-1110-23
Chapter 3
Checks that if MGC failover is specified, the failover IPs are specified
For EXTNODES where it refers to an MGX, checks PeerAddrs on IPLNK to ensure that they are
addresses on the specified MGX
Note
The number of IPFAS sessions utilizing a given port is displayed because some IPLNKs might
use different port IDs.
When D channels are defined as FAS and NFAS PRI in the trunk group or trunk section, VSPT
verifies that there are corresponding IPFASPATH signaling services.
Checks if there are any defined IPFASPATH signaling services defining a D channel but no
corresponding trunk group/trunk in the traffic information with a corresponding NFAS or FAS PRI.
Checks that signaling services defined for trunk groups exist in the configuration
For information about an integrity check of dial plan results, see the Cisco PGW 2200 Softswitch
Release 9 Dial Plan Guide (through Release 9.7).
Use the following procedure to perform an integrity check of your configuration:
Step 1
Select Tools > Integrity Check on the main Cisco VSPT menu bar. A window similar to the one shown
in Figure 3-112 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-151
Chapter 3
Figure 3-112
Step 2
Integrity Check
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-152
OL-1110-23
Chapter 3
Select Tools > Deploy from the main Cisco VSPT menu. A window similar to the one shown in
Figure 3-115 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-153
Chapter 3
Figure 3-115
Deploying a Configuration
Step 2
Step 3
To incrementally deploy a configuration component type, click Advanced. A window similar to the one
shown in Figure 3-116 displays.
Figure 3-116
Step 4
Step 5
If you want to send the configuration to the MGC but not activate it, select the radio button Send
Configuration to MGC Only.
If you want to send the configuration to the MGC and activate it, select the radio button Send and
Activate Configuration.
If you have a continuous-service configuration with two MGC hosts, select the radio button Send,
Activate and Synchronize failover. The configuration is saved on the active host and copied to the
standby host. You must restart the standby server after reconfiguration to apply changes.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-154
OL-1110-23
Chapter 3
Step 6
Step 7
Click OK. A window similar to the one shown in Figure 3-117 displays, showing the status, as the
current provisioning session is deployed.
Figure 3-117
Note
Deployment Progress
HSIActive configuration
ITPL2600Active configuration
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-155
Chapter 3
The backup and restore tool also provides the status of each activity and generates user-viewable status
logs.
Note
This tool operates in coordination with the MGC server operating system and can be used by only one
UNIX login. The login is specified during the installation process
Select Tools > Backup and Restore on the main Cisco VSPT menu bar. A window similar to the one
shown in Figure 3-118 displays:
Figure 3-118
Step 2
Click the component for which you want to schedule a backup or restore. The following example shows
a backup for the MGC. A window similar to the one shown in Figure 3-119 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-156
OL-1110-23
Chapter 3
Figure 3-119
Note
Step 3
If you want to perform a restore, a backup file must already be created and available on the MGC.
To schedule a backup or restore, click the component you want to back up or restore in the left pane of
the main backup and restore tool window, and click Add. A window similar to the one shown in
Figure 3-120 displays:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-157
Chapter 3
Figure 3-120
Note
Schedule an Activity
Step 4
Select the action you want to perform in the Activity field. Valid choices include backup and restore.
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Specify whether or not to use verbose log mode. Verbose mode records all commands issued by the Cisco
VSPT and any system responses.
Step 11
Step 12
Monthly
Daily
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-158
OL-1110-23
Chapter 3
Hourly
Weekly
Now
Later
Step 13
Step 14
Click OK. The backup activity is scheduled, and a window similar to the one shown in Figure 3-121
displays.
Figure 3-121
After the backup is complete, the status of the activity becomes available immediately, and the backup
file with the name specified is available for use with the Cisco VSPT to perform a restore.
Success or failure
If a user has specified verbose log mode, the status log also displays the sequence of commands issued
by the Cisco VSPT and any system responses.
Use the following procedure to check the status of a backup or restore activity:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-159
Chapter 3
Step 1
Click the device that has been backed up or restored in the left pane of the backup and restore tool
window, and click the Status tab in the right pane.
Step 2
Step 3
Select the appropriate button for the action you want to perform. Choices are:
Show status
Acknowledge
Clear
Use the Cisco VSPT to create, copy, modify, and deploy a configuration for the BAMS server. The Cisco
BAMS provisioning session can exist as a standalone provisioning application using MML.
The VSPT performs the following tasks when you are configuring the Cisco BAMS:
Generates an MML batch file either from scratch or based on a preexisting configuration
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-160
OL-1110-23
Chapter 3
Imports the TrunkGroup file from the MGC host to keep trunk group information synchronized
Performs an integrity check to ensure that the current configuration check is valid
General provisioning
Defines country codes
Defines map types
Defines tollfree prefixes
Zone provisioning
Creates zones in the Zone_Information for separate rating zones
Assigns NPA-NXX prefixes to appropriate zones
For each From/To Zone pair, define the appropriate rating type for that zone pair
Defines rating exceptions in the Rate-Exc table
groups, routing files, or dial plans. Map SigpathID/Bearer Channel Numbers to Trunk Group
Number/Member Numbers.
Other
ALM-PARMS
NODE-PARMS
POLL
SKIPCDB
SKIPCDE
P01FILTER
SWITCHINFO
BIN1110
System
MSC-MASK
MSC-THRES
SYS-ALM-PARMS
For information on provisioning these tags, see the Cisco Media Gateway Controller Software Release
9 Billing Interface Guide. For more details on which tags are fully supported, see the documentation for
your release of Cisco BAMS.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-161
Chapter 3
Step 2
Select File > Open on the menu bar to open an existing configuration, and go to Step 4. If you want to
start a new configuration, go to the next step. For more information, see the Cisco Voice Services
Provisioning Tool Users Guide for the software release you are using.
Step 3
Select Tools > BAMS Config on the menu bar. A window similar to the one shown in Figure 3-123
displays.
Figure 3-123
Step 4
Step 5
Enter a name for the provisioning session you are creating, and click OK. A window similar to the one
shown in Figure 3-124 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-162
OL-1110-23
Chapter 3
Figure 3-124
Step 6
If you want to import an existing configuration from a Cisco BAMS, select the Import from BAMS
radio button. Enter the host name, login, password, and the configuration you want to import. If you do
not know the name of the configuration, click Select, select the configuration you want, and click OK.
If you want to manually configure the Cisco BAMS, select the Perform manual configuration radio
button, and click OK. A window similar to the one shown in Figure 3-125 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-163
Chapter 3
Figure 3-125
Step 7
Step 8
Step 9
Optionally, enter the network addresses (IP Addr: 1 and IP Addr: 2) in dotted notation; for example,
172.16.145.3.
Step 10
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-164
OL-1110-23
Chapter 3
Note
For more information on Cisco BAMS parameter definitions and values, see the Cisco Billing and
Measurements Server Users Guide for the Cisco BAMS release you are using.
Click the icon next to General in the left pane of the BAMS Configuration window to expand the
hierarchical tree.
Step 2
Click Country Codes. A window similar to the one shown in Figure 3-126 displays.
Figure 3-126
Step 3
Click Add. A window similar to the one shown in Figure 3-127 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-165
Chapter 3
Figure 3-127
Step 4
Enter the country code and country name, and click OK. A window similar to the one shown in
Figure 3-128 displays.
Figure 3-128
Step 5
Click Maptypes. A window similar to the one shown in Figure 3-129 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-166
OL-1110-23
Chapter 3
Figure 3-129
Step 6
Click Get Default. A window similar to the one shown in Figure 3-130 displays.
Figure 3-130
Step 7
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-167
Chapter 3
Figure 3-131
Step 8
Click Get Default. A window similar to the one shown in Figure 3-132 displays.
Figure 3-132
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-168
OL-1110-23
Chapter 3
Step 9
Step 10
Enter the toll-free code, and click OK. Repeat Step 9 and Step 10 for each toll-free prefix you want to
configure for the Cisco BAMS.
Provisioning Zones
Note
If your MGC system does not need BAF output, proceed to the Provisioning Measurements section on
page 3-178.
Zoning provides a mechanism for differentiating between rating types. Each supported NPANXX
combination must be a member of a zone.
Use the following procedure to provision zones:
Step 1
Click the icon next to Zones in the left pane of the BAMS Configuration window to expand the
hierarchical tree.
Step 2
Click Identification. A window similar to the one shown in Figure 3-133 displays.
Figure 3-133
Step 3
Click Add. A window similar to the one shown in Figure 3-134 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-169
Chapter 3
Figure 3-134
Step 4
Enter the zone number and description, and click OK. A window similar to the one shown in
Figure 3-135 displays.
Figure 3-135
Step 5
Click Membership. A window similar to the one shown in Figure 3-136 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-170
OL-1110-23
Chapter 3
Figure 3-136
Step 6
Click Add. A window similar to the one shown in Figure 3-137 displays.
Figure 3-137
Add Npanxx
Step 7
Enter the 6-digit NPANXX numbers. You can enter several numbers by separating them with commas,
for example, 123456,345678,567890. You can obtain A/Bdig numbers from the MGC by clicking Look
up. A window displaying the dial plans defined on the MGC displays.
Step 8
Select a dial plan, and click OK. A window displaying all A/Bdig numbers displays.
Step 9
Step 10
A window similar to the one shown in Figure 3-137 redisplays. Enter the LATA, and select the zone.
Step 11
Click OK. A window similar to the one shown in Figure 3-138 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-171
Chapter 3
Figure 3-138
Step 12
Click Relationships. A window similar to the one shown in Figure 3-139 displays.
Figure 3-139
Step 13
Click Add. A window similar to the one shown in Figure 3-140 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-172
OL-1110-23
Chapter 3
Figure 3-140
Step 14
Select the origination zone, termination zone, and rate type. Indicate whether or not the relationship is
bidirectional. If you select bidirectional, two entries are added to the table.
Step 15
Click OK. A window similar to the one shown in Figure 3-141 displays.
Figure 3-141
Step 16
Click Exceptions. A window similar to the one shown in Figure 3-142 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-173
Chapter 3
Figure 3-142
Step 17
Click Add. A window similar to the one shown in Figure 3-143 displays.
Figure 3-143
Add RateExc
Step 18
Select the origination NPANxx, termination NPANxx, and rate type. Indicate whether or not the
exception is bidirectional.
Step 19
Click OK. A window similar to the one shown in Figure 3-144 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-174
OL-1110-23
Chapter 3
Figure 3-144
Exceptions Added
Specifying default origination and termination NPAs and the number of circuits in the trunk group
Click the icon next to Trunk Group Info in the left pane of the BAMS Configuration window to expand
the hierarchical tree.
Step 2
Click Trunk Group. A window similar to the one shown in Figure 3-145 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-175
Chapter 3
Figure 3-145
Step 3
To import trunk groups from the MGC, click Import, and then click OK at the confirmation prompt.
If you previously defined individual trunk groups, a message displays warning that they will be removed.
If you did not previously define individual trunk groups, this message does not display.
Step 4
Click OK. All trunk groups on the MGC display on the trunk group window.
Step 5
To add individual trunk groups, click Add. A window similar to the one shown in Figure 3-146 displays.
Figure 3-146
Add Trunkgrp
Step 6
Enter the trunk group name, select the connection type, and enter the origination NPA, termination NPA,
circuits, and prefix.
Step 7
Click OK. A window similar to the one shown in Figure 3-147 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-176
OL-1110-23
Chapter 3
Figure 3-147
Step 8
Click Sigpath. A window similar to the one shown in Figure 3-148 displays.
Figure 3-148
Step 9
Add a Sigpath if the MGC is nailed up. You can import from the MGC by clicking Import.
Step 10
To add a Sigpath, click Add. A window similar to the one shown in Figure 3-149 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-177
Chapter 3
Figure 3-149
Step 11
Enter the Sigpath ID in hexadecimal, select the trunk group number, and click OK. A window similar to
the one shown in Figure 3-150 displays.
Figure 3-150
Sigpath Added
Provisioning Measurements
Cisco BAMS generates and maintains measurements and performance indicators. It maintains a history
of traffic statistics on a network. Each measurement represents an accumulation of activity that took
place during a specific interval.
Use the following procedure to provision measurement types and properties:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-178
OL-1110-23
Chapter 3
Step 1
Click the icon next to Measurements in the left pane of the BAMS Configuration window to expand the
hierarchical tree.
Step 2
Click Thresholds A window similar to the one shown in Figure 3-151 displays.
Figure 3-151
Step 3
You can set thresholds for the item displayed in the drop-down menu next to VSCID/TRK/[IC]. Select
a value from the drop-down menu next to the threshold you want to change. When you have finished
setting thresholds, click Modify.
Step 4
To add an item to the drop-down menu next to VSCID/TRK/[IC], click Add. A window similar to the
one shown in Figure 3-152 displays.
Figure 3-152
Add TcaTbl
Step 5
Enter the VSCID, select the trunk group, and enter the carrier ID.
Step 6
Cisco BAMS generates and maintains measurements and performance indicators. It maintains a history
of traffic statistics on a network. Each measurement represents an accumulation of activity that took
place during a specific interval.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-179
Chapter 3
Step 7
Click OK. The item added is now accessible in the drop-down menu next to VSCID/TRK/[IC].
After the Cisco BAMS server is provisioned, you must deploy the new configuration. See the Cisco Voice
Services Provisioning Tool Users Guide for the software release you are using for complete instructions.
Provisioning Other
Provisioning other Cisco BAMS information includes information for provisioning Tag ID parameters
for the following tags:
ALM-PARMS
NODE-PARMS
POLL
SKIPCDB
SKIPCDE
P01FILTER
SWITCHINFO
BIN1110
Note
For more information on provisioning Cisco BAMS Tag ID parameter definitions and values, see the
Cisco Billing and Measurements Server Users Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps522/products_user_guide_list.html.
Provisioning ALM-PARMS
Use the following procedure to provision Cisco BAMS alarm parameter information:
Step 1
Click the icon next to Other in the left pane of the main BAMS Configuration window to expand the
hierarchical tree.
Step 2
Click ALM-PARMS. A window similar to the one shown in Figure 3-153 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-180
OL-1110-23
Chapter 3
Figure 3-153
Step 3
Enter a value for Maxlines (1 through 99999) indicating the maximum number of lines in a log file.
Step 4
Select the Message forward level value (0 through 6) by clicking the desired item displayed in the
drop-down menu.
Step 5
Select the Message discovery level value (0 through 6) by clicking the desired item displayed in the
drop-down menu.
Step 6
Provisioning NODE-PARMS
Use the following procedure to provision Cisco BAMS node parameter information:
Step 1
Click the icon next to Other in the left pane of the BAMS Configuration window to expand the
hierarchical tree.
Step 2
Click NODE-PARMS. A window similar to the one shown in Figure 3-154 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-181
Chapter 3
Figure 3-154
Step 3
Select the desired value from the drop-down menu for each node parameter you wish to set.
Step 4
Provisioning POLL
Use the following procedure to provision Cisco BAMS poll parameter information:
Step 1
Click the icon next to Other in the left pane of the BAMS Configuration window to expand the
hierarchical tree.
Step 2
Click POLL. A window similar to the one shown in Figure 3-155 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-182
OL-1110-23
Chapter 3
Figure 3-155
Step 3
Select the desired value from the drop-down menu for each node parameter you wish to set.
Step 4
Click Modify. The BAMS configuration for the POLL parameter is set.
Provisioning SKIPCDB
Use the following procedure to provision Cisco BAMS skip call data block (CDB) parameter
information:
Step 1
Click the icon next to Other in the left pane of the BAMS Configuration window to expand the
hierarchical tree.
Step 2
Click SKIPCDB.
Step 3
Click Add. A window similar to the one shown in Figure 3-156 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-183
Chapter 3
Figure 3-156
Step 4
Enter the desired identifier value in the dialog box for the new CDB being created by the MGC for which
Cisco BAMS is to skip processing.
Step 5
Click OK. A window similar to the one shown in Figure Figure 3-157 displays.
Figure 3-157
Provisioning SKIPCDE
Use the following procedure to provision Cisco BAMS skip call data element (CDE) parameter
information:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-184
OL-1110-23
Chapter 3
Step 1
Click the icon next to Other in the left pane of the BAMS Configuration window to expand the
hierarchical tree.
Step 2
Click SKIPCDE.
Step 3
Click Add. A window similar to the one shown in Figure 3-158 displays.
Figure 3-158
Step 4
Enter the desired identifier value in the dialog box for the new CDE being created by the MGC for which
Cisco BAMS is to skip processing.
Step 5
Click OK. A window similar to the one shown in Figure 3-159 displays.
Figure 3-159
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-185
Chapter 3
Provisioning P01FILTER
Use the following procedure to provision Cisco BAMS P01Filter parameter information:
Step 1
Click the icon next to Other in the left pane of the BAMS Configuration window to expand the
hierarchical tree.
Step 2
Click P01Filter. A window similar to the one shown in Figure 3-160 displays.
Figure 3-160
Step 3
Step 4
Step 5
Step 6
Step 7
Provisioning SWITCHINFO
Use the following procedure to provision the Cisco BAMS switch information parameters:
Step 1
Click the icon next to Other in the left pane of the BAMS Configuration window to expand the
hierarchical tree.
Step 2
Click SWITCHINFO. A window similar to the one shown in Figure 3-161 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-186
OL-1110-23
Chapter 3
Figure 3-161
Step 3
Enter the switch information value in the dialog box for the switch you are using.
Step 4
Provisioning BIN1110
Use the following procedure to provision BAMS BIN1110 information parameters:
Step 1
Click the icon next to Other in the left pane of the BAMS Configuration window to expand the
hierarchical tree.
Step 2
Click BIN1110. A window similar to the one shown in Figure 3-162 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-187
Chapter 3
Figure 3-162
Step 3
In the Enable 1070 CDB Output drop-down menu, select disable or enable.
Step 4
In the Enable 1060 CDB Output drop-down menu, select disable or enable.
Step 5
Step 6
Provisioning System
Provisioning system Cisco BAMS information includes information for provisioning Tag ID parameters
for the following tags:
MSC-PARMS
MSC-THRES
SYS-ALM-PARMS
MSC-PARMS tag ID is used to update the Mass Storage Control (MSC) Parameters table. This table
maintains definitions of conditions that generate alarms or events, based on parameters such as file type,
size, and age.
MSC-THRES tag ID is used to update the Mass Storage Thresholds table. This table maintains the
sytem-level MSC thresholds that determine when the MSC task generates alarms based on the
disk-capacity thresholds, and when it begins and stops deleting specific types of files to free up disk
space.
ALM-PARMs tag ID is used to update the Alarm Parameters table. The maxlines field is used to set the
size of the system log (syslog) file. The default value is 10, 000 lines. When the maxlines threshold is
surpassed, BAMS begins deleting lines from the syslog, starting with the oldest entries. The msgdisclvl
field is to set the level (for example, minor, major, critical) of alarms written to the syslog. The
msgfwdlvl field to set the level (for example, critical) of alarms forwarded to a network management
platform.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-188
OL-1110-23
Chapter 3
Provisioning MSC-PARMS
Use the Mass Storage Control (MSC) Parameters (Parms) tag ID to update the MSC-PARMS table. This
table maintains definitions of conditions that generate alarms or events based on parameters such as file
type, size, and age.
Use the following procedure to provision Cisco BAMS MSC parameter information:
Step 1
Click the icon next to System in the left pane of the BAMS Configuration window to expand the
hierarchical tree.
Step 2
Click MSC-PARMS. A window similar to the one shown in Figure 3-163 displays.
Figure 3-163
Step 3
Click the Add button. A window simialar to the one in Figure 3-164 displays.
Step 4
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-189
Chapter 3
Figure 3-164
Adding MSC-PARMS
Step 5
Click OK.
Step 6
When you have finished entering the desired parameter value, click Add.
Provisioning MSC-THRES
Use the Mass Storage Control Thresholds (MSC-THRES) tag ID to update the MSC-THRES table. This
table maintains the system-level MSC thresholds that determine when the MSC task generates alarms
based on disk-capacity, and when it starts and stops deleting specific file types to free up disk space.
Use the following procedure to provision Cisco BAMS MSC threshold parameter information:
Step 1
Click the icon next to System in the left pane of the BAMS Configuration window to expand the
hierarchical tree.
Step 2
Click MSC-THRES. A window similar to the one shown in Figure 3-165 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-190
OL-1110-23
Chapter 3
Figure 3-165
Step 3
Step 4
Provisioning SYS-ALM-PARMS
Use the Alarm Parameters (ALM-PARMS) tag ID to update the SYS-ALM-PARMS table. Use the
maxlines field to set the size of the system log (syslog) file. The default value is 10,000 lines. When the
maxlines threshold is surpassed, the Cisco BAMS begins deleting lines from the syslog, starting with the
oldest entries.
Use the msgdisclvl field to set the level (for example, minor, major, critical) of alarms written to the
syslog. Use the msgfwdlvl field to set the level (for example, critical) of alarms forwarded to a network
management platform.
Use the following procedure to provision the Cisco BAMS system alarm parameter information:
Step 1
Click the icon next to System in the left pane of the BAMS Configuration window to expand the
hierarchical tree.
Step 2
Click SYS-ALM-PARMS. A window similar to the one shown in Figure 3-166 displays.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
3-191
Chapter 3
Figure 3-166
Step 3
Step 4
Enter a value for Maxlines (1 through 99999), which indicates the maximum number of lines in a log file.
Step 5
Select the Message forward level value (0 through 6) by clicking the desired item displayed in the
drop-down menu.
Step 6
Select the Message discovery level value (0 through 6) by clicking the desired item displayed in the
drop-down menu.
Step 7
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
3-192
OL-1110-23
CH A P T E R
MML Basics
Revised: February 25, 2010, OL-1110-23
This chapter describes how to use Man-Machine Language (MML) commands to configure the
Cisco PGW 2200 Softswitch. It includes the following sections:
For more information on MML, including starting an MML session, killing an MML session, saving an
MML session, stopping an MML session, online help, operating tips, command syntax, and status
message definitions, refer to Cisco PGW 2200 Softswitch Release 9 MML Command Reference.
Before starting an actual configuration, refer to Chapter 2, Planning for Provisioning, for instructions
and worksheets for configuring your system.
Tip
In general, MML commands are not case sensitive (ExtCOT is an example of a case-sensitive command);
however, property values are case sensitive.
Tip
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-1
Chapter 4
MML Basics
Tip
Tip
An open provisioning session is not needed to access the AWHITE, ABLACK, BWHITE, BBLACK,
PORTTBL, TERMTBL, ANUMDPSEL, ACHGORIGIN, CLIPREFIX, CLIIPADDRESS,
H323IDDIVFROM, ANNOUNCEMENT, and SCRIPT tables.
Tip
After starting a provisioning session, MML displays COMPLD, indicating success. (This is true for all
successful commands; for all failed commands, MML displays DENY.).
Tip
A provisioning session inactive for 30 minutes results in a warning. If the session continues without
activity for five more minutes, it terminates.
Tip
As many as 12 MML sessions may exist at any given time; however, only one provisioning session is
allowed.
Tip
You can create an ASCII text file to batch process provisioning commands.
Tip
When performing batch provisioning, be sure no call processing is going on to prevent impacting call
performance.
Tip
You can create batch files for individual segments of provisioned data.
Tip
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.
Tip
Place quotes around all value strings in your commands. For example, card=Interface1. The keyword
card does not have to be enclosed in quotes. The value Interface1 is being assigned to keyword card and
must be enclosed in quotes.
Tip
You can obtain online help in an MML session by typing help at the command prompt.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-2
OL-1110-23
Chapter 4
MML Basics
MML Configuration Commands
Timesaver
To repeat the last MML command you entered, press the Up Arrow key. To scroll through all the previous
MML commands, continue to press the Up Arrow key after pressing the Shift key starting an MML
session.
Caution
Configuration session commandsUse session commands to work with entire provisioning data
filesets. The session commands are described in Table 4-1.
Configuration bulk export commandUse the bulk command to export the current
Cisco PGW 2200 Softswitch configuration to a file. The bulk export command is described in
Table 4-3.
Due to differences in software file formats, do not use the prov-sync command between
Cisco PGW 2200 Softswitch platforms that have different software revision levels.
Table 4-1
CommandExplanation
Description
PROV-STAStart Provisioning
Session
PROV-CPYCopy Provisioning
Session
Note
Note
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-3
Chapter 4
MML Basics
Table 4-1
CommandExplanation
Description
PROV-DPLYDeploy Provisioning
Session
PROV-SYNCSynchronize
Provisioning Data
Note
Note
Note
Caution
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-4
OL-1110-23
Chapter 4
MML Basics
MML Configuration Commands
Table 4-1
CommandExplanation
Description
PROV-STPStop Provisioning
Session
PROV-EXPExport Configuration
Data
Table 4-2
CommandExplanation
Description
PROV-ADDAdds a Component
PROV-DLTDeletes a Component
PROV-EDEdits a Component
PROV-RTRVRetrieves a
Component
Note
For more information on these commands, refer to the Cisco PGW 2200 Softswitch Release 9
MML Command Reference.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-5
Chapter 4
MML Basics
Table 4-3
CommandExplanation
Description
Tip
Although you can save to either the same version or a revised version, saving to a revised version instead
of overwriting the old version gives you an easy way to return to a known configuration if there are
problems with the revised version.
Note
On the Cisco PGW 2200 Softswitch running software Release 9, it is possible that the standby system
may not recover from a failover if the active system has an open provisioning session. Make sure there
is no provisioning session open on the active Cisco PGW 2200 Softswitch.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-6
OL-1110-23
Chapter 4
MML Basics
Working with MML Session Commands
Note
You can use new as the source configuration only when there is no existing, active set of provisioning
data in the configuration library. Therefore, new cannot be used as the source configuration once a
provisioning session has been saved and activated by using prov-cpy or prov-dply. Once you have saved
and activated a set of data, you must use either active or the name of the set of provisioning data as the
source configuration.
Purpose
mml> prov-sta::srcver="new",dstver="ver1"
Use the PROV-RTRV command to verify that your new configuration has been saved.
Note
If you create a new configuration, while a non-empty active configuration is running, and the same MML
component names exist in both, the new configuration is treated as a modification and not a creation. If
this is not your desired result, start the provisioning session on an empty active configuration.
Tip
An empty active configuration can be created by using the following MML commands. Use caution
when creating an empty configuration because an empty configuration indicates no service is available.
mml> prov-sta:srcvernew,dstver=empty-ver
mml> prov-cpy
Tip
The Cisco PGW 2200 Softswitch software Release 9 appends CFG_ in front of any user-supplied
destination version name. For example, ver1 becomes CFG_ver1.
In the preceding example, if you enter the PROV-STA command without including the quotation marks
around new or ver1, the following error message is generated:
M
DENY
IIDT
"SRCVER"
/* Input, Invalid Data Parameter */
;
Note
If you enter an invalid MML command, only the first error encountered in the command string is listed.
Any additional errors in the MML command are not listed.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-7
Chapter 4
MML Basics
The first line of the returned MML error message indicates the command was denied (DENY). The
second line indicates the error was due to an invalid input data parameter (IIDT). The third line indicates
the invalid data parameter (SRCVER). And the fourth line indicates the error cause in generic terms.
Note
Refer to the Cisco Media Gateway Controller Software Release 9 Messages Reference Guide for a list
of error messages and their meanings.
Purpose
mml> prov-sta::srcver="ver1",dstver="ver1"
Observe the terminal window to verify that COMPLD is displayed in response to the MML command.
Note
For you to modify an existing configuration directory, the srcver and dstver must be the same. If they are
the same, then the original configuration is overwritten by the new configuration.
Tip
It is a good practice to copy an existing configuration instead of overwriting it. This gives you an easy
way to return to a known configuration if there are problems with the new configuration.
Note
If the source configuration specified is new, the software does not allow you to overwrite an existing
configuration. For example, if a provisioning directory CFG_ver1 exists, the following command fails:
mml> prov-sta::srcvernew,dstver=ver1
Note
In Release 9, an existing, nonactive configuration can be overwritten by using the following command:
mml> prov-sta::srcvernew,dstver=ver1, confirm
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-8
OL-1110-23
Chapter 4
MML Basics
Working with MML Session Commands
Command
Purpose
mml> prov-sta::srcver="active",
dstver="ne_active"
Use the PROV-RTRV command to verify that the existing configuration has been saved as another
version.
Tip
dstver cannot be the same as the existing directory name; otherwise, you overwrite the existing
non-active provisioning configuration.
Tip
A provisioning session inactive for 30 minutes results in a warning. If the session continues without
activity for five more minutes, it terminates.
Purpose
mml> prov-sta::srcver="ver1",dstver="ver2"
Use the PROV-RTRV command to verify that the existing configuration has been saved as another
version.
Tip
A provisioning session inactive for 30 minutes results in a warning. If the session continues without
activity for five more minutes, it terminates.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-9
Chapter 4
MML Basics
Tip
Command
Purpose
mml> PROV-CPY
The PROV-CPY command differs from the PROV-DPLY command in that the PROV-DPLY command
applies the configuration changes to dual Cisco PGW 2200 Softswitch configurations, whereas the
PROV-CPY command applies the configuration changes to single Cisco PGW 2200 Softswitch
configurations only.
To avoid errors before a complete configuration change, be sure the component being changed is not in
service (IS), then execute the PROV-CPY command.
Use the RTRV-softw:all command to verify that all processes are running.
Use the PROV-RTRV:session command to verify your configuration.
Purpose
mml> PROV-DPLY
Tip
A provisioning session not active for 30 minutes results in a warning. If the session continues without
activity for five more minutes, it terminates.
The PROV-CPY command is different from the PROV-DPLY command in that the PROV-DPLY
command applies the configuration changes to dual Cisco PGW 2200 Softswitch configurations,
whereas the PROV-CPY command applies the configuration changes to a single
Cisco PGW 2200 Softswitch configuration.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-10
OL-1110-23
Chapter 4
MML Basics
Working with MML Session Commands
Command
Purpose
mml> PROV-SYNC
Note
Caution
Tip
The configuration data always goes from the active Cisco PGW 2200 Softswitch side to the standby side.
Note
You cannot perform the PROV-SYNC command with an open provisioning session.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-11
Chapter 4
MML Basics
Command
Purpose
mml> PROV-STP
On successful completion of this command, the POM releases the lock on the configuration data files.
Tip
Caution
This command saves the new configuration but does not activate it. You must use the PROV-CPY or
PROV-DPLY command to activate the configuration.
Quitting an MML session does not stop the session. While inactive sessions terminate, the only
commands that can stop a session are PROV-STP, PROV-CPY, and PROV-DPLY.
Purpose
mml> sw-over::CONFIRM
Use the RTRV-NE command to verify the manual switchover. For information on this command, refer
to the Cisco Media Gateway Controller Software Release 9 MML Command Reference Guide.
The standby system becomes active in less than two seconds after the switchover.
If a provisioning session exists, the PROV-EXP command uses the provisioning link as the source
of the data to be exported. If no provisioning session exists, this command uses the active link as the
source of the data to be exported.
If the directory indicated with DIR_NAME already exists, the PROV-EXP command fails. This
ensures that current files generated by previous PROV-EXP commands are not overwritten by a
subsequent PROV-EXP command.
To export core configuration data (signaling paths, SS7 nodes, trunks, trunk groups), routing plans, and
dial plans, use the PROV-EXP command as follows:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-12
OL-1110-23
Chapter 4
MML Basics
Working with MML Session Commands
Command
Purpose
mml> prov-exp:config:dirname=saved_config
mml> prov-exp:routing:dirname=saved_config
mml> prov-exp:numan:dirname=saved_config
mml> prov-exp:all:dirname=saved_config
Caution
Cisco strongly recommends that you perform this import procedure during a maintenance window. This
procedure will stop all call processing on both the active and standby systems.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-13
Chapter 4
MML Basics
Note
Be sure that you are familiar with the use of the prov-cpy and prov-sync commands as described in the
PROV-SYNCSynchronize Provisioning Data section of the Cisco PGW 2200 Softswitch Release 9
MML Command Reference.
Step 1
Step 2
Step 3
Log in as mgcusr.
b.
c.
d.
e.
f.
Note
The system replaces the XECfgParm.dat file when it copies the new configuration files,
so you must restore XECfgParm.data with the above command.
Step 4
Step 5
When the previously active system comes up, combine the two MML files.
a.
Navigate to the directory that contains the saved (previously exported) configuration:
cd /opt/CiscoMGC/etc/cust_specific/<saved_config>
b.
c.
Step 6
> all-config.mml
Find the numan-add:dialplan:custgrpid in <CustGrpID>.mml file and add it to the top of the
all-config.mml file. You must do this step manually for numan-add:dialplan:custgrpid, because
it does not copy automatically.
Step 7
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-14
OL-1110-23
Chapter 4
MML Basics
Working with Provisioning Commands
Step 8
When the standby system comes up, issue the prov-sync command on the active system:
prov-sync
Note
When you migrate an export_trkgrp.dat file from Release 9.6(1) or earlier into Release 9.7(3) or later,
first use the migrateTKGfile script to change the file from nonXML format to XML format. Then
execute the prov-add:files commands to import the files.
Files exported from Release 9.7(3) and later are in XML format and can be imported directly into later
releases. Therefore, there is no need for you to use the migrateTKGfile script in these cases.
ComponentsDescribe physical and logical entities, such as external switches, signaling links, and
signaling services.
ParametersAre defined when you create or modify a component. For example, when you add a
signaling service, the options that you specify when you create the service are called parameters.
Note
Although parameters are often called options or properties, properties have a specific
meaning in this guide.
PropertiesAre options that are applied to a linkset or signaling service or trunk groups when you
create the linkset or service. A default set of properties is assigned to each linkset and signaling
service. The default property settings should work for most installations. You can override them to
customize your installation.
Use the MML provisioning commands for the actions discussed in the following sections:
Adding a Component
To add a component to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD command
as follows:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-15
Chapter 4
MML Basics
Command
Purpose
mml> prov-add:dpc:name="dpc1",
netaddr="0.0.1",netind=2,desc="DPC1",
Tip
After you add a system component, you can change the value of most parameters at any time. However,
you cannot change the component type or name, because these attributes uniquely identify the
component you are modifying. To change the type or name of a component, you must delete the
component and create a new component with a new type and name.
If you want to use a components default values, you do not have to specify any parameters. For
information on component default parameters, refer to Chapter 2, Planning for Provisioning.
When adding components, add the components in the following order.
Add linksets
Add IP links
Modifying a Component
To modify a provisioning object within the data files, use the PROV-ED command as follows:
Command
Purpose
mml> prov-ed:opc:name="opc1",
netaddr="120.40.221",netind=2,desc="opc1,
type="trueopc"
After you enter the command to modify a component, the component is changed. To verify the change,
use the PROV-RTRV command.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-16
OL-1110-23
Chapter 4
MML Basics
Working with Provisioning Commands
Tip
Deleting a Component
To remove a component from the Cisco PGW 2200 Softswitch configuration, use the PROV-DLT
command as follows:
Command
Purpose
mml> prov-dlt:opc:name="opc1"
Tip
If you cannot remember the name of a component, use the PROV-RTRV:ALL command to display all
components.
Note
You cannot delete a component that is a parent of another component. For example, you cannot delete a
linkset that contains links. You receive an error message when you try to delete a parent component.
Command
Purpose
mml> prov-add:sigsvcprop:name="ss7srv1",
alarmcarrier="1"
To view the component configuration, use the PROV-RTRV command as described in the Retrieving
Provisioning Session Information section on page 4-33.
Tip
Working with properties is similar to working with components, but there are differences. For example,
when you create a component, you have to define values for all the component parameters. However, you
never have to create a component property, because a set of default properties is automatically created
when you create a component. If you want to change a default property value, you must override that
value.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-17
Chapter 4
MML Basics
For more information on components, parameters, and properties, refer to Chapter 2, Planning for
Provisioning.
After overriding a property value with the PROV-ADD command, an override statement is added to the
configuration file for a specific linkset or signaling service property. Do not use additional PROV-ADD
commands to change the overridden property value. Use the PROV-ED command to modify overridden
property values, as explained in the Changing Overridden Properties section on page 4-18.
Purpose
mml> prov-ed:sigsvcprop:NAME="ss7srv1",
alarmcarrier="2"
After you enter the PROV-ED command, the property value is changed. To view the component
configuration, use the PROV-RTRV command.
Tip
There are two property types: lnksetprop and sigsvcprop. The lnksetprop property type changes
properties for a linkset, and the sigsvcprop property type changes properties for a signaling service. The
name parameter in the command above specifies a specific protocol family for the linkset or a specific
signaling service that you have already defined. Replace the property parameter with the property name.
For more information on these property types, refer to the Chapter 2, Planning for Provisioning.
Note
Changes made to the lnksetprop property type do not take effect until the Cisco PGW 2200 Softswitch
software is stopped and started again, even though the PROV-RTRV command indicates the changed
value.
Note
The TRNKGRPPROP property type supports trunk group provisioning. For more information, refer to
Overriding the Trunk Group Property section on page 5-32.
Table 4-4 lists the properties that can be provisioned and indicates if the modified property value takes
effect without stopping and restarting the Cisco PGW 2200 Softswitch software.
Table 4-4
Provisionable Properties
Property
ACCRespCatName
Yes
ACCRespCntlInhibit
No
ACLDur
No
ADigitCCPrefix
Yes
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-18
OL-1110-23
Chapter 4
MML Basics
Working with Provisioning Commands
Table 4-4
adjDestinations
No
AInternationalPrefix
Yes
AlarmCarrier
Yes
allowCRMCRA
Yes
allowEXM
Yes
AllowH323Hairpin
Yes
ANationalPrefix
Yes
AnnSuppressInbandInfo
Yes
Anumnormalise
Yes
AOCDefaultTariffId
Yes
AOCEnabled
Yes
AOCInvokeType
Yes
AOCNodeID
Yes
AtmConnectionType
Yes
atpInclude
Yes
AuditWhenSscIs
No
BcInitState
Yes
BDigitCCPrefix
Yes
BDigitCCrm
Yes
BInternationalPrefix
Yes
BNationalPrefix
Yes
Bnumnormalise
Yes
BothwayWorking
Yes
BTechPrefix
Yes
CallForwardRerouteDisabled
Yes
CarrierInfoTransferBackward
Yes
CarrierInfoTransferForward
Yes
CarrierScreening
No
carrierSelectInclude
Yes
CCOrigin
Yes
CctGrpCarrier
Yes
CGBA2
Yes
cgpnForceIncomplete
Yes
cgpnInclude
Yes
cgpnPres
Yes
CgpnPresRes
Yes
ChargeAreaInformation
Yes
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-19
Chapter 4
MML Basics
Table 4-4
ChargeOrigin
Yes
chnNonGeo
Yes
chnOlipInclude
Yes
cipInclude
Yes
cipNonGeo
Yes
CircHopCount
Yes
CLIDefaultAllowed
Yes
CLIPEss
Yes
CLISelect
Yes
CliSelectionForCodeOfPractice3
Yes
CLLI
Yes
COLDefaultAllowed
Yes
CompressionType
Yes
confusion
Yes
congProc
Yes
CorrelationCallIDFormat
Yes
CotInTone
Yes
CotOnTerminatingSupport
Yes
CotOutTone
Yes
CotPercentage
Yes
CustGrpId
No
CustomerVPNid
Yes
CustomerVPNOffNetTblNum
Yes
CustomerVPNOnNetTblNum
Yes
defaultBC
Yes
DefaultCARIDNatNetIdPlan
Yes
DefaultCARIDNetId
Yes
DefaultCARIDNetType
Yes
DefaultCHG
Yes
DefaultCHGNOA
Yes
DefaultCHGNPI
Yes
DefaultDN
Yes
DefaultDNNOA
Yes
DefaultDNNPI
Yes
DefaultDNPres
Yes
DefaultDNSI
Yes
DefaultOLI
Yes
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-20
OL-1110-23
Chapter 4
MML Basics
Working with Provisioning Commands
Table 4-4
DefaultPN
Yes
DefaultPNNOA
Yes
DefaultPNNPI
Yes
DefaultPNPres
Yes
delayTimer
No
dialogRange
No
EchoCanRequired
Yes
EnableIPScreening
Yes
ExpiresTimer
Yes
ExpiryWarnToneDur
Yes
ExpiryWarnToneType
Yes
ExtCOT
Yes
FastConnect
Yes
FAXsupport
Yes
FeatureTransparencyDisabled
Yes
ForwardCLIinIAM
Yes
ForwardSegmentedNEED
Yes
FromField
Yes
gapInclude
Yes
GatewayName
No
GatewayRBToneSupport
Yes
GenTimerT1
Yes
GenTimerT2
Yes
GLARE
Yes
gnInclude
Yes
GRA2
Yes
GRSEnabled
No
GRSonSSCEnabled
No
GtdCapTypeProp
Yes
GtdMsgFmt
Yes
GWDefaultATMProfile
Yes
GWDefaultCodecString
No
GWNetworkContinuity
Yes
GWProtocolVersion
No
H323AdjunctLink
Yes
HoldTimer
Yes
hopOn
Yes
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-21
Chapter 4
MML Basics
Table 4-4
InhibitIncomingCallingNameDisplay
Yes
InhibitIncomingConnectedNameDisplay
Yes
InhibitIncomingConnectedNumberDisplay
Yes
InhibitOutgoingCallingNameDisplay
Yes
InhibitOutgoingConnectedNameDisplay
Yes
InhibitOutgoingConnectedNumberDisplay
Yes
InitEndpointsAsEnabled
No
InSessionTimer
Yes
InviteTimerT1
Yes
IOCC.chkPtPort
Yes
IOCC.port
Yes
IsupTransEarlyACMEnable
Yes
IsupTransEarlyBackwardDisabled
Yes
IsupTransparencyDisabled
No
jipDefault
Yes
jipInclude
Yes
lapdDropErr
No
lapdKval
No
lapdN200
No
lapdN201
No
lapdT200
No
lapdT203
No
layerRetries
No
layerTimer
No
LocalPort
Yes
LocationNumber
Yes
LoopAvoidanceCounter
Yes
LoopAvoidanceSupport
Yes
MaxACL
Yes
MaxForwards
Yes
maxMessageLength
No
MaxRedirectCnt
Yes
MaxSubscriptionDuration
Yes
MGCdomain
Yes
MgcpBehavior
No
mgcpDomainNameRemote
No
mgcpGWRspAckTimeout
No
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-22
OL-1110-23
Chapter 4
MML Basics
Working with Provisioning Commands
Table 4-4
mgcpGWStdbyHeartbeatInterval
No
mgcpHeartbeatInterval
No
mgcpLocalIpInterfacePollCount
No
mgcpMaxRspAckToBuffer
No
mgcpRemoteIpPollCount
No
mgcpRetxCount
No
mgcpRetxTimer
No
MGCSipVersion
Yes
MidCallCPInterval
Yes
MinEventSubscribeDuration
Yes
mtp3Queue
No
MWIInvokeTimerT1
Yes
MwiStringOFF
Yes
MwiStringON
Yes
NatureOfAddrHandling
No
NetworkType
Yes
NFASImplicitInterfaceId
Yes
Normalization
Yes
notificationInclude
Yes
Npa
Yes
ocnInclude
Yes
OD32DigitSupport
Yes
OMaxDigits
No
OMinDigits
No
OmitCgPnFromUnavailable
Yes
OOverlap
No
OrigCarrierId
No
OutSessionTimer
Yes
OverlapDigitTime
Yes
OwnClli
Yes
PackageType
Yes
PlayAnnouncement
Yes
populateSDPInfoInCDR
Yes
PostConnectToneDuration
Yes
PostConnectToneValue
Yes
PropagateSvcMsgBlock
Yes
ProtocolidandVariantidProv
Yes
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-23
Chapter 4
MML Basics
Table 4-4
radiuskey
Yes
radiusretrycount
Yes
radiustimeout
Yes
redirCapInclude
Yes
redirCounterInclude
Yes
RedirectingNbrMap
Yes
redirInfoInclude
Yes
RedirMax
Yes
ReleaseMode
Yes
restartTimer
No
RetryAfterTimer
Yes
RingNoAnswer
Yes
RLM.port
Yes
RLM.PropagateSvcMsgBlock
Yes
RLM.timerCmdAck
Yes
RLM.timerLinkDownMin
Yes
RLM.timerLinkEcho
Yes
RLM.unstableLink
Yes
rnInclude
Yes
RouteId
Yes
RoutePref
Yes
rudpNumRetx
No
rudpRetxTimer
No
rudpWindowSz
No
SatelliteInd
Yes
ScreenFailAction
Yes
SdpXmitToH323Trigger
Yes
SendAddressInCgpn
Yes
sendAfterRestart
No
SendDtmfBeforeConnect
Yes
serviceCodeInclude
Yes
sgcpRetxCount
No
sgcpRetxTimer
No
SipIPSource
Yes
sipMimeBodySupport
Yes
SipReferForSingleStepXfer
Yes
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-24
OL-1110-23
Chapter 4
MML Basics
Working with Provisioning Commands
Table 4-4
SipSatelliteIndEnable
(Release 9.7(3) S5P5 and later)
Yes
slsTimer
No
spanId
No
srcpAuditGwInterval
No
srcpAuditLineInterval
No
srcpHeartbeatInterval
No
srcpIpPortLocal
No
srcpIpPortRemote
No
srcpRemoteAuditGwInterval
No
srcpRetxCount
No
srcpRetxTimer
No
srtTimer
No
SS7-ANSI.mtp3ApcMtpRstrtT28
No
SS7-ANSI.mtp3DlnkConnAckT7
No
SS7-ANSI.mtp3FrcUnhT13
No
SS7-ANSI.mtp3InhAckT14
No
SS7-ANSI.mtp3LocInhTstT20
No
SS7-ANSI.mtp3MaxSltTries
No
SS7-ANSI.mtp3MsgPriority
No
SS7-ANSI.mtp3MtpRstrtT24
No
SS7-ANSI.mtp3RepeatRstrtT26
No
SS7-ANSI.mtp3TfrUsed
No
SS7-ANSI.mtp3TraSntT29
No
SS7-ANSI.mtp3tstSltmT1
No
SS7-ANSI.mtp3tstSltmT2
No
SS7-ANSI.mtp3UnhAckT12
No
SS7-ANSI.reference
Yes
SS7-ANSI.standard
No
SS7-China.mtp3ApcMtpRstrtT21
No
SS7-China.mtp3DlnkConnAckT7
No
SS7-China.mtp3FrcUnhT13
No
SS7-China.mtp3InhAckT14
No
SS7-China.mtp3LocInhTstT22
No
SS7-China.mtp3MaxSltTries
No
SS7-China.mtp3MsgPriority
No
SS7-China.mtp3MtpRstrtT20
No
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-25
Chapter 4
MML Basics
Table 4-4
SS7-China.mtp3TfrUsed
No
SS7-China.mtp3tstSltmT1
No
SS7-China.mtp3tstSltmT2
No
SS7-China.mtp3UnhAckT12
No
SS7-China.reference
Yes
SS7-ITU.mtp3ApcMtpRstrtT21
No
SS7-ITU.mtp3DlnkConnAckT7
No
SS7-ITU.mtp3FrcUnhT13
No
SS7-ITU.mtp3InhAckT14
No
SS7-ITU.mtp3LocInhTstT22
No
SS7-ITU.mtp3MaxSltTries
No
SS7-ITU.mtp3MsgPriority
No
SS7-ITU.mtp3MtpRstrtT20
No
SS7-ITU.mtp3TfrUsed
No
SS7-ITU.mtp3tstSltmT1
No
SS7-ITU.mtp3tstSltmT2
No
SS7-ITU.mtp3UnhAckT12
No
SS7-ITU.reference
Yes
SS7-ITU.standard
Yes
SS7-Japan.mtp3ApcMtpRstrtT21
No
SS7-Japan.mtp3ClearTfc
No
SS7-Japan.mtp3DlnkConnAckT7
No
SS7-Japan.mtp3FrcUnhT13
No
SS7-Japan.mtp3InhAckT14
No
SS7-Japan.mtp3LocInhTstT22
No
SS7-Japan.mtp3MaxSltTries
No
SS7-Japan.mtp3MsgPriority
No
SS7-Japan.mtp3MtpRstrtT20
No
SS7-Japan.mtp3T12
No
SS7-Japan.mtp3T13
No
SS7-Japan.mtp3T14
No
SS7-Japan.mtp3T20
No
SS7-Japan.mtp3T21
No
SS7-Japan.mtp3T22
No
SS7-Japan.mtp3T7
No
SS7-Japan.mtp3Tc
No
SS7-Japan.mtp3TfrUsed
No
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-26
OL-1110-23
Chapter 4
MML Basics
Working with Provisioning Commands
Table 4-4
SS7-Japan.mtp3tstSltmT1
No
SS7-Japan.mtp3tstSltmT2
No
SS7-Japan.mtp3tstSrtaT10
No
SS7-Japan.mtp3UnhAckT12
No
SS7-Japan.reference
Yes
SS7-Japan.sltmT1
Yes
SS7-Japan.sltmT2
Yes
SS7-Japan.srtaT10
Yes
SS7-UK.mtp3ApcMtpRstrtT21
No
SS7-UK.mtp3DlnkConnAckT7
No
SS7-UK.mtp3FrcUnhT13
No
SS7-UK.mtp3InhAckT14
No
SS7-UK.mtp3LocInhTstT22
No
SS7-UK.mtp3MaxSltTries
No
SS7-UK.mtp3MsgPriority
No
SS7-UK.mtp3MtpRstrtT20
No
SS7-UK.mtp3TfrUsed
No
SS7-UK.mtp3tstSltmT1
No
SS7-UK.mtp3tstSltmT2
No
SS7-UK.mtp3UnhAckT12
No
SS7-UK.reference
Yes
SSCTInvokeTimerT1
Yes
sstTimer
No
STdigitforCLI
Yes
SubscribeNotifySupport
Yes
Support183
Yes
SupportReliable100
Yes
SuppressCHGNtoCGPNMapping
Yes
SuppressCLIDigits
Yes
SwitchID
Yes
T_CCR
Yes
T_CCRR
Yes
T_CGB
Yes
T_CGBA
Yes
T_CRA
Yes
T_CVT
Yes
T_GRS
Yes
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-27
Chapter 4
MML Basics
Table 4-4
T1
Yes
T12
Yes
T13
Yes
T14
Yes
T15
Yes
T16
Yes
T17
Yes
T18
Yes
T19
Yes
T2
Yes
T20
Yes
T21
Yes
T22
Yes
T23
Yes
T24
Yes
T25
Yes
T26
Yes
T27
Yes
T28
Yes
T309Time
Yes
T310Time
Yes
T33
Yes
T34
Yes
T35
Yes
T36
Yes
T38
Yes
T4
Yes
T5
Yes
T6
Yes
T7
Yes
T8
Yes
T9
Yes
Ta1TimePeriod
Yes
Ta2TimePeriod
Yes
Ta3TimePeriod
Yes
TCAPOverIPKpAlive
No
TCAPOverIPKpOpcod
No
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-28
OL-1110-23
Chapter 4
MML Basics
Working with Provisioning Commands
Table 4-4
TCAPOverIPKpTimer
No
TCAPOverIPTcpConn
No
TlinkAlignTime
Yes
TMaxDigits
Yes
TMinDigits
Yes
TOverlap
Yes
TransferAwaitConnect
Yes
transReqInclude
Yes
unavailProc
Yes
UnsolicitedNotifyMethod
Yes
variant
No
VOIPPrefix
Yes
WaitAnswerTimer
Yes
WaitOrigSDPTimer
Yes
WaitTermSDPTimer
Yes
Purpose
mml> prov-rtrv:all
/*
Name
Parent Name
-------------"TKGFile"
"LPC-01"
"BCFile"
"LPC-01"
"TrkRtFile"
"LPC-01"
"Ether1"
"LPC-01"
"Ether2"
"LPC-01"
"en1"
"Ether1"
"en2"
"Ether2"
"ls1"
"stp1"
"route1"
"LPC-01"
"opc"
"LPC-01"
"dpc1"
"LPC-01"
"dpc2"
"LPC-01"
"ss7svc1"
"dpc1"
"ss7svc2"
"dpc2"
"ls1link1"
"ls1"
"stp1"
"LPC-01"
"stp2"
"LPC-01"
"mate1"
"LPC-01"
*/
TID
--TRNKGRP
BEARCHAN
TRNKROUTE
CARD
CARD
ENETIF
ENETIF
LNKSET
SS7ROUTE
PTCODE
PTCODE
PTCODE
SS7PATH
SS7PATH
C7IPLNK
APC
APC
SS7SUBSYS
Description
----------""
""
""
"Motherboard 1"
"Motherboard 2"
"Ethernet IF 1"
"Ethernet IF 2"
"Link Set 1"
"route to dpc1 via ls1"
"Own Pointcode"
"Dest Point Code 1"
"Dest Point Code 2"
"SS7 Service to DPC1"
"SS7 Service to DPC2"
"SS7 link 1 to SP1"
"STP 1 Point Code"
"STP 2 Point Code"
"mate stp1 to stp2"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-29
Chapter 4
MML Basics
Tip
If you cannot remember the name of a component, use the PROV-RTRV:ALL command to display all
components.
Purpose
mml> prov-rtrv:card:"ALL"
Tip
Command
Purpose
mml> prov-rtrv:enetif:name="en2"
If you cannot remember the name of a component, use the PROV-RTRV:ALL command to display all
components.
Purpose
mml> prov-rtrv:iplnk:svc="mgcpsvc1"
You can use the following provisioning commands to retrieve information based on the signaling service
or trunk group.
Nailed trunkRetrieve all nailed trunks associated with the named (source or destination) signaling
service.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-30
OL-1110-23
Chapter 4
MML Basics
Working with Provisioning Commands
mml> prov-rtrv:nailedtrnk:srcsvc="sc-1"
Switched trunkRetrieve all switched trunks associated with the named (source or destination)
signaling service. You can also retrieve the span (source or destination) too.
mml> prov-rtrv:switchtrnk:trnkgrpnum="1000"
Trunk groupRetrieve all trunk groups associated with the named signaling service. You can also
retrieve the span (source or destination) too.
mml> prov-rtrv:trnkgrp:svc="ss7svc1"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-31
Chapter 4
MML Basics
Command
Purpose
mml> prov-rtrv:variants
/*
MDO File name
Protocol Family
-------------------------DPNSS_BTNR188PNSS
ETS_300_102ISDNPRI
ETS_300_102_C2ISDNPRI
ATT_41459ISDNPRI
ATT_41459_C2ISDNPRI
BELL_1268ISDNPRI
ETS_300_172ISDNPRI
BELL_1268_C2ISDNPRI
NTT_INS_1500ISDNPRI
ETS_300_121SS7-ITU
Q931_AUSTRALIAISDNPRI
Q931ISDNPRI
Q931_SINGAPOREISDNPRI
GR317SS7-ANSI
NORTEL_IBN7SS7-ANSI
ANSISS7_92SS7-ANSI
ANSISS7_STANDARDSS7-ANSI
ANSISS7_C2SS7-ANSI
ANSISS7_C3SS7-ANSI
BTNUP_BTNR167SS7-UK
BTNUP_NRCSS7-UK
BTNUP_IUPSS7-UK
HONGKONGSS7-ITU
ETS_300_356SS7-ITU
ISUPV2_FRENCHSS7-ITU
ISUPV2_AUSTRIANSS7-ITU
ISUPV2_SWISSSS7-ITU
ISUPV2_SWISS_C2SS7-ITU
ISUPV2_GERMANSS7-ITU
ISUPV2_FINNISH96SS7-ITU
ISUPV1_POLISS7-ITU
ISUPV2_DUTCHSS7-ITU
ISUPV2_JAPANSS7-Japan
ISUPV2_JAPAN_C2SS7-Japan
ISUPV2_CZECHSS7-ITU
ISUPV3SS7-ITU
ISUPV3_UKSS7-UK
ISUPV3_UK_C2SS7-UK
ISUPV3_UK_C3SS7-UK
ISUPV3_UK_C4SS7-UK
*/
Tip
Note
The protocol variants displayed may vary depending on the software revision you are using.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-32
OL-1110-23
Chapter 4
MML Basics
Working with Provisioning Commands
Purpose
mml> prov-rtrv:session
Note
The MML provisioning commands must be in the correct provisioning sequence based on component
dependencies. For example, a line interface cannot be provisioned before the interface card.
Some advantages to using an MML provision batch file are that you can cut and paste commands and
the batch files can be used repeatedly to re-provision the Cisco PGW 2200 Softswitch or to quickly
provision multiple MGCs.
Note
When performing batch provisioning, be sure no call processing is on going to prevent impacting call
processing performance.
To create a batch file, use an ASCII text editor program to create a new file with one MML command on
each line, as shown in Figure 4-1. You can use any name for the file (use the UNIX file naming
convention) and you can copy and paste components. You can store it in any location; however, the file
must be accessible on the machine where you run MML sessions.
Figure 4-1
prov-sta::srcver="new",dstver="oldyella"
prov-add:opc:name="opc1",netaddr="111.111.666",netind=1,desc="opc1",type=trueopc
prov-add:dpc:name="dpc1",netaddr="444.777.444",netind=1,desc="TDM Switch dpc1"
prov-add:dpc:name="dpc2",netaddr="555.333.555",netind=3,desc="Host Node dpc2"
prov-add:apc:name="apc1",netaddr="666.222.222",desc="STP 1 APC pointcode",netind=1
prov-add:apc:name="apc2",netaddr="777.333.333",desc="STP 2 APC pointcode",netind=2
prov-add:apc:name="apc3",netaddr="888.777.777",desc="STP 3 APC pointcode",netind=3
prov-cpy
In the sample batch file shown in Figure 4-1, notice that 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 then
automatically stops the provisioning session.
Also notice that the commands in the file do not configure a complete system. You can create batch files
to define complete systems or modify parts of an existing system.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-33
Chapter 4
MML Basics
Note
If you want to test the batch file before you use it, use the PROV-STP command to first stop the
provisioning session.
If you plan to run the batch file multiple times on the same host, plan the source and destination
directories to ensure file names are not duplicated.
The example shown in Figure 4-1 would fail if run twice, because the destination directory already
exists. You could edit the batch file after the first execution and replace the source version name with the
destination version name. Future executions of the batch file would then replace the previous
configuration. For more information on the source and destination directories, refer to the Starting a
Provisioning Session section on page 4-6.
Note
If any of the provisioning commands fail in batch mode, the changes do not become active. The
PROV-CPY and PROV-DPLY commands fail, indicating that some of the provisioning commands in
the batch file have failed.
Purpose
mml -b path/filename.ext
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.
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 called DIAGLOG. For more information on using this command, refer to the Cisco
Media Gateway Controller Software Release 9 MML Command Reference Guide.
The DIAGLOG commands to start and stop can be placed at the beginning and end, respectively, of an
MML batch file.
All MML commands are automatically logged to the mml.log file located in the /opt/CiscoMGC/var/log
directory. A sample log file is shown below:
va-cerulean% more mml.log.4
Sat Jan 8 04:10:01:694 2001 | mml11 (PID 24954) <Info>
MML_INFO_COMMAND: MML Command
Sat Jan 8 04:10:06:218 2001 | mml11 (PID 24954) <Info>
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-34
OL-1110-23
Chapter 4
MML Basics
Working with Provisioning Commands
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
4-35
Chapter 4
MML Basics
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
4-36
OL-1110-23
CH A P T E R
This chapter describes how to add components, describes how to verify the addition of the components,
and gives tips that can help you solve problems. It includes the following sections:
Before starting an actual configuration, see Chapter 2, Planning for Provisioning for instructions and
worksheets for configuring your system. That chapter describes the system components that can be
configured on the Cisco PGW 2200 Softswitch. Each component has a specified type, name, and
description, and may have additional configuration parameters.
When adding components, add the components in the following order.
Add linksets
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-1
Chapter 5
This chapter also provides basic provisioning procedures for the following features on the
Cisco PGW 2200 Softswitch Release 9.7(3):
DPNSS Service Interworking with Cisco CallManager Over QSIG Tunneling, page 5-85
Enhanced Local Number Portability and Dial Plan Selection, page 5-96
SIP and ISUP Interworking for Call Hold and Terminal Portability, page 5-113
Note
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-2
OL-1110-23
Chapter 5
Step 1
Step 2
Start a provisioning session as described in theStarting a Provisioning Session section on page 4-6.
The source configuration that you chose during startup determines the configuration to which you can
add components.
Step 3
Where:
description is the long name assigned that can be as many as 128 alphanumeric characters in length.
name is the name you want to give to the component. The name can be as many as 20 characters
long and can contain numbers, letters, and the dash (-) symbol.
Note
For information on point code parameters, refer to Table 2-2 on page 2-14.
To add a destination point code to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD
command as follows:
Step 1
Use the following MML command to add the component and required parameters.
mml> prov-add:dpc:name="dpc1",netaddr="214.110.80",netind=2,desc="dpc1"
Step 2
Use the following MML command to add the component and required parameters.
mml> prov-add:dpc:name="dpc2",netaddr="214.110.90",netind=2,desc="Dest Switch 1"
Step 3
Tip
Point codes provide the addressing scheme for the SS7 network. ITU point codes are 14 bits long, and
ANSI point codes are 24 bits long.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-3
Chapter 5
Note
ITU point codes contain 14 bits and ANSI point codes contain 24 bits.
Use care when provisioning point codes since they are not checked in the provisioning session.
A maximum of 6 true OPCs can be supported per Cisco PGW 2200 Softswitch.
For each OPC added, you must specify a different local port number for each C7 IP link on the same
interface.
For each OPC added, you must create a duplicate DPC with a different name but with the same point
code.
When specifying a local port number, it must be greater than 1024 (for example, 7000).
Each OPC requires its own linkset (a linkset cannot be shared by 2 OPCs).
A maximum of 2 Session Manager sessions (1 active and 1 standby) can be supported per
Cisco PGW 2200 Softswitch (1 session per link).
A maximum of 192 links can be supported per Cisco PGW 2200 Softswitch.
A maximum of 4096 DS0s (CICs) can be supported per OPC-DPC pair for ITU or a maximum of
16, 384 DS0s (CICs) for ANSI.
To add another point code to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD
command as follows:
Step 1
Use the following MML command to add the component and required parameters.
mml> prov-add:opc:name="opc1",desc="OPC1",netaddr="1.2.1",netind=2,type="trueopc"
Step 2
Use the following MML command to add the component and required parameters.
mml> prov-add:opc:name="opc1a",desc="CAPOPC",netaddr="1.2.2",netind=2,type="capopc",
trueopc="opc1"
Step 3
Due to the number of commands involved to add an additional OPC, the commands have been included
in the following series of commands.
prov-sta::srcver="new",dstver="2lnks11"
prov-add:card:name="hme0",type="EN",slot=0,desc="Ethernet Card 1"
prov-add:enetif:name="enif1",desc="Ethernet Interface",card="hme0"
prov-add:card:name="hme1",type="EN",slot=1,desc="Ethernet Card 2"
prov-add:enetif:name="enif2",desc="Ethernet Interface",card="hme1"
prov-add:opc:name="opc1",netaddr="1.2.1",netind=2,desc="OPC1",type="trueopc"
prov-add:opc:name="opc1a",netaddr="1.2.2",netind=2,desc="OPC1",type="capopc",trueopc="opc1"
prov-add:dpc:name="dpc1",netaddr="2.2.2",netind=2,desc="DPC1"
prov-add:dpc:name="dpc2",netaddr="1.1.2",netind=2,desc="DPC2"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-4
OL-1110-23
Chapter 5
prov-add:dpc:name="apc1",netaddr="3.3.3",netind=2,desc="apc1"
prov-add:dpc:name="apc2",netaddr="3.3.2",netind=2,desc="apc2"
prov-add:ss7path:name="c7s-1",desc="C7 Service to
INET",mdo="ANSISS7_STANDARD",dpc="dpc1",custgrpid="1122",side="network",opc="opc1"
prov-add:ss7path:name="c7s-2",desc="C7 Service to
SIM",mdo="ANSISS7_STANDARD",dpc="dpc2",custgrpid="1122",side="network",opc="opc1"
prov-add:lnkset:name="ls-1",desc="Linkset 1",apc="dpc1",type="IP",proto="SS7-ANSI"
prov-add:lnkset:name="ls-2",desc="Linkset 2",apc="dpc2",type="IP",proto="SS7-ANSI"
prov-add:EXTNODE:NAME="va-2600-stim1",DESC="stim1-2600 SLT",TYPE="SLT"
prov-add:SESSIONSET:NAME="c7-2600-1",EXTNODE="va-2600-stim1",IPADDR1="IP_Addr1",PEERADDR1="192.0.2.5",PORT=70
00,PEERPORT=7000,NEXTHOP1="0.0.0.0",NETMASK1="255.255.255.0",TYPE="BSMV0"
prov-add:EXTNODE:NAME="va-2600-stim2",DESC="stim1-2600 SLT",TYPE="SLT"
prov-add:SESSIONSET:NAME="c7-2600-2",EXTNODE="va-2600-stim2",IPADDR1="IP_Addr1",PEERADDR1="192.0.2.6",PORT=70
00,PEERPORT=7000,NEXTHOP1="0.0.0.0",NETMASK1="255.255.255.0",TYPE="BSMV0"
prov-add:ss7route:name="r1",opc="opc1",dpc="dpc1",lnkset="ls-1",pri=1,desc="SS7 Route"
prov-add:ss7route:name="r2",opc="opc1",dpc="dpc2",lnkset="ls-2",pri=1,desc="SS7 Route"
prov-add:c7iplnk:name="ip-ch1",pri=1,slc=0,lnkset="ls-1",desc="INET SS7",timeslot=0,sessionset="c7-2600-1"
prov-add:c7iplnk:name="ip-ch2",pri=1,slc=1,lnkset="ls-1",desc="INET SS7",timeslot=1,sessionset="c7-2600-1"
prov-add:c7iplnk:name="ip-ch3",pri=1,slc=3,lnkset="ls-2",desc="SIM SS7",timeslot=0,sessionset="c7-2600-2"
prov-add:c7iplnk:name="ip-ch4",pri=1,slc=4,lnkset="ls-2",desc="SIM SS7",timeslot=1,sessionset="c7-2600-2"
prov-add:trnkgrp:name="1",svc="c7s-1",type="TDM_ISUP",selseq="MIDL",clli="trk-1"
prov-add:trnkgrp:name="2",svc="c7s-2",type="TDM_ISUP",selseq="MIDL",clli="trk-2"
prov-add:extnode:name="mgcp1",type="CAT8510",desc="SIM"
prov-add:mgcppath:name="mgcpsvc1",extnode="mgcp1",desc="MGCP to SIM"
prov-add:iplnk:name="mgcplk1",ipaddr="IP_Addr2",port=2427,pri=1,peeraddr="192.0.2.10",peerport=2427,svc="mgcp
svc1",desc="IP Link for MGCP"
prov-add:switchtrnk:name="01",trnkgrpnum="1",span="ffff",cic=1,cu="mgcp1",endpoint="s1/ds1-1/1@inet",spansize
=24
prov-add:switchtrnk:name="02",trnkgrpnum="2",span="ffff",cic=1,cu="mgcp1",endpoint="s1/ds1-2/1@sim",spansize=
24
prov-add:rttrnkgrp:name="1",type=1,reattempts=3,queuing=0,cutthrough=1
prov-add:rttrnk:name="rt1",trnkgrpnum=1
prov-add:rtlist:name="rtlist1",rtname="rt1"
prov-add:rttrnkgrp:name="2",type=1,reattempts=3,queuing=0,cutthrough=1
prov-add:rttrnk:name="rt2",trnkgrpnum=2
prov-add:rtlist:name="rtlist2",rtname="rt2"
prov-cpy
prov-stp
14-bit address
16-bit address
24-bit address
Each point code addressing type has unique formats that are used to provide a structure for the network,
where the lowest order bits in the address identify a particular signaling point, the highest order bits
identify the wider zone, and the bits in-between identify an area or network. For example, ANSI
SS7 uses 24-bit addresses with a format of 8-bits for each field (8-8-8).
Note
An exception to this is found in Japanese ISUP, in which the order is reversed (that is, the lowest order
bits identify the wider zone and the highest order bits identify a particular signaling point).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-5
Chapter 5
Note
Another exception is found in some National ITU SS7 variants, where there may be more or less than
three fields used in the point code format. However, the ordering concept for the bits (bits in lower order
fields are lower in the network hierarchy) still applies.
You can find more information about point code addressing and how it is handled in the
Cisco PGW 2200 Softswitch software in the following sections:
13
12
11
Zone
identification
3 bits
10 9
Area/network identification
8 bits
Signaling point
identification
3 bits
The decimal value of the maximum point code for an International 14-bit address is 7.255.7. The decimal
value of the maximum point code for a National 14-bit address varies. For a Singapore National point
code maximum value would be 63.15.15.
Note
When you provision an ITU point code on the Cisco PGW 2200 Softswitch, you must use the
International point code format. If the point code provided to you is in a National point code format,
convert the point code into International format using the procedure in Converting National Point Codes
To International Point Code Values section on page 5-6.
Convert the decimal value of the National point code into binary, using the associated point code format
as a reference.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-6
OL-1110-23
Chapter 5
If you do not know the format for a National point code, you must consult the recommendations
for that National SS7 variant.
Note
For example, if you wanted to convert a Singapore National point code of 54-3-3 to its binary value, you
would apply the Singapore National point code format, which is 6-4-4. This would result in a binary
value of 110110.0011.0011 or 11011000110011, with the National point code format removed.
Apply the International point code format to the binary number, and convert back to decimal.
Step 2
Staying with the above example, you would apply the International point code format, which is 3-8-3,
to the binary value 11011000110011, or 110.11000110.011. This would result in a decimal value of
6.198.3.
15
14
13
12
11
10
Zone identification
Area/network
(Main Number Area)
identification
(Sub Number Area) 5 bits
4 bits
The TTC recommendation (JT-Q704) uses the same terminology to describe the sub-fields as the ITU
Recommendation Q.704. The NTT recommendation (NTT-Q704-b) uses unique terms for these
sub-fields. The NTT names for these sub-fields appear in Figure 5-2 in parenthesis.
Note
Point codes in the Cisco PGW 2200 Softswitch software are all provisioned in the
zone.area/network.signaling point format. When you provision a point code for Japanese ISUP on the
Cisco PGW 2200 Softswitch, the order of the fields must be reversed to match that format. For example,
if you want to connect to a destination that uses Japanese ISUP with a point code of 78.9.20, you would
provision a DPC on the Cisco PGW 2200 Softswitch with a point code of 20.9.78. The
Cisco PGW 2200 Softswitch transmits the DPC address in the correct order (78.9.20).
The decimal value of the maximum point code for a 16-bit address is 127.15.31. However, since Japanese
point code values must be reversed when provisioned on the Cisco PGW 2200 Softswitch, the maximum
point code value you can provision is 31.15.127.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-7
Chapter 5
Figure 5-3
23
22 21 20 19 18 17 16 15 14 13 12 11 10 9
Zone identification
(Network Octet)
8 bits
Area/Network identification
(Cluster Octet)
8 bits
3 2
The Chinese GF001-9001 recommendation uses the same terminology to describe the sub-fields as the
ITU Recommendation Q.704. The ANSI T1.111.4 recommendation (uses unique terms for these
sub-fields. The ANSI names for these sub-fields appear in Figure 5-3 in parenthesis.
The decimal value of the maximum point code for a 24-bit address is 255.255.255.
Adding a Linkset
A linkset is the group of all signaling links between two point codes. Its MML name is LNKSET. For
information on linkset parameters, refer to Table 2-3 on page 2-15.
To add a linkset to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD command as
follows:
Step 1
Use the following MML command to add the component and required parameters.
mml> prov-add:lnkset:name="linkset1",desc="linkset 1 to STP-A",apc="STP-A",type="IP",
proto="SS7-ANSI"
Step 2
Use the following MML command to add the component and required parameters.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-8
OL-1110-23
Chapter 5
Step 3
Tip
Setting up linksets is a two-step process that consists of first adding the linkset and then adding links to
the linkset.
Use the following MML command to add the component and required parameters.
mml> prov-add:ss7subsys:name="mate1",svc="STPA",matedapc="STPB",proto="SS7-ANSI",pri=1,
desc="mate STPA to STPB"
Step 2
Use the following MML command to add the component and required parameters.
mml> prov-add:ss7subsys:name="mate2",svc="STPB",matedapc="STPA",proto="SS7-ANSI",pri=2,
desc="mate STPB to STPA"
Step 3
Use the PROV-RTRV command to verify the SS7 subsystem was added.
The following MML commands provide an example of other components to add when adding a mated
STP.
mml> prov-add:APC:NAME="STPA-5-83-230",DESC="STPA LA 5-83-230",NETADDR="5.83.230",NETIND=2
mml> prov-add:APC:NAME="STPB-5-83-231",DESC="STPB LA 5-83-231",NETADDR="5.83.231",NETIND=2
mml> prov-add:LNKSET:NAME="ls1",DESC="Linkset from STPA to pgw2200",APC="STPA-5-83-230",
PROTO="SS7-ANSI",TYPE="IP"
mml> prov-add:LNKSET:NAME="ls2",DESC="Linkset from STPB to pgw2200",APC="STPB-5-83-231",
PROTO="SS7-ANSI",TYPE="IP"
mml> prov-add:SS7ROUTE:NAME="ss7rte1-la",DESC="SS7 route set on ls1 to LA switch",
OPC="opc-itxc-la",DPC="dpc-la",LNKSET="ls1",PRI=1
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-9
Chapter 5
Tip
Protocol families must be the same for mated subsystems. If one pair of STPs handles both ITU and
ANSI variants, you must configure two pairs of STPs: one for ITU and the other for ANSI.
Use the following MML command to add the component and required parameters.
mml> prov-add:ss7subsys:name="LNP-1",svc="stpa",transproto="SCCP",proto="SS7-ANSI",pri=1,
ssn=231,desc="LNP231 for STP A"
Step 2
Use the following MML command to add the component and required parameters.
mml> prov-add:ss7subsys:name="AIN-1",svc="stpb",transproto="SCCP",proto="SS7-ANSI",pri=1,
ssn=241,desc="AIN8xx for STP B"
Step 3
Use the PROV-RTRV command to verify the subsystem number was added.
Use the following MML command to add the component and required parameters.
mml> prov-add:ss7route:name="rte1DPC1",opc="OPC",dpc="DestSW1PC",lnkset="linkset1",
pri=1,desc="route 1 to DestSW1 thru STP-A"
Step 2
Use the following MML command to add the component and required parameters.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-10
OL-1110-23
Chapter 5
mml> prov-add:ss7route:name="rte2DPC1",opc="OPC",dpc="DestSW1PC",lnkset="linkset2",
pri=1,desc="route 2 to DestSW1 thru STP-B"
Step 3
Tip
Use the PROV-RTRV command to verify the SS7 route was added.
Use the PROV-RTRV command to verify the SS7 signaling service was added.
Tip
Do not change the default values for CUSTGRPID and CUSTGRTBL; they are used for DPNSS feature
transparency.
CUSTGRPID also associates variants and dial plans. Use the RTRV-VARIANTS command to see valid
variants.
Note
Use the PROV-RTRV command to verify the FAS path was added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-11
Chapter 5
Note
Step 1
Use the following MML command to add the component and required parameters.
mml> prov-add:card:name="Ethernet1",type="EN",slot=0,desc="Ethernet Card 1"
Step 2
Use the following MML command to add the component and required parameters.
mml> prov-add:card:name="Ethernet2",type="EN",slot=1,desc="Ethernet Card 2"
Step 3
Tip
Use the PROV-RTRV command to verify the card component was added.
You must configure the adapter card before you configure its corresponding interface.
Note
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-12
OL-1110-23
Chapter 5
Step 1
Use the following MML command to add the component and required parameters.
mml> prov-add:enetif:name="EtherIF1",desc="Ethernet IF 1",card="Ethernet1"
Step 2
Use the following MML command to add the component and required parameters.
mml> prov-add:enetif:name="EtherIF2",desc="Ethernet IF 2",card="Ethernet2"
Step 3
Tip
Use the PROV-RTRV command to verify the Ethernet interface was added.
Adding a C7 IP Link
A C7 IP link component identifies a link between a Cisco ITP-L IP address and port and the SS7 network
(SSP or STP). Its MML name is C7IPLNK. For information on C7 IP link parameters, refer to Table 2-12
on page 2-33.
Tip
Tip
When expanding a network past 32 links, spreading the links evenly across the ports is recommended to
prevent service interruption.
Tip
Use this component only when the Cisco PGW 2200 Softswitch uses Cisco ITP-Ls to communicate SS7
messages over IP.
Note
Provision the ITP-L as an external node, then provision your sessionsets before adding the C7 IP links.
To add a C7 IP link to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD command as
follows:
mml> prov-add:c7iplnk:name="lkset1SLC0",desc="SS7ANSI",sessionset=slt1,
lnkset="linkset1",slc=0,pri=1,timeslot=0
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-13
Chapter 5
Note
TDMIF is not supported in software Release 9.4(1) and later software revisions.
To add a TDM interface to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD
command as follows:
mml> prov-add:tdmif:name="card1lif1",desc="V35 LIF 1",card="card1",lifnum=2,
sigtype="V.35",datarate=64
Use the PROV-RTRV command to verify the TDM card was added.
Table 5-1 shows typical parameters based on card type.
Table 5-1
TDM Interfaces
DTEDCE
Format/
Line Coding Framing
75
NA
B8ZS
ESF
T1
IHDLC
120
NA
HDB3
CRC4
CEPT
IHDLC
DTE
NA
NA
V.35
DEFAULT
Card Type
LIFNUM
RESIST
ITK (T1)
ITK (E1)
V.35
Data Rate/
Clock
64/EXT
Note
Use the PROV-RTRV command to verify the TDM link was added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-14
OL-1110-23
Chapter 5
Use the PROV-RTRV command to verify the external node has been added.
Tip
Adding a Card
The card being referred to is a network card or adapter that is operating in the
Cisco PGW 2200 Softswitch. Its MML name is CARD.
Note
CARD is not provisionable in software Release 9.4(1) and later software revisions.
To add an adapter card to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD command
as follows:
mml> prov-add:card:name="home1",type="EN",slot=0,desc="MGC1 Ethernet card"
Use the PROV-RTRV command to verify the Ethernet card was added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-15
Chapter 5
Note
In the Cisco PGW 2200 Softswitch, the same cards and interfaces can be used for communication with
Cisco ITP-Ls and media gateways. When configured this way, separate links are assigned for
Cisco ITP-L and media gateway communications.
Note
ENETIF is not supported in software Release 9.4(1) and later software revisions.
To add an adapter card to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD command
as follows:
mml> prov-add:enetif:name="en1",desc="MGC1 Ethernet card1",card="home1"
Use the PROV-RTRV command to verify the Ethernet card was added.
Use the PROV-RTRV command to verify the EISUP signaling service was added.
Note
To ensure correct failover operation in a configuration with two local MGCs (one active and one standby)
and a remote Cisco PGW 2200 Softswitch, you need a minimum of two E-ISUP links from the remote
Cisco PGW 2200 Softswitch to each Cisco PGW 2200 Softswitch redundant pair.
Use the PROV-RTRV command to verify the IPFAS transport service was added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-16
OL-1110-23
Chapter 5
To add an MGCP signaling link to the media gateway configuration, use the PROV-ADD command as
follows:
mml> prov-add:mgcppath:name="mgcpsrv1",extnode="cu1",desc="MGCP Service to CU 1"
Use the PROV-RTRV command to verify the MGCP signaling service was added.
Use the PROV-RTRV command to verify the MGCP signaling service was changed.
Note
If you are configuring a redundant system, you must define two redundant link manager links between
each Cisco PGW 2200 Softswitch and media gateway. Each redundant link manager group must be
associated with a different port number and a different NASPATH, but the same EXTNODE.
To add a NAS signaling service to the media gateway configuration, use the PROV-ADD command as
follows:
mml> prov-add:naspath:name="nassrv1",extnod="nas1",desc="Service to
NAS1",mdo="BELL_1268_C3"
Use the PROV-RTRV command to verify the NAS signaling service was added.
Tip
For the NASPATH component, there is only one protocol: Bell_1268_C2 (for software Revision 9.3(2)
or Bell_1268_C3 for earlier software revisions.
Adding an IP Link
The IP link is an IP connection between an Cisco PGW 2200 Softswitchs Ethernet interface and an
media gateway. Its MML name is IPLNK. For information on IP link parameters, refer to Table 2-18 on
page 2-41.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-17
Chapter 5
To add an IP link to the media gateway configuration, use the PROV-ADD command as follows:
mml> prov-add:iplnk:name="Iplink1",if="en-1lif1",ipaddr="IP_Addr1",port=3001,
peeraddr="192.12.214.10",peerport=3001,svc="nassvc1",desc="IP link for NAS service to
NAS1"
Tip
When configuring two IP links to the same NAS, you need to configure two different Ethernet IP
addresses on both the Cisco PGW 2200 Softswitch and the NAS.
SESSIONSETs that share a peer address (that is, PEERADDR, PEERADDR1, or PEERADDR2)
must be assigned directly or indirectly to the same external node.
The PORT attribute cannot be set to the same value as the PORT attribute of another SESSIONSET
with a different TYPE value.
If IPADDR2 or PEERADDR2 is specified then they must both be specified. You cannot have one
local address and two remote addresses, or two local addresses and one remote address.
Another SESSIONSET with a different EXTNODE cannot use the resolved value of PEERADDR1
or PEERADDR2.
When an IP Route is specified in a link object for SESSIONSET, the IPADDR must match the
IPADDR of the link. And when an IP Route is specified in a link object for SESSIONSET, the IP
address resolved from the PEERADDR attribute must be the same as the DESTINATION and
NETMASK attributes to verify the IPROUTE is valid.
Use the PROV-RTRV command to verify the session set was added. Keep in mind that although
IPADDR1 and PEERADDR1 are specified in the provisioning command, the 1 is not included in the
retrieved response.
MGC1 mml> prov-rtrv:sessionset:name="c7-2600-1"
MGC-01 - Media Gateway Controller 2002-09-26 07:24:05.845 EST
M RTRV
"session=wags2:sessionset"
/*
NAME = c7-2600-1-1
DESC = Session Set c7-2600-1 Backhaul Link 1
EXTNODE = va-2600-stim1
IPADDR = IP_Addr1
PORT = 7000
PEERADDR = 192.0.2.11
PEERPORT = 7000
NEXTHOP = 0.0.0.0
NETMASK = 255.255.255.255
TYPE = BSMV0
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-18
OL-1110-23
Chapter 5
Adding D-channels
To configure two D-channels from the Cisco PGW 2200 Softswitch to a Cisco MGX8850, MGX 8880,
or AS5xxx, you can provision two D-channels and designate one D-channel as the primary and the other
D-channel as the secondary.
For a Primary Rate Interface (PRI) with a Facility Associated Signaling (FAS) that uses only one
D-channel for each T1/E1 interface, the single D-channel becomes a single point of failure. By
provisioning a backup D-channel, the single point of failure is removed and allows a D-channel on one
PRI interface to carry signaling for the B-channels on the other PRI interfaces, which allows all the
channels on the other PRI interfaces to be used as B-channels.
When provisioning D-channels keep the following in mind:
Note
A session set cannot span channel controllers. Therefore all the D-channels assigned to a session set
must be on one channel controller.
Create the external node, IPFAS signaling path, and session set before adding the D-channels.
To add two back up D-channels to the media gateway configuration, use the PROV-ADD command as
follows:
Step 1
With an open provisioning session, use the following MML command to add an two D-channels to the
PGW 2200.
prov-add:DCHAN:NAME="dchan1a-207-3",DESC="Primary DCHAN for
PRI-Svc1",SVC="prisvc1",PRI=1,SESSIONSET="sset-207-3",SIGSLOT=0,SIGPORT=1,SUBUNIT=0
Step 2
Use the following MML command to provision the secondary (backup) D-channel for IPFASPATH
service with the second D-channel having a priority of 2, and using line 2 of the VXSM on slot 3.
Note
Use the PROV-RTRV command to verify the D-channels were added. Use the following MML
command to retrieve all provisioned D-channels:
prov-rtrv:dchan:"all"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-19
Chapter 5
Refer to the documentation for your voice gateway for more information.
Note
If your network supports both PRI and BRI backhaul signaling, we recommend that you maintain the
PRI and BRI interfaces on different media gateways. PRI signaling backhaul configurations typically use
redundant links between the Cisco PGW 2200 Softswitch and the media gateway, and BRI signaling
backhaul configurations use a single link between the Cisco PGW 2200 Softswitch and the media
gateway.
If you decide to configure PRI and BRI signaling backhaul on the same media gateway, we recommend
that you use a single link between the media gateway and the Cisco PGW 2200 Softswitch. If you do not
remove a link from your PRI signaling backhaul provisioning, and one of those links should fail and be
restored, you will need to set the service state of the related MGCP signaling service to OOS, and then
set it to IS to restore both links to full functioning.
Perform the following steps to add an ISDN BRI backhaul connection.
Step 1
Step 2
Enter the following command to add a Cisco BRI voice gateway external node named va-3640-01:
mml>prov-add:extnode:name="va-3640-01",desc="BRI 3640",type="C3640",isdnsigtype=na
Step 3
Repeat Step 2 for each Cisco BRI voice gateway external node you want to add to your provisioning data.
Step 4
Enter the following command to add an ISDN BRI signaling service named brisvc1.
mml>prov-add:bripath:name="brisvc1",extnode="bri-3640-01",desc="BRI service to C2600",
mdo="ETS_300_172",side="network",custgrpid="V123",crlen=2
Note
Step 5
Enter the following command to add a backhaul TCP link named britcp1.
mml>prov-add:tcplink:NAME="britcp1",DESC="BRI TCP link 1",TYPE="BRI",IPADDR="IP_Addr1",
PORT="1024",PEERADDR="192.0.2.12",PEERPORT="1024",extnode=va-3640-01,IPROUTE="iprte1"
Step 6
Repeat Step 5 for each Backhaul TCP link you want to add to your provisioning data.
Step 7
Enter the following command to add an ISDN BRI D-channel named bridchan1.
mml>prov-add:dchan:NAME="bridchan1",DESC="ISDN BRI D channel 1",SVC="BRI",PRI="1",
TCPLINK="britcp1",sigslot="4",sigport="1",subunit="1"
Note
Set the sigslot parameter to 0 for ISDN BRI D-channels when the associated external node is a C17xx.
If there are no other components that you need to provision, end your provisioning session.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-20
OL-1110-23
Chapter 5
Note
Caution
Step 1
Do not modify the other XECfgParm.dat parameters associated with this feature.
Log in to the standby Cisco PGW 2200 Softswitch as root and change directories to the etc subdirectory
by entering the following UNIX command:
cd /opt/CiscoMGC/etc
Step 2
Step 3
Search for the *.IP_NextHop1 parameter and enter the IP address of your first next hop destination.
Note
The IP address should be expressed in dotted decimal notation (for example, 192.0.2.2).
Step 4
Repeat Step 3 for every next hop destination (*.IP_NextHop2, *.IP_NextHop3, and so forth) that you
want to identify. You can specify up to eight next hop IP addresses.
Step 5
Step 6
Manually stop the Cisco PGW 2200 Softswitch software on the standby Cisco PGW 2200 Softswitch by
entering the following UNIX command:
/etc/init.d/CiscoMGC stop
Step 7
Once the software shutdown is complete, manually start the Cisco PGW 2200 Softswitch software on
the standby Cisco PGW 2200 Softswitch by entering the following command:
/etc/init.d/CiscoMGC start
Step 8
Log in to the active Cisco PGW 2200 Softswitch, start an MML provisioning session, and enter the
following command:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-21
Chapter 5
mml> sw-over::confirm
Site alarms are automatically set until the out-of-service (OOS) Cisco PGW 2200 Softswitch host is
returned to an in-service (IS) state.
Step 9
Repeat steps 2 through 8 for the newly standby Cisco PGW 2200 Softswitch host.
Step 2
Enter the following MML command to add a Cisco access server external node named va-5400-36.
mml> prov-add:extnode:name="va-5400-36",desc="AS5400",type="AS5400",isdnsigtype="iua"
Step 3
Repeat Step 2 for each Cisco access server external node you want to add to your provisioning data.
Step 4
If there are no other components that you need to provision, save your changes and end your provisioning
session.
Otherwise, proceed to Adding NAS Signaling Services.
Step 2
Enter the following MML command to add a NAS signaling service named nassvc1.
mml> prov-add:naspath:NAME="nassvc1",DESC="IUA NAS path",extnode="va-5400-37",sigport=45,
sigslot=10
Step 3
Repeat Step 2 for each NAS signaling service you want to add to your provisioning data.
Step 4
If there are no other components that you need to provision, save your changes and end your provisioning
session.
Otherwise, you may:
Proceed to Adding IP Routes (Optional) if your Cisco PGW 2200 is on a different subnet from the
associated access server; or
Proceed to the Adding SCTP Associations, page 5-25 if your Cisco PGW 2200 is on the same subnet
as the associated access server.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-22
OL-1110-23
Chapter 5
Step 1
Step 2
Step 3
Repeat Step 2 for each IP route you want to add to your provisioning data.
Step 4
If there are no other components that you need to provision, save your changes and end your provisioning
session.
Otherwise, proceed to Adding SCTP Associations.
Step 2
Note
The parameters listed above are those required for the creation of an SCTP association for an
IUA interface. For a complete list of parameters for this component, refer to the Association
section on page A-3.
Step 3
Repeat Step 2 for each SCTP association you want to add to your provisioning data.
Step 4
If there are no other components that you need to provision, save your changes and end your provisioning
session.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-23
Chapter 5
Note
Caution
Step 1
Do not modify the other XECfgParm.dat parameters associated with this feature.
Log in to the standby Cisco PGW 2200 Softswitch as root and change directories to the etc subdirectory
by entering the following UNIX command:
cd /opt/CiscoMGC/etc
Step 2
Step 3
Search for the *.IP_NextHop1 parameter and enter the IP address of your first next hop destination.
Note
The IP address should be expressed in dotted decimal notation (for example, 192.0.2.2).
Step 4
Repeat Step 3 for every next hop destination (*.IP_NextHop2, *.IP_NextHop3, and so forth) that you
want to identify. You can specify up to eight next hop IP addresses.
Step 5
Step 6
Manually stop the Cisco PGW 2200 Softswitch software on the standby Cisco PGW 2200 Softswitch by
entering the following UNIX command:
/etc/init.d/CiscoMGC stop
Step 7
Once the software shutdown is complete, manually start the Cisco PGW 2200 Softswitch software on
the standby Cisco PGW 2200 Softswitch by entering the following command:
/etc/init.d/CiscoMGC start
Step 8
Log in to the active Cisco PGW 2200 Softswitch, start an MML provisioning session, and enter the
following command:
mml> sw-over::confirm
Site alarms are automatically set until the out-of-service (OOS) Cisco PGW 2200 Softswitch host is
returned to an in-service (IS) state.
Step 9
Repeat steps 2 through 8 for the newly standby Cisco PGW 2200 Softswitch host.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-24
OL-1110-23
Chapter 5
Step 1
Step 2
Enter the following MML command to add a Cisco access server external node named va-5400-36.
mml> prov-add:extnode:name="va-5400-36",desc="AS5400",type="AS5400",isdnsigtype="iua"
Step 3
Repeat Step 2 for each Cisco access server external node you want to add to your provisioning data.
Step 4
If there are no other components that you need to provision, save your changes and end your provisioning
session.
Otherwise, proceed to Adding NAS Signaling Services.
Step 2
Step 3
Repeat Step 2 for each IP route you want to add to your provisioning data.
Step 4
If there are no other components that you need to provision, save your changes and end your provisioning
session.
Otherwise, proceed to Adding SCTP Associations.
Step 2
Note
The parameters listed above are those required for the creation of an SCTP association for an
IUA interface. For a complete list of parameters for this component, refer to the Association
section on page A-3.
Step 3
Repeat Step 2 for each SCTP association you want to add to your provisioning data.
Step 4
If there are no other components that you need to provision, save your changes and end your provisioning
session.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-25
Chapter 5
Step 2
Enter the following MML command to add a DPNSS signaling service named dpnsvc1.
mml> prov-add:dpnssspath:NAME="dpnsssvc1",DESC="IUA DPNSS path",extnode="va-3660-20",
sigport=45,sigslot=10
Step 3
Repeat Step 2 for each DPNSS signaling service you want to add to your provisioning data.
Step 4
If there are no other components that you need to provision, save your changes and end your provisioning
session.
prov-add:sigsvcprop:name="dpnsssv1",InhibitIncomingCallingNameDisplay="1"
prov-add:trnkgrpprop:name="2222",InhibitIncomingCallingNameDisplay="1"
prov-add:sigsvcprop:name="dpnsssv1",InhibitOutgoingCallingNameDisplay="1"
prov-add:trnkgrpprop:name="2222", nhibitOutgoingCallingNameDisplay="1"
prov-add:sigsvcprop:name="dpnsssvc2",LoopAvoidanceCounter="3"
prov-add:trnkgrpprop:name="3333",LoopAvoidanceCounter="3"
prov-add:sigsvcprop:name="dpnsssvc2",LoopAvoidanceSupport="1"
prov-add:trnkgrpprop:name="3333",LoopAvoidanceSupport="1"
prov-add:sigsvcprop:name="dpnsssvc2",MwiStringON="*58*AN*0#"
prov-add:sigsvcprop:name="dpnsssvc2",MwiStringOFF="*58*AN*1#"
mml> numan-add:digmodstring:custgrpid="1111",name="mwion",digstring="4085556666"
mml> numan-add:digmodstring:custgrpid="1111",name="mwioff",digstring="4085556667"
mml> numan-add:resulttable:custgrpid="1111",name="rtab1t49",resulttype="BNBRMODMWI",
dw1="mwion",dw2="mwioff",setname="rset1"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-26
OL-1110-23
Chapter 5
Adding Files
The FILES component consists of customer-specific flat files that you can use to provision trunk groups,
trunk routes, trunks, and dial plans. The MML name is FILES. For information on file parameters, refer
to the Provisioning Trunk Groups and Trunks section on page 2-50.
To add a file to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD command as
follows:
mml> prov-add:files:name="BCFile",file="trunkCust.dat",action="import"
Note
When you are importing screening files, for example AWhite list or BBlack list, the import file name
must be one of the following: <custGrpId>.awhite, <custGrpId>.bwhite, <custGrpId>.ablack, or
<custGrpId>.bblack.
Use the PROV-RTRV command to verify the flat file was added.
Use the PROV-RTRV command to verify the nailed trunk was added.
Tip
Use the FILES component with flat files to provision trunks; use the NAILEDTRNK component with an
individual trunk.
Use the PROV-RTRV command to verify the trunk group was added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-27
Chapter 5
Routing
This section is used to configure the routing file. Three components are necessary to configure routing.
Their MML names are RTTRNKGRP, RTTRNK, and RTLIST.
Tip
The examples listed below illustrate the syntax and sequence of these commands. For detailed
descriptions of the individual command parameters, and additional guidance on using these commands,
see the Route Analysis section on page 2-87, including Table 2-32, Table 2-33, and Table 2-34.
To add routing files to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD commands
as follows:
Step 1
Use the following MML command to add the component and required parameters.
mml> prov-add:rttrnkgrp:name="501",type=7,reattempts=1,queuing=0,cutthrough=2
Step 2
Use the following MML command to add the component and required parameters.
mml> prov-add:rttrnk:name="rt513",trnkgrpnum=513
Step 3
Use the following MML command to add the component and required parameters.
mml> prov-add:rtlist:name="rtlist501",rtname="rt501"
Step 4
Tip
Use the PROV-RTRV command to verify the routing files were added.
All the route lists, route trunks, and route trunk groups information can be retrieved by using the
prov-rtrv:rtlist:all command. The all option cannot be used with other parameters.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-28
OL-1110-23
Chapter 5
When calculating the percentage of idle circuits and the percentage of the busy circuit, all circuits that
are available for call processing are used as the 100% base. The circuits that are available for call
processing are the circuits in service and not blocked. Circuits that are blocked (local, remote, or
gateway) or not in service are not considered.
For example, if there are 25 blocked circuits, 40 idle circuits, and 60 circuits with calls in progress
(includes both incoming and outgoing), the total configured circuit is 125 in the trunk group, and the
circuit available for call processing is 100. Therefore the percentage of the idle circuit is 40% (since 25
circuits are blocked and therefore not counted) and the percentage of the busy circuit is 60%. If the
ResIncPerc property configured against the trunk group is 30%, no outgoing circuit is selected if the
percentage of the idle circuit is less than 30%. When the percentage of the idle circuit is equal to or more
than 30%, new outgoing calls are allowed for the trunk group.
You can reserve a percentage of the available circuits (in service and not blocked) for incoming calls
only when the number of idle and available circuits is equal to or below the reserved incoming
percentage. If the ResIncPerc is set higher (that is reserving more incoming trunk groups), no calls are
dropped to increase the current number of idle circuits, but no new outgoing calls are placed on the trunk
group until the number of idle circuits drops below the new reserved incoming percentage value.
If alternative routing trunk groups are specified, the call is routed using the alternative trunk group if the
number of idle circuits is less than the configured ResIncPerc threshold. However, if no alternative
routing trunk group is specified, the call is dropped.
The range for this property is from 0 to 100%. The property value is saved during the routing data
commit. The following MML command example sets the percentage of trunks in the routing trunk group
that are reserved for incoming calls to 65%, if the trunk group name was 1000.
mml> prov-add:rttrnkgrp:name="1000",type="0",reattempts="5",queuing="1",cutthrough="1",
resincperc="65"
Use the following MML command to add the component and required parameters.
mml> prov-add:bearercap:name="bearer1",bearercap="12;05;31"
Step 2
Use the following MML command to add the component and required parameters.
mml> prov-add:siprttrnkgrp:name="2222",url="128.107.132.143",srvrr=0,sipproxyport=5060,
version="2.0",cutthrough=1,extsupport=1,bearercapname="bearer1"
Step 3
Use the following MML command to add the component and required parameters.
mml> prov-add:rrttrnkgrp:name="1",type=1,reattempts=3,queuing=0,cutthrough=1,
bearercapname="bearer1"
Step 4
Use the PROV-RTRV command to verify the bearer capability file was modified.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-29
Chapter 5
Note
The inserted route or trnkgrp appears before the next trunk group name.
The following MML command examples show a route defined with four trunk groups.
mgc4 mml> prov-rtrv:rttrnk:name="routea"
MGC-01 - Media Gateway Controller 2002-02-23 01:16:43.381 GMT
M RTRV
"session=nexttrnkgrp:rttrnk"
/*
routeName
--------routea
trunkGroup
---------2000
3000
4000
5000
nextTrunkGroup
-------------3000
4000
5000
*/
=======================================
If you discover you are required to change the trunk group order (that is, trunk group 5000 is the best
value), start a provisioning session and perform the following MML commands.
mgc4 mml> prov-ed:rttrnk:name="routea",trnkgrpnum=5000,nexttrkgrp=2000
MGC-01 - Media Gateway Controller 2002-02-23 01:17:00.944 GMT
M COMPLD
"rttrnk"
;
mgc4 mml> prov-rtrv:rttrnk:name="routea"
MGC-01 - Media Gateway Controller 2002-02-23 01:17:03.039 GMT
M RTRV
"session=nexttrnkgrp:rttrnk"
/*
routeName
--------routea
trunkGroup
---------5000
2000
3000
4000
nextTrunkGroup
-------------2000
3000
4000
*/
As a result of executing the previous MML commands, trunk group 5000 is now first. Commit the
provisioning MML changes by performing the prov-cpy/dply sequence.
If you discover that you now need to remove trunk group 3000 entire from the list, start a provisioning
session and perform the following MML commands.
mgc4 mml> prov-dlt:rttrnk:name="routea",trnkgrpnum=3000
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-30
OL-1110-23
Chapter 5
trunkGroup
---------5000
2000
4000
nextTrunkGroup
-------------2000
4000
*/
As a result of performing the preceding MML commands, trunk group 3000 no longer in the list. Commit
the provisioning MML changes by performing the prov-cpy/dply sequence.
However, if you discover you want to add in trunk group 3000 again, open a provisioning session and
perform the following MML commands.
Note
nextTrunkGroup
-------------2000
4000
3000
*/
;
mgc4 mml>
===================================================================
If, after adding trunk group 3000, you want to make it the primary choice trunk group, open a
provisioning session and perform the following MML commands.
mgc4 mml> prov-ed:rttrnk:name="routea",trnkgrpnum=3000,nexttrkgrp=5000
MGC-01 - Media Gateway Controller 2002-02-23 01:47:24.965 GMT
M COMPLD
"rttrnk"
;
mgc4 mml> prov-rtrv:rttrnk:name="routea"
MGC-01 - Media Gateway Controller 2002-02-23 01:47:26.551 GMT
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-31
Chapter 5
RTRV
"session=nexttrnkgrp:rttrnk"
/*
routeName
--------routea
trunkGroup
---------3000
5000
2000
4000
nextTrunkGroup
-------------5000
2000
4000
*/
;
mgc4 mml>
Use the PROV-RTRV command to verify the specified trunk group property has been overridden.
Note
The 32-digit functionality does not apply to the protocol variants of the Q.721 protocol, since these
protocols have a 4-bit field for the number (length) of the address signals contained in each parameter,
thus it is not possible to have any parameter with more than 16 digits.
Note
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-32
OL-1110-23
Chapter 5
Table 5-2
Protocol Family
Parameters
32 Digits Support
Overdecadic
Digits Support
Yes
Yes
Yes
Yes
Carrier Identification
No (3 or 4 digits)
No (see Note 1)
Charge Number
Yes
Yes
Generic Address
Yes
Yes
Jurisdiction Information
No (6 digits)
No
Yes
Yes
No (6 digits)
No
Redirecting Number
Yes
Yes
Redirection Number
Yes
Yes
No (3 or 4 digits)
No (see Note 1)
No (see Note 2)
Yes
No (see Note 2)
Yes
No (see Note 2)
Yes
No (see Note 2)
Yes
No (see Note 2)
Yes
No (1 digit)
Yes
No (see Note 2)
No
Yes
Yes
Yes
Yes
No (3 or 4 digits)
Yes
Yes
Yes
ANSI
Q.721
Q.761
Note 1: The overdecadic support for the listed parameters was introduced previously in software
Release 9. Overdecadic support only applies when the Cisco PGW 2200 Softswitch (configured for
Signaling Mode) receives an SS7 call and terminates to the Network Access Server (NAS) gateway or
vice versa; and does not apply to an SS7-to-SS7 call, which does not support overdecadic digits.
Note 2: There is a 4-bit length field associated with the number of address signals (digits) within the
bit string of the parameter, thus not making it possible to have more than 16 digits.
Parameters marked with an (*), are only specific to the protocol variants that appear in parenthesis
meaning that the base variant of the protocol family does not support the parameter. The Japanese ISUP
consists of the NTT, TOKYO, JAPAN, and JAPAN_JT protocol variants.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-33
Chapter 5
Table 5-2
Protocol Family
Parameters
32 Digits Support
Overdecadic
Digits Support
Connected Number
Yes
Yes
Yes
Yes
Generic Number
Yes
Yes
Yes
Location Number
Yes
Yes
Yes
Yes
Yes
Yes
Redirecting Number
Yes
Yes
Redirection Number
Yes
Yes
Subsequent Number
Yes
Yes
No (3 or 4 digits)
Yes
Yes
Yes
Yes
Yes
Connected Number
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Q.767
Note 1: The overdecadic support for the listed parameters was introduced previously in software
Release 9. Overdecadic support only applies when the Cisco PGW 2200 Softswitch (configured for
Signaling Mode) receives an SS7 call and terminates to the Network Access Server (NAS) gateway or
vice versa; and does not apply to an SS7-to-SS7 call, which does not support overdecadic digits.
Note 2: There is a 4-bit length field associated with the number of address signals (digits) within the
bit string of the parameter, thus not making it possible to have more than 16 digits.
Parameters marked with an (*), are only specific to the protocol variants that appear in parenthesis
meaning that the base variant of the protocol family does not support the parameter. The Japanese ISUP
consists of the NTT, TOKYO, JAPAN, and JAPAN_JT protocol variants.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-34
OL-1110-23
Chapter 5
Table 5-2
Protocol Family
Parameters
32 Digits Support
Overdecadic
Digits Support
Subsequent Number
Yes
Yes
No (3 or 4 digits)
Yes
Note 1: The overdecadic support for the listed parameters was introduced previously in software
Release 9. Overdecadic support only applies when the Cisco PGW 2200 Softswitch (configured for
Signaling Mode) receives an SS7 call and terminates to the Network Access Server (NAS) gateway or
vice versa; and does not apply to an SS7-to-SS7 call, which does not support overdecadic digits.
Note 2: There is a 4-bit length field associated with the number of address signals (digits) within the
bit string of the parameter, thus not making it possible to have more than 16 digits.
Parameters marked with an (*), are only specific to the protocol variants that appear in parenthesis
meaning that the base variant of the protocol family does not support the parameter. The Japanese ISUP
consists of the NTT, TOKYO, JAPAN, and JAPAN_JT protocol variants.
To support up to 32 digits and overdecadic digits (A through F) in called and calling numbers across all
supported protocols, set the TMaxDigits property (set on the sigpath) as follows:
mml> prov-add:sigsvcprop="ss7svc1",TMaxDigits="32"
Note
Provisioning the Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14
Mapping Feature
With a provisioning session active, perform the following steps to provision the Generic LNP Protocol
Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping Feature.
Step 1
Assuming the 32-digit overdecadic feature is disabled, dynamically change the OD32DigitSupport
property for 32-digit and overdecadic support.
mml> prov-add:trnkgrpprop:name="1000",OD32DigitSupport="1"
Note
Step 2
Setting the value of the OD32DigitSupport property to 0 disables overdecadic 32 digit support. The
default property value is 1 (enabled).
A response similar to the following is returned:
Media Gateway Controller - MGC-03 2003-02-17 14:25:56
M COMPLD
"trnkgrp"
Step 3
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-35
Chapter 5
Verifying the Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping
Feature
After you have provisioned the Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and
Cause 14 Mapping Feature, perform the following steps to verify its setting.
Step 1
With an provisioning session active, use prov-rtrv:trnkgrpprop:name=1000 to verify the trunk group
property is correctly provisioned.
mml> prov-rtrv:trnkgrpprop:name="1000"
Step 2
OD32DigitSupport = 1
*/
;
Step 2
Enable the SUBSCRIBE/NOTIFY methods on a SIP trunk group with the following command:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-36
OL-1110-23
Chapter 5
mml> prov-ed:trnkgrpprop:name="trnkgrpnum",custgrpid="grpid",SubscribeNotifySupport=1
For example, to enable the SUBSCRIBE/NOTIFY methods on a SIP trunk group called 3333, you would
enter the following command:
mml> prov-ed:trnkgrpprop:name="3333",custgrpid="1111",SubscribeNotifySupport=1
Step 3
If there are no other components that you need to provision, end your provisioning session.
Step 2
Disable the SUBSCRIBE/NOTIFY methods on a SIP trunk group with the following command:
mml> prov-ed:trnkgrpprop:name="trnkgrpnum",custgrpid="grpid",SubscribeNotifySupport=0
For example, to disable the SUBSCRIBE/NOTIFY methods on a SIP trunk group called 3333, you would
enter the following command:
mml> prov-ed:trnkgrpprop:name="3333",custgrpid="1111",SubscribeNotifySupport=0
Step 3
If there are no other components that you need to provision, end your provisioning session.
Step 2
Enable unsolicited notifications on a SIP trunk group using the following command:
mml> prov-ed:trnkgrpprop:name="trnkgrpnum",custgrpid="grpid",UnsolicitedNotifyMethod=1
For example, to enable unsolicited notifications on a SIP trunk group called 3333, you would enter the
following command:
mml> prov-ed:trnkgrpprop:name="3333",custgrpid="1111",UnsolicitedNotifyMethod=1
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-37
Chapter 5
Step 3
If there are no other components that you need to provision, end your provisioning session.
Step 2
Disable unsolicited notifications on a SIP trunk group using the following command:
mml> prov-ed:trnkgrpprop:name="trnkgrpnum",custgrpid="grpid",UnsolicitedNotifyMethod=0
For example, to disable unsolicited notifications on a SIP trunk group called 3333, you would enter the
following command:
mml> prov-ed:trnkgrpprop:name="3333",custgrpid="1111",UnsolicitedNotifyMethod=0
Step 3
If there are no other components that you need to provision, end your provisioning session.
Step 2
For example, to provision a telephony event to last a minimum of 200 ms on a SIP trunk group called
3333, you would enter the following command:
mml> prov-ed:trnkgrpprop:name="3333",custgrpid="1111",MinEventSubscribeDuration=200
Step 3
If there are no other components that you need to provision, end your provisioning session.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-38
OL-1110-23
Chapter 5
Step 2
Set the maximum duration time for a subscription on a SIP trunk group:
mml> prov-ed:trnkgrpprop:name="trnkgrpnum",custgrpid="grpid",
MaxSubscriptionDuration=maxsub
For example, to provision a subscription to last a maximum of 3600 seconds on a SIP trunk group called
3333, you would enter the following command:
mml> prov-ed:trnkgrpprop:name="3333",custgrpid="1111",MaxSubscriptionDuration=3600
Step 3
If there are no other components that you need to provision, end your provisioning session.
Step 2
Step 3
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-39
Chapter 5
Step 2
Step 3
Table 5-3
Trunk Group
Number
Trunk Group
Member
Span
CIC
Endpoint
CLI
1000
ffff
25
S0/DS1-1/7@li-5300-3
gw1
1000
ffff
26
S0/DS1-1/8@li-5300-3
gw1
1000
ffff
27
S0/DS1-1/9@li-5300-3
gw1
1000
ffff
28
S0/DS1-1/10@li-5300-3
gw1
1000
ffff
29
S0/DS1-1/11@li-5300-3
gw1
1000
ffff
30
S0/DS1-1/12@li-5300-3
gw1
Use the PROV-RTRV command to verify the switched trunks were added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-40
OL-1110-23
Chapter 5
The previous command added the six nailed trunks shown in Table 5-4.
Table 5-4
Name
SRCSVC
SRCSPAN
SRCTIMESLOT
DSTSVC
DSTSPAN
DSTTIMESLOT
SC-1
PC-7-200-7
ffff
4065
SC-1
PC-7-200-7
ffff
4066
SC-1
PC-7-200-7
ffff
4067
SC-1
PC-7-200-7
ffff
4068
SC-1
PC-7-200-7
ffff
4069
SC-1
PC-7-200-7
ffff
4070
Use the PROV-RTRV:nailedtrnk:srcsvc=sc-1 command to verify the nailed trunk groups were
added.
Note
Only one source service, destination service, source span, or destination span is allowed at a time.
Use the PROV-RTRV command to verify multiple trunk groups and bearer channels were added.
Note
You cannot provision other trunk group types (for example, TDM or IP) with MLTTRNKGRP.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-41
Chapter 5
Use the PROV-RTRV command to verify the multiple trunk groups and bearer channels were removed.
To verify the component added to the port table, use the NUMAN-RTRV command.
Creating a Profile
A profile must be created before a property, which belongs to a profile, can be added. Profile types are:
GRPROFILE
ISUPTMRPROFILE
ATMPROFILE
When configuring a profile, you can attach a profile to a signaling service, but both the profile and the
signaling service must belong to the same variant. However, you can create a profile even though the
signaling service does not exist.
A profile allows one or more properties to be set once and then reused multiple times. To create a profile,
use the PROV-ADD command as follows:
mml> prov-add:profile:name="profile1",type="grprofile",hopon="0"defaultBC="3_1_KHZ",
confusion="1"
Note
A GR317 profile must be created before a trunk group can be associated with the profile.
Note
A profile must be created before a trunk group can be associated with the profile.
To add a profile type, use the PROV-ADD command as follows:
mml> prov-add:trnkgrpprof:name="1000",grprofile="profile1"
Use the PROV-RTRV command to verify the specified trunk group property profile has been overridden.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-42
OL-1110-23
Chapter 5
Use the PROV-RTRV command to verify the specified trunk group property profile has been deleted.
To retrieve all profile types, use the PROV-RTRV:profiletypes command.
Note
The validation parameter is added in software Release 9.5(2), This parameter is valid only for
ISUP timer profiles. When the validation parameter is set to off, ISUP timer values can be
entered that are outside the valid range as defined by the specification. During an export
(prov-exp), if any of the timer values are out of range, the validation parameter is exported with
its value set to off.
Use the following MML commands to retrieve, delete, edit, and attach an ISUP timer profile.
mml> prov-rtrv:profile:name="set1"
The profile can be deleted if it is not attached to a component using the following MML command.
mml> prov-dlt:profile:name="set3"
The profile edit command does not need variant information with it.
The profile edit command causes the change to parameters if it is already existing with profile. If it is a
new property, it is added against this profile.
mml> prov-ed:profile:name="prof1",type="isuptmrprofile",T6="13",T7="24",T25="3"
The prov-edit command shows the defaults and the over-ridden values.
The following MML command attaches a profile to a sigpath:
mml> prov-add:sigpathprof:name="ss7svc1",isuptmrprofile="set1"
Refer to Appendix A, Profile, for a list the valid ranges and default values of each configurable ISUP
timer for each supported protocol variant.
When configuring an ISUP timer profile, you must specify a protocol variant listed in Appendix A,
Protocol Variants. However, you can create a profile even though the signaling service does not exist.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-43
Chapter 5
To suppress the CLID, GN, or PN in a SIP environment, set the cgpnInclude trunk group property to 0.
See Table 5-5, Table 5-6, and Table 5-7 for a list of CLID, GN, and PN suppression values based upon
the incoming PSTN signaling settings for a SIP terminated call through a SIP trunk group.
Table 5-5
Received CLIR
(in IAM)
Outgoing FROM
header
Displayname field
Outgoing FROM
header
Username field
Not applicable
Not available
Not available
Unknown
Unknown
Available
CLID
Available
1 (restriction)
Anonymous
1 (include)
Available
CLID
1 (include)
Available
1 (restriction)
CLID
Table 5-6
Anonymous
Anonymous
Received GN
APRI1 (in IAM)
Outgoing FROM
header
Displayname field
Outgoing FROM
header
Username field
Not applicable
Not available
Not available
Unknown
Unknown
Available
Address signal of
GN
Available
1 (restriction)
Anonymous
1 (include)
Available
Address signal of
GN
1 (include)
Available
1 (restriction)
Address signal of
GN
Address signal of
GN
Anonymous
Table 5-7
Received PN
APRI (in IAM)
Outgoing FROM
header
Displayname field
Outgoing FROM
header
Username field
Not applicable
Not available
Not available
Unknown
Unknown
Available
Available
1 (restriction)
Anonymous
Anonymous
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-44
OL-1110-23
Chapter 5
Table 5-7
Received PN
APRI (in IAM)
Outgoing FROM
header
Displayname field
Outgoing FROM
header
Username field
1 (include)
Available
1 (include)
Available
1 (restriction)
Anonymous
Table 5-8 and Table 5-9 show the mapping of the RDN and OCN parameters from PSTN signaling to
SIP Diversion Header with different settings for the SIP trunk group property cgpnInclude.
Table 5-8
RDN
(in IAM)
Presentation
Indicator
(in RDN)
cgpnInclude
(on originating SIP displayname
username
trunk group)
(Diversion header) (Diversion header)
Available
0 (no restriction)
RDN
Available
1 (restricted or
unavailable)
Anonymous
Available
RDN
Available
RDN
Table 5-9
OCN
(in IAM)
Presentation
Indicator
(in OCN)
cgpnInclude
(on originating SIP displayname
username
trunk group)
(Diversion header) (Diversion header)
Available
0 (no restriction)
OCN
Available
1 (restricted or
unavailable)
Anonymous
Available
OCN
Available
OCN
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-45
Chapter 5
The following example represents the result of the previous MML command in routeAnalysis.dat:
$ATMProfiles
# CiscoMGC:
#name
atmprof1
01
ATMProfiles
ITU1;cust100
prov-ed:atmprofiles:name="atmprof1",atmprofiles="ITU1;custom200"
prov-dlt:atmprofiles:name="atmprof1"
prov-rtrv:atmprofiles:name="atmprof1"
prov-rtrv:atmprofiles:"all"
prov-add:trnkgrp:name="1000",svc="ss7svc1",type="ATM"
prov-ed:trnkgrpprop:name="1000",playannouncement="0"
prov-ed:trnkgrpprop:name="1000",GWDefaultATMProfile="profile1;profile2"
prov-ed:trnkgrpprop:name="1000",NetworkType="1"
prov-ed:trnkgrpprop:name="1000",AtmConnectionType="4"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-46
OL-1110-23
Chapter 5
E164 numbers must be associated with route groups. Each route group may contain one or more routes.
And in turn, each route may be associated with a SIP trunk group. The E164 number to SIP trunk group
association must be provisioned. In addition, the SIP signaling path between the
Cisco PGW 2200 Softswitch and the SIP server must be provisioned. These procedures are described in
the following sections.
Use the PROV-RTRV command to verify that the SIP signaling service was added.
Use the PROV-RTRV command to verify that the SIP signaling link was added.
Note
If the Virtual IP Address, in XECfgParm.dat, is configures with the 0.0.0.0, a fail over does not create
the new logical interface, thus not enable the SIP failover support feature and does not block creation of
a second SIP signaling link.
Use the PROV-RTRV command to verify that the SIP trunk group was added.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-47
Chapter 5
mml> prov-add:trnkgrpprop:name="1111",custgrpid="1122",MGCdomain="mgc.cisco.com",
mgcsipversion="2.0",Localport="5060",InvitetimerT1="2000",gentimerT1="800",
genTimerT2="7000",maxRedirectCnt="9",Support183="4",Fromfield="anonymous",
DefaultsessionTimer="500000",MaxSessionTimer="800000",holdtimer="400000"
Use the PROV-RTRV command to verify that the SIP trunk group property was added.
Use the PROV-RTRV command to verify the SIP routing trunk group property was added.
Use the PROV-RTRV command to verify that the SIP DNS property was set.
The following is a sample MML test script for provisioning SIP:
prov-sta::srcver="new",dstver="ems"
prov-add:card:name="enet-card",type="EN",slot=0,desc="Ethernet card",type="EN"
prov-add:enetif:name="enet-if",desc="Ethernet interface",card="enet-card"
;
; provision SIP sigpath
;
prov-add:sippath:name="sip-path",mdo="IETF_SIP",desc="SIPsigpath"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-48
OL-1110-23
Chapter 5
;
: provision SIP link
;
prov-add:siplnk:name="sip-link",ipaddr="IP_Addr1",svc="sip-path",
port=5060,pri=1,desc="SIPlink"
;
;provision trunk group for incoming SIP calls
;
prov-add:trnkgrp:name="1701",svc="sip-path",type="SIP_IN"
prov-add:TRNKGRPPROP:name="1701",CustGrpId="1133",MGCdomain="192.0.2.15",mgcsipversion="2.
0",Localport="5060",InvitetimerT1="1000",gentimerT1="500"
,genTimerT2="4000",maxRedirectCnt="5",Support183="4",Fromfield="sip-network",holdtimer="40
0000"
;
;provision trunk group for outgoing SIP calls
;
prov-add:trnkgrp:name="707",svc="sip-path",type="IP_SIP"
prov-add:TRNKGRPPROP:name="707",CustGrpId="1133",MGCdomain="192.0.2.15",mgcsipversion="2.0
",Localport="5060",InvitetimerT1="1000",gentimerT1="500",
genTimerT2="4000",maxRedirectCnt="5",Support183="4",Fromfield="sip-network",holdtimer="400
000"
;
;provision trunk group for outgoing SIP calls
;
prov-add:trnkgrp:name="706",svc="sip-path",type="IP_SIP"
prov-add:TRNKGRPPROP:name="706",CustGrpId="1133",MGCdomain="192.0.2.15",mgcsipversion="2.0
",Localport="5060",InvitetimerT1="1000",gentimerT1="500",
genTimerT2="4000",maxRedirectCnt="5",Support183="4",Fromfield="pstn-network",holdtimer="40
0000"
prov-add:siprttrnkgrp:name="707",url="192.0.2.16",srvrr=0,sipproxyport=5060,version="2.0",
cutthrough=1,extsupport=1
prov-add:siprttrnkgrp:name="706",url="192.0.2.16",srvrr=0,sipproxyport=5060,version="2.0",
cutthrough=1,extsupport=1
;
; provision DNS parameters
;
prov-add:dnsparam:dnsserver1="64.102.6.247",cachesize="500",ttl="3600",policy="hierarchy",
querytimeout="1000",keepalive="30"
prov-add:rttrnk:name="route707",trnkgrpnum=707
prov-add:rttrnk:name="route706",trnkgrpnum=706
prov-add:rtlist:name="list707",rtname="route707"
prov-add:rtlist:name="list706",rtname="route706"
numan-add:resultset:custgrpid="1133",name="set707"
numan-add:resultset:custgrpid="1133",name="set706"
numan-add:resulttable:custgrpid="1133",name="result707",resulttype="ROUTE",dw1="list707",s
etname="set707"
numan-add:resulttable:custgrpid="1133",name="result706",resulttype="ROUTE",dw1="list706",s
etname="set706"
numan-add:bdigtree:custgrpid="1133",callside="originating",digitstring="707",setname="set7
07"
numan-add:bdigtree:custgrpid="1133",callside="originating",digitstring="706",setname="set7
06"
prov-stp
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-49
Chapter 5
To modify a SIP signaling service for the signaling gateway from the Cisco PGW 2200 Softswitch
configuration, use the PROV-ED command as follows:
mml> prov-ed:sippath:name="sip-path",mdo="IETF_SIP",desc="SIP sigpath"
Use the PROV-RTRV command to verify that the SIP signaling service was modified.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-50
OL-1110-23
Chapter 5
Verifying Parameter Settings and Re-configuring Cisco PGW 2200 Softswitch Software
Perform the following steps to verify parameter settings and re-configure the
Cisco PGW 2200 Softswitch software to support the SIP Automatic Switchover Using Dual-VLAN
feature:
Caution
Re-configuration of the Cisco PGW 2200 Softswitch software requires that the system software be shut
down. In a simplex system, calls cannot be processed during system shutdown. In a continuous service
system, your system loses the ability to maintain calls during a critical event if the system software on
one of the Cisco PGW 2200 Softswitch hosts is shut down.
Step 1
Log in to the standby Cisco PGW 2200 Softswitch as root and change directories to the etc subdirectory
by entering the following UNIX command:
cd /opt/CiscoMGC/etc
Step 2
Step 3
Search for the *.Virtual_IP_Addr1 parameter and ensure that the current setting is a virtual address
within the subnet of the IP address defined in the IP_Addr1 parameter.
Note
The IP address should be expressed in dotted decimal notation (for example, 192.0.2.2).
If the value of the parameter is correct, proceed to Step 4. Otherwise, correct the value of the parameter
and then proceed to Step 4.
Step 4
If you have not configured a second virtual IP address, proceed to Step 6. Otherwise, search for the
*.Virtual_IP_Addr2 parameter and ensure that the current setting is a virtual address within the subnet
of the IP address defined in the IP_Addr2 parameter.
Note
The IP address should be expressed in dotted decimal notation (for example, 192.0.2.2).
If the value of the parameter is correct, proceed to Step 5. Otherwise, correct the value of the parameter
and then proceed to Step 5.
Step 5
Search for the *.sipFailover parameter and ensure that the current setting is true.
If the value of the parameter is correct, proceed to Step 6. Otherwise, correct the value of the parameter
and then proceed to Step 7.
Step 6
If you have made any changes to the parameter values, proceed to Step 7. Otherwise, close the text editor
and proceed to Step 10.
Step 7
Step 8
Manually stop the Cisco PGW 2200 Softswitch software on the standby Cisco PGW 2200 Softswitch by
entering the following UNIX command:
/etc/init.d/CiscoMGC stop
Step 9
Once the software shutdown is complete, manually start the Cisco PGW 2200 Softswitch software on
the standby Cisco PGW 2200 Softswitch by entering the following command:
/etc/init.d/CiscoMGC start
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-51
Chapter 5
Step 10
Log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the following
command:
mml> sw-over::confirm
Site alarms are automatically set until the out-of-service (OOS) Cisco PGW 2200 Softswitch host is
returned to an in-service (IS) state.
Step 11
Repeat steps 1 through 5 for the newly standby Cisco PGW 2200 Softswitch host.
Step 12
If you have not made any changes to the parameter values, proceed to Step 13. If you have made any
changes to the parameter values, repeat steps 7 through 10. Once you have completed step 10, the
procedure is complete.
Step 13
Contact the Cisco Technical Assistance Center (TAC) for assistance in resolving this problem.
Information on contacting the Cisco TAC can be found in the Obtaining Documentation and Submitting
a Service Request, page -xxiii.
Note
The XECfgParm.dat parameters for this feature must be configured before you can provision virtual IP
addresses for SIP IP links. If you have not configured the parameters, perform the steps in the Verifying
Parameter Settings and Re-configuring Cisco PGW 2200 Softswitch Software section on page 5-51
before performing the following procedures.
To provision virtual IP address(es) on your SIP IP links, perform the following steps:
Step 1
Step 2
If you are provisioning SIP IP links for the first time, proceed to Step 9. Otherwise, proceed to Step 3.
Step 3
Enter the following command to display the settings for your SIP IP links:
mml> prov-rtrv:siplnk:all
The system returns a response that lists the settings for all of your provisioned SIP IP links. Take note
of the IP address settings (ipaddr1 and ipaddr2) for each link. Identify the SIP IP links that do not have
an IP address setting of Virtual_IP_Addr1.
Step 4
The identified SIP IP links must be taken out-of-service. To do this, enter the following command:
mml> set-iplnk:name:OOS
Where name is the MML name of a SIP IP link provisioned with standard IP addressing. Repeat this step
for each affected SIP IP link.
Step 5
The identified SIP IP links must be deleted. Enter the following command to delete one SIP IP link:
mml> prov-dlt:siplnk:name="name"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-52
OL-1110-23
Chapter 5
Repeat this step for each SIP IP link you are to delete.
Step 6
If any of the SIP IP links have an IP address setting of Virtual_IP_Addr1, proceed to Step 9. Otherwise,
proceed to Step 7.
Step 7
Delete the signaling service associated with the deleted SIP IP links. To do this, enter the following
MML command:
mml> prov-dlt:sippath:name="name"
Where name is the MML name of the new SIP signaling service.
For example, to provision a new SIP signaling service called sipsrv1, enter the following command:
mml> prov-add:sippath:name="sipsrv1",mdo="ietf_sip"
Step 9
For example, to provision a SIP IP link that supports a virtual IP address, enter the following MML
command:
mml> prov-add:siplnk:name="sip-sigchan1",ipaddr="Virtual_IP_Addr1",svc="sip-sigpath",
port=5060,pri=1,desc="SIP sigchan 1"
Step 10
If you want to create a second virtual IP address, enter the following command. Otherwise, proceed to
Step 11.
mml> prov-add:siplnk:name="sip-sigchan2",ipaddr="Virtual_IP_Addr2",svc="sip-sigpath",
port=5060,pri=1,desc="SIP sigchan 2"
Step 11
Repeat steps 2 through 10 for each SIP IP link you provision with a virtual IP address.
Step 12
Note
Step 1
Log in to the standby Cisco PGW 2200 Softswitch as root and change directories to the etc subdirectory
by entering the following UNIX command:
cd /opt/CiscoMGC/etc
Step 2
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-53
Chapter 5
Step 3
Search for the *.Virtual_IP_Addr1 parameter and set the value to 0.0.0.0.
Step 4
If you have not configured a second virtual IP address, proceed to Step 5. Otherwise, search for the
*.Virtual_IP_Addr2 parameter and set the value to 0.0.0.0.
Step 5
Search for the *.sipFailover parameter and set the value to false.
Step 6
Step 7
Manually stop the Cisco PGW 2200 Softswitch software on the standby Cisco PGW 2200 Softswitch by
entering the following UNIX command:
/etc/init.d/CiscoMGC stop
Step 8
Once the software shutdown is complete, manually start the Cisco PGW 2200 Softswitch software on
the standby Cisco PGW 2200 Softswitch by entering the following command:
/etc/init.d/CiscoMGC start
Step 9
Log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the following
command:
mml> sw-over::confirm
Site alarms are automatically set until the out-of-service (OOS) Cisco PGW 2200 Softswitch host is
returned to an in-service (IS) state.
Step 10
Repeat steps 1 through 8 for the newly standby Cisco PGW 2200 Softswitch host.
Step 11
The affected SIP links must be taken out-of-service. To do this, enter the following command:
mml> set-iplnk:name:OOS
Where name is the MML name of a SIP IP link provisioned with virtual IP addressing. Repeat this step
for each affected SIP IP link.
Step 12
Log in to the active Cisco PGW 2200 Softswitch host, start an MML session, and begin a provisioning
session.
Step 13
To change from virtual IP addressing to standard IP addressing, delete the SIP IP links provisioned with
virtual IP addressing. Enter the following command to delete an affected SIP IP link:
mml> prov-dlt:siplnk:name="name"
Where name is the MML name of a SIP IP link provisioned with virtual IP addressing. Repeat this step
for each affected SIP IP link.
Step 14
Enter the following command to delete the associated SIP signaling service:
mml> prov-dlt:sippath:name="name"
Where name is the MML name of a SIP signaling service associated with the SIP IP links provisioned
with virtual IP addressing.
Step 15
Where name is the MML name of the new SIP signaling service.
For example, to provision a new SIP signaling service called sipsrv1, enter the following command:
mml> prov-ed:sippath:name="sipsrv1",mdo="ietf_sip"
Step 16
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-54
OL-1110-23
Chapter 5
Where name is the MML name of the affected SIP IP link; addr is the first local IP address for a LAN
interface. IP address should be IP_Addr1, IP_Addr2, IP_Addr3, or IP_Addr4, as defined in the
XECfgParm.dat file.
For example, to enable an IP address on a SIP IP link, you would enter the following command:
mml> prov-add:siplnk:name="sip-sigchan1",ipaddr="IP_Addr1"
Repeat this step for each SIP IP link you provision with standard IP addressing.
Step 17
Note
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-55
Chapter 5
Repeat the MML command for the SIP trunk groups for which you want to activate SIP-T or SIP-GTD
support.
Note
The GTD parameter names that can be entered in the override_string are:
RGN.noa | OCN.noa | CPN.noa | CGN.noa |
BCI.inter | BCI.acc | OBI.inb | CAI.loc | ATP.dat
Note
The override_string GTD command is not valid for use with SIP.
The parameters contained in gtdParamString indicate all the GTD parameters the
Cisco PGW 2200 Softswitch supports for the specified NAS sigpath. The parameters contained in
gtdOverrideFieldsString indicate all the GTD fields that the Cisco PGW 2200 Softswitch overrides for
the specified NAS sigpath.
The GTD parameter names that can be entered in the build_string are:
ACL | ADI | APP | ATP |
BCI | BSG | BVN | CAI |
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-56
OL-1110-23
Chapter 5
Note
MML validates the length of gtdParamString and overrideString, but does not validate the syntax. The
parameters and fields with invalid syntax are ignored.
An example of the content of gtdParam.dat:
CompTypeID
gtdParamString
overrideString
00370001
CPC,CGN,CDN,BCI,R
GN,CID
CDN.noa,CGN.noa,RG
N.noa
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-57
Chapter 5
00370002
ALL
NONE
00370003
CPC,CGN,CDN
CGN.#,CGN.si
00370004
NONE
CDN.noa
To support sigpath as well, the existing Trunk Group property ISUP Transparency Disabled
(IsupTransParencyDisabled) permits disabling the ISUP transparency feature and supports NAS sigpath
and SS7 sigpaths.
The possible values are 1 (Disabled) or 0 (Enabled). The default value is 1 (Disabled). The value is a
string type.
In addition, another property (IsupTransEarlyBackwardDisabled) is used by ISDN PRI sigpath to
indicate if Early Backward Call Setup Message supported.
The possible values are 1 (Disabled) or 0 (Enabled). The default value is 1 (Disabled).
You can provision a subset of GTD parameters using a set of MML interface commands. No validation
is performed on the input of GTD parameters.
An MML command with the TID gtdParam supports the configurable GTD parameters. The following
are examples of adding, editing, and deleting GTD parameters.
prov-add:gtdParam:name="t3",gtdParamString="BCI,CPC,CGN,CIC,CPN,MCR"
prov-ed:gtdParam:name="t3",gtdParamString="BCI,CPC,CGN,UUI",
overridestring="RGN.noa,CGN.noa"
prov-dlt:gtdParam:name="t3"
You can also define GtdCapTypeProp to be associated with a NAS sigpath. This property is used by the
Cisco PGW 2200 Softswitch as a pointer to the subset of GTD parameters that you have already defined.
The default value the GtdCapTypeProp is t0, which stands for no GTD support.
The property GtdMsgFmt is associated with isdnpri sigpath. The value is a string, where c = compact
(default).
The property CorrelationCallIDFormat is associated with isdnpri sigpath. The value is an integer, where
0 = H323 (default) and 1 = SIP.
The property IsupTransEarlyBackwardDisabled is associated with isdnpri sigpath. The value is integer
type, where 0 = Enabled and 1 = Disabled (default).
The property IsupTransParencyDisabled is associated with isdnpri sigpath. The value is an integer,
where 0 = Enabled and 1 = Disabled (default).
For SS7-to-SS7 calls, GTD transports the backward call indicator (BCI) and optional backward call
indicators within the facility indicator parameter. However; unless specified in the override string, the
default setting is for the ISUP data to populate the BCI fields. Use the following MML command to
populate the BCI fields with GTD data.
mml> prov-add:gtdparam:name="t1",gtdparamstring="ALL",overridestring="BCI.acc,OBI.inb,
BCI.inter"
where:
BCI.acc is used to override the ISDN ACCESS IND field in the BCI
BCI.inter is used to override INTERWORKING field in the BCI
OBI.inb is used to override INBAND INFO field in the optional backward call indicators
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-58
OL-1110-23
Chapter 5
Note
If you enable GTD on your system, the following ISUP parameter codes are always allowed, regardless
of your individual selections: EVI, GCI, PCI, PRN, MCI, and FDC.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-59
Chapter 5
Redirecting number
Redirection number
Generic number
Each number has an inbound and outbound CTT. Although in most cases the inbound and out bound
NOA translation values would be the same, they can be different.
Depending on the CTT configuration, Type B (calls between the same SS7 protocol variant) exchange
operation may be affected. For example, without CTT configured, for some non-called party numbers, a
line NOA value may be out of range, and this information would be passed from the ingress to the egress
and populated in the egress message.
However, if an inbound CTT is configured that translates the inbound line out-of-range NOA value to a
value that is in range, the call is then handled as a normal call. The outbound message on the egress side
may or may not contain the same line NOA value as the ingress depending on the outbound CTT.
The following sections describe the MML commands used to provision the NOA configurable mapping
feature and the corresponding line translate file (linexlate.dat).
where:
MML name = an NOA translate table entry name, as many as 20 characters in length, or all
Description = a more descriptive name for the entry, which can be as many as 128 characters in length
Parameter = 1
Direction = 0 or 1
Number = 0 through 5
Intnoa = 0 through 52
Extnoa = 0 through 127
For adding an entry, none of the parameters are optional, all must be present, as shown in the following
example.
mml> prov_add:linexlate:name=noa1,desc=noa in calling 10,svc=ss7svc1,parameter=1,
direction=in,number=calling,intnoa=17,extnoa=10
The following MML command syntax is used to delete an entry from the linexlate.dat file.
mml> prov-dlt:linexlate:name=<MML name>
The following MML command syntax is used to retrieve an entry in the linexlate.dat file.
prov-rtrv:linexlate:name=<MML name>
Where the MML name is the name of an NOA translate table entry.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-60
OL-1110-23
Chapter 5
Note
The line translation table contains no default entries, since all parameters must be entered to create a
configuration entry.
Caution
Step 2
Do not name the destination directory active or new. The names active and new have special
meanings in the Cisco PGW 2200 Softswitch software. Starting a provisioning session with a source
version name of new, is to be done only the first time provisioning is performed.
Dynamically add the internal NOA and line NOA property for LineXlate.
mml> prov-add:linexlate:name=noa1,desc=noa in calling 10,svc=ss7svc1,
direction=in,number=calling,intnoa=17,extnoa=10
Step 3
Step 4
For more information on provisioning for the rest of the Cisco PGW 2200 Softswitch software, refer to
the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Step 2
Dynamically delete the internal NOA and line NOA property for LineXlate.
mml> prov-dlt:linexlate:name=noa1
Step 3
Step 4
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-61
Chapter 5
Step 1
Step 2
Dynamically add the internal NOA and line NOA property for LineXlate.
mml> prov-add:linexlate:name=noa2,desc=noa in calling 10,svc=ss7svc1,
direction=out,number=called,intnoa=17,extnoa=10
Step 3
Step 4
Step 2
Step 3
Step 4
Validation Rules
Note
The Configured Translation table contains no default entries since all parameters must be entered to
create a configuration entry.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-62
OL-1110-23
Chapter 5
Note
Note
To support M3UA and SUA interfaces, the value of the type parameter must be set to trueopc.
Add an SUA routing key named suakey1 by entering the following MML command.
mml> prov-add:SUAKEY:NAME="suakey1",OPC="opc1",APC="apc1",localssn=200,ROUTINGCONTEXT=20
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-63
Chapter 5
Add an SUA route named suarte1 by entering the following MML command.
mml> prov-add:SUAROUTE:NAME="suarte1",DESC="SUA Rte 1",APC="apc1",OPC="opc1",
EXTNODE="itp1",remotessn=40
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-64
OL-1110-23
Chapter 5
Cisco
PGW 2200
Softswitch
5.3.5
SS7
HLR
SIP
IP
SIP
209.165.200.224
ITP
MAP gateway
192.0.2.1
253703
Figure 5-4
If the Cisco PGW 2200 Softswitch is unable to optimize the call routing based on the MSRN, it
continues to route calls based on the mobile subscribers MSISDN (telephone number). The
Cisco PGW 2200 Softswitch routes calls based on an MSISDN by means of cause analysis.
The following procedure provisions the Cisco PGW 2200 Softswitch to send the customized SIP invite
to the ITP, requesting a MAP query of the subscribers MSRN. It also sets up alternative routing based
on the subscribers MSISDN; the system uses the alternative routing if it does not receive an MSRN from
the ITP.
Step 1
Create two trunk groups, one for the MSRN (when the ITP returns an MSRN), and a second trunk group
for the MSISDN (when the ITP does not return an MSRN). In the following examples, trunk group 907
is for the MSRN and trunk group 1001 is for the MSISDN (or if routing on trunk group 907 fails):
mml> prov-add:rttrnk:weightedTG="OFF",name="rg907",trnkgrpnum=907
mml> prov-ed:rttrnk:name="rg907",trnkgrpnum=1001
mml> prov-add:rtlist:name="rlst907",rtname="rg907",distrib="OFF"
Step 2
Enter the following command to enable the MAP request on the trunk group for the MSRN:
mml> prov-ed:trnkgrpprop:name="xxx",ItpActionRequest="map-app"
Note
Step 3
If you need to disable the MAP request, enter the following command
prov-dlt:trnkgrpprop:name="xxx", "ItpActionRequest"
(Optional) Advance the trunk for failed calls using the following MML commands:
mml> numan-add:resultset:custgrpid="DP00",name="tgadvset"
mml> numanadd:resulttable:custgrpid="DP00",name="tgadvset",resulttype="RETRY_ACTION",
dw1="tgadvance",setname="tgadvset"
mml> numan-ed:cause:custgrpid="DP00",causevalue=176,setname="tgadvset"
/* The value for the internal cause code, IC_ITP_QUERY_FAIL, is 176. */
Step 4
(Optional) Switch to new a new dial plan for failed calls using the following MML commands:
mml> numan-add:dialplan:custgrpid="DP01",OVERDEC="NO"
mml> numan-add:resultset:custgrpid="DP01",name="rset-1"
mml> numan-add:resulttable:custgrpid="DP01",name="rtab-1",resulttype="ROUTE",
dw1="rtlist1",setname="rset-1"
mml> numan-add:bdigtree:custgrpid="DP01",callside="originating",digitstring="12",
setname="rset-1"
mml> numan-add:dpsel:custgrpid="DP00", newdp="DP01"
mml> numan-add:resultset:custgrpid="DP00",name="SwToDP01"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-65
Chapter 5
mml> numan-add:resulttable:custgrpid="DP00",name="SwitchDP1",resulttype="NEW_DIALPLAN",
dw1="DP01",dw2="2",setname="SwToDP01"
mml> numan-ed:cause:custgrpid="DP00",causevalue=176,setname="SwToDP01"
/* The value for the internal cause code, IC_ITP_QUERY_FAIL, is 176. */
The provisioning examples for ITP as a MAP proxy for this feature are as follows:
cs7 variant itu
cs7 point-code 5.3.5
interface ethernet 0/0
ip address 209.165.200.224 255.255.255.224
cs7 mapua SIP_MAP_GW sip
client 192.0.2.1
map-source-addr digits 1234567890 tt 0 gti 2
gsm-send-routing-info version 2
invoke-timer 20
For more information on the ITP provisioning, see the Implementing a PGW SIP MAP Gateway
section in Cisco IP Transfer Point (ITP) in IOS Software Release 12.4(I5)SW4 at
http://www.cisco.com/en/US/docs/wireless/itp/itp_12_2_18_ipx/PDFs/12415sw4.pdf
You can use the following three commands to monitor ITP for this feature:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-66
OL-1110-23
Chapter 5
Playing an Announcement when the Call Limiting Threshold is Exceeded, page 5-75
Caution
Do not name the destination directory active or new. The names active and new have special
meanings in the Cisco PGW 2200 Softswitch software. Starting a provisioning session with a source
version name of new, is to be done only the first time provisioning is performed.
prov-stp
prov-sta::srcver="new",dstver="ver1"
prov-add:loclabel:name="loclbl1",desc="local label 1",calllimit=2345
prov-add:loclabel:name="loclbl2",desc="local label 2",calllimit=6000
prov-rtrv:loclabel:name="loclbl1"
prov-rtrv:loclabel:name="loclbl2"
prov-rtrv:loclabel:"all"
locationLabel.dat
005f0001 2345
005f0002 6000
prov-add:sippath:name="sip-sigpath",mdo="IETF_SIP",desc="SIP sigpath",ORIGLABEL="loclbl1",
TERMLABEL="loclbl2"
prov-rtrv:sippath:name="sip-path"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-67
Chapter 5
sigPath.dat
00150001 SS7-ANSI ANSISS7_STANDARD 1111 0101 0 network n 2 00130002 00130001
00000000 00000000 0 005f0001 005f0002
00190001 EISUP EISUP 0000 0101 0 network n 2 00000000 00000000 00000000
00000000 0 005f0001 005f0002
00340001
dummy 0000 0101 0 network n 2 00000000 00000000 00000000 00000000 0
005f0001 005f0002
003e0001 SIP IETF_SIP 0000 0101 0 network n 2 00000000 00000000 00000000
00000000 0 005f0001 005f0002
00420001 SS7-ANSI ANSISS7_STANDARD 1111 0101 0 network n 2 00130003 00130001
00410001 00000000 0 005f0001 005f0002
00550001 DPNSS DPNSS_BTNR188 1111 0101 26 network n 2 00000000 00000000 00000000
00000000 513 005f0001 005f0002
prov-add:trnkgrp:name="3000",svc="sip-sigpath",type="SIP_IN",ORIGLABEL="loclbl1",
TERMLABEL="loclbl2",selSeq="LIDL"
prov-rtrv:trnkgrp:name="3000"
MGC-01 - Media Gateway Controller 2005-07-06 16:25:36.691 EDT
M RTRV
"session=begon-base1:trnkgrp"
/*
NAME = 3000
CLLI = stim-dpnss1
SVC = sip-sigpath
TYPE = SIP_IN
SELSEQ = LIDL
ORIGLABEL =
TERMLABEL =
*/
;
trunkGroup.dat
00200001 3000
005f0002
0000
0000
003e0001
SIP_IN
LIDL
0/0/0/0
0/0/0/0
005f0001
components.dat
00570001 00010001 "LI"
005f0001 00010001 "loclbl1"
005f0002 00010001 "loclbl2"
Note
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-68
OL-1110-23
Chapter 5
Figure 5-5
PSTN Gateway
PGW 2200
IP
M
H.323
Gatekeeper
CCM-X
IP Phone
AS5X00/UP
GK
IP
M
CCM-Y
Packet
Core
PSTN
IP Phone
MGX 8800
Voice GW
V
PBX-2
Two Gateways used for redundancy, total DS0=60
Call limiting can limit calls, for example to 10 DS0
138058
MGCP
SS7/IP between nodes
SIP
H.323
C7/SS7
PRI/Q.SIG/DPNSS signaling backhaul
Data
PRI/Q.SIG/DPNSS physical interface
IMT
1. Remove the PBX icon (to the left of the PSTN Gateway rectangle).
2. Remove the line (shown in red) from the PBX to the AS icon and to the MGX icon.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-69
Chapter 5
To provision this, create a label, for example LABELCCMY with a value of 12, then in the B-number
analysis, set the LOC_LABEL to the label (LABELCCMY) you just created. In the A-number analysis,
select a dial plan based on the LOC_LABEL to the XX LABEL.
If the CCM has a prefix of 300XXX, the incoming calling limit for 300XXXX is 100 and the outgoing
calling limit for 300XXXX is 12.
This allows you to define the incoming and outgoing trunk group call limiting separately.
//For outgoing call limit
prov-add:loclabel:name="location1",calllimit=12
numan-add:resultset:custgrpid="1111",name="set300"
numan-add:resulttable:resulttype="LOC_LABEL",dw1="location1",setname="set300",
custgrpid="1111",name="resultloc300"
numan-add:resulttable:custgrpid="1111",name="result300",resulttype="ROUTE",dw1="rtlist3",
setname="set300"
numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="300",
setname="set300"
//For incoming call limit
numan-add:Numan-add:resultset:custgrpid="1111"?name="set301"
numan-add:resulttable:resulttype="LOC_LABEL",dw1="location1",setname="set301",
custgrpid="1111",name="resultloc301"
numan-add:adigtree:custgrpid="1111",callside="originating",digitstring="300",
setname="set301"
Figure 5-6
PSTN Gateway
PGW 2200
IP
M
H.323
Gatekeeper
CCM-X
IP Phone
AS5X00/UP
GK
IP
M
CCM-Y
Packet
Core
PSTN
IP Phone
MGX 8800
Voice GW
V
Per Business contract
For example set the limit to
12 calls to this Call Manager
138059
MGCP
SS7/IP between nodes
SIP
H.323
C7/SS7
PRI/Q.SIG/DPNSS signaling backhaul
Data
PRI/Q.SIG/DPNSS physical interface
IMT
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-70
OL-1110-23
Chapter 5
Figure 5-7
PSTN Gateway
PGW 2200
IP
M
H.323
Gatekeeper
CCM-X
IP Phone
AS5X00/UP
GK
IP
M
CCM-Y
Packet
Core
PSTN
IP Phone
MGX 8800
Voice GW
V
PBX-2
Radio station contest results in many simultaneous
calls to the same B-Number. This feature can be
used to limit the calls to the B-number by setting XX
138060
MGCP
SS7/IP between nodes
SIP
H.323
C7/SS7
PRI/Q.SIG/DPNSS signaling backhaul
Data
PRI/Q.SIG/DPNSS physical interface
IMT
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-71
Chapter 5
Note
Either the EISUP path or the HSI trunk group can be provisioned with location label.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-72
OL-1110-23
Chapter 5
2. For example, if all incoming calls that A-numbers have prefix of 300XXX, calling limiting for
300XXXX is set to 100.
numan-add:resultset:custgrpid=1111Cname=set201
//provision call limit location label in resultset
numan-add:resulttable:resulttype="LOC_LABEL",dw1="location2",setname="set201",
custgrpid="1111",name="resultloc201"
//provision Adigtree for A-number 300XXX
numan-add:adigtree:custgrpid="1111",callside="originating",digitstring=300",
setname="set201"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-73
Chapter 5
prov-add:trnkgrp:name="8000",type="IP_SIP",svc="sip-path",clli="",selseq="LIDL",
termlabel="location3"
//location label 3 can be used as DPNSS trunk group 9000
prov-add:trnkgrp:name="9000",type="TDM_DPNSS",svc="dpnss-path1",clli="va-3745-2",
selseq="ASC",qable="N",origlabel="location3",termlabel="location3"
Option 2: Set call limiting with an EISUP trunk group, for example, the trunk group is 6000.
prov-add:loclabel:name="location5",calllimit=100
prov-add:EISUPPATH:NAME="eisup-orkid",DESC="to orchid",EXTNODE="sh-orchid",
CUSTGRPID="1111"
//provision EISUP IP link
prov-add:IPLNK:NAME="elinkorchid1",DESC="Link to orchid",SVC="eisup-orchid",
IPADDR="IP_Addr1",PORT=8001,PEERADDR="192.0.2.20",PEERPORT=8001,PRI=1,IPROUTE=""
//provision call limit in EISUP trunk group
prov-add:trnkgrp:name="6000",type="IP",svc="eisup-daisy",clli="sh-daisy",selseq="ASC",
origlabel="location5",termlabel="location5"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-74
OL-1110-23
Chapter 5
Tip
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-75
Chapter 5
Table 5-10
Signaling Protocol
Type
Family
Parameter in
XECfgParm.dat (Default
maximum number of
links)
NAS
Port number.
MaxNumLinks
Number of links.
(32)
PRIIP
PRIL3
Number of links.
Links associated with the
same port number cannot
be split over different
channel controllers.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-76
OL-1110-23
Chapter 5
Table 5-10
Parameter in
XECfgParm.dat (Default
maximum number of
links)
Signaling Protocol
Type
Family
MGCP
Number of links.
MGCP
SGCP
Number of links.
MaxNumLinks (32)
EISUP
EISUP
Number of links.
MaxNumLinks (32)
FAS
ISDNPRI
Number of links.
MaxNumLinks (32)
Number of links.
MaxNumLinks (32)
DPNSS
TCAP
OverIP
TCAP
OverIP
S77
Switch Type
SS7-ITU
OPC
Protocol Family
Switch Type
SS7-ANSI
SS7-China
0, 5
SS7-ITU
0, 5
SS7-Japan
0, 10
SS7-UK
0, 5
MaxNumLinks (32)
Table 5-11
Component
Scaling Limit
16
32
256
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-77
Chapter 5
Provisioning Examples
Table 5-11
Component
Scaling Limit
512
192
96
600
1200
48
64
96
1536
Provisioning Examples
The following sections provide provisioning examples for Cisco PGW 2200 Softswitch operating
conditions.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-78
OL-1110-23
Chapter 5
to the NAS. This affects the routes of both signal channels. The routes used from the NAS to the
Cisco PGW 2200 Softswitch has not changed, therefore the signal channel that uses hme0 will be out of
service.
To establish two signal paths in the Solaris environment, two IPLNKs must be provisioned on the
Cisco PGW 2200 Softswitch for each NASPATH to the NAS. These two IPLNKs have the same PORT,
PEERPORT, PEERADDR, NETMASK, and SVC values. However, the two IPLNKs have different
IPADDR, IF, and NEXTHOP values.
For each IPLNK, the NEXTHOP is the IP address of the router on the subnet of the IPADDR that is used
to get to the NAS. Be sure the IF of each IPLNK matches the ENETIF corresponding to the IP address
of the IPADDR.
The Cisco PGW 2200 Softswitch uses the NEXTHOP, PEERADDR, and NETMASK values of the
IPLNK to define a static IP route to be put in the Solaris routing table. The destination of the IP route is
determined by ANDing the NETMASK with the PEERADDR.
The NETMASK value determines if the IP route is for a subnet or for an individual NAS. The default
value of 255.255.255.255 causes an IP route to be defined for each individual NAS. If a subnet
NETMASK is used, multiple NASs on the same subnet share the same two IP routes.
Only one of the two IP routes to the same destination and NETMASK are in the Solaris routing table at
a time. If both interfaces are in service, the Cisco PGW 2200 Softswitch picks one of the two IP routes
to the NAS. If the Ethernet interface associated with the IP route that is in the Solaris routing table fails,
the Cisco PGW 2200 Softswitch deletes that IP route from the Solaris routing table and puts the other
IP route to the same destination and NETMASK in the Solaris routing table. The original IP route is not
restored when the Ethernet interface associated with it is restored. The new IP route remains in the
Solaris routing table unless the interface associated with it fails.
Note
If you want to use proxy ARP and host routes, the NEXTHOP parameter can be set to the local address
by using one of the following special strings: IP_Addr1 or IP_Addr2. This is translated into an actual
local address in the same way as the IPADDR parameter. The NETMASK is set to 255.255.255.255 to
produce a host route instead of a subnet route.
The following three alarms are associated with this configuration.
The first alarm, IP RTE FAIL, is generated against an IPLNK or IPSESSION that is provisioned with a
next hop address if the system failed to add the required route. This could be due to an invalid or
conflicting parameter.
The second alarm, IP CONF RTE FAIL, is generated when an IPLNK or IPSESSION is not using the
route that it is configured to use. A conflicting route generated by another signal channel or by another
process can cause this.
The Cisco PGW 2200 Softswitch sets the third alarm, LIF FAIL, when it determines that the Ethernet
interface used by the IPSESSON or IPLNK object is non-operational. It is cleared when the Ethernet
interface becomes operational.
When set, the LIF FAIL alarm is accompanied by a log message, GEN_ERR_IPINTF_FAIL, that
includes the provisioning name and operating system name of the failed Ethernet interface. An example
of the provisioning name is IP_Addr1. An example of the operating system name is hme0. The error
message also contains the failure cause. A cause of Link Down indicates the interface has lost the
carrier. This can be caused by removing the cable or a failure at the Ethernet switch. A cause of Admin
Down indicates that the interface was taken down using the UNIX command ifconfig <interface
name> down.
When cleared, the LIF FAIL alarm is accompanied by a log message, GEN_INFO_IPINTF_RECOV, that
also includes the provisioning name and the operating system name of the interface.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-79
Chapter 5
Provisioning Examples
The following is an example oh how to configure the Cisco PGW 2200 Softswitch and NAS when there
are two IP address on the Cisco PGW 2200 Softswitch and one IP address on the NAS. Each NAS in the
example has one NFAS group and therefore one RLM group.
The following is the example Cisco PGW 2200 Softswitch configuration file for provisioning. The NAS
portion of the configuration is shown in bold.
prov-sta::srcver="new",dstver="dualEnetMGCsingleEnetGW",confirm
prov-add:CARD:NAME="MBRD",DESC="Motherboard",TYPE="EN",SLOT=0
prov-add:ENETIF:NAME="hme0",DESC="IP_Addr1,ipAddrLocalA",CARD="MBRD"
prov-add:ENETIF:NAME="hme1",DESC="IP_Addr2,ipAddrLocalB",CARD="MBRD"
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; SS7 External Node
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:extnode:name="va-2600-56",type="SLT",desc="2611 SLT V.35"
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Point Codes
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:apc:name="stp1",DESC="Own pointcode",NETADDR="1.1.1",NETIND=2
prov-add:apc:name="stp2",DESC="Own pointcode",NETADDR="1.1.2",NETIND=2
prov-add:opc:name="opc",DESC="Own pointcode",NETADDR="1.1.3",NETIND=2,type="TRUEOPC"
prov-add:dpc:name="dpc1",DESC="Destination pointcode1",NETADDR="1.1.4",NETIND=2
prov-add:dpc:name="dpc2",DESC="Destination pointcode2",NETADDR="1.1.5",NETIND=2
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Signal Services to Inet via SLT
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:SS7PATH:NAME="ss7svc1",DESC="SS7 to dpc1",DPC="dpc1",
OPC="opc",MDO="Q761_BASE"
prov-add:SS7PATH:NAME="ss7svc2",DESC="SS7 to dpc2",DPC="dpc2",
OPC="opc",MDO="Q761_BASE"
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; SS7 linksets
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:LNKSET:NAME="ls1",DESC="linkset 1 to stp1",APC="stp1",
PROTO="SS7-ITU",TYPE="IP"
prov-add:LNKSET:NAME="ls2",DESC="linkset 2 to stp2",APC="stp2",
PROTO="SS7-ITU",TYPE="IP"
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; SS7 route
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:SS7ROUTE:NAME="rte1",DESC="opc-stp1-dpc1",
OPC="opc",DPC="dpc1",LNKSET="ls1",PRI=1
prov-add:SS7ROUTE:NAME="rte2",DESC="opc-stp1-dpc2",
OPC="opc",DPC="dpc2",LNKSET="ls1",PRI=1
prov-add:SS7ROUTE:NAME="rte3",DESC="opc-stp2-dpc1",
OPC="opc",DPC="dpc1",LNKSET="ls2",PRI=1
prov-add:SS7ROUTE:NAME="rte4",DESC="opc-stp2-dpc2",
OPC="opc",DPC="dpc2",LNKSET="ls2",PRI=1
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Session Sets
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:sessionset:name="c7sset1",ipaddr1="IP_Addr1",ipaddr2="IP_Addr2",
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-80
OL-1110-23
Chapter 5
port=7000,peeraddr1=""10.82.82.124",peeraddr2="10.82.83.123",
peerport=7000,extnode="va-2600-56",TYPE="BSMV0"
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; C7IPLinks
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:C7IPLNK:NAME="ls1lk1",DESC="SS7ANSI",LNKSET="ls1",sessionset="c7sset1",
SLC=0,PRI=1,TIMESLOT=0
prov-add:C7IPLNK:NAME="ls2lk1",DESC="SS7ANSI",LNKSET="ls2",sessionset="c7sset1",
SLC=0,PRI=1,TIMESLOT=1
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; NAS External Nodes
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:EXTNODE:NAME="va-5300-36",TYPE="AS5300",DESC="remote NAS 5300"
prov-add:EXTNODE:NAME="va-5300-37",TYPE="AS5300",DESC="remote NAS 5300"
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; NAS Signal Paths
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:NASPATH:NAME="nassrv36",DESC="remote NAS sigpath 1",
EXTNODE="va-5300-36",MDO="BELL_1268_C3"
prov-add:NASPATH:NAME="nassrv37",DESC="remote NAS sigpath 2",
EXTNODE="va-5300-37",MDO="BELL_1268_C3"
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; NAS IP Links
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:IPLNK:NAME="nas-lnk36a",DESC="IP link A to va-5300-36",
SVC="nassrv36",IF="hme0",IPADDR="IP_Addr1",PORT=3001,
PEERADDR="10.82.81.29",PEERPORT=3001,PRI=1,
nexthop="10.82.82.1",netmask="255.255.255.0"
prov-add:IPLNK:NAME="nas-lnk36b",DESC="IP link B to va-5300-36",
SVC="nassrv36",IF="hme1",IPADDR="IP_Addr2",PORT=3001,
PEERADDR="10.82.81.29",PEERPORT=3001,PRI=1,
nexthop="10.82.83.1",netmask="255.255.255.0"
prov-add:IPLNK:NAME="nas-lnk37a",DESC="IP link A to va-5300-37",SVC="nassrv37",
IF="hme0",IPADDR="IP_Addr1",PORT=3001,
PEERADDR="10.82.81.30",PEERPORT=3001,PRI=1,
nexthop="10.82.82.1",netmask="255.255.255.0"
prov-add:IPLNK:NAME="nas-lnk37b",DESC="IP link B to va-5300-37",
SVC="nassrv37",IF="hme1",IPADDR="IP_Addr2",PORT=3001,
PEERADDR="10.82.81.30",PEERPORT=3001,PRI=1,
nexthop="10.82.83.1",netmask="255.255.255.0"
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Bearer Channels
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:files:name="BCFile",file="dualEnetMGCsingleEnetGW-bearChan.import",
action="import"
prov-cpy
prov-stp
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-81
Chapter 5
Provisioning Examples
The following is the portion of one of a AS5300 configuration that deals with the IP connectivity to the
Cisco PGW 2200 Softswitch and defining the NFAS and RLM groups.
!
controller T1 0
framing esf
clock source line primary
linecode b8zs
pri-group timeslots 1-24 nfas_d primary nfas_int 0 nfas_group 0
!
controller T1 1
framing esf
clock source line secondary 1
linecode b8zs
pri-group timeslots 1-24 nfas_d none nfas_int 1 nfas_group 0
!
controller T1 2
framing esf
linecode b8zs
pri-group timeslots 1-24 nfas_d none nfas_int 2 nfas_group 0
!
controller T1 3
framing esf
linecode b8zs
pri-group timeslots 1-24 nfas_d none nfas_int 3 nfas_group 0
!
!
!
interface Serial0:23
no ip address
isdn switch-type primary-ni
isdn incoming-voice modem
isdn rlm-group 1
no isdn send-status-enquiry
isdn negotiate-bchan resend-setup
fair-queue 64 256 0
no cdp enable
!
interface FastEthernet0
description production 100 Mbit hub
ip address 10.82.81.29 255.255.255.0
no ip route-cache
no ip mroute-cache
duplex full
speed auto
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.82.82.1
!
rlm group 1
server va-kent
link address 10.82.82.53 source FastEthernet0 weight 2
link address 10.82.83.53 source FastEthernet0 weight 1
server va-surrey
link address 10.82.82.55 source FastEthernet0 weight 2
link address 10.82.83.55 source FastEthernet0 weight 1
!
!
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-82
OL-1110-23
Chapter 5
The Solaris routing table on the Cisco PGW 2200 Softswitch is modified as a result of this
configuration. This can be verified using the netstat rvn command from the unix prompt. The
following is a sample output based on above example for MGC1 with both Ethernet interfaces operating.
The Cisco PGW 2200 Softswitch chooses the IP route associated with IP_Addr1 (that is, hme0). Some
columns have been omitted for clarity. The new entry is in bold text:
IRE Table:
Destination Mask GatewayDeviceFlags
------------- ---------------- ------------- -----10.0.81.1255.255.255.010.82.82.1UGH
10.82.82.0255.255.255.010.82.82.53hme0U
10.82.83.0255.255.255.010.82.83.53hme1U
224.0.0.0240.0.0.010.0.1.10hme0U
default0.0.0.010.82.82.1UG
127.0.0.1255.255.255.255127.0.0.1lo0UH
-----
If the hme0 interface fails, the Solaris routing table is modified to reach the NASs by hme1. The Solaris
routing table from the above example appears as follows:
IRE Table:
DestinationMaskGatewayDeviceFlags
--------------- ---------------- ------------- -----10.0.81.1255.255.255.010.82.83.1UGH
10.82.82.0255.255.255.010.82.82.53hme0U
10.82.83.0255.255.255.010.82.83.53hme1U
224.0.0.0240.0.0.010.0.1.10hme0U
default0.0.0.010.82.82.1UG
127.0.0.1255.255.255.255127.0.0.1lo0UH
-----
If the hme0 interface on MGC1 fails while the platform is active, the rtrv-iplnk shows the c7sset1-1,
nas-lnnk36a, and nas-lnk37a in the OOS state.
The nas-lnk36a and nas-lnk37 have the LIF FAIL and SC FAIL alarms set. The c7sset1-1 has the LIF
FAIL and IP CONNECTION FAIL alarms set. There is also be a PEER LINK A FAILURE alarm set
against the ipAddrPeerA.
The C7IPLNKs, SS7PATH, and NASPATH destinations would still be in-service.
In addition to removing the country code, the Cisco PGW 2200 Softswitch modifies the NOA value in
the ISUP message from international to national.
In the following example, the user remove 12345 if the outgoing A-number contains 12345 as the leading
digits (country code) on the trunk group 8000.
To use remove the A-number country code, perform the following provisioning procedure:
Step 1
Start a provisioning session as described in Starting a Provisioning Session section on page 4-6.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-83
Chapter 5
Call Reporting
Step 2
Provision the digits (country code) that you want to remove from the outgoing A-number on the trunk
group 8000.
mml> prov-add:trnkgrpprop:adigitccrm="12345",name="8000"
Step 3
Repeat Step 2 for each outgoing A-number digit string you want to remove.
Step 4
End the provisioning session as described in Stopping a Configuration Session section on page 4-11.
Call Reporting
You can find the provisioning procedure in the Provisioning Call Reporting section of Chapter 4,
Provisioning Dial Plans with MML, in Cisco PGW 2200 Softswitch Release 9 Dial Plan Guide (through
Release 9.7).
Start a provisioning session as described in Starting a Provisioning Session section on page 4-6.
Step 2
Step 3
Repeat Step 2 for each trunk group you want to add out of band DTMF capability to your provisioning
data.
Step 4
Step 5
Add Level 2 (trunk group) CODEC capabilities on the ingress SIP trunk group:
mml> prov-add:trnkgrpprop:name="1100",custgrpid="1111",GWDefaultCodecString="G723"
Step 6
Add Level 2 (trunk group) CODEC capabilities on the second trunk group:
mml> prov-add:trnkgrpprop:name="2200",custgrpid="1111",GWDefaultCodecString="G729"
Step 7
Add two result sets for Level 3 (dial plan) CODEC capabilities:
mml> numan-add:resultset:custgrpid="1111",name="set1"
mml> numan-add:resultset:custgrpid="1111",name="set2"
Step 8
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-84
OL-1110-23
Chapter 5
Step 9
Step 10
Step 11
Step 12
End the provisioning session as described in Stopping a Configuration Session section on page 4-11.
Start a provisioning session as described in Starting a Provisioning Session section on page 4-6.
Step 2
Set the digit length limit by using the following MML command:
mml> prov-ed:sigsvcprop:name="ss7svc1",tbufferdigitlength="16"
Step 3
End the provisioning session as described in Stopping a Configuration Session section on page 4-11.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-85
Chapter 5
(PBXs) over DPNSS and QSIG. The Feature Transparency mode enables full end-to-end Route
Optimization for mixed CCM and DPNSS PBX networks and also provides significant benefits by
enabling call back services through QSIG tunneling.
Note
Cisco CallManager (CCM) was the old name for Cisco Unified Communications Manager (CUCM).
Before you provision DPNSS service interworking with CCM over QSIG tunneling, configure the
*.DisableCCBSoverTunneledQSIG parameter in the XECfgParm.dat file.
The default value (0) uses the Tunnel QSIG interface for Callback service. Setting a value of 1 selects
the QBE interface for Callback service.
Note
For procedures on configuring parameters in the XECfgParm.dat file, see the Changing
XECfgParm.dat File Parameters in a Running Fault Tolerant System section of
Cisco PGW 2200 Softswitch Release 9.7 Software Installation and Configuration Guide.
In the following sections, you can find the following provisioning procedures:
Provisioning Route Optimization Initiated by the Cisco PGW 2200 Softswitch, page 5-89
Provisioning Route Optimization Responded by the Cisco PGW 2200 Softswitch, page 5-91
Provisioning an H.323 EISUP Trunk Group or sigPaths for Transparent Annex M1 (Tunneled
QSIG), page 5-96
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-86
OL-1110-23
Chapter 5
Figure 5-8
slt7
Session Mgr/
RUDP
PSTN
PGW 2200
HSI
EISUP
V
MGCP
sh-5300-5
Siemens PBX
RAS
DUA/SCTP
& MGCP
GK
Call Manager
V
va-3745-2
H.323 Annex M1
IP
158257
IP
Step 2
Add the DPNSS media gateway, the association, and the DPNSS signaling path:
mml> prov-add:extnode:name="va-3745-2",desc="MGW for dpnss",type="3745",isdnsigtype="IUA",
group=0
mml> prov-add:association:name="assoc-dpnss-gw",desc="siemens pbx", extnode="va-3745-2",
sgp="",type="IUA",ipaddr1="IP_Addr1", ipaddr2="N/A",port=9904,peeraddr1="192.0.2.30",
peeraddr2="0.0.0.0",peerport=9904,iproute1="",iproute2="",rcvwin=18000,
maxinitretrans=10,maxinitrto=2000,maxretrans=5,cumsackto=300,bundleto=100,minrto=300,
maxrto=3000,hbto=2000,ipprecedence="routine",dscp="AF31",maxretransdest=3
mml> prov-add:dpnsspath:name="dpnss-path-1",desc="dpnss sigpath to Siemens PBX",
extnode="va-3745-2",mdo="DPNSS_BTNR188",custgrpid="1111",sigslot=2,sigport=0,origlabel="",
termlabel="",subunit=0
Step 3
Step 4
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-87
Chapter 5
Step 5
Step 6
Step 7
Step 8
prov-add:SIGSVCPROP:name="eisup-bighead",AllowH323Hairpin="1"
prov-add:SIGSVCPROP:name="eisup-bighead",FeatureTransparencyDisabled="1"
prov-add:SIGSVCPROP:name="eisup-bighead",H323AdjunctLink="1"
prov-add:SIGSVCPROP:name="eisup-bighead",OOverlap="1"
prov-add:SIGSVCPROP:name="eisup-bighead",OwnRoutingNumber="488"
prov-add:SIGSVCPROP:name="eisup-bighead",QSIGTunnelVariant="1"
prov-add:SIGSVCPROP:name="eisup-bighead",TOverlap="0"
prov-add:TRNKGRP:name="9300",clli="EISUP2B",svc="eisup-bighead",type="IP"
prov-add:RTTRNKGRP:name="9300",type=4
prov-add:RTTRNK:weightedtg="OFF",name="eisup-bighead",trnkgrpnum=9300
prov-add:RTLIST:name="rtlist-bighead",rtname="eisup-bighead"
mml> prov-add:TRNKGRPPROP:name="9300",QSIGTunnelVariant="1"
mml> prov-add:trnkgrpprop:name="9300",OwnRoutingNumber="488"
Step 9
Step 10
Step 11
Add a result of the ROUTE result type for the DPNSS media gateway:
mml> numan-add:RESULTSET:custgrpid="1111",name="dpnss-rs-1"
mml> numan-add:RESULTTABLE:custgrpid="1111",name="dpnss-route1",resulttype="ROUTE",
dw1="rtlist-dpnss-3745",setname="dpnss-rs-1"
mml> numan-add:BDIGTREE:custgrpid="1111",callside="originating",digitstring="3",
setname="dpnss-rs-1"
Step 12
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-88
OL-1110-23
Chapter 5
mml> numan-add:RESULTTABLE:custgrpid="1111",name="self-result02",
resulttype="RTRN_START_ANAL",dw1="2",setname="self-set02"
mml> numan-add:BDIGTREE:custgrpid="1111",callside="originating",digitstring="02",
setname="self-set02"
Step 13
Add the result of the ROUTE result type for the CCM whose routing number for is 446:
mml> numan-add:RESULTSET:custgrpid="1111",name="446"
mml> numan-add:RESULTTABLE:custgrpid="1111",name="446",resulttype="ROUTE",
dw1="rtlist-bighead",setname="446"
mml> numan-add:BDIGTREE:custgrpid="1111",callside="originating",digitstring="446",
setname="446"
Step 14
End the provisioning session as described in Stopping a Configuration Session section on page 4-11.
Step 2
Step 3
Step 4
Step 5
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-89
Chapter 5
mml>
mml>
mml>
mml>
Step 6
prov-add:RTTRNKGRP:name="1100",type=1
prov-add:RTTRNK:name="rt-ss7-1",trnkgrpnum=1100
prov-add:RTLIST:name="rtlist-ss7-1",rtname="rt-ss7-1",distrib="OFF"
prov-ed:TRNKGRPPROP:name="1100",custgrpid="1111",MGCdomain="192.0.2.42"
Step 7
prov-add:TRNKGRP:name="9300",clli="EISUP2B",svc="eisup-bighead",type="IP"
prov-add:RTTRNKGRP:name="9300",type=4
prov-add:RTTRNK:weightedtg="OFF",name="eisup-bighead",trnkgrpnum=9300
prov-add:RTLIST:name="rtlist-bighead",rtname="eisup-bighead"
mml> prov-add:TRNKGRPPROP:NAME="9300",QSIGTunnelVariant="1"
mml> prov-add:TRNKGRPPROP:NAME="9300",OwnRoutingNumber="545"
Step 8
Step 9
numan-add:DIALPLAN:custgrpid="1111",overdec="NO"
numan-add:DIGMODSTRING:custgrpid="1111",name="ccm02",digstring="6"
numan-add:DIGMODSTRING:custgrpid="1111",name="ccm3003",digstring="02"
numan-add:DIGMODSTRING:custgrpid="1111",name="a6",digstring="6"
Step 10
Step 11
Step 12
Add the result of the ROUTE result type for the Cisco PGW 2200 Softswitch whose routing number for
is 545:
mml> numan-add:RESULTSET:custgrpid="1111",name="545"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-90
OL-1110-23
Chapter 5
mml> numan-add:RESULTTABLE:custgrpid="1111",name="545",resulttype="RTRN_START_ANAL",
dw1="3",setname="545"
mml> numan-add:BDIGTREE:custgrpid="1111",callside="originating",digitstring="545",
setname="545"
Step 13
End the provisioning session as described in Stopping a Configuration Session section on page 4-11.
Follow Step 1 to Step 11 in the previous procedure described in Provisioning Route Optimization
Initiated by the Cisco PGW 2200 Softswitch section on page 5-89.
Step 2
Add the result of the ROUTE result type for the CCM whose routing number for is 446:
mml> numan-add:RESULTSET:custgrpid="1111",name="446"
mnl> numan-add:RESULTTABLE:custgrpid="1111",name="446",resulttype="ROUTE",
dw1="rtlist-bighead",setname="446"
mml> numan-add:BDIGTREE:custgrpid="1111",callside="originating",digitstring="446",
setname="446"
Step 3
End the provisioning session as described in Stopping a Configuration Session section on page 4-11.
Follow Step 1 to Step 6 in the previous procedure described in Provisioning Route Optimization
Transit section on page 5-86.
Step 2
Step 3
prov-add:sigsvcprop:name="eisup-bighead",AllowH323Hairpin="1"
prov-add:sigsvcprop:name="eisup-bighead",FeatureTransparencyDisabled="0"
prov-add:sigsvcprop:name="eisup-bighead",H323AdjunctLink="1"
prov-add:sigsvcprop:name="eisup-bighead",OOverlap="1"
prov-add:sigsvcprop:name="eisup-bighead",QSIGTunnelVariant="1"
prov-add:sigsvcprop:name="eisup-bighead",TOverlap="0"
prov-add:sigsvcprop:name="eisup-bighead",EnableCCBSpathReservation="1"
prov-add:trnkgrp:name="9300",clli="EISUP2B",svc="eisup-bighead",type="IP"
prov-add:rttrnkgrp:name="9300",type=4
prov-add:rttrnk:weightedtg="OFF",name="eisup-bighead",trnkgrpnum=9300
prov-add:rtlist:name="rtlist-bighead",rtname="eisup-bighead"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-91
Chapter 5
mml>
mml>
mml>
mml>
mml>
Step 4
prov-add:trnkgrpprop:name="9300",FeatureTransparencyDisabled="0"
prov-add:trnkgrpprop:name="9300",CustomerVPNid="longan"
prov-add:trnkgrpprop:name="9300",customervpnoffnettblnum="5"
prov-add:trnkgrpprop:name="9300",customervpnonnettblnum="5"
prov-add:trnkgrpprop:name="9300",EnableCCBSpathReservation="1"
Step 5
Step 6
Step 7
End the provisioning session as described in Stopping a Configuration Session section on page 4-11.
Step 2
Step 3
Add the MGCP signaling path, the association, and the DPNSS path:
mml> prov-add:mgcppath:name="mgcp-stim-dpnss001",desc="MGCP",extnode="sh-stim-001"
mml> prov-add:iplnk:name="sh-stim-dpnss1",desc="link 1 to
sh-stim-001",svc="mgcp-stim-dpnss001",ipaddr="IP_Addr1",port=2427,peeraddr="192.0.2.35",
peerport=2427,pri=1,iproute=""
mml> prov-add:sigsvcprop:name="mgcp-stim-dpnss001",
mgcpDomainNameRemote="s0/ds1-0/1@192.0.2.252"
mml> prov-add:association:name="stim-dpnss1",desc="",extnode="sh-stim-001",sgp="",
type="IUA",ipaddr1="IP_Addr1",port=9903,peeraddr1="192.0.2.36",peerport=9903,iproute1="",
rcvwin=18000,maxinitretrans=10,maxinitrto=2000,maxretrans=5,cumsackto=300,bundleto=100,
minrto=300,maxrto=3000,hbto=2000,maxretransdest=3
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-92
OL-1110-23
Chapter 5
mml>
mml>
mml>
mml>
mml>
prov-add:sigsvcprop:name="dpnss-pathin1",CustomerVPNOnNetTblNum="5"
prov-add:sigsvcprop:name="dpnss-pathin1",CustomerVPNOffNetTblNum="5"
prov-add:sigsvcprop:name="dpnss-pathin1",customervpnid="1"
prov-ed:sigsvcprop:name="dpnss-pathin1",ownroutingnumber="488"
prov-ed:sigsvcprop:name="dpnss-pathin1",MgcpBehavior="2",name="mgcp-stim-dpnss001"
Step 4
Step 5
Add the Cisco HSI external node, and the EISUP signaling path:
mml> prov-add:extnode:name="sh-bighead",desc="HSI sh-bighead",type="H323",
isdnsigtype="N/A",group=0
mml> prov-add:eisuppath:name="eisup-bighead",desc="EISUP to HSI sh-bighead",
extnode="sh-bighead",custgrpid="1111",origlabel="",termlabel=""
mml> prov-add:iplnk:name="ip-bighead",desc="IP lnk to HSI sh-bighead",
svc="eisup-bighead",ipaddr="IP_Addr1",port=8003,peeraddr="192.0.2.36",
peerport=8003,pri=1,iproute=""
mml>
mml>
mml>
mml>
mml>
mml>
Step 6
Step 7
prov-add:sigsvcprop:name="eisup-bighead",AllowH323Hairpin="1"
prov-add:sigsvcprop:name="eisup-bighead",FeatureTransparencyDisabled="0"
prov-add:sigsvcprop:name="eisup-bighead",H323AdjunctLink="1"
prov-add:sigsvcprop:name="eisup-bighead",OOverlap="1"
prov-add:sigsvcprop:name="eisup-bighead",QSIGTunnelVariant="0"
prov-add:sigsvcprop:name="eisup-bighead",TOverlap="0"
prov-add:trnkgrp:name="9300",clli="EISUP2B",svc="eisup-bighead",type="IP"
prov-add:rttrnkgrp:name="9300",type=4
prov-add:rttrnk:weightedtg="OFF",name="eisup-bighead",trnkgrpnum=9300
prov-add:rtlist:name="rtlist-bighead",rtname="eisup-bighead"
Step 8
Add results, a B digit tree entry, and digit modifications for Cisco HSI:
mml> numan-add:resultset:custgrpid="1111",name="eisup-set4"
mml> numan-add:resulttable:custgrpid="1111",name="eisup-result4",resulttype="ROUTE",
dw1="rtlist-bighead",setname="eisup-set4"
mml> numan-add:resulttable:custgrpid="1111",name="tab33",resulttype="BNBRMODMWI",
dw1="mwion", dw2="wioff",setname="rset33"
mml> numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="4",
setname="eisup-set4"
mml> numan-add:digmodstring:custgrpid="1111",name="mwioff",digstring="5719"
mml> numan-add:digmodstring:custgrpid="1111",name="mwion",digstring="5718"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-93
Chapter 5
Step 9
End the provisioning session as described in Stopping a Configuration Session section on page 4-11.
Follow Step 1 to 4 in the previous procedure described in Provisioning Message Waiting Indicator (with
no QSIG Tunneling) section on page 5-92.
Step 2
Add the Cisco HSI external node and the EISUP signaling path:
mml> prov-add:extnode:name="sh-bighead",desc="HSI sh-bighead",type="H323",
isdnsigtype="N/A", group=0
mml> prov-add:eisuppath:name="eisup-bighead",desc="EISUP to HSI sh-bighead",
extnode="sh-bighead",custgrpid="1111",origlabel="",termlabel=""
mml> prov-add:iplnk:name="ip-bighead",desc="IP lnk to HSI sh-bighead",svc="eisup-bighead",
ipaddr="IP_Addr1",port=8003,peeraddr="192.0.2.37",peerport=8003,pri=1,iproute=""
Step 3
Step 4
Step 5
prov-add:sigsvcprop:name="eisup-bighead",AllowH323Hairpin="1"
prov-add:sigsvcprop:name="eisup-bighead",FeatureTransparencyDisabled="0"
prov-add:sigsvcprop:name="eisup-bighead",H323AdjunctLink="1"
prov-add:sigsvcprop:name="eisup-bighead",OOverlap="1"
prov-add:sigsvcprop:name="eisup-bighead",OwnRoutingNumber="545"
prov-add:sigsvcprop:name="eisup-bighead",QSIGTunnelVariant="1"
prov-add:sigsvcprop:name="eisup-bighead",TOverlap="0"
prov-add:trnkgrp:name="9300",clli="EISUP2B",svc="eisup-bighead",type="IP"
prov-add:rttrnkgrp:name="9300",type=4
prov-add:rttrnk:weightedtg="OFF",name="eisup-bighead",trnkgrpnum=9300
prov-add:rtlist:name="rtlist-bighead",rtname="eisup-bighead"
mml>
mml>
mml>
mml>
prov-add:trnkgrpprop:name="9300",FeatureTransparencyDisabled="0"
prov-add:trnkgrpprop:name="9300",CustomerVPNid="longan"
prov-add:trnkgrpprop:name="9300",customervpnoffnettblnum="5"
prov-add:trnkgrpprop:name="9300",customervpnonnettblnum="5"
Step 6
Add results and a B digit tree entry in the dial plan 1111:
mml> numan-add:resultset:custgrpid="1111",name="eisup-set4"
mml> numan-add:resulttable:custgrpid="1111",name="eisup-result4",resulttype="ROUTE",
dw1="rtlist-bighead",setname="eisup-set4"
mml> numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="4",
setname="eisup-set4"
Step 7
End the provisioning session as described in Stopping a Configuration Session section on page 4-11.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-94
OL-1110-23
Chapter 5
prov-add:trnkgrpprop:name="9300",FeatureTransparencyDisabled="0"
prov-add:trnkgrpprop:name="9300",CustomerVPNid="longan"
prov-add:trnkgrpprop:name="9300",customervpnoffnettblnum="5"
prov-add:trnkgrpprop:name="9300",customervpnonnettblnum="5"
Create the dial plan by using the following MML commands in an open provisioning session:
mml> numan-add:dialplan:custgrpid="T002"
Step 2
Add entries in the customer VPN ID table and the result set:
mml> numan-add:customervpnid:custgrpid="T002",name="Abbey"
mml> numan-add:resultset:custgrpid=T002,name=VpnCust1
mml> numan-add:resulttable:custgrpid="T002",name="result1",resulttype="ORIG_VPN_ID",
dw1="Abbey",dw2="5",dw3="5",setname="VpnCust1"
Step 3
Step 4
Step 5
End the provisioning session as described in Stopping a Configuration Session section on page 4-11.
Step 2
Step 3
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-95
Chapter 5
Step 4
End the provisioning session as described in Stopping a Configuration Session section on page 4-11.
Step 2
Step 3
Step 4
Step 5
Note
End the provisioning session as described in Stopping a Configuration Session section on page 4-11.
If QBE is to be used for CCBS instead of tunnel, change the value of the
*.DisableCCBSoverTunneledQSIG property to a value of 1 in the XECfgParm.dat file.
Add entries in the ported number table by using the following MML commands:
mml> numan-add:porttbl:digitstring="9981234",routenum="44",minlength=6,maxlength=20
mml> numan-add:porttbl:digitstring="9991234",routenum="44",minlength=6,maxlength=20
Step 2
Note
If full A-number matches the digit string provisioned in the CLI parameter, the
Cisco PGW 2200 Softswitch chooses the new dial plan provisioned in the newdp parameter.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-96
OL-1110-23
Chapter 5
mml> numan-add:anumdpsel:custgrpid="1111",cli="99712345",newdp="2222"
Step 3
Add the result of the E_PORTED_NUM result type in dial plan 1111:
mml> numan-add:resultset:custgrpid=1111,name=rtsetlnp99812
mml> numan-add:resulttable:custgrpid="1111",name="rtblnp99812",resulttype="E_PORTED_NUM",
setname="rtsetlnp99812
Step 4
Add the result of the DB_XLATED result type in dial plan 1111:
mml> numan-add:resulttable:custgrpid="1111",name="rtblnp99912",resulttype="DB_XLATED",
dw1=6,dw2="dp01",dw3="dp02",setname="rtsetlnp99812
Note
Step 5
Dw1 = 6 indicates that any longest match search searches down from the currently received
number of digits to a digit length of 6 for potential matches. Dw2 & 3 respectively, indicate the
dial plan to move into according to matching (dp01) or not matching (dp02).
Add the result of the A_NUM_DP_TABLE result type in dial plan 1111:
mml> numan-add:resultset:custgrpid=1111,name=rtsetdpsel996
mml> numan-add:resulttable:custgrpid="1111",setname="rtsetdpsel996",name="rttbldpsel996",
resulttype="A_NUM_DP_TABLE",dw1="5
Note
Step 6
Dw1 = 5 indicates that a database longest match query searches down from the currently
received number of digits to a digit length of 5 for potential matches. If dw1 is omitted or set to
zero, the existing functionality with exact matching applies.
Step 7
End the provisioning session as described in Stopping a Configuration Session section on page 4-11.
Global Titles
You can find the provisioning procedure in the Provisioning Global Titles section of Chapter 4,
Provisioning Dial Plans with MML, in Cisco PGW 2200 Softswitch Release 9 Dial Plan Guide (through
Release 9.7).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-97
Chapter 5
MGC
(PGW)
EISUP
MGC
(PGW)
SS7
SS7
H.248
IP/MPLS
Core Network
H.248
SS7 Network
SS7 network
TGW
(MG)
TGW
(MG)
RTP
Voice
Voice
250271
PSTN Network
Phone
Phone
Before you provision H.248 protocol feature, configure the following parameters in the XECfgParm.dat
file:
H248.maxNumH248Links = 500
H248.maximumActionsInTransaction=64
H248.localMID = cisco.com
H248.MgcHeaderAddrType = 2
To provision H.248 protocol on the Cisco PGW 2200 Softswitch, perform the following steps:
Step 1
Step 2
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-98
OL-1110-23
Chapter 5
Note
Unlike MGCP, only one UDP link is allowed between the Cisco PGW 2200 Softswitch and the
media gateway for H.248 sigPath.
H.248 sigPath based on SCTP Transport
mml> prov-add:EXTNODE:NAME="h248-VXSM-02",DESC="VXSM-02",TYPE="VXSM"
mml> prov-add:H248PATH:NAME="h248-sigpath-sctp",DESC="Service to H248",EXTNODE="
h248-VXSM-02"
mml> prov-add: iproute:name="iproute-h248-1",dest="192.0.2.39",
netmask="255.255.255.0", ipaddr="IP_Addr1",nexthop="209.165.200.240",pri=1
mml> prov-add: iproute:name="iproute-h248-2",dest="192.0.2.39",
netmask="255.255.255.0", ipaddr="IP_Addr2",nexthop="209.165.201.16",pri=2
mml> prov-add:association:NAME="h248-sctp-2",DESC="link 1 to VXSM-02",type="H248",
sgp="N/A",ipaddr1="IP_Addr1", port=2944,iproute1="iproute_h248_1",ipaddr2="IP_Addr2",
port=2944,iproute1="iproute_h248_2",peeraddr1="192.",extnode="h248-VXSM-02"
Step 3
Step 4
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-99
Chapter 5
Lawful Intercept
Step 5
Note
Step 6
End the provisioning session as described in Stopping a Configuration Session section on page 4-11.
Lawful Intercept
The lawful intercept (LI) feature on the Cisco PGW 2200 Softswitch allows personnel authorized by a
Law Enforcement Agency (LEA) to intercept data from targeted calls and send the call data to an LI
Mediation Device.
Lawful Intercept on Cisco PGW 2200 Softswitch works within the architecture of the Cisco Service
Independent Intercept (SII).
Figure illustrates how the Cisco PGW 2200 Softswitch fits into the Cisco Service Independent Intercept
(SII) architecture.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-100
OL-1110-23
Chapter 5
Cisco PGW 2200 Softswitch in Cisco Service Independent Intercept (SII) Architecture
Administration
centre
LI
mediation
device
H.225 RAS
GK
Content
CCM/ITS
HI1
HI2
HI3
Call Data to Med.
Device (RADIUS)
Provisioning
to PGW (MML)
PGW2200
LEA/LEMF
monitoring
centre
SS7
STP
SNMPv3
Content
SNMPv3
PSTN
MGCP
IP
H.225 CC,
H.245
Target identity
IP
Content
Target identity
V
aggregation
router
MGX8850
230478
Figure 5-10
IMT
Cisco SII dissociates call content requests from the signaling architecture. This is done by having the LI
Mediation Device make call content requests through the SNMPV3 from the voice gateway.
When a call is made on the Cisco PGW 2200 Softswitch that matches a trunk group, full number, or
partial number on the target list, the Cisco PGW 2200 Softswitch sends the call data to the LI Mediation
Device. The LI Mediation Device is triggered when it receives the call data from the
Cisco PGW 2200 Softswitch.
There are two different types of commands that you can use to interact with the
Cisco PGW 2200 Softswitch when implementing the LI features. The first set of commands are used by
the service provider organization to provision the Cisco PGW 2200 Softswitch to be able to handle
lawful intercept or wiretap. These provisioning commands involve adding LI sigpaths and IP links.
The second set of commands is used by someone authorized by the LEA to add, modify, delete and
retrieve wiretapped numbers.
Configure the Cisco PGW 2200 Softswitch with the IP addresses of the Mediation Device(s) that it will
contact for call interception.
Step 2
Edit the XECfgParm.dat file and set the LISupport parameter value to enable. The default value is
*.LISupport=disable.
Step 3
Note
Provision a wiretap Channel Controller and associated IP Link before adding wiretap entries. Do
not use the user ID meant for controlling wiretap entries (liusr).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-101
Chapter 5
Location Mapping
Step 4
Step 5
Step 6
Note
This MML command defines an IP link to the LI mediation device and associates an LI sigPath
to the IP link.
The local_address and local_port are parameters in the existing Cisco PGW 2200 Softswitch two-way
communications IP link object. In this case, the LI Channel Controller does not use the local_port, thus
the local port value is ignored.
Step 7
End the provisioning session as described in Stopping a Configuration Session section on page 4-11.
Location Mapping
Location mapping on the Cisco PGW 2200 Softswitch allows you to
Map to different cause and location values based on received cause values and location values.
Map to a different cause value based on the received cause value and location values.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-102
OL-1110-23
Chapter 5
Map cause value to new values without changing location values (existing).
Map to a new cause value and location value based on received cause value.
Map a location value to new values without changing cause values, with the use of wildcard of cause
value.
Add the dial plan, Nat1, in an open provisioning session by using the following MML command:
mml> numan-add:dialplan:custgrpid="Natl"
Step 2
Step 3
Step 4
Note
Step 5
Dw1 specifies the cause value 8. Dw2 specifies the location value 7.
Associate the result set, chCause, with the location block 1 and location block value 2 in the location
table:
mml> numan-add:location:custgrpid="Natl",locationblock=1,blockvalue=2, setname=chCause"
Step 6
Note
In this procedure, if the cause code in the Release message is 8, and the mapped-to internal
location value from the external location value in Release message is 3, then the
Cisco PGW 2200 Softswitch uses the chCause result set. The blockvalue in numan-add:location
should be one less than the intended internal value.
Note
For detailed information on Cause and Location, see the Cause Analysis section in Chapter 1,
Dial Plan and Routing, of the Cisco PGW 2200 Softswitch Release 9 Dial Plan Guide (through
Release 9.7).
Add an entry in the cause table, with cause value 8, and location block 1:
mml> numan-add:cause:custgrpid="Natl",causevalue=8,locationblock=1
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-103
Chapter 5
Location Mapping
Note
For any cause value that has no value entered in the Cause table, or has a value of 0, the default
Cause table is used.
Add the result set, chCause, in an open provisioning session by using the following MML command:
mml> numan-add:resultset:custgrpid="Natl",setname="chCause"
Step 2
Step 3
Associate the result set, chCause, with the location block 1 and location block value 2 in the location
table:
mml> numan-add:location:custgrpid="Natl",locationblock=1,blockvalue=2,setname=chCause"
Note
Step 4
The blockvalue in numan-add:location should be one less than the intended internal value. For
detailed information on Cause and Location, see the Cause Analysis section in Chapter 1, Dial
Plan and Routing, of the Cisco PGW 2200 Softswitch Release 9 Dial Plan Guide (through
Release 9.7).
Add an entry in the cause table, with cause value 1, and location block 1:
mml> numan-add:cause:custgrpid="Natl",causevalue=1,locationblock=1
Add the result set, chgCause, in an open provisioning session by using the following MML command:
mml> numan-add:resultset:custgrpid="Natl",name="chgCause"
Step 2
Step 3
Associate the result set, chgCause, with the cause value 40:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-104
OL-1110-23
Chapter 5
mml> numan-add:cause:custgrpid="Natl",causevalue=40,setname="chgCause"
Note
On the Cisco PGW 2200 Softswitch, internal cause and location values are used for provisioning. In this
example, SIP cause 408 and 501 both map to internal cause 40 IC_RECOVERY_ON_TIMER_EXPIRY.
Internal cause 40 is mapped to internal cause 91 IC_SUB_ABSENT, which is cause 21 in SS7. For a
complete list of all SIP, ISUP, and Cisco PGW 2200 Softswitch internal cause and location values and
how they are mapped to each other, see Cisco Media Gateway Controller Software Release 9 Dial Plan
Guide.
Add the result set, chCause2, in an open provisioning session by using the following MML command:
mml> numan-add:resultset:custgrpid="1111",name="chCause2"
Step 2
Add cause analysis data (cause value 40 and location value 4):
mml> numan-add:resulttable:custgrpid="1111",setname="chCause2",resulttype="CAUSE",
name="cause1",dw1=40,dw2=4
Step 3
Associate the result set, chCause2, with the location block 1 and location block value 2 in the location
table:
mml> numan-add:location:custgrpid="1111",locationblock=1,blockvalue=2,setname=chCause2"
Note
Step 4
The blockvalue in numan-add:location should be one less than the intended internal value. For
detailed information on Cause and Location, see the Cause Analysis section in Chapter 1, Dial
Plan and Routing, of the Cisco PGW 2200 Softswitch Release 9 Dial Plan Guide (through
Release 9.7).
Add an entry in the cause table, with cause value 0, and location block 1:
mml> numan-add:cause:custgrpid="1111",causevalue="0",locationblock=1
Add the result set, chCause1, in an open provisioning session by using the following MML command:
mml> numan-add:resultset:custgrpid="custid",name="chCause1"
Step 2
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-105
Chapter 5
Step 3
Add a SIP signaling path in an open provisioning session by using the following MML command:
mml> prov-add:sippath:name="sippath-1",mdo="IETF_SIP",desc="SIP sigpath"
Step 2
Note
You can create up to 2 SIP IP links and edit them to add up to 100 new listening ports per SIP
IP link.
Note
You must define all SIP IP links with the same set of listening ports. In the preceding example,
the port parameter was edited twice, one per SIP IP link.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-106
OL-1110-23
Chapter 5
Step 3
Note
Step 4
You must apply the same set of nonstandard port numbers to each SIP link. When you use a
nonstandard port number, you must apply the prov-ed:SIPLNK command to each SIP link you
define.
Step 5
Note
In this step, you define the traffic that the Cisco PGW 2200 Softswitch forwards to the new trunk
group. You can define the incoming SIP traffic based on incoming IP address, subnet mask, port
number (the SIP port on the PGW), or a combination of these elements.
Step 6
Step 7
Enable inbound trunk groups and specify that the Cisco PGW 2200 Softswitch discards incoming traffic
that does not match existing incoming IP trunk groups:
mml> prov-add:sigsvcprop:name="sippath-1",ipinscreening=1
Note
The ipinscreening property specifies whether the Cisco PGW 2200 Softswitch permits traffic
that does not match defined incoming IP trunk group properties. For detailed information on this
property, see Chapter 6, Properties, of Cisco PGW 2200 Softswitch Release 9 MML Command
Reference.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-107
Chapter 5
Add an Cisco PGW 2200 Softswitch external node in an open provisioning session by using the
following MML command:
mml> prov-add:extnode:name="pgw-1",type="MGC",desc="External Node PGW2200-1"
Step 2
Step 3
Add an IP link:
mml> prov-add:iplnk:name="eisuplnk-1",desc="Iplnk#1 to PGW-1",svc="eisuppath-1",
ipaddr="IP_Addr1",port=5001,peeraddr="192.0.2.43",peerport=5001, pri=1,iproute=""
Step 4
Step 5
Note
In this step, you define the traffic that the Cisco PGW 2200 Softswitch forwards to the new trunk
group. You can define the incoming EISUP traffic based on incoming IP address, subnet mask,
port number (the SIP port on the PGW), or a combination of these elements.
mml> prov-add:ipinmapping:name="eisupinmapping-1",sigsvc="eisuppath-1",
allowedIP="192.0.2.43",trnkgrpNum=2000
Step 6
Enable the inbound trunk group and specify that the Cisco PGW 2200 Softswitch discards incoming
traffic that does not match existing incoming IP trunk groups:
mml> prov-add:sigsvcprop:name="eisuppath-1",ipinscreening=1
Note
The ipinscreening property specifies whether the Cisco PGW 2200 Softswitch permits traffic
that does not match defined incoming IP trunk group properties. For detailed information on this
property, see Chapter 6, Properties, of Cisco PGW 2200 Softswitch Release 9 MML Command
Reference.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-108
OL-1110-23
Chapter 5
If the Cisco PGW 2200 Softswitch sends an IP address to the HSI over E-ISUP, the HSI sends a SETUP
directly to the endpoint. In addition, the Cisco PGW 2200 Softswitch stores the H.323 destination IP
address in the Cisco PGW 2200 Softswitch Call Detail Record (CDR).
Cisco PGW 2200 Softswitch Support of HSI non-RAS Mode enables a Cisco PGW 2200 Softswitch to
be deployed with a connected Cisco HSI without a gatekeeper in networks that do not require admission
or location of the H.323 endpoint. Cisco PGW 2200 Softswitch Support of HSI non-RAS Mode is also
used when selection of the endpoint does not benefit from H.323 mechanisms such as Resource
Availability Indication (RAI). Examples of such deployments include Cisco Unified Communications
Manager (CUCM), H.323 ITS, or cases in which an H.323 gateway provides the only connection to a
PBX.
Modify the value of the h323adjunctlink property to 1 to indicate the EISUP signaling path between the
Cisco PGW 2200 Softswitch and the Cisco HSI in an open provisioning session by using the following
MML command:
mml> prov-add:SIGSVCPROP:name="eisupsvc1",h323adjunctlink="1"
Step 2
Note
When two destinations are used for a route trunk group, the reattempt value must be set to 1, as
in the previous MML command.
Configure gatekeeper mode for the trunk group
mml> prov-add:TRNKGRPPROP:name="111",H323Destination="0.0.0.0"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-109
Chapter 5
PSTN
PGW 2200
SIP
273682
Figure 5-11
Set the value of the trunk group property CCOrigin to 44 on the origination side by using the following
MML command:
mml> prov-ed:trnkgrpprop:name=1000,ccorgin=44
Step 2
Set the value of the trunk group property ADigitCCPrefix to 1, and BDigitCCPrefix to 1 on the
terminating side:
Note
Setting ADigitCCPrefix to 1 enables the Cisco PGW 2200 Softswitch to add the prefix country
code to both the PN and CgPn. Setting BDigitCCPrefix to 1 enables
Cisco PGW 2200 Softswitch to add the prefix country code to the called number.
mml> prov-ed:trnkgrpprop:name=2222,adigitccprefix=1
mml> prov-ed:trnkgrpprop:name=2222,bdigitccprefix=1
Step 3
Add the required country code digit strings for B-number modification:
mml> numan-add:digmodstring:custgrpid="t001",name="ccUK",digstring="44"
Step 4
Add the result of the CC_DIG result type to the dial plan (identified as t001 in this example):
mml> numan-add:resulttable:custgrpid="t001",name="result2",resulttype="CC_DIG", dw1=UK,
setname="set5"
Step 5
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-110
OL-1110-23
Chapter 5
Setting MapCLItoSipHeader to 0 enables the Cisco PGW 2200 Softswitch to map the PN to the
display name and the CgPn to the user name in the From Header of the SIP message. If you set
the property MapCLItoSipHeader to 3, the Cisco PGW 2200 Softswitch maps the PN to the
display name and user name in the From header of the SIP message and the CgPn to the
P-Asserted-ID header.
Note
Step 6
Set the value of the cgpnInclude property to either 0 or 1 to alter number display behavior when the
presentation indicator is ''presentation restricted.''
mml> prov-add:grprofile:name=grprof,cgpninclude=0
mml> prov-add:trnkgrpprof:name=2222,grprofile=grprof
Note
A service provider sets the property cgpnInclude to meet the requirements of its network:
If you set cgpnInclude = 0, and the SIP network is not trusted, the From header has SIP URI as:
Anonymous <sip:Anonymous@anonymous.invalid>
If you set cgpnInclude = 1, and the SIP network is trusted, and honors the anonymous setting by not
passing the CLI to the SIP end point, the From header has URI as Anonymous
<sip:CGPN@PGW_HOST>
PSTN
PGW 2200
273683
Figure 5-12
Set the value of the InhibitSipFromMapping property to 3 on the originating side by using the following
MML command:
mml> prov-ed:trnkgrpprop:name="2000",custgrpid="DP00",InhibitSipFromMapping="3",
ADigitCCPrefix="1
Step 2
Set the value of the ADigitCCRm (country code to remove in the A-number) and BDigitCCRm (country
code to remove in B-number) to 44:
mml> prov-add:trnkgrpprop:name="1000",adigitccrm="44",bdigitccrm="44"
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-111
Chapter 5
Step 3
Set the value for the trunk group property CliSelectionForCodeOfPractice3 to provision the level of
calling line identity (CLI).
mml> prov-ed:trnkgrpprop:name="1000",cliselectionforcodeofpractice3="2
For details on parameter descriptions and configuration procedures, see Cisco PGW 2200 Softswitch
Release 9 Software Installation and Configuration Guide (through Release 9.7).
To enable the RADIUS enhancement for accounting, perform the following steps:
Step 1
Add a RADIUS accounting server as an external node in an open provisioning session by using the
following MML command:
mml> prov-add:EXTNODE:NAME="ranode",TYPE="RACLUSTER",DESC="Radius accounting server
cluster"
Step 2
Add a signaling path to a RADIUS accounting server cluster (made up of one or multiple RADIUS
servers):
mml> prov-add:RAPATH:NAME="racluster",DESC="Radius accounting server cluster",
EXTNODE="ranode"
Step 3
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-112
OL-1110-23
Chapter 5
SIP and ISUP Interworking for Call Hold and Terminal Portability
This feature supports the message mapping between SIP and ISUP for call hold and terminal
portability (TP) supplementary services on the Cisco PGW 2200 Softswitch. The implementation is
based on Q.1912.5 Annex B.10 for Call Hold and Annex B.13 for Terminal Portability (TP). ISUP and
HSI interworking for Call hold and TP is also supported. The ISUP call hold and TP messages are
mapped to EISUP notification message.
To provision SIP and ISUP interworking for call hold and TP, perform the following steps:
Step 1
Add a SIP signaling path in an open provisioning session by using the following MML command:
mml> prov-add:SIPPATH:NAME="sip-path",DESC="Nothing defined",MDO="IETF_SIP"
mml> prov-add:SIPLNK:NAME="sip-lnk",DESC="notSet",SVC="sip-path",
IPADDR="Virtual_IP_Addr1",PORT=5060,PRI=1
Step 2
Step 3
Step 4
Step 5
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-113
Chapter 5
For detailed information on property descriptions, see Chapter 6, Properties, of Cisco PGW 2200
Softswitch Release 9 MML Command Reference.
To provision SIP overlap signaling, perform the following steps:
Step 1
Add the originating trunk group, 444, and the terminating trunk group, 666 using the existing SIP
signaling path, sippath1:
mml> prov-add:trnkgrp:name=444,type=SIP_IN,svc=sippath1
mml> prov-add:trnkgrp:name=666,type=IP_SIP,svc=sippath1
Step 2
Step 3
Step 4
The Cisco PGW 2200 Softswitch maps the calling party number to the SIP From header and ignores the
ACgPN if it is presented in the ISUP message. If Presentation in the calling party number is restricted,
the Cisco PGW 2200 Softswitch maps the calling party number to the SIP From header as Anonymous
<sip:Anonymous@anonymous.invalid>.
To provision SIP remote party ID and P-asserted support, perform the following steps:
Step 1
Modify the value of the mapclitosipheader property to 0 in an open provisioning session by using the
following MML command:
mml> prov-ed:sigsvcprop:name="sip-path",mapclitosipheader="0"
Note
The default value of mapclitosipheader is 0. If this property is not modified, or you are
provisioning from "new", this command is not needed.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-114
OL-1110-23
Chapter 5
Step 2
Step 3
Scenario 2
The Cisco PGW 2200 Softswitch maps the calling party number to the SIP From header and ignores the
ACgPN if it is presented in the ISUP message. If Presentation in the calling party number is restricted,
the Cisco PGW 2200 Softswitch maps the calling party number to the SIP From header as Anonymous
<sip:CGPN@PGW_HOST>.
To provision SIP remote party ID and P-asserted support, perform the following steps:
Step 1
Modify the value of the mapclitosipheader property to 0 in an open provisioning session by using the
following MML command:
mml> prov-ed:sigsvcprop:name="sip-path",mapclitosipheader="0"
Note
Step 2
The default value of mapclitosipheader is 0. If this property is not modified, or you are
provisioning from "new", this command is not needed.
Step 3
Scenario 3
The Cisco PGW 2200 Softswitch maps the calling party number to the SIP From header and the
P-Asserted ID header. If ACgPN is presented and Presentation is allowed, the
Cisco PGW 2200 Softswitch overwrites the SIP From header with the ACgPN. If Presentation is
restricted in ACgPN, the Cisco PGW 2200 Softswitch overwrites the SIP From header as Anonymous
<sip:Anonymous@anonymous.invalid>. If Presentation is NA in ACgPN, the
Cisco PGW 2200 Softswitch does not overwrite the SIP From header.
To provision SIP remote party ID and P-asserted support, perform the following steps:
Step 1
Modify the value of the mapclitosipheader property to 3 in an open provisioning session by using the
following MML command:
mml> prov-ed:sigsvcprop:name="sip-path",mapclitosipheader="3"
Step 2
Step 3
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-115
Chapter 5
Scenario 4
The Cisco PGW 2200 Softswitch maps the calling party number to the SIP From header and the Remote
Party ID header. If ACgPN is presented and Presentation is allowed, the Cisco PGW 2200 Softswitch
overwrites the SIP From header with the ACgPN. If Presentation is restricted in ACgPN, the
Cisco PGW 2200 Softswitch overwrites the SIP From header as Anonymous
<sip:Anonymous@anonymous.invalid>. If Presentation is NA in ACgPN, the
Cisco PGW 2200 Softswitch does not overwrite the SIP From header.
To provision SIP remote party ID and P-asserted support, perform the following steps:
Step 1
Modify the value of the mapclitosipheader property to 1 in an open provisioning session by using the
following MML command:
mml> prov-ed:sigsvcprop:name="sip-path",mapclitosipheader="1"
Step 2
Step 3
Add a result set within the dial plan 1111 in an open provisioning session by using the following MML
command:
mml> numan-add:resultset:name=rset1,custgrpid=1111
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-116
OL-1110-23
Chapter 5
Step 2
Use one of the following commands to add the result of the FACILITY result type:
Proxy mode:
mml> numan-add:resulttable:custgrpid="1111",name="fac01",resulttype="FACILITY",
dw1="1",setname="rset1"
Back the backward transit of the Redirection is not supported. The existing redirection mechanism
(that is, into Cause analysis) applies:
mml> numan-add:resulttable:custgrpid="1111",name="fac01",resulttype="FACILITY",
dw1="2",dw2="1",setname="rset1"
The backward transit of the Refer is conditionally supported if the received Refer-To header domain
in the REFER message (term side) matches the domain in the From header received within the
original INVITE on the OCC side:
mml> numan-add:resulttable:custgrpid="1111",name="fac01",resulttype="FACILITY",
dw1="3",dw2="3",setname="rset1"
Step 3
No provisioning requirements are required for NBT or NCT. This section provides a provisioning
example for iTNT on SIP trunks. Provisioning for TNT is similar to the provisioning of iTNT. However,
the route list provisioned for TNT must be a real route list, whereas the route list provisioned for iTNT
can be any existing route list. This difference is also pointed out in the following example.
Step 1
Add an overdecadic dial plan for the mid-call service in an open provisioning session by using the
following MML command:
mml> numan-add:dialplan:custgrpid="2222",overdec="yes"
Step 2
Step 3
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-117
Chapter 5
Step 4
Note
Step 5
In the preceding command, the total length of digits is 7 (including the length of the string "*8")
for intelligent blind transfer service.
Add the result of the BMODDIG result type to modify the B number:
mml> numan-add:resulttable:custgrpid="2222",name="itnt-bmod",resulttype="BMODDIG",dw1="1",
dw2="2",setname="rset-itnt"
Step 6
Add the result of the ROUTE result type to route the call:
mml> numan-add:resulttable:custgrpid="2222",name="itnt-rte",resulttype="ROUTE",
dw1="rtlist99", setname="rset-itnt"
Note
Step 7
For TNT, a real route list name is required in the above command; for iTNT, you can enter any
existing route list name in the preceding command.
Note
Step 8
The digit string "*82xxxx" invokes the mid-call service and transfers the call. The string "*8" is
removed from the digits after the digit analysis.
Step 9
Note
Step 10
Note
Step 11
For the mid-call announcement, the dw2 must be 0 and dw4 must be 2 (local and final
announcement). This announcement is played to the transferring party if the digit string is
matched.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-118
OL-1110-23
Chapter 5
Note
Step 12
The string "*9" is not a valid transferred-to number prefix. The provisioned announcement is
played when "*9" is dialed.
Step 13
For detailed information on this MML command, see Chapter 4, PROV: Commands for Provisioning
Signaling and Trunking Components, of Cisco PGW 2200 Softswitch Release 9 MML Command
Reference.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
5-119
Chapter 5
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
5-120
OL-1110-23
A P P E N D I X
The names and values associated with Cisco PGW 2200 Softswitch components, processes, and
properties are used throughout the Cisco PGW 2200 Softswitch system. Frequently, they are parameters
used in MML commands. This chapter describes these names and their associated values, in the
following sections:
Components
This section describes network element (NE) components and dial plan provisioning components. The
NE components are used with the PROV commands, and the dial plan provisioning components are used
with the NUMAN commands.
Parameter MML
Name
Parameter
Description
NAME
Unique ID of this
component and
component name
used in MML
commands
DESC
Component
description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-1
Appendix A
Components
Adapter Card
The Adapter Card component type represents a card used on the Cisco PGW 2200 Softswitch. Its MML
name is as follows:
Note
MML NameCARD
Parameter MML
Name
Parameter
Description
NAME
DESC
Component
description
TYPE
Card type
SLOT
Card Slot
MML NameAPC
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-2
OL-1110-23
Appendix A
Table A-3
DESC
Component
description
NETADDR
Network address
NETIND
Network indicator
; (0)
Association
The association component represents a Stream Control Transmission Protocol (SCTP) association,
which is the connection between the Cisco PGW 2200 Softswitch and a Cisco access server. Its MML
name is as follows:
MML NameASSOCIATION
Parameter Description
NAME
Unique component
name used in MML
commands
DESC
Component description
TYPE
Signaling Type
SGP
IPADDR1
IPADDR2
PORT
PEERADDR1
IP address.
PEERADDR2
IP address; (0.0.0.0).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-3
Appendix A
Components
Table A-4
Parameter Description
PEERPORT
EXTNODE
MML name of an
MML name of a previously configured external
external node (optional) node. Used in IUA interfaces.
IPROUTE1
IPROUTE2
RCVWIN
Number of bytes to
advertise for the local
receive window
(optional)
MAXINITRETRANS
Maximum number of
times to retransmit
SCTP INIT message
(optional)
MAXINITRTO
MAXRETRANS
CUMSACKTO
BUNDLETO
MINRTO
MAXRTO
Maximum value
allowed for the
retransmission timer
(optional)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-4
OL-1110-23
Appendix A
Table A-4
Parameter Description
HBTO
Time between
heartbeats. The
heartbeat is this value
plus the current
retransmission timeout
value (optional)
IPPRECEDENCE
Internet Protocol
Precedence. The binary
value is placed in the IP
PRECEDENCE portion
of the Type Of Service
field for outgoing SCTP
datagrams (optional)
ROUTINE000
PRIORITY001
IMMEDIATE010
FLASH011
FLASH-OVERRIDE100
CRITICAL101
INTERNET110
NETWORK; (ROUTINE)111
DSCP
Differential Service
Code Point. (Where EF
is Expedited Forward,
AF is Assured Forward,
and DP is Drop
Precedence). The binary
value is placed in the
DSCP portion of the
Type Of Service field
for outgoing SCTP
datagrams (optional)
EF101110
AF11Class 1 Low DP001010
AF12Class 1 Medium DP001100
AF13Class 1 High DP001110
AF21Class 2 Low DP010010
AF22Class 2 Medium DP010100
AF23Class 2 High DP010110
AF31Class 3 Low DP011010
AF32Class 3 Medium DP011100
AF33Class 3 High DP011110
AF41Class 4 Low DP100010
AF42Class 4 Medium DP100100
AF43Class 4 High DP100110
N/A; (N/A)
0 means disabled.
NAME
EXTNODE
TYPE
SGP
The following rules apply when you are creating or editing SCTP associations:
Only one association with a type of IUA can be assigned to an external node.
If the type of the association is IUA, the associated external node must have its ISDN signaling type
set to IUA, and that external node must be able to support IUA signaling.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-5
Appendix A
Components
If two associations have the same port value, the values of IPADDR1 and IPADDR2 must both be
the same or both different.
If the value of IPPRECEDENCE is not ROUTINE, the value of DSCP must be N/A.
If the value of DSCP is not N/A, the value of IPPRECEDENCE must be ROUTINE.
The value of MAXRTO must be greater than or equal to the value of MINRTO.
When a peer IP address (PEERADDR1 or PEERADDR2) is not on the local subnet of IPADDR1 or
IPADDR2, that peer IP address cannot be on the subnet of any other local interface, even if it is not
defined within the Cisco PGW 2200 Softswitch software.
When a peer IP address (PEERADDR1 or PEERADDR2) is not on the local subnet of IPADDR1 or
IPADDR2, an IP route (IPROUTE1 or IPROUTE2) must be specified. IPROUTE1 is specified for
IPADDR1, and IPROUTE2 is specified for IPADDR2.
When an IP route is specified, the values set in PEERADDR1 and PEERADDR2 are checked against
the DESTINATION and NETMASK values of the IP route(s) to ensure that the IP route is valid.
When an IP route is specified, its value for IPADDR must match the related IP address of the
association. In other words, IPROUTE1 should have an IPADDR that matches IPADDR1 in the
association, and IPROUTE 2 should have an IPADDR that matches IPADDR2 in the association.
When an IP route is not specified, the IP address resolved from the PEERADDR1 or PEERADDR2
parameter is checked against the defined IP routes to see if it should be assigned to one of those IP
routes. If the peer address is on the same subnet as an IP route, the link should use that IP route.
The value of PEERADDR1 cannot be 0.0.0.0 or 255.255.255.255, and the value of PEERADDR2
cannot be 255.255.255.255.
When a hostname is specified for a peer IP address, the hostname must resolve to an IP address.
PEERADDR1 and PEERADDR2 can resolve to the same IP Address. If the external node only has
one IP address and two IP addresses (IPADDR1 and IPADDR2) are defined, PEERADDR2 should
be set to the same value as PEERADDR1.
Associations, session sets, IP links, SIP links, and SS7 signaling gateway links that share a peer
address (that is, PEERADDR, PEERADDR1, or PEERADDR2) must be assigned directly or
indirectly to the same external node.
When you are deleting an association, and a NASPATH uses the same external node, a warning
message is issued to inform the you that the NASPATH must also be deleted. If it hasn't when the
provisioning session is copied or deployed, an error message is generated and the copy or
deployment is stopped.
The value of PORT cannot be set to the same value as the PORT attribute of any IP link, session set,
SIP link, or SS7 signaling gateway link.
If a value for IPADDR2 or PEERADDR2 is specified, values for IPADDR1 or PEERADDR1 must
also be specified. In other words, you cannot have one local address and two remote addresses, or
two local addresses and one remote address.
An IP link, session set, SS7 signaling gateway link, or an association with a different external or
signaling gateway node cannot use the resolved value set in PEERADDR1 or PEERADDR2.
Only one association can be defined for an SS7 signaling gateway process (SGP).
A value for EXTNODE can be defined only when the association type is IUA.
A value for SGP can be defined only when the association type is M3UA or SUA.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-6
OL-1110-23
Appendix A
The maximum number of associations with a type of M3UA is defined in the XECfgParm.dat
parameter, M3UA.maxSgp.
The maximum number of associations with a type of SUA is defined in the XECfgParm.dat
parameter, SUA.maxSgp.
AXL Server
The AXL server component represents the AXL server. Its MML name is as follows:
Note
MML NameAXLSERVR
NAME
DESC
Component description
IPADDR1
IPADDR2
PORT
PEERADDR1
IP address
PEERADDR2
IP address; (0.0.0.0).
PEERPORT
Defaults to 2750.
Defaults to 2750.
CTIPATH
IPROUTE1
IPROUTE2
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-7
Appendix A
Components
Table A-5
USERNAME
N/A
PASSWORD
N/A
Note
MML NameBRIPATH
Parameter MML
Name
Parameter Description
NAME
Unique component
name used in MML
commands
DESC
Component description
EXTNODE
MDO
ETS_300_102
Q931
ETS_300_172
SIDE
CUSTGRPID
VNET ID
CRLEN
Note
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-8
OL-1110-23
Appendix A
NAME
EXTNODE
The following rules apply when you are creating or editing ISDN BRI signaling services:
You must define the TCPLINK parameter with the same EXTNODE attribute that its associated
BRIPATH has. If the TCPLNK is not defined when the BRIPATH is added/edited, a warning is
issued. If the TCPLINK is not defined when the provisioning session is copied or deployed, an error
message is generated and the copy or deployment is stopped.
If the TCPLINK with the same EXTNODE value as the BRIPATH is deleted, a warning message is
issued to inform you that the BRIPATH must also be deleted. If the BRIPATH is not deleted when
the provisioning session is copied or deployed, an error message is generated and the copy or
deployment is stopped.
A maximum of 2000 BRIPATHs can be provisioned on your Cisco PGW 2200 Softswitch.
C7 IP Link
The C7 IP Link component type represents a C7 IP link used on the Cisco PGW 2200 Softswitch. These
links are used to communicate with the signal termination point (2600). Its MML name is as follows:
MML NameC7IPLNK
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
PRI
Priority
TIMESLOT
SLC
LNKSET
SESSIONSET
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-9
Appendix A
Components
Charge
The Charge component type is used to provision the Charge table. Its MML name is as follows:
MML NameCHARGE
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
CHORIG
CHDEST
Charge Destination
DOW
TARIFFDESC
Tariff Description
Charge Holiday
The Charge Holiday component type is used to provision the Charge Holiday table. Its MML name is as
follows:
MML NameHOLIDAY
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-10
OL-1110-23
Appendix A
Table A-9
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
DATE
HDAY
CTI Manager
The CTI manager component represents the CTI manager. Its MML name is as follows:
Note
MML NameCTIMGR
NAME
DESC
Component description
IPADDR1
IPADDR2
PEERADDR1
IP address
PEERADDR2
IP address; (0.0.0.0).
PORT
Defaults to 2750.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-11
Appendix A
Components
Table A-10
PEERPORT
Defaults to 2750.
CTIPATH
IPROUTE1
IPROUTE2
USERNAME
N/A
PASSWORD
N/A
CTIVERSION
When an IPROUTE1 and/or IPROUTE2 are specified, the IP address(es) resolved from the
PEERADDR1 and PEERADDR2 attributes must be checked against the DESTINATION and
NETMASK attributes of the IPROUTE(s) to verify that the IPROUTE is valid.
When IPROUTE1 or IPROUTE2 is not specified, the IP address resolved from the PEERADDR1 or
PEERADDR2 attribute must be checked against the defined IPROUTES to verify that it should not
be assigned to one of the IPROUTEs. If the PEERADDR is on the same subnet as an IPROUTE, the
link should use that IPROUTE.
When a hostname is used for PEERADDR1 or PEERADDR2, the hostname must resolve to an IP
address.
PEERADDR1 and PEERADDR2 can resolve to the same IP address. If External node only has one
IP Address, that is, IPADDR2 is defined; then set PEERADDR2 to the same value as PEERADDR1.
If IPADDR2 or PEERADDR2 is specified, then they must both be specified. In other words, you
cannot have one local address and two remote addresses, or two local addresses and one remote
address.
CTI Path
The CTI path component type represents the CTI signaling service. Its MML name is as follows:
MML NameCTIPATH
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-12
OL-1110-23
Appendix A
Note
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
EXTNODE
MDO
MML NameDPC
NAME
Unique ID of this
component and
component name
used in MML
commands
DESC
Component
description
NETADDR
Network address
NETIND
Network indicator
; (0)
D Channel
The D-channel component type represents a D-channel used on the Cisco PGW 2200 Softswitch. There
can be a maximum of two channels per IPFAS (one primary and 1 backup). Its MML name is as follows:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-13
Appendix A
Components
MML NameDCHAN
Parameter MML
Name
Parameter Description
NAME
Unique ID of this
component and component
name used in MML
commands
DESC
Component description
PRI
Priority
SVC
SESSIONSET
TCPLINK
SIGSLOT
SIGPORT
SUBUNIT
The following rules apply when you are creating or editing D-channels:
Backup D-channels for ISDN BRI signaling services are not supported.
Up to 1000 D-channels can be provisioned against a single IP address and port combination used by
your Backhaul TCP links. Since the Cisco PGW 2200 Softswitch supports a maximum of two IP
address and port combinations, you can provision a maximum of 1000 D-channels for an ISDN BRI
signaling service.
DNS Parameters
This command is used to configure domain name system (DNS)-related parameters to support SIP URL.
Its MML name is as follows:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-14
OL-1110-23
Appendix A
MML NameDNSPARAM
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
DNSSERVER1
DNSSERVER2
IP address of secondary
DNS server
This is optional.
CACHESIZE
TTL
POLICY
KEEPALIVE
MML NameDPNSSPATH
Parameter MML
Name
Parameter Description
NAME
IP route name
DESC
Component description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-15
Appendix A
Components
Table A-15
MDO
EXTNODE
CUSTGRPID
Customer group ID
ABFLAG
DPNSS side
SIGSLOT
SIGPORT
ORIG LABEL
TERM LABEL
NAME
EXTNODE
The following rules apply when creating or editing DPNSS signaling paths:
The maximum number of combined DPNSSPATHs and IUA NASPATHs per IUA External Node is
112.
An ASSOCIATION must be defined with same EXTNODE attribute as the DPNSSPATH. If this
ASSOCIATION hasnt been defined when the DPNSSPATH is added/edited, a warning is issued. If
the ASSOCIATION still hasnt been defined when provisioning session is copied or deployed, an
error message is generated and the copy or deployment is stopped.
If the ASSOCIATION with the same EXTNODE value as the DPNSSPATH is deleted, a warning
message is issued to inform the user that the DPNSSPATH must also be deleted. If it hasnt when
the provisioning session is copied or deployed, an error message is generated and the copy or
deployment is stopped.
MML NameEISUPPATH
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-16
OL-1110-23
Appendix A
Table A-16
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
EXTNODE
CUSTGRPID
Customer group ID
CUSTGRPTBL
ORIG LABEL
TERM LABEL
Ethernet Interface
The Ethernet interface component type represents an Ethernet interface used on the
Cisco PGW 2200 Softswitch. Its MML name is as follows:
Note
MML NameENETIF
Parameter MML
Name
NAME
Parameter Description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-17
Appendix A
Components
Table A-17
DESC
Component description
CARD
External Node
The external node component type represents another node with which the Cisco PGW 2200 Softswitch
communicates. Its MML name is as follows:
MML NameEXTNODE
Table A-18
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
TYPE
ISDNSIGTYPE
GROUP
Note
DESC is the only parameter for this command that can be modified:
The following rules apply when you are creating or editing external nodes:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-18
OL-1110-23
Appendix A
Note
MML NameFASPATH
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
SIDE
MDO
CUSTGRPID
Customer ID
CUSTGRPTBL
ABFLAG
DPNSS side
CRLEN
Files
Files component type represents files used to generate .dat files on the Cisco PGW 2200 Softswitch. The
MML name is as follows:
MML NameFILES
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-19
Appendix A
Components
Table A-20
Parameter MML
Name
Parameter Description
NAME
File type
FILE
File name
ACTION
Action to be performed on
the files.
The intelligent network service table component structure is shown in Table A-21.
Table A-21
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
SKORTCV
Service key
GTORSSN
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-20
OL-1110-23
Appendix A
Table A-21
Parameter MML
Name
Parameter Description
GTFORMAT
MSNAME
Global title format (GTFORMAT) must be set to NOGT if the GTORSSN parameter is set to
ROUTEBYSSN. Otherwise, GTFORMAT must be set to a value other that NOGT.
Only one entry can exist in the INSERVICE table for each MSNAME.
The inService.dat ID should be consistent. You cannot delete the current inService entry.
MML NameIPFASPath
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
EXTNODE
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-21
Appendix A
Components
Table A-22
SIDE
MDO
CUSTGRPID
VNET ID
CUSTGRPTBL
ABFLAG
DPNSS side
CRLEN
ORIG LABEL
TERM LABEL
IPINMAPPING
The ipinmapping component type allows you to define mapping between a single SIP or EISUP interface
and multiple IP trunk groups using incoming IP address, subnet mask, and port number. Its MML name
is as follows:
MML NameIPINMAPPING
Parameter MML
Name
Parameter Description
Name
Desc
Description
Sigsvc
AllowedIP
Allowed IP Address
AllowedIPNet
Mask
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-22
OL-1110-23
Appendix A
Table A-23
Parameter MML
Name
Parameter Description
Sipport
Trnkgrpnum
Parameter Analysis
The PGW compares incoming traffic against ipinmapping entries in the following order:
SIP
1.
2.
IP address only
3.
EISUP
1.
IP address only
Analysis Criteria
For incoming IP traffic to match an ipinmapping entry, the following criteria must be true:
AllowedIPNetMask parameters.
The destination port of the incoming SIP message matches the port number defined by the
sipport parameter.
IP address only:
The incoming IP address (the SIP proxy source IP or EISUP H323SourceAddress) falls within
ipinmapping entry.
When the PGW finds a match between incoming traffic and an ipinmapping entry, it forwards the traffic
to the trunk group defined for that ipinmapping entry.
IP Link
The IP link component type represents an IP link used on the Cisco PGW 2200 Softswitch. IP links are
used to communicate with the access control devices, such as a NAS. Its MML name is as follows:
MML NameIPLNK
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-23
Appendix A
Components
Table A-24
Parameter MML
Name
Parameter Description
NAME
Unique ID of this
component and component
name used in MML
commands
DESC
Component description
IF
PORT
PRI
Priority
PEERADDR
Remote IP address
PEERPORT
Remote port
IPADDR
SVC
NEXTHOP
NETMASK
IPROUTE
The following rules apply when you are creating or editing IP links:
If the SVC is a NASPATH, then the ISDNSIGTYPE of the EXTNODE must be N/A.
If the SVC is a NASPATH, then the port number must be an odd number.
If the SVC is a NASPATH, then the local and remote ports must be the same.
The maximum number of links per port is defined by the XECfgParm.dat parameter, maxNumLinks.
Links using the same SVC must have the same port number.
Links using the same SVC must have the same peer port number.
You cannot have more than two links using the same SVC and port number.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-24
OL-1110-23
Appendix A
When an IPROUTE is specified, the IP address resolved from the PEERADDR attribute is checked
against the DESTINATION and NETMASK attributes of the IPROUTE to ensure that the IPROUTE
is valid.
When an IPROUTE is specified, the IPADDR must match the IPADDR of the IP link.
When an IPROUTE is not specified, the IP address resolved from the PEERADDR attribute is
checked against the defined IPROUTES to ensure that it is not assigned to one of the IPROUTEs. If
the PEERADDR is on the same subnet as an IPROUTE, the link uses that IPROUTE.
The PORT attribute cannot have the same value as the PORT attribute of any ASSOCIATION,
SESSIONSET, or SIPLNK.
The PORT attribute cannot be set to the same value as the PORT attribute of another IPLNK with a
different SVC type. That is, the PORT value of an IPLNK supporting an NASPATH SVC cannot be
the same as the PORT value of an IPLNK supporting an MGCPPATH or EISUPPATH SVC.
Another IPLNK, SESSIONSET, or ASSOCIATION with a different EXTNODE cannot use the
resolved value of PEERADDR.
IP Route
The IP route represents a static IP route. Its MML name is as follows:
MML NameIPROUTE
Parameter MML
Name
Parameter Description
NAME
Unique component
name used in MML
commands
DESC
Component description
DEST
NETMASK
Subnet mask of
Destination (optional)
NEXTHOP
IPADDR
Local IP address
PRI
Priority
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-25
Appendix A
Components
Note
NAME is the only parameter for this command that cannot be modified.
The following rules apply when creating or editing IP Routes:
The NETMASK attribute is validated by the system. For your provisioning set-up to work correctly,
its value (when converted to binary) must have at least one leading 1 and cannot have any trailing
1s after the first 0. The values 255.255.0.0 and 255.255.255.128 are valid. The values 0.0.255.255,
255.0.0.255, and 0.0.0.0 are invalid.
When the resolved destination address is bit ORed with the netmask value, the result is equal to the
netmask (for example, a destination of 10.11.12.13 and a netmask of 255.255.0.0 would be invalid
because the ORed result would be 255.255.12.13, which is not equal to 255.255.0.0).
The combination of DESTINATION, NETMASK, and IPADDR must be unique for each IP Route.
The combination of DESTINATION, NETMASK, and PRI must be unique for each IP Route.
When an IPROUTE is not specified for a link object (having that option), the IP Address resolved
from the PEERADDR attribute must be checked against the defined IPROUTES to verify that it
should not be assigned an IPROUTE. If the PEERADDR is on the same subnet as the
DESTINATION (based on the NETMASK), and if the IPADDR matches the IPADDR of the link
object, then use IPROUTE.
If the NEXTHOP attribute is a hostname or symbolic name from XECfgParm.dat, it can resolve to
the address 0.0.0.0, which indicates the IPROUTE is not used. The IPROUTE status shows up in the
rtrv-iproute:all command output when in the OOS, OFF_DUTY state.
If the resolved NEXTHOP address is not 0.0.0.0, it must be on the same subnet of the IPADDR.
LABEL
The LABEL component represents the number of calls allowed on a location. Its MML name is as
follows:
MML nameLABEL
Parameter MML
Name
NAME
Parameter Description
Unique component
name used in MML
commands
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-26
OL-1110-23
Appendix A
Table A-26
Note
DESC
Component description
CALL LIMIT
Maximum number of
calls allowed on one
location label
NAME is the only parameter for this command that cannot be modified.
LineXlate
The linexlate component type represents a line e number and internal number translation. Its MML name
is as follows:
MML NameLINEXLATE
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
SVC
PARAMETER
DIRECTION
1 = NOA
NUMBER
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-27
Appendix A
Components
Table A-27
Parameter MML
Name
Parameter Description
INTNOA
EXTNOA
The value of the NOA field in the Any 7-bit value, 0 through 127, no
protocol message.
restrictions.
Linkset
The linkset component type represents a linkset in an SS7 network used by the
Cisco PGW 2200 Softswitch to communicate with an STP. Its MML name is as follows:
MML NameLNKSET
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
APC
PROTO
Protocol family
TYPE
Transport type
Linkset Property
The linkset property component type represents the configuration parameters that you can use to tune
linkset communications. Its MML is as follows:
MML NameLNKSETPROP
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-28
OL-1110-23
Appendix A
Table A-29
Parameter Description
Default Value
Units
mtp2AermEmgThr
Messages
mtp2AermNrmThr
Messages
mtp2CongDiscard
mtp2LssuLen
Link status signal unit, status field length. Specify one or two. SS7-ANSI = 1
This property is removed in software Revision 9.3(1) and
SS7-UK = 1
later.
SS7-CHINA = 1
SS7-ITU = 1
SS7-Japan = 2
Octets
mtp2MaxAlignRetries
Attempts
Note
Octets
mtp2MaxOutsFrames
Frames
mtp2ProvingEmgT4
Tenths of a
second
mtp2ProvingNormalT4
SS7-ANSI = 23
SS7-UK = 23
SS7-CHINA = 23
SS7-ITU = 23
SS7-Japan = 30
Tenths of a
second
mtp2SuermThr
64
Frames
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-29
Appendix A
Components
Table A-29
Note
Parameter Description
Default Value
Units
All timer values are expressed in tenths of a second. For example, 130 = 13 seconds.
Tenths of a
SS7-ANSI = 130
second
SS7-UK = 450
SS7-CHINA = 450
SS7-ITU = 450
SS7-Japan = 150
mtp2T1
mtp2T2
Tenths of a
Maximum period in not aligned state before return to
SS7-ANSI = 115
second
out-of-service state. Value range: 5 through 30 seconds. This SS7-UK = 250
property is removed in software Revision 9.3(1) and later.
SS7-CHINA = 250
SS7-ITU = 250
SS7-Japan = 50
mtp2T3
SS7-ANSI = 115
SS7-UK = 20
SS7-CHINA = 20
SS7-ITU = 20
SS7-Japan = 30
Tenths of a
second
mtp2T5
Thousandths
of a second
mtp2T6
SS7-ANSI = 30
SS7-UK = 60
SS7-CHINA = 60
SS7-ITU = 60
SS7-Japan = 30
Tenths of a
second
mtp2T7
SS7-ANSI = 10
SS7-UK = 10
SS7-CHINA = 10
SS7-ITU = 10
SS7-Japan = 20
Tenths of a
second
Note
The mtp2 parameters are used with directly connected SS7 signaling links (for example, ITK or PTI
cards).
mtp3ApcMtpRstrtT28
Overall restart timer for signaling point adjacent to one whose SS7-ANSI = 50
MTP restarts. Value range: 3 through 35 seconds (for ANSI
only).
Tenths of a
second
mtp3DlnkConnAckT7
Tenths of a
second
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-30
OL-1110-23
Appendix A
Table A-29
Parameter Description
Default Value
Units
mtp3FrcUnhT13
SS7-ANSI = 10
SS7-UK = 10
SS7-CHINA = 10
SS7-ITU = 10
SS7-Japan = 0
Tenths of a
second
mtp3InhAckT14
SS7-ANSI = 20
SS7-UK = 20
SS7-CHINA = 20
SS7-ITU = 20
SS7-Japan = 0
Tenths of a
second
mtp3LocInhTstT20
SS7-ANSI = 900
Tenths of a
second
mtp3MaxSltTries
mtp3MsgPriority
Messages
SS7-ANSI = 2
SS7-UK = 1
SS7-CHINA = 1
SS7-ITU = 1
SS7-Japan = 1
mtp3MtpRstrtT20
Overall MTP restart timer at the signaling point whose MTP SS7-UK = 900
restarts. Value range: 0 to disable, or 59 through 61 seconds. SS7-CHINA = 0
SS7-ITU = 600
Note
This parameter is for BT, CHINA, and ITU.
SS7-Japan = 0
Tenths of a
second
mtp3ApcMtpRstrtT21
SS7-UK = 640
SS7-CHINA = 0
SS7-ITU = 640
SS7-Japan = 0
Tenths of a
second
SS7-UK = 3000
SS7-CHINA =
3000
SS7-ITU = 3000
SS7-Japan = 0
Tenths of a
second
Note
mtp3LocInhTstT22
mtp3MtpRstrtT24
Overall MTP restart timer for local MTP restart. Value range SS7-ANSI = 60
is network-dependent.
Tenths of a
second
mtp3RepeatRstrtT26
Tenths of a
second
SS7-ANSI = 150
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-31
Appendix A
Components
Table A-29
Parameter Description
Default Value
Units
mtp3TfrUsed
SS7-ANSI = false
SS7-UK = false
SS7-CHINA =
false
SS7-ITU = false
SS7-Japan = false
true/false
mtp3TraSnT29
Timer started when traffic restart allowed is sent in response SS7-ANSI = 600
to unexpected traffic restart allowed or traffic restart waiting.
Value range: 60 through 65 seconds.
Tenths of a
second
mtp3tstSltmT1
Tenths of a
second
mtp3tstSltmT2
Tenths of a
SS7-ANSI = 600
second
SS7-UK = 300
SS7-CHINA = 300
SS7-ITU = 300
SS7-Japan = 300
mtp3UnhAckTl2
SS7-ANSI = 10
SS7-UK = 10
SS7-CHINA = 10
SS7-ITU = 10
SS7-Japan = 0
Tenths of a
second
mtp3T0
Not used.
SS7-Japan = 200
Tenths of a
second
mtp3T7
Tenths of a
second
mtp3T12
Tenths of a
second
mtp3T13
Same as mtp3FrcUnhT13.
SS7-Japan = 0
Tenths of a
second
mtp3T14
Same as mtp3InhAckT14.
SS7-Japan = 0
Tenths of a
second
mtp3T20
Same as mtp3MtpRstrtT20.
SS7-Japan = 0
Tenths of a
second
mtp3T21
Same as mtp3ApcMtpRstrtT21.
SS7-Japan = 0
Tenths of a
second
mtp3T22
Same as mtp3LocInhTstT22.
SS7-Japan = 0
Tenths of a
second
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-32
OL-1110-23
Appendix A
Table A-29
Parameter Description
Default Value
reference
SS7-ANSI =
ANSI96
SS7-UK = ITU92
SS7-CHINA =
ITU92
SS7-ITU = ITU92
SS7-Japan = NTT
rudpAck
Not used.
Enable
rudpKeepAlives
Not used.
Enable
rudpNumRetx
rudpWindowSz
32
rudpRetxTimer
rudpSdm
Not used.
Enable
Units
Tenths of a
second
M3UA Key
This component represents an M3UA routing key. The parent component of the M3UAKEY is the OPC.
MML NameM3UAKEY
Parameter Description
NAME
DESC
Component description
OPC
Associated OPC
DPC
Associated DPC
(optional)
ROUTING CONTEXT
SI
Service indicator
NETWORK
APPEARNCE
Network appearance
(optional)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-33
Appendix A
Components
Note
Two M3UA keys or SUA keys cannot have the same routing context value
M3UA Route
This component represents an M3UA route. It is used to determine how to get an SS7 message to a
particular destination using M3UA.
MML NameM3UAROUTE
Note
Parameter Description
NAME
DESC
Component description
DPC
Associated DPC
EXTNODE
Associated external
node
OPC
Associated OPC
NAME is the only parameter for this command that cannot be modified.
The following rules apply when creating/editing M3UA routes:
The associated DPC must have an SS7 signaling service with an M3UA key defined (matches DPC
attribute). If an M3UA key does not exist when the M3UA route is added/edited, a warning is issued.
If an M3UA key is still not defined when the provisioning session is copied or deployed, an error
message is generated and the copy or deployment is stopped.
Multiple DPCs with the same NETADDR cannot be routed to the same OPC
For a given OPC/DPC only one route can be defined through a given external node.
M3UA routes for the same OPC-DPC pair must have external nodes in the same group
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-34
OL-1110-23
Appendix A
When the provisioning session is saved and activated, there must be an ASSOCIATION of type
M3UA using an SGP that is using the EXTNODE of each M3UAROUTE.
MML NameMGCPPATH
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
EXTNODE
MML NameMLTIPFAS
The multiple IPFAS Signaling Service component structure is shown in Table A-33.
Table A-33
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
CUSTGRPID
Customer ID
MDO
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-35
Appendix A
Components
Table A-33
Parameter MML
Name
Parameter Description
SIDE
EXTNODE
PATHSIZE
SESSIONSET
SIGSLOT
SIGPORT
SIGPORTSKIP
BACKUP
Indicates if a backup
YES or NO; (NO)
D-channel is to be created.
(Only required for IPNFAS.)
ABFLAG
DPNSS side
CRLEN
ORIG LABEL
TERM LABEL
MML NameMLTTRNK
The multiple trunk group and trunk component structure is shown in Table A-34.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-36
OL-1110-23
Appendix A
Table A-34
Parameter MML
Name
Parameter Description
NAME
SVC
CLLI
Common Language
Location Identification
TYPE
Select sequence
QABLE
Queueable
Y or N; (N).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-37
Appendix A
Components
Table A-34
Parameter MML
Name
Parameter Description
VSF
NUMTRNKGRP
SPANSIZE
NUMSPAN
DCHAN
DCHANSPAN
TRNKMEMNUM
SPAN
Span
CIC
ENDPOINT
Text description of the trunk Enter as many as 128 characters and enclose in
endpoint. An endpoint value straight quotes.
is typically composed of an
interface, a timeslot, and a
domain name.
CU
COTPERCENTA
GE
RINGNOANSWE
R
GLARE
SATELLITEIND
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-38
OL-1110-23
Appendix A
Table A-34
Parameter MML
Name
NPA
Parameter Description
CARRIERIDENTI Trunk group property carrier Any integer of 4 digits greater than 0; (0).
TY
identity
SCREENFAILAC
TION
CUSTGRPID
If EchoCanRequired=1:
If the echo device indicator = 0 in BCI,
If EchoCanRequired=0 (default):
Do not send an MDCX for echo control
MML NameNAILEDTRNK
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-39
Appendix A
Components
Table A-35
Parameter MML
Name
Parameter Description
NAME
Trunk identifier
SRCSVC
DSTSVC
SRCSPAN
Source span
DSTSPAN
Destination span
SRCTIMESLOT
Source timeslot
DSTTIMESLOT
Destination timeslot
SPANSIZE
MML NameNASPATH
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
MDO
EXTNODE
CUSTGRPID
Customer group ID
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-40
OL-1110-23
Appendix A
Table A-36
SIGSLOT
SIGPORT
Physical Port on the slot of An integer, 0 through 167; (0). This parameter
NAS defining the NFAS
is added in software Release 9.4(1).
Group. (optional)
NAME
EXTNODE
The following rules apply when creating or editing NAS signaling paths:
You must have an IP link configured if the ISDNTYPE of the EXTNODE is N/A.
The maximum number of DPNSSPATHs and IUA NASPATHs per IUA external node is 112.
The SIGPORT and SIGSLOT attributes can be defined only if the ISDNTYPE of EXTNODE is IUA.
An ASSOCIATION must be defined with the same EXTNODE attribute as its parent NASPATH. If
this ASSOCIATION is not defined when the NASPATH is added or edited, a warning is issued. If
the ASSOCIATION still is not defined when the provisioning session is copied or deployed, an error
message is generated, and the copy or deployment procedure is stopped.
If the ASSOCIATION with the same EXTNODE value as the NASPATH is deleted, a warning
message is issued informing the user that the NASPATH must also be deleted. If it is not deleted
when the provisioning session is copied or deployed, an error message is generated and the copy or
deployment procedure is stopped.
MML NameOPC
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
NETADDR
Network address
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-41
Appendix A
Components
Table A-37
Parameter MML
Name
Parameter Description
NETIND
Network indicator
; (0)
TYPE
TRUEOPC or CAPOPC.
TRUEOPC
MML name of the true OPC The MML name of a previously defined true OPC.
with which the capability
It only applies to the capability OPC.
OPC is associated
Profile
The Profile component supports the ability to retrieve all entries in the table with overridden properties
by specifying all. Its MML name is as follows:
MML NamePROFILE
Parameter MML
Name
Parameter Description
NAME
Profile name
TYPE
The following list identifies the ISUP timers that can be provisioned for signaling service. Information
for each timer consists of:
ComponentsIdentifies the protocol variants supported, the default value, and the range for each
protocol variant.
*.T1
Desc:
T1
Default:
Type:
Components:
SigPath Profile = Yes
SS7-ANSI
ANSISS7_STANDARD Default: 4000 Range=4000-15000
SS7-ITU
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-42
OL-1110-23
Appendix A
*.T12
Desc:
T12
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 6000 Range=4000-15000
SS7-ITU
Q761_BASE Default: 15000 Range=15000-60000
Q767_BASE Default: 15000 Range=4000-15000
Q761_SINGAPORE Default: 60000 Range=60000-60000
Q761_ARGENTINA Default: 10000 Range=10000-60000
ISUPV2_SPANISH Default: 30000 Range=10000-60000
ISUPV2_FINNISH96 Default: 15000 Range=15000-60000
ISUPV2_FRENCH Default: 15000 Range=15000-60000
Q761_THAILAND Default: 15000 Range=15000-60000
Q761_PERU Default: 30000 Range=15000-60000
Q761_BELG_C2 Default: 15000 Range=15000-60000
SS7-Japan
ISUPV2_JAPAN Default: 15000 Range=15000-60000
*.T13
Desc:
T13
Default:
Type:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-43
Appendix A
Components
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 60000 Range=60000-60000
SS7-ITU
Q761_BASE Default: 300000 Range=300000-900000
Q767_BASE Default: 60000 Range=60000-60000
Q761_SINGAPORE Default: 300000 Range=300000-900000
Q761_ARGENTINA Default: 60000 Range=60000-900000
ISUPV2_SPANISH Default: 600000 Range=60000-900000
ISUPV2_FINNISH96 Default: 300000 Range=300000-900000
ISUPV2_FRENCH Default: 300000 Range=300000-900000
Q761_THAILAND Default: 60000 Range=60000-900000
Q761_PERU Default: 600000 Range=300000-900000
Q761_BELG_C2 Default: 300000 Range=300000-900000
SS7-Japan
ISUPV2_JAPAN Default: 300000 Range=60000-900000
*.T14
Desc:
T14
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 6000 Range=4000-15000
SS7-ITU
Q761_BASE Default: 15000 Range=15000-60000
Q767_BASE Default: 15000 Range=4000-15000
Q761_SINGAPORE Default: 60000 Range=60000-60000
Q761_ARGENTINA Default: 10000 Range=10000-60000
ISUPV2_SPANISH Default: 30000 Range=10000-60000
ISUPV2_FINNISH96 Default: 15000 Range=15000-60000
ISUPV2_FRENCH Default: 15000 Range=15000-60000
Q761_THAILAND Default: 15000 Range=15000-60000
Q761_PERU Default: 30000 Range=15000-60000
Q761_BELG_C2 Default: 15000 Range=15000-60000
SS7-Japan
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-44
OL-1110-23
Appendix A
*.T15
Desc:
T15
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 60000 Range=60000-60000
SS7-ITU
Q761_BASE Default: 300000 Range=300000-900000
Q767_BASE Default: 60000 Range=60000-60000
Q761_SINGAPORE Default: 300000 Range=300000-900000
Q761_ARGENTINA Default: 6000 Range=60000-900000
ISUPV2_SPANISH Default: 600000 Range=60000-900000
ISUPV2_FINNISH96 Default: 300000 Range=300000-900000
ISUPV2_FRENCH Default: 300000 Range=300000-900000
Q761_THAILAND Default: 60000 Range=60000-900000
Q761_PERU Default: 600000 Range=300000-900000
Q761_BELG_C2 Default: 300000 Range=300000-900000
SS7-Japan
ISUPV2_JAPAN Default: 300000 Range=300000-900000
*.T16
Desc:
T16
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 5000 Range=4000-15000
SS7-ITU
Q761_BASE Default: 15000 Range=15000-60000
Q767_BASE Default: 5000 Range=4000-15000
Q761_SINGAPORE Default: 60000 Range=60000-60000
Q761_ARGENTINA Default: 10000 Range=10000-60000
ISUPV2_SPANISH Default: 30000 Range=10000-60000
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-45
Appendix A
Components
*.T17
Desc:
T17
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 60000 Range=60000-60000
SS7-ITU
Q761_BASE Default: 300000 Range=300000-900000
Q767_BASE Default: 60000 Range=60000-60000
Q761_SINGAPORE Default: 300000 Range=300000-900000
Q761_ARGENTINA Default: 60000 Range=60000-900000
ISUPV2_SPANISH Default: 600000 Range=60000-900000
ISUPV2_FINNISH96 Default: 300000 Range=300000-900000
ISUPV2_FRENCH Default: 300000 Range=300000-900000
Q761_THAILAND Default: 60000 Range=60000-900000
Q761_PERU Default: 600000 Range=300000-900000
Q761_BELG_C2 Default: 300000 Range=300000-900000
SS7-Japan
ISUPV2_JAPAN Default: 60000 Range=60000-900000
*.T18
Desc:
T18
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 15000 Range=4000-15000
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-46
OL-1110-23
Appendix A
SS7-ITU
Q761_BASE Default: 15000 Range=15000-60000
Q767_BASE Default: 15000 Range=4000-15000
Q761_SINGAPORE Default: 60000 Range=60000-60000
Q761_ARGENTINA Default: 10000 Range=10000-60000
ISUPV2_SPANISH Default: 30000 Range=10000-60000
ISUPV2_FINNISH96 Default: 15000 Range=15000-60000
ISUPV2_FRENCH Default: 15000 Range=15000-60000
Q761_THAILAND Default: 15000 Range=15000-60000
Q761_PERU Default: 30000 Range=15000-60000
Q761_BELG_C2 Default: 15000 Range=15000-60000
SS7-Japan
ISUPV2_JAPAN Default: 15000 Range=15000-60000
*.T19
Desc:
T19
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 60000 Range=60000-60000
SS7-ITU
Q761_BASE Default: 300000 Range=300000-900000
Q767_BASE Default: 60000 Range=60000-60000
Q761_SINGAPORE Default: 300000 Range=300000-900000
Q761_ARGENTINA Default: 60000 Range=60000-900000
ISUPV2_SPANISH Default: 600000 Range=60000-900000
ISUPV2_FINNISH96 Default: 300000 Range=300000-900000
ISUPV2_FRENCH Default: 300000 Range=300000-900000
Q761_THAILAND Default: 60000 Range=60000-900000
Q761_PERU Default: 600000 Range=300000-900000
Q761_BELG_C2 Default: 300000 Range=300000-900000
SS7-Japan
ISUPV2_JAPAN Default: 300000 Range=300000-900000
*.T2
Desc:
T2
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-47
Appendix A
Components
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 180000 Range=180000-180000
SS7-ITU
Q761_BASE Default: 180000 Range=180000-180000
Q767_BASE Default: 180000 Range=180000-180000
Q761_SINGAPORE Default: 180000 Range=180000-180000
Q761_ARGENTINA Default: 180000 Range=180000-180000
ISUPV2_SPANISH Default: 180000 Range=180000-180000
ISUPV2_FINNISH96 Default: 180000 Range=180000-180000
ISUPV2_FRENCH Default: 180000 Range=180000-180000
Q761_THAILAND Default: 180000 Range=180000-180000
Q761_PERU Default: 180000 Range=180000-180000
Q761_BELG_C2 Default: 180000 Range=180000-180000
SS7-Japan
ISUPV2_JAPAN Default: 180000 Range=180000-180000
*.T20
Desc:
T20
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 15000 Range=4000-15000
SS7-ITU
Q761_BASE Default: 15000 Range=15000-60000
Q767_BASE Default: 15000 Range=4000-15000
Q761_SINGAPORE Default: 60000 Range=60000-60000
Q761_ARGENTINA Default: 10000 Range=10000-60000
ISUPV2_SPANISH Default: 30000 Range=10000-60000
ISUPV2_FINNISH96 Default: 15000 Range=15000-60000
ISUPV2_FRENCH Default: 15000 Range=15000-60000
Q761_THAILAND Default: 15000 Range=15000-60000
Q761_PERU Default: 30000 Range=15000-60000
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-48
OL-1110-23
Appendix A
*.T21
Desc:
T21
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 60000 Range=60000-60000
SS7-ITU
Q761_BASE Default: 300000 Range=300000-900000
Q767_BASE Default: 60000 Range=60000-60000
Q761_SINGAPORE Default: 300000 Range=300000-900000
Q761_ARGENTINA Default: 60000 Range=60000-900000
ISUPV2_SPANISH Default: 600000 Range=60000-900000
ISUPV2_FINNISH96 Default: 300000 Range=300000-900000
ISUPV2_FRENCH Default: 300000 Range=300000-900000
Q761_THAILAND Default: 60000 Range=60000-900000
Q761_PERU Default: 600000 Range=300000-900000
Q761_BELG_C2 Default: 300000 Range=300000-900000
SS7-Japan
ISUPV2_JAPAN Default: 300000 Range=300000-900000
*.T22
Desc:
T22
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 15000 Range=4000-15000
SS7-ITU
Q761_BASE Default: 15000 Range=15000-60000
Q767_BASE Default: 15000 Range=4000-15000
Q761_SINGAPORE Default: 60000 Range=60000-60000
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-49
Appendix A
Components
*.T23
Desc:
T23
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 60000 Range=60000-60000
SS7-ITU
Q761_BASE Default: 300000 Range=300000-900000
Q767_BASE Default: 60000 Range=60000-60000
Q761_SINGAPORE Default: 300000 Range=300000-900000
Q761_ARGENTINA Default: 60000 Range=60000-900000
ISUPV2_SPANISH Default: 600000 Range=60000-900000
ISUPV2_FINNISH96 Default: 300000 Range=300000-900000
ISUPV2_FRENCH Default: 300000 Range=300000-900000
Q761_THAILAND Default: 60000 Range=60000-900000
Q761_PERU Default: 600000 Range=300000-900000
Q761_BELG_C2 Default: 300000 Range=300000-900000
SS7-Japan
ISUPV2_JAPAN Default: 60000 Range=60000-900000
*.T24
Desc:
T24
Default:
Type:
Components:
SigPath Profile=Yes
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-50
OL-1110-23
Appendix A
SS7-ANSI
ANSISS7_STANDARD Default: 20000 Range=20000-20000
SS7-ITU
Q761_BASE Default: 2000 Range=0-2000
Q767_BASE Default: 2000 Range=0-2000
Q761_SINGAPORE Default: 2000 Range=2000-2000
Q761_ARGENTINA Default: 2000 Range=2000-2000
ISUPV2_SPANISH Default: 1500 Range=1500-2000
ISUPV2_FINNISH96 Default: 2000 Range=0-2000
ISUPV2_FRENCH Default: 2000 Range=0-2000
Q761_THAILAND Default: 2000 Range=0-2000
Q761_PERU Default: 15000 Range=0-2000
Q761_BELG_C2 Default: 2000 Range=0-2000
SS7-Japan
ISUPV2_JAPAN Default: 2000 Range=0-2000
*.T25
Desc:
T25
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 1000 Range=1000-10000
SS7-ITU
Q761_BASE Default: 2000 Range=1000-10000
Q767_BASE Default: 2000 Range=1000-10000
Q761_SINGAPORE Default: 10000 Range=1000-10000
Q761_ARGENTINA Default: 10000 Range=1000-10000
ISUPV2_SPANISH Default: 10000 Range=1000-10000
ISUPV2_FINNISH96 Default: 2000 Range=1000-10000
ISUPV2_FRENCH Default: 2000 Range=1000-10000
Q761_THAILAND Default: 2000 Range=1000-10000
Q761_PERU Default: 10000 Range=1000-10000
Q761_BELG_C2 Default: 2000 Range=1000-10000
SS7-Japan
ISUPV2_JAPAN Default: 2000 Range=1000-10000
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-51
Appendix A
Components
*.T26
Desc:
T26
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 120000 Range=60000-180000
SS7-ITU
Q761_BASE Default: 180000 Range=60000-180000
Q767_BASE Default: 180000 Range=60000-180000
Q761_SINGAPORE Default: 180000 Range=60000-180000
Q761_ARGENTINA Default: 120000 Range=60000-180000
ISUPV2_SPANISH Default: 120000 Range=60000-180000
ISUPV2_FINNISH96 Default: 180000 Range=60000-180000
ISUPV2_FRENCH Default: 180000 Range=60000-180000
Q761_THAILAND Default: 180000 Range=60000-180000
Q761_PERU Default: 120000 Range=60000-180000
Q761_BELG_C2 Default: 180000 Range=60000-180000
SS7-Japan
ISUPV2_JAPAN Default: 180000 Range=60000-180000
*.T27
Desc:
T27
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 240000 Range=180000-240000
SS7-ITU
Q761_BASE Default: 240000 Range=240000-240000
Q767_BASE Default: 240000 Range=240000-240000
Q761_SINGAPORE Default: 240000 Range=240000-240000
Q761_ARGENTINA Default: 240000 Range=240000-240000
ISUPV2_SPANISH Default: 240000 Range=240000-240000
ISUPV2_FINNISH96 Default: 240000 Range=240000-240000
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-52
OL-1110-23
Appendix A
*.T28
Desc:
T28
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 10000 Range=10000-10000
SS7-ITU
Q761_BASE Default: 10000 Range=10000-10000
Q761_SINGAPORE Default: 10000 Range=10000-10000
Q761_ARGENTINA Default: 10000 Range=10000-10000
ISUPV2_SPANISH Default: 10000 Range=10000-10000
ISUPV2_FINNISH96 Default: 10000 Range=10000-10000
ISUPV2_FRENCH Default: 10000 Range=10000-10000
Q761_THAILAND Default: 10000 Range=10000-10000
Q761_PERU Default: 10000 Range=10000-10000
Q761_BELG_C2 Default: 10000 Range=10000-10000
SS7-Japan
ISUPV2_JAPAN Default: 10000 Range=10000-10000
*.T33
Desc:
T33
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 120000 Range=120000-120000
SS7-ITU
Q761_BASE Default: 15000 Range=12000-15000
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-53
Appendix A
Components
*.T34
Desc:
T34
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 10000 Range=10000-10000
SS7-ITU
Q761_BASE Default: 2000 Range=2000-4000
Q761_SINGAPORE Default: 3800 Range=2000-4000
Q761_ARGENTINA Default: 15000 Range=2000-15000
ISUPV2_SPANISH Default: 2000 Range=2000-15000
ISUPV2_FINNISH96 Default: 2000 Range=2000-4000
ISUPV2_FRENCH Default: 4000 Range=2000-4000
Q761_THAILAND Default: 2000 Range=2000-4000
Q761_PERU Default: 2000 Range=2000-4000
Q761_BELG_C2 Default: 2000 Range=2000-4000
SS7-Japan
ISUPV2_JAPAN Default: 2000 Range=2000-4000
*.T35
Desc:
T35
Default:
Type:
Components:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-54
OL-1110-23
Appendix A
SigPath Profile=Yes
SS7-ITU
Q761_BASE Default: 15000 Range=15000-20000
Q767_BASE Default: 15000 Range=15000-20000
Q761_SINGAPORE Default: 15000 Range=15000-20000
Q761_ARGENTINA Default: 15000 Range=15000-20000
ISUPV2_SPANISH Default: 15000 Range=15000-20000
ISUPV2_FINNISH96 Default: 15000 Range=15000-20000
ISUPV2_FRENCH Default: 15000 Range=15000-20000
Q761_THAILAND Default: 15000 Range=15000-20000
Q761_PERU Default: 15000 Range=15000-20000
Q761_BELG_C2 Default: 15000 Range=15000-20000
SS7-Japan
ISUPV2_JAPAN Default: 15000 Range=15000-20000
*.T36
Desc:
T36
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 10000 Range=10000-10000
SS7-ITU
Q761_BASE Default: 10000 Range=10000-15000
Q767_BASE Default: 10000 Range=10000-15000
Q761_SINGAPORE Default: 10000 Range=1000-15000
Q761_ARGENTINA Default: 10000 Range=1000-15000
ISUPV2_SPANISH Default: 15000 Range=1000-15000
ISUPV2_FINNISH96 Default: 10000 Range=10000-15000
ISUPV2_FRENCH Default: 10000 Range=10000-15000
Q761_THAILAND Default: 10000 Range=10000-15000
Q761_PERU Default: 15000 Range=10000-15000
Q761_BELG_C2 Default: 10000 Range=10000-15000
SS7-Japan
ISUPV2_JAPAN Default: 10000 Range=10000-15000
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-55
Appendix A
Components
*.T38
Desc:
T38
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ITU
Q761_BASE Default: 125000 Range=125000-125000
Q761_SINGAPORE Default: 125000 Range=125000-125000
Q761_ARGENTINA Default: 125000 Range=125000-125000
ISUPV2_SPANISH Default: 125000 Range=125000-125000
ISUPV2_FINNISH96 Default: 125000 Range=125000-125000
ISUPV2_FRENCH Default: 125000 Range=125000-125000
Q761_THAILAND Default: 125000 Range=125000-125000
Q761_BELG_C2 Default: 125000 Range=125000-125000
SS7-Japan
ISUPV2_JAPAN Default: 125000 Range=125000-125000
*.T5
Desc:
T5
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 60000 Range=60000-60000
SS7-ITU
Q761_BASE Default: 300000 Range=300000-900000
Q767_BASE Default: 60000 Range=60000-60000
Q761_SINGAPORE Default: 300000 Range=300000-900000
Q761_ARGENTINA Default: 60000 Range=60000-900000
ISUPV2_SPANISH Default: 600000 Range=60000-900000
ISUPV2_FINNISH96 Default: 300000 Range=300000-900000
ISUPV2_FRENCH Default: 300000 Range=300000-900000
Q761_THAILAND Default: 60000 Range=60000-900000
Q761_PERU Default: 600000 Range=300000-900000
Q761_BELG_C2 Default: 300000 Range=300000-900000
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-56
OL-1110-23
Appendix A
SS7-Japan
ISUPV2_JAPAN Default: 60000 Range=60000-900000
*.T6
Desc:
T6
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 32000 Range=10000-32000
SS7-ITU
Q761_BASE Default: 120000 Range=60000-120000
Q767_BASE Default: 120000 Range=60000-120000
Q761_SINGAPORE Default: 20000 Range=20000-130000
Q761_ARGENTINA Default: 60000 Range=10000-60000
ISUPV2_SPANISH Default: 60000 Range=10000-60000
ISUPV2_FINNISH96 Default: 120000 Range=60000-120000
ISUPV2_FRENCH Default: 60000 Range=60000-120000
Q761_THAILAND Default: 90000 Range=60000-120000
Q761_PERU Default: 15000 Range=15000-120000
Q761_BELG_C2 Default: 120000 Range=60000-120000
SS7-Japan
ISUPV2_JAPAN Default: 3000 Range=2000-4000
*.T7
Desc:
T7
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 30000 Range=20000-30000
SS7-ITU
Q761_BASE Default: 30000 Range=20000-30000
Q767_BASE Default: 30000 Range=20000-30000
Q761_SINGAPORE Default: 20000 Range=20000-30000
Q761_ARGENTINA Default: 20000 Range=20000-30000
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-57
Appendix A
Components
*.T8
Desc:
T8
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
ANSISS7_STANDARD Default: 10000 Range=10000-15000
SS7-ITU
Q761_BASE Default: 10000 Range=10000-15000
Q767_BASE Default: 10000 Range=10000-15000
Q761_SINGAPORE Default: 10000 Range=10000-15000
Q761_ARGENTINA Default: 15000 Range=10000-15000
ISUPV2_SPANISH Default: 15000 Range=10000-15000
ISUPV2_FINNISH96 Default: 10000 Range=10000-15000
ISUPV2_FRENCH Default: 10000 Range=10000-15000
Q761_THAILAND Default: 10000 Range=10000-15000
Q761_PERU Default: 15000 Range=10000-15000
Q761_BELG_C2 Default: 10000 Range=10000-15000
SS7-Japan
ISUPV2_JAPAN Default: 10000 Range=10000-15000
*.T9
Desc:
T9
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-58
OL-1110-23
Appendix A
RASERVER
The RASERVER component defines a signal channel to the Radius Accounting Server. RASERVER also
associates an RA SigPath to the channel.
MML NameRASERVER
The following restrictions apply to the RASERVER component:
If you want to delete a single RASERVER, you must also delete the RAPATH.
To modify an RASERVER, the PORT parameter value must match the existing RASERVER.
The PGW uses PORT with a value between <local-port> and <local-port + <number of port>>
Table 1:
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-59
Appendix A
Components
Table 1:
Parameter MML
Name
Parameter Description
SVC
IPADDR
Remote IP address
This parameter is mandatory.
PEERPORT
1025 to 65535.
The accounting port number
used on the destination server for
accounting data.
This parameter is mandatory.
IPROUTE
ORDER
KEY
TIMEOUT
1 to 30. (6)
RETRYCOUNT
Routing
The routing file can be moved onto the Cisco PGW 2200 Softswitch using FTP and then associated with
the relevant session using SNMP. Its MML name is as follows:
MML NameRTTRNKGRP
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-60
OL-1110-23
Appendix A
Table A-40
Component MML
Name
Parameter MML
Name
SIPRTTRNKGR NAME
P
Parameter Description
URL
SIPPROXYPORT
VERSION
CUTTHROUGH
EXTSUPPORT
RTTRNK
0 = Undefined
1 = Seize - call is through
connected a seize, not applicable
2 = ACM - call is through
connected at ACM
3 = ANM - call is through
connected at ANM
RTLIST
0 through 3; (0)
SRVRR
NAME
20 alphanumeric
RTNAME
Route name
; (0)
NEXTRTNAME
20 alphanumeric
DISTRIB
Indicates if random or
sequential distribution
is enabled
NAME
Route name
20 alphanumeric
TRNKGRPNUM
; (0)
NEXTTRKGRP
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-61
Appendix A
Components
Table A-40
Component MML
Name
RTTRNKGRP
Parameter MML
Name
Parameter Description
WEIGHTEDTG
NAME
TYPE
0 to 8; (0)
0 = General (default)Used with
SS7 signaling services with switch
types not equal to 0, 5, or 20.
1 = ISUPUsed with SS7
signaling services with switch
types of 0 or 20.
2 = CAScurrently not
supported.
3 = TUPUsed with SS7
signaling services with switch
type of 5.
4 = IPUsed with EISUP
signaling service.
5 = ATMUsed with VSI path
signaling service
6 = DPNSSUsed with DPNSS
protocol family signaling services
7 = PRIUsed with ISDN PRI
protocol family signaling services.
8 = BTNUPUsed with SS7
signaling services with switch
type 5.
9 = IP_SIPUsed with SIP
signaling services at the
terminating side.
10 = SIP_INUsed with SIP
signaling services at the
originating side.
11 = CTIUsed with CTI
signaling.
REATTEMPTS
Number of reattempts
0 to 5; (0)
QUEUING
Queuing time
0 to 120; (0)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-62
OL-1110-23
Appendix A
Table A-40
Component MML
Name
Parameter MML
Name
Parameter Description
0 through 3; (0)
RESINCPERC
Reserve incoming
bandwidth percentage
BEARERCAPNA
ME
20 alphanumeric (NULL)
NAME
Used to configure
CARRIERID,
RTEOPTION, and
RTLISTNAME.
CARRIERID
RTEOPTION
Optional parameter;
identifies the route
option
RTLISTNAME
NAME
Conditional routing
name
20 alphanumeric
DOW
Day of week
DEFAULT; (DEFAULT),
SUNDAY, MONDAY, TUESDAY,
WEDNESDAY, THURSDAY,
FRIDAY, SATURDAY, SUNDAY,
HOL1, HOL2, HOL3
RTEDESC
Conditional routing
descriptor
CUTTHROUGH
CARRIERTBL
CONDRTE
0 = Undefined
1 = Seize - call is through
connected a seize, not applicable
2 = ACM - call is through
connected at ACM
3 = ANM - call is through
connected at ANM
The following rules apply when creating or editing the Routing table:
To add, modify, or delete the contents of a Routing table, an active provisioning session is required.
At the time of deploying or copying, routing files from the provisioning directory are copied to the active
directory. The active directory for the routing file is: /opt/CiscoMGC/etc.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-63
Appendix A
Components
All of the TIDs, except CARRIERTBL and ROUTING, require a name. Currently it is only possible to
retrieve against a name.
All the Carrier tables, route lists, route trunks, and route trunk groups information can be retrieved by
using the prov:rtrv:rtlist:"ALL" command. The ALL option cannot be used with other parameters.
The NEXTRTNAME parameter is used for changing the order of routes in the route list. If not specified
when a route is added to a route list, the routes are added in the order in which they are entered.
NEXTRTNAME is only valid for use when modifying the route list.
The NEXTRKGRP parameter is used for changing the order of trunk groups in the route. If not specified
when a trunk group is added to a route, the trunk groups are added in the order in which they are entered.
NEXTRKGRP is only valid for use when modifying the route list.
The CARRIERID is not available in RTLIST in software Release 9.x.
The ROUTING TID provides the functionality to add and to delete a routing file. When adding a routing
file, if there is currently no routing file one is created, otherwise an error occurs. When deleting, if a
routing file exists, it is deleted, otherwise an error occurs.
Edits are not supported for the ROUTING TID and for CARRIERTBL, edits are only valid when using
the RTLISTNAME with the RTOPTION CARRIER.
When the first entry is added to a conditional route, the day of week of DEFAULT is used. Thus a default
value is always set for all conditional routes. For all days of the week, the user enters as the first value
in the set a conditional route name. Then the user can add up to four pair of time changes and conditional
route names. The time changes can be configure in the range 0015 to 2345 and must be divisible by 15
minutes. A check is performed to ensure that the times are added only in ascending order.
Session Set
The session set component type represents a pair of backhaul IP links used on the
Cisco PGW 2200 Softswitch. These links are used to communicate with external nodes that support
IPFAS. Its MML name is as follows:
MML NameSESSIONSET
Parameter MML
Name
Parameter Description
NAME
Unique ID of this
component and component
name used in MML
commands
DESC
Component description
IPADDR1
IPADDR2
PORT
PEERADDR1
Remote IP address 1
PEERADDR2
Remote IP address 2
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-64
OL-1110-23
Appendix A
Table A-41
Parameter MML
Name
Parameter Description
PEERPORT
Remote port
EXTNODE
NEXTHOP1
NETMASK1
NEXTHOP2
NETMASK2
IPROUTE1
IPROUTE2
TYPE
BSMV0 or IPFAS.
The following rules apply when you are creating or editing session sets:
The type of the session set must be BSMV0 for C7 session sets.
The type of the session set must be IPFAS for IPFAS session sets.
IP addresses cannot be split across session sets. For example if SET 1 has IP_Addr1 and IP_Addr2,
then SET 2 cannot have IP_Addr1 and IP_Addr3.
If IPADDR2 or PEERADDR2 is specified, they must both be specified. In other words you cannot
have one local address and two remote addresses, or two local addresses and one remote address.
PEERADDR1 and PEERADDR2 must have different values except when the EXTNODE is a VISM
(MGX8850).
The PORT attribute cannot be set to the same value as the PORT attribute of any ASSOCIATION,
IPLNK, or SIPLNK.
The PORT attribute cannot be set to the same value as the PORT attribute of another SESSIONSET
with a different TYPE value. In other words the PORT value of a BSMV0 SESSIONSET cannot be
the same as the PORT value of an IPFAS SESSIONSET.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-65
Appendix A
Components
When IPROUTE1 or IPROUTE2 is specified the IP address resolved from the PEERADDR1 or
PEERADDR2 attribute must be checked against the DESTINATION and NETMASK attributes to
verify that the IPROUTE is valid.
When IPROUTE1 is specified, the IPADDR must match the IPADDR1 of the session set.
When IPROUTE2 is specified, the IPADDR must match the IPADDR2 of the session set.
When IPROUTE1 or IPROUTE2 is not specified, the IP address resolved from the PEERADDR1 or
PEERADDR2 attribute is checked against the defined IPROUTES to determine whether they should
assigned to one of the IPROUTEs. If the PEERADDR is on the same subnet as an IPROUTE, the
link should use that IPROUTE.
Another IPLNK, SESSIONSET, or ASSOCIATION with a different EXTNODE cannot use the
resolved value of PEERADDR.
A Session Set is a logical representation of one or two backhaul IP links. The SESSIONSET MML
command generates a Session Set that is one or two (if PEERADDR2 is specified) Backhaul IP Links.
The names are NAME-1 and NAME-2. The DESCRIPTIONs are Session Set NAME Backhaul Link 1
and Session Set NAME Backhaul Link 2.
All MML commands (add, edit, delete, and retrieve) are performed against the IP link pair by specifying
only the NAME. Retrieving a session set displays the backhaul IP links (there may only be one) for the
session set. Retrieving all session sets displays all backhaul IP links.
SGP
This is the Cisco PGW 2200 Softswitch NE component type and represents an SS7 signaling gateway
process. Its MML name is as follows:
MML NameSGP
Parameter MML
Name
Parameter Description
NAME
Unique ID of this
component and component
name used in MML
commands
DESC
Component description
EXTNODE
SIP IP Link
This is the Cisco PGW 2200 Softswitch NE component type and represents a SIP IP link used on the
Cisco PGW 2200 Softswitch NE. These links are used to communicate with the SIP proxy servers. Its
MML name is as follows:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-66
OL-1110-23
Appendix A
MML NameSIPLNK
Parameter MML
Name
Parameter Description
NAME
Unique ID of this
component and component
name used in MML
commands
DESC
Component description
IF
PORT
PRI
Priority
IPADDR
SVC
NEXTHOP
NETMASK
MML NameSIPPATH
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-67
Appendix A
Components
Table A-44
MDO
ORIG LABEL
TERM LABEL
SS7 Route
The SS7 route component type represents an SS7 route. It is used to determine how to get an SS7
message to a particular destination. Its MML name is as follows:
MML NameSS7ROUTE
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
DPC
LNKSET
OPC
PRI
Priority
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-68
OL-1110-23
Appendix A
Table A-46
Parameter Description
Parameter Values
adjDestinations
AInternationalPrefix
ANationalPrefix
BothwayWorking
CGBA2
Values: 0 or 1.
Values: 0 or 1.
Note
CLIDefaultAllowed
Default = NULL
Default = 1
Default = 0
Sets the presentation restricted field in the calling Values: TRUE (1) or FALSE (0)
line identity (CLI).
Default: FALSE
When set to TRUE and an incoming Q931 setup
Note
Used in all protocols that are based
message has the presentation restricted indicator
on Q761.
absent, then the presentation restricted indicator in
the outgoing message (IAM or setup) is set to
Note
Only valid for ISDN PRI inbound to
presentation allowed.
either C7 ISUP outbound or ISDN
When set to FALSE and an incoming Q931 setup
message has the presentation restricted indicator
absent, then the presentation restricted indicator in
the outgoing message (IAM or setup) is set to
presentation restricted.
CLIPEss
Default = NULL
PRI outbound.
Values: 0, 1, or 2.
Sets the Calling Line Identity Presentation
Essential operation. 0Do not request CLI.,
Default = 0
1Request CLI if not already provided and drop
the call if CLI is not provided, or 2Request CLI
if not already provided and continue with the call
even if CLI is not provided.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-69
Appendix A
Components
Table A-46
Parameter Description
Parameter Values
COLDefaultAllowed
Default: FALSE
When set to TRUE and an incoming Q931 setup
Note
Used in all protocols that are based
message has the presentation restricted indicator
on q761 except HONG_KONG,
absent, then the presentation restricted indicator in
AUSTRALIA, FRENCH, NTT,
the outgoing message (IAM or setup) is set to
JAPAN_JT.
presentation allowed.
When set to FALSE and an incoming Q931 setup
message has the presentation restricted indicator
absent, then the presentation restricted indicator in
the outgoing message (IAM or setup) is set to
presentation restricted.
CotInTone
CotListenDuration
Default = 2000 20
Default = 60
CotOutTone
Transmit tone for COT hardware. The tone that is Enter value in Hz. Value: 1780 or 2010.
produced.
Default = 2000 20
CotPercentage
Statistical COT.
CotPlayDuration
Maximum period in not aligned state before return Value range: 1 through 200, specified in
to out-of-service state (should be less than or equal milliseconds.
to the CotListenDuration).
Default = 60
dialogRange
0 = entire range.
ExtCOT
ForwardCLIinIAM
Default = 0
Default = Loop
Values: 0 or 1.
ForwardSegmentedNEED Set to 0 to disable the forwarding of segmented
NEED messages within the BTNUP_NRC
Default = 1
protocol. If segmenting is disabled, all mandatory
DPNSS information elements are packed into a
single BTNUP NEED message.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-70
OL-1110-23
Appendix A
Table A-46
Parameter Description
Parameter Values
GLARE
Note
Note
Note
Note
Default = 0
GRA2
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-71
Appendix A
Components
Table A-46
Parameter Description
Parameter Values
GRSEnabled
GRSonSSCEnabled
Note
hopCount
layerRetries
layerTimer
Time (in tenths of a second) to wait for a response Value range: 0 through 10.
from adjacent layer (SS7 controller, TCAP to
0 = Disabled, 10 = 1 second.
SCCP); tailor when layers are not resident on same
Default = 10
processor.
maxMessageLength
NatureOfAddrHandling
Default = 0
NFASImplicitInterfaceId
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-72
OL-1110-23
Appendix A
Table A-46
Parameter Description
Parameter Values
OD32DigitSupport
OMaxDigits
Specifies maximum number of digits to receive for Value range: 0 through system maximum.
overlap digit processing for call origination from
Default = 24
this traffic path.
OMinDigits
Specifies minimum number of digits to receive for Value range: 0 through system maximum.
overlap digit processing for call origination from
Default = 0
this traffic path.
Note
OwnClli
Default = 0
Default = 6
Specifies the common language location identifier Value range: Alphanumeric string, up to 11
(CLLI).
characters.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-73
Appendix A
Components
Table A-46
Parameter Description
Parameter Values
RedirMax
Default: 5
Value range prior to Release 9.7(3) S22P22:
0 to system maximum.
Value range for Release 9.7(3) S22P22 and
later:
15:
0:
restartTimer
Note
RoutePref
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-74
OL-1110-23
Appendix A
Table A-46
Parameter Description
Parameter Values
SdpXmitToH323Trigger
slsTimer
Time (in tenths of a second) to maintain the same Value range: 0 through 600.
signal linkset in class 1 (connectionless)
0 = Disabled, 300 = 30 seconds.
messages. This is the type of service provided by
Default = SS7-ANSI = 300
the SCCP layer.
srtTimer
Time (in tenths of a second) between the sending Value range: 0 through 3000.
of Subsystem Route Test message (SRT) to remote 0 = disabled, 300 = 30 seconds.
subsystems.
Default = SS7-ANSI = 300
sstTimer
standard
SS7-ANSI = ANSI96,
SS7-ITU = ITU96,
ANSI96,
ITU96,
ANSI92,
ITU92
TMaxDigits
Specifies maximum number of digits to receive for Value range: 0 through system maximum.
overlap digit processing for call termination to this
Default = 24
traffic path.
TMinDigits
Specifies minimum number of digits to receive for Value range: 0 through system maximum.
overlap digit processing for call termination to this
Default = 0
traffic path.
TOverlap
Values: 0 or 1.
variant
Default = SS7-ANSI=SS7-ANSI,SS7-ITU
VOIPPrefix
A numeric string.
Default = 0
Default = 0
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-75
Appendix A
Components
MML NameSS7PATH
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
SIDE
MDO
DPC
CUSTGRPID
Customer group ID
OPC
ORIG LABEL
TERM LABEL
SS7 Subsystem
The SS7 subsystem component type represents an SS7 subsystem. It is used for specifying mated STPs
and to provide LNP support through a SCP. Its MML name is as follows:
MML NameSS7SUBSYS
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-76
OL-1110-23
Appendix A
Table A-48
Parameter MML
Name
Parameter Description
NAME
Unique component
name used in MML
commands
DESC
Component description
LOCALSSN
Subsystem number
(formerly SSN)
MATEDAPC
PRI
Priority
PROTO
Protocol family
OPC
Remote subsystem
number
SUAKEY
MML name of
SUAKEY
SVC
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-77
Appendix A
Components
Table A-48
Parameter MML
Name
Parameter Description
STPSCPIND
STP/SCP index used for Integer greater than 0; (0). Not used when mating
IN triggers
STP pairs.
Note
SSN has been renamed LOCALSSN to clarify the intent of the parameter. There is continued support of
SSN for the MML command line. If both SSN and LOCALSSN are specified, LOCALSSN is used.
When using the prov-exp command, LOCALSSN is used.
SUA Key
This component represents a SUA Routing key. The parent component for the SUAKEY is the OPC.
MML NameSUAKEY
Note
Parameter Description
NAME
DESC
Component description
OPC
Associated OPC
APC
Associated APC
(optional)
LOCAL SSN
ROUTING CONTEXT
NETWORK
APPEARNCE
Network appearance
(optional)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-78
OL-1110-23
Appendix A
Two M3UA keys or SUA keys cannot have the same routing context value
SUA Route
This component represents a SUA route. It is used to determine how to get an SS7 message to a particular
destination using SUA.
MML NameSUAROUTE
Note
Parameter Description
NAME
DESC
Component description
APC
Associated APC
EXTNODE
Associated external
node
OPC
Associated OPC
REMOTESSN
Associated remote SSN Number of a remote SSN. Values are 0, 2-254 (0).
NAME is the only parameter for this command that cannot be modified.
The following rules apply when creating/editing SUA routes:
The associated APC must have an SS7 subsystem with an SUA key defined. If an SUA key is not
defined when the provisioning session is saved and activated, an error message is generated and the
operation is stopped.
Multiple APCs with the same NETADDR cannot be routed to the same OPC.
For a given OPC, DPC, and remote SSN set, only one route can be defined through a given external
node.
Up to two SUA routes can be defined per OPC, APC, and remote SSN set.
SUA routes for the same OPC-APC pair must have external nodes in the same group.
When the provisioning session is saved and activated, there must be an ASSOCIATION of type SUA
using an SGP that is using the EXTNODE of each SUAROUTE.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-79
Appendix A
Components
MML NameSGP
The SS7 signaling gateway process component structure is shown in Table A-51.
Table A-51
Note
Parameter Description
NAME
DESC
Component description
EXTNODE
DESC is the only parameter for this command that can be modified.
The following rules apply when creating/editing SS7 signaling gateway processes:
For the provisioning session to be copied or deployed without error, an SCTP association must be
using the SS7 signaling gateway process.
MML NameSWITCHTRNK
Parameter
Description
NAME
Trunk group
member number
TRNKGRPNUM
Trunk group
number
SPAN
Span
CIC
Circuit Identifier
Code.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-80
OL-1110-23
Appendix A
Table A-52
Parameter
Description
CU
ENDPOINT
End point
End point
SPANSIZE
Number of trunks
per span.
TARIFF
This is the Cisco PGW 2200 Softswitch NE component used to provision entries in the Tariff table. Its
MML name is as follows:
MML NameTARIFF
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
TARIFFID
Tariff ID
TARIFFRATE
Tariff rate
SCALEFACTOR
Scale factor
Note
MML NameTCPLINK
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-81
Appendix A
Components
Table A-54
Parameter MML
Name
Parameter Description
NAME
Unique component
name used in MML
commands
DESC
Component description
TYPE
IPADDR
Local IP address
PORT
Port number
PEERADDR
Highest priority
destination address
PEERPORT
EXTNODE
IPROUTE
NAME
EXTNODE
The following rules apply when you are creating or editing ISDN BRI signaling services:
You must define the TYPE parameter as PRI. If the TYPE parameter is not defined as PRI when the
TCPLINK is added/edited, a warning is issued. If the TYPE parameter is not defined as PRI when
the provisioning session is copied or deployed, an error message is generated and the copy or
deployment is stopped.
You must define the TCPLINK parameter with the same EXTNODE attribute that its associated
BRIPATH has. If the TCPLNK is not defined when the BRIPATH is added/edited, a warning is
issued. If the TCPLINK is not defined when the provisioning session is copied or deployed, an error
message is generated and the copy or deployment is stopped.
If the TCPLINK with the same EXTNODE value as the BRIPATH is deleted, a warning message is
issued to inform you that the BRIPATH must also be deleted. If the BRIPATH is not deleted when
the provisioning session is copied or deployed, an error message is generated and the copy or
deployment is stopped.
Only two combinations of local IP address and port number can be used per
Cisco PGW 2200 Softswitch. Once you have identified two unique local IP address and port number
combinations, all subsequent Backhaul TCP links must use one of those combinations.
TDM Interface
The TDM interface component type represents a TDM interface used on the
Cisco PGW 2200 Softswitch. Its MML name is as follows:
MML NameTDMIF
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-82
OL-1110-23
Appendix A
Note
Parameter
MML Name
Parameter Description
NAME
DESC
Component description
CARD
LIFNUM
RESIST
DATARATE
Data rate
CLOCK
Internal or external
DTEDCE
DTE or DCE
CODING
Line coding
FORMAT
Interface Format
SIGTYPE
Signal type
HDLC
TDM Link
The TDM link component type represents a TDM link used on the Cisco PGW 2200 Softswitch. Its
MML name is as follows:
MML NameTDMLNK
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-83
Appendix A
Components
Note
Parameter MML
Name
Parameter Description
NAME
DESC
Component description
SLC
0 to 15; (1)
PRI
Priority
SVC
IF
TIMESLOT
MML NameTRNKGRP
The trunk group provisioning interface component structure is shown in Table A-57.
Table A-57
Parameter MML
Name
Parameter Description
NAME
CLLI
CLLI
SVC
Signaling service
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-84
OL-1110-23
Appendix A
Table A-57
TYPE
SELSEQ
Select sequence
QABLE
Y or N; (N)
ORIG LABEL
TERM LABEL
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-85
Appendix A
Components
MML NameTRNKGRPROF
The trunk group profile provisioning component structure is shown in Table A-58.
Table A-58
Parameter MML
Name
NAME
Parameter Description
MML NameGTDPARAM
Parameter MML
Name
Parameter Description
NAME
GTDPARAMSTRI
NG
Table A-60 lists the GTD parameters that can be entered in the build_string in alphabetical order.
Table A-60
GTP Parameters
ADI
APP
Application Transport
ATP
Access Transport
BCI
BSG
Business Group
BVN
Backward GVNS
CAI
Cause Indicators
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-86
OL-1110-23
Appendix A
Table A-60
CCS
CDI
CDN
CDT
CGL
CGN
CHI
CHN
Charge Number
CIC
CID
Carrier Identification
CIN
Called IN Number
CMI
CNF
CNN
Connected Number
CNR
Connection Request
COL
COR
Correlation Identity
CPC
CPN
CRF
Call Reference
CSI
CSP
CTI
Continuity Indicators
CTN
CTR
DIS
Display Information
ECI
EGR
Egress
EVI
FAI
Facility Indicators
FCI
FDC
FVN
Forward GVNS
GCI
GEA
Generic Address
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-87
Appendix A
Components
Table A-60
Generic Digits
GEN
Generic Name
GIC
GNO
Generic Notification
GRF
Generic Reference
HOC
Hop Counter
HTR
Hard To Reach
INI
Information Indicators
IRI
ISC
JUR
Jurisdiction
LON
Location Number
LPI
LSP
MCI
MCR
MLP
MLPP precedence
MRI
NET
Network Transport
NMC
NOC
NPF
NRN
NSF
OBI
OCI
OCN
OCT
OFI
OLI
OSI
OTN
PBI
PCA
Pivot Capability
PCI
PCT
Pivot Counter
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-88
OL-1110-23
Appendix A
Table A-60
CCS
CDI
CDN
CDT
CGL
CGN
CHI
CHN
Charge Number
CIC
CID
Carrier Identification
CIN
Called IN Number
CMI
CNF
CNN
Connected Number
CNR
Connection Request
COL
COR
Correlation Identity
CPC
CPN
CRF
Call Reference
CSI
CSP
CTI
Continuity Indicators
CTN
CTR
DIS
Display Information
ECI
EGR
Egress
EVI
FAI
Facility Indicators
FCI
FDC
FVN
Forward GVNS
GCI
GEA
Generic Address
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-89
Appendix A
Components
Table A-60
CCS
CDI
CDN
CDT
CGL
CGN
CHI
CHN
Charge Number
CIC
CID
Carrier Identification
CIN
Called IN Number
CMI
CNF
CNN
Connected Number
CNR
Connection Request
COL
COR
Correlation Identity
CPC
CPN
CRF
Call Reference
CSI
CSP
CTI
Continuity Indicators
CTN
CTR
DIS
Display Information
ECI
EGR
Egress
EVI
FAI
Facility Indicators
FCI
FDC
FVN
Forward GVNS
GCI
GEA
Generic Address
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-90
OL-1110-23
Appendix A
Table A-60
CCS
CDI
CDN
CDT
CGL
CGN
CHI
CHN
Charge Number
CIC
CID
Carrier Identification
CIN
Called IN Number
CMI
CNF
CNN
Connected Number
CNR
Connection Request
COL
COR
Correlation Identity
CPC
CPN
CRF
Call Reference
CSI
CSP
CTI
Continuity Indicators
CTN
CTR
DIS
Display Information
ECI
EGR
Egress
EVI
FAI
Facility Indicators
FCI
FDC
FVN
Forward GVNS
GCI
GEA
Generic Address
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-91
Appendix A
Components
Table A-60
Generic Digits
GEN
Generic Name
GIC
GNO
Generic Notification
GRF
Generic Reference
HOC
Hop Counter
HTR
Hard To Reach
INI
Information Indicators
IRI
ISC
JUR
Jurisdiction
LON
Location Number
LPI
LSP
MCI
MCR
MLP
MLPP precedence
MRI
NET
Network Transport
NMC
NOC
NPF
NRN
NSF
OBI
OCI
OCN
OCT
OFI
OLI
OSI
OTN
PBI
PCA
Pivot Capability
PCI
PCT
Pivot Counter
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-92
OL-1110-23
Appendix A
Table A-60
PFI
PRI
PRN
Protocol Name
PVS
Pivot Status
QOR
RBI
RCT
Redirect Counter
RDC
Redirect Capability
RDS
Redirect Status
RFI
RGN
Redirecting Number
RMO
Remote Operations
RNI
Redirection Information
RNN
Redirection Number
RNR
SCF
SCF ID
SCI
SEA
Service Activation
SEG
Segmentation Indicator
SPC
SPR
SRI
Suspend/Resume Indicators
SUN
Subsequent Number
TID
Transaction ID
TMP
TMR
TMU
TNS
TRR
Transaction Request
UCI
UFC
UID
UID Indicators
USI
USP
UTI
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-93
Appendix A
Components
Table A-60
User-To-User Indicators
UUS
User-To-User Information
VER
Version of GTD
Component MML
Name
Parameter
Description
DIALPLAN
OVERDEC
Overdecadic Status
ADIGTREE
SETNAME
DIGITTOPRESENT
Digit
CALLSIDE
string
DIGITSTRING
Digits
SETNAME
DIGITTOPRESENT
Digit
CALLSIDE
string
DIGITSTRING
Digits
NAME
Result Name
RESULTTYPE
Result type
; (0)
DW1
Data word 1
; (x)
DW2
Data word 2
; (x)
DW3
Data word 3
; (x)
DW4
Data word 4
; (x)
NEXTRESULT
; (x)
SETNAME
NAME
Digit Modification
Name
DIGSTRING
Digit string
; (x)
BDIGTREE
RESULTTABLE
DIGMODSTRING
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-94
OL-1110-23
Appendix A
Table A-61
Component MML
Name
ANOA
NOAVALUE
A-number NOA
Value
; (0)
NPIBLOCK
NPI index
; (0)
SETNAME
NPIBLOCK
; (0)
BLOCKVALUE
Block value
SETNAME
NOAVALUE
B-number NOA
Value
; (0)
NPIBLOCK
NPI index
; (0)
SETNAME
NPIBLOCK
; (0)
BLOCKVALUE
Block value
SETNAME
CAUSEVALUE
Cause Value
; (0)
LOCATIONBLOCK
Location block
; (0)
SETNAME
LOCATIONBLOCK
Location Block
; (0)
SETNAME
BLOCKVALUE
Block value
SERVICE
NAME
Service name
RESULTSET
NAME
AWHITE
CLI
ABLACK
CLI
BWHITE
CLI
SVCNAME
Service name
CLI
SVCNAME
Service name
DIGITSTRING
ROUTENUM
Routing Number
; (x)
DIGITSTRING
Number Termination
Table
; (x)
RTLISTNAME
; (x)
ANPI
BNOA
BNPI
CAUSE
LOCATION
BBLACK
PORTTBL
TERMTBL
Parameter
Description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-95
Appendix A
Components
Table A-61
Component MML
Name
ACHGORIGIN
CUSTGRPID
Customer Group
Identity
CLI
CORIGIN
Charge Origin
RESULTTYPE
Result Type
; (0)
DW1
Data Word 1
; (x)
DW2
Data Word 2
; (x)
DW3
Data Word 3
; (x)
DW4
Data Word 4
; (x)
DPSEL
NEWDP
ANUMDPSEL
CLI
NEWDP
DATE
HDAY
Holiday day
CPCVALUE
CPC value.
SETNAME
TMRVALUE
TMR value.
SETNAME
TNSVALUE
TNS value.
SETNAME
CLISETNAME
CLIPREFIX
CUSTGRPID
CUSTGRPID
IPADDR
The IP Address.
IP address or DEFAULT.
SUBNETMASK
IP address (255.255.255.255).
CLISETNAME
DEFRESULSTSET
RTEHOLIDAY
CPC
TMR
TNS
CLIPREFIX
CLIIPADDRESS
Parameter
Description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-96
OL-1110-23
Appendix A
Table A-61
Component MML
Name
Parameter
Description
H323IDDIVFROM
CUSTGRPID
H323IDDIVFROM
CLISETNAME
To add, modify, or delete the contents of a dial plan table, an active provisioning session is required. At
the time of deploying or copying, dial plan files from the provisioning directory are copied to the active
directory. Active directory for dial plan files is: /opt/MGC/dialPlan.
All the TIDs, with the exception of DIALPLAN, need a customer group ID and a name. DIALPLAN
only needs customer group ID. The verb ED cannot be used with the DIALPLAN. The verb RTRV can
be used with DIALPLAN to determine all of the dialplans currently configured.
Routes and digit modification string table should be provisioned before result and digit tree tables.
When an index is added to a table the missing indices are also added with default values. For example,
if index 10 is added to A digit tree table, and indexes 4 to 9 are missing, they are added with default
values.
When an index is deleted from a result or digit tree table, all the elements in the index are made 0s. When
an index is deleted from routes or digit modification string table all the elements in the index are made
x. When an index is deleted from any table and if there are no indexes with non-default values
following this index, all the indexes following this index are deleted.
The modify command is not supported for result sets as modifications would be done at the result table
level.
The modify command is not supported for the service table.
When an entry is added to the result table, the corresponding entry is added to the result set table.
When an entry is deleted from the result set table, the corresponding entries are deleted from the result
table.
Index is no longer required to perform any operations on the result table, service table, or digit
modification table.
The result set cannot be modified for a result table.
The TIDs dialplan, resulttable, digmodstring, noa, npi, cause, location, service, and resultset support the
ability to retrieve all entries in the table by specifying all. For example:
numan-rtrv:resultset:custgrpid=T001,all.
The TIDs adigtree and bdigtree support the ability to retrieve all entries in the table by either not
specifying a digitstring or specifying an empty digitstring. For example:
numan-rtrv:adigtree:custgrpid= T001,digitstring=
Configuring a result set as the default result set replaces the previous result set.
The default result set can only have one of the following result types: BLACKLIST, ROUTE, or
CAUSE.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-97
Appendix A
Processes
Processes
This section describes every process that the Cisco PGW 2200 Softswitch is responsible for monitoring.
Three different monitoring levels are offered:
Active ProcessA process identified in the record that is controlled and monitored directly by the
Process Manager.
Passive ProcessA process identified in the record that does not communicate with the Process
Manager.
Monitoring ProcessA process that periodically runs an executable or script and sets or clears an
alarm based on the return code. This type of process may monitor other processes or tasks that can
be checked programmatically. Examples include the amount of disk space, system daemon
existence, and established process dependency.
Table A-62 contains an alphabetical listing of process names and their descriptions.
Table A-62
Processes
Process
Description
ALM-01
AMDMPR-01
CDRDMPR-01
CFM-01
DSKM-01
ENG-01
FOD-01
IOCC-01
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-98
OL-1110-23
Appendix A
Table A-62
Processes (continued)
Process
Description
IOCC-02
IOCM-01
LOG-01
MEASAGT
MM-01
MMDB-01
OPERSAGT
POM-01
PROVSAGT
Replic-01
TCAP-01
Properties
Properties are configurable entities within the Cisco PGW 2200 Softswitch system. These entities can
be equipment, circuits, protocols, or software.
Properties take the following syntax:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-99
Appendix A
Protocol Variants
PropertyName = PropertyValue
Protocol Variants
The tables in this section list the protocol variants supported for the corresponding software release.
Protocol Family
Switch Supported
ETS_300_102
ISDNPRI
27
ETS_300_102_C2
ISDNPRI
27
ATT_41459
ISDNPRI
17
ATT_41459_C2
ISDNPRI
17
BELL_1268
ISDNPRI
22
ETS_300_172
ISDNPRI
29
BELL_1268_C2
ISDNPRI
22
ETS_300_121
SS7-ITU
Q931_AUSTRALIA
ISDNPRI
19
Q931
ISDNPRI
27
Q931_SINGAPORE
ISDNPRI
27
GR317
SS7-ANSI
ANSISS7_92
SS7-ANSI
ANSISS7_STANDARD
SS7-ANSI
ANSISS7_C2
SS7-ANSI
20
ANSISS7_C3
SS7-ANSI
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-100
OL-1110-23
Appendix A
Table A-63
Protocol Family
Switch Supported
ANSISS7_E1
SS7-ANSI
23
ANSISS7_2K
SS7-ANSI
BTNUP_BTNR167
SS7-UK
BTNUP_IUP
SS7-UK
HONGKONG
SS7-ITU
ETS_300_356
SS7-ITU
ISUPV2_FRENCH
SS7-ITU
ISUPV2_AUSTRIAN
SS7-ITU
ISUPV2_SWISS
SS7-ITU
ISUPV2_SWISS_C2
SS7-ITU
ISUPV2_GERMAN
SS7-ITU
ISUPV2_FINNISH96
SS7-ITU
ISUPV1_POLI
SS7-ITU
ISUPV2_POLISH
SS7-ITU
ISUPV2_DUTCH
SS7-ITU
ISUPV2_JAPAN
SS7-Japan
10
ISUPV2_JAPAN_C2
SS7-Japan
ISUPV2_CZECH
SS7-ITU
ISUPV3
SS7-ITU
ISUPV3_UK
SS7-UK
ISUPV3_UK_C2 SS7-UK
SS7-UK
15
ISUPV3_UK_C3 SS7-UK
SS7-UK
ISUPV3_UK_C4
SS7-UK
15
ISUPV2_SPANISH_C2
SS7-ITU
ISUPV2_SPANISH
SS7-ITU
ISUPV2_32DIG
SS7-ITU
ISUPV2_VIETNAM
SS7-ITU
ISUPV2_NORWEGIAN
SS7-ITU
ISUPV2_ISRAEL
SS7-ITU
40
Q721_FRENCH
SS7-ITU
Q721_CHINA
SS7-China
Q721_BASE
SS7-ITU
Q721_PHILLIPINE
SS7-ITU
Q721_BRAZILIAN
SS7-ITU
Q761_97VER
SS7-ITU
Q761_CHINA
SS7-China
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-101
Appendix A
Protocol Variants
Table A-63
Protocol Family
Switch Supported
Q761_CHINA_C2
SS7-China
Q761_BELG_C2
SS7-ITU
Q761_BELG_C3
SS7-ITU
Q761_DANISH
SS7-ITU
Q761_INDIA
SS7-ITU
Q761_MALAYSIAN
SS7-ITU
Q761_JAPAN
SS7-Japan
10
Q761_KOREAN
SS7-ITU
Q761_TAIWAN
SS7-ITU
Q761_CHILE
SS7-ITU
Q761_SINGAPORE
SS7-ITU
Q761_SINGAPORE_C2
SS7-ITU
Q761_THAILAND
SS7-ITU
Q761_ARGENTINA
SS7-ITU
Q761_ARGENTINA_C2
SS7-ITU
Q761_BELG
SS7-ITU
Q761_AUSTRL
SS7-ITU
Q761_AUSTRL_C2
SS7-ITU
Q761_NEWZEALAND
SS7-ITU
Q761_BASE
SS7-ITU
Q761_PORTUGAL
SS7-ITU
Q761_GERMAN
SS7-ITU
Q761_PERU
SS7-ITU
Q767_BASE
SS7-ITU
Q767_SPAN
SS7-ITU
Q767_ITAL
SS7-ITU
Q767_RUSS
SS7-ITU
Q767_SWED
SS7-ITU
Q767_ITAL_C2
SS7-ITU
Q767_MEXICAN
SS7-ITU
Q767_AUSTRALIA
SS7-ITU
Q767_COLOMBIA
SS7-ITU
Q767_INDONESIA
SS7-ITU
Q767_BRAZIL
SS7-ITU
Q767_GUATEMALA
SS7-ITU
Q767_TURKISH
SS7-ITU
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-102
OL-1110-23
Appendix A
Table A-63
Protocol Family
Switch Supported
Q767_SINGAPORE
SS7-ITU
Q767_NIGERIAN
SS7-ITU
EISUP
EISUP
BELL_SGCP
MGCP
MGCPCAS
CAS
dummy
SGCP
dummy
MGCP
dummy
TCAPOverIP
dummy
VSI
dummy
AVM
IETF_SIP
SIP
IETF_DCS
SIP
Protocol Family
Switch Supported
DPNSS_BTNR188
DPNSS
26
ETS_300_102
ISDNPRI
27
ETS_300_102_C2
ISDNPRI
27
ATT_41459
ISDNPRI
17
ATT_41459_C2
ISDNPRI
17
BELL_1268
ISDNPRI
22
ETS_300_172
ISDNPRI
29
BELL_1268_C2
ISDNPRI
22
ETS_300_121
SS7-ITU
Q931_AUSTRALIA
ISDNPRI
19
Q931
ISDNPRI
27
Q931_SINGAPORE
ISDNPRI
27
GR317
SS7-ANSI
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-103
Appendix A
Protocol Variants
Table A-64
Protocol Family
Switch Supported
ANSISS7_92
SS7-ANSI
ANSISS7_STANDARD
SS7-ANSI
ANSISS7_C2
SS7-ANSI
20
ANSISS7_C3
SS7-ANSI
ANSISS7_E1
SS7-ANSI
23
ANSISS7_2K
SS7-ANSI
BTNUP_BTNR167
SS7-UK
BTNUP_IUP
SS7-UK
HONGKONG
SS7-ITU
ETS_300_356
SS7-ITU
ISUPV2_FRENCH
SS7-ITU
ISUPV2_AUSTRIAN
SS7-ITU
ISUPV2_AUSTRIAN_C2
SS7-ITU
ISUPV2_SWISS
SS7-ITU
ISUPV2_SWISS_C2
SS7-ITU
ISUPV2_GERMAN
SS7-ITU
ISUPV2_FINNISH96
SS7-ITU
ISUPV1_POLI
SS7-ITU
ISUPV2_POLISH
SS7-ITU
ISUPV2_DUTCH
SS7-ITU
ISUPV2_JAPAN
SS7-Japan
10
ISUPV2_JAPAN_C2
SS7-Japan
ISUPV2_CZECH
SS7-ITU
ISUPV3
SS7-ITU
ISUPV3_UK
SS7-UK
ISUPV3_UK_C2
SS7-UK
15
ISUPV3_UK_C3
SS7-UK
ISUPV3_UK_C4
SS7-UK
15
ISUPV2_SPANISH_C2
SS7-ITU
ISUPV2_SPANISH
SS7-ITU
ISUPV2_32DIG
SS7-ITU
ISUPV2_VIETNAM
SS7-ITU
ISUPV2_NORWEGIAN
SS7-ITU
ISUPV2_ISRAEL
SS7-ITU
40
Q721_FRENCH
SS7-ITU
Q721_CHINA
SS7-China
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-104
OL-1110-23
Appendix A
Table A-64
Protocol Family
Switch Supported
Q721_BASE
SS7-ITU
Q721_PHILLIPINE
SS7-ITU
Q721_BRAZILIAN
SS7-ITU
Q761_CHINA
SS7-China
Q761_CHINA_C2
SS7-China
Q761_DANISH
SS7-ITU
Q761_INDIA
SS7-ITU
Q761_MALAYSIAN
SS7-ITU
Q761_JAPAN
SS7-Japan
10
Q761_KOREAN
SS7-ITU
Q761_TAIWAN
SS7-ITU
Q761_CHILE
SS7-ITU
Q761_SINGAPORE
SS7-ITU
Q761_SINGAPORE_C2
SS7-ITU
Q761_THAILAND
SS7-ITU
Q761_ARGENTINA
SS7-ITU
Q761_ARGENTINA_C2
SS7-ITU
Q761_BELG
SS7-ITU
Q761_BELG_97VER
SS7-ITU
Q761_AUSTRL
SS7-ITU
Q761_AUSTRL_C2
SS7-ITU
Q761_NEWZEALAND
SS7-ITU
Q761_BASE
SS7-ITU
Q761_PORTUGAL
SS7-ITU
Q761_GERMAN
SS7-ITU
Q761_PERU
SS7-ITU
Q767_BASE
SS7-ITU
Q767_SPAN
SS7-ITU
Q767_ITAL
SS7-ITU
Q767_RUSS
SS7-ITU
Q767_SWED
SS7-ITU
Q767_ITAL_C2
SS7-ITU
Q767_MEXICAN
SS7-ITU
Q767_AUSTRALIA
SS7-ITU
Q767_COLOMBIA
SS7-ITU
Q767_INDONESIA
SS7-ITU
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-105
Appendix A
Protocol Variants
Table A-64
Protocol Family
Switch Supported
Q767_BRAZIL
SS7-ITU
Q767_GUATEMALA
SS7-ITU
Q767_TURKISH
SS7-ITU
Q767_SINGAPORE
SS7-ITU
Q767_NIGERIAN
SS7-ITU
EISUP
EISUP
BELL_SGCP
MGCP
MGCPCAS
CAS
dummy
SGCP
dummy
MGCP
dummy
TCAPOverIP
dummy
VSI
dummy
AVM
IETF_SIP
SIP
IETF_DCS
SIP
Protocol Family
Switch Supported
DPNSS_BTNR188
DPNSS
26
ETS_300_102
ISDNPRI
27
ETS_300_102_C2
ISDNPRI
27
ATT_41459
ISDNPRI
17
ATT_41459_C2
ISDNPRI
17
BELL_1268
ISDNPRI
22
ETS_300_172
ISDNPRI
29
BELL_1268_C2
ISDNPRI
22
ETS_300_121
SS7-ITU
Q931_AUSTRALIA
ISDNPRI
19
Q931
ISDNPRI
27
Q931_SINGAPORE
ISDNPRI
27
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-106
OL-1110-23
Appendix A
Table A-65
Protocol Family
Switch Supported
GR317
SS7-ANSI
ANSISS7_92
SS7-ANSI
ANSISS7_STANDARD
SS7-ANSI
ANSISS7_C2
SS7-ANSI
20
ANSISS7_C3
SS7-ANSI
ANSISS7_E1
SS7-ANSI
23
ANSISS7_2K
SS7-ANSI
BTNUP_BTNR167
SS7-UK
BTNUP_IUP
SS7-UK
HONGKONG
SS7-ITU
ETS_300_356
SS7-ITU
ISUPV2_FRENCH
SS7-ITU
ISUPV2_AUSTRIAN
SS7-ITU
ISUPV2_AUSTRIAN_C2
SS7-ITU
ISUPV2_SWISS
SS7-ITU
ISUPV2_SWISS_C2
SS7-ITU
ISUPV2_GERMAN
SS7-ITU
ISUPV2_FINNISH96
SS7-ITU
ISUPV1_POLI
SS7-ITU
ISUPV2_POLISH
SS7-ITU
ISUPV2_DUTCH
SS7-ITU
ISUPV2_JAPAN
SS7-Japan
10
ISUPV2_JAPAN_C2
SS7-Japan
ISUPV2_CZECH
SS7-ITU
ISUPV3
SS7-ITU
ISUPV3_UK
SS7-UK
ISUPV3_UK_C2
SS7-UK
15
ISUPV3_UK_C3
SS7-UK
ISUPV3_UK_C4
SS7-UK
15
ISUPV2_SPANISH_C2
SS7-ITU
ISUPV2_SPANISH
SS7-ITU
ISUPV2_VIETNAM
SS7-ITU
ISUPV2_NORWEGIAN
SS7-ITU
ISUPV2_ISRAEL
SS7-ITU
40
Q721_FRENCH
SS7-ITU
Q721_CHINA
SS7-China
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-107
Appendix A
Protocol Variants
Table A-65
Protocol Family
Switch Supported
Q721_BASE
SS7-ITU
Q721_PHILLIPINE
SS7-ITU
Q721_BRAZILIAN
SS7-ITU
Q721_BRAZILIAN_C2
SS7-ITU
Q761_97VER_BASE
SS7-ITU
Q761_99VER_BASE
SS7-ITU
Q761_CHINA
SS7-China
Q761_CHINA_C2
SS7-China
Q761_DANISH
SS7-ITU
Q761_INDIA
SS7-ITU
Q761_MALAYSIAN
SS7-ITU
Q761_KOREAN
SS7-ITU
Q761_TAIWAN
SS7-ITU
Q761_CHILE
SS7-ITU
Q761_SINGAPORE
SS7-ITU
Q761_SINGAPORE_C2
SS7-ITU
Q761_THAILAND
SS7-ITU
Q761_ARGENTINA
SS7-ITU
Q761_ARGENTINA_C2
SS7-ITU
Q761_BELG
SS7-ITU
Q761_BELG_97VER
SS7-ITU
Q761_AUSTRL
SS7-ITU
Q761_AUSTRL_C2
SS7-ITU
Q761_99VER_AUSTRL_C3
SS7-ITU
Q761_97VER_RUSS
SS7-ITU
Q761_NEWZEALAND
SS7-ITU
Q761_BASE
SS7-ITU
Q761_PORTUGAL
SS7-ITU
Q761_GERMAN
SS7-ITU
Q761_PERU
SS7-ITU
Q767_BASE
SS7-ITU
Q767_SPAN
SS7-ITU
Q767_ITAL
SS7-ITU
Q767_RUSS
SS7-ITU
Q767_RUSS_C2
SS7-ITU
Q767_SWED
SS7-ITU
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-108
OL-1110-23
Appendix A
Table A-65
Protocol Family
Switch Supported
Q767_ITAL_C2
SS7-ITU
Q767_MEXICAN
SS7-ITU
Q767_AUSTRALIA
SS7-ITU
Q767_COLOMBIA
SS7-ITU
Q767_INDONESIA
SS7-ITU
Q767_BRAZIL
SS7-ITU
Q767_BRAZIL_C2
SS7-ITU
Q767_GUATEMALA
SS7-ITU
Q767_TURKISH
SS7-ITU
Q767_SINGAPORE
SS7-ITU
Q767_NIGERIAN
SS7-ITU
EISUP
EISUP
dummy
SGCP
dummy
MGCP
dummy
TCAPOverIP
dummy
VSI
dummy
AVM
dummy
LI
IETF_SIP
SIP
Protocol Family
Switch Supported
ANSISS7_2K
SS7-ANSI
BTNUP_BTNR167
SS7-UK
BTNUP_IUP
SS7-UK
HONGKONG
SS7-ITU
ETS_300_356
SS7-ITU
ISUPV2_FRENCH
SS7-ITU
ISUPV2_AUSTRIAN
SS7-ITU
ISUPV2_AUSTRIAN_C2
SS7-ITU
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-109
Appendix A
Protocol Variants
Table A-66
Protocol Family
Switch Supported
ISUPV2_SWISS
SS7-ITU
ISUPV2_SWISS_C2
SS7-ITU
ISUPV2_GERMAN
SS7-ITU
ISUPV2_FINNISH96
SS7-ITU
ISUPV1_POLI
SS7-ITU
ISUPV2_POLISH
SS7-ITU
ISUPV2_DUTCH
SS7-ITU
ISUPV2_JAPAN
SS7-Japan
10
ISUPV2_JAPAN_C2
SS7-Japan
ISUPV2_CZECH
SS7-ITU
ISUPV3
SS7-ITU
ISUPV3_UK
SS7-UK
ISUPV3_UK_C2
SS7-UK
15
ISUPV3_UK_C3
SS7-UK
ISUPV3_UK_C4
SS7-UK
15
ISUPV2_SPANISH_C2
SS7-ITU
ISUPV2_SPANISH
SS7-ITU
ISUPV2_VIETNAM
SS7-ITU
ISUPV2_NORWEGIAN
SS7-ITU
ISUPV2_ISRAEL
SS7-ITU
40
Q721_FRENCH
SS7-ITU
Q721_CHINA
SS7-China
Q721_BASE
SS7-ITU
Q721_PHILLIPINE
SS7-ITU
Q721_BRAZILIAN
SS7-ITU
Q721_BRAZILIAN_C2
SS7-ITU
Q761_97VER_BASE
SS7-ITU
Q761_99VER_BASE
SS7-ITU
Q761_CHINA
SS7-China
Q761_CHINA_C2
SS7-China
Q761_DANISH
SS7-ITU
Q761_INDIA
SS7-ITU
Q761_MALAYSIAN
SS7-ITU
Q761_KOREAN
SS7-ITU
Q761_TAIWAN
SS7-ITU
Q761_CHILE
SS7-ITU
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-110
OL-1110-23
Appendix A
Table A-66
Protocol Family
Switch Supported
Q761_SINGAPORE
SS7-ITU
Q761_SINGAPORE_C2
SS7-ITU
Q761_THAILAND
SS7-ITU
Q761_ARGENTINA
SS7-ITU
Q761_ARGENTINA_C2
SS7-ITU
Q761_BELG
SS7-ITU
Q761_BELG_97VER
SS7-ITU
Q761_AUSTRL
SS7-ITU
Q761_AUSTRL_C2
SS7-ITU
Q761_99VER_AUSTRL_C3
SS7-ITU
Q761_NEWZEALAND
SS7-ITU
Q761_BASE
SS7-ITU
Q761_PORTUGAL
SS7-ITU
Q761_GERMAN
SS7-ITU
Q761_PERU
SS7-ITU
Q767_BASE
SS7-ITU
Q767_SPAN
SS7-ITU
Q767_ITAL
SS7-ITU
Q767_RUSS
SS7-ITU
Q767_RUSS_C2
SS7-ITU
Q767_SWED
SS7-ITU
Q767_ITAL_C2
SS7-ITU
Q767_MEXICAN
SS7-ITU
Q767_AUSTRALIA
SS7-ITU
Q767_COLOMBIA
SS7-ITU
Q767_INDONESIA
SS7-ITU
Q767_BRAZIL
SS7-ITU
Q767_BRAZIL_C2
SS7-ITU
Q767_GUATEMALA
SS7-ITU
Q767_TURKISH
SS7-ITU
Q767_SINGAPORE
SS7-ITU
Q767_NIGERIAN
SS7-ITU
EISUP
EISUP
dummy
SGCP
dummy
MGCP
dummy
TCAPOverIP 0
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
A-111
Appendix A
Protocol Variants
Table A-66
Protocol Family
Switch Supported
dummy
VSI
dummy
AVM
dummy
LI
IETF_SIP
SIP
QBE
CTI-QBE
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
A-112
OL-1110-23
A P P E N D I X
Planning Worksheets
Revised: February 25, 2010, OL-1110-23
You will find a variety of planning worksheets for you to copy and fill in. The worksheets contain a
sample entry for the component and then blank rows for you to fill in.
Table B-1
Name
Type
Slot
Description
en-1
EN
Ethernet interface 1
Table B-2
Name
Card
Description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
B-1
Appendix B
Table B-3
Planning Worksheets
Device IP Address
(x.x.x.x)
Device Name
Description
10.15.7.34
as5300-34
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
B-2
OL-1110-23
Appendix B
Planning Worksheets
Table B-4
Name
Netaddr
Netind
Description
OPC Type
True OPC
OPC1
22.22.23
MGC 1 OPC
TRUEOPC
OPC1
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
B-3
Appendix B
Table B-5
Planning Worksheets
Name
Netaddr
Netind
Description
DPC1
32.32.33
DPC 1
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
B-4
OL-1110-23
Appendix B
Planning Worksheets
Table B-6
Name
Netaddr
Netind
Description
Type
STP1
12.12.13
TRUEOPC
True OPC
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
B-5
Appendix B
Table B-7
Planning Worksheets
Name
Netaddr
Netind
Description
STP1
12.12.13
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
B-6
OL-1110-23
Appendix B
Table B-8
Planning Worksheets
Name
External
Node
brisvc1
va-3640-01
Q.931
Call Model
Side
MDO File
Customer
Group ID
ETS_300_102
Call
Reference
Length
Description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
B-7
Appendix B
Table B-9
Planning Worksheets
Name
Point Code
Type
Protocol
Description
Lnkset-1
DPC-1
IP
SS7-ANSI
Linkset 1 to ITP-L 1
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
B-8
OL-1110-23
Appendix B
Planning Worksheets
Table B-10
MML
Parameter
Name
Configuration Setting
NAME
ss7lnk1
SESSIONSET
slt1
PRIORITY
TIMESLOT
SLC
LNKSET
lnkset1
DESC
NAME
SESSIONSET
slt1
PRIORITY
TIMESLOT
SLC
LNKSET
DESC
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
B-9
Appendix B
Table B-11
MML
Parameter
Name
Value
NAME
eiplnk1
DESC
sigeisup1
SVC
sigeisup1
IF
EnIf2
IPADDR
IP_Addr_1
PORT
8001
PEERADDR
172.24.235.205
PEERPORT
8001
PRIORITY
NEXTHOP
0.0.0.0
NETMASK
255.255.255.255
Planning Worksheets
NAME
DESC
SVC
IF
IPADDR
PORT
PEERADDR
PEERPORT
PRIORITY
NEXTHOP
NETMASK
NAME
DESC
SVC
IF
IPADDR
PORT
PEERADDR
PEERPORT
PRIORITY
NEXTHOP
NETMASK
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
B-10
OL-1110-23
Appendix B
Planning Worksheets
Table B-12
Name
OPC
DPC
Linkset
Priority
Description
ss7rt1
opc
dpc1
lnkset1
SS7 Route to
dpc1 by stp1
ss7rt2
opc
dpc2
lnkset2
SS7 Route to
dpc1 by stp2
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
B-11
Appendix B
Table B-13
Planning Worksheets
Trunk ID
Source
Signaling
Service
Source
Span
Source
Time
slot/CIC
Dest Sig
Service
Dest
Span
Dest
Time
Span
Slot/CIC Size
101
ss7srv
fixed
signal1
fixed
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
B-12
OL-1110-23
Appendix B
Planning Worksheets
Table B-14
Trunk ID
Trunk
Group
Number
Span
CIC
Coding
Unit
End
Point
Span
Size
10101
25535
100
signal1
fixed
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
B-13
Appendix B
Table B-15
Parameter
Planning Worksheets
Parameter Value
apc2
Priority
Local SSN
STP/SCP Index
Transport
protocol
SCCP
OPC
ROUTING_KEY_ID
Routing Key
rtkey1
SUA Key
Remote SSN
Table B-16
Name
Type
Gw1
AS5300
ISDN
Signaling
Type
Group
Description
AS5300 gateway 1
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
B-14
OL-1110-23
Appendix B
Planning Worksheets
Table B-16
Name
Table B-17
MML Parameter
Name
Type
ISDN
Signaling
Type
Group
Description
Configuration Setting
NAME
MDO
EXTNODE
SIDE
CUSTGRPID
CUSTGRPTBL
ABFLAG
CRLEN
DESC
PATHSIZE
PORT
PEERPORT
SIGSLOT
SIGPORT
SIGPORTSKIP
BACKUP
Table B-18
NAME
CARD
Description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
B-15
Appendix B
Table B-19
Planning Worksheets
Name
Ext Node
Description
MGCpth1
Gw1
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
B-16
OL-1110-23
Appendix B
Table B-20
Name
Planning Worksheets
Side
MDO
DPC
CustgrpId
OPC
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
B-17
Appendix B
Table B-21
Planning Worksheets
Service Type
Name
Description
Protocol Type
Customer Group ID
SS7
ss7svc1
SS7 service to
DPC1
ANSISS7_
STANDARD
7777
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
B-18
OL-1110-23
Appendix B
Table B-22
Planning Worksheets
Description
Linkset
Card Interface
Linkset Type
Linkset Rate
Protocol
Signaling
Link 1 to
ITP-L1
ls-stpa
T1
A link
64 kbps
SS7-ANSI
10.15.7.5
10.15.7.8
Signaling
Link 2 to
ITP-L1
ls-stpb
T1
A link
64 kbps
SS7-ANSI
10.15.7.5
10.15.7.8
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
B-19
Appendix B
Table B-23
Name
Planning Worksheets
Interface
MGC-lnk1 EnIf1
Table B-24
IP
Address
Port
IP_Addr1 2427
Priority
Peer IP Address
Peer Port
Field
Service
Description
175.24.235.155
2427
mgcpsr-1
Name
Signaling
Type
Local
IP Address
Local
Port Number
Destination
IP Address
Destination
Port Number
External
Node
britcp1
bri
175.25.211.17
1024
175.25.211.17
1024
va-3640- na
01
Table B-25
IP Route
Description
IP route to
va-3640-01
Card
LIFNum
Resist
Data Rate
Clock
DTE/DCE
Coding
Format
Sig Type
HDLC
card1
56
EXT
DTE
NA
NA
V.35
HDLC
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
B-20
OL-1110-23
Appendix B
Planning Worksheets
Table B-25
Card
LIFNum
Resist
Data Rate
Clock
Table B-26
MML
Parameter
Name
Configuration Setting
DTE/DCE
Coding
Format
Sig Type
HDLC
DESC
IF
NAME
PRI
SLC
SVC
TIMESLOT
Table B-27
MML
Parameter
Name
Value
NAME
IPADDR1
IPADDR2
PORT
PEERADDR1
PEERADDR2
PEERPORT
EXTNODE
TYPE
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
B-21
Appendix B
Table B-28
Planning Worksheets
Name
Destination
Subnet Mask
Next Hop
IP Address
Priority
Description
iproute1
itp1
255.255.255.0
itp2
175.25.211.17
IP route to itp1
Table B-29
Q.931
Call Model
Side
MDO File
Name
External
Node
brisvc1
va-3640-01
Table B-30
Customer
Group ID
A-B
Flag
ETS_300_102
Call
Reference
Length
Description
Name
External
Node
dpnsvc2
va-3660-20
Customer
Group ID
DPNSS
Side
Signaling
Port
Signaling
Slot
Description
IUA DPNSSpath to GW
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
B-22
OL-1110-23
Appendix B
Planning Worksheets
Table B-30
External
Node
Name
Table B-31
Name
Customer
Group ID
DPNSS
Side
Signaling
Port
Signaling
Slot
Description
Signaling Type
brichan1 bri
Table B-32
Priority
Link
Slot
Port
Subunit
Description
britcp1
bri d-channel 1
Name
OPC
DPC
Routing
Context
Service Indicator
Network
Appearance
Description
m3key1
opc1
dpc1
14
ISUP
700
M3UA key 1
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
B-23
Appendix B
Table B-33
Planning Worksheets
Name
DPC
External Node
OPC
Description
m3rte1
dpc1
itp1
opc1
M3UA route 1
Table B-34
Parameter
Parameter Value
Name
assoc1
Description
association 1
Signaling Type
M3UA
SGP name
sgp1
175.23.211.15
n/a
2905
117.52.16.20
itp1
iproute2
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
B-24
OL-1110-23
Appendix B
Table B-34
Planning Worksheets
Parameter
Parameter Value
Table B-35
Name
External Node
Description
sgp1
itp1
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
B-25
Appendix B
Table B-35
Name
Table B-37
External Node
Table B-36
Planning Worksheets
Description
DPC
Linkset
OPC
Priority
dpc1
lnkset1
opc1
Name
Q.931 Call
Model Side
Customer Group ID
OPC or Route
Key ID
ss7svc1
network
ansi_ss7
0000
m3rtkey1
dpc1
Description
SS7 signaling
service 1
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
B-26
OL-1110-23
Appendix B
Table B-38
Planning Worksheets
Name
OPC
APC
Local SSN
Routing Context
Network
Appearance
Description
suakey1
opc1
apc1
70
ISUP
7000
SUA key 1
Table B-39
Name
APC
External Node
OPC
Remote SSN
Description
suarte1
apc1
itp1
opc1
100
SUA route 1
Table B-40
Name
Description
sipsrv1
va-3660-20
path to Unity
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
B-27
Appendix B
Table B-40
Name
Table B-41
Planning Worksheets
Description
Name
Signaling Service
Priority
IP Address
Port
Description
brichan1
bri
britcp1
bri d-channel 1
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
B-28
OL-1110-23
INDEX
call limiting
5-64
card
APC
3-10
Customer Group ID
DPC
3-28
3-11
channels
3-59
2-6, 2-7
1-3
3-86
CLI
linkset
3-17
C-links
MGCP IP links
3-86
SigSS7 component
SS7 route
3-27
2-6
bulk
4-3
component or parameter
address
3-27
4-3
2-2
session
5-8
2-2
3-10
4-3
4-6
3-154
component
association
ExtNode
provisioning
4-5
4-3
committing, configuration
adding
4-6
3-63
commands
3-31
SS7 subsystem
5-14
2-7
CIC
IP link
IP
3-61
2-10
3-55
component/parameter commands
4-3
components
adding
5-4
deleting
backup D-channel
batch file
4-33
creating
4-33
2-47
4-17
modifying
4-16
overriding properties
retrieving all
4-17
4-29
sample
4-33
retrieving one
starting
4-34
4-30
components to add
5-2
configuration
C
C7 IP link
4-30
committing
5-13
3-154
4-7
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
IN-1
Index
deploying
3-154
dual MGCs
4-10
4-8, 4-9
GTD parameters
4-8
GUI
4-33
A-86
1-3
GWDefaultCodecString
4-9
synchronizing data
4-10
terminating session
4-11
types of commands
4-3
5-56
5-17
configuring
importing
3-53
3-99
interface
3-28
Ethernet
2-29
interface card
definition
D-channel
2-47
deploying, configuration
destination
dnsparam
DPC
IPFASPath
3-154
IP link
2-2
iplnk
2-2, 5-3
3-60
3-86
5-18
IP redundancy
3-11
3-12
5-17
adding
5-48
DPC, adding
5-12
2-32
IP route
provisioning
ITP
A-8
5-63
5-16
5-12, 5-15
5-15
Japanese ISUP
3-54
ExtNode component
5-5
3-55
L
F
5-27
5-11
5-16
3-59
link
5-30
2-4
2-6
C7IP
IP
linkset
2-4
2-5
2-3, 5-8
adding
3-17
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
IN-2
OL-1110-23
Index
changing properties
location
3-19
2-2
location label
mgcppath
5-16
nailedtrnk
5-27
naspath
5-65
5-17
prov-add
prov-cpy
4-3, 4-9
prov-dlt
prov-dply
A-1, A-94
4-4, 4-10
prov-ed
3-86
3-64
4-5
5-16, 5-17
prov-exp
4-5, 4-6
prov-rtrv
4-5, 4-30
MGC software
prov-sta
starting
prov-stp
4-5, 4-11
MGW
4-1
prov-sync
2-2
ptcode
rtlist
5-15
5-3
5-28
rttrnk
5-17
rttrnkgrp
MML
ss7path
5-16
tdmif
5-14
tdmlnk
3-53
trnkgrp
c7iplnk
5-14, 5-16
4-1
5-47
trnkgrpprop
5-13
5-47
5-12, 5-15
dnsparam
5-48
eisuppath
5-16
enetif
5-12, 5-15
extnode
5-15
faspath
files
5-9
5-14
5-3, 5-8
card
5-10
ss7subsystem
5-16, 5-17
1-3
apc
5-48
5-11
ss7route
5-17
5-47
siprttrnkgrp
5-15
5-28
5-47
sippath
5-15
5-28
siplnk
5-16
4-4
5-11
iplnk
5-17
lnkset
5-8
lnksetprop
2-6
5-27
5-17
5-27
ipfaspath
5-16
network indicator
3-12
3-12
3-2
5-9
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
IN-3
Index
IP route
OPC
2-2
4-10
A-8
4-10
provisioning components
association
prov-rtrv
path
4-5
prov-sta
4-3
4-5, 4-11
EISUP
2-5
prov-stp
MGCP
2-5
prov-sync
3-87
point code
destination
format
2-2
Q
Q.931 protocol path
5-17
2-2
remote switch
2-14
route
2-2
storage
signaling
5-8
SS7
2-14
point codes
routing
2-5
2-5
5-28
5-3
converting
5-6
International
National
5-6
5-6
provisioning
profile
2-5
5-7
originating
STP
4-4, 4-10
5-7
Japanese
SS7
2-10
S
session commands
5-6
4-3
signaling link
adding a C7 IP link
5-13
Properties
A-99
adding a card
properties
4-15
changing
4-18
property types
protocols
4-18
3-28
protocol variants
4-31
5-14
components to add
5-12
4-5
siplnk
prov-cpy
4-3
sippath
prov-dply
prov-ed
prov-exp
4-5, 4-17
4-4
4-5
3-27
5-47
5-47, 5-50
siprttrnkgrp
SP
5-12
5-14
prov-add
prov-dlt
5-12
5-48
2-2
span
4-5, 4-6
E1
2-7
provisioning
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
IN-4
OL-1110-23
Index
T1
span ID
SS7
components to add
2-6
trunk ID
2-6
2-6, 2-7
trunk route
3-11
SS7PATH
3-27
SS7 route
5-10
adding
trunks
5-26
3-97
3-97
3-31
5-11
5-27
5-27
components to add
5-17, 5-26
configuring routes
5-28
5-8
5-2
5-8
U
unknown MGC
5-10
5-3
V
5-9, 5-10
3-1
5-11
2-6, 5-9
3-27
SS7 subsystem
Step 4
3-5
5-8
3-2
3-162
2-2
2-7
T
TDM interface
TDM link
5-14
5-14
Time Out 02
time slots
2-62
2-7
tips
before provisioning
TO-02 timer
trnkgrp
3-1
2-62
5-47
trnkgrpprop
true OPC
5-48
2-15
trunk group
3-97
3-99
trunk groups
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
IN-5
Index
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
IN-6
OL-1110-23