Cisco PGW 2200

Cisco PGW 2200 Softswitch Release 9
Provisioning Guide (through Release 9.7)

February 25, 2010
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
Text Part Number: OL-1110-23
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
About this Preface
xvii
Document Objective
Audience
xvii
xvii
Document Organization
xviii
Document Conventions
xix
Syntax Conventions
xix
Documentation Roadmap and Documentation Suite xxi

Documentation Roadmap xxi
Hardware Documentation xxii
Software Installation and Configuration Documentation
Gateway Documentation xxii
Terminology xxii
Obtaining Documentation and Submitting a Service Request
Summary History of Document Changes
CHAPTER
Provisioning Overview
Before You Begin
1-1
1-1
Cisco PGW 2200 Softswitch Provisioning
xxiii
xxiii
Cisco PGW 2200 Softswitch Provisioning Overview
CHAPTER
xxii
1-2
1-2
Cisco PGW 2200 Softswitch Provisioning Rules
1-3
Cisco PGW 2200 Softswitch Provisioning Tools
1-3
Planning for Provisioning 2-1

Prerequisite Provisioning Information 2-1
Collecting External Device Addresses 2-2
Collecting SS7 Point Code Data 2-2
Collecting External Node Information 2-2
Collecting Media Gateway Controller Interface Card Data
Collecting SS7 Signaling Service Data 2-3
Collecting MGW Signaling Service Data 2-3
Collecting Linkset Data 2-3
Collecting Cisco ITP-L Data 2-4
2-2
OL-1110-23
iii
Contents
Collecting Sessionset Data 2-4

Collecting C7 IP Link Data 2-4
Collecting IP Link Data 2-5
Collecting SS7 Route Data 2-5
Collecting SS7 Subsystem Data 2-6
Collecting Trunk Data (Nailed) 2-6
Collecting Trunk Data (Switched) 2-7
Collecting QSIG/Q.931 Over BRI Backhaul Path Data 2-7
Collecting Backhaul TCP Link Data 2-8
Collecting IP Route Data 2-8
Collecting IP FAS Path Data 2-8
Collecting DPNSS Path Data 2-9
Collecting M3UA Key Data 2-9
Collecting M3UA Route Data 2-9
Collecting D-Channel Data 2-10
Collecting SCTP Association Data 2-10
Collecting SS7 Signaling Gateway Process Data 2-11
Collecting SS7 Signaling Service Data 2-11
Collecting SUA Key Data 2-11
Collecting SUA Route Data 2-12
Collecting SIP Path Data 2-12
Planning SS7 Signaling Routes 2-12
Planning Point Codes (SS7 Network Addresses) 2-13
Planning Linksets 2-15
Planning Linkset Properties 2-16
Planning SS7 Subsystems 2-20
Planning SS7 Routes 2-21
Planning the SS7 Signaling Service 2-22
Changing SS7 Signaling Service Properties 2-23
Planning SS7 Signaling Links 2-28
Planning Network Cards for Cisco ITP-L Communications 2-29
Planning Ethernet Interfaces for Cisco ITP-L Communications 2-30
Planning TDM Interfaces for Cisco ITP-L Communications 2-31
Planning A-Links Through Cisco ITP-Ls 2-32
Planning F-Links through Cisco ITP-Ls 2-33
Planning F-Links to Signaling Points 2-34
Planning PRI Backhaul Links 2-34
Planning Media Gateway Control Links 2-34
Planning Media Gateway External Nodes
2-34
iv
OL-1110-23
Contents
Planning for the Media Gateway Signaling Service 2-38

Planning Network Cards for Media Gateway Communications 2-40
Planning Ethernet Interfaces for Media Gateway Communications 2-40
Planning IP Links 2-41
Planning Backhaul TCP Link 2-43
Planning QSIG/Q.931 Over BRI Backhaul Signaling Service 2-44
Planning Session Sets 2-45
Planning for D-Channels 2-47
Planning for NOA Line Translation 2-48
Provisioning Bearer Capability 2-49
Provisioning Trunk Groups and Trunks 2-50
Provisioning Trunk Groups and Trunks Using MML Commands 2-50
Provisioning Trunk Groups and Trunks Using an Imported File 2-50
Provisioning a Nailed Configuration 2-51
Adding Nailed Trunks 2-51
Configuring Profiles 2-52
Attaching a Trunk Group Profile to a Trunk Group
Configuring Signaling Service Profiles 2-55
Configuring ATM Profiles 2-55
AtmConnectionType 2-55
GWDefaultATMProfile 2-57
Creating the Trunk Group 2-58
Populating a Trunk Group File 2-58
Populating a Trunk File 2-86
2-52
Route Analysis 2-87

Creating a Routing Trunk Group 2-87
Provisioning a Routing Trunk Group Using MML Commands
Associating a Route with a Trunk Group 2-89
Weighted Trunk Group 2-89
Creating a Route List 2-90
An MML Example for Creating a Routing File 2-91
Planning for Session Initiation Protocol Provisioning
CHAPTER
2-91
Provisioning with the Cisco Voice Services Provisioning Tool

Installing Cisco VSPT
Provisioning Cisco ITP-L
2-87
3-1
3-1
3-2
Manual Provisioning with Cisco VSPT
3-2
Configuring the MGC 3-2

Adding a Cisco PGW 2200 Softswitch Host
3-3
OL-1110-23
Contents
Configuring Signaling Services 3-7

Adding Point Codes 3-8
Adding Origination Point Codes 3-8
Adding Adjacent Point Codes 3-10
Adding Destination Point Codes 3-11
Adding Routing Keys 3-13
Adding M3UA Routing Keys 3-13
Adding SUA Routing Keys 3-14
Adding Location Labels 3-16
Adding Linksets 3-17
Adding and Changing Linkset Properties 3-19
Adding SS7 Subsystems 3-20
Adding SS7 Subsystems (Mating APCs) 3-21
Adding SS7 Subsystems (AIN Services) 3-22
Adding ISUP Timer Profiles 3-23
Adding an Inservice Subsystem 3-24
Configuring SS7 Paths 3-27
Adding and Changing SS7 Properties 3-29
Configuring SS7 Routes 3-30
Configuring IPRoutes 3-32
Configuring M3UA Routes 3-33
Configuring SUA Routes 3-34
Adding and Changing SS7 Signaling Properties 3-35
Adding a Line Number Translation 3-36
Adding Session Initiation Protocols 3-38
Configuring a DNS Parameter 3-38
Adding a SIP Signaling Path 3-39
Adding and Changing SIP Signaling Properties 3-40
Adding a SIP IP Link 3-41
Configuring Automatic Congestion Control 3-43
Configuring Advice of Charge 3-45
Configuring a Holiday 3-45
Configuring a Charge 3-46
Configuring a Tariff 3-47
Configuring a Meter Tariff 3-48
Configuring a Pritariff 3-49
Configuring a Pricharge 3-51
Adding GTD Parameters 3-52
Configuring TOS 3-53
Configuring Cisco MGW Control Links
3-53
vi
OL-1110-23
Contents
Adding External Nodes 3-54

Configuring Cisco MGWs 3-55
Adding a Session Set 3-57
Adding and Changing Session Set Properties 3-58
Adding an IPFAS Signaling Service 3-59
Changing IPFAS Signaling Service Properties 3-63
Adding an MGCP Signaling Service 3-64
Adding and Changing MGCP Signaling Service Properties 3-65
Adding a DPNSS Path 3-67
Adding and Changing DPNSS Path Signaling Properties 3-68
Adding an H.248 Signaling Service 3-69
Adding and Changing H248 Signaling Properties 3-69
Adding an EISUP Signaling Service 3-70
Adding or Changing EISUP Signaling Properties 3-71
Adding an LIpath Signaling Service 3-72
Adding or Changing LI Signaling Properties 3-73
Adding a NAS Signaling Service 3-74
Adding and Changing NAS Signaling Properties 3-75
Adding a CTI Signaling Service 3-76
Adding and Changing CTI Signaling Properties 3-77
Adding an SS7 SGP 3-78
Adding a TCPLNK 3-79
Adding and Changing Tcplnk Properties 3-80
Adding a BRI Signaling Service 3-81
Adding a RAPATH 3-84
Adding a RASERVER for RAPATH 3-84
Configuring IP Links 3-86
Adding IP Links for MGCP 3-86
Adding IP Links for H248 3-87
Adding IP Links for EISUP 3-89
Adding IP Links for LI 3-90
Adding IP Links for NAS 3-91
Adding C7 IP Links 3-93
Adding an ASSOCIATION 3-94
Adding a CTI Manager 3-95
Adding an AXL Server 3-96
Configuring Bearer Traffic 3-97
Importing Trunk Groups and Trunks 3-99
Adding a Trunk Group Profile 3-101
Adding Trunk Groups 3-102
OL-1110-23
vii
Contents
Trunk Group Properties 3-104

Adding Trunks 3-139
Deleting Trunks from a Trunk Group 3-142
Adding a CodecString 3-143
Adding a BearerCap 3-145
Adding an ATMProfile 3-146
Adding Routes 3-147
Adding Route Lists 3-148
Hierarchical View of Provisioned Components 3-149
Performing an Integrity Check 3-150
Checking Integrity for an MGC Signaling Configuration 3-150
Checking Traffic Against an MGC Configuration 3-151
Viewing Generated MML Commands
Deploying a New Configuration
3-153
3-153
Backup and Restore 3-155

Schedule a Backup or Restore 3-156
Check Status of Backup or Restore
3-159
Provisioning the Cisco Billing and Measurements Server

Starting a Cisco BAMS Provisioning Session
3-160
3-162
Cisco BAMS Server Configuration 3-164

Provisioning General BAMS Information 3-165
Provisioning Zones 3-169
Provisioning Trunk Group Information 3-175
Provisioning Measurements 3-178
Provisioning Other 3-180
Provisioning ALM-PARMS 3-180
Provisioning NODE-PARMS 3-181
Provisioning POLL 3-182
Provisioning SKIPCDB 3-183
Provisioning SKIPCDE 3-184
Provisioning P01FILTER 3-186
Provisioning SWITCHINFO 3-186
Provisioning BIN1110 3-187
Provisioning System 3-188
Provisioning MSC-PARMS 3-189
Provisioning MSC-THRES 3-190
Provisioning SYS-ALM-PARMS 3-191
viii
OL-1110-23
Contents
CHAPTER
MML Basics
4-1
Working with MML
4-1
MML Configuration Commands
4-3
Working with MML Session Commands 4-6

Starting a Provisioning Session 4-6
Creating a New Provisioning Configuration 4-7
Overwriting an Existing Inactive Configuration 4-8
Modifying and Activating a Configuration 4-8
Modifying an Existing Configuration and Saving It as Another Version 4-9
Committing a Provisioning Session to a Single Cisco PGW 2200 Softswitch 4-9
Deploying a Provisioning Session to Dual MGCs 4-10
Synchronizing Configuration Data 4-10
Stopping a Configuration Session 4-11
Performing a Manual Switchover 4-12
Exporting Configuration Data 4-12
Importing Saved MML Configuration Data 4-13
Working with Provisioning Commands 4-15
Adding a Component 4-15
Modifying a Component 4-16
Deleting a Component 4-17
Overriding Component Properties 4-17
Changing Overridden Properties 4-18
Retrieving All Components 4-29
Retrieving All Components of a Specific Type 4-30
Retrieving an Individual Component 4-30
Retrieving a Component Based on Signaling Service
Retrieving Protocol Variants 4-31
Retrieving Provisioning Session Information 4-33
Creating a Batch File 4-33
Executing a Batch File 4-34
CHAPTER
Adding Components with MML
4-30
5-1
Adding SS7 Signaling Route Components 5-2

Adding a Destination Point Code 5-3
Adding Multiple OPCs 5-4
Understanding Point Code Addressing 5-5
14-Bit Address (ITU) 5-6
16-Bit Address (Japan) 5-7
24-Bit Address (ANSI and China) 5-7
OL-1110-23
ix
Contents
Cisco PGW 2200 Softswitch Point Code Storage

Adding an Adjacent Point Code 5-8
Adding a Linkset 5-8
Adding a Linkset Property 5-9
Adding an SS7 Subsystem 5-9
Adding Subsystem Numbers 5-10
Adding an SS7 Route 5-10
Adding an SS7 Signaling Service 5-11
Adding a FAS Signaling Service 5-11
5-8
Adding Signaling Link Components 5-12

Adding an Interface Card 5-12
Adding an Ethernet Interface 5-12
Adding a C7 IP Link 5-13
Adding a TDM Interface 5-14
Adding a TDM Link 5-14
Adding Media Gateway Control Links 5-14
Adding an External Node 5-15
Adding a Card 5-15
Adding an Ethernet Interface 5-15
Adding an E-ISUP Signaling Service 5-16
Adding an IPFAS Transport Service 5-16
Adding an MGCP Signaling Service 5-16
Modifying an MGCP Signaling Service Property 5-17
Adding a NAS Signaling Service 5-17
Adding an IP Link 5-17
Adding a Session Set 5-18
Adding D-channels 5-19
Adding ISDN BRI Backhaul Connections 5-19
Adding IUA Connections 5-21
Verifying Next Hop Parameter Configuration 5-21
Adding Cisco Access Server External Nodes 5-22
Adding NAS Signaling Services 5-22
Adding IP Routes (Optional) 5-22
Adding SCTP Associations 5-23
Adding DPNSS Connections 5-23
Verifying Next Hop Parameter Configuration 5-24
Adding Cisco Access Server External Nodes 5-24
Adding IP Routes (Optional) 5-25
Adding DPNSS Signaling Services 5-26
OL-1110-23
Contents
Adding DPNSS Supplementary Services
5-26
Adding Trunks, Trunk Groups, and Routing 5-26

Adding Files 5-27
Adding a Nailed Trunk (Bearer Channel) 5-27
Adding a Trunk Group 5-27
Adding Mapping to Multiple Trunk Groups 5-28
Routing 5-28
Provisioning Reserving Incoming Bandwidth 5-28
Provisioning Bearer Capability 5-29
Provisioning Least Cost Routing 5-30
Overriding the Trunk Group Property 5-32
Enabling Overdecadic 32 Digit Operation 5-32
Provisioning the Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14
Mapping Feature 5-35
Verifying the Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14
Mapping Feature 5-36
Provisioning SUBSCRIBE/NOTIFY Methods 5-36
Enabling SUBSCRIBE/NOTIFY Methods 5-36
Disabling SUBSCRIBE/NOTIFY Methods 5-37
Provisioning Unsolicited Notifications 5-37
Enabling Unsolicited Notifications 5-37
Disabling Unsolicited Notifications 5-38
Provisioning Subscription Duration 5-38
Provisioning Minimum Subscription Duration for Telephony Event 5-38
Provisioning Maximum Duration for SUBSCRIBE 5-39
Enabling/Disabling Information Extraction from SDP 5-39
Enabling Support of Information Extraction from Sockets Direct Protocol (SDP) 5-39
Disabling Support of Information Extraction from SDP 5-39
Adding a Switched Trunk (Multiple Switched Trunks) 5-40
Retrieving Multiple Switched Trunks 5-40
Adding Multiple Nailed Trunks 5-41
Retrieving Multiple Nailed Trunks 5-41
Adding Multiple Trunk Groups and Bearer Channels 5-41
Removing Multiple Trunk Groups and Bearer Channels 5-42
Creating a Profile 5-42
Adding a Trunk Group Profile 5-42
Deleting a Trunk Group Profile 5-42
Adding an ISUP Timer Profile 5-43
Suppressing Caller ID in a SIP Environment 5-43
Adding an ATM Profile 5-45
OL-1110-23
xi
Contents
Provisioning ATM Profiles 5-46

Provisioning ATM Profiles Result Types 5-46
Provisioning Trunk Group Properties 5-46
Provisioning SigPath Properties 5-46
Adding SIP Components 5-46
Adding a SIP Signaling Service 5-47
Adding a SIP Signaling Link 5-47
Adding a SIP Trunk Group 5-47
Adding SIP Trunk Group Properties 5-47
Adding Mapping to Multiple IP Trunks 5-48
Adding SIP Routing Trunk Group Properties 5-48
Adding SIP Domain Name System Properties 5-48
Modifying a SIP Signaling Service 5-49
Modifying Session Timers 5-50
Modifying Session Timer for Incoming SIP Trunk Groups 5-50
Modifying Session Timer for Outgoing SIP Trunk Groups 5-50
Adding Dual Presentation CLI 5-50
Adding Automatic Switchover Using Dual-VLAN 5-50
Verifying Parameter Settings and Re-configuring Cisco PGW 2200 Softswitch Software
Enabling SIP Automatic Switchover Using Dual-VLAN 5-52
Disabling SIP Automatic Switchover Using Dual-VLAN 5-53
Adding SIP-T and SIP-GTD Support 5-55
Adding SIP-T and SIP-GTD Support 5-55
Enabling the Early Backward ISUP Message
GTD NOA Override 5-56
GTD Provisioning Examples
5-51
5-56
5-59
NOA Configurable Mapping 5-59

Provisioning the NOA Configurable Mapping Feature 5-60
Adding an NOA Value to the LineXlate File for Inbound Calls 5-61
Deleting an NOA Value from the LineXlate File 5-61
Adding an NOA Value to the LineXlate File for Outbound Calls 5-61
Deleting an NOA Value from the LineXlate File 5-62
Validation Rules 5-62
Adding M3UA and SUA Connections 5-62
Adding a Cisco ITP External Node 5-63
Adding Point Codes (OPC, DPC, and APC) 5-63
Adding M3UA and SUA Routing Keys 5-63
Adding SS7 Signaling Services 5-63
Adding M3UA and SUA Routes 5-64
xii
OL-1110-23
Contents
Adding SS7 Subsystems 5-64

Adding M3UA and SUA Signaling Gateway Processes
Adding IP Routes (optional) 5-64
5-64
Adding Location Labels 5-64

Adding Location Labels to Trunk Groups and Sigpaths 5-65
Applying Call Limiting Over DPNSS 5-67
Applying Call Limiting to Incoming and Outgoing Trunk Groups 5-68
B-number Based Call Limiting Scenario 5-69
Applying Call Limiting to a SIP Trunk Group 5-70
Applying Call Limiting to an H.323 Trunk Group 5-70
Applying Call Limiting to the DPNSS Trunk Groups 5-71
Applying Call Limiting to an SS7 ISUP Trunk Group 5-71
Applying Call Limiting to Digit Strings in a Dial Plan 5-72
Applying Call Limiting to Multiple Trunk Groups 5-72
Applying Call Limiting to IP Addresses 5-72
Applying Call Limiting to an MGCP Gateway 5-73
Playing an Announcement when the Call Limiting Threshold is Exceeded
Scaling System Components 5-74
Dynamically Configuring the Input/Output Channel Controller
5-74
Provisioning Examples 5-77

Configuring Two IP Addresses on the MGW to One IP Address on a NAS
A-number Country Code Digit Removal
Call Reporting
5-73
5-77
5-82
5-82
CODEC Capabilities and DTMF Preferential Routing

Digit Buffering for International Gateways
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
OL-1110-23
xiii
Contents
Full Number Translations

Global Titles
5-96
5-96
Provisioning H.248 Protocol
5-96
Lawful Intercept 5-99

Provisioning LI for the Service Provider 5-100
Provisioning a Wiretap Entry for the Medication Device
5-101
Location Mapping 5-101

Provisioning Location Values 5-102
Provisioning Internal Cause Value Mapping 5-103
Provisioning Cause Value Mapping 5-103
Cause Value Mapping Based on Received Cause and Location Values 5-103
Cause and Location Value Mapping to Different Values 5-104
Cause Value Mapping to Different Cause and Location Values 5-104
Multiple Inbound IP Trunks 5-105
Creating a New Inbound SIP Trunk 5-105
Creating a New Inbound ISUP Trunk 5-107
Support of HSI Non-RAS Mode 5-107
Provisioning Cisco PGW 2200 Softswitch
Provisioning Cisco HSI 5-108
5-108
Presentation Number Modification 5-109

Provisioning PN Modification for PSTN to SIP Calls
RADIUS Enhancement for Accounting
5-109
5-110
5-111
SIP and ISUP Interworking for Call Hold and Terminal Portability
SIP Overlap Signaling
5-112
SIP Remote Party ID and P-Asserted Support
5-113
SIP Service Handling and Feature Interworking Enhancement

Take Back and Transfer
QoS for Signaling Traffic
APPENDIX
5-112
Components and Properties
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
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
OL-1110-23
xv
Contents
SS7 Signaling Service (sigpath) A-76

SS7 Subsystem A-76
SUA Key A-78
SS7 Signaling Gateway Process A-80
Switched Trunk Provisioning A-80
TARIFF A-81
Backhaul TCP Link A-81
TDM Interface A-82
TDM Link A-83
Trunk Group Provisioning A-84
Trunk Group Profile MML Provisioning A-85
GTD Parameter Provisioning A-86
Dial Plan Provisioning Components A-94
Processes
A-98
Properties
A-99
Protocol Variants A-100

Software Release 9.3(2) Protocol Variants
APPENDIX
Planning Worksheets
A-100
A-103
A-106
A-109
B-1
INDEX
xvi
OL-1110-23
Preface
Revised: February 25, 2010, OL-1110-23
About this Preface

This preface describes the objectives, audience, organization, and conventions of this document, and
explains how to find additional information on related products and services. It contains the following
sections:
Document Objective, page xvii
Audience, page xvii
Document Organization, page xviii
Document Conventions, page xix
Syntax Conventions, page xix
Documentation Roadmap and Documentation Suite, page xxi
Obtaining Documentation and Submitting a Service Request, page xxiii
Summary History of Document Changes, page xxiii
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:
Telecommunications network operations
Data network operations
SS7 protocols, switching, and routing
OL-1110-23
xvii
Preface
Telecommunications hardware
Data network hardware
In addition, the following audiences may find this document useful:
Software and hardware installers
Network designers
This document contains the chapters listed in Table 1.
Table 1
Chapter
Title
Description
Chapter 1
This chapter includes a checklist of tasks to perform

before you use this guide to provision your system, and
information to gather before beginning. It also
includes the following information:
Chapter 2
Planning for Provisioning
Before You Begin

Overview
This chapter provides a general overview of planning

for provisioning, including:
Planning signaling routes to other switches
Planning signaling links to Signaling Points (SPs)
Planning media gateway control links
Planning trunks, trunk groups, and routes
Chapter 3
Provisioning with the Cisco

Voice Services Provisioning
Tool
This chapter describes the graphical user interface

provisioning procedures.
Chapter 4
MML Basics
This chapter describes how to use MML commands.
Chapter 5
Adding Components with

MML
This chapter describes how to use MML commands to

add system components.
Appendix A
This appendix lists the component names and

properties.
Appendix B
Planning Worksheets
This appendix contains worksheets to use for

provisioning.
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
Means the following information might help you solve a problem.
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
Commands and keywords

you enter as shown.
offset-list
Italics
Variables for which you

supply values.
command type interface

You replace the variable with the type
of interface.
In contexts that do not allow italics,
such as online help, arguments are
enclosed in angle brackets (< >).
Square brackets ([ ])
Optional elements.
command [abc]
abc is optional (not required), but you
can choose it.
Vertical bars ( | )
Separated alternative
elements.
command [ abc | def ]

You can choose either abc or def, or
neither, but not both.
OL-1110-23
xix
Preface
Table 2
Conventions (continued)
Convention
Meaning
Description / Comments
Braces ({ })
Required choices.
command { abc | def }

You must choose either abc or def, but
not both.
Braces and vertical bars

within square brackets
([ { | } ])
A required choice within an command [ abc { def | ghi } ]

optional element.
You have three options:
nothing
abc def
abc ghi
Caret character (^)
Control key.
The key combinations ^D and Ctrl-D

are equivalent: Both mean hold down
the Control key while you press the D
key. Keys are indicated in capital
letters, but are not case sensitive.
A nonquoted set of
characters
A string.
For example, when setting an SNMP

community string to public, do not use
quotation marks around the string;
otherwise, the string will include the
quotation marks.
System prompts
Denotes interactive
sessions, indicates that the
user enters commands at the
prompt.
The system prompt indicates the

current command mode. For example,
the prompt Router (config) #
indicates global configuration mode.
Screen
font
Terminal sessions and

information the system
displays.
Angle brackets (< >)
Nonprinting characters such

as passwords.
Exclamation point (!) at the

beginning of a line
A comment line.
Comments are sometimes displayed by

the Cisco IOS software.
Conventions used in the Cisco PGW 2200 Softswitch system (such as in MML commands) are shown in
Table 3.
xx
OL-1110-23
Preface
Table 3
Data Types
Data Type
Definition
Example
Integer
A series of decimal digits from the set of 0 through 9 that 123

represents a positive integer. An integer may have one or
000123
more leading zero digits (0) added to the left side to align
the columns. Leading zeros are always valid as long as 4200000000
the number of digits is less than or equal to ten digits.
Values of this type have a range of zero through
4294967295.
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.
Hexadecimal A series of 16-based digits from the set of 0 through 9, a 1f3

through f, or A through F. The hexadecimal number may 01f3000
have one or more leading zeros (0) added to the left side.
For all hexadecimal values, the maximum size is
0xffffffff (eight hexadecimal digits).
Text
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 and Documentation Suite

Consult the following related documentation for information about the Cisco PGW 2200 Softswitch
software and the solutions it supports, including the Cisco SS7 Interconnect for Access Servers Solution
and the Cisco SS7 Interconnect for Voice Gateways Solution and the Cisco Packet Tandem Solution.
Documentation Roadmap
You can find the Cisco PGW 2200 Softswitch Documentation Map at the following URL:
OL-1110-23
xxi
Preface
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/products_documentation_roadmaps_list.ht
ml
Hardware Documentation
Cisco PGW 2200 Softswitch Hardware Installation Guide - Releases 7 & 9
Regulatory Compliance and Safety Information for Cisco Media Gateway Controller Hardware
Software Installation and Configuration Documentation
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 Media Gateway Controller Software Release 9 Billing Interface Guide
Cisco PGW 2200 Softswitch Release 9 MML Command Reference
Cisco PGW 2200 Softswitch Release 9 Messages Reference
Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide
Release Notes for Cisco PGW 2200 Softswitch Release 9.7(3)
Cisco Media Gateway Controller Online Documentation Notice
Cisco Media Gateway Controller SLT Documentation Notice
Billing and Measurements Server Users 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.
xxii
OL-1110-23
Preface
Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly Whats New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation at
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the Whats New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free
service and Cisco currently supports RSS version 2.0.

Table 4 describes the document changes made after the initial release of the Cisco PGW 2200 Softswitch
Release 9 Provisioning Guide (through Release 9.7).
Table 4
Subject
Provisioning
procedures for
PGW-to-ITP routing
with MAP query
Document Number and Change

Date
OL-1110-23, February 25, 2010
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
Added provisioning procedures for features in Release 9.7(3)

in Chapter 5, Adding Components with MML.
Replaced property
OL-1110-21, December 17, 2009
tables with a reference
to another book
Replaced property tables with a reference to

Cisco PGW 2200 Softswitch Release 9 MML Command
Reference in Appendix A Components and Properties.
Removed references to TALI, SGNODE, SGPAIR,
SS7SGIPLNK, SS7SGPATH, SS7SGSUBSYS, and
SS7SGLNK in Chapter 2, Planning for Provisioning, and
Chapter 5, Adding Components with MML.
Added new properties

and values
OL-1110-20, December 1, 2009
Updated the DCHAN parameter SUBUNIT with new values

(modified Table 2-22).
Added the trunk group properties UseGtdCalledPartyNumber
and InhibitPasson. (Modified Table 2-30, Table A-68, and
Table A-69).
Added the property CallHoldInterworkingEnabled (Modified
Table A-68 and Table A-69).
Modified the description of the property
H248GatewayReserveValue in Table A-68 and Table A-69.
Added a note to indicate that this property is deleted in Release
9.7S23P23 and later.
Added an new value to OL-1110-19, October 2, 2009

a property
Inserted an additional acceptable value (2) for the

UnsolicitedNotifyMethod property. (Modified Table 2-30,
Table 3-16, Table A-68, Table A-69).
OL-1110-23
xxiii
Preface
Table 4
Summary History of Document Changes (continued)
Subject

Date
Added clarifications
OL-1110-18, August 25, 2009
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 trunk group

properties and
descriptions
OL-1110-17, July 30, 2009
Updated Table 3-16 to include all the properties applicable to

the trunk group in the Trunk Group Properties section on
page 3-104.
Added feature
information and
updated product name
OL-1110-16, July 23, 2009
Updated product name to Cisco PGW 2200 Softswitch

throughout the document.
Corrected the description of the EchoCanRequired property in
the Properties section on page A-99.
Added the properties NetSuspendResumeMap2Invite and
RejectOfferForResourcePending to the Trunk Group
Properties section on page 3-104 and the Properties section
on page A-99.
Corrected the spelling of the property
SuppressCHGNtoCGPNMapping in the Properties section
on page A-99.
Increased the range of the property RedirNumForAnalysis in
the Properties section on page A-99.
Throughout the document, for the command
prov-add:DPNSSPATH, deleted MDO=xxxxx. It is not part of
this command.
Updated the list of external nodes in the Planning Media
Gateway External Nodes section on page 2-34.
Added feature
information
OL-1110-15, June 15, 2009
Made additional corrections in the Importing Saved MML

Configuration Data section on page 4-13.
Added the trunk group property MidCallCodecSelect in
Appendix A Components and Properties.
Added feature
information
OL-1110-15, June 10, 2009
Removed the obsolete note in the Trunk Group Properties

section on page 3-104, Although the property order in the
Cisco VSPT Trunk Group Data and Property window is
somewhat different from that required in the MML file, the
output file that Cisco VSPT generates uses the correct
sequence. For a list of properties in that sequence, see
Table 2-30 on page 2-61.
Updated the procedure in the Importing Saved MML
Configuration Data section on page 4-13.
Removed the invalid property, if="enet-if" in the
prov-add:siplnk command in Adding a SIP Signaling Link
section on page 5-47.
xxiv
OL-1110-23
Preface
Table 4
Subject
Added feature
information

Date
OL-1110-14, February, 2009
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
OL-1110-13, March, 2008
Added information for the Multiple Incoming IP Trunks

featurette.
Updated for VSPT

Release 2.7(3)
OL-1110-13, December, 2007
Updated Chapter 3, Provisioning with the Cisco Voice

Services Provisioning Tool for VSPT release 2.7(3).
Added Cisco IP Transfer Point - LinkExtender (ITP-L) as

the new name for Cisco Signaling Link Terminal (SLT).
Over time, Cisco ITP-L will replace Cisco SLT in
publications and the product.
Added new information for Release 9.7 features.
Updated for Release

9.7
OL-1110-13, November, 2007
OL-1110-23
xxv
Preface
Table 4

Date
Subject
Change Summary
Added feature
information
OL-1110-12, October, 2007
Modified CDR 4239, added CDR 4065 for Redirect Server

feature.
Added feature
information
OL-1110-12, October, 2007
Added the following properties for the SIP Loose Routing

feature:
*.sipEgressRoutingControl
*.sipIngressRoutingControl
Added feature
information
OL-1110-12 June 27, 2007
Added the *.ItpActionRequest property for the Optimize

Routing with MAP Query feature.
Added feature
information
OL-1110-11 August 12, 2005
Added the *.SendDtmfBeforeConnect property.
Added ATP.dat as a GTD override_string parameter.
Added values 3 and 4 to *.GatewayRBToneSupport.
Added the *.NFASImplicitInterfaceId property.
Added a value of 2 to the CLIPEss parameter range.
Added a note for *.GatewayRBToneSupport.
Deleted the DetectFaxModemTone information.
Changed *.CustomerVPNOffNetTblNum and

*.CustomerVPNOnNetTblNum range from 0-8 to 1-8.
Added VXSM to the selection for *.MGCPBehavior.
Added software Release 9.6(1) information.
Changed the name parameter range to 1 through 9999 for

RTTRNKGRP, SIPRTTRNKGRP, and TRNKGRP.
Added the *.SuppressCHGNtoCGPNMapping property.
Added the M3UA scaling limits to Table 5-11 in

Chapter 5, Adding Components with MML.
Changed the *.MaxForwards default value from 10 to 70.
Removed SIPPROFILE references from Chapter 5.
Added the *.LocalAnnBehavior property.
Corrected the mgcpRetxTimer default value in Appendix

A.
Added CAI.loc to the list of GTD parameter names that

can be entered in the override_string.
Changed the valid values for *.Support183 to 0, 3, or 4.
Added feature
information
OL-1110-10 June 28, 2004
xxvi
OL-1110-23
Preface
Table 4
Subject
Added feature
information
Added feature
information

Date
OL-1110-10 June 28, 2004
OL-1110-09 October 30, 2003
Change Summary
Changed the listed RedirMax property default value to 5.
Added TCPLINK and BRIPATH components in support of

the QSIG over BRI and Q.931 backhaul feature.
Added Table 5-6 and Table 5-7 to Chapter 5, Adding

Components with MML.
Added the validation parameter for the ISUP timer profile

in Adding Components with MML.
Corrected the DetectFaxModemTone default value in

Appendix A.
Added Understanding Point Code Addressing, page 5

information in Chapter 5, Adding Components with
MML.
Changed the maximum value of CUMSACKTO to 500.
Added the following new properties for software Release

9.5(2): MwiStringON, MwiStringOFF,
TransferAwaitConnect, MWIInvokeTimerT1,
SSCTInvokeTimerT1, SipReferForSimpleStepXfer,
GWDefaultATMProfile, PlayAnnouncement,
AtmConnectionType, BTechPrefix,
LoopAvoidanceSupport, LoopAvoidanceCounter, and
CliCodeOfPractice3
Added DPNSS as a protocol family supported by

SuppressCLIDigits. in Table A-68.
Added a reference to Appendix A, Protocol Variants to

the ISUPTMRPROFILE descriptions in Chapter 2 and
Chapter 5.
Revised the SIPRTTRNKGRP URL parameter description

in Table A-40 on page 61.
Incorporated changes for software Release 9.4(1)

including: the following new components:
ASSOCIATION, IPLNK, IPROUTE, LINEXLATE,
M3UAKEY, M3UAROUTE, SGP, SIPLNK,
SS7SGIPLNK, SS7PATH, SUAKEY, and SUAROUTE;
and the following new properties: Anumnormalise,
Bnumnormalise, CallForwardRerouteDisabled,
CustomerVPNid, CustomerVPNOffNetTblNum,
CustomerVPNOnNetTblNum,
FeatureTransparencyDisabled, sipMimeBodySupport,
DefaultPN, DefaulPNNOA, DefaulPNNPI, DefaulPNPres,
EnableIPScreening, SipIPSource,
populateSDPInfoInCDR, MaxSubscribeDuration,
MinEventSubscribeDuration, SubscribeNotifySupport,
UnsolicitedNotifyMethod, OD32DigitSupport, and
SdpXmitToH323Trigger
OL-1110-23
xxvii
Preface
Table 4

Date
Subject
Added text for property OL-1110-08 March 30, 2003

changes
Added feature
information
Added feature
information
Provisioning changes
OL-1110-07 December 9, 2002
OL-1110-06 September 19, 2002
OL-1110-05 March 22, 2002
Change Summary
Revised the NEXTHOP note on page 42.
Added TO-02 timer information for the RingNoAnswer

trunk group property in Table 2-30 on page 61.
Added the value of 0 to disable mtp3MtpRstrtT20 and

mtp3ApcMtpRstrtT21 for all SS7 protocol variants.
Added a note explaining new source version Note in

MML Basics.
Revised text for the PROV-EXPExport Configuration

Data description.
Revised the MML example under Adding SIP Domain

Name System Properties.
Added information regarding the GWDefaultCodecString

property description.
Software Release 9.2(2) patch CSCOnn033 added the

IsupTransEarlyACMEnabled property.
Changed the SS7-ANSI.mtp3TfrUsed default value to

true.
Changed the IsupTransEarlyBackwardDisabled and

IsupTransparencyDisabled default values to 1.
Added variable ISUP timers.
Revised property information.
Added dual MGCP IP link note.
Modified the CGBA2 and default BC descriptions.
Updated trunk group property list.
Added internal cause code values.
Added new properties and property parent object.
Removed obsoleted MML commands (SGCPPATH,

CASPATH, and TCAPIPPATH).
Added information regarding profiles, GTD NOA, and

time conditional routing.
Changed the value of DPCs per MGC to 600.
Changed the value of routes per MGC to 1200.
VSPT changes
OL-1110-04, January 28, 2002
Modified Chapter 3, Provisioning with the Cisco Voice

Services Provisioning Tool.
Added properties
OL-1110-03, January 8, 2002
In Appendix A, Components and Properties, added

SS7-ANSI.congProc and SS7-ANSI.unavailProc property
definitions.
xxviii
OL-1110-23
Preface
Table 4
Subject

Date
Provisioning rules
OL-1089-02, December 3, 2001
MML names
re-ordered for routing
Change Summary
In Chapter 1, Provisioning Overview, added

Cisco PGW 2200 Softswitch Provisioning Rules, page 3.
In Chapter 5, Adding Components with MML,

re-ordered MML names and steps under Routing, page 28.
Added parameter value details in Table A-40 on page 61.
Parameter values
OL-1110-01, October 16, 2001
Initial release
OL-1110-23
xxix
Preface
xxx
OL-1110-23
CH A P T E R
This chapter provides an overview of the Cisco PGW 2200 Softswitch provisioning process and tools. It
includes the following sections:
Before You Begin, page 1-1
Cisco PGW 2200 Softswitch Provisioning Overview, page 1-2
Cisco PGW 2200 Softswitch Provisioning, page 1-2
Cisco PGW 2200 Softswitch Provisioning Rules, page 1-3
Cisco PGW 2200 Softswitch Provisioning Tools, page 1-3
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).
Before You Begin

You should have performed the following tasks before using this guide:
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
OL-1110-23
1-1
Chapter 1

All solutions involving the Cisco PGW 2200 Softswitch are configured using one or more
Cisco PGW 2200 Softswitch hosts, one or more Signaling System 7 (SS7) network signaling options,
and one or more media gateways that control bearer-traffic routing. Figure 1-1 shows a simplified layout
of the entities that make up a Cisco PGW 2200 Softswitch solution in a typical continuous -service
configuration.
Note
Most of the links shown Figure 1-1 represent multiple connections between devices.
Figure 1-1
Typical Solution Configuration Using the Cisco PGW 2200 Softswitch
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).

Provisioning tasks are performed in a sequence that can vary depending on your configuration. However,
some provisioning tasks must be performed before certain other tasks are performed. The following list
identifies a recommended provisioning sequence.
Add external nodes for each device connected to the network
1-2
OL-1110-23
Chapter 1
Add point codes
Add the interface cards
Add SS7 signaling service
Add media gateway signaling service
Add linksets
Add C7 IP links (redundant)
Add IP links
Add SS7 routes
Add SS7 subsystem
Add trunks (x24 or x31)

When provisioning the Cisco PGW 2200 Softswitch, the following rules apply.
Install the software on the active host.
Configure the software on the active host.
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.
Exit the provisioning session on the active host
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 Cisco PGW 2200 Softswitch includes two tools that you can use for provisioning:
The Voice Services Provisioning Tool Version 2.3, (VSPT) graphical user interface (GUI)
application.
The Man-Machine Language (MML) command-line interface (CLI) application.
OL-1110-23
1-3
Chapter 1
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.
1-4
OL-1110-23
Chapter 1
Figure 1-2
Sample Cisco Voice Services Provisioning Tool Window
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
Sample MML Script
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-stp
OL-1110-23
1-5
Chapter 1
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
Voice Services Provisioning Tool and MML Features
Specifications/Features
Voice Services Provisioning Tool
MML
System Basics
X-windows GUI front end, MML

back end.
CLI that interacts directly with the

Cisco PGW 2200 Softswitch.
System
Hardware/Software
Requirements
Sun Sparc station running

Sun Solaris 2.6 OS, or later.
Runs on the
Cisco PGW 2200 Softswitch host
server.
Batch File Support

Best Used For
Note
Running the VSPT on the

same server as the
Cisco PGW 2200 Softswitch
can adversely impact
performance. We recommend
that you use a separate server.
No
Yes
Setting up a single configuration

or few configurations on
individual machines.
Modifying an existing
configuration.
Creating batch files to

configure many
servers or to retrieve
measurements.
Modifying configurations.
Scaling large configurations.
Troubleshooting.
1-6
OL-1110-23
CH A P T E R

This chapter describes how to plan for your system provisioning.

This chapter includes the following sections:
Planning SS7 Signaling Routes, page 2-12
Planning SS7 Signaling Links, page 2-28
Planning Media Gateway Control Links, page 2-34
Route Analysis, page 2-87
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.
Prerequisite Provisioning Information

Before you can complete the provisioning planning tables in this chapter, you must collect the following
information:
Device addresses
SS7 point codes
External nodes
Media gateway controller interface card information
Trunk identification data
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.
Collecting External Device Addresses

For the control signaling network, list each device attached to the network that has a unique IP address
assigned to it. In addition to the device IP address, you should also record a device name, and a
description.
Collecting SS7 Point Code Data

The SS7 point codes are SS7 network addresses that uniquely identify every switch, Signal Transfer
Point (STP), and Cisco PGW 2200 Softswitch node on the SS7 network. To communicate with the SS7
network, you must get the SS7 point codes for your Cisco PGW 2200 Softswitch and for every SS7
network device with which you are to communicate. At a minimum, you need at least one originating
point code (OPC) for the Cisco PGW 2200 Softswitch node and one destination point code (DPC) for
the remote switch. If you plan to connect the Cisco Cisco PGW 2200 Softswitch to STPs, you need an
adjacent point code (APC) for every STP to which you connect.
Table 2-13 serves as a form you can use to plan point codes for the OPCs, DPCs, and APCs you need to
configure. The point code type, network address, and network indicator are required for each SS7
network device. The description column is not required; however, you can use this column to note special
information about a point code, such as its geographical location or network administrator.
Collecting External Node Information

An external node is another device, such as a media gateway, with which the
Cisco PGW 2200 Softswitch communicates. Within the Cisco PGW 2200 Softswitch software, an
external node is a system component that describes another device. The Cisco PGW 2200 Softswitch can
connect to a maximum of 1,000 media gateways, and you must configure an external node for each
MGW.
External node configuration parameters include:
External node name
Type
Description
ISDN signaling type
M3UA/SUA group number
Table B-16 serves as a form you can use to plan for each external node.
Collecting Media Gateway Controller Interface Card Data

When configuring connections between the Cisco PGW 2200 Softswitch and Cisco IP Transfer Point LinkExtenders (ITP-Ls), media gateways (MGWs), or SS7 signaling points (SPs), you must be ready to
enter information about the name, location, type, and address of the network interface cards. The
interface card location and type are determined when the card is installed. The location is identified by
the slot where the card is installed, and the type must be the type designation listed in the second column
of Table 2-1. Table B-2 serves as a form you can use to record Ethernet interface card information.
2-2
OL-1110-23
Chapter 2
Note
The CARD component is not supported in software Release 9.4(1).

Table 2-1
Media Gateway Controller Network Interface Card Type
Card
Type Designation
Card Slot Location
Description
Ethernet interface
card
EN
(No slot number is Used for connections to Cisco ITP-Ls

required for
and MGWs.
Ethernet cards.)
Collecting SS7 Signaling Service Data

When configuring connections between the Cisco PGW 2200 Softswitch and the SS7 signaling network,
you must be ready to enter the following information about the SS7 service for the link to be created.
Service type
Name
Description
Protocol type (SS7-ANSI, SS7-China, SS7-ITU, SS7-Japan, or SS7-UK)
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.
Collecting MGW Signaling Service Data

The signaling service between the Cisco PGW 2200 Softswitch and the media gateway (MGW) needs to
be defined for each pair attached to the network. You must be ready to enter the following information
about the MGW signaling service:
Service type
Device
Description
Protocol service
Side
This MGW signaling service link information can be listed in Table B-21.
Collecting Linkset Data

The linkset must be defined for each link between the Cisco PGW 2200 Softswitch and the adjacent STP.
If there are two adjacent STPs, you need to create two linksets (for example, LS01 and LS02). A linkset
can contain from 1 to 16 links. You must be ready to enter the following information about each linkset:
Point code
Type of component
Name
Description
OL-1110-23
2-3
Chapter 2
Protocol (SS7-ANSI, SS7-China, SS7-ITU, SS7-Japan, or SS7-UK)
IP transport type
This linkset information can be listed in Table B-9.
Collecting Cisco ITP-L Data

A link must be defined for each path from the Cisco ITP-L to the Cisco PGW 2200 Softswitch. There
must be one path (two maximum) for each connection between the Cisco ITP-L and
Cisco PGW 2200 Softswitch. The link corresponds to the linksets you previously created. You will
create a linkset pair for each linkset that exists in your system. For example, if your system has two
linksets, you will create two links for each linkset, resulting in your creating a total of four links. You
must be ready to enter the following information about each Cisco ITP-L linkset:
Description
Linkset name
Card interface type
Linkset type
Linkset rate
Protocol family variant
Cisco ITP-L IP address
Cisco PGW 2200 Softswitch IP address
This linkset information can be listed in Table B-9.
Collecting Sessionset Data

A sessionset 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, or BSMV0.
Sessionset parameters include:
External node name (predefined)
IP address
Peer IP address
Port number
Peer port number
IP route
Type
This sessionset information can be listed in Table B-27.
Collecting C7 IP Link Data

A C7 IP link needs to be defined for each physical SS7 link that is connected to the SS7 network by the
Cisco ITP-L. The C7 IP links correspond to linksets you previously created. You must be ready to enter
the following information about the C7 IP link:
Description
2-4
OL-1110-23
Chapter 2
Linkset
Sessionset
SLC
Priority
Time slot (the physical slot (serial port) information on the Cisco ITP-L)
This C7 IP link information can be listed in Table B-10.
Collecting IP Link Data

An IP link needs to be defined from the MGW to the Cisco PGW 2200 Softswitch (MGCP path), from
the Cisco PGW 2200 Softswitch to the ITP-L (SS7 MTP3 backhaul path), from one
Cisco PGW 2200 Softswitch to another Cisco PGW 2200 Softswitch (EISUP path), and from each NAS
to the Cisco PGW 2200 Softswitch. You must be ready to enter the following information about the IP
link:
Description
Line interface
IP address
Port number
Priority
Peer IP address
Peer port field
Service
Next hop
Net mask
This IP link information can be listed in Table B-23.
Collecting SS7 Route Data

You must define an SS7 route for each signaling route from the Cisco PGW 2200 Softswitch to the
PSTN switch. There must be an SS7 route for each linkset. You must be ready to enter the following
information about the SS7 route to be created:
Name
Description
Signal DPC
Linkset
OPC
This SS7 route information can be listed in Table B-12.
OL-1110-23
2-5
Chapter 2
Collecting SS7 Subsystem Data

An internal SS7 subsystem must be defined that connects each mated pair of STPs. This allows the
Cisco PGW 2200 Softswitch to route traffic over the C-links between the STPs. Thus if one STP fails,
the Cisco PGW 2200 Softswitch can route traffic over a C-link to the other STP. The SS7 subsystem
component type represents an SS7 subsystem. You must be ready to enter the following data:
MML name of SS7 subsystem
Component description
MML name of Adjacent point code or TCAP/IP service
Protocol family
Adjacent point code of the mated STP
Priority
Local subsystem number
STP/SCP index used for IN triggers
Transport protocol (must be SUA for this feature)
MML name of an SUA key (optional)
Remote subsystem number
The SS7 subsystem component structure is shown in Table B-15.
Collecting Trunk Data (Nailed)

During the provisioning process, you must define all of the nailed bearer trunks that connect remote
switches to the media gateway. Each remote switch is identified by its DPC, and each trunk is identified
by the trunk ID. Table B-13 provides space for you to provide the following information for the nailed
trunks coming from remote switches:
Trunk ID (name)
Source signaling service
Source span
Source time slot/CIC (1)
Destination signaling service
Destination span
Destination time slot/CIC(1)
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
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.
Collecting Trunk Data (Switched)

During the provisioning process, you must define all of the switched bearer trunks that connect remote
switches to the media gateway. Each remote switch is identified by its DPC, and each trunk is identified
by the trunk ID. Table B-14 provides space for you to provide the following information for the switched
trunks coming from remote switches:
Trunk ID (trunk group member number)
Trunk group number
Span
Circuit identifier code
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.
Collecting QSIG/Q.931 Over BRI Backhaul Path Data

The QSIG/Q.931 over BRI Backhaul component type represents an QSIG/Q.931 over BRI Backhaul
signaling service to a particular Cisco BRI voice gateway. You must be ready to enter the following data:
MML name
MML name of the associated external node
Q.931 call model side (user or network)
MDO file name (ETS_300_102, Q931, or ETS_300_172)
Customer group ID
Customer group table
OL-1110-23
2-7
Chapter 2
Call reference length (0 through 2 bytes)
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.
Collecting Backhaul TCP Link Data

The Backhaul TCP link component type represents the connection between the
Cisco PGW 2200 Softswitch and a Cisco BRI voice gateway. You must be ready to enter the following
data:
MML name
Description of this component
Signaling type (BRI)
Local IP address
Local port number
Destination IP address
Destination port number
MML name of the external node
MML name of first IPROUTE (optional)
You can define the parameters for your Backhaul TCP links in Table B-24.
Collecting IP Route Data

The IP route represents a static IP route. You must be ready to enter the following data:
IP route name
Destination hostname or IP address
Subnet mask of Destination (optional)
Next hop router IP address
Local IP address
Priority
The IP route component information can be listed in Table B-28.
Collecting IP FAS Path Data

The IP FAS path represents an IP Feature Associated Signaling (FAS) signaling service to a particular
Cisco VoIP gateway. You must be ready to enter the following data:
MML name
2-8
OL-1110-23
Chapter 2
Q.931 call model side (user or network)
MDO file name
Customer group ID
A-B flag
Call reference length (0 through 2 bytes)
ISDN FAS signaling services information can be listed in Table B-29.
Collecting DPNSS Path Data

This component type represents a DPNSS signaling service to a particular Cisco VoIP gateway. You must
be ready to enter the following data:
Unique ID of this component and component name used in MML commands
Customer group ID
Identification of the DPNSS path as either A side, B side, or neither
Signaling port number (physical port on the Cisco access server)
Signaling port slot (physical slot on the Cisco access server)
DPNSS signaling services component information can be listed in Table B-30.
Collecting M3UA Key Data

This component represents an M3UA routing key. You must be ready to enter the following data:
M3UA key name
Associated OPC
Associated DPC (optional)
Routing context value
Service indicator
Network appearance (optional)
The M3UA key component information can be listed in Table B-32.
Collecting M3UA Route Data

This component represents an M3UA route. You must be ready to enter the following data:
M3UA route name
Associated DPC
Associated external node
OL-1110-23
2-9
Chapter 2
Associated OPC
The M3UA route component information can be listed in Table B-33.
Collecting D-Channel Data

The D-channel component type represents the connection between the Cisco PGW 2200 Softswitch and
a Cisco VoIP gateway. You must be ready to enter the following data:
MML name
Signaling type
Priority
MML name of associated MGCP IP or backhaul TCP link
Physical slot number on voice gateway
Physical port number for slot on voice gateway
Local subunit
D-channel component information can be listed in Table B-31.
Collecting SCTP Association Data

The SCTP association represents the connection between the Cisco PGW 2200 Softswitch and media
gateways (IUA) and signaling gateways (M3UA/SUA). The Cisco ITP is a signaling gateway. You must
be ready to enter the following data:
MML Name of the SCTP association
Signaling Type
MML name of SGP (required only form M3UA/SUA associations)
First local address
Second local address (optional)
Local SCTP port number (optional)
The highest priority destination address
The lowest priority destination address (optional)
Destination SCTP port number. (optional)
MML Name of first IPROUTE (optional)
MML Name of second IPROUTE (optional)
Number of bytes to advertise for the local receive window. (optional)
Maximum number of times to retransmit SCTP INIT message (optional)
Maximum initial timer retransmission value (optional)
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)
2-10
OL-1110-23
Chapter 2
Maximum time SCTP waits for other outgoing datagrams for bundling (optional)
Minimum value allowed for the retransmission timer (optional)
Maximum value allowed for the retransmission timer (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)
Maximum number of retransmissions to either PEERADDR1 or PEERADDR2 before it is declared

failed (optional)
The SCTP association component structure is shown in Table B-34.
Collecting SS7 Signaling Gateway Process Data

This component represents a SS7 signaling gateway process (SGP). You must be ready to enter the
following data:
MML name of SGP
M3UA route name
External node that is running the SS7 signaling gateway process
The SS7 signaling gateway process component structure is shown in Table B-35.
Collecting SS7 Signaling Service Data

This component represents an SS7 signaling service or signaling path to a particular SS7 switch
(destination). You must be ready to enter the following data:
MDO file name
Destination point code MML name
Customer group ID
M3UA Routing key ID MML name
The SS7 signaling service component structure is shown in Table B-36.
Collecting SUA Key Data

This component represents a SUA Routing key. You must be ready to enter the following data:
SUA key name
Associated OPC
Associated APC (optional)
OL-1110-23
2-11
Chapter 2
Planning SS7 Signaling Routes
Associated local SSN
The SUA key component structure is shown in Table B-38.
Collecting SUA Route Data

This component represents a SUA route. You must be ready to enter the following data:
SUA route name
Associated APC
Associated external node
Associated OPC
Associated remote SSN
The SUA route component structure is shown in Table B-39.
Collecting SIP Path Data

This component type represents a SIP path. You must be ready to enter the following data:
Local port number
Priority
Local logical IP address
Signaling service supported
The SIP path component structure is shown in Table B-40.

To configure routes between the Cisco PGW 2200 Softswitch and a destination device (for example, a
switch), you must do the following:
1.
Define the point codes (SS7 network addresses) of devices along the signaling route.
2.
Define linksets.
3.
Override linkset properties (if necessary).
4.
Define C link as an SS7 subsystem for each pair of STPs.
5.
Define an SS7 signaling service to support the signaling route.
6.
Override the SS7 signaling service properties (if necessary).
7.
Define the SS7 signaling route.
Figure 2-1 shows the relationship of these components. Figure 2-2 shows the order in which these
components are to be configured.
2-12
OL-1110-23
Chapter 2

Figure 2-1
SS7 Signaling Route Configuration Components
External switch
Virtual switch zone

Media gateway
controller
Linkset
Route A
SS7
signaling
service
Destination
point
code
(DPC)
Figure 2-2
Origination
point
code
(OPC)
SS7 Signaling Route Component Hierarchy
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.
Planning Point Codes (SS7 Network Addresses)

The first step in planning signaling routes is to identify the SS7 network devices that link the
Cisco PGW 2200 Softswitch to remote switches. To uniquely identify these network devices, you must
assign a point code (see Table 2-2 for a list of point code parameter descriptions) to each network device,
which serve as SS7 network addresses. The point codes must be unique within the SS7 network. You
must get these point codes from your SS7 network administrator.
Point codes are necessary for the following network devices:
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
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
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:
VSPT name: Originating Point Code
MML name: OPC Table B-6
VSPT name: Destination Point Code
MML name: DPC Table B-5
VSPT name: Adjacent Point Code
MML name: APC Table B-7
Table 2-2
Point Code Parameter Descriptions
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
SS7 network address in dotted notation.
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.
2-14
OL-1110-23
Chapter 2

Table 2-2
Point Code Parameter Descriptions (continued)
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
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
VSPT name: LinkSet
MML name: LNKSET
When configuring linksets for STP connections, you will usually configure two linksets for each pair of
STPs.
Table 2-3
Linkset Configuration Parameter Descriptions
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.
OL-1110-23
2-15
Chapter 2
Table 2-3
Linkset Configuration Parameter Descriptions
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
PROTO
Protocol family Enter one of the following:
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.
Planning Linkset Properties

Linkset properties serve as additional configuration parameters you can use to tune linkset
communications. Table 2-4 lists the default properties assigned to linksets. These properties apply to all
linksets you create. You do not have to enter these values.
To change linkset properties, use the following component:
Table 2-4
VSPT name: Properties (accessed from the LinkSet component window)
MML name: LNKSETPROP
Linkset Property Descriptions
MML Parameter Name
Default Value
Unit
Description
mtp2LssuLen
1 for all except

SS7-JAPAN=2
Octets
Link status signal unit, status field length. Specify either 1 or

2. This property is removed in software Revision 9.3(1) and
later.
mtp2MaxAlignRetries
Attempts
Maximum number of attempts to align link before declaring

it Out-of-Service (OOS). Value range: 1 through 10 attempts.
Note
The Cisco PGW 2200 Softswitch also reattempts link

alignment every 5 seconds.
This property is removed in software Revision 9.3(1) and

later.
mtp2MaxMsuFrmLen
272
Octets
Maximum frame length of a C7 message signal unit. Specify

62 or 272. This property is removed in software Revision
9.3(1) and later.
mtp2MaxOutsFrames
127 for all except

SS7-JAPAN=40
Frames
The maximum outstanding frames that can be sent without

receiving acknowledgment. Value range: 1 through 127. This
property is removed in software Revision 9.3(1) and later.
2-16
OL-1110-23
Chapter 2

Table 2-4
Linkset Property Descriptions (continued)
MML Parameter Name
Default Value
Unit
Description
mtp2ProvingEmgT4
6 for all except

SS7-JAPAN=30
Tenths of a
second
Emergency proving period. Value range: 5 through 7 tenths of

a second. This property is removed in software Revision
9.3(1) and later.
mtp2ProvingNormalT4
23 for all except

SS7-JAPAN=302
Tenths of a
second
Normal proving period. Value range: 1 through 3 seconds.

later.
mtp2SuermThr
64 for all except

Frames
SS7-JAPAN=16384
mtp2T1
SS7-ANSI=130
SS7-UK=450
SS7-CHINA=450
SS7-ITU=450
SS7-JAPAN=150
Tenths of a
second
Maximum period in Aligned/Ready state before return to

Out-of-Service state. Value range: 12 through 16 seconds (for
ANSI) or 40 through 50 seconds (for UK, CHINA, and ITU).
later.
mtp2T2
SS7-ANSI=115
SS7-UK=250
SS7-CHINA=250
SS7-ITU=250
SS7-JAPAN=50
Tenths of a
second
Maximum period in Not Aligned state before return to

Out-of-Service state. Value range: 5 through 30 seconds. This
mtp2T3
SS7-ANSI=115
SS7-UK=20
SS7-CHINA=20
SS7-ITU=20
SS7-JAPAN=30
Tenths of a
second
Maximum period in Aligned state before return to

Out-of-Service state. Value range: 5 through 14 seconds (for
ANSI) or 1 through 2 seconds (for UK, CHINA, and ITU).
later.
mtp2T5
1 for all except

SS7-JAPAN=2
Thousandths Period for sending a SIB3 message to far-end.

of a second Value range: 80 through 120 seconds. This property is
removed in software Revision 9.3(1) and later.
mtp2T6
SS7-ANSI=30
SS7-UK=60
SS7-CHINA=60
SS7-ITU=60
SS7-JAPAN=30
Tenths of a
second
Remote congestion timer. If congestion is not cleared before

expiration of this timer, the link fails. Value range: 1 through
6 seconds (for ANSI) or 3 through 6 seconds (for UK,
CHINA, and ITU). This property is removed in software
Revision 9.3(1) and later.
mtp2T7
10 for all except

SS7-JAPAN=20
Tenths of a
second
MTP2 acknowledgment timer. On expiration, the link fails

and an excessive delay of acknowledgment management
message is generated. Value range: 0.5 through 2 seconds (for
UK, CHINA, and ITU). This property is removed in software
mtp3ApcMtpRstrtT28
SS7-ANSI=10
Tenths of a
second
Overall restart timer for signaling point adjacent to one whose

MTP restarts. Value range: 3 through 35 seconds (for ANSI
only).
mtp3DlnkConnAckT7
10 for all except

SS7-JAPAN=20
Tenths of a
second
Waiting for signaling data link connection acknowledgment.

Value range: 1 through 2 seconds, or through 5 seconds when
connecting over a Cisco ITP-L.
mtp3FrcUnhT13
10 for all except

SS7-JAPAN=0
Tenths of a
second
Waiting for force uninhibited. Value range: 0.8 through 1.5

seconds.
Signal unit error rate monitor threshold for emergency

operation. Value range: 1 through 16385. This property is
OL-1110-23
2-17
Chapter 2
Table 2-4
MML Parameter Name
Default Value
Unit
Description
mtp3InhAckT14
20 for all except

SS7-JAPAN=0
Tenths of a
second
Waiting for inhibit acknowledgment. Value range: 2 through

3 seconds.
mtp3LocInhTstT20
SS7-ANSI=900
Tenths of a
second
Waiting to repeat local inhibit test.

Value range: 90 through 120 seconds (for ANSI only).
mtp3MaxSltTries
2 for all except

SS7-JAPAN=0
Messages
Maximum number of retries of signaling link test message. If

MTP3 does not receive a response after two signaling link test
messages, the system fails the link. Value range: 1 through 5.
mtp3MsgPriority
SS7-ANSI=2
SS7-UK=1
SS7-CHINA=1
SS7-ITU=2
SS7-JAPAN=2
mtp3MtpRstrtT20
900 for all except

SS7-JAPAN=0
Message priority of management messages for congestion

periods.
Value range: 0 through 3. Priority 1 (default) indicates
without congestion priorities. Priorities greater than 1
indicate multiple congestion priorities. Priority 3 is the
highest priority.
Tenths of a
second
Overall MTP restart timer at the signaling point whose MTP

restarts. Value range: 0 to disable, or 59 through 61 seconds.
Note
This parameter is for UK, CHINA, and ITU.
SS7-UK=640
SS7-CHINA=10
SS7-ITU=640
SS7-JAPAN=0
Tenths of a
second
mtp3LocInhTstT22
3000 for all except

SS7-JAPAN=0
Tenths of a
second

Value range: 3 through 6 minutes.
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
Traffic restart waiting message at local MTP restart.

Value range: 12 through 15 seconds.
mtp3TfrUsed
false
mtp3TraSnT29
SS7-ANSI=600
Tenths of a
second
Timer started when traffic restart allowed is sent in response

to unexpected traffic restart allowed or traffic restart waiting.
mtp3tstSltmT1
SS7-ANSI=60
SS7-UK=50
SS7-CHINA=50
SS7-ITU=50
SS7-JAPAN=0
Tenths of a
second
Waiting for signaling link test acknowledgment message.

This must be greater than the value in mtp2T6. Value range: 0
through 12 seconds.
mtp3tstSltmT2
SS7-ANSI=600
SS7-UK=300
SS7-CHINA=300
SS7-ITU=300
SS7-JAPAN=0
Tenths of a
second
Interval for sending signaling link test message.

mtp3ApcMtpRstrtT21
Overall MTP restart timer at an SP adjacent to an SP whose

MTP restarts. Value range: 0 to disable, or 63 through 65
seconds.
Note
This parameter is for UK, CHINA, and ITU.
Transfer restricted procedure is enabled (true) or disabled

(false). Set to true or false.
2-18
OL-1110-23
Chapter 2

Table 2-4
MML Parameter Name
Default Value
Unit
Description
mtp3UnhAckTl2
10 for all except

SS7-JAPAN=0
Tenths of a
second
Waiting for uninhibited acknowledgment.

Value range: 0.8 through 1.5 seconds.
mtp3T0
SS7-JAPAN=200
Tenths of a
second
Not used.
mtp3T7
SS7- JAPAN=20
Tenths of a
second
Waiting for signaling data link connection acknowledgement.

mtp3T12
SS7-JAPAN=0
Tenths of a
second
Waiting for signaling data link connection acknowledgement.

Value range: 500 through 1500 milliseconds.
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
Denotes versions for protocol standards supported for MTP.

for SS7-ANSI: options ANSI92, ANSI96
for SS7-UK, SS7-CHINA, SS7-ITU: options ITU88 and
ITU92 for SS7-JAPAN: options Japan, TTC.
rudpAck
enable
Not used.
rudpKeepAlives
enable
Not used.
rudpNumRetx
The maximum number for Retransmission count.

Value range: 1 through 100.
rudpWindowSz
32
The maximum number for Unacknowledged Segments in the

RUDP window.
rudpRetxTimer
rudpSdm
enable
Tenths of a
second
The Retransmission timeout. Value range: 2 through 100.

Not used.
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
OL-1110-23
2-19
Chapter 2
Planning SS7 Subsystems

In the Cisco PGW 2200 Softswitch, an SS7 subsystem is used to mate two STPs or to define SS7 systems
that access IN services. When two STPs are defined as mates within the Cisco PGW 2200 Softswitch,
the software can use either STP for communications with an external switch. Table 2-5 lists the
configuration parameters you define for each SS7 subsystem during provisioning. Table B-15 serves as
a form that you can use to plan the SS7 subsystems.
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:
VSPT name: SS7SubSys
MML name: SS7SUBSYS
For mated STPs, the subsystem defined for each STP defines the other STP as the mate using the
MATEDAPC parameter.
Table 2-5
SS7 Subsystem Configuration Parameter Descriptions
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
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
MML name of a previously defined originating point code.
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
Not used if SUAKEY is specified.
Default = 1.
2-20
OL-1110-23
Chapter 2

Table 2-5
MML Parameter
Name
PROTO
SS7 Subsystem Configuration Parameter Descriptions (continued)
Voice
Services
Provisioning
Tool
Parameter
Name
Protocol
family
Description
Protocol family. When mating STPs, only the SS7 variant is allowed.
SS7-ANSI - when creating an AIN subsystem.
SS7-ITU - when creating an AIN subsystem.
SS7-China - when mating an STP pair.
SS7-Japan - when mating an STP pair.
SS7-UK - when mating an STP pair.
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
SUA Routing MML name of previously defined routing key.

Key
This is an optional parameter and is used only for SUA.
Not used if OPC is specified.
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.
Planning SS7 Routes

The final step in planning SS7 signaling routes is to define the SS7 routes themselves. Routes are defined
in terms of the point codes along the path and the linksets that lead from the MGC node through the STPs
to each DPC. Table 2-6 describes the configuration parameters you use to define routes during
provisioning. Table B-12 serves as a form you can use to plan your routes. It is a good practice to define
two routes to each remote switch. Each route should pass through a different STP in a mated pair. The
linkset parameter, LNKSET, defines which STP a route will follow.
To define an SS7 route, use the following component:
VSPT name: SS7Route
MML name: SS7ROUTE
OL-1110-23
2-21
Chapter 2
Table 2-6
SS7 Route Configuration Parameter Descriptions
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.
Planning the SS7 Signaling Service

The SS7 signaling service is the Cisco MGC software service that communicates over the route with a
remote switch. You must define a separate service for each remote switch. Table 2-7 describes each of
the SS7 signaling service parameters and provides space for you to plan the configuration of one service.
Table B-21 serves as a form you can use to plan your signaling services.
To define an SS7 signaling service, use the following component:
VSPT name: SigSS7
MML name: SS7PATH
Table 2-7
SS7 Signaling Service Configuration Parameter Descriptions
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
MML name
Unique name for this signaling service. Enter as many as 20

alphanumeric characters and enclose in straight quotes. Hyphens (-) can
be used.
DESC
Description
Text description of this signaling service. Enter as many as 128

characters and enclose in straight quotes.
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
Destination point code. Enter the MML name of a previously defined

destination point code.
2-22
OL-1110-23
Chapter 2

Table 2-7
SS7 Signaling Service Configuration Parameter Descriptions (continued)
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
Customer Group ID. Virtual network identification characters (formerly

called the Closed User Group). Values accepted for this field depend on
the use of the D channel. Used to retrieve information about this
signaling service and which dial plan to use. Enter the four-digit ID.
Default = 0000.
OPC
Originating
Point Code
Originating Point Code. Enter the MML name of a previously

originating point code.
Changing SS7 Signaling Service Properties

SS7 signaling service properties serve as additional configuration parameters that you can use to tune
signaling service communications. Table 2-8 lists the default properties assigned to an SS7 signaling
service. These properties apply to all SS7 signaling services you create. You do not have to enter these
values.
To change SS7 signaling service properties, use the following component:
Table 2-8
VSPT name: Properties (access from the SigSS7 component window)
MML name: SIGSVCPROP
SS7 Signaling Service Property Descriptions
MML Parameter Name
Default Value
Description
adjDestinations
16
Number of adjacent destination point codes. Value range: 1 through 256.
AInternationalPrefix
NULL
International prefix string to be added to the international dialed number

when NOA is enabled. Value range: NULL or a numeric string.
ANationalPrefix
NULL
National prefix string to be added to the national dialed number when

NOA is enabled. Value range: NULL or a numeric string.
BInternationalPrefix
NULL
International prefix string to be added to the international dialed number

when NOA is enabled. Value range: NULL or a numeric string.
BNationalPrefix
NULL
National prefix string to be added to the national dialed number when

NOA is enabled. Value range: NULL or a numeric string.
BothwayWorking
Set to 0 to disable both way release / circuit free handling for BTNUP
protocol. Value range: 0 or 1.
CGBA2
Determines if paired 0 or single 1 circuit group blocking

acknowledgments (CGBAs) are required before the blocking is
considered successful. Only applicable to ANSI SS7, IBN7, and CTUP
protocols.Value range: 0 or 1.
OL-1110-23
2-23
Chapter 2
Table 2-8
SS7 Signaling Service Property Descriptions (continued)
MML Parameter Name
Default Value
Description
CLIDefaultAllowed
false
Adjusts the presentation restricted field in the calling line identity to

presentation allowed if set to true. Takes the mapped value from the
OCC or TCC protocol side or the default value from the map for this
field if false. Value range: true or false.
CLIPEss
Sets the Calling Line Identity Presentation Essential operation. 0Do

not request CLI., 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.
Value range: 0, 1, or 2.
COLDefaultAllowed
false
Adjusts the presentation restricted field in the Connected Line ID to

presentation allowed if set to true. Takes the mapped value from the
OCC or TCC protocol side or the default value from the map for this
field if false. Value range: true or 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
Statistical COT. Value range: 0 through 100%.
dialogRange
TCAP transaction ID range (for example, 1 through 10000) for a specific

subsystem.
0 = entire range.
ForwardCLIinIAM
Set to 1 if outgoing initial address message (IAM) should contain the

calling line identity, if available. Only applicable for BTNUP when
interworking from other protocols.
Value range: 0 or 1.
ForwardSegmentedNEED
Set to 0 to disable the forwarding of segmented NEED messages within

the BTNUP_NRC protocol. If segmenting is disabled, all mandatory
DPNSS information elements will be packed into a single BTNUP
NEED message.
2-24
OL-1110-23
Chapter 2

Table 2-8
MML Parameter Name
Default Value
Description
GLARE
Call Collision Handling. Valid values are:
Note
Note
Note
Note
0 = No glare handling; also known as yield to all double seizures.

Call collision results in a REL sent to both calls.
Both ends of a link can be given this option. Default = 0.
1 = The Cisco PGW 2200 Softswitch has control of all circuits and
any call collisions are handled by this Cisco PGW 2200 Softswitch.
It ignores incoming IAMs and proceeds with its own calls as
normal.
Only one end of a link can be designated with this option.
2 = Highest point code controls the even circuits. Depending on the
OPC of the Cisco PGW 2200 Softswitch nodes, the side that has the
higher point code will control the even circuits, while the side with
the lower point code will control the odd circuits.
Both ends of a link can be given this option.
3 = No control. The Cisco PGW 2200 Softswitch specified with this
option does not control any circuits. It accepts incoming IAMs from
the side with control.
This option is usually used along with the remote node
designated with control.
GRA2
Determines if paired (0) or single (1) group reset acknowledgments

(GRAs) are required before the reset is considered successful. Only
applicable to ANSI SS7, IBN7, and CTUP protocols.
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
This property (available in software Release 9.4(1) patch 8 and above)

is assigned to an SS7 point code type signal path. Enables Group Reset
on Service State Change procedure at point code initialization.
Note
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.
OL-1110-23
2-25
Chapter 2
Table 2-8
MML Parameter Name
Default Value
Description
hopCount
Default hop count. Value range: 0 or 15 (this indicates the maximum

number of hops allowed for SCCP messages).
layerRetries
Number of times to resend request to adjacent layer without getting a

response. Value range: 0 through 5. 0 = No retries.
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
Maximum length of message to MTP3.

This value must be less than the value for mtp2MaxMsuFrmLen.
NatureOfAddrHandling
Determines whether or not to do pre-analysis. Value range: 0 or 1.
NFASImplicitInterfaceId
65535
Is used when an incoming ISDN message containing a Channel

identification information element identifier with bit 7 of octet 3 set to
0 (Interface implicitly identified) as the implied interface ID value.
This property is added in software Release 9.5(2).
Normalization
Normalization of dialed number to unknown. Set to 0 for disabled and 1

for enabled. Value range: 0 or 1.
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).
OMaxDigits
24
Specifies maximum number of digits to receive for overlap digit

processing for call origination from this traffic path.
Value range: 0 through system maximum.
OMinDigits
Specifies minimum number of digits to receive for overlap digit

processing for call origination from this traffic path.
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).
OOverlap
Set to 1 to enable overlap signaling for call origination from this traffic
path.
OverlapDigitTime
Overlap interdigit timer. The time to wait for the rest of the digits.
Note
If OverlapDigitTimeValue timer is set to more than 30 seconds,

other timers expire before this timer.
2-26
OL-1110-23
Chapter 2

Table 2-8
MML Parameter Name
Default Value
Description
OwnClli
na
Specifies the common language location identifier (CLLI). This can be

up to 11 alphanumerical digits.
RedirMax
Specifies the maximum allowable value of the redirection counter

parameter available in some C7 signaling systems before the call is
force-released. Used to prevent routing loops in certain applications.
Value range prior to Release 9.7(3) S22P22: 0 to system maximum.
Value range for Release 9.7(3) S22P22 and later:
15:
OCCAllow the specified number (15) of redirections before the

call is force-released.
TCCReset the redirect counter to 5 if it is < 1 or > 5.
0:
OCCAllow the redirection counter to have any value from 1 to 7.
TCCIf the redirection counter is set to a value 07, set it as is; if

the redirection counter is greater than 7, reset it to 7.
Note
restartTimer
10
OCC = Originating (side) call control.

TCC = Terminating (side) call control.
Time (in tenths of a second) to pause before sending next group of

messages to MTP3 after restart. Value range: 0 through 100.
RoutePref
Determines the preferred route. Value range: 0 through 9.

0 = No Preference (default)
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.
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
Time (in tenths of a second) to maintain the same signal linkset in

class 1 (connectionless) messages. This is the type of service provided
by the SCCP layer. Value range: 0 through 600.
0 = Disabled, 300 = 30 seconds.
OL-1110-23
2-27
Chapter 2
Planning SS7 Signaling Links
Table 2-8
MML Parameter Name
Default Value
Description
srtTimer
SS7-ANSI=300
Time (in tenths of a second) between sending Subsystem Route Test

message (SRT) to remote subsystems. Value range: 0 through 3000.
0 = disabled, 300 = 30 seconds.
sstTimer
SS7-ANSI=300
Time (in tenths of a second) between sending Subsystem Status Test

(SST) messages to an unavailable remote subsystem.
standard
SS7-ANSI=ANSI9
6,
SS7-ITU=ITU96,
Version of protocol standard supported for this STP/SCP.
ANSI96,
ITU96,
ANSI92,
ITU92
TMaxDigits
24
Specifies maximum number of digits to receive for overlap digit

processing for call termination to this traffic path.
TMinDigits
Specifies minimum number of digits to receive for overlap digit

processing for call termination to this traffic path.
TOverlap
Set to 1 to enable overlap signaling for call termination to this traffic

path.
variant
SS7-ANSI=SS7-A
NSI, SS7-ITU
SS7 protocol variants supported by the local subsystem.
VOIPPrefix
A numeric string.

Once you have planned your SS7 routes (as described in the Planning SS7 Signaling Routes section),
it is time to plan the communication links between the Cisco PGW 2200 Softswitch and the SS7 SPs.
SPs are SS7 network nodes, such as STPs and SSPs, with which the Cisco PGW 2200 Softswitch
communicates. The Cisco PGW 2200 Softswitch supports two types of SP links: Cisco ITP-L links and
direct SP links. Cisco ITP-L links use the Cisco ITP-L to offload MTP 1 and MTP 2 processing to
Cisco ITP-Ls. Direct SP links directly link the Cisco PGW 2200 Softswitch to an SP; the
Cisco PGW 2200 Softswitch performs all signal processing including MTP 1 and MTP 2 processing.
While linksets define which SP a given route uses, it is the links that carry the communications traffic.
Signaling Link Component Hierarchy (without Cisco ITP-Ls)
This section describes how to plan for provisioning the signaling link components:
1.
Create point codes (APC or DPC)
2-28
OL-1110-23
Chapter 2

2.
Create linkset
3.
Override linkset properties (if necessary)
4.
Create adapter
5.
Create interface
6.
Create TDM link
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:
Cisco PGW 2200 Softswitch cards
Cisco PGW 2200 Softswitch interfaces
Links
The following sections describe how to plan for each of these components.
Planning Network Cards for Cisco ITP-L Communications

Cards are the hardware cards that are installed on the host computer and provide the network interfaces
that communicate with other devices. When planning STP links, you define cards that will communicate
with the MGC node Cisco ITP-Ls.
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
VSPT name: Adapter
MML name: CARD
The CARD component is not provisionable in software Release 9.4(1).
OL-1110-23
2-29
Chapter 2
Table 2-9
Card Configuration Parameter Descriptions for Cisco ITP-L Communications
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
Unique name for this component. Enter as many as 20 alphanumeric

characters and enclose in straight quotes. Hyphens (-) can be used.
SLOT
Slot
None
Location of card or adapter within the host machine. Acceptable values

depend on the host machine. The first slot is usually 0. Enter a value
from 0 through 15.
TYPE
Type
None
The interface card type. Acceptable value is:
Description
DESC
Description
None
EN
Text description of this component. Enter as many as 128 characters and

enclose in straight quotes.
Planning Ethernet Interfaces for Cisco ITP-L Communications

Each SS7 link in the MGC node must be associated with an interface component, which must be
associated with a network card. The interface represents a physical network connection on the network
card.
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
VSPT name: EnetIF
MML name: ENETIF
ENETIF is not supported in software Release 9.4(1).

Table 2-10 describes the configuration parameters that define an Ethernet interface. Table B-2 serves as
a form you can use to plan the Ethernet interfaces on your Cisco PGW 2200 Softswitch.
Table 2-10
Ethernet Interface Configuration Parameter Descriptions
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.
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.
Planning TDM Interfaces for Cisco ITP-L Communications

Each SS7 link in the Cisco PGW 2200 Softswitch node must be associated with an interface component,
which must be associated with a network card. The interface represents a physical network connection
on the network card.
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
TDMIF is not supported in software Release 9.4(1).

To provision a TDM interface for the V.35 card, use the following component:
VSPT name: TDMIf
MML name: TDMIF
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
TDM Interface Configuration Parameter Descriptions
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
Unique name for this link. Enter as many as 20 alphanumeric characters

and enclose in straight quotes. Hyphens (-) can be used.
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
Selects the line interface number. Choose 1 through 4 for V.35;

otherwise, choose1.
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
OL-1110-23
2-31
Chapter 2
Table 2-11
TDM Interface Configuration Parameter Descriptions (continued)
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
Selects the link framing format. Choose ESF (extended superframe) or

D4 (superframe) for T1. Choose CRC4 (cyclic redundancy check 4) or
CCS (common channel signaling) for E1. Choose NA (not applicable)
for V.35.
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.
Planning A-Links Through Cisco ITP-Ls

After you have planned your cards and interfaces, you are ready to plan the SS7 signaling links. When
you configure C7 IP links, you can configure a maximum of two of these links for every Cisco ITP-L.
Within the MGC node, the ends of each link are identified as follows:
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.
2-32
OL-1110-23
Chapter 2

For SS7 provisioning, keep the following points in mind.

A maximum of 6 OPCs that can be supported.
Enter routing information for the OPC before creating the C7 IP link.
For each OPC added, you must specify a different local port for each C7 IP link.
Provision a maximum of 32 links per local port number. Specify another port number for each additional
group of 32 links.
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
VSPT name: C7IPLink
MML name: C7IPLNK
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
C7 IP Link Configuration Parameter Descriptions
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None

DESC
Description
None
Text description of this link. Enter as many as 128 characters and

PRI
Priority
SS7 route priority. Enter an integer that is greater than 0. One (1) is the
highest priority level.
SESSIONSET
Session set
None
MML Name of a previously configured Session Set.
LNKSET
Link set
None
Linkset to which this link belongs. Enter the MML name of a previously
defined linkset.
SLC
Link code
SS7 Signaling link code. Value range: 0 through 15.
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.
Description
Planning F-Links through Cisco ITP-Ls

you configure F-links, you must configure one of these links for every Cisco ITP-L. Within the MGC
node, the ends of each link are identified from the Cisco ITP-L to the specific DPC.
OL-1110-23
2-33
Chapter 2
Planning Media Gateway Control Links
Planning F-Links to Signaling Points

you configure F-links, you must configure one of these links for every PTI card. Within the MGC node,
the ends of each link are identified from the Cisco PGW 2200 Softswitch to the specific DPC.
Planning PRI Backhaul Links

you configure PRI backhaul links, you must configure one of these links for every Ethernet card to the
media gateway (MGW). Within the MGC node, the ends of each link are identified from the
Cisco PGW 2200 Softswitch to the MGW.

The MGW control links provide the communication path the Cisco PGW 2200 Softswitch uses to
control the bearer traffic that passes through each MGW. Planning MGW control links is similar to
planning the other components described earlier in this chapter.
The cards and interfaces are configured in the same way as the cards and interfaces used for SS7
signaling links. In fact, you might be able to use the same cards and interfaces previously planned for
your MGW control links. You must define IP link components for MGW communications; you cannot
use C7 IP links or TDM links.
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
Cisco PGW 2200 Softswitch cards
Cisco PGW 2200 Softswitch interfaces
Media gateway signaling services
Override properties (if necessary)
IP links
The following sections describe how to plan for each of these components.

An external node is another device, such as a media gateway, with which the
Cisco PGW 2200 Softswitch communicates. Within the Cisco MGC software, an external node is a
system component that describes another device. The Cisco PGW 2200 Softswitch can connect to a
maximum of 1,000 media gateways, and you must configure an external node for each MGW.
2-34
OL-1110-23
Chapter 2

To provision media gateway external nodes, use the following component:
Note
VSPT name: ExtNode
MML name: EXTNODE
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
External Node Configuration Parameter Descriptions
MML Parameter
Name
Voice
Services
Provisioning
Tool
Parameter
Name
Default Value
Description
NAME
MML name
None
Unique name for an external device. Enter as many as 20 alphanumeric

DESC
Description
None
Text description of an external device. Enter as many as 128 characters

and enclose in straight quotes.
OL-1110-23
2-35
Chapter 2
Table 2-13
External Node Configuration Parameter Descriptions (continued)
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
AS5200IPFASNAS
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
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
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
Planning for the Media Gateway Signaling Service

A media gateway signaling service must be defined for each media gateway. As shown in Table 2-15,
each media gateway signaling service defines the parent media gateway external node and assigns a
media gateway ID to that device. Table B-17 provides space to plan a single media gateway signaling
service.
To provision a media gateway signaling service, use the following component:
VSPT name: Multiple IPFAS
MML name: MLTIPFAS
VSPT name: SigNAS
MML name: NASPATH
VSPT name: SigEISUP
MML name: EISUPPATH
VSPT name: SigIPFAS
MML name: IPFASPath
VSPT name: TCAPOverIP
MML name: TCAPIPPATH
2-38
OL-1110-23
Chapter 2

Table 2-15
Media Gateway Signaling Service Configuration Parameter Descriptions
Voice Services
Provisioning
MML Parameter Tool Parameter
Name
Default Value
Name
Description
NAME
MML name
None

be used. The name should begin with a letter character.
MDO
MDO file name None
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
Customer Group ID. Virtual network identification characters (formerly

called the VNET ID). Values accepted for this field depend on the use of
the D-channel. Enter the four-digit ID. (Used only for IP FAS transport
service.)
CUSTGRPTBL Customer
group table
0101
Customer Group table. This is a four-digit index used in the Customer

Group table.
ABFLAG
A/B flag
A/B flag. Specifies digital private network signaling system (DPNSS) a

or b side. Enter A for a side, B for b side, or N for not applicable. (Used
only for IP FAS transport service.)
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
Number of IPFAS paths.
SESSIONSET
Session set
MML name of a previously configured 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
Signal port skip. Number of SIGPORT values t be skipped before using

the next port value. (Used only for NFAS signaling service.) Value
range: 0 through 167.
BACKUP
Backup
NO
Backup D-channel. Indicates whether or not to create a backup

D-channel. (Used only for IPNFAS.) Values: YES or 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.
OL-1110-23
2-39
Chapter 2
Planning Network Cards for Media Gateway Communications

Network cards are the hardware cards installed on the host computer providing the network interfaces
that communicate with other devices. When planning media gateway control links, you define the cards
that will communicate with the media gateways.
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
Note
CARD is not supported in software Release 9.4(1).

To provision cards, use the following component:
VSPT name: Adapter
MML name: CARD
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
Card Configuration Parameter Descriptions for Media Gateway Communications
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
Unique name for this component. Enter as many as 20 alphanumeric

SLOT
Slot
None
Location of card or adapter within the host machine. Acceptable values

depend on the host machine. The first slot is usually 0.
TYPE
Type
None
Type of card or adapter. Acceptable value is:
Description
DESC
Description
None
EN
Description of this component. Enter as many as 128 characters and

Planning Ethernet Interfaces for Media Gateway Communications

Each SS7 link in the MGC node must be associated with an Ethernet interface component, which must
be associated with a network card. The Ethernet interface represents a physical network connection on
the network card.
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.
2-40
OL-1110-23
Chapter 2

To provision an Ethernet interface, use the following component:
Note
VSPT name: EnetIF
MML name: ENETIF

Table 2-17 describes the configuration parameters that define an Ethernet interface. Table B-2 serves as
a form you can use to plan the Ethernet interfaces on your Cisco PGW 2200 Softswitch.
Table 2-17
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
Unique name for this interface. Enter as many as 20 alphanumeric

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
Text description of this interface. Enter as many as 128 characters and

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.
To provision a media gateway IP link, use the following component:
VSPT name: IPLink
MML name: IPLNK
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
IP-Link Configuration Parameter Descriptions
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None

DESC
Description
None
Text description of this link. Enter as many as 128 characters and

Description
OL-1110-23
2-41
Chapter 2
Table 2-18
IP-Link Configuration Parameter Descriptions (continued)
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
Priority. Enter an integer that is greater than 0.
PEERADDR
Peer address
0.0.0.0
Remote IP address of link interface on media gateway.
PEERPORT
Peer port
Port number of link interface on remote device.

Enter any valid IP port number greater than 1024. (For MGCP and
SGCP, the recommended setting is 2427.)
IPADDR
IP address
None
Cisco PGW 2200 Softswitch IP address for interface. Enter the IP

address variable defined in the XECfgParm.dat file during the
installation of the Cisco PGW 2200 Softswitch. Valid entries are:
IP_Addr1, IP_Addr2, IP_Addr3, or IP_Addr4.
SVC
IP signaling
Services
None
Signaling service this IP link supports. Enter the MML name of a

previously defined signal service.
NEXTHOP
Next hop
0.0.0.0
Router IP address where packets are to be sent for delivery to the

PEERADDR that is not a subnet directly connected to the
Cisco PGW 2200 Softswitch. Typically the PEERADDR is on a subnet
directly connected to the Cisco PGW 2200 Softswitch. NEXTHOP can
be specified in dot notation or using the DNS name. Optional parameter.
Value range: 0.0.0.0 (default, disables the IP routing feature) through
223.255.255.255.
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.
2-42
OL-1110-23
Chapter 2

Planning Backhaul TCP Link

The Backhaul TCP link component represents a static IP route. Its MML name is as follows:
MML NameTCPLINK
The Backhaul TCP link component structure is shown in Table 2-19.

Table 2-19
TCPLINK Component Structure
Parameter MML
Name
Parameter Description
Parameter Value (Default)
NAME
Unique component
name used in MML
commands
The name can be as many as 20 alphanumeric

characters. No special characters other than - are
allowed. The name should begin with a letter.
DESC
The description can be up to 128 characters.
TYPE
Signaling service type
Identifies the type of signaling service associated

with this link. Must be set to BRI.
IPADDR
Local IP address
PORT
Port number
1024 through 65535; (2428).
PEERADDR
Highest priority
destination address
IP address in dotted decimal notation.
PEERPORT
Destination port number 1024 through 65535; (2428).
EXTNODE
MML name for

MML name of a previously provisioned Cisco BRI
associated external node voice gateway.
IPROUTE
MML name for first IP

route (optional)
MML name of a previously provisioned IP route.
The following attributes cannot be modified:
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
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.
Planning QSIG/Q.931 Over BRI Backhaul Signaling Service

The QSIG/Q.931 Over BRI Backhaul signaling service component represents a static IP route. Its MML
name is as follows:
MML NameBRIPATH
The QSIG/Q.931 Over BRI Backhaul signaling service component structure is shown in Table 2-20.
Table 2-20
BRIPATH Component Structure
Parameter MML
Name
NAME
Unique component
name used in MML
commands

DESC
EXTNODE
MML name of external

node
MML name of a previously provisioned

QSIG/Q.931 BRI voice gateway external node.
MDO
MDO file name
A valid protocol name. You can use the following

files:
ETS_300_102
Q931
ETS_300_172
SIDE
Q.931 call model side
User for user side and network for network side;

(network).
CUSTGRPID
VNET ID
Four digit ID; (0000).
CRLEN
Call reference length
1 for 1-byte or 2 for 2-byte call reference length;

(0).
Note
If you are using the ETS_300_102 or

Q931 protocol files, this should be set to
1. If you are using the ETS_300_172
protocol file, this should be set to 2.
NAME
EXTNODE
The following rules apply when you are creating or editing QSIG/Q.931 Over BRI Backhaul signaling
services:
2-44
OL-1110-23
Chapter 2

A maximum of 2000 BRIPATHs can be provisioned on your Cisco PGW 2200 Softswitch.
Planning Session Sets

The session set component is used for ISDN and SS7 backhaul over RUDP links. A session set 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. You must identify each link in the session set as
follows:
At the Cisco PGW 2200 Softswitch end of each link, the link is associated with a port, an IP address,
and a peer address.
To provision a session set, use the following component:
VSPT name: Session Set
MML name: SESSIONSET
Keep the following points in mind when provisioning session sets.
The PEERPORT and PEERADDRESS must be unique for each backhaul IP link created.
IPADDR1 and IPADDR2 must be different.
Once a session set is created, it cannot be separated.
A maximum of 50 IPFAS session sets are supported per port.

NAME
EXTNODE
TYPE
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 ISDNSIGTYPE of the EXTNODE must be N/A.
The session set TYPE must be BSMV0 for C7 session sets.
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.
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
Session Set Parameter Descriptions
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
Unique name for this link. Enter as many as 20 alphanumeric

IPADDR1
IP address 1
None
Local logical IP address for interface. Enter the IP address variable

defined in the XECfgParm.dat file during the installation of the
Cisco PGW 2200 Softswitch. Valid entries are: IP_Addr1, IP_Addr2,
IP_Addr3, or IP_Addr4.
IPADDR2
IP address 2
None
Local logical IP address for interface. Enter the IP address variable

defined in the XECfgParm.dat file during the installation of the
Cisco PGW 2200 Softswitch. Valid entries are: IP_Addr1, IP_Addr2,
IP_Addr3, or IP_Addr4.
PORT
Port
None
Local port number of link interface on the

Cisco PGW 2200 Softswitch. Enter any valid IP port number from
1025 through 65535.
PEERADDR1
Peer address 1
0.0.0.0
PEERADDR2
Peer address 2
0.0.0.0
PEERPORT
Peer port
Port number of link interface on remote device.

Enter any valid IP port number greater than 1024. For MGCP and
SGCP, 2427 is recommended.
Description
2-46
OL-1110-23
Chapter 2

Table 2-21
Session Set Parameter Descriptions (continued)
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
EXTNODE
External node
None
External node. The MML name of a previously configured external

node.
NEXTHOP1
Next hop 1
0.0.0.0
IP address or host name of the next hop.
NETMASK1
Net mask
255.255.255.255 Subnet mask address
NEXTHOP2
Next hop 2
0.0.0.0
NETMASK2
Net mask 2
255.255.255.255 Subnet mask address
TYPE
Type
Description
IP address or host name of the next hop

Type indicator. The value is either BSMV0 or IPFAS.
Planning for D-Channels

A D-channel is the signaling channel between the Cisco PGW 2200 Softswitch and an external node.
One D-channel is created for a FAS interface and up to two D-channels for an NFAS interface. The
second D-channel is a backup D-channel to prevent a single point of failure for NFAS. There can be a
maximum of two D-channels per IPFAS. Table 2-15 lists and describes the configuration parameters that
define each D-channel. Table B-31 provides space to plan a D-channel between the
Cisco PGW 2200 Softswitch and a gateway.
To provision a D-channel, use the following component:
MML name: DCHAN
VSPT name: D Channel
Table 2-22
D-Channel Configuration Parameter Descriptions
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None

DESC
Description
None
Text description of this signaling service. Enter as many as 128

PRI
Priority
Priority. Enter an integer that is greater than 0.
SVC
IP signaling
Services
None
Signaling service this IP supports. Enter the MML name of a previously

defined signal service.
SESSIONSET
Session set
None
MML name of a previously configured session set.
TCPLINK
TCP Link
None
MML name of a previously provisioned TCP link. This parameter is

used only for D-channels associated with QSIG/Q.931 Over BRI
Backhaul signaling services.
Description
OL-1110-23
2-47
Chapter 2
Table 2-22
D-Channel Configuration Parameter Descriptions (continued)
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
Set this parameter to 0 for ISDN BRI D-channels when the

associated external node is a C17xx.
The SIGPORT value for the backup D-channel will be one

greater than the primary D-channel value.
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
Required for QSIG/Q.931 Over BRI Backhaul D-channels.
Note
Use 99 only for onboard 2-tuple T1/E1 controller on

NM-HDV2-1T1/E1 and NM-HDV2-2T1/E1 and so forth.
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.
Session sets are used only in support of IPFAS D-channels.
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.
Planning for NOA Line Translation

Configurable NOA mapping is supported in Cisco PGW 2200 Softswitch software Release 9.4(1) and
allows you to translate an external NOA value to any internal NOA value for inbound or outbound calls.
Table 2-23 lists and describes the configuration parameters that define the NOA line translation
capability.
To provision the line translation capability, use the following component:
MML name: LINEXLATE
VSPT name: Line Translate
2-48
OL-1110-23
Chapter 2

Table 2-23
MML
Parameter
Name
NOA Provisioning Parameters
Parameter Values (Default)
NAME
Unique ID of this component and The name can be up to any 20 alphanumeric

component name used in MML characters. No special characters other than
commands
- are allowed. The name should begin with
an alphabetic character.
DESC
The description can be as many as 128

characters.
SVC
Signal path MML name.
MML name of previously defined signal

service.
PARAMETER
This indicates the parameter or

field in the protocol message to
which this entry refers.
Currently NOA is the only parameter

supported.
DIRECTION
1 = NOA
Direction in which the message 0 = in

is going, either into or out of the 1 = out
Note
This is not ingress or

egress.
NUMBER
A number representing a specific 0 = called

number type in the protocol
1 = calling
message.
2 = original called
3 = redirecting
4 = redirection
5 = generic
INTNOA
Internal NOA value.
EXTNOA
The value of the NOA field in the Any 7-bit value, 0 through 127, no
protocol message.
restrictions.
Any 7-bit value, 0 through 127, no

restrictions.
Provisioning Bearer Capability

Create a bearer capability blacklist for each trunk group. This blacklist is used during route analysis and
route selection to check the bearer capability against the trunk group list. Table 2-24 lists and describes
the configuration parameters that define each bearer capability.
To provision a bearer capability, use the following component:
MML name: BEARERCAP
VSPT name: Bearer Capability
OL-1110-23
2-49
Chapter 2
Provisioning Trunk Groups and Trunks
Table 2-24
Bearer Capability Configuration Parameter Descriptions
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None

DESC
Description
None

BEARERCAP
Bearer
Capability
Name
None
Bearer capability is a string of Transmission Medium Requirement

(TMR) values less than or equal to 96 characters (0 through 9 and
only) that are separated by semicolons.
Description
Provisioning Trunk Groups and Trunks

There are two different methods that can be used to provision trunk groups and trunks. Provisioning can
be performed individually creating each trunk group and trunk by using MML commands. Or
provisioning can be performed by importing a customer-created file.
Provisioning Trunk Groups and Trunks Using MML Commands

Provisioning trunk groups and trunks can be performed using MML commands. Examples of the
provisioning MML commands are contained in this chapter. More extensive MML command examples
are listed in Chapter 5, Adding Components with MML.
When provisioning using MML commands, it is important to realize that the MML commands are used
to add to existing components. Therefore, MML commands are very useful when modifying existing
trunk groups and trunks. However, if you have to create large trunk group or trunk files, importing a file
can greatly speed the provisioning effort.
Provisioning Trunk Groups and Trunks Using an Imported File

Importing a customer-created file is another way to provision trunk groups and trunks. The customer file
can be created using Voice Services Provisioning Tool or a text editor. MML commands cannot be used
to create the customer file. After the file is created, you must import it into the
Cisco PGW 2200 Softswitch. When importing this file, you can use either MML commands or the Voice
Services Provisioning Tool.
When provisioning using an imported customer-created file, it is important to realize that the imported
file overwrites the existing file. For example, if a customer-created trunk group file is imported, the
existing trunk group file is overwritten.
2-50
OL-1110-23
Chapter 2

Provisioning a Nailed Configuration

Adding Nailed Trunks
You need to add trunks for each connection between the MGW and a destination switch. These trunks
can be either nailed or switched. For nailed trunks, the Cisco PGW 2200 Softswitch does not perform
switching of trunks. To create a nailed trunk, you can use an MML command to create a single trunk,
use the Voice Services Provisioning Tool to create a trunk, or use the MML command to import a trunk
file created using a text editor. To add multiple nailed trunks, refer to the Adding Multiple Nailed
Trunks section on page 5-41.
The MML command format used to create one nailed trunk is:
prov-add:nailedtrnk:name="1910",srcsvc="ss7svc1",srctimeslot=101,dstsvc="nassrv1",
dstspan=3,dsttimeslot=1,spansize=1
Table 2-25 lists the nailed trunk MML command parameter definitions and their associated values.
Table 2-25
Nailed Trunk Parameter Descriptions
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:
OL-1110-23
2-51
Chapter 2
TrunkSrcSrc Src DestDestDest

ID cmp-idSpanTime slotcmp-idSpanTime slot
101 00130002ffff6500140001
3
102 00130002ffff66
00140001
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:
GRPROFILE a profile of GR properties for trunk groups
ISUPTMRPROFILE a profile of ISUP timers for signaling service
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
Profile Parameter Descriptions
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
TYPE
Profile Type
Profile type name. Can be either GRPROFILE or ISUPTMRPROFILE.
VARIANT
Variant
Variant name, as many as 20 alphanumeric characters (only used for ISUP timer
profiles), listed in Appendix A, Protocol Variants.
PROPERTYNAME Property Name Unique property name, as many as 20 alphanumeric characters.
Attaching a Trunk Group Profile to a Trunk Group

Trunk group profiles allow property values, listed in Table 2-27, to be overridden for the specified
component.
2-52
OL-1110-23
Chapter 2

Table 2-27
MML Parameter
Name
Trunk Group Profile Property Parameter Descriptions
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
Indicates whether or not to mark the included CgPN as address presentation

restricted. Acceptable values are: 0 (default) to not include, or 1 to include.
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
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.
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.
OL-1110-23
2-53
Chapter 2
Table 2-27
Trunk Group Profile Property Parameter Descriptions (continued)
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
Indicates the default value of Jurisdiction Information Parameter (JIP) to be sent

when jipInclude = yes and no JIP value is present. If value is 0, treated as if no value
is present. Acceptable values are: 0 (default) for no, or 1 for yes.
jipInclude
jipInclude
Indicates whether or not to include the Jurisdiction Information Parameter (JIP) in the
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.
redirCounterInclude redirCounterIn Indicates whether or not to include the Redirect Counter in the IAM. Acceptable
clude
redirInfoInclude
redirInfoInclud Indicates whether or not to include the Redirection Info in the IAM. Acceptable
e
rnInclude
rnInclude
serviceCodeInclude
serviceCodeInc Indicates whether or not to include the Service Code parameter in the IAM.
lude
transReqInclude
transReqInclud Indicates whether or not to include the transaction request parameter in the IAM.
e
unavailProc
unavailProc
Indicates whether or not to include the Redirecting Number in the IAM. Acceptable
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.
2-54
OL-1110-23
Chapter 2

Table 2-28
Profile Parameter Descriptions
MML Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
NAME
Name
PROFILETYPENA Profile Type

ME
Name
Unique name for this profile name. Enter as many as 20 alphanumeric characters and
Unique profile type name, as many as 20 alphanumeric characters.
Configuring Signaling Service Profiles

ISDN User Part (ISUP) timer profile properties allow property values, listed in Appendix A, Profile,
to be overridden for the specified protocol.
When configuring an ISUP timer profile, you can attach a profile to a signaling service, but both the
profile and the signaling service must belong to the same variant (refer to Appendix A, Protocol
Variants for a list of variant names). However, you can create a profile even though the signaling service
does not exist.
The following is an MML command format used to create an ISUP timer profile and attach it to a
signaling service:
prov-add:profile:name=mtp3profile1,type=isuptmrprofile,variant=ISUPV2_FRENCH,T1=140
00,T12=14000,T13=20000,T14=70000,T15=200000,T16=50000,T17=950000,T18=70000,
T19=50000,T2=280000,T20=70000,T21=20000,T22=70000,T23=50000,T24=900,T25=900
,T26=50000,T27=200000,T28=9000,T33=16000,T34=1000,T35=10000,T36=16000,T38=
120000,T5=50000,T6=70000,T7=40000,T8=25000,T9=50000,
prov-add:sigpathprof:name=ss7svc1,isuptmrprofile=mtp3profile1
Note
A profile must be created before a signaling service can be associated with the profile.
Configuring ATM Profiles

When the Cisco PGW 2200 Softswitch is acting as a Call Agent making ATM Voice Connections
between two Gateways, the Cisco PGW 2200 Softswitch must provide the capability to influence the
profile negotiation between the sides. To facilitate ATM profile negotiation, the AtmConnectionType
and GWDefaultATMProfile trunk group property settings are used. These two trunk group properties are
described in the following sections.
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.
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)
Profile Negotiation Levels

This implementation provides the following structure with regard to ATM profile negotiation when the
Cisco PGW 2200 Softswitch is involved.
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).
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
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.
Creating the Trunk Group

Before switched trunk groups and trunks can be created, the following two files need to be created:
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.
Populating a Trunk Group File

After you create a trunk group file, you need to populate that file. Trunk group information is used to
populate the trunkGroup file and spawns information for the Properties file and the SigPath file.
Table 2-29 lists the MML trunk group parameters, the corresponding VSPT names, the parameter
definitions and the associated values.
Table 2-29
Trunk Group Parameter Descriptions
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.
2-58
OL-1110-23
Chapter 2

Table 2-29
Trunk Group Parameter Descriptions (continued)
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Description
TYPE
Type
Identifies the trunk group type. Values:

TDM_GENUsed with SS7 signaling services with switch types not equal to 0, 5, 20, 23,
or 40.
TDM_ISUPUsed with SS7 signaling services with switch types of 0, 20, 23, or 40.
TDM_CASCurrently not supported.
TDM_TUPUsed with SS7 signaling services with switch type of 5.
IPUsed with EISUP signaling service.
ATMUsed with VSI path signaling service.
TDM_DPNSSUsed with DPNSS protocol family signaling services
TDM_ PRIUsed with ISDN PRI protocol family signaling services.
TDM_BTNUPUsed with SS7 signaling services with switch type of 5.
IP_SIPUsed for SIP signaling services at the terminating side.
SIP_INUsed for SIP signaling services at the originating side (only one such trunk group
can be configured on each Cisco PGW 2200 Softswitch node).
CTIUsed 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
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.
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
Trunk Group File Properties Descriptions
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.
OL-1110-23
2-61
Chapter 2
Table 2-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
Description
TYPE
Trunk Type

TDM_GENUsed with SS7 signaling services with switch types not equal to 0, 5,
20, 23, or 40.
TDM_ISUPUsed with SS7 signaling services with switch types of 0, 20, 23, or
40.
TDM_CASCurrently not supported.
TDM_TUPUsed with SS7 signaling services with switch type of 5.
IPUsed with EISUP signaling service.
ATMUsed with VSI path signaling service.
TDM_DPNSSUsed with DPNSS protocol family signaling services
TDM_ PRIUsed with ISDN PRI protocol family signaling services.
TDM_BTNUPUsed with SS7 signaling services with switch type of 5.
IP_SIPUsed for SIP signaling services at the terminating side.
SIP_INUsed for SIP signaling services at the originating side (only one such
trunk group can be configured on each Cisco PGW 2200 Softswitch node).
CTIUsed with CTI signaling services.
5 = BTNUP27 = NET5
22 = NI2
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.
2-62
OL-1110-23
Chapter 2

Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
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 ...
OL-1110-23
2-63
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
Selseq
Select
Sequence
... continued:
LIDL = Least idle (default). The system selects the least idle (most 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 ...).
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).
2-64
OL-1110-23
Chapter 2

Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
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
ISUP transparency disable function. Permits disabling the ISUP transparency

feature for a specified trunk group. Values are: 0 (ISUP transparency enabled), or 1
(ISUP transparency disabled) (default).
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
Carrier screening. Defines whether or not carrier screening and selection is to be

applied on the current call (using the Carrier Translation table). Values are: 0 (do
not apply screening) (default), or 1 (do apply 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).
OL-1110-23
2-65
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
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).
2-66
OL-1110-23
Chapter 2

Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
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),
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),
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
Default Charge Default charge NOA. Values are: 0 (NOTUSED) (default),

Number NOA 1 (CHNOA_ANI_CGSUB_SUB_NUM),
2 (CHNOA_ANI_NOT_AVAIL),
3 (CHNOA_ANI_CGSUB_NAT_NUM),
4 (CHNOA_ANI_CDSUB_SUB_NUM),
5 (CHNOA_ANI_CDSUB_NO_NUM), or
6 (CHNOA_ANI_CDSUB_NAT_NUM)
OL-1110-23
2-67
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
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
Default directory number. This property is needed on the Trunk Group if it is a

switched call and on the SigPath if it is a nailed call. Values are: 1 to 14 digits or
NULL. Default = 0.
2-68
OL-1110-23
Chapter 2

Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
DefaultDNNOA
Default
Directory
Number NOA
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),
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
OL-1110-23
2-69
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
DefaultDNNPI
Default
Directory
Number NPI
Default directory number NPI. Values are: 0 (NOTUSED) (default),

1 (NPI_NONE),
2 (NPI_E164),
3 (NPI_DATA),
4 (NPI_TELEX),
5 (NPI_PNP),
6 (NPI_NATIONAL),
7 (NPI_TELEPHONY),
DefaultDNPresI
Default
Directory
Presentation
Indicator
Default directory presentation indicator. Values are: 0 (NOTUSED) (default),
Default
Directory
Screening
Indicator
Default directory screening indicator (SI). Values are: 0 (NOTUSED) (default),
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 SIP Port
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
2-70
OL-1110-23
Chapter 2

Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
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
Retry after timer. Indicates the time (in milliseconds) the

Cisco PGW 2200 Softswitch waits before successfully retrying a SIP call. Value
range: any value greater than 0. Default: 90000.
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
Failure to configure this property correctly may result in calls terminating

in the H.323 network failing to have ring back tones applied.
OL-1110-23
2-71
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
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
Wait for originating SDP timer. On H.323 originated calls, the

Cisco PGW 2200 Softswitch transits the answer message and starts this timer when
the originating SDP information has not been received. Value range: 0 to 50 (in
seconds).
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
Cgpn Pres Res
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.
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.
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.
2-72
OL-1110-23
Chapter 2

Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
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
Ta3TimePeriod
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
Expiry warning tone duration, in seconds. Value range: 1 through 5. Default: 1
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
H.323 adjunct link. Indicates if an EISUP link is connected to an H323 adjunct

platform. This allows using the generic mechanism for COT handling when the
terminating side does not support COT. Valid Values: 0 (EISUP link is not
connected to an H.323 adjunct platform) or 1 (EISUP link is connected to an H.323
adjunct platform). Default: 0
Note
Removed from trunk group properties and added to SigPath properties in

software Release 9.4(1), but will retain the default value in the export trunk
group file.
OL-1110-23
2-73
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
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
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
Option 2 is added in software Release 9.7(3) and later.
MinEventSubscribeD
uration
Min Event
Subscribe
Duration
Minimum event subscribe duration. Defines the minimum duration (in

milliseconds) for which a telephony event can be subscribed. Value range: 40
through 3600.
Default: 40
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
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
populateSDPInfoIn
CDR
Populate SDP
Info In CDR
Populate SDP Information In the CDR. Enables or disables the extraction of

information from Session Description Protocol (SDP). Extracted SDP information
is populated in call detail records (CDRs). Values: 0 (disabled) or 1 (enabled).
Default: 0
2-74
OL-1110-23
Chapter 2

Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
Anumnormalise
A Number
Normalise
Anumnormalise indicates that A-number (CgPn) normalization is appropriate based

on the NOA value and the leading digits of the A-number. Leading digits 0 or 00
are the only accepted digits. Valid values: 0 (disabled) or 1 (enabled),
Default: 0
When this property is provisioned, any normalization action is applied to the
Calling Party number and the following numbers, if present (stored internally):
GN_AcgPnGeneric number parameter containing additional Calling Party

number
Redirecting Number (all if more than one)
OCNOriginal Called Number
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
Bnumnormalise indicates that B-number (CdPn) 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 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.
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
OL-1110-23
2-75
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
IsupTransEarlyBackw ISUP
ardDisabled
Transparency
Early
Backward
Disabled
Indicates if the egress Cisco PGW 2200 Softswitch is to send an end-to-end

message, called Early Backward Call Setup Message, immediately after receiving
the call setup message with GTD information about the outgoing protocol variant.
Valid values: 0 (enable) or 1 (disable).
sipMimeBodySupport SIP Mime

Body Support
Determines if SIP-T or SIP-GTD special data processing is supported on a trunk

group. Valid Values: 0None, 1SIP-T supported, or 2SIP-GTD supported.
Default: 1
Default Value: 0
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
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
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
2-76
OL-1110-23
Chapter 2

Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
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),
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
OL-1110-23
2-77
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
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),
Default Value: 0
DefaultPNPres
Default PN
Pres
Displays the Default Presentation Number Presentation Indicator value. Valid

values: 0 through 4.
0 (NOTUSED) (default),
2 (PRES_ALLOWED),
4 (PRES_UNAVAIL)
Default Value: 0
CallForwardRerouteD Call Forward

isabled
Reroute
Disabled
Disables Call Forwarding rerouting for all calls on the

Cisco PGW 2200 Softswitch. Valid values: 0 (reroute enabled) or 1 (reroute
disabled).
Default Value: 0
2-78
OL-1110-23
Chapter 2

Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
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.)
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.)
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
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.)
5 (Sets to indicate that the attempted feature will be removed from the onward
routed call, and the indicator is informed of this.)
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)
OL-1110-23
2-79
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
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
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.
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
AtmConnectionType
Atm.
Connection
Type
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).
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.
2-80
OL-1110-23
Chapter 2

Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
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
LoopAvoidanceCount Loop
er
Avoidance
Counter
Enables the support of the loop avoidance feature in DPNSS protocol. Valid values:
0 through 25.
Default value: 0
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.

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

InhibitIncomingCallin Inhibit
gNameDisplay
Incoming
Calling Name
Display
Enables or disables inhibit incoming calling name display in DPNSS and EISUP
(HSI) protocols. Valid values: 0 (enable) or 1 (disable).
Default value: 0
InhibitOutgoingCallin Inhibit
gNameDisplay
Outgoing
Calling Name
Display
Enables or disables inhibit outgoing calling name display in DPNSS and EISUP
Default value: 0
InhibitIncomingConn
ectedNameDisplay
Inhibit
Incoming
Connected
Name Display
Enables or disables inhibit incoming connected name display in DPNSS and EISUP
Default value: 0
OL-1110-23
2-81
Chapter 2
Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
InhibitIncomingConn
ectedNumberDisplay
Inhibit
Incoming
Connected
Number
Display
Enables or disables the support of incoming connected number display in DPNSS

and EISUP (HSI) protocols. Valid values: 1 (inhibit incoming connected number
display) or 0 (enable incoming connected number display).
Default value: 0
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
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
InhibitOutgoingConn
ectedNameDisplay
Inhibit
Outgoing
Connected
Name Display
Enables or disables inhibit outgoing connected name display in DPNSS and EISUP
Default value: 0
InhibitOutgoingConn
ectedNumberDisplay
AOCInvokeType
Inhibit
Outgoing
Connected
Number
Display
Enables or disables inhibit outgoing connected number display in DPNSS and

EISUP (HSI) protocols. Valid values: 0 (enable) or 1 (disable).
AOC Invoke
Type
Allows configuration of whether or not the AOC Supplementary services are

applicable on a per call basis or for all calls. Values: 1 (on a per call basis the
default) or 2 (for all calls).
Default value: 0
Default value: 1
AOCDefaultTariffId
AOC Default
Tariff Id
Allows configuration of the default tariff ID to be applied when AOCInvokeType is

configured for all calls (that is, AOCInvokeType = 2). Value range: 1 (default)
through 9999.
Default value: 1
2-82
OL-1110-23
Chapter 2

Table 2-30
Voice Services
Provisioning
Tool Parameter
Description
oLocLabel
Originating
Local Label
Originating call control (OCC) side location label. As many as 20-character

alphanumeric string.
Default value: n/a
This parameter is added in software Release 9.6(1).
tLocLabel
Terminating
Local Label
Terminating call control (TCC) side location label. As many as 20-character

alphanumeric string.
Default value: n/a
This parameter is added in software Release 9.6(1).
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
Specifies whether to inhibit pass-on of unrecognized messages/parameters. Values

are:
0 = pass on unrecognized messages/parameters (allow pass-on)
1 = do not pass on unrecognized messages/parameters (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
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
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)
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)
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
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,
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)
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,
CustomerVPNOffNetTblNum, FeatureTransparencyDisabled, SdpXmitToH323Trigger,
GWDefaultATMProfile, PlayAnnouncement, AtmConnectionType, BTechPrefix,
LoopAvoidanceSupport, LoopAvoidanceCounter, MwiStringOFF, MwiStringON,
InhibitIncomingCallingNameDisplay, InhibitOutgoingCallingNameDisplay,
InhibitIncomingConnectedNameDisplay, InhibitIncomingConnectedNumberDisplay,
OL-1110-23
2-85
Chapter 2
AOCDefaultTariffId, AOCInvokeType, MidCallCPInterval, CliSelectionForCodeOfPractice3,

InhibitOutgoingConnectedNameDisplay, InhibitOutgoingConnectedNumberDisplay, oLocLabel,
tLocLabel
The following are examples of a trunk group file #format3 text formats:
#format3 9.4001
1000
1 1111 0 ABC 0 0 0 703 0 0 301 0 0 0 0
600000 300000 600000 30000 FALSE 90000
NULL 20 30 3 NULL 1 CLI NULL 0 0 0 0 0
0 0
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
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
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
Populating a Trunk File

After you have finished creating a trunk file, you need to populate that file. Trunk information is used to
populate the trunk file. Create a trunk row entry in the trunk file using a text editor. Then use the MML
command to import the trunk file (trunkCust.txt).
Table 2-31 lists the trunk MML parameter definitions and their associated values.
Table 2-31
Trunk Parameter Descriptions
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
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).
2-86
OL-1110-23
Chapter 2

Route Analysis
Table 2-31
Trunk Parameter Descriptions (continued)
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
SPANSIZE
Span size
Span size. Indicates the number of trunks per span.

Value: 1 through 24 for T1, or 1 through 31 for E1.
The following is an example of a trunk file text format:

#format3
1910 191001
1910 191002
1910 191003
1910 191004
1910 191005
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.
Creating a Routing Trunk Group

You need to create a routing trunk group. You can use either the MML command to create a routing trunk
group or use the Voice Services Provisioning Tool to import a routing file.
Provisioning a Routing Trunk Group Using MML Commands

Provisioning routing trunk groups can be performed using MML commands. Examples of the
provisioning MML commands are contained in this chapter. More extensive MML command examples
are listed in Chapter 5, Adding Components with MML.
The MML command format used to create a row in the routing trunk group file is:
prov-add:rttrnkgrp:name="1910",type=7,reattempts=1,queuing=0,cutthrough=2
Table 2-32 lists the routing trunk group MML command parameter definitions and their associated
values.
OL-1110-23
2-87
Chapter 2
Route Analysis
Table 2-32
Routing Trunk Group Parameter Descriptions
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
TYPE
Type
Identifies the trunk group type. Value range: 0 through 11.

0 = TDM_GEN (default)Used with SS7 signaling services with switch types not
equal to 0, 5, 20, 23, or 40.
1 = TDM_ISUPUsed with SS7 signaling services with switch types of 0, 5, 20, 23,
or 40.
2 = TDM_CASCurrently not supported.
3 = TDM_TUPUsed with SS7 signaling services with switch type of 5.
4 = IPUsed with EISUP signaling service.
5 = ATMUsed with VSI path signaling service.
6 = TDM_DPNSSUsed with DPNSS protocol family signaling services.
7 =TDM_ PRIUsed with ISDN PRI protocol family signaling services.
8 = TDM_BTNUPUsed with SS7 signaling services with switch type of 5.
9 = IP_SIPUsed for SIP signaling services at the terminating side.
10 = SIP_INUsed for SIP signaling services at the originating side
11 = CTIUsed for CTI signaling.
5 = BTNUP27 = NET5
22 = NI2
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.
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
2-88
OL-1110-23
Chapter 2

Route Analysis
Table 2-32
Routing Trunk Group Parameter Descriptions
Voice Services
Provisioning
Tool Parameter
Name
Description
MML Parameter
Name
RESINCPERC
Reserve
Incoming
Percentage
Identifies the percentage of bandwidth for incoming calls. It defaults to 0 if

ResIncomingPerc is not defined. Value range 0 (default) through 100.
BEARERCAPNA
ME
Bearer
Capability
Name
Unique name for this bearer capability (NULL). Enter as many as 20 alphanumeric
Associating a Route with a Trunk Group

You need to create a route to connect to a trunk group. You can use either the MML commands to
associate a route with a trunk group or use the Voice Services Provisioning Tool to import a routing file.
The MML command format used to create a row in the route trunk file is:
prov-add:rttrnk:name="rt1910",trnkgrpnum=501910
Table 2-33 lists the route trunk MML command parameter definitions.
Table 2-33
Route Trunk Parameter Descriptions
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
TRNKGRPNUM
Trunk group
number
Identifies the trunk group number.
NEXTTRKGRP
Next trunk
group
Identifies the next trunk group number.
Each line entry in the route trunk file is one entry in the route list file.
Weighted Trunk Group

Weighted trunk group based routing allows the same trunk group to be used multiple times in the same
route when the random distribution algorithm is enabled. The user has the option of setting the
distribution indicator on the route entry to determine how the trunk groups are selected in each route. If
the distrib parameter is OFF then sequential selection is used to choose the trunk groups in that route. If
the distrib parameter is ON then random selection is used, this is useful if there is a need to balance the
choice of trunk groups across the connected equipment. This required an extra parameter to be added at
the rttrnk level to specify if weighted trunk group base routing is enabled. If weighted trunk group based
routing is enabled or disabled at the route trunk level, then the following rules must be observed:
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.
Limit the number of route trunk group in an route trunk to 100.
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: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.
Creating a Route List

After you have finished creating a route trunk, you need to create a route list. You can use either the
MML command to create a route list, use the Voice Services Provisioning Tool, or import a routing file.
The MML command format used to create the route list is:
prov-add:rtlist:name="rtlist1910",rtname="rt1910",carrierid=333
Table 2-34 lists the route list MML command parameter definitions and their associated values.
2-90
OL-1110-23
Chapter 2

Table 2-34
Route List Parameter Descriptions
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
RTNAME
Route name
Used to look up the source service component ID.
NEXTRTNAME
Next route name.
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.
An MML Example for Creating a Routing File

The following MML commands provide a sample routing file.
prov-add:rtlist:name="rtlist1910",rtname="rt1910"

To pass calls between the Cisco PGW 2200 Softswitch and a Session Initiation Protocol (SIP) domain,
configure the following SIP parameters using MML commands:
SIP signal path
SIP link
SIP trunk group
Domain Name System
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.
OL-1110-23
2-91
Chapter 2
Table 2-35
SIP Routing Trunk Group Parameters
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
URL
SIP URL
SIP proxy service address in the format of IP address, host name, or DNS name.
PORTNUM
Port number
UDP port number used by the SIP proxy server.
VERSION
SIP version
SIP version of the SIP proxy server.
CUTTHROUGH
Cut through
Cut through. Value range: 0 through 3 (default).

0 = Undefined
2 = ACM
3 = Answer
EXTSUPPORT
Extension
support
SIP extension supported. Value range: 0 (default) or 1.

Note
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
2-92
OL-1110-23
CH A P T E R
Provisioning with the Cisco Voice Services

Provisioning Tool
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.
Installing Cisco VSPT

If you are a registered Cisco.com user, you can download the 2.6(1) and previous Cisco VSPT software
from the Cisco website. For VSPT 2.7(3) and higher, VSPT is included with the licensed Cisco MGC
Node Manager.
Refer to the Cisco Voice Services Provisioning Tool Users Guide for information on obtaining,
installing, and operating the Cisco VSPT software.
OL-1110-23
3-1
Chapter 3

If your network contains a Cisco ITP-L, ensure that the following components are provisioned:
T1 or E1 line
IP address
IP route
Signaling System 7 (SS7) session address
ITU protocol variant
Manual Provisioning with Cisco VSPT

Provisioning a Cisco MGC is a complex process that can be logically divided into the following steps
for all solutions:
Configuring the MGC
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
Configuring bearer traffic
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
Configuring the MGC, page 3-2
Configuring Signaling Services, page 3-7
Configuring Cisco MGW Control Links, page 3-53
Configuring Bearer Traffic, page 3-97
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.
Configuring the MGC

To provision an MGC, configure the following basic network elements:
Active MGC host
Standby MGC host, if applicable
3-2
OL-1110-23
Chapter 3

Configuring the MGC
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
Adding a Cisco PGW 2200 Softswitch Host

The MGC host is a Sun workstation that runs the MGC software. Table 3-1 lists the MGC host
properties. Use this information to add an MGC host and a standby host if you are configuring a
redundant MGC.
Table 3-1
MGC Properties
Field Name
Description
Default
Valid Values
MGC Hostname
IP address or hostname that identifies the target MGC host
None
User defined
Login / Password
Specifies the valid MGC login and password
None
User defined
Protocol
Specifies the protocol to log into the MGC
SSH
SSH None
(Telnet)
PGW Mode
The MGC switch mode
Depends on
PGW
Switched
Nailed
BAMS Version
Specifies the Cisco BAMS version for configuration
Bams V3
Bams V3
BAMS Config
Gives the name of the Cisco BAMS configuration
<UNSET>
xxxx
IP Addr:1
IP address of the MGC primary interface used for signaling and

control
None
x.x.x.x
IP Addr:2
IP address of a secondary interface used for signaling or control

backup
None
x.x.x.x
IP Addr:3
IP address of a third interface used for signaling or control backup None
x.x.x.x
IP Addr:4
IP address of a fourth interface used for signaling or control backup None
x.x.x.x
Failover
Indicates whether this is a failover configuration
None
No, Yes
Failover IP
Addr:1
IP address of the primary interface for signaling on the standby

MGC (if included)
None
x.x.x.x
Failover IP
Addr:2
IP address of the secondary interface for signaling on the standby

MGC (if included)
None
x.x.x.x
Failover IP
Addr:3
IP address of the third interface for signaling on the standby MGC

(if included)
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.
OL-1110-23
3-3
Chapter 3
Configuring the MGC
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
Enter your log in ID and password to log in VSPT.
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
New Configuration Wizard
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.
3-4
OL-1110-23
Chapter 3

Configuring the MGC
Figure 3-2
Configuration Chooser
Step 6
Make sure MGC Config radio button is selected.
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.
OL-1110-23
3-5
Chapter 3
Configuring the MGC
Figure 3-3
Adding an MGC Host
Step 8
Enter the IP address or hostname of the MGC in the MGCHostname field (for example, 172.16.145.38).
Step 9
Enter a valid MGC login ID and password.
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.
3-6
OL-1110-23
Chapter 3

Configuring Signaling Services
Figure 3-4
MGC Host Added

Signaling services identify all signaling types processed by the MGC. To configure signaling services,
use the steps provided in the sections below.
Adding Point Codes, page 3-8
Adding Routing Keys, page 3-13
Adding Location Labels, page 3-16
Adding Linksets, page 3-17
Adding SS7 Subsystems, page 3-20
Adding ISUP Timer Profiles, page 3-23
Adding an Inservice Subsystem, page 3-24
Configuring SS7 Paths, page 3-27
Configuring SS7 Routes, page 3-30
Configuring IPRoutes, page 3-32
Configuring M3UA Routes, page 3-33
OL-1110-23
3-7
Chapter 3
Configuring SUA Routes, page 3-34
Adding and Changing SS7 Signaling Properties, page 3-35
Adding a Line Number Translation, page 3-36
Adding Session Initiation Protocols, page 3-38
Configuring Automatic Congestion Control, page 3-43
Configuring Advice of Charge, page 3-45
Adding GTD Parameters, page 3-52
Configuring TOS, page 3-53
Adding Point Codes

Every signaling point in the SS7 network is identified by a unique point code. To provision point codes,
use the steps provided in the subsections below.
Note
Adding Origination Point Codes
Adding Adjacent Point Codes
Adding Destination Point Codes
Point codes provide the addressing scheme for the SS7 network. ITU point codes contain 14 bits, and
ANSI point codes contain 24 bits.

An origination point code (OPC) is an SS7 network address assigned to the MGC. You can define up to
six OPCs. To provision an OPC, use the following steps:
Step 1
Click the icon next to Signaling to expand the hierarchical tree.
Step 2
Click Point Codes > OPCs. A window similar to the one shown in Figure 3-5 displays.
3-8
OL-1110-23
Chapter 3

Figure 3-5
Step 3
Enter a name.
Step 4
Enter the description.
Step 5
Enter the network address.
Step 6
In the NetIndicator drop-down menu, select one of the following values:
International networkUsed if the node is an international gateway.
Reserved for international useDo not use.
National networkUsed if the node routes calls through the national network.
Reserved for national useDo not use.
Step 7
Select the OPC type. Choices are TRUEOPC and CAPOPC.

TRUEOPC defines this OPC as a primary (true) OPC within this PGW. CAPOPC defines this OPC as an
point code which have primary (true) OPCs associated to.
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.
OL-1110-23
3-9
Chapter 3

Adjacent point codes (APCs) are the SS7 network addresses of the Signal Transfer Points (STPs) (or
Service Switching Points[SSPs] directly connected to the Cisco ITP-L) that connect to the MGC node.
The MGC node communicates with external SSPs and Service Control Points (SCPs) through an STP.
Table 3-2 lists the APC properties. Use the values in the table as you add APCs to the MGC.
Table 3-2
APC Properties
Property
MML
Parameter
Name
Description
Default
Valid Values
Name
name
Identifies the adjacent point code MML name.
STP-x
Up to 20 alphanumeric
characters
Description
desc
Describes the point code. Use up to 128

alphanumeric characters.
Adjacent
Point
Code
characters
NetAddr
netaddr
Enter the point code in this field. Valid for both

ITU and North American point codes.
0.0.0
User defined
NetIndicator
netind
Identifies the type of node receiving the point

code.
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.
3-10
OL-1110-23
Chapter 3

Figure 3-6
Step 3
Enter the name (for example, STP-1).
Step 4
Enter the description (for example, Adjacent Point Code).
Step 5
Enter the network address in dotted notation (for example, 2.1.2).
Step 6
In the NetIndicator drop-down menu, select one of the following values:
Step 7
International networkUsed if the node is an international gateway.
National networkUsed if the node routes call through the national network.
Click Add. The hierarchical tree changes to reflect the APC added (STP-1).

A destination point code (DPC) is an SS7 network address that identifies an SS7 network node, such as
an STP, SSP, or media gateway with which the MGC node communicates.
Use the following procedure to add the DPCs for the ILEC and CLEC switches:
Step 1
Step 2
Click Point Codes > DPCs. A window similar to the one shown in Figure 3-7 displays.
OL-1110-23
3-11
Chapter 3
Figure 3-7
Step 3
Enter a name.
Step 4
Step 5
Enter the network address in dotted notation (for example, 1.1.2).
Step 6
Select the network numbering scheme type used:
Step 7
Step 8
ANSI
ETSI
In the NetIndicator drop-down menu, select one of the following network indicators:
International networkUsed if the node is an international gateway (default value).
National networkUsed if the node routes calls through the national network.
Click Add. The hierarchical tree changes to reflect the DPC added.
3-12
OL-1110-23
Chapter 3

Adding Routing Keys

To provision routing keys, use the steps provided in the subsections below.
Adding M3UA Routing Keys, page 3-13
Adding SUA Routing Keys, page 3-14
Adding M3UA Routing Keys

The M3UA component represents a routing key. The parent component of the M3UAKEY is OPC.
Table 3-3 provides the structure of the M3UA key component.
Table 3-3
M3UA Key Component Structure
Parameter MML Name
NAME
M3UA key name

characters. No special characters other than "-"
are allowed. The name should begin with a letter.
DESC
Up to 128 characters.
OPC
Associated OPC
MML name of a previously configured OPC.
DPC
Associated DPC (optional)
MML name of a previously configured DPC.
ROUTING CONTEXT
Any integer except 0 (0 indicates no routing

context). Each M3UA key must have a unique
routing context.
SI
Service indicator
Service type, values are ISUP, TUP, and N/A

(N/A).
NETWORK APPEARNCE
This parameter is optional. The valid values are

integers from 1 through 32767. A value of 0
indicates an invalid network appearance.)
The following rules apply when you are creating M3UA keys:
You can provision a maximum of 1536 M3UA keys.
Up to 64 OPCs can use M3UA signaling services.
Parent OPC must be a true OPC.
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.
To provision an M3UA routing key, use the following steps:

Step 1
Step 2
Click Routing Keys > M3UAs. A window similar to the one shown in Figure 3-8 displays.
OL-1110-23
3-13
Chapter 3
Figure 3-8
Adding M3UA Routing Keys
Step 3
Enter a name.
Step 4
Step 5
In the Orig. Point Code drop-down menu, select TRUEOPC.
Step 6
In the Dest. Point Code drop-down menu, select the DPC. This parameter is optional.
Step 7
Enter the Routing Context (for example, 0-2147483647).
Step 8
Select the Service Indicator. Choices are ISUP, N/A, and TUP.
Step 9
Enter the Network Appearance (for example, 0-32767).
Step 10
Click Add. The hierarchical tree changes to reflect the M3UA routing keys added.
Adding SUA Routing Keys

To provision an OPC, use the following steps:
Step 1
Step 2
Click Routing Keys > SUAs. A window similar to the one shown in Figure 3-9 displays.
3-14
OL-1110-23
Chapter 3

Figure 3-9
Adding SUA Routing Keys
Step 3
Enter a name.
Step 4
Step 5
In the Orig. Point Code drop-down menu, select TRUEOPC.
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.
OL-1110-23
3-15
Chapter 3
Adding Location Labels

The location label concept is used in the Call Limiting feature. It is associated with one or more sources
and destinations, so calls can be limited to or from one or more interfaces. As many as four location
labels can be applied to a call, with two location labels on the inbound call leg and two location labels
on the outbound call leg. The location label has a call threshold limit that can be set. If the call threshold
for a location is exceeded, all other calls to or from that location are rejected.
To provision a Location Label, use the following steps:
Step 1
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.
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 an adjacent STP (APC)
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
Identifies the linkset MML name
Lnkset-x
Up to 20
alphanumeric
characters
Description desc
Describes the linkset
Lnkset
Up to 128
alphanumeric
characters
Point Code
apc
Identifies the APC components for the SS7 node

providing the linkset
<UNSET> User defined
Protocol
proto
Identifies the protocol family associated with this

linkset
SS7-ANSI SS7-ANSI
SS7-China
SS7-ITU
SS7-Japan
SS7-UK
Type
type
Link Set 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
OL-1110-23
3-17
Chapter 3
Figure 3-11
Adding Linksets
Step 2
Enter a name (for example, Linkset-1).
Step 3
Enter the description (for example, Linkset).
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
In the Protocol drop-down menu, select one of the following protocols:
SS7-ANSI
SS7-China
SS7-ITU
SS7-Japan
SS7-UK
Step 6
Select the Type. Choices are IP and TDM.
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.
3-18
OL-1110-23
Chapter 3

Adding and Changing Linkset Properties

You can add and change the properties of a linkset after it is created, including message and timer values.
Changes apply to all linksets you create. You do not have to change the default properties.
Perform the following steps to add or change linkset properties:
Step 1
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
Adding and Changing Linkset Properties
Step 3
In the Value drop-down menu, select a property and enter a value.
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
Linkset Property Added
Step 5
To modify an existing property, click the property you want to change.
Step 6
In the value field, enter the new property value.
OL-1110-23
3-19
Chapter 3
Step 7
Click Modify.
Step 8
Click OK when you are finished modifying properties.
Note
You cannot modify properties until you have created the linkset.
Adding SS7 Subsystems

An SS7 subsystem allows the MGC to route traffic over the C-links between mated STPs to increase
network reliability. The links to these STPs are defined in the Adding Routing Keys section on
page 3-13.
The SS7 subsystem provides local number portability (LNP) support through an SCP. Because the SS7
subsystem is an instance of an application, you need to configure a subsystem for each application type
of service (for example, LNP). The SS7 subsystem is also used to connect an STP to an SCP database
for advanced intelligent network (AIN) queries. In this case, there is no mated STP.
Table 3-5 lists SS7 subsystem properties. Use the values in the table as you add SS7 subsystems to your
MGC.
Table 3-5
SS7 Subsystem Properties
Property
MML Parameter
Description
Default
Valid Values
Name
name
Identifies the MML name for this SS7 subsystem.
Ss7ss-1
Up to 20
alphanumeric
characters
Description
desc
Describes the subsystem.
SS7 Subsystem
Up to 128
alphanumeric
characters
Identifies the type of subsystem.
None
Mating APCs
AIN Services
Subsystem
Type
TCAPIP or
APC
svc
Identifies the STP (or STP pair) to be used for

TCAP messages.
<UNSET>
User defined
Priority
pri
Identifies the priority value of the route. Used for

load sharing.
1 through 16
Subsystem
number
ssn
Identifies the desired SCP services. The value is

provider specific.
x.x.x.x
STP/SCP Index stpscpind
Identifies each SCP in a virtual switch

configuration.
0 through 99
Transport
Protocol
transproto
Identifies the transport protocol used for TCAP

TCP/IP
messages. Accessing SCPs with SS7 uses the SCCP
protocol.
Protocol
Family
proto
Identifies the protocol family used for SS7

messages.
<UNSET>
SCCP
TCP/IP
SS7-ANSI
SS7-China
SS7-ITU
SS7-Japan
SS7-UK
3-20
OL-1110-23
Chapter 3

To provision SS7 subsystems, use the steps provided in the subsections below.
Adding SS7 Subsystems (Mating APCs)
Adding SS7 Subsystems (AIN Services)

To provision SS7 Subsystems (Mating APCs), use the following steps:
Step 1
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
Select Mating APCs as the Subsystem type.
Step 5
In the OPC drop-down menu, select the OPC.
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
In the Protocol Family drop-down menu, select a protocol family to use.
OL-1110-23
3-21
Chapter 3
Step 9
Click Add. The hierarchical tree changes to reflect the SS7 Subsystems added.

To provision an SS7 Subsystem (AIN Services), use the following steps:
Step 1
Click SS7 Subsystems in the left pane of the main Cisco VSPT window. A window similar to the one
Figure 3-15
Step 2
Enter a name.
Step 3
Step 4
Select AIN Services as the Subsystem type.
Step 5
In the TCAPIP or APC drop-down menu, select the APC.
Step 6
Enter the Priority.
Step 7
Enter the Local SSN.
Step 8
Enter the STP/SCP index.
Step 9
In the Transport Protocol drop-down menu, select SCCP or SUA.
3-22
OL-1110-23
Chapter 3

Step 10
In the Protocol Family drop-down menu, select a protocol family to use.
Step 11
In the OPC drop-down menu, select the OPC.
Step 12
In the SuaKey drop-down menu, select the Suakey.
Step 13
Enter the Remote SSN.
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.
Adding ISUP Timer Profiles

To provision an ISUP Timer Profile, use the following steps:
Step 1
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.
OL-1110-23
3-23
Chapter 3
Figure 3-16
Adding ISUP Timer Profiles
Step 4
Enter a name.
Step 5
In the Variant drop-down menu, select the variant.
Step 6
In the Validation drop-down menu, select ON or OFF.
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
In the Name drop-down menu, select the timer name.
Step 10
Enter the Value.
Step 11
Click Add. The ISUP timer profile properties window changes to reflect the properties added.
Adding an Inservice Subsystem

The structure of the Inservice component is shown in Table 3-6.
3-24
OL-1110-23
Chapter 3

Table 3-6
Intelligent Network Service (INSERVICE)
Parameter MML
Name
Parameter
Description
NAME
Intelligent Network As many as 20 alphanumeric characters.

Service name
SKORTCV
Service key
Integer. 0 through 214783647 (0). Service key value that

specifies the feature that caused the trigger to be hit
(ITU/ETSI INAP only). Otherwise, it is the trigger criteria
value.
GTORSSN
Global title or
subsystem number
Text string. Route by global title (ROUTEBYGT) or route by

subsystem number (ROUTEBYSSN).
0 = ROUTEBYGT (route by global title)

1 = ROUTEBYSSN (subsystem number)
GTFORMAT
Global title format
Text string. How to use Global Title; SCCP Called Party

Address, Address indicator field. User provisions the string
value. For example, NOGT.
0 = NOGT (No global title. Use this when routing by SSN.)
1 = GTTTNBRENC (Use global title translation type
numbering scheme encoding scheme.)
2 = GTTT (Use global title translation type.)
3 = GTONLY (Use global title only.)
4 = UNKNOWN (unknown).
MSNAME
Message Sending
Name
As many as 20 alphanumeric characters.
The following rules are used to support Inservice table provisioning:
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.
The MSNAME must exist in the MessageSendingName table in trigger.dat.
Only one entry can exist in the INSERVICE table for each MSNAME.
To add an Inservice subsystem, use the following steps:

Step 1
Step 2
Click Inservice in the left pane of the main VSPT window. A window similar to the one shown in
OL-1110-23
3-25
Chapter 3
Figure 3-17
Adding an Inservice Subsystem
Step 3
Enter a name.
Step 4
Enter the Service Key.
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
Enter the Message Sending Name.
Step 8
Click Add. The hierarchical tree changes to reflect the Inservice added.
3-26
OL-1110-23
Chapter 3

Configuring SS7 Paths

An SS7 signaling service identifies the path over which the MGC node communicates using a specific
protocol with a remote MGC or switch. The (Man-Machine Language) MML component name is
SS7PATH. Table 3-7 lists the SS7 signaling service properties. Use the values in this table as you add
SS7 paths to your MGC.
Table 3-7
SS7 Signaling Service Properties
Property
MML Parameter
Description
Default
Valid Values
Name
name
Identifies the SS7 service path.
None
characters
Description
desc
Describes the SS7 service path.
None
Up to 128
alphanumeric
characters
Orig. Point
Code
opc
Specifies the orig point code of the SSP in the

service path.
<UNSET>
User defined
Dest. Point
Code
dpc
Specifies the dest point code of the SSP in the

service path.
<UNSET>
User defined
M3UAKey
m3uakey
m3uakey
M3UA Key
None
See the drop-down list

Figure 3-18.
Side
side
Distinguishes the network equipment (like a

switch) from the user equipment (like a
terminal adapter or PBX). (Used for ISDN
systems.)
network
network
user
MDO
mdo
Identifies the protocol (MDO file name) for this ANSISS7_S

SS7 service path. Select the MDO file name
TANDARD
from a drop-down list.
Customer
Group ID
custgrpid
Contains a unique identifier for the number

0000
analysis file. (Used with nailed solutions only.)
0009999; can be up to
4-digit alphanumeric
characters.
ISUP Timer
Profile
sigpathProf->isu
ptmrprofile
ISUP Timer Profile Name
None

Figure 3-18.
Origination
Label
origlabel
Origination Location Label
None

Figure 3-18.
'Termination
Label
termlabel
Termination Location Label
None

Figure 3-18.
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.
OL-1110-23
3-27
Chapter 3
Figure 3-18
Adding SS7 Paths
Step 2
Enter the name of the SS7 signaling path.
Step 3
Enter the description of the SS7 signaling path.
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
Enter the customer group ID.
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.
3-28
OL-1110-23
Chapter 3

Step 13
Click Add. The hierarchical tree changes to reflect the SS7 path added.
Adding and Changing SS7 Properties

You can add and change the properties of a SS7 path after it is created. Changes apply to all SS7 paths
you create. You do not have to change the default properties.
Perform the following steps to add or change SS7 properties:
Step 1
Select the appropriate SS7 path in the left pane of the main Cisco VSPT window.
Step 2
displays.
Figure 3-19
Adding and Changing SS7 Properties
Step 3
To add a property, select it from the Name drop-down menu.
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
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.
Configuring SS7 Routes

An SS7 route is a path through a linkset between the MGC node and another MGC node or a switch. In
Figure 3-21, the SS7 routes indicate the linksets that carry SS7 signals between the MGC node and the
ILEC Class 5 switch or the CLEC Class 5 switch. You must define a separate route for each remote
switch.
Table 3-8 lists the SS7 route properties. Use the values in this table as you add SS7 routes to your MGC.
Table 3-8
SS7 Route Properties
Property
MML Parameter
Description
Default
Valid Values
Name
name
Identifies the MML name for a route set.
Ss7r-1
Up to 20
alphanumeric
characters
Description
desc
Description of the route.
SS7 Route
Up to 128
alphanumeric
characters
Originating PC
opc
Selects the MML name of the MGC point code.
<UNSET>
User defined
Destination PC
dpc
Selects the point code of the destination switch

delivering bearer traffic to the solution.
<UNSET>
User defined
3-30
OL-1110-23
Chapter 3

Table 3-8
SS7 Route Properties (continued)
Property
MML Parameter
Description
Default
Valid Values
Linkset
lnkset
Selects the linkset over which the SS7 signals travel.
<UNSET>
User defined
Priority
pri
Sets the priority value of the route. You can create

1
load sharing by setting all routes to the same number.
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
Figure 3-21
Adding SS7 Routes
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
Enter the priority.
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
Adding IPRoutes
Step 2
Enter a name.
Step 3
Step 4
In the IP Addr drop-down menu, select the IP address of the MGC:
IP Addr1
IP Addr2
IP Addr3
3-32
OL-1110-23
Chapter 3

IP Addr4
Step 5
Enter the Destination Addr.
Step 6
Enter the IP Gateway.
Step 7
Enter the IP Net Mask.
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.
Configuring M3UA Routes

The M3UA routes component is used to set the means for getting an SS7 message to a particular
destination.
The M3UA route component structure is shown in Table 3-9.
Table 3-9
M3UAROUTE Component Structure
Parameter MML
Name
Parameter
Description
NAME
M3UA route name
The name can be as many as 20 alphanumeric characters. No

special characters other than "-" are allowed. The name
should begin with a letter.
DESC
Component
description
Up to 128 characters.
DPC
Associated DPC
EXTNODE
Associated external MML name of a previously configured external node.

node
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.
The associated OPC must be a true OPC.
For a given OPC/DPC, only one route can be defined through a given external node.
Up to two M3UA routes can be defined per OPC-DPC pair.
The associated external node must support M3UA signaling.
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.
Use the following procedure to add M3UA routes to the MGC:
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
Figure 3-23
Adding M3UA Routes
Step 2
Enter a name.
Step 3
Step 4
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
Enter the Priority.
Step 8
Click Add. The hierarchical tree changes to reflect the M3UA route added.
Configuring SUA Routes

Use the following procedure to add SUA routes to the MGC:
Step 1
Click SUA Routes in the left pane of the main Cisco VSPT window. A window similar to the one shown
3-34
OL-1110-23
Chapter 3

Figure 3-24
Adding SUA Routes
Step 2
Enter a name.
Step 3
Step 4
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
Enter the Remote SSN.
Step 8
Click Add. The hierarchical tree changes to reflect the SUA route added.
Adding and Changing SS7 Signaling Properties

You can add and change the properties of a sigpath after it is created. Changes apply to all sigpaths
created. You do not have to change the default properties.
Perform the following steps to add or change sigpath properties:
Step 1
Highlight the appropriate sigpath in the left pane of the main Cisco VSPT window.
Step 2
displays.
OL-1110-23
3-35
Chapter 3
Figure 3-25
Adding and Changing Sigpath Properties
Step 3
To add a property, select a property and enter a value.
Step 4
Click Add. A window similar to the one shown in Figure 3-26 displays with the property added. After a
Figure 3-26
Sigpath Property Added
Step 5
To modify an existing property, select the property you want to change.
Step 6
Step 7
Click Modify.
Step 8
Note
You cannot modify properties until you have created the sigpath.
Adding a Line Number Translation

Line number translation represents a line number and an internal number translation and is dynamically
reconfigurable.
To provision Line Number Translation, use the following steps:
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
Adding a Line Number Translation
Step 3
Enter a name.
Step 4
Step 5
In the SVC drop-down menu, select the configured SS7 Paths.
Step 6
In the Direction drop-down menu, select in or out.
Step 7
In the Number drop-down menu, select one of the following numbers:
Called
Calling
Generic
Original called
Redirecting
Redirection
Step 8
Enter the intNoa (for example, 0127).
Step 9
Enter the extNoa (for example, 0127).
Step 10
Click Add. The hierarchical tree changes to reflect the Line Number Translation added.
OL-1110-23
3-37
Chapter 3
Adding Session Initiation Protocols

The Session Initiation Protocol (SIP) signaling service is the connection between an MGC and a SIP
server. To pass calls between the MGC and a SIP domain, you must configure an SIP signaling service.
Table 3-10 lists the SIP properties.
Table 3-10
SIP Properties
Field Name
Description
Default
Valid Values
Name
Unique ID of this component.
Description
Description of the external node.
None
Up to 128 alphanumeric characters.
MDO
Identifies protocol (MDO file name)

for this SIP signal path. Select the
MDO file name from the drop-down
menu.
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.
To provision SIP, use the steps provided in the subsections below.
Configuring a DNS Parameter, page 3-38
Adding a SIP Signaling Path, page 3-39
Configuring a DNS Parameter

Use the following procedure to configure the DNS parameter:
Step 1
In the left pane of the main Cisco VSPT window, click SIP > DNS. A window similar to the one shown
3-38
OL-1110-23
Chapter 3

Figure 3-28
Configuring a DNS Parameter
Step 2
Enter the DNS 1 IP Addr. IP address of the primary DNS server.
Step 3
Enter the DNS 2 IP Addr. IP address of the secondary DNS server.
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.
Adding a SIP Signaling Path

Use the following procedure to add a SIP Signaling Path:
Step 1
Click SIP in the left pane of the main Cisco VSPT window. A window similar to the one shown in
OL-1110-23
3-39
Chapter 3
Figure 3-29
Adding a SIP Signaling Path
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
In the Originating Label drop-down menu, select the location label.
Step 6
In the Termination Label drop-down menu, select the location label.
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
Adding and Changing SIP Signaling Properties

You can add and change the SIP signaling properties after a SIP signaling path is created. Changes apply
to all linksets created. You do not have to change the default properties.
Perform the following steps to add or change SIP signaling properties:
Step 1
Select the appropriate SIP signaling path in the left pane of the main Cisco VSPT window.
Step 2
displays.
3-40
OL-1110-23
Chapter 3

Figure 3-30
Adding and Changing SIP Signaling Properties
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
SIP Signaling Property Added
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.
Adding a SIP IP Link

Use the following procedure to add a SIP IP link for the SIP signaling path:
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
Adding a SIP IP Link
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
Enter the port (for example, 102565535).
Step 6
Step 7
Click Add. The hierarchical tree changes to reflect the new SIP IP link added.
3-42
OL-1110-23
Chapter 3

Configuring Automatic Congestion Control

Automatic congestion control (ACC) is used to configure call load balancing. Use the following
procedure to configure ACC:
Step 1
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
Enter the ACL name of the ACC response category.
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.
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.
3-44
OL-1110-23
Chapter 3

Figure 3-35
MCL Call Rejection
Step 10
Select the MCL name in the drop-down list.
Step 11
Enter the percentage of calls to reject at this level.
Step 12
Click Add. The hierarchical tree changes to reflect the call reject rate added.
Configuring Advice of Charge

Advice of charge (AOC) is used (typically in the European arena) where licensed operators are required
to provide the capability to inform interconnecting networks of the charge rates applied to calls
traversing the networks. The charge rates are determined by destination, distance, time of day, and day
of year. Additionally, since tariff rates can vary through the length of a day and from day to day, calls
that continue through a tariff rate change must have their charges adjusted accordingly, and the
interconnecting network must be informed of the rate change.
Use the following procedures to configure AOC on the MGC:
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.
OL-1110-23
3-45
Chapter 3
Figure 3-36
Advice of Charge, Holiday
Step 2
Enter a date for the holiday by clicking the name in the drop-down list for the desired month.
Step 3
Click the up or down arrow to select the desired year.
Step 4
Click the day to select the desired day.
Step 5
Click the Holiday drop-down list to select a holiday value.
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
3-46
OL-1110-23
Chapter 3

Figure 3-37
Advice of Charge, Charge
Step 2
Enter the charge origin (for example, 09999).
Step 3
Enter the charge destination (for example, 09999).
Step 4
Enter the day of week (for example, SundaySaturday or HOL1HOL3).
Step 5
Enter a tariff description.
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
OL-1110-23
3-47
Chapter 3
Figure 3-38
Advice of Charge, Tariff
Step 2
Enter the tariff ID (for example, 09999).
Step 3
Enter the tariff rate (for example, 0-999999).
Step 4
Enter the tariff scale (for example, 0-999999).
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).
Configuring a Meter Tariff

Use the following procedure to configure a meter tariff on the MGC:
Step 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.
3-48
OL-1110-23
Chapter 3

Figure 3-39
Advice of Charge, Meter Tariff
Step 2
Enter the Tariff ID (for example, 09999).
Step 3
Enter the Number of Pulses on Answer (for example, 0255).
Step 4
Enter the Interval Between Pulses (for example, 5003600000).
Step 5
Enter the Number of Periodic Pulses (for example, 0 255).
Step 6
Enter the Periodic Charge Application (for example, 0 or 1).
Step 7
Enter the AOC Indicator (for example, 0 or 1).
Step 8
Enter the Maximum Call Length (for example, 0240).
Step 9
Enter the Tariff Type (for example, 015).
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
OL-1110-23
3-49
Chapter 3
Figure 3-40
Advice of Charge, Pritariff
Step 2
Enter the Tariff ID (for example, 19999).
Step 3
Enter the S Charged Item (for example, 04).
Step 4
Enter the SCA (for example, 110).
Step 5
Enter the S Recorded Charge (for example, 16).
Step 6
Enter the D Recorded Charge (for example, 13).
Step 7
Enter the E Recorded Charge (for example, 13).
Step 8
Enter the Currency.
Step 9
Enter the Amount (for example, 116777215).
Step 10
Enter the Amount Multiplier (for example, 06).
Step 11
Enter the Time Length (for example, 016777215).
Step 12
Enter the Time Scale (for example, 06).
Step 13
Enter the Granularity Length (for example, 016777215).
Step 14
Enter the Granularity Time Scale (for example, 06).
Step 15
Enter the Volume (for example, 02).
Step 16
Enter the SCU (for example, 032767).
Step 17
Enter the Billing Id (for example, 06).
Step 18
Enter the Charging Units (for example, 116777215).
Step 19
Enter the Duration (for example, 016777215).
Step 20
Enter the Rate Type (for example, 0 or 1).
3-50
OL-1110-23
Chapter 3

Step 21
Enter the Initial Tariff.
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
Advice of Charge, Pricharge
Step 2
Enter the charge origin (for example, 09999).
Step 3
Enter the charge destination (for example, 19999).
Step 4
Enter the day of week (for example, SundaySaturday or HOL1HOL3).
Step 5
Enter the STariff.
Step 6
Enter the DTariff.
Step 7
Enter the ETariff.
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).
OL-1110-23
3-51
Chapter 3
Adding GTD Parameters

Generic transparency descriptor (GTD) provides a means for specifying messages of various protocols
used in the PSTN network in plain text format. This is so they can be easily understood by the network
elements within the IP network or lie on the boundary between PSTN and IP. To provision GTD
Parameters, use the following steps:
Step 1
Step 2
Click GTD Parameters in the left pane of the main VSPT window. A window similar to the one shown
Figure 3-42
Adding GTD Parameters
Step 3
Enter a name.
Step 4
Enter the GTD Params.
Step 5
Enter the Override.
Step 6
Click Add. The hierarchical tree changes to reflect the GTD Parameters added.
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
In the DSCP drop-down menu, select a value.
Step 4
Click Modify. The hierarchical tree changes to reflect the TOS configured.

Cisco Media Gateway (MGW) control links provide the communication path used by the signaling
controller to control the bearer traffic passing through each media gateway. To configure the Cisco MGW
control links, use the components outlined in the sections below.
Adding External Nodes, page 3-54
Adding a Session Set, page 3-57
Adding an IPFAS Signaling Service, page 3-59
OL-1110-23
3-53
Chapter 3
Adding an MGCP Signaling Service, page 3-64
Adding a DPNSS Path, page 3-67
Adding an H.248 Signaling Service, page 3-69
Adding an EISUP Signaling Service, page 3-70
Adding an LIpath Signaling Service, page 3-72
Adding a NAS Signaling Service, page 3-74
Adding a CTI Signaling Service, page 3-76
Adding an SS7 SGP, page 3-78
Adding a TCPLNK, page 79
Adding a BRI Signaling Service, page 3-81
Adding a RAPATH, page 3-84
Adding a RASERVER for RAPATH, page 3-84
Configuring IP Links, page 3-86
Adding IP Links for MGCP, page 3-86
Adding IP Links for H248, page 3-87
Adding IP Links for EISUP, page 3-89
Adding IP Links for LI, page 3-90
Adding IP Links for NAS, page 3-91
Adding an ASSOCIATION, page 3-94
Adding a CTI Manager, page 3-95
Adding an AXL Server, page 3-96
Adding External Nodes

An external node is a node with which the MGC communicates either directly or indirectly. In the
example presented below, the media gateway is the external node. lists the external node properties. Use
the values in this table as you add external nodes to your MGC.
Table 3-11
External Node Properties
Field Name
MML Parameter
Description
Default
Valid Values
Name
name
Identifies the MML name for the external node
External-1
Up to 20
alphanumeric
characters;
cannot start
with a number
Description
desc
Describes the external node
External Node
Up to 128
alphanumeric
characters
Type
type
Lists the various external nodes supported; for

example, Cisco ITP-L or VISM
<UNSET>
See the
drop-down list
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
Figure 3-44
Adding External Nodes
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
Enter the M3UA/SUA group.
Step 7
Click Add. The hierarchical tree changes to reflect the External Nodes added.
Configuring Cisco MGWs

A Cisco MGW is the interface between the QoS packet network and the PSTN/ISDN network. A
gateway digitizes and compresses voice calls from the PSTN, creating IP packets for routing to another
gateway for forwarding to the PSTN or to a terminal.
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
Configuring a Cisco MGW
Step 2
In the MGX8850 Slot drop-down menu, select the slot.
Step 3
Enter the GW Domain.
Step 4
Enter the IP Address #1 in dotted notation.
Step 5
Enter the IP Subnet Mask #1 in dotted notation.
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.
3-56
OL-1110-23
Chapter 3

Adding a Session Set

A session set is a pair of backhaul IP links used by the MGC to communicate with external nodes that
support IP Facility Associated Signaling (IPFAS) and provide communication for IPFAS signaling
service between the MGC node and a media gateway. You must configure a session set before you can
add an IPFAS signaling service.
Table 3-12 lists session set properties.
Table 3-12
Session Set Properties
Field Name
Description
Default
Valid Values
Name
Unique ID of this component
None
characters; the name should
begin with an alphabetic
character. - is the only special
character permitted.
IPAddr1
Local logical IP address 1
IP_Addr1
IP_Addr1, IP_Addr2, IP_Addr3,

IP_Addr4.
IPAddr2
IP_Addr2
IP_Addr1, IP_Addr2, IP_Addr3,

IP_Addr4.
Port
Local UDP port number
None
102565535.
PeerAddr1
Remote IP address 1
None
IP address in dotted decimal

notation.
PeerAddr2
Remote IP address 2
None
IP address in dotted decimal

notation.
IPRoute 1
IP Route 1 Name
None
See the drop-down list in

Figure 3-46.
IPRoute 2
IP Route 2 Name
None
See the drop-down list in

Figure 3-46.
PeerPort
Remote UDP port
None
102565535.
Extnode
MML name of external node
None
MML name of previously

configured external port.
Type
Session Set Type
IPFAS
IPFAS and BSMV0.
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
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
Enter the port number.
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
Enter the Peer Port number.
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).
Adding and Changing Session Set Properties

You can add and change the properties of a session set after it is created. Changes apply to all session
sets created. You do not have to change the default properties.
Perform the following steps to add or change session set properties:
Step 1
Select the appropriate sessionset in the left pane of the main Cisco VSPT window.
Step 2
displays.
3-58
OL-1110-23
Chapter 3

Figure 3-47
Adding and Changing Session Set Properties
Step 3
Step 4
Click Add.
Step 5
Step 6
Step 7
Click Modify.
Step 8
Click OK when you are finished.
Note
You cannot modify properties until you have created the sessionset.
Adding an IPFAS Signaling Service

An IPFAS signaling service defines the FAS or NFAS over IP transport service or signaling path from
an MGC node to a media gateway.
Table 3-13 lists the IPFAS signaling service properties.
Table 3-13
IPFAS Signaling Service Properties
Property
MML Parameter
Description
Default
Valid Values
Name
name
Identifies the MML name of the IPFAS service

path.
Ipfas-1
Up to 20
alphanumeric
characters.
Description
desc
Describes the IPFAS service path.
Ipfaspath
signaling service
Up to 128
alphanumeric
characters.
External
Node
extnode
Identifies the external node.
None
User defined.
Up to 20
alphanumeric
characters;
cannot start with
a number.
OL-1110-23
3-59
Chapter 3
Table 3-13
IPFAS Signaling Service Properties (continued)
Property
MML Parameter
Description
Default
Side
side
Distinguishes the network equipment (like a

network
switch) from the user equipment (like a terminal
adapter or PBX). (Used for ISDN systems.)
Valid Values
Network,
User.
MDO
mdo
Identifies the protocol (MDO file name) for this

IPFAS service path. You select the MDO file
name in a drop-down list.
Bell_1268
See list.
Customer
Group ID
custgrpid
Contains a unique identifier for the number

analysis file. (Used with nailed solutions only.)
0000
00009999.
A/B Flag
abflag
Specifies DPNSS a or b side.
A side.
B side.
BNA.
(Field is ignored for ETSI.)

Call
Reference
Length
crlen
Identifies the field length (1 or 2 bytes) for the

call reference number.
2standard ETSI 0DPNSS.

11 byte.
22 bytes.
Originating
Label
origlabel
Origination Location Label
None
See the
drop-down list in
Figure 3-51.
Termination
Label
termlabel
Termination Location Label
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
3-60
OL-1110-23
Chapter 3

Figure 3-48
Adding an IPFAS Signaling Service
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
In the A/B Flag drop-down menu, select a value.
Step 8
In the Call Reference Length drop-down menu, select 0, 1, or 2.
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
In the DS1 type drop-down menu, select a value.
Step 12
In the MGW Card Slot drop-down menu, select a value.
Step 13
In the DS1 start drop-down menu, select a value.
Step 14
Enter a step interval.
Step 15
Enter the number of IPFASPATHs to create multiple IPFASPATHs.
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).
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
IPFAS Signaling Service Added
Add a D Channel
Enter a name.
3-62
OL-1110-23
Chapter 3

Step 19
Step 20
Select a priority from the Priority drop-down menu.
Step 21
Select a signal slot.
Step 22
Select a signal port.
Step 23
Select a session set.
Step 24
Click Add. The new D channel for the IPFAS signaling path displays in the lower portion of the window.
Step 25
Continue adding D channels for the IPFAS signaling paths as needed.
Changing IPFAS Signaling Service Properties

You can modify the properties of the IPFAS signaling services that you created. These properties apply
to all IPFAS signaling services. You do not have to change the default properties.
Use the following procedure to add or change IPFAS signaling service properties:
Step 1
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
Adding and Changing IPFAS Signaling Properties
To modify the IPFAS path configuration, click Properties. A window similar to the one shown in
OL-1110-23
3-63
Chapter 3
Figure 3-52
IPFAS Signaling Service Property Added
Step 3
To add a property, select the property in the Name drop-down list.
Step 4
Enter the property value in the Value drop-down list.
Step 5
Click Add. The new property and value appear in the top portion of the window.
Step 6
To modify a property, click the property you want to change.
Step 7
Step 8
Click Modify.
Step 9
Click OK when you are finished adding or modifying properties.
Note
You cannot modify properties until you have created the IPFAS signaling service.
Adding an MGCP Signaling Service

The MGCP signaling service specifies the path that the MGC node uses to communicate with a media
gateway. The MML component name is MGCPPATH.
Table 3-14 lists the MGC signaling service properties. Use the values in the table as you add an MGCP
signaling service.
Table 3-14
MGC Signaling Service Properties
Property
MML Parameter
Description
Default
Valid Values
Name
name
Identifies the MML name for the MGCP signaling Mgcp-1

service
Up to 20
alphanumeric
characters
Description
desc
Describes the service path
Mgcppath
Signaling Service
Up to 128
alphanumeric
characters
External
Node
extnode
Identifies the gateway for this signaling service
None
User defined
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
Step 2
Enter a name.
Step 3
Step 4
Click Add. The hierarchical tree changes to reflect the MGCP signaling service link added.
Adding and Changing MGCP Signaling Service Properties

You can add and change the properties of the signaling service for all the signaling services you create.
You do not have to change the default properties.
Set the following properties for all MGCP signaling services defined in your Cisco MGC:
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).
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
displays.
Figure 3-54
Step 2
Adding and Changing MGCP Signaling Properties
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
MGCP Signaling Service Property Added
Step 3
Step 4
Step 5
Click Modify.
Step 6
3-66
OL-1110-23
Chapter 3

Note
You cannot modify properties until you have created the MGCP signaling service.
Adding a DPNSS Path

Use the following procedure to add DPNSS paths to the media gateway:
Step 1
Click DPNSS in the left pane of the main Cisco VSPT window. A window similar to the one shown in
Figure 3-56
Adding a DPNSS Path
Step 2
Enter a name.
Step 3
Step 4
Enter the Signal Port.
Step 5
Enter the Signal Slot.
Step 6
Enter the Customer Group ID.
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.
OL-1110-23
3-67
Chapter 3
Adding and Changing DPNSS Path Signaling Properties

Use the following procedure to add or change DPNSS path signaling properties:
Step 1
displays.
Figure 3-57
Adding and Changing DPNSS Path Signaling Properties
Step 2
To add a property, enter a name and value.
Step 3
Click Add. A window similar to the one shown in Figure 3-58 displays with the property added.
Figure 3-58
DPNSS Path Signaling Property Added
Step 4
Step 5
Step 6
Click Modify.
Step 7
Note
You cannot modify properties until you have created the DPNSS path.
3-68
OL-1110-23
Chapter 3

Adding an H.248 Signaling Service

Use the following procedure to add an H.248 signaling service to the media gateway:
Step 1
Click H248 in the left pane of the main Cisco VSPT window. A window similar to the one shown in
Figure 3-59
Adding an H.248 Signaling Service
Step 2
Enter a name.
Step 3
Step 4
Click Add. The hierarchical tree changes to reflect the H248 signaling service added.
Adding and Changing H248 Signaling Properties

Use the following procedure to add or change H248 signaling properties:
Step 1
displays.
OL-1110-23
3-69
Chapter 3
Figure 3-60
Adding and Changing H248 Signaling Properties
Step 2
Step 3
Figure 3-61
H248 Signaling Property Added
Step 4
Step 5
Step 6
Click Modify.
Step 7
Note
You cannot modify properties until you have created the H248 signaling service.
Adding an EISUP Signaling Service

Use the following procedure to add an EISUP signaling service to the media gateway:
Step 1
Click EISUP in the left pane of the main Cisco VSPT window. A window similar to the one shown in
3-70
OL-1110-23
Chapter 3

Figure 3-62
Adding an EISUP Signaling Service
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.
Adding or Changing EISUP Signaling Properties

Use the following procedure to add or change EISUP signaling properties:
Step 1
displays.
OL-1110-23
3-71
Chapter 3
Figure 3-63
Adding and Changing EISUP Signaling Properties
Step 2
Step 3
Figure 3-64
EISUP Signaling Property Added
Step 4
Step 5
Step 6
Click Modify.
Step 7
Note
You cannot modify properties until you have created the EISUP signaling service.
Adding an LIpath Signaling Service

Use the following procedure to add a lawful intercept path (LIpath) signaling service to the media
gateway:
Step 1
Click LI in the left pane of the main Cisco VSPT window. A window similar to the one shown in
3-72
OL-1110-23
Chapter 3

Figure 3-65
Adding LIpath Signaling Service
Step 2
Enter a name.
Step 3
Step 4
Click Add. The hierarchical tree changes to reflect the LIpath signaling service added.
Adding or Changing LI Signaling Properties

Use the following procedure to add or change LI signaling properties:
Step 1
displays.
Figure 3-66
Step 2
Adding and Changing LI Signaling Properties
OL-1110-23
3-73
Chapter 3
Step 3
Figure 3-67
LI Signaling Property Added
Step 4
Step 5
Step 6
Click Modify.
Step 7
Note
You cannot modify properties until you have created the LI signaling service.
Adding a NAS Signaling Service

Use the following procedure to add a NAS signaling service to the media gateway:
Step 1
Click NAS in the left pane of the main Cisco VSPT window. A window similar to the one shown in
3-74
OL-1110-23
Chapter 3

Figure 3-68
Step 2
Enter a name.
Step 3
Step 4
In the message definition object (MDO) drop-down menu, select BELL_1268_C2.
Step 5
Step 6
Enter the SigSlot.
Step 7
Enter the SigPort.
Step 8
Adding and Changing NAS Signaling Properties

Use the following procedure to add or change NAS signaling properties:
Step 1
displays.
OL-1110-23
3-75
Chapter 3
Figure 3-69
Adding and Changing NAS Signaling Properties
Step 2
Step 3
Figure 3-70
NAS Signaling Property Added
Step 4
Step 5
In the Value field, enter the new property value.
Step 6
Click Modify.
Step 7
Note
You cannot modify properties until you have created the NAS signaling service.
Adding a CTI Signaling Service

Use the following procedure to add a CTI signaling service to the media gateway:
Step 1
Click CTI in the left pane of the main Cisco VSPT window. A window similar to the one shown in
3-76
OL-1110-23
Chapter 3

Figure 3-71
Adding a CTI Signaling Service
Step 2
Enter a name.
Step 3
Step 4
In the MDO drop-down menu, select the appropriate mdo.
Step 5
Adding and Changing CTI Signaling Properties

Use the following procedure to add or change CTI signaling properties:
Step 1
displays.
Figure 3-72
Adding and Changing CTI Signaling Properties
OL-1110-23
3-77
Chapter 3
Step 2
Step 3
Figure 3-73
CTI Signaling Property Added
Step 4
Step 5
Step 6
Click Modify.
Step 7
Note
You cannot modify properties until you have created the CTI signaling service.
Adding an SS7 SGP

Use the following procedure to add an SS7 SGP:
Step 1
Click SGP in the left pane of the main Cisco VSPT window. A window similar to the one shown in
3-78
OL-1110-23
Chapter 3

Figure 3-74
Adding an SS7 SGP
Step 2
Enter the name.
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
OL-1110-23
3-79
Chapter 3
Figure 3-75
Adding a TCPLNK
Step 2
Enter a name.
Step 3
In the IP Address drop-down menu, select the appropriate IP address.
Step 4
Enter the Port number.
Step 5
In the Peer Address drop-down menu, select the appropriate IP address.
Step 6
Enter the peer Port number.
Step 7
In the IP Router drop-down menu, select the appropriate IPRoute.
Step 8
Click Add. The hierarchical tree changes to reflect the Tcplnk added.
Adding and Changing Tcplnk Properties

You can add and change the properties of a Tcplnk after it is created. Changes apply to all tcplnks
created. You do not have to change the default properties.
Perform the following steps to add or change tcplnk properties:
Step 1
Select the appropriate Tcplnk in the left pane of the main Cisco VSPT window.
Step 2
displays.
3-80
OL-1110-23
Chapter 3

Figure 3-76
Adding and Changing Tcplnk Properties
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.
Adding a BRI Signaling Service

Use the following procedure to add a BRI signaling service to the media gateway:
Step 1
Click BRI in the left pane of the main Cisco VSPT window.
Step 2
OL-1110-23
3-81
Chapter 3
Figure 3-77
Adding a BRI Signaling Service
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
In the Tcplnk drop-down menu, select the appropriate Tcplnk.
Step 10
In the First Slot drop-down menu, select a value.
Step 11
In the First Subunit drop-down menu, select a value.
Step 12
In the First Port drop-down menu, select a value.
Step 13
Enter a Number To Create.
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).
3-82
OL-1110-23
Chapter 3

Figure 3-78
Step 15
BRI Signaling Service Added
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
Select a signal slot.
Step 19
Select a signal subunit.
Step 20
Select a signal port.
Step 21
Select a Tcplnk.
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
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.
Adding a RASERVER for RAPATH

Use the following procedure to define a signal channel to the RADIUS accounting server. These
procedure also associates a RADIUS accounting signal path to this channel.
Step 1
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.
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
In the Peer Address drop-down menu, select the peer address.
Step 7
Enter the port number in the peer port field.
Step 8
In the IP Route drop-down menu, select the appropriate IP route.
Step 9
Enter the Order, Key, Timeout and Retrycount.
Step 10
Click Add. The hierarchical tree changes to reflect the RASERVER added.
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.
Adding IP Links for MGCP

An IP link for MGCP IP links identifies the connection that supports the MGCP service between an
MGC Ethernet interface and a media gateway. Use the following procedure to add MGCP IP links:
Step 1
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
Adding MGCP IP Links
Step 2
Enter a name.
Step 3
Step 4
IP Addr1
IP Addr2
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
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
Step 8
Step 9
Step 10
Click Add. The hierarchical tree changes to reflect the MGCP IP link added (see Figure 3-82).
Adding IP Links for H248

An IP link for H248 IP links identifies the connection that supports the H248 service between an MGC
Ethernet interface and a media gateway. Use the following procedure to add H248 IP links:
Step 1
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.
OL-1110-23
3-87
Chapter 3
Figure 3-83
Adding H248 IP Links
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
Step 5
Step 6
recommended for H248), but you should not use 1 through 1024; these are reserved for other
applications.
Step 7
Step 8
Step 9
Step 10
Click Add. The hierarchical tree changes to reflect the H248 IP link added.
3-88
OL-1110-23
Chapter 3

Adding IP Links for EISUP

An IP link for EISUP IP links identifies the connection that supports the EISUP service between an MGC
Ethernet interface and a media gateway. Use the following procedure to add EISUP IP links:
Step 1
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
Adding EISUP IP Links
Step 2
Enter a name.
Step 3
Step 4
Note
Step 5
IP Addr1
IP Addr2
IP Addr3
IP Addr4
OL-1110-23
3-89
Chapter 3
Step 6
recommended for EISUP), but you should not use 1 through 1024; these are reserved for other
applications.
Step 7
Step 8
Step 9
Step 10
Click Add. The hierarchical tree changes to reflect the EISUP IP link added.
Adding IP Links for LI

An IP link for LI IP links identifies the connection that supports the LI service between an MGC Ethernet
interface and a media gateway. Use the following procedure to add LI IP links:
Step 1
Click the icon next to LI in the left pane of the main Cisco VSPT window to expand the tree, and click
Figure 3-85
Adding LI IP Links
Step 2
Enter a name.
Step 3
Step 4
IP Addr1
IP Addr2
3-90
OL-1110-23
Chapter 3

Note
IP Addr3
IP Addr4
Step 5
Step 6
recommended for LI), but you should not use 1 through 1024; these are reserved for other applications.
Step 7
Step 8
Step 9
Step 10
Click Add. The hierarchical tree changes to reflect the LI IP link added.
Adding IP Links for NAS

An IP link for NAS IP links identifies the connection that supports the NAS service between an MGC
Ethernet interface and a media gateway. Use the following procedure to add NAS IP links:
Step 1
Click the icon next to NAS in the left pane of the main Cisco VSPT window to expand the tree, and click
OL-1110-23
3-91
Chapter 3
Figure 3-86
Adding NAS IP Links
Step 2
Enter a name.
Step 3
Step 4
Note
IP Addr1
IP Addr2
IP Addr3
IP Addr4
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
Step 8
Step 9
Step 10
Click Add. The hierarchical tree changes to reflect the NAS IP link added.
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
Adding a C7 IP Link
Step 2
Enter a name.
Step 3
Step 4
In the Priority drop-down menu, select the priority.
Step 5
In the Linkset drop-down menu, select the linkset for this link.
Note
The linkset is created in the Adding Linksets section on page 3-17.
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.
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
Figure 3-88
Adding an ASSOCIATION for a Media Gateway
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
Enter a number of the UDP port on the MGC.
Step 7
In the Peer Address 1 and Peer Address 2 drop-down menu, select the appropriate peer ip addr.
3-94
OL-1110-23
Chapter 3

Step 8
Enter a number of the peer UDP port on the MGC.
Step 9
In the IPRoute1 and IPRoute 2 drop-down menus, select the appropriate iproute.
Step 10
Enter the Receive Window (valid value range: 1500 to 65535).
Step 11
Enter the Retransmit SCTP Msgs (valid value range: 0 to 100).
Step 12
Enter the Timer Retransmissions (valid value range: 0 to 100).
Step 13
Enter the Max Number Retransmissions (0 or a value from 300 to 3000).
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
Enter the Retrans Time Out (valid value range: 1 to 10).
Step 22
Click Add. The hierarchical tree changes to reflect the association added.
Adding a CTI Manager

Use the following procedure to add a CTI Manager:
Step 1
Click CTI Manager in the left pane of the main Cisco VSPT window. A window similar to the one
OL-1110-23
3-95
Chapter 3
Figure 3-89
Adding a CTI Manager
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
Enter the Local CTI Port.
Step 6
Enter the Peer Address 1 and Peer Address 2.
Step 7
Enter the Peer Port.
Step 8
In the Peer Address 1 and Peer Address 2 drop-down menus, select the appropriate peer ip addr.
Step 9
In the CTIPATH drop-down menu, select the appropriate citpath.
Step 10
In the IPRoute 1 and IPRoute 2 drop-down menus, select the appropriate iproute.
Step 11
Enter the UserName, Password, and CTI Version of CTI Manager.
Step 12
Click Add. The hierarchical tree changes to reflect the CTI Manager added.
Adding an AXL Server

Use the following procedure to add an AXL Server:
Step 1
Click AXL Server in the left pane of the main Cisco VSPT window. A window similar to the one shown
3-96
OL-1110-23
Chapter 3

Configuring Bearer Traffic
Figure 3-90
Adding an AXL Server
Step 2
Enter the name.
Step 3
Step 4
In the IP Addr 1 and IP Addr 2 drop-down menus, select the appropriate ip addr.
Step 5
Enter the Local CTI Port.
Step 6
Enter the Peer Address 1 and Peer Address 2.
Step 7
Enter the Peer Port.
Step 8
In the Peer Address 1 and Peer Address 2 drop-down menus, select the appropriate peer ip addr.
Step 9
In the CTIPATH drop-down menu, select the appropriate citpath.
Step 10
In the IPRoute 1 and IPRoute 2 drop-down menus, select the appropriate iproute.
Step 11
Enter the UserName and Password of the AXl Server.
Step 12
Click Add. The hierarchical tree changes to reflect the AXL Server added.

Bearer traffic includes the trunk groups, trunks, and trunk routing information required by an MGC to
direct calls. It uses this information in conjunction with a dial plan to perform number analysis and route
selection.
A trunk is a speech path between any two switches. Trunks are DS0 endpoints; one trunk can ride on one
DS0 or one DS0 can carry one trunk. A trunk group is a logical grouping of trunks to a switch, and a
trunk route is a set of trunk groups.
The configuration example in this section uses SS7 and PRI trunks.
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
Setting Up the MGC Node for Call Routing
If you want to:

Create a new configuration
Modify an existing
configuration
Perform these steps:
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.
Build a dial plan using the instructions in the

Cisco PGW 2200 Softswitch Release 9 Dial Plan Guide (through
Release 9.7).
Load the existing configuration into the Cisco Voice Services

Provisioning Tool:
If you are modifying a local configuration, select File > Open,
and specify the configuration you want to modify.

If you are modifying a configuration on an MGC, select File >
Import, and specify the configuration you want to import.
Caution
Add, modify, or delete trunk groups using the instructions in the

Adding Trunk Groups section on page 3-102.
Add or delete trunks on a trunk group basis, using the instructions

in the Adding Trunks section on page 3-139.
Add, modify, or delete route groups using the instructions in the

Adding Routes section on page 3-147.
Build a dial plan using the instructions in the

Cisco PGW 2200 Softswitch Release 9 Dial Plan Guide (through
Release 9.7).
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.
Importing Trunk Groups and Trunks, page 3-99
Adding a Trunk Group Profile, page 3-101
Adding Trunk Groups, page 3-102
Adding Trunks, page 3-139
Figure 3-102Adding a CodecString, page 3-144
3-98
OL-1110-23
Chapter 3

Adding a BearerCap, page 3-145
Adding an ATMProfile, page 3-146
Adding Routes, page 3-147
Hierarchical View of Provisioned Components, page 3-149
Importing Trunk Groups and Trunks

You can import trunk groups and trunks to make them available to the MGC. Consider importing a trunk
group for initial provisioning only. When you import a trunk group, all of the existing trunk groups are
replaced by the imported trunk groups, and all existing trunks are deleted.
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).
OL-1110-23
3-99
Chapter 3
Figure 3-92
Step 3
Imported File Type
Enter the name of the file you want to import. If you do not know the name of the file, click Select. A
Figure 3-93
Specify the File to Import
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
Click OK. The file you selected is imported.
3-100
OL-1110-23
Chapter 3

Adding a Trunk Group Profile

A trunk group profile allows you to define a collection of trunk group properties and associate trunk
groups with those properties.
Use the following procedure to configure a profile:
Step 1
Select the Traffic radio button in the top portion of the main Cisco VSPT window.
Step 2
Click Profiles in the left pane.
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
Trunk Group Profile Added
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.
OL-1110-23
3-101
Chapter 3
Adding Trunk Groups

A trunk group is a collection of DS0 circuits arranged so that dialing a single trunk number provides
access to the entire trunk group.
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
Click Trunk Groups in the left pane.
Step 3
Figure 3-95
Defining a Trunk Group
Step 4
Enter the trunk group number.
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
In the Trunk Type drop-down menu, select the type of trunk.
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
In the Select Sequence drop-down menu, select the sequence.
Step 10
In the VSF Priority drop-down menu, select the priority.
Step 11
In the Originating Location Label drop-down menu, select the label.
Step 12
In the Terminating Location Label drop-down menu, select the label.
Step 13
Click the Prop-1 tab. A window similar to the one shown in Figure 3-96 displays.
Figure 3-96
Trunk Group Properties
Step 14
Enter the ring no answer.
Step 15
In the Glare drop-down menu, select Always, Even/Odd, or Never.
Step 16
Enter the COT percentage.
Step 17
In the Satellite drop-down menu, select Yes or No.
Step 18
Enter the numbering plan area.
Step 19
Step 20
In the Compression Type drop-down menu, select Mu-law or A-law.
Step 21
In the Echo Canceller Required drop-down menu, select Yes or No.
Step 22
In the External COT drop-down menu, select Loop, Transponder, or 0.
Step 23
Select whether trunks detect fax modem tones, and then select Yes or No.
Step 24
Enter the wait interval for origination SDP Timer.
Step 25
Enter the wait interval for termination SDP Timer.
Step 26
Select Send Address in cgpn, and then select FALSE or TRUE.
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.
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
Trunk Group Added
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.
Trunk Group Properties

Table 3-16 lists the trunk group properties shown on each tab in the Trunk Group Data and Property
window, along with their MML name and description. The specific appearance of the window depends
on your version of Cisco VSPT. As MML features are added to MGC software, the tabs and properties
are expanded.
Table 3-16
Trunk Group Properties Descriptions
VSPT Parameter Name
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
Any 11 or fewer alphanumeric characters.
3-104
OL-1110-23
Chapter 3

Table 3-16
Trunk Group Properties Descriptions (continued)
VSPT Parameter Name
MML Parameter
Name
Signaling Service
Signal Service
The MML name of a previously defined SS7, IPFAS, or FAS signaling

service associated with or controlling the trunk group.
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.
5 = BTNUP27 = NET5
22 = NI2.
Queueable Type
QABLE
Determines if queuing is used on the trunk during call processing. Value

range: Y for yes or N for no (default).
OL-1110-23
3-105
Chapter 3
Table 3-16
VSPT Parameter Name
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 ...).
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 ....
3-106
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name

Select Sequence
(continued)
MML Parameter
Name
Description
selseq
... continued:
LIDL = Least idle (default). The system selects the least idle (most 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...).
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
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 Priority
VSF
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).
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
Indicates the number of allowed reattempts on this trunk group if congestion

prevails. Value range: 05.
Queuing
Queuing
Indicates the length of time in milliseconds that queuing is permitted on the

trunk group. Value range: 0120.
Routing Property
OL-1110-23
3-107
Chapter 3
Table 3-16
VSPT Parameter Name

Cutthrough
MML Parameter
Name
Description
Cutthrough
Indicates the point at which a call is connected. Valid values:

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
ResIncoming
Perc
ResIncPerc
Percentage of bandwidth reserved for incoming calls. Value range: 0100.
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
Ring no answer. Indicates the time, in seconds, ringing is allowed to occur.

Value range: 0 through 255 (default), which is converted to milliseconds.
Glare
GLARE
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).
Numbering Plan Area
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
Echo Canceller Required. Specifies whether to send a modify-connection

message (MDCX) for echo control. Enter a value of 0 or 1 for
EchoCanRequired on the trunk group or sigpath.
Prop-1 tab
receives a call-in-progress message (CPG) with backward call indicators
(BCI) from the SS7 side, it takes the specified action.
3-108
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name
MML Parameter
Name
External COT
ExtCOT
Detect Fax Modem

Tone
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.
Wait OrigSDP Timer
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).
Wait TermSDP Timer
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
Send Address in Cgpn
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
destination. Values are: 0-no COT, loop (default), or transponder.
Prop-2
Maximum ACL
MaxACL
Maximum automatic congestion level. The MGC indicates its congestion

level (if it is greater than 0) in the ISUP release message. Values: 0, 2, or 3
(default).
ACL Duration
ACLDuration-
Automatic congestion level duration. When MGC receives ACL indication

from a linked switch, the MGC assumes ACL is in effect for the duration
specified (in seconds). Value range: Any value greater than 0 (5 is the
default).
ACC Response Control

Inhibit
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
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).
Carrier Screening
CarrierScreening
Carrier screening. Defines whether or not carrier screening and selection is to

be applied on the current call (using the Carrier Translation table). Values are:
0 (do not apply screening) (default), or 1 (do apply screening).
Originating Carrier ID
OrigCarrierId
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).
Notify Setup Complete
NotifySetupCompl
ete
Notify setup complete. Used for notifying the Asynchronous Notification

task. When the MGC 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.
OL-1110-23
3-109
Chapter 3
Table 3-16
VSPT Parameter Name
MML Parameter
Name
Signaling Service
Signal Service
The MML name of a previously defined SS7, IPFAS, or FAS signaling

service associated with or controlling the trunk group.
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.
5 = BTNUP27 = NET5
22 = NI2.
Queueable Type
QABLE
Determines if queuing is used on the trunk during call processing. Value

range: Y for yes or N for no (default).
3-110
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name
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 ...).
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
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 ....
OL-1110-23
3-111
Chapter 3
Table 3-16
VSPT Parameter Name

Select Sequence
(continued)
MML Parameter
Name
Description
selseq
... continued:
LIDL = Least idle (default). The system selects the least idle (most 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...).
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
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 Priority
VSF
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.
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
Indicates the number of allowed reattempts on this trunk group if congestion

prevails. Value range: 05.
Queuing
Queuing
Indicates the length of time in milliseconds that queuing is permitted on the

trunk group. Value range: 0120.
Routing Property
3-112
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name

Cutthrough
MML Parameter
Name
Description
Cutthrough
Indicates the point at which a call is connected. Valid values:

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
ResIncoming
Perc
ResIncPerc
Percentage of bandwidth reserved for incoming calls. Value range: 0100.
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
Ring no answer. Indicates the time, in seconds, ringing is allowed to occur.

Value range: 0 through 255 (default), which is converted to milliseconds.
Glare
GLARE
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).
Numbering Plan Area
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
Echo Canceller Required. Specifies whether to send a modify-connection

message (MDCX) for echo control. Enter a value of 0 or 1 for
Prop-1 tab
receives a call-in-progress message (CPG) with backward call indicators
(BCI) from the SS7 side, it takes the specified action.
OL-1110-23
3-113
Chapter 3
Table 3-16
VSPT Parameter Name
MML Parameter
Name
External COT
ExtCOT
Detect Fax Modem

Tone
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.
Wait OrigSDP Timer
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
Wait TermSDP Timer
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
Send Address in Cgpn
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
destination. Values are: 0-no COT, loop (default), or transponder.
Prop-2
Maximum ACL
MaxACL
Maximum automatic congestion level. The MGC indicates its congestion

level (if it is greater than 0) in the ISUP release message. Values: 0, 2, or 3
(default).
ACL Duration
ACLDuration-
Automatic congestion level duration. When MGC receives ACL indication

from a linked switch, the MGC assumes ACL is in effect for the duration
specified (in seconds). Value range: Any value greater than 0 (5 is the
default).
ACC Response Control

Inhibit
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
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).
Carrier Screening
CarrierScreening
Carrier screening. Defines whether or not carrier screening and selection is to

be applied on the current call (using the Carrier Translation table). Values are:
0 (do not apply screening) (default), or 1 (do apply screening).
Originating Carrier ID
OrigCarrierId
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).
Notify Setup Complete
NotifySetupCompl
ete
Notify setup complete. Used for notifying the Asynchronous Notification

task. When the MGC 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.
3-114
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name
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
Automatic congestion control response category name. Specifies the ACC

Response Controls listed in the ACC Response Category table. Value range:
any character string. Default: default.
Default Carrier ID
NatNet ID Plan
DefaultCARIDNat
NetIdPlan
Default Carrier Identification national network identification plan. Values

are: 0 (NOTUSED) (default),
1 (NATIONAL_NETWORK_ID_NATIONAL
CARRIER_ACCESS_CODE),
2 (NATIONAL_NETWORK_ID_PLAN_2_DIGIT),
3 (NATIONAL_NETWORK_ID_PLAN_3_DIGIT), or
4 (NATIONAL_NETWORK_ID_PLAN_4_DIGIT).
Default Originating
Line Information
DefaultOLI
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),
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),
29 (OLI_INTERLATA_RESTRICTED_HOTEL), or
30 (OLI_INTERLATA_RESTRICTED_COINLESS)
OL-1110-23
3-115
Chapter 3
Table 3-16
VSPT Parameter Name
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 Charge Number DefaultCHG
Default charge number. Values are: 1 to 16 digits or NULL. Default: 0.
Default Charge Number DefaultCHGNOA

NOA
Default charge NOA. Values are: 0 (NOTUSED) (default),

1 (CHNOA_ANI_CGSUB_SUB_NUM),
2 (CHNOA_ANI_NOT_AVAIL),
3 (CHNOA_ANI_CGSUB_NAT_NUM),
4 (CHNOA_ANI_CDSUB_SUB_NUM),
5 (CHNOA_ANI_CDSUB_NO_NUM), or
6 (CHNOA_ANI_CDSUB_NAT_NUM)
Default Charge Number DefaultCHGNPI

NPI
Default charge number NPI. Values are: 0 (NOTUSED) (default),

1 (NPI_NONE),
2 (NPI_E164),
3 (NPI_DATA),
4 (NPI_TELEX),
5 (NPI_PNP),
6 (NPI_NATIONAL),
7 (NPI_TELEPHONY),
Default Directory
Number
Default directory number. This property is needed on the Trunk Group if it is

a switched call and on the SigPath if it is a nailed call. Values are: 1 to 14
digits or NULL. Default = 0.
DefaultDN
3-116
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name
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)
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)
OL-1110-23
3-117
Chapter 3
Table 3-16
VSPT Parameter Name
MML Parameter
Name
Description
Default Directory
Number NPI
DefaultDNNPI
Default directory number NPI. Values are: 0 (NOTUSED) (default),

1 (NPI_NONE),
2 (NPI_E164),
3 (NPI_DATA),
4 (NPI_TELEX),
5 (NPI_PNP),
6 (NPI_NATIONAL),
7 (NPI_TELEPHONY),
Default Directory
Presentation Indicator
DefaultDNPres
Default directory presentation indicator. Values are: 0 (NOTUSED) (default),
Default Directory
Screening Indicator
DefaultDNSI
2 (PRES_ALLOWED),
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
Default carrier identifier network type. Values are: 0 (NOTUSED) (default),

1 (NETWORK_USER_SPECIFIED),
2 (NETWORK_NATIONAL),
3 (NETWORK_INTERNATIONAL), or
4 (NETWORK_CCITT)
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
Wait Answer Timer
WaitAnswerTimer
Failure to configure this property correctly may result in calls

terminating in the H.323 network failing to have ring back tones
applied.
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.
3-118
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name
MML Parameter
Name
Charge Origin
ChargeOrigin
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
A-number international prefix. Determines the prefix of the outgoing calling

number when NOA is set to National. Value range: NULL (default) or a
numeric string.
BInternationalPrefi
x
B-number international prefix. Determines the prefix for outgoing called

numbers when NOA is set to International. Value range: NULL (default) or
digit string.
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
A-digit country code prefix. Controls functionality that applies a country

code 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
BDigitCCPrefix
B-digit country code prefix. Controls functionality that applies a country

code 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.
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
Ta3TimePeriod
Ta3TimePeriod
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
Expiry warning tone duration, in seconds. Value range: 1 through 5. Default:

1.
OL-1110-23
3-119
Chapter 3
Table 3-16
VSPT Parameter Name
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
Allow H.323 hairpinning. Allows the MGC to interconnect H.323-originated

and H.323-terminated calls by the HSI component. Valid values: 0 (not
allowed) or 1 (allowed). Default: 0.
EISUP link to H323

Platform
H323AdjunctLink
H.323 adjunct link. Indicates if an EISUP link is connected to an H323

adjunct platform. This allows using the generic mechanism for COT handling
when the terminating side does not support COT. Valid Values: 0 (EISUP link
is not connected to an H.323 adjunct platform) or 1 (EISUP link is connected
to an H.323 adjunct platform). Default: 0.
Note
Incoming Trkgrp Fax

support
Removed from trunk group properties and added to SigPath

properties in software Release 9.4(1).
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
SIP Subscribe/Notify methods. Determines if the SIP Subscribe/Notify

methods for solicited notification of SIP DTMF digits is enabled or disabled.
Valid Values: 0 = Subscribe/Notify methods disabled or 1 = Subscribe/Notify
methods enabled.
Prop-5 tab
Subscribe Notify
Support
Default: 0
Unsolicited Notify
Method
UnsolicitedNotify
Method
Unsolicited Notify method. Determines if the unsolicited Notify method for

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
Option 2 is added in software Release 9.7(3) and later
3-120
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name

MinEvent Subscribe
Duration
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
Max Subscription
Duration
MaxSubscriptionD
uration
Maximum subscription duration. Defines the maximum duration (in seconds)

for which a subscription can be made. Value range: 0 through 3600.
Default: 0
PopulateSDPInfo
InCDR
PopulateSDP
InfoInCDR
Enables or disables the extraction of SDP information from SDP. Extracted

SDP information is placed in call detail records (CDRs). Valid values: 0
(Disable SDP information extraction) or 1 (Enable SDP information
extraction). Default: 0.
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).
Anumnormalise
Anumnormalise
A Number Normalise. Anumnormalise indicates that calling party number

(A-number) normalization is appropriate based on the NOA value and the
leading digits of the A-number. Leading digits 0 or 00 are the only accepted
digits. Valid values: 0 (disabled) or 1 (enabled).
Default: 0
When this property is provisioned, any normalization action is applied to the
A-number and the following numbers, if present (stored internally):
GN_AcgPnGeneric number parameter containing additional calling

party number
Redirecting number (or all redirecting numbers if there is more than one)
OCNOriginal called number
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.
This property is added in software Release 9.4(1) and is a European feature

only.
OL-1110-23
3-121
Chapter 3
Table 3-16
VSPT Parameter Name
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
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.
This property is added in software Release 9.4(1) and is a European feature

only.
GtdCapTypeProp
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
ISUP Transparency Early Backward Disabled. Indicates if the egress

Cisco PGW 2200 Softswitch is to send an end-to-end message, called Early
Backward Call Setup message, immediately after receiving the call setup
message with GTD information about the outgoing protocol variant. Valid
values: 0 (enable) or 1 (disable). Default: 1
sipMimeBodySupport
sipMimeBodySupp
ort
Determines if SIP-T or SIP-GTD special data processing is supported on a

trunk group. Valid Values: 0None, 1SIP-T supported, or 2SIP-GTD
supported.
Default Value: 0
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
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
3-122
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name
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
OL-1110-23
3-123
Chapter 3
Table 3-16
VSPT Parameter Name
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)
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)
3-124
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name

Number NPI
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)
Default value: 0.
Number Indicator
DefaultPNPres
Displays the Default Presentation Number Presentation Indicator value. Valid

values: 0 through 4.
0 (NOTUSED)
1 (PRES_NO_INDICATION)
2 (PRES_ALLOWED)
3 (PRES_RESTRICT)
4 (PRES_UNAVAIL)
Default value: 0.
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.
OL-1110-23
3-125
Chapter 3
Table 3-16
VSPT Parameter Name
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.
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.
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
Assigns a VPN ID to a trunk group or system. Valid values: 1 through 8

numeric character string.
Default value: 00000000
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.
5The Cisco PGW 2200 Softswitch removed the attempted feature from the
onward-routed call and informs the indicator of the change.
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)
3-126
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name
MML Parameter
Name
Description
Feature
Transparency
Disabled
Feature
Transparency
Disabled
Disables QSIG feature transparency for all calls on the

Cisco PGW 2200 Softswitch. Valid values: 0 (Feature Transparency enabled)
or 1 (Feature Transparency disabled).
Default value: 0
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
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:
A list of profile names separated by semicolons such as

<Profile1>;<Profile2>;<ProfileN>.
NULL
Default value: NULL.

PlayAnnouncement Id
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.
OL-1110-23
3-127
Chapter 3
Table 3-16
VSPT Parameter Name

AtmConnection
Type
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).
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.
Prop-7 tab
Loop Avoidance
Support
LoopAvoidance
Support
Enables support of the loop avoidance feature in DPNSS protocol. Valid

values: 0 (disable) or 1 (enable).
Default value: 0
Loop Avoidance
Counter
LoopAvoidance
Counter
Enables support of the loop avoidance feature in DPNSS protocol. Valid

values: 0 (disable) or 1 (enable).
Default value: 0
MWI Off String
MwiStringOFF
Enables support for a Message Waiting Indication (MWI) string in a DPNSS

protocol message. The message instructs a particular extension to extinguish
its MWI LED (also known as the MWI lamp).
Valid values: Digit string from 1 through 32 digits.
Note
Ensure that the digit string provisioned is the same MWI string
provisioned in Cisco CallManager.

MWI On String
MwiStringON
Enables support for a Message Waiting Indication (MWI) string in a DPNSS

protocol message. The message instructs a particular extension to light its
MWI LED (also known as the MWI lamp).
Valid values: Digit string from 1 through 32 digits.
Note
Ensure that the digit string provisioned is the same MWI string
provisioned in Cisco CallManager.
3-128
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name
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.
InhibitOutgoingCalling InhibitOutgoingCal Enables or disables the inhibiting of the outgoing calling name display in
NameDisplay
lingNameDisplay
Default value: 0.
InhibitIncomingConnec InhibitIncomingCo
tedNameDisplay
nnectedNameDispl
ay
Enables or disables the inhibiting of the incoming connected name display in

Default value: 0.
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
AOC Default Tariff Id
AOCDefaultTariffI
d
Allows configuration of the default tariff ID to be applied when

AOCInvokeType is configured for all calls (that is, AOCInvokeType = 2).
Default value: 1
AOC Invoke Type
AOCInvokeType
Allows configuration of whether or not the AOC Supplementary services are

applicable on a per call basis or for all calls. Values: 1 (on a per call basis, the
default) or 2 (for all calls).
Default value: 1
MidCallCPInterval
MidCallCPInterval
Enables or disables mid-call checkpointing. When it is 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
OL-1110-23
3-129
Chapter 3
Table 3-16
VSPT Parameter Name

CliSelectionFor
CodeOfPractice3
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
InhibitOutgoingConnec InhibitOutgoingCo
tedNameDisplay
nnectedNameDispl
ay
Enables or disables inhibit outgoing connected name display in DPNSS and

EISUP (HSI) protocols. Valid values: 0 (enable) or 1 (disable).
Default value: 0
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
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.
Dynamically reconfigurable: Yes

ADigitCCrm
ADigitCCrm
Provides a country code digit string to which leading digits of CgPN,

GN_ACgPN, RDN, OCN and PN can be compared. If the digits match, those
digits are removed from the front of that number. The NOA code of that
number is set to National. This modification is made before the call is sent
forward. Values are NULL (default) or null, or a maximum 5-digit string.
Valid values: 1 through 99999.
Default: NULL
Prop-8 tab
3-130
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name

Own Routing Number
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).
QSIG Tunnel Variant
QSIGTunnelVariant Controls the QSIG tunnel capability across outbound EISUP (HSI) interfaces
and specifies which protocol variant is used.
Valid Values:
0QSIG tunneling is disabled
1QSIG tunneling is enabled
Default Value: 0
Disable QSIG Release
Method
DisableQSIGRelea
seMethod
Indicates the QSIG release method. An H.225 signaling connection can be

released with a single Release Complete message instead of a three-stage
QSIG release sequence. This is only applicable to release procedures initiated
by the PGW 2200. The PGW accepts receipt of either type of release method.
Valid Values:
0 Normal QSIG release is enabled for QSIG tunneling
1 Normal QSIG release is disabled for QSIG tunneling
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
Allows configuration of the Path Reservation option for each QSIG

destination. In the case of EISUP, this is valid for HSI destinations only.
Valid values:
0CCBS with Path Reservation is disabled
1CCBS with Path Reservation is enabled
Default value: 0
OL-1110-23
3-131
Chapter 3
Table 3-16
VSPT Parameter Name
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
H248GatewayReser Note This property is deleted in Release 9.7S23P23 and later.

veValue
This property allows H.248 to send ADD commands with the ReserveValue
on or off to indicate whether the media gateway (MG) should reverse resource
or not. This property applies only to the originating MG; for the terminating
side, the ReserveValue is always off.
Valid values (boolean):
0Do not reserve resource
1Reserve resource
Default value: 0
Dynamically reconfigurable: yes
This property is removed since Cisco VSPT Release 2.7(3) patch 5.
3-132
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name
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.
1Map the RN to the Diversion header. Map the RN to the EISUP RN

parameter.
2Map the RN to the Diversion header only when RN presentation is

allowed. Map the RN to the EISUP RN parameter only when the RN
presentation is allowed.
Default Value: 1
Itp Action Request
ItpActionRequest
The ItpActionRequest property indicates that the PGW should send a

customized SIP invite to the ITP to return the location of a mobile subscriber.
Setting this property to map-app indicates that the PGW should send a
customized SIP invite to the ITP to return the location of a mobile subscriber.
The customized SIP invite causes the ITP to send a MAP query to the service
provider HLR for the mobile subscribers current mobile station roaming
number (MSRN). The PGW then routes the call to the closest Gateway MSC
based upon the new MSRN.
If the PGW is unable to optimize the call routing based on the MSRN, it
continues to route calls based on using the mobile subscribers MSISDN
(telephone number). The PGW routes calls based on an MSISDN using cause
analysis.
Values: Null or map-app
Default: Null
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
Specifies minimum number of digits to receive for overlap digit processing

for call termination to this traffic path. Value range: 0 through system
maximum.
Default: 0
TMaxDigits
TMaxDigits
Specifies maximum number of digits to receive for overlap digit processing

for call termination to this traffic path. Value range: 0 through system
maximum.
Default: 24
Prop-9 tab
OOverlap
OOverlap
Set to 1 to enable overlap signaling for call origination from this traffic path.
Default: 0
OL-1110-23
3-133
Chapter 3
Table 3-16
VSPT Parameter Name
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
Specifies maximum number of digits to receive for overlap digit processing

for call origination from this traffic path. Value range: 0 through system
maximum.
Default: 24
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
Defines the DTMF capability of the egress trunk group.

Valid values:
0Ignore DTMF capability
1RFC 2833 DTMF capability
2Out of band DTMF capability
Default Value: 0
3-134
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name

MapCLItoSipHeader
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.
If cgpnInclude = 0, and the SIP network is untrusted, the From
header has SIP URI as: Anonymous

<sip:Anonymous@anonymous.invalid>
If 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>
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.
2Map the calling party number to the Remote-Party-ID header only

when the calling party number presentation is allowed. For handling the
additional calling party number in the generic number, the operation is
the same as for a value of 1.
3The calling party number is mapped to the P-Asserted ID, with

privacy header value ID, if necessary. If an additional calling party
number is present in the generic number, it is mapped to the SIP From
header.
Note
If the calling party number presentation is allowed, there is no privacy

header. If the calling party number presentation is restricted, there is
a privacy header with a value ID.
4Map the calling party number to the P-Asserted ID header only when
the calling party number presentation is allowed. For handling the
additional calling party number in the generic number, the operation is
the same as for a value of 3.
Default Value: 0
Note
In Release 9.6(1), mapclitosipheader is a sigpath property only. In

Release 9.7(3), it is a sigpath and a trunk group property.
OL-1110-23
3-135
Chapter 3
Table 3-16
VSPT Parameter Name
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:
0If the PAID/RPID E164 number is present, map the PAID/RPID to

CgPN, map the E164 number in username in From header to GN
(additional CgPN). If the PAID/RPID E164 number is not present, map
the E164 number in username in From header to CgPN.
1 Ignore the From header, map PAID/RPID E164 number to CgPN.
2Ignore the PAID/RPID, map the E164 number in username in From

header to CgPN.

CgPN, map the E164 number in Display name in From header to GN
(additional CgPN). If the PAID/RPID E164 number is not present, map
the E164 number in username in From header to ISUP CgPN, and map
the E164 number in displayname in From header to GN (additional
CgPN)

CgPN, map the E164 number in username in From header to GN
(additional CgPN). If the PAID/RPID E164 number is not present, ignore
the From header.
Note
The 4 value is only available in Release 9.7(3).
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
3-136
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name
MML Parameter
Name
Description
ReferRedirecting
Ind
Refer
RedirectingInd
Redirecting indicator of Redirection Information in ITU SS7 REL message

for blind transfer by SIP REFER.
Value range:
0No redirection
1Call rerouted
2Call rerouted, all redirection information presentation restricted
3Call diverted
4Call diverted, all redirection information presentation restricted
5Call rerouted, redirection number presentation restricted
6Call diversion, redirection number presentation restricted
SipDtmfContentType
SipDtmfContentTy
pe
This property determines the Content-Type header and the SDP content of
INFO requests PGW sends out.
Valid values:
0 = Sets the Content-Type header to audio/telephone-event
1 = Sets the Content-Type header to application/dtmf-relay
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:
0Buffer the new offer
1Reject the new offer
Default value: 1
IsdnNSF
IsdnNSF
Indicates the network specific facilities parameter for ISDN PRI.

Specify an integer from 0256.
0255: Directly mapping to 0x00-0xFF in the outgoing message.
256: No NSF in the outgoing message.
Default: 256.
This property is added in software release 9.7(3) S22P22.
MidCallCodecSelect
UseGtdCalledPartyNu
mber
MidCallCodecSele
ct
Enable/disable codec selection for Mid-Call. It works only on the originating

side. Valid values: 0disable, 1enable.
UseGtdCalledParty Enables the Cisco PGW 2200 Softswitch to use embedded

Number
calledPartyNumber field of GTD in the invite message instead of url/number
contained in the request line. Valid values: 0disable, 1enable.
SIP-1 tab
MGC Domain Name
MGCdomain
MGC domain name. Indicates the MGC domain name used in SIP messages.
Value range: Any valid domain name or NULL (default).
OL-1110-23
3-137
Chapter 3
Table 3-16
VSPT Parameter Name
MML Parameter
Name
MGC SIP Version
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.
Local SIP Port
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
Maximum redirect count. Indicates the maximum number of SIP message

redirections allowed. Value range: any value greater than 0.
Default: 5
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.
Out Session Timer
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.
Support Reliable 100
SupportReliable100 Support reliable 100. Indicates if the MGC support reliable100 response
code. Values are: TRUE (default) or FALSE.
Retry After Timer
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
Maximum forwards. Indicates the maximum number of SIP forwards allowed.

Value range: any value greater than 0. Default: 70.
SIP-2 tab
3-138
OL-1110-23
Chapter 3

Table 3-16
VSPT Parameter Name

Mid Call Service
CustID
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.
NonInvite Req Attempts NonInviteReqAtte

mpts
Specifies the transmission times for SIP Non-INVITE request.Value range:

from 1 to 15. Default: 11.
Response Attempts
ResponseAttempts
Specifies the transmission times for SIP response.Value range: from 1 to 15.
Default: 11.
Retrans Method
RetransMethod
Specifies the re-transmission mode for SIP messages. Value:

1(exponential),2(linear). Default: 1.
Invite Wait Timer
InviteWaitTimer
Specifies the timer value (in milliseconds) for SIP waiting for final response
of INVITE request.Value range: from 10000 to 500000. Default: 200000.
SIP Ingress Routing

Control
sipIngressRoutingC Maps to trunk group property sipIngressRoutingControl. Defines the

ontrol
preferred SIP header used for initial routing decisions. Values are: 1 - Explicit
Route header; 2 - Request Line ; 3: To: header. Default: 1.
SIP Egress Routing

Control
sipEgressRoutingC
ontrol
Maps to trunk group property sipEgressRoutingControl. Defines the

preferred SIP header used for initial routing decisions during sending of the
initial INVITE. Values are: 1 - 5. Default: 0.
respectSipUriUserParm respectSipUriUserP Determines whether or not respect user=phone in p-asserted-id and

arm
remote-party-id header. Values: 0 (no) or 1 (yes). Default: 0.
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
OL-1110-23
3-139
Chapter 3
Figure 3-98
Step 2
Trunk Window
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
Enter the MCGP Domain.
Step 6
Enter the first trunk CIC Number.
Step 7
Select DS Format (optional).
Step 8
In the Slot Number drop-down menu, select the slot number.
Step 9
In the Subunit Number drop-down menu, select the subunit where you want to add trunks.
Step 10
Enter the DS1 number.
Step 11
Enter the first DS0 number.
Step 12
Enter the DS1 type. The trunk type is displayed.
Step 13
Select SS7, PRI FAS, or PRI NFAS and enter the appropriate properties:
SS7Enter the number of trunk members.
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.
Enter the number of trunk members in the trunk group.
OL-1110-23
3-141
Chapter 3
Step 15
Click More to add more trunks to other trunk groups.
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
Deleting Trunks from a Trunk Group

Use the following procedure to delete individual trunks from a trunk group:
Step 1
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
Select the individual trunks you want to delete:
Step 3
To delete all the trunks in a trunk group, click Delete All.
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.
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
OL-1110-23
3-143
Chapter 3
Figure 3-102
Adding a CodecString
Step 3
Enter a name.
Step 4
Enter the Codec String.
Step 5
Click Finish. A window similar to the one shown in Figure 3-103 displays.
Figure 3-103
CodecString Added
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
Figure 3-104
Adding a BearerCap
Step 3
Enter a name.
Step 4
Enter the Bearer Cap.
Step 5
Click Finish. A window similar to the one shown in Figure 3-105 displays.
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
Enter the profile value.
Step 5
Click OK. A window similar to the one shown in Figure Figure 3-107 displays.
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
Figure 3-108
Adding a Route
Step 3
Enter a route name.
Step 4
Select whether the Weighted Trunk Group is on or off.
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
Route Group Added
Adding Route Lists

A route list is a collection of routes that go to the same endpoint. Use the following procedure to add
route lists:
Step 1
Click Route Lists in the left pane of the main Cisco VSPT window.
Step 2
3-148
OL-1110-23
Chapter 3

Figure 3-110
Adding Route Lists
Step 3
Enter a route group name.
Step 4
To associate the route with a route group, select a route in the Available box.
Step 5
Click Select >>.
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
Hierarchical View of Provisioned Components

The results of the provisioning session you completed are visible in the hierarchical tree in the left pane
of the main Cisco VSPT window. You can expand the branches to view individual components (see
Figure 3-111).
OL-1110-23
3-149
Chapter 3
Performing an Integrity Check
Figure 3-111
Hierarchical Tree of Components

When provisioning is complete, you can perform an integrity check to prevent possible configuration
errors. The integrity check involves examining the following:
Integrity of MGC signaling configuration
Traffic against MGC configuration
Dial plan results
Each integrity check is explained in more detail in the following subsections.
Checking Integrity for an MGC Signaling Configuration

When you perform an integrity check for an MGC signaling configuration, the Cisco VSPT does the
following:
Checks that the hostname is specified for an MGC
Checks that login/passwords are specified for an MGC
Checks that MGC ipaddrs are specified
3-150
OL-1110-23
Chapter 3

Checks that if MGC failover is specified, the failover IPs are specified
Checks that the MGX hostname is specified
Checks that MGX logins and passwords are specified
Checks the MGX IPaddrs
For EXTNODES where it refers to an MGX, checks PeerAddrs on IPLNK to ensure that they are
addresses on the specified MGX
For IPFAS IPLNKS:

Ensures that SigSlot/SigPort are specified
Checks SigSlots and SigPorts on the MGX to ensure that they are valid as specified on the MGX
Ensures that MGC ports and MGX ports match on the IPLNK
Checks that all IPLNKs under a single IPFASPATH map to the same port number
Note
The number of IPFAS sessions utilizing a given port is displayed because some IPLNKs might
use different port IDs.
Checking Traffic Against an MGC Configuration

When you perform an integrity check of traffic against an MGC configuration, the Cisco VSPT does the
following:
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
OL-1110-23
3-151
Chapter 3
Figure 3-112
Step 2
Integrity Check
Indicate the tests you want to run, and click Start.

When the tests are finished, a window similar to the one shown in Figure 3-113 displays with the results
of the integrity checks performed.
Figure 3-113
Integrity Check Results
3-152
OL-1110-23
Chapter 3


The Cisco VSPT automatically generates the MML commands to provision your MGC and saves these
commands in a file to be executed when you deploy the configuration. To view the MML commands
generated from your Cisco VSPT provisioning session, select View > MML on the main Cisco VSPT
menu bar. A window displaying generated MML similar to the window shown in Figure 3-114 displays.
Figure 3-114
First Generated MML Window

When you finish defining a configuration, you must deploy that configuration to the MGC. A new
configuration should not be deployed during times of peak load on the MGC.
The new configuration can be deployed completely or in parts (incremental deployment). Deploying
incrementally allows you to verify each component type configuration before proceeding to the next
component deployment.
If you want to delete a component and plan to reuse the component name, first delete the component,
deploy the session, and verify that the component name has been deleted before reusing the name.
Use the following procedure to deploy a new configuration:
Step 1
Select Tools > Deploy from the main Cisco VSPT menu. A window similar to the one shown in
OL-1110-23
3-153
Chapter 3
Figure 3-115
Deploying a Configuration
Step 2
Enter the configuration name on the destination MGC.
Step 3
To incrementally deploy a configuration component type, click Advanced. A window similar to the one
Figure 3-116
Incremental Deployment Component Selector
Step 4
Select one or more component types to deploy, and click OK.
Step 5
Indicate how you want to deploy the configuration:
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.
3-154
OL-1110-23
Chapter 3

Backup and Restore
Step 6
Select the gateways you want to deploy, if applicable.
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
In a continuous-service configuration, the XECfgParm.dat file on each machine must be configured. If

you experience problems, verify that the XECfgParm.dat files on both machines are correct by following
the instructions in Chapter 2, Installing Cisco Media Gateway Controller Software, in the Cisco Media
Gateway Controller Software Installation and Configuration (Release 9.7).
Backup and Restore

The Cisco VSPT backup and restore tool allows a user to create, modify, and delete scheduled backups
and restores on a hourly, daily, weekly, or monthly basis, or on demand. Backup and restore activities
can be performed on any of the following devices that have been configured for the MGC:
MGC HostActive configuration
HSIActive configuration
CAT6509Configuration and image on flash
CAT5500Configuration and image on flash
CAT2900XLRunning-config and image on flash
ITPL2600Active configuration
BAMS P3Active configuration
OL-1110-23
3-155
Chapter 3
Backup and Restore
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
Schedule a Backup or Restore

Use the following procedure to open the Cisco VSPT backup and restore tool and to schedule an activity:
Step 1
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
Backup and Restore Utility
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.
3-156
OL-1110-23
Chapter 3

Backup and Restore
Figure 3-119
Note
Step 3
Scheduling a Backup or Restore
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:
OL-1110-23
3-157
Chapter 3
Backup and Restore
Figure 3-120
Note
Schedule an Activity
Available fields vary depending on the component selected.
Step 4
Select the action you want to perform in the Activity field. Valid choices include backup and restore.
Step 5
Enter the IP address of the MGC.
Step 6
Enter the MGC login and password.
Step 7
Enter a name for the backup file.
Step 8
Enter the IP address of the TFTP server.
Step 9
Enter the TFTP login and password.
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
Specify whether or not to use ssh connect.
Step 12
Select the schedule type. Valid choices include
Monthly
Daily
3-158
OL-1110-23
Chapter 3

Backup and Restore
Hourly
Weekly
Now
Later
Step 13
Select the hour and minute when the backup is to begin.
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
Display Activity Schedule
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.
Check Status of Backup or Restore

The Cisco VSPT generates status logs that provide information about each scheduled activity. The status
log displays the following information for the activity:
Date and time
Success or failure
File name on the TFTP server
Directory of configuration files
Image file name
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:
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
Click the backup or restore for which you want information.
Step 3
Select the appropriate button for the action you want to perform. Choices are:
Show status
Acknowledge
Clear

The Cisco BAMS provides enhanced billing and measurement functions corresponding to those found
in a traditional class 4 tandem switch. The Cisco BAMS server collects, formats, and stores billing and
measurement data from the MGC. The data can then be processed by a billing system and other
measurement collection and reporting systems. Cisco BAMS runs on a standalone server designed to
interface with the MGC.
.Figure 3-122 provides an overview of the Cisco BAMS components and their relationship to the MGC.
Figure 3-122
Cisco BAMS Overview
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
Imports configuration information from a host and exports it to the host
Deploys the current configuration to a host
Supports incremental deployment
Displays the current MML batch file
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
The Cisco VSPT provisions a Cisco BAMS by using the following:
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
Trunk group provisioning

Define trunk groups that map to trunk groups on the MGC. Used to define default originating
and terminating NPAs and the number of circuits in a trunk group.

Defines SigPath table for a Dial configuration, because Dial configurations have no trunk
groups, routing files, or dial plans. Map SigpathID/Bearer Channel Numbers to Trunk Group
Number/Member Numbers.
Measurements provisioningConfigure thresholding alarms by means of the Threshold Crossing

Alarms table (TCA-TBL).
The following tags for BAMS 3.0 are available:
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.
OL-1110-23
3-161
Chapter 3

Use the following procedure to start a Cisco VSPT BAMS provisioning session:
Step 1
Start and log in to the Cisco VSPT.
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
Cisco BAMS Configuration Window
Step 4
Select File > New from the menu bar.
Step 5
Enter a name for the provisioning session you are creating, and click OK. A window similar to the one
3-162
OL-1110-23
Chapter 3

Figure 3-124
Step 6
New Configuration Wizard
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.
OL-1110-23
3-163
Chapter 3
Cisco BAMS Server Configuration
Figure 3-125
Cisco BAMS Configuration
Step 7
Enter a BAMS IP address in the BAMS Hostname field.
Step 8
Enter a Cisco BAMS login ID and password.
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
Click Modify, and begin the Cisco BAMS provisioning.

This section provides directions for using the Cisco VSPT to configure a Cisco BAMS server. The Cisco
VSPT performs the following procedures:
Provisioning General BAMS Information, page 3-165
Provisioning Zones, page 3-169
Provisioning Trunk Group Information, page 3-175
Provisioning Measurements, page 3-178
Provisioning Other, page 3-180
Provisioning System, page 3-188
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.
Provisioning General BAMS Information

Provisioning general Cisco BAMS information includes defining country codes, map types, and tollfree
prefixes. Use the following procedure to provision general Cisco BAMS information:
Step 1
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
Cisco BAMS Configuration, Country Codes
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
Step 5
Add Country Code
Country Code Added
Click Maptypes. A window similar to the one shown in Figure 3-129 displays.
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 BAMS Configuration, Maptype
Maptype Information Added
Click Tollfree. A window similar to the one shown in Figure 3-131displays.
OL-1110-23
3-167
Chapter 3
Figure 3-131
Step 8
Cisco BAMS Configuration, Tollfree
Click Get Default. A window similar to the one shown in Figure 3-132 displays.
Figure 3-132
Tollfree Information Added
3-168
OL-1110-23
Chapter 3

Step 9
If you want to add more toll-free prefixes, click Add.
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
Cisco BAMS Configuration, Identification
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
Step 5
Add Zone Information
Zone Identification Added
Click Membership. A window similar to the one shown in Figure 3-136 displays.
3-170
OL-1110-23
Chapter 3

Figure 3-136
Step 6
Cisco BAMS Configuration, Membership
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
Select one or more, and click OK.
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.
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
Membership Information Added
Cisco BAMS Configuration, Relationships
3-172
OL-1110-23
Chapter 3

Figure 3-140
Add Rating Type
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
Figure 3-141
Step 16
Rating Type Information Added
Click Exceptions. A window similar to the one shown in Figure 3-142 displays.
OL-1110-23
3-173
Chapter 3
Figure 3-142
Step 17
Cisco BAMS Configuration, Exceptions
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
3-174
OL-1110-23
Chapter 3

Figure 3-144
Exceptions Added
Provisioning Trunk Group Information

Provisioning trunk group information includes
Defining trunk groups that map to trunk groups on the MGC
Specifying default origination and termination NPAs and the number of circuits in the trunk group
Defining a SigPath table for dial configurations
Use the following procedure to provision trunk group information:

Step 1
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.
OL-1110-23
3-175
Chapter 3
Figure 3-145
Step 3
Cisco BAMS Configuration, Trunk Groups
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
3-176
OL-1110-23
Chapter 3

Figure 3-147
Step 8
Trunk Group Added
Click Sigpath. A window similar to the one shown in Figure 3-148 displays.
Figure 3-148
Cisco BAMS Configuration, Sigpath
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.
OL-1110-23
3-177
Chapter 3
Figure 3-149
Step 11
Add Sigpath Set
Enter the Sigpath ID in hexadecimal, select the trunk group number, and click OK. A window similar to
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:
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
Cisco BAMS Configuration, Thresholds
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.
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.
3-180
OL-1110-23
Chapter 3

Figure 3-153
Cisco BAMS Configuration, ALM-PARMS
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
Click Modify. The BAMS configuration for the ALM-PARMS is set.
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.
OL-1110-23
3-181
Chapter 3
Figure 3-154
Cisco BAMS Configuration, NODE-PARMS
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 NODE-PARMS is set.
Provisioning POLL
Use the following procedure to provision Cisco BAMS poll parameter information:
Step 1
hierarchical tree.
Step 2
Click POLL. A window similar to the one shown in Figure 3-155 displays.
3-182
OL-1110-23
Chapter 3

Figure 3-155
Cisco BAMS Configuration, POLL
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
hierarchical tree.
Step 2
Click SKIPCDB.
Step 3
OL-1110-23
3-183
Chapter 3
Figure 3-156
Adding the SKIPCDB Code
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
Cisco BAMS Configuration, SKIPCDB
Provisioning SKIPCDE
Use the following procedure to provision Cisco BAMS skip call data element (CDE) parameter
information:
3-184
OL-1110-23
Chapter 3

Step 1
hierarchical tree.
Step 2
Click SKIPCDE.
Step 3
Figure 3-158
Adding the SKIPCDE Code
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
Figure 3-159
Cisco BAMS Configuration, SKIPCDE
OL-1110-23
3-185
Chapter 3
Provisioning P01FILTER
Use the following procedure to provision Cisco BAMS P01Filter parameter information:
Step 1
hierarchical tree.
Step 2
Click P01Filter. A window similar to the one shown in Figure 3-160 displays.
Figure 3-160
BAMS Configuration, P01Filter
Step 3
In the Answered drop-down menu, select Set(1), Filter(0), or Ignore.
Step 4
In the No Answer drop-down menu, select Set(1), Filter(0), or Ignore.
Step 5
In the Busy drop-down menu, select Set(1), Filter(0), or Ignore.
Step 6
In the Other drop-down menu, select Set(1), Filter(0), or Ignore.
Step 7
Click Modify. The BAMS configuration for the P01Filter is set.
Provisioning SWITCHINFO
Use the following procedure to provision the Cisco BAMS switch information parameters:
Step 1
hierarchical tree.
Step 2
Click SWITCHINFO. A window similar to the one shown in Figure 3-161 displays.
3-186
OL-1110-23
Chapter 3

Figure 3-161
Cisco BAMS Configuration, SWITCHINFO
Step 3
Enter the switch information value in the dialog box for the switch you are using.
Step 4
Click Modify. The BAMS configuration for the SWITCHINFO is set.
Provisioning BIN1110
Use the following procedure to provision BAMS BIN1110 information parameters:
Step 1
hierarchical tree.
Step 2
Click BIN1110. A window similar to the one shown in Figure 3-162 displays.
OL-1110-23
3-187
Chapter 3
Figure 3-162
Cisco BAMS Configuration, BIN1110
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
Enter the select File Suffix name.
Step 6
Click Modify. The BAMS configuration for the BIN1110 is set.
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.
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
Cisco BAMS Configuration, MSC-PARMS
Step 3
Click the Add button. A window simialar to the one in Figure 3-164 displays.
Step 4
Enter the desired MSC-PARMS values in the dialog box.
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
hierarchical tree.
Step 2
Click MSC-THRES. A window similar to the one shown in Figure 3-165 displays.
3-190
OL-1110-23
Chapter 3

Figure 3-165
Cisco BAMS Configuration, MSC-THRES
Step 3
Enter the desired MSC-THRES value in the dialog box.
Step 4
Click Modify. The BAMS configuration for the MSC-THRES is set.
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
hierarchical tree.
Step 2
Click SYS-ALM-PARMS. A window similar to the one shown in Figure 3-166 displays.
OL-1110-23
3-191
Chapter 3
Figure 3-166
Cisco BAMS Configuration, SYS-ALM-PARMS
Step 3
Enter the desired SYS-ALM-PARMS value in the dialog box.
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
Click Modify. The BAMS configuration for the SYS-ALM-PARMS is set.
3-192
OL-1110-23
CH A P T E R
MML Basics
This chapter describes how to use Man-Machine Language (MML) commands to configure the
Cisco PGW 2200 Softswitch. It includes the following sections:
Working with MML, page 4-1
MML Configuration Commands, page 4-3
Working with MML Session Commands, page 4-6
Working with Provisioning Commands, page 4-15
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.
Working with MML

You must start an MML session before you can start a provisioning session. MML interfaces with the
Provisioning Object Manager (POM). The POM requires an active provisioning session to make
provisioning changes. During an active session, the POM locks all the data files to prevent other users
from making changes.
You must start an MML session before you can start a provisioning session.
If a provisioning session is running, you cannot start another provisioning session. To see if another
provisioning session is running, use the PROV-RTRV command (refer to the Retrieving Provisioning
Session Information section on page 4-33).
Keep the following tips in mind when working with MML.
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
Keywords do not need to be enclosed in quotes ( ).
OL-1110-23
4-1
Chapter 4
MML Basics
Working with MML
Tip
Use only one MML command on each line.
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.
4-2
OL-1110-23
Chapter 4
MML Basics
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.

There are three types of MML configuration commands:
Caution
Configuration session commandsUse session commands to work with entire provisioning data
filesets. The session commands are described in Table 4-1.
Configuration provisioning commandsUse provisioning commands to perform actions on

components or parameters affecting a specific data file. The provisioning commands are described
in Table 4-2.
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
MML Configuration Session Commands
CommandExplanation
Description
PROV-STAStart Provisioning
Session
Starts a provisioning session to create a new configuration or

to modify an existing configuration. The POM locks the data
files to prevent other users from making changes.
Note
PROV-CPYCopy Provisioning
Session
The PROV-STA command cannot be performed on the

standby Cisco PGW 2200 Softswitch.
Copies configuration settings from the current provisioning

session to the active Cisco PGW 2200 Softswitch in a single
Cisco PGW 2200 Softswitch configuration, activates the
configuration, and then terminates the current provisioning
session. Requires an open provisioning session.
Note
You can use PROV-CPY on dual systems to change

the configuration of one machine (for example, during
upgrading). Use the PROV-SYNC command to
resynchronize both machines.
Note
The PROV-CPY command cannot be performed on

the standby Cisco PGW 2200 Softswitch.
Note
The PROV-CPY command terminates the current

provisioning session only if it is successfully executed.
OL-1110-23
4-3
Chapter 4
MML Basics
Table 4-1
MML Configuration Session Commands (continued)
CommandExplanation
Description
PROV-DPLYDeploy Provisioning
Session
Copies configuration settings from the current provisioning

session to both MGCs in a dual Cisco PGW 2200 Softswitch
configuration, activates the configuration, and then terminates
the current provisioning session. Requires an open
provisioning session.
PROV-SYNCSynchronize
Provisioning Data
Note
The PROV-DPLY command terminates the current

provisioning session only if it is successfully executed.
Note
Use the PROV-DPLY command to commit SS7

provisioning changes.
Copies the active configuration (in the CONFIG_LIB) from

the active Cisco PGW 2200 Softswitch side to the standby side
in a dual Cisco PGW 2200 Softswitch configuration to ensure
that both sides are using the same configuration.
Note
You cannot perform a PROV-SYNC command in an

open provisioning session. You must stop the
provisioning session before using the PROV-SYNC
command.
Note
After adding a signaling link or CIC, perform a reboot

of the standby system to synchronize the new objects
in the active system to the standby system. Not
rebooting the standby system can cause the loss of
calls after a switchover.
Caution
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.
4-4
OL-1110-23
Chapter 4
MML Basics
Table 4-1
MML Configuration Session Commands (continued)
CommandExplanation
Description
PROV-STPStop Provisioning
Session
Stops the provisioning session and saves the configuration. It

releases the lock on the configuration data files, but does not
activate the new configuration.
PROV-EXPExport Configuration
Data
Exports current configuration data routing plans, dial plans,

configuration, or all three in MML-command form to the
directory /opt/CiscoMGC/etc/cust_specific/directory name
where the files names are:
all (exports the entire Cisco PGW 2200 Softswitch
configuration)
Note
The prov-exp:all MML command creates a

properties.dat file that is used only by VSPT to display
the default values. This file is not used by the
config.mml (core configuration information with trunks and

trunk groups)
export_trkgrp.dat (if trunk groups are defined, only trunk
group data)
export_trunks.dat (if trunks are defined, only trunk data)
numan.mml (dial plan only)
routing.mml (routing only)
custGrpID.mml (for dial plans)
Table 4-2
MML Configuration Provisioning Commands
CommandExplanation
Description
PROV-ADDAdds a Component
Adds a component to the Cisco PGW 2200 Softswitch

configuration.
PROV-DLTDeletes a Component
Deletes a provisioned component.

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.
PROV-EDEdits a Component
Edits a provisioned component.
PROV-RTRVRetrieves a
Component
Retrieves the information about an existing provisioning

session, variants, or all components.
Note
For more information on these commands, refer to the Cisco PGW 2200 Softswitch Release 9
MML Command Reference.
OL-1110-23
4-5
Chapter 4
MML Basics
Working with MML Session Commands
Table 4-3
MML Configuration Bulk Export Command
CommandExplanation
Description
PROV-EXPExport Configuration Data
Exports current core configuration data (signaling

paths, SS7 nodes, and so on) with or without
trunks and trunkgroup definitions, routing plans,
dial plans, trunkgroups, trunks, or all in one
directory.
Note
When using the prov-exp command,

default values are not listed in the
exported configuration.
MML-command form to the directory

/opt/CiscoMGC/etc/cust_specific/directory_
name where the files names are:
config (includes trunks and trunkgroup
definitions)
routing
numan
trkgrp
trunks
all

Use session commands to work with the entire set of provisioning data files.
Starting a Provisioning Session

Use the PROV-STA command to start a provisioning session when you want to:
Create a new configuration.
Modify an existing configuration.
Modify an existing configuration and save it as another version.
Copy a provisioning session, deploy a provisioning session, or synchronize a provision session.
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.
4-6
OL-1110-23
Chapter 4
MML Basics
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.
Creating a New Provisioning Configuration

To create a new configuration, use the PROV-STA command as follows:
Command
Purpose
mml> prov-sta::srcver="new",dstver="ver1"
Starts a new provisioning session (new),

names it CFG_ver1, and saves the
configuration files at
/opt/CiscoMGC/etc/CONFIG_LIB/CFG_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.
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.
Overwriting an Existing Inactive Configuration

To overwrite an existing inactive configuration, use the PROV-STA command as follows:
Command
Purpose
mml> prov-sta::srcver="ver1",dstver="ver1"
Starts a provisioning session, opens the

existing configuration named ver1, and
overwrites that configuration.
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
Modifying and Activating a Configuration

To modify an existing configuration and save it as another version, use the PROV-STA command as
follows:
4-8
OL-1110-23
Chapter 4
MML Basics
Command
Purpose
mml> prov-sta::srcver="active",
dstver="ne_active"
Starts a provisioning session, selects the

active configuration as the source for
configuration change, and saves the
configuration as new_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
Modifying an Existing Configuration and Saving It as Another Version

To modify an existing configuration and save it as another version, use the PROV-STA command as
follows:
Command
Purpose
mml> prov-sta::srcver="ver1",dstver="ver2"
Starts a provisioning session, opens the

existing configuration named ver1, and
saves the configuration as ver2.
Use the PROV-RTRV command to verify that the existing configuration has been saved as another
version.
Tip
Committing a Provisioning Session to a Single Cisco PGW 2200 Softswitch

To direct the POM to make the data files that belong to the current provisioning session operational on
a single Cisco PGW 2200 Softswitch and then terminate the POM session, use the PROV-CPY
command as follows:
OL-1110-23
4-9
Chapter 4
MML Basics
Tip
Command
Purpose
mml> PROV-CPY
Copies configuration settings from the

current provisioning session to the active
Cisco PGW 2200 Softswitch in a single
configuration, and then activates the
configuration.
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.
Deploying a Provisioning Session to Dual MGCs

To (1) direct the POM to make the data files that belong to the current POM session operational, (2) copy
the data files to the standby Cisco PGW 2200 Softswitch, and (3) terminate the POM session, use the
PROV-DPLY command as follows:
Command
Purpose
mml> PROV-DPLY
Copy configuration settings from the current

provisioning session to both MGCs in a dual
Cisco PGW 2200 Softswitch configuration, and
then activate the configuration.
Tip
A provisioning session not active for 30 minutes results in a warning. If the session continues without
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.
Synchronizing Configuration Data

To synchronize the configuration data between two MGCs, use the PROV-SYNC command as follows:
4-10
OL-1110-23
Chapter 4
MML Basics
Command
Purpose
mml> PROV-SYNC
Copies the configuration data from the

active Cisco PGW 2200 Softswitch side
to the standby side to ensure that both
sides are using the same configuration.
Note
Set pom.dataSync to true in

XEcfgParm.dat for prov-sync.
Note
After adding a signaling link or

CIC, perform a reboot of the
standby system to synchronize
the new objects in the active
system to the standby system. Not
rebooting the standby system can
cause the loss of calls after a
switchover.
Caution
Due to differences in software

file formats, do not use the
PROV-SYNC command
between
platforms that have different
software revision levels.
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.
Stopping a Configuration Session

To save all changes made during the configuration session and terminate the session with the POM, use
the PROV-STP command as follows:
OL-1110-23
4-11
Chapter 4
MML Basics
Command
Purpose
mml> PROV-STP
Stop the provisioning session and save

your configuration changes to the
destination version specified when the
session was started.
mml> PROV-STP:<session name>:confirm
Stop a provisioning session started from

another MML session.
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.
Performing a Manual Switchover

To switch over from an active to a standby system, use the SW-OVER command as follows:
Command
Purpose
mml> sw-over::CONFIRM
Performs a manual switchover to a

standby system platform.
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.
Exporting Configuration Data

The following are key points to understand when you are exporting routing and dial plan information:
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:
4-12
OL-1110-23
Chapter 4
MML Basics
Command
Purpose
mml> prov-exp:config:dirname=saved_config
Exports configuration data in MML format to

the directory:
/opt/CiscoMGC/etc/cust_specific/saved_config
The directory contains the MML commands for
all of the configuration data.
mml> prov-exp:routing:dirname=saved_config
Exports routing data in MML format to the

directory:
The directory contains the MML add/edit
commands for all of the data in the route
analysis file.
mml> prov-exp:numan:dirname=saved_config
Exports dial plan data in MML format to the

directory:
The directory contains MML commands for all
of the data in the dial plan. The first line of the
created file will contain an MML command to
create the dial plan.
mml> prov-exp:all:dirname=saved_config
Exports configuration, routing, and dial plan

data in MML format to the directory:
The directory contains the MML commands for
all of the data in the configuration, route
analysis, and dial plan files.
Examine the exported data to verify the configuration data.

If trunks and trunk groups are defined, a file for the trunks and a file for the trunk groups will also be
generated as part of the command to export configuration data. The files export_trunks.dat and
export_trkgrp.dat are placed in the same directory created by the initial PROV-EXP command.
To export the MML trunk group file, use the following MML commands:
mml> prov-add:files:name=TKGFile,file=trunkGroupCust.dat,action=export
mml> prov-ed:files:name=TKGFile,file=trunkGroupCust.dat,action=export
Importing Saved MML Configuration Data

To import previously exported configuration data (from the directory saved_config in the previous
procedure), you can use batch MML configuring as described in this section.
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.
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
Stop the standby Cisco PGW 2200 Softswitch.
Step 2
Stop the active Cisco PGW 2200 Softswitch.
Step 3
On the previously active system, clear the existing provisioning:

a.
Log in as mgcusr.
b.
Navigate to the etc directory:

cd /opt/CiscoMGC/etc
c.
Make a backup of the XECfgParm.dat file by copying it to a temporary directory:

cp XECfgParm.dat /tmp/XECfgParm.dat
d.
Remove the .dat and .link files:

rm *.dat
rm *link
e.
Copy the new configuration files:

cp /opt/CiscoMGC/etc/CONFIG_LIB/new/*.dat /opt/CiscoMGC/etc/
f.
Restore the XECfgParm.dat file.

cp /tmp/XECfgParm.dat ./
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
Start the previously active system.
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.
Combine the files:

cat config.mml routing.mml <CustGrpID>.mml
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.
Enter the following commands to import the combined provisioning file:

mml
prov-sta::srcver=new,dstver=mmlImport, confirm
quit
mml b all-config.mml
mml
prov-cpy
Step 7
Start the standby system.
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.

Use provisioning commands to work with components, parameters, and properties.
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, page 4-15
Modifying a Component, page 4-16
Deleting a Component, page 4-17
Overriding Component Properties, page 4-17
Changing Overridden Properties, page 4-18
Retrieving All Components, page 4-29
Retrieving an Individual Component, page 4-30
Retrieving a Component Based on Signaling Service, page 4-30
Retrieving Provisioning Session Information, page 4-33
Adding a Component
To add a component to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD command
as follows:
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",
Add a point code with the MML name of

dpc1, a net address (point code) of 0.0.1,
and a net indicator of 2, and a component
description of the point code for DPC1.
To verify the new component, use the PROV-RTRV command.
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 point codes (OPC, DPC, and APC)
Add linksets
Add IP links
Add SS7 routes
Add SS7 subsystem
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"
Changes the description of a provisioned

point code named opc1.
After you enter the command to modify a component, the component is changed. To verify the change,
use the PROV-RTRV command.
4-16
OL-1110-23
Chapter 4
MML Basics
Tip
Enter only those parameters that you want to modify.
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"
Deletes the point code component named

opc1.
To verify that the component is removed, use the PROV-RTRV:ALL command.
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.
Overriding Component Properties

To override component properties for an existing provisioning component, use the PROV-ADD
command as follows:
Step
Command
Purpose
mml> prov-add:propertyType:name=" name",

property=value
Each command adds a property to a

different signaling service.
mml> prov-add:sigsvcprop:name="ss7srv1",
alarmcarrier="1"
The property override value is added to

the configuration the current session is
modifying.
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.
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.
Changing Overridden Properties

To modify a provisioning object within the data files, use the PROV-ED command as follows:
Command
Purpose
mml> prov-ed:sigsvcprop:NAME="ss7srv1",
alarmcarrier="2"
Change the SS7 signaling service

(ss7srv1) overridden property (alarm
carrier) value to 2 for a different alarm
carrier (hardware carrier).
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
Modified value takes effect without restart
ACCRespCatName
Yes
ACCRespCntlInhibit
No
ACLDur
No
ADigitCCPrefix
Yes
4-18
OL-1110-23
Chapter 4
MML Basics
Table 4-4
Provisionable Properties (continued)
adjDestinations
No
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
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
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
4-20
OL-1110-23
Chapter 4
MML Basics
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
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
4-22
OL-1110-23
Chapter 4
MML Basics
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
No
NetworkType
Yes
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
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
Yes
SendAddressInCgpn
Yes
sendAfterRestart
No
SendDtmfBeforeConnect
Yes
serviceCodeInclude
Yes
sgcpRetxCount
No
sgcpRetxTimer
No
SipIPSource
Yes
sipMimeBodySupport
Yes
SipReferForSingleStepXfer
Yes
4-24
OL-1110-23
Chapter 4
MML Basics
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
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
4-26
OL-1110-23
Chapter 4
MML Basics
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
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
4-28
OL-1110-23
Chapter 4
MML Basics
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
Retrieving All Components

To retrieve all configured components, use the PROV-RTRV command as follows:
Command
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"
*/
Displays all configured

components. A
provisioning session is
not required.
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"
OL-1110-23
4-29
Chapter 4
MML Basics
Tip
components.
Retrieving All Components of a Specific Type

To retrieve all the components of a specific type, use the PROV-RTRV command as follows:
Command
Purpose
mml> prov-rtrv:card:"ALL"
Retrieves all the components associated

with the component named card.
Retrieving an Individual Component

To display an individual component that is configured on the Cisco PGW 2200 Softswitch, use the
PROV-RTRV command as follows:
Tip
Command
Purpose
mml> prov-rtrv:enetif:name="en2"
Retrieves the attributes associated with

the Ethernet interface component named
en2.
components.
Retrieving a Component Based on Signaling Service

To display a component that is based on the signaling service and is configured on the
Cisco PGW 2200 Softswitch, use the PROV-RTRV command as follows:
Command
Purpose
mml> prov-rtrv:iplnk:svc="mgcpsvc1"
Retrieves the IP links associated with the

signaling service for mgcpsvc1.
You can use the following provisioning commands to retrieve information based on the signaling service
or trunk group.
IP linksRetrieve the IP links associated with the named signaling service.

mml> prov-rtrv:iplnk:srcsvc="mgcpsvc1"
Nailed trunkRetrieve all nailed trunks associated with the named (source or destination) signaling
service.
4-30
OL-1110-23
Chapter 4
MML Basics
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"
Retrieving Protocol Variants

To retrieve the signaling protocol variants available on the Cisco PGW 2200 Softswitch, use the
PROV-RTRV:VARIANTS command as follows:
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
To display the signaling protocol variants

on the Cisco PGW 2200 Softswitch.
Note
The list to the left is for example

purposes only and is not complete
and may not reflect all the
protocols available for your
software version. For more
information on protocol families,
refer to the Cisco Media Gateway
Controller Software Release 9
Installation and Configuration
(Release 9.7).
*/
Tip
A provisioning session is not required to retrieve protocol variants.
Note
The protocol variants displayed may vary depending on the software revision you are using.
4-32
OL-1110-23
Chapter 4
MML Basics
Retrieving Provisioning Session Information

To obtain information about the provisioning session, for example, if there is an active session, use the
PROV-RTRV command as follows:
Command
Purpose
mml> prov-rtrv:session
To display information about the

Creating a Batch File

You can create a file of MML provisioning commands for use as a batch file. All commands go into a
single ASCII text file and, when read by MML, the commands are executed sequentially.
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
Sample MML Provisioning Batch File
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-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.
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
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.
Executing a Batch File

To start executing the batch file, use the following UNIX command as follows:
Command
Purpose
mml -b path/filename.ext
To execute the MML commands in the

batch file.
Replace the path parameter with the
absolute path to the file, and replace the
filename.ext parameter with the filename
of the batch file containing the
provisioning commands.
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>
4-34
OL-1110-23
Chapter 4
MML Basics
MML_INFO_COMMAND: MML Command

mml> sta-aud
Media Gateway Controller - MGC-01 2001-01-08 04:10:06
M RTRV
SABT
/* Status, Command Aborted - Command has timed out
without successful completion of operation
Some operations may have completed successfully */
va-cerulean%
OL-1110-23
4-35
Chapter 4
MML Basics
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:
Adding SS7 Signaling Route Components, page 5-2
Adding Signaling Link Components, page 5-12
Adding Media Gateway Control Links, page 5-14
Adding Trunks, Trunk Groups, and Routing, page 5-26
Adding SIP Components, page 5-46
Adding SIP-T and SIP-GTD Support, page 5-55
Adding Location Labels, page 5-66
Scaling System Components, page 5-75
Provisioning Examples, page 5-78
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 point codes (OPC, DPC, and APC)
Add linksets
Add links (IP or SIP)
Add SS7 routes
Add SS7 subsystem
OL-1110-23
5-1
Chapter 5
Adding SS7 Signaling Route Components
This chapter also provides basic provisioning procedures for the following features on the
Cisco PGW 2200 Softswitch Release 9.7(3):
A-number Country Code Digit Removal, page 5-83
Call Reporting, page 5-84
CODEC Capabilities and DTMF Preferential Routing, page 5-84
Digit Buffering for International Gateways, page 5-85
DPNSS Service Interworking with Cisco CallManager Over QSIG Tunneling, page 5-85
Enhanced Local Number Portability and Dial Plan Selection, page 5-96
Full Number Translations, page 5-97
Global Titles, page 5-97
Provisioning H.248 Protocol, page 5-98
Lawful Intercept, page 5-100
Location Mapping, page 5-102
Multiple Inbound IP Trunks, page 5-106
Support of HSI Non-RAS Mode, page 5-108
Presentation Number Modification, page 5-110
RADIUS Enhancement for Accounting, page 5-112
SIP and ISUP Interworking for Call Hold and Terminal Portability, page 5-113
SIP Overlap Signaling, page 5-113
SIP Remote Party ID and P-Asserted Support, page 5-114
SIP Service Handling and Feature Interworking Enhancement, page 5-116
Take Back and Transfer, page 5-117
QoS for Signaling Traffic, page 5-119

Your first task is to configure SS7 signaling routes that link the Cisco PGW 2200 Softswitch to the SS7
network nodes (signaling points). This process is described in the following sections:
Note
Adding a Destination Point Code, page 5-3
Adding an Adjacent Point Code, page 5-8
Adding a Linkset, page 5-8
Adding an SS7 Subsystem, page 5-9
Adding an SS7 Route, page 5-10
Adding an SS7 Signaling Service, page 5-11
Adding a FAS Signaling Service, page 5-11
When provisioning, fully define all components before deploying a configuration.

To add a component, do the following:
5-2
OL-1110-23
Chapter 5

Step 1
Start an MML session.
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
Enter the following command:

mml> prov-add:componentType:name="name",desc="description",paramName=value
Where:
componentType is the type of component you want to create,
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.
value is the parameter value of the component.
Adding a Destination Point Code

A point code is an SS7 network address that identifies an SS7 network node, such as a switch, SCP, STP,
or SSP. Its MML name is DPC. A point code can be the Cisco PGW 2200 Softswitch originating point
code (OPC), the adjacent point code (APC), or the destination point code (DPC) of a remote node with
which the Cisco PGW 2200 Softswitch communicates.
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
mml> prov-add:dpc:name="dpc2",netaddr="214.110.90",netind=2,desc="Dest Switch 1"
Step 3
Tip
Use the PROV-RTRV command to verify the OPC was added.
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.
OL-1110-23
5-3
Chapter 5
Adding Multiple OPCs

Depending on your system configuration, you may have to assign more than one OPC to a single
Cisco PGW 2200 Softswitch. When adding multiple OPCs, keep the following information in mind.
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 true OPC, there can be a maximum of 8 capability OPCs.
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.
Enter the OPC before creating the C7 IP link.
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 16 linksets can be included per Control Channel.
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
mml> prov-add:opc:name="opc1",desc="OPC1",netaddr="1.2.1",netind=2,type="trueopc"
Step 2
mml> prov-add:opc:name="opc1a",desc="CAPOPC",netaddr="1.2.2",netind=2,type="capopc",
trueopc="opc1"
Step 3
Use the PROV-RTRV command to verify the OPC was added.
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"
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-cpy
prov-stp
Understanding Point Code Addressing

Point codes are used in SS7 networks as addresses for each element. The following three different point
code address lengths are used in SS7 networks.
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).
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:
14-Bit Address (ITU), page 5-6
16-Bit Address (Japan), page 5-7
24-Bit Address (ANSI and China), page 5-7
Cisco PGW 2200 Softswitch Point Code Storage, page 5-8
14-Bit Address (ITU)

The 14-bit address is used to identify point codes in countries that conform to the ITU SS7
recommendations. In ITU SS7 networks, there are two types of point code: International and National.
International point codes always conform to the format (3-bits/8-bits/3-bits or 3-8-3) defined in ITU
Recommendation Q.704, which is illustrated in Figure 5-1. There are many formats used to define
National point codes. For example, the Singapore National point code format is 6-4-4. The formats for
National point codes are defined in each ITU SS7 National variant recommendation.
Figure 5-1
13
12
14-bit Address Point Code Format - International Point Code
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.
Converting National Point Codes To International Point Code Values

The key to converting ITU National point codes to ITU International point code values is knowing the
format of the National point codes, which can be found in the National SS7 variant recommendations.
To convert an ITU National point code to an International point code value, perform the following steps:
Step 1
Convert the decimal value of the National point code into binary, using the associated point code format
as a reference.
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.
16-Bit Address (Japan)

A 16-bit address is used to identify point codes in Japan. There are two standards agencies in Japan, the
Telecommunications Technology Committee (TTC) and Nippon Telephone and Telegraph (NTT). The
16-bit address point code format is defined in the JT-Q704 and NTT-Q704-b recommendations. These
documents divide the point code into three fields (7-4-5), as seen in Figure 5-3.
Figure 5-2
15
14
16-bit Address Point Code Format
13
12
11
10
Signaling point identification

(Unit Number)
7 bits
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.
24-Bit Address (ANSI and China)

The 24-bit address is used to identify point codes in China and countries that conform to the ANSI SS7
recommendations. The 24-bit address is divided into three 8-bit fields (8-8-8), as defined in the Chinese
GF001-9001 and ANSI T1.111.4 recommendations, which can be seen in Figure 5-3.
OL-1110-23
5-7
Chapter 5
Figure 5-3
23
24-bit Address Point Code Format
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
Signaling Point identification

(Member Octet)
8 bits
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.
Cisco PGW 2200 Softswitch Point Code Storage

The Cisco PGW 2200 Softswitch uses a 32-bit field to store point code addresses. When you provision
a point code on the Cisco PGW 2200 Softswitch, the format used depends upon the associated protocol.
The Cisco PGW 2200 Softswitch software pads the unused bits in the field with zeros when the point
code is saved.
For example, if you provisioned a DPC of 6.198.3 for an ITU SS7 network, it would have a binary
equivalent of 110.11000110.011, and would be stored in the Cisco PGW 2200 Softswitch as
00000000000000000011011000110011.
Adding an Adjacent Point Code

An adjacent point code (APC) defines an SS7 STP through the Cisco PGW 2200 Softswitch to which it
is connected. The APC is the SS7 network address of the STP. Its MML name is APC.
For information on point code parameters, refer to Table 2-2 on page 2-14.
To add an APC to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD command as
follows:
mml> prov-add:apc:name="STP-A",netaddr="214.111.0",desc="STP A pointcode",netind=2,
type="trueopc"
Use the PROV-RTRV command to verify the APC was added.
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
mml> prov-add:lnkset:name="linkset1",desc="linkset 1 to STP-A",apc="STP-A",type="IP",
proto="SS7-ANSI"
Step 2
5-8
OL-1110-23
Chapter 5

mml> prov-add:lnkset:name="linkset2",desc="linkset 2 to STP-B",apc="STP-B",type="IP",

proto="SS7-ANSI"
Step 3
Tip
Use the PROV-RTRV command to verify the linkset was added.
Setting up linksets is a two-step process that consists of first adding the linkset and then adding links to
the linkset.
Adding a Linkset Property

Linksets have a number of properties associated with them. Using the linkset property MML command,
properties for a linkset can be changed one at a time or several at one time. Its MML name is
LNKSETPROP. For information on linkset parameters, refer to Table 2-3 on page 2-15.
To add a linkset property to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD
command as follows:
mml> prov-add:lnksetprop:name="SS7-ANSI",layerRetries="6",layerTimer="6",
sendAfterRestart="6", slsTimer="6",sstTimer="302",dialogRange="2",standard="ITU90"
Adding an SS7 Subsystem

The SS7 subsystem is a logical entity that mates two STPs. When two STPs are defined as mates within
the Cisco PGW 2200 Softswitch, the controller can use either STP for communications to a destination
device. Its MML name is SS7SUBSYS. For information on SS7 subsystem parameters, refer to Table 2-5
on page 2-20.
To add an SS7 subsystem to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD
command as follows:
Step 1
mml> prov-add:ss7subsys:name="mate1",svc="STPA",matedapc="STPB",proto="SS7-ANSI",pri=1,
desc="mate STPA to STPB"
Step 2
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
OL-1110-23
5-9
Chapter 5
mml> prov-add:SS7ROUTE:NAME="ss7rte2-la",DESC="SS7 route set on ls2 to LA switch",

OPC="opc-itxc-la",DPC="dpc-la",LNKSET="ls2",PRI=1
mml> prov-add:SS7ROUTE:NAME="route-STPA",DESC="route to STPA",OPC="opc-itxc-la",
DPC="stpA-5-83-231",LNKSET="ls1",PRI=1
mml> prov-add:SS7ROUTE:NAME="route-stpB",DESC="route to STPB",OPC="opc-itxc-la",
DPC="STPB-5-83-230",LNKSET="ls2",PRI=1
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.
Adding Subsystem Numbers

You can also use the SS7 subsystem to define an SCP using TCAP. For TCAP applications,
TRANSPROTO is set to TCPIP and the subsystem number is set to a value greater than 0 to support AIN.
You also must set STPSCPIND to route to the appropriate SCP. For information on SS7 subsystem
parameters, including STPSCPIND, refer to Table 2-5 on page 2-20.
To add a subsystem number to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD
command as follows:
Step 1
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
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.
Adding an SS7 Route

An SS7 route is a path from the Cisco PGW 2200 Softswitch to another Cisco PGW 2200 Softswitch or
SSP switch. Its MML name is SS7ROUTE. For information on SS7 route parameters, refer to Table 2-6
on page 2-22.
To add an SS7 route to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD command
as follows:
Step 1
mml> prov-add:ss7route:name="rte1DPC1",opc="OPC",dpc="DestSW1PC",lnkset="linkset1",
pri=1,desc="route 1 to DestSW1 thru STP-A"
Step 2
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.
You must create a route for each DPC-OPC combination.
Adding an SS7 Signaling Service

An SS7 signaling service specifies the protocol variant and the path that the Cisco PGW 2200 Softswitch
uses to communicate with a remote switch (SSP) sending bearer traffic to the media gateways. Its MML
name is SS7PATH. For information on signaling service parameters, refer to Table 2-7 on page 2-22.
To add an SS7 signaling service to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD
command as follows:
mml> prov-add:ss7path:name="ss7svc1",mdo="ANSISS7_STANDARD",dpc="dpc1",opc="opc1",
desc="SS7 svc to dpc1"
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.
Adding a FAS Signaling Service

The facility associated signaling (FAS) service is the signaling path to a particular destination when you
are using either ISDN-PRI or DPNSS. Its MML name is FASPATH. For information on signaling service
parameters, refer to Table 2-15 on page 2-39.
Note
FASPATH is not provisionable in software Release 9.4(1).

To add an FAS path to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD command as
follows:
mml> PROV-ADD:FASPATH:NAME="FASPATH1",SIDE="network",MDO="ETSI_300_102",
CUSTGRPID="1000",CUSTGRPTBL="0101",DESC="FASPATH 1",ABFLAG="a",CRLEN=1
Use the PROV-RTRV command to verify the FAS path was added.
OL-1110-23
5-11
Chapter 5
Adding Signaling Link Components

After configuring the SS7 signaling routes, you need to configure the signaling link components. These
components link the Cisco PGW 2200 Softswitch to the STPs and to the media gateways. The
configuration process is described in the following sections:
Adding an Interface Card, page 5-12
Adding an Ethernet Interface, page 5-12
Adding a C7 IP Link, page 5-13
Adding a TDM Interface, page 5-14
Adding a TDM Link, page 5-14
Adding an Interface Card

This is a network interface card or adapter that is operating in the Cisco PGW 2200 Softswitch host. Its
MML name is CARD. For information on interface card parameters, refer to Table 2-9 on page 2-30.
Note
The CARD component is not provisionable in software Release 9.4(1).

To add an interface card to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD
command as follows:
Step 1
mml> prov-add:card:name="Ethernet1",type="EN",slot=0,desc="Ethernet Card 1"
Step 2
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.
Adding an Ethernet Interface

The Ethernet interface provides the physical line interface between a Cisco PGW 2200 Softswitch
Ethernet network card/adapter and the physical Ethernet network. You configure parameters that control
communications between the network card/adapter and the Ethernet. Its MML name is ENETIF. For
information on Ethernet interface parameters, refer to the Table 2-10 on page 2-30.
Note

To add an Ethernet interface to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD
command as follows:
5-12
OL-1110-23
Chapter 5

Step 1
mml> prov-add:enetif:name="EtherIF1",desc="Ethernet IF 1",card="Ethernet1"
Step 2
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.
You must configure the adapter/card before configuring the interface.
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
For SS7 provisioning, keep the following points in mind.

A maximum of 6 OPCs that can be supported.
group of 32 links.
Use the same port number for links in the same linkset.
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
Use the PROV-RTRV command to verify the C7 IP link was added.

For more information, refer to the Cisco Media Gateway Controller Software Release 9 Installation and
Configuration Guide.
OL-1110-23
5-13
Chapter 5
Adding Media Gateway Control Links
Adding a TDM Interface

The TDM interface provides the physical line interface between a Cisco PGW 2200 Softswitch TDM
network card/adapter and the physical TDM network. Its MML name is TDMIF. For information on
TDM interface parameters, refer to Table 2-11 on page 2-31.
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
Signal Type I/HDLC
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
Adding a TDM Link

A TDM link is a communications link between a TDM interface card on the
Cisco PGW 2200 Softswitch and TDM hardware element. For each link, you need to specify the card
interface to which the link connects. Its MML name is TDMLNK.
Note
TDMLNK is not supported in software Release 9.4(1).

To add a TDM link to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD command as
follows:
mml> prov-add:tdmlnk:name="tdmlink1",if="card1lif1",pri=2,slc=2,svc="ls-1",
desc="signal link 1"
Use the PROV-RTRV command to verify the TDM link was added.

Now you need to configure media gateway control links. The Cisco PGW 2200 Softswitch uses these
links to control the bearer traffic that passes between each media gateway. You typically add media
gateway control links by:
Adding an External Node, page 5-15
5-14
OL-1110-23
Chapter 5

Adding a Card, page 5-15
Adding an Ethernet Interface, page 5-15
Adding an E-ISUP Signaling Service, page 5-16
Adding an IPFAS Transport Service, page 5-16
Adding an MGCP Signaling Service, page 5-16
Adding a NAS Signaling Service, page 5-17
Adding an IP Link, page 5-17
Adding an External Node

An external node is a media gateway with which the Cisco PGW 2200 Softswitch communicates. Its
MML name is EXTNODE. For information on external node parameters, refer to Table 2-13 on
page 2-35.
To add an external node to the media gateway configuration, use the PROV-ADD command as follows:
mml> prov-add:extnode:name="mgx-8850",type="MGX8850"desc="MGX 8850"
Use the PROV-RTRV command to verify the external node has been added.
Tip
You must create an external node for each media gateway.
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.
Adding an Ethernet Interface

The Ethernet interface provides the physical line interface between an Cisco PGW 2200 Softswitch
Ethernet network card/adapter and the physical Ethernet network. You configure parameters that control
communications between the network card/adapter and the Ethernet. Its MML name is ENETIF.
Each SS7 link in the node must be associated with an Ethernet interface component, which must be
associated with a network card. The Ethernet interface represents a physical network connection on the
network card.
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
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.
Adding an E-ISUP Signaling Service

The E-ISUP signaling service or signaling path is the signaling path to an externally located
Cisco PGW 2200 Softswitch (destination). Its MML name is EISUPPATH. For information on signaling
service parameters, refer to Table 2-15 on page 2-39.
To add an E-ISUP signaling service to the media gateway configuration, use the PROV-ADD command
as follows:
mml> prov-add:eisuppath:name="eisupsrv1",extnode="extseq1",desc="EISUP Service to Ext Seq
Node1"
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.
Adding an IPFAS Transport Service

The FAS over IP transport service or signaling path is the transport service from a Gateway to a
Cisco PGW 2200 Softswitch. Its MML name is IPFASPath. For information on signaling service
parameters, refer to Table 2-15 on page 2-39.
To add an IPFAS transport service to the media gateway configuration, use the PROV-ADD command
as follows:
mml> prov-add:ipfaspath:name="ipfassvc1",extnode="nas1",desc="PRI Backhaul Service to
NAS1",mdo="ETSI_300_172",custgrpid="1111",abflag="a",crlen=1
Use the PROV-RTRV command to verify the IPFAS transport service was added.

The MGCP signaling service or signaling path is the signaling service to a trunking gateway. Its MML
name is MGCPPATH. For information on signaling service parameters, refer to Table 2-15 on page 2-39.
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.
Modifying an MGCP Signaling Service Property

The MGCP signaling service property is the signaling service to a trunking gateway. The following is an
example of how to change the codec used between an ingress and egress MGW. Ensure the
GWDefaultCodecString value matches the codec value of the device to which the
Cisco PGW 2200 Softswitch is connected. Its MML name is GWDefaultCodecString. For information
on signaling service parameters, see to Chapter 6, Properties, of Cisco PGW 2200 Softswitch MML
Command Reference for a list of possible values.
To change an MGCP signaling service property to the media gateway configuration, use the PROV-ED
command as follows:
mml> prov-ed:sigsvcprop:name="mgcsrv1",GWDefaultCodecString="G.711u",desc="MGC Signaling
Service to MGW1"
Use the PROV-RTRV command to verify the MGCP signaling service was changed.

The network access server (NAS) signaling path is the Q.931 protocol path between the
Cisco PGW 2200 Softswitch and the media gateway. Its MML name is NASPATH. For information on
signaling service parameters, refer to Table 2-15 on page 2-39.
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.
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"
Use the PROV-RTRV command to verify the IP link was added.
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.

You must specify one or two (if the IPADDR2 and PEERADDR2 parameters are specified) backhaul IP
links. Keep the following rules in mind when provisioning a session set.
SESSIONSETs that share a peer address (that is, PEERADDR, PEERADDR1, or PEERADDR2)
must be assigned directly or indirectly to the same external node.
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.
In the following example, one session set is added.

To add a session set to the media gateway configuration, use the PROV-ADD command as follows:
mml> prov-add:sessionset:NAME="c7-2600-1",EXTNODE="va-2600-stim1",IPADDR1="ip_addr1",
PEERADDR1="192.0.2.11",PORT=7000,PEERPORT=7000,NEXTHOP1="0.0.0.0",
NETMASK1="255.255.255.0,TYPE="BSMV0"
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
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
The maximum number of D-channels per channel controller is controlled by

maxNumDChansPerIOCC as defined in XECfgParm.dat.
A session set cannot span channel controllers. Therefore all the D-channels assigned to a session set
must be on one channel controller.
The maximum number of session sets per channel controller is 50.
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
This step is only required for a NFAS with a backup D-channel.
prov-add:DCHAN:NAME="dchan1b-207-3",DESC="Primary DCHAN for

PRI-Svc1",SVC="prisvc1",PRI=2,SESSIONSET="sset-207-3",SIGSLOT=0,SIGPORT=2,SUBUNIT=0
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"
Adding ISDN BRI Backhaul Connections

To enable ISDN BRI backhaul connections on the Cisco PGW 2200 Softswitch, the connected Cisco
ISDN BRI voice gateway must be configured such that the switchback function is disabled. This prevents
the voice gateway from automatically reconnecting with the active Cisco PGW 2200 Softswitch. The
switchback function is disabled using the following command:
OL-1110-23
5-19
Chapter 5
Gateway(config)#ccm-manager switchback never
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
Start a provisioning session.
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
Up to 2000 ISDN BRI signaling services can be provisioned on your

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.
5-20
OL-1110-23
Chapter 5

Adding IUA Connections

The following sections contain the procedures that you must perform to add IUA connections to your
Cisco PGW 2200 Softswitch provisioning data. When provisioning the components that enable the
Cisco PGW 2200 Softswitch to support IUA, perform the procedures in the following order:
Note
Verifying Next Hop Parameter Configuration, page 5-21
Adding Cisco Access Server External Nodes, page 5-24
Adding NAS Signaling Services, page 5-22
Adding IP Routes (Optional), page 5-22
Adding SCTP Associations, page 5-23
This functionality is available starting in software Release 9.4(1).
Verifying Next Hop Parameter Configuration

To ensure proper functioning of the Support for IUA with SCTP feature, verify the next hop IP address
parameters in the XECfgParm.dat file. These IP addresses are used when the next hop router IP addresses
on the Cisco PGW 2200 Softswitch hosts do not match. To enter next hop IP addresses, perform the
following steps:
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:
Step 2
Open the XECfgParm.dat using a text editor, such as vi.
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
Save your changes and close the text editor.
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:
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.
Adding Cisco Access Server External Nodes

To add Cisco access server external nodes to your provisioning data, perform the following steps:
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.
Adding NAS Signaling Services

To add NAS signaling services to your provisioning data, perform the following steps:
Step 1
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
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.
Adding IP Routes (Optional)

IP routes are required in your provisioning data if your Cisco PGW 2200 Softswitch hosts are not on the
same subnet as the Cisco access servers. To add IP routes, perform the following steps:
5-22
OL-1110-23
Chapter 5

Step 1
Step 2
Enter the following MML command to add an IP route named iprte1.

mml> prov-add:IPROUTE:NAME="iprte1",DESC="IP Route 1",dest="192.0.2.12",ipaddr="IP_Addr1",
netmask="255.255.255.0",nexthop="209.165.200.225"
Step 3
Repeat Step 2 for each IP route you want to add to your provisioning data.
Step 4
session.
Otherwise, proceed to Adding SCTP Associations.
Adding SCTP Associations

To add SCTP associations to your provisioning data, perform the following steps:
Step 1
Step 2
Enter the following MML command to add an SCTP association nasassoc1.

mml> prov-add:ASSOCIATION:NAME="nasassoc1",DESC="NAS Association 1",TYPE="IUA",
IPADDR1="IP_Addr1",IPADDR2="IP_Addr2",PEERADDR1="209.165.200.226",
PEERADDR2="209.165.201.2",extnode=va-5400-37,IPROUTE1="iprte1",IPROUTE2="iprte2"
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
session.
Adding DPNSS Connections

The following sections contain the procedures that you must perform to add DPNSS connections to your
Cisco PGW 2200 Softswitch provisioning data. When provisioning the components that enable the
Cisco PGW 2200 Softswitch to support DPNSS, perform the procedures in the following order:
Verifying Next Hop Parameter Configuration, page 5-24
Adding Cisco Access Server External Nodes, page 5-24
Adding IP Routes (Optional), page 5-25
Adding DPNSS Signaling Services, page 5-26
Adding DPNSS Supplementary Services, page 5-26
OL-1110-23
5-23
Chapter 5
Note
Verifying Next Hop Parameter Configuration

To ensure proper functioning of the Support for IUA with SCTP feature, verify the next hop IP address
parameters in the XECfgParm.dat file. These IP addresses are used when the next hop router IP addresses
on the Cisco PGW 2200 Softswitch hosts do not match. To enter next hop IP addresses, perform the
following steps:
Caution
Step 1
Do not modify the other XECfgParm.dat parameters associated with this feature.
Step 2
Step 3
Search for the *.IP_NextHop1 parameter and enter the IP address of your first next hop destination.
Note
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
Step 7
Step 8
Log in to the active Cisco PGW 2200 Softswitch, start an MML provisioning session, and enter the
following command:
Step 9
Adding Cisco Access Server External Nodes

To add Cisco access server external nodes to your provisioning data, perform the following steps:
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
session.
Otherwise, proceed to Adding NAS Signaling Services.
Adding IP Routes (Optional)

IP routes are required in your provisioning data if your Cisco PGW 2200 Softswitch hosts are not on the
same subnet as the Cisco access servers. To add IP routes, perform the following steps:
Step 1
Step 2
Enter the following MML command to add an IP route named iprte1.

mml> prov-add:IPROUTE:NAME="iprte1",DESC="IP Route 1",dest="192.0.2.13",ipaddr="IP_Addr1",
netmask="255.255.255.0",nexthop="209.165.200.227"
Step 3
Repeat Step 2 for each IP route you want to add to your provisioning data.
Step 4
session.
Otherwise, proceed to Adding SCTP Associations.

To add SCTP associations to your provisioning data, perform the following steps:
Step 1
Step 2
Enter the following MML command to add an SCTP association nasassoc1.

mml> prov-add:ASSOCIATION:NAME="nasassoc1",DESC="NAS Association 1",TYPE="IUA",
IPADDR1="IP_Addr1",IPADDR2="IP_Addr2",PEERADDR1="209.165.200.228",
PEERADDR2="209.165.201.4",extnode="va-5400-37",IPROUTE1="iprte1",IPROUTE2="iprte2"
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
session.
OL-1110-23
5-25
Chapter 5
Adding Trunks, Trunk Groups, and Routing
Otherwise, proceed to Adding DPNSS Signaling Services.
Adding DPNSS Signaling Services

To add DPNSS signaling services, perform the following steps:
Step 1
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
session.
Adding DPNSS Supplementary Services

Use the following MML commands to provision the DPNSS supplementary services, which are available
in software Release 9.6(1),
mml>
mml>
mml>
mml>
mml>
mml>
mml>
mml>
mml>
mml>
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"

You now need to configure trunks, trunk groups, and routing. The Cisco PGW 2200 Softswitch uses this
information for determining the call traffic on each trunk between the switches and the media gateways.
The procedures for configuring trunks, trunk groups, and trunk routes are described in the following
sections:
Adding Files, page 5-27
Adding a Nailed Trunk (Bearer Channel), page 5-27
Routing, page 5-28
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.
Adding a Nailed Trunk (Bearer Channel)

The nailed trunk component is for adding individual nailed bearer channels in a dial access
configuration. Its MML name is NAILEDRNK. For information on routing parameters, refer to the
Provisioning Trunk Groups and Trunks section on page 2-50.
To add a nailed trunk to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD command
as follows:
mml> prov-add:nailedtrnk:name="101",srcsvc="ss7svc1",srctimeslot=101,dstsvc="nassrv1",
dstspan=3,dsttimeslot=1
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.
Adding a Trunk Group

The trunk group component is for provisioning individual trunk groups. Its MML name is TRNKGRP.
For information on TRNKGRP parameters, refer to Table 2-29 on page 2-58.
To add a trunk group to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD command
as follows:
mml> prov-add:trnkgrp:name="1000",clli="tttt-ss-xxx",svc="ss7svc1",type="tdm_gen",
selseq="lidl",qable="n"
Use the PROV-RTRV command to verify the trunk group was added.
OL-1110-23
5-27
Chapter 5
Adding Mapping to Multiple Trunk Groups

To add mapping to multiple trunk groups on an incoming SIP or EISUP sigpath, see Adding Mapping to
Multiple IP Trunks, page 5-48.
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
mml> prov-add:rttrnkgrp:name="501",type=7,reattempts=1,queuing=0,cutthrough=2
Step 2
mml> prov-add:rttrnk:name="rt513",trnkgrpnum=513
Step 3
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.
Provisioning Reserving Incoming Bandwidth

In countries where 2-way trunk groups are used between a carriers network and an incumbents network,
these trunk groups carry outgoing traffic as well as incoming traffic to and from the incumbent.
When a trunk group toward a certain access area becomes congested, reserving incoming bandwidth
allows the carrier to re-direct outing traffic away from the congested trunk group and toward less
congested trunk groups. Thus a carrier can reserve a configurable percentage (in 1% increments) of
circuits for incoming calls and redirect outgoing traffic away when a trunk group is congested. This
maximizes the carriers opportunity to bring in revenue generating traffic, or to reserve circuits (increase
availability) for premier customers.
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"
Provisioning Bearer Capability

This section is used to configure the bearer capability for each trunk group.
To provision bearer capabilities to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD
commands as follows:
Step 1
mml> prov-add:bearercap:name="bearer1",bearercap="12;05;31"
Step 2
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
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.
OL-1110-23
5-29
Chapter 5
Provisioning Least Cost Routing

When provisioning the routing components in the Cisco PGW 2200 Softswitch, it is possible to modify
and change the order of trunk groups (rttrnkgrp) in a route (rttrnk), or routes (rttrnk) in a route list (rtlist).
These commands can be very useful in dynamically adjusting Least Cost Routing.
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
M COMPLD
"rttrnk"
;
M RTRV
/*
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
5-30
OL-1110-23
Chapter 5


COMPLD
"rttrnk"
;
M RTRV
/*
routeName
--------routea
M
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
Trunk group 3000 is appended to the bottom of the route list.

mgc4 mml> prov-ed:rttrnk:name="routea",trnkgrpnum=3000
M COMPLD
"rttrnk"
;
M RTRV
/*
routeName
--------routea
trunkGroup
---------5000
2000
4000
3000
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
M COMPLD
"rttrnk"
;
OL-1110-23
5-31
Chapter 5
RTRV
/*
routeName
--------routea
trunkGroup
---------3000
5000
2000
4000
nextTrunkGroup
-------------5000
2000
4000
*/
;
mgc4 mml>
Overriding the Trunk Group Property

The trunk group component is used to provision trunk group properties. Its MML name is
TRNKGRPPROP. In the following example, the trunk group property NPA is overridden for trunk group
number 1000. For information on TRNKGRPPROP properties, refer to Table 2-30 on page 2-61.
To override the Cisco PGW 2200 Softswitch trunk group properties, use the PROV-ADD command as
follows:
mml> prov-add:TRNKGRPPROP:NAME="1000",NPA="703"
Use the PROV-RTRV command to verify the specified trunk group property has been overridden.
Enabling Overdecadic 32 Digit Operation

Enabling the 32-digit overdecadic feature extends protocol-specific developments to all supported
protocols for 32-digits and overdecadic digits (A through F), and to support number portability when
receiving and generating Cause 14. Refer to Table 5-2 for a list of supported parameters per protocol
family.
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
5-32
OL-1110-23
Chapter 5

Table 5-2
Protocol Family
Parameters Affected by Overdecadic and 32 Digits Support
Parameters
32 Digits Support
Overdecadic
Digits Support
Called Party Number
Yes
Yes
Calling Party Number
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
Original Called Number
Yes
Yes
Outgoing Trunk Group Number
No (6 digits)
No
Redirecting Number
Yes
Yes
Redirection Number
Yes
Yes
Transit Network Selection
No (3 or 4 digits)
No (see Note 1)
Additional Identity* (French ISUP)
No (see Note 2)
Yes
Called Party Number
No (see Note 2)
Yes
Calling Line Identity (Calling Party

Number)
No (see Note 2)
Yes
No (see Note 2)
Yes
Subsequent Address Message

(Subsequent Number)
No (see Note 2)
Yes
Subsequent Address Message with One

signal
No (1 digit)
Yes
Transit Exchange Identity
No (see Note 2)
No
Called Party Number
Yes
Yes
Yes
Yes
Carrier Selection* (German ISUP)
No (3 or 4 digits)
Yes
Charge Area Information (Japanese

ISUP)
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.
OL-1110-23
5-33
Chapter 5
Table 5-2
Protocol Family
Parameters Affected by Overdecadic and 32 Digits Support (continued)
Parameters
32 Digits Support
Overdecadic
Digits Support
Connected Number
Yes
Yes
Contract Number* (Japanese ISUP)
Yes
Yes
Generic Number
Yes
Yes
Last Diverting Line Identity* (UK ISUP) Yes
Yes
Location Number
Yes
Yes
Yes
Yes
Presentation Number* (UK ISUP)
Yes
Yes
Redirecting Number
Yes
Yes
Redirection Number
Yes
Yes
Subsequent Number
Yes
Yes
No (3 or 4 digits)
Yes
Called Party Number
Yes
Yes
Yes
Yes
Connected Number
Yes
Yes
Generic Number* (Italian Interconnect

and Russian ISUPs)
Yes
Yes
Location Number* (Colombia, Russian,

Spanish, and Swedish ISUPs)
Yes
Yes
Original Called Number* (Colombia,

Indonesia, Mexican, Russian, Spanish,
and Swedish ISUPs)
Yes
Yes
Redirecting Number* (Colombia,

and Swedish ISUPs)
Yes
Yes
Redirection Number* (Colombia,

and Swedish ISUPs)
Yes
Yes
Q.767
5-34
OL-1110-23
Chapter 5

Table 5-2
Protocol Family
Parameters Affected by Overdecadic and 32 Digits Support (continued)
Parameters
32 Digits Support
Overdecadic
Digits Support
Subsequent Number
Yes
Yes
Transit Network Selection* (Colombia

and Mexican ISUPs)
No (3 or 4 digits)
Yes
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
MML targets of AWHITE, BWHITE, ABLACK, BBLACK, TERMTBL, ANUMDPSEL, and

ACHGORIGIN only support the Calling Line Identity (CLI) up to 20 digits. The MML target of
PORTTBL supports the called number and routing number up to 20 digits as well.
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:
M COMPLD
"trnkgrp"
Step 3
Commit the provisioning session changes.

mml> prov-cpy
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
A response, similar to the following, is returned:

M RTRV
"session=trnkgrpprop"
/*
BOrigStartIndex = 0
BTermStartIndex = 1
CarrierIdentity = 0
CLLI = STEVE
CompressionType = 1
CotPercentage = 0
CustGrpId = 0000
EchoCanRequired = 0
ExtCOT = Loop
GLARE = 0
Npa = 0
RingNoAnswer = 255000
SatelliteInd = 0
ScreenFailAction = 0
OD32DigitSupport = 1
*/
;
Provisioning SUBSCRIBE/NOTIFY Methods

Note

The procedures for provisioning the SUBSCRIBE/NOTIFY methods are in the following sections:
Enabling SUBSCRIBE/NOTIFY Methods, page 5-36
Disabling SUBSCRIBE/NOTIFY Methods, page 5-37
Enabling SUBSCRIBE/NOTIFY Methods

Use the following steps to enable the SUBSCRIBE/NOTIFY methods:
Step 1
Step 2
Enable the SUBSCRIBE/NOTIFY methods on a SIP trunk group with the following command:
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
Disabling SUBSCRIBE/NOTIFY Methods

Use the following steps to disable the SUBSCRIBE/NOTIFY methods:
Step 1
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
Provisioning Unsolicited Notifications

Note

The procedures for provisioning unsolicited notifications are in the following sections:
Enabling Unsolicited Notifications, page 5-37
Disabling Unsolicited Notifications, page 5-38
Enabling Unsolicited Notifications

Use the following steps to enable the Unsolicited NOTIFY method for SIP DTMF digits by the
Cisco PGW 2200 Softswitch:
Step 1
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
OL-1110-23
5-37
Chapter 5
Step 3
Disabling Unsolicited Notifications

Use the following steps to disable the Unsolicited NOTIFY method for SIP DTMF digits by the
Cisco PGW 2200 Softswitch:
Step 1
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
Provisioning Subscription Duration

Note

The procedures for provisioning the duration data for subscriptions are in the following sections:
Provisioning Minimum Subscription Duration for Telephony Event, page 5-38
Provisioning Maximum Duration for SUBSCRIBE, page 5-39
Provisioning Minimum Subscription Duration for Telephony Event

Use the following steps to define the minimum duration for which a telephony event can exist before it
can be re-subscribed:
Step 1
Step 2
Set the minimum duration of a telephony event on a SIP trunk group:

mml> prov-ed:trnkgrpprop:name="trnkgrpnum",custgrpid="grpid",
MinEventSubscribeDuration=minsub
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
5-38
OL-1110-23
Chapter 5

Provisioning Maximum Duration for SUBSCRIBE

Use the following steps to define the maximum duration for which the subscription can exist before it
needs a re-subscription:
Step 1
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
Enabling/Disabling Information Extraction from SDP

Note

The procedures required to enable or disable extracting information from the SD P is in the following
sections.
Enabling Support of Information Extraction from Sockets Direct Protocol (SDP)

Use the following steps to enable extracting SDP information for billing purposes.
Step 1
Step 2
Enter the following command to enable SDP information extraction:

mml> prov-ed:trnkgrpprop:name="trnk_num",populateSDPInfoInCDR="1"
Where: trnk_numThe number of the trunk to be modified.

For example, to enable SDP information extraction on a trunk group called 5000, you would enter the
following command:
mml> prov-add:trnkgrpprop:name="5000",populateSDPInfoInCDR="1"
Step 3
Repeat Step 2 for each trunk group you want to modify.
Disabling Support of Information Extraction from SDP

Use the following steps to disable extracting SDP information for billing purposes.
Step 1
OL-1110-23
5-39
Chapter 5
Step 2
Enter the following command to disable SDP information extraction:

mml> prov-ed:trnkgrpprop:name="trnk_num",populateSDPInfoInCDR="0"
Where: trnk_numThe number of the trunk to be modified.

For example, to disable SDP information extraction on a trunk group called 5000, you would enter the
following command:
mml> prov-add:trnkgrpprop:name="5000",populateSDPInfoInCDR="0"
Step 3
Repeat Step 2 for each trunk group you want to modify.
Adding a Switched Trunk (Multiple Switched Trunks)

The trunk (switched bearer channel) component is used for provisioning multiple switched trunks. Its
MML name is SWITCHTRNK. For information on SWITCHTRNK parameters, refer to the Creating
the Trunk Group section on page 2-58. The following command adds the six switched trunks shown in
Table 5-3 on page 5-40.
To add switched trunks to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD
command as follows
mml> prov-add:switchtrnk:name="1",trnkgrpnum="1000",span="ffff",cic=25,cu="gw1",
spansize=6,endpoint="S0/DS1-1/6@li-5300-3"
Table 5-3
Switched Trunk Command Result
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.
Retrieving Multiple Switched Trunks

To retrieve multiple switched trunks based on the trunk group number, span, or coding unit name, use
the PROV-RTRV command as follows:
mml> prov-rtrv:switchtrnk:trnkgrpnum="1000"
5-40
OL-1110-23
Chapter 5

Adding Multiple Nailed Trunks

To add multiple nailed trunks based on source service, source span, destination service, and destination
span, use the PROV-ADD command as follows:
mml> prov-add:nailedtrnk:name="100",srcsvc="SC-1",dstsvc="PC-7-200-7",srcspan="0",
dstspan="ffff",srctimeslot="1",dsttimeslot="4065",spansize=6
The previous command added the six nailed trunks shown in Table 5-4.
Table 5-4
Nailed Trunk Command Result
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.
Retrieving Multiple Nailed Trunks

To retrieve multiple nailed trunks, use the PROV-RTRV command as follows:
mml> prov-rtrv:nailedtrnk:srcsvc="SC-1"
Observe the screen to verify the command was successful.
Note
Only one source service, destination service, source span, or destination span is allowed at a time.
Adding Multiple Trunk Groups and Bearer Channels

The multiple trunk group component is for provisioning multiple PRI trunk groups and bearer channels.
Its MML name is MLTTRNKGRP.
To add multiple trunk groups and bearer channels to the Cisco PGW 2200 Softswitch configuration, use
the PROV-ADD command as follows:
mml> prov-add:mlttrnkgrp:name="1000",svc="bsc1",clli="5300E4011",numtrnkgrp=2,spansize=4,
trnkmemnum=1,span=0,cic=1,endpoint="S10/DS1-0/1@mgx-8850,cu="mgx-east"
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.
OL-1110-23
5-41
Chapter 5
Removing Multiple Trunk Groups and Bearer Channels

Only specify the NAME and NUMTRNKGRP parameters to remove several multiple trunk groups and
associated bearer channels.
To remove multiple trunk groups and bearer channels from the Cisco PGW 2200 Softswitch
configuration, use the PROV-DLT command as follows:
mml> prov-dlt:mlttrnkgrp:name="1000",numtrnkgrp=2
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.
Adding a Trunk Group Profile

Only specify the NAME and PROFILENAME parameters to add a trunk group profile for the specified
trunk group.
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.
Deleting a Trunk Group Profile

Only specify the NAME and PROFILENAME parameters to delete a trunk group profile for the specified
trunk group.
5-42
OL-1110-23
Chapter 5

To delete a profile type, use the PROV-DLT command as follows:

mml> prov-dlt:trnkgrpprof:name="1000","grprofile"
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.
Adding an ISUP Timer Profile

Before you can configure ISUP timers, you must first create an ISUP timer profile by using the following
MML command.
mml> prov-add:profile:name="set1",type=ISUPTMRPROFILE,variant=Q761_BASE,
validation=off,T1=5,T2=7
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.
Suppressing Caller ID in a SIP Environment

In software Revision 9.2(2) and above, you can control how the system suppresses (restricts) the
information contained in the following calling-party identity parameters:
Calling Line Identification (CLI)
Generic Name (GN)
Presentation Number (PN)
OL-1110-23
5-43
Chapter 5
Redirecting Number (RDN)
Original Called Number (OCN)
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
CLID Suppression in a SIP Environment
cgpnInclude Value (of

terminating/outgoing Received CLI
SIP trunk group)
(in IAM)
Received CLIR
(in IAM)
Outgoing FROM
header
Displayname field
Outgoing FROM
header
Username field
Not applicable
Not available
Not available
Unknown
Unknown
0 (do not include)
Available
0 (no restriction) CLID
CLID
0 (do not include)
Available
1 (restriction)
Anonymous
1 (include)
Available
0 (no restriction) CLID
CLID
1 (include)
Available
1 (restriction)
CLID
Table 5-6
Anonymous
Anonymous
GN Suppression in a SIP Environment

terminating/outgoing Received GN
SIP trunk group)
(in IAM)
Received GN
APRI1 (in IAM)
Outgoing FROM
header
Displayname field
Outgoing FROM
header
Username field
Not applicable
Not available
Not available
Unknown
Unknown
0 (do not include)
Available
0 (no restriction) Address signal of

GN
Address signal of
GN
0 (do not include)
Available
1 (restriction)
Anonymous
1 (include)
Available
0 (no restriction) Address signal of

GN
Address signal of
GN
1 (include)
Available
1 (restriction)
Address signal of
GN
Address signal of
GN
Anonymous
1. APRI = Address Presentation Restricted Indicator
Table 5-7
PN Suppression in a SIP Environment

terminating/outgoing Received PN
SIP trunk group)
(in IAM)
Received PN
APRI (in IAM)
Outgoing FROM
header
Displayname field
Outgoing FROM
header
Username field
Not applicable
Not available
Not available
Unknown
Unknown
0 (do not include)
Available
0 (no restriction) PN, if present for

the ISUP variant
PN, if present for

the ISUP variant
0 (do not include)
Available
1 (restriction)
Anonymous
Anonymous
5-44
OL-1110-23
Chapter 5

Table 5-7
PN Suppression in a SIP Environment (continued)

terminating/outgoing Received PN
SIP trunk group)
(in IAM)
Received PN
APRI (in IAM)
Outgoing FROM
header
Displayname field
Outgoing FROM
header
Username field
1 (include)
Available
0 (no restriction) PN, if present for

the ISUP variant
PN, if present for

the ISUP variant
1 (include)
Available
1 (restriction)
PN, if present for

the ISUP variant
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-to-SIP Diversion Header Mapping
RDN
(in IAM)
Presentation
Indicator
(in RDN)
cgpnInclude
(on originating SIP displayname
username
trunk group)
(Diversion header) (Diversion header)
Available
0 (no restriction)
0 (do not include if RDN

its presentation is
set to restricted)
RDN
Available
1 (restricted or
unavailable)
0 (do not include if Anonymous

its presentation is
set to restricted))
Anonymous
Available
1 (always include) RDN
RDN
Available
1 (always include) Anonymous
RDN
Table 5-9
OCN-to-SIP Diversion Header Mapping
OCN
(in IAM)
Presentation
Indicator
(in OCN)
cgpnInclude
(on originating SIP displayname
username
trunk group)
(Diversion header) (Diversion header)
Available
0 (no restriction)
0 (do not include if OCN

its presentation is
set to restricted)
OCN
Available
1 (restricted or
unavailable)
0 (do not include if Anonymous

its presentation is
set to restricted)
Anonymous
Available
1 (always include) OCN
OCN
Available
1 (always include) Anonymous
OCN
Adding an ATM Profile

ATM profiles are used on the Cisco PGW 2200 Softswitch to change the network Service Level
Agreement. You can add an ATM profile in routeAnalysis.dat by using the following MML command:
mml> prov-add:atmprofiles:name="atmprof1",atmprofiles="ITU1;custom100"
OL-1110-23
5-45
Chapter 5
Adding SIP Components
The following example represents the result of the previous MML command in routeAnalysis.dat:
$ATMProfiles
# CiscoMGC:
#name
atmprof1
01
ATMProfiles
ITU1;cust100
Provisioning ATM Profiles

After an ATM profile has been created, you can edit, delete, or retrieve an ATM profile you created in
routeAnalysis.dat by using the following MML commands:
mml>
mml>
mml>
mml>
prov-ed:atmprofiles:name="atmprof1",atmprofiles="ITU1;custom200"
prov-dlt:atmprofiles:name="atmprof1"
prov-rtrv:atmprofiles:name="atmprof1"
prov-rtrv:atmprofiles:"all"
Provisioning ATM Profiles Result Types

Provision ATM profiles result types by using the following MML commands:
mml> numan-add:resulttable:custgrpId="T002",name="result59",
resulttype="ATM_ORIG_PROFILE",dw1="atmprof1",dw2="1",setname="set1"
mml> numan-add:resulttable:custgrpId="T002",name="result60",
resulttype="ATM_TERM_PROFILE",dw1="atmprof1",dw2="1",setname="set1"
Provisioning Trunk Group Properties

Provision trunk group properties by using the following MML commands:
mml>
mml>
mml>
mml>
mml>
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"
Provisioning SigPath Properties

Provision the SigPath properties by using the following MML commands:
mml> prov-add:mgcppath:name="mgcpsvc1",extnode="AS5400",desc="MGCP service"
mml> prov-add:sigsvcprop:name="mgcpsvc1",GWProtocolVersion="MGCP 1.0"

For calls from the PSTN to the SIP domain, E164 numbers must be mapped to the URL of the Session
Initiation Protocol (SIP) proxy server that will handle the call. Each SIP trunk group is associated with
a URL of a SIP proxy server. There may be multiple trunk groups and each trunk group may be mapped
to a different SIP proxy server.
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.
Adding a SIP Signaling Service

The SIP signaling service is the connection between an Cisco PGW 2200 Softswitch and a SIP server.
Its MML name is SIPPATH.
To add a SIP signaling service for the signaling gateway from the Cisco PGW 2200 Softswitch
configuration, use the PROV-ADD command as follows:
mml> prov-add:sippath:name="sip-path",mdo="IETF_SIP",desc="SIP sigpath"
Use the PROV-RTRV command to verify that the SIP signaling service was added.
Adding a SIP Signaling Link

The SIP signaling link is the connection between an Cisco PGW 2200 Softswitch and a SIP server. Its
MML name is SIPLNK.
To add a SIP signaling link for the SG from the Cisco PGW 2200 Softswitch configuration, use the
PROV-ADD command as follows:
mml> prov-add:siplnk:name="sip-sipchan",ipaddr="IP_Addr1",svc="sip-sigpath",
port=5060,pri=1,desc="SIP sigchan"
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.
Adding a SIP Trunk Group

The SIP trunk group is the trunk group for incoming SIP calls. Its MML name is TRNKGRP.
To add a SIP trunk group for the signaling gateway from the Cisco PGW 2200 Softswitch configuration,
use the PROV-ADD command as follows:
mml> prov-add:trnkgrp:name="1111",svc="sip-sigpath",type="SIP_IN"
Use the PROV-RTRV command to verify that the SIP trunk group was added.
Adding SIP Trunk Group Properties

The SIP trunk group properties are for incoming SIP calls. Its MML name is TRNKGRPPROP.
To add a SIP trunk group property for the signaling gateway from the Cisco PGW 2200 Softswitch
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.
Adding Mapping to Multiple IP Trunks

The IPINMAPPING sigpath property allows you define mapping between a single SIP or EISUP
interface and multiple IP trunk groups using incoming IP address, subnet mask, and port number. To add
a new mapping entry, use the PROV-ADD:IPINMAPPING command as follows:
Prov-add:ipinmapping:name="sipinmapping-1",sigsvc="sippath-1",allowedIP="192.0.2.14",
sipport=5063, trnkgrpNum=1000
Use the PROV-RTRV to verify the incoming trunk group properties.

For more information about the IPINMAPPING component, see IPINMAPPING, page A-22.
For more information on the provisioning procedures for multiple inbound IP trunks, see the Multiple
Inbound IP Trunks section on page 5-106.
Adding SIP Routing Trunk Group Properties

The SIP routing trunk group properties are for incoming SIP calls. Its MML name is SIPRTTRNKGRP.
To add a SIP routing trunk group property for the signaling gateway from the
Cisco PGW 2200 Softswitch configuration, use the PROV-ADD command as follows:
mml> prov-add:siprttrnkgrp:name="2222",url="ss1.wrong.com",srvrr=1,sipproxyport=5060,
version="2.0",cutthrough=3,extsupport=0
Use the PROV-RTRV command to verify the SIP routing trunk group property was added.
Adding SIP Domain Name System Properties

The SIP domain name system (DNS) properties are for provisioning DNS-related parameters. Its MML
name is DNSPARAM.
To add a SIP DNS property for the signaling gateway from the Cisco PGW 2200 Softswitch
mml> prov-add:dnsparam:dnsserver1="172.22.1.1",dnsserver2="143.83.1.1",cachesize="500",
ttl="3600",policy="hierarchy",querytimeout="1000",icmptimeout="30",keepalive="30"
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"
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: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
Modifying a SIP Signaling Service

The SIP signaling service is the connection between a Cisco PGW 2200 Softswitch and a SIP server. Its
MML name is SIPPATH.
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.
Modifying Session Timers

The following two procedures indicate the MML command used for modifying the session timer for
incoming and outgoing SIP trunk groups.
Modifying Session Timer for Incoming SIP Trunk Groups

Use the following MML command to modify the session timer for an incoming SIP trunk group called
3333.
mml> prov-ed:trnkgrpprop:name="3333",InSessionTimer=26000
Modifying Session Timer for Outgoing SIP Trunk Groups

Use the following MML command to modify the session timer for an outgoing SIP trunk group called
3333.
mml> prov-ed:trnkgrpprop:name="3333",OutSessionTimer=26000
Adding Dual Presentation CLI

For networks providing PC-to-phone capabilities, a requirement to populate dual CLI fields in the
outgoing IAM message field exists.The following MML command is used to populate the Generic
Number CLI in the transmitted IAM for UK-ISUP.
mml> prov-add:trnkgrpprop:name="2222",,AInternationalPrefix="1234567890"
Adding Automatic Switchover Using Dual-VLAN

Note

This feature is not supported for systems where the active and standby Cisco PGW 2200 Softswitch
hosts are geographically separated. This feature is only supported for systems where the active and
standby Cisco PGW 2200 Softswitch hosts are configured as part of the same set of subnets. Systems
that have geographically separated Cisco PGW 2200 Softswitch hosts must use the existing
methodology, using two IP addresses each for the active and standby Cisco PGW 2200 Softswitch hosts.
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
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
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
Step 5
Search for the *.sipFailover parameter and ensure that the current setting is true.
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
Step 9
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:
Step 11
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.
Enabling SIP Automatic Switchover Using Dual-VLAN

This section contains the procedure you perform to add SIP Automatic Switchover Using Dual-VLAN
support to your Cisco PGW 2200 Softswitch software provisioning data. For more information on this
feature, see the SIP Automatic Switchover Using Dual-VLAN feature module at
http://cisco.com/en/US/docs/voice_ip_comm/pgw/9/feature/module/9.4_1_/FMvlan.html
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"
Where name is the MML name of a SIP IP link to be deleted.
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 a SIP signaling service to be deleted.

Repeat this step for each SIP signaling service you delete.
Step 8
Enter the following command to provision a new SIP signaling service:

mml> prov-add:sippath:name="name",mdo="ietf_sip"
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
Enter the following command to provision a virtual IP address on a SIP IP link:

mml> prov-add:siplnk:name="name",desc="description",ipaddr="addr",svc="sigsrv",
port=port=pnum,pri=priority,desc="description"
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
Save and activate your new provisioning settings.
Disabling SIP Automatic Switchover Using Dual-VLAN

This section contains the procedure you perform to disable SIP Automatic Switchover Using
Dual-VLAN support in your system.
Note
Start an MML provisioning session.

Perform the following steps to disable the virtual IP addresses on your SIP IP links:
Step 1
Step 2
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
Step 8
Step 9
Log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the following
command:
Step 10
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
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
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
Enter the following command to provision a new SIP signaling service:

mml> prov-add:sippath:name="name",mdo="ietf_sip"
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
Enter the following command to enable the IP addresses on a SIP IP link:

mml> prov-add:siplnk:name="name",ipaddr="addr",ipaddr="addr"
5-54
OL-1110-23
Chapter 5

Adding SIP-T and SIP-GTD Support
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
Save and activate your provisioning session.

Note

This section contains the procedures you perform to add SIP-T and SIP-GTD support to your
Cisco PGW 2200 Softswitch software provisioning data. When provisioning the components that enable
the Cisco PGW 2200 Softswitch software to support SIP-T and SIP-T, perform the procedures in the
following order.
Adding an SS7 Signaling Service, page 5-11
Adding an External Node, page 5-15
Adding a SIP Signaling Service, page 5-47
Adding a SIP Signaling Link, page 5-47
Adding a Trunk Group, page 5-27
Adding a Switched Trunk (Multiple Switched Trunks), page 5-40
Adding SIP-T and SIP-GTD Support, page 5-55
GTD Provisioning Examples, page 5-59
Enabling the Early Backward ISUP Message, page 5-56
Enabling Partial GTD Support, page 5-59
Adding SIP Domain Name System Properties, page 5-48

To add SIP-T or SIP-GTD support to your system, you must set two properties in both the ingress SS7
trunk group and in the SIP trunk group. To do this, use the following MML commands.
Enter the following command to enable SIP-T or SIP-GTD on an ingress SS7 trunk group.
mml> prov-add:trnkgrpprop:name="550",sipMimeBodySupport="1",IsupTransparencyDisabled=0
Note
The IsupTransparencyDisabled property appears in the MML command because enabling

SIP-T/SIP-GTD support requires that ISUP transparency be enabled on the selected trunk group.
OL-1110-23
5-55
Chapter 5
GTD NOA Override
Repeat the MML command for the SIP trunk groups for which you want to activate SIP-T or SIP-GTD
support.
Enabling the Early Backward ISUP Message

To enable the early backward ISUP message on GTD-enabled SIP trunk groups, perform the following
MML command.
mml> prov-ed:trnkgrpprop:name="1000",IsupTransEarlyBackwardDisabled="0"
Where name is the number of a previously provisioned trunk group.
GTD NOA Override

The Generic Transparency Descriptor (GTD) Nature of Address (NOA) feature is used to specify a set
of GTD fields that the Cisco PGW 2200 Softswitch desires to override the corresponding ISDN
Information Element (IE) fields. NOA is one of the override fields. The override fields are specified in
a string. For fields not specified in the string, ISDN IE fields take precedence.
The GTD parameter string for building is a single string of GTD parameters separated by comma(s). The
maximum length of this string is 460 bytes (4x115). The ALL string stands for all GTD parameters and
the NONE string (the default) stands for null or no GTD parameters.
The following is the GTD parameter string syntax for building the GTD parameter string, where the
parameter is in three uppercase letters:
gtdParamString = NONE | ALL | build_string
Note
The default value of gtdParamString is NONE.

GTD override fields string is a single string of GTD parameters, as well as fields separated by comma.
The maximum length of this string is 256 bytes. A special string NONE stands for null string. The
following is the syntax of GTD override fields string where the filed should be in lower case letters of
varying length:
gtdOverrideFieldsString = NONE | override_string
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 |
5-56
OL-1110-23
Chapter 5

GTD NOA Override
CCN | CCS | CDI | CDN |

CDT | CGL | CGN | CHI |
CHN | CIC | CID | CIN |
CMI | CNF | CNN | CNR |
COL | COR | CPC | CPN |
CRF | CSI | CSP | CTI |
CTN | CTR | DIS | ECI |
EGR | EVI | FAI | FCI |
FDC | FVN | GCI | GEA |
GED | GEN | GIC | GNO |
GRF | HOC | HTR | INI |
IRI | ISC | JUR | LON |
LPI | LSP | MCI | MCR |
MLP | MRI | NET | NMC |
NOC | NPF | NRN | NSF |
OBI | OCI | OCN | OCT |
OFI | OLI | OSI | OTN |
PBI | PCA | PCI | PCT |
PDC | PFI | PRI | PRN |
PVS | QOR | RBI | RCT |
RDC | RDS | RFI | RGN |
RMO | RNI | RNN | RNR |
SCF | SCI | SEA | SEG |
SPC | SPR | SRI | SUN |
TID | TMP | TMR | TMU |
TNS | TRR | UCI | UFC |
UID | USI | USP | UTI |
UUI | UUS | VER
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
OL-1110-23
5-57
Chapter 5
GTD NOA Override
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
5-58
OL-1110-23
Chapter 5

NOA Configurable Mapping
GTD Provisioning Examples

If the system has no GTD related provisioning, all sigpaths have the default value of gtdcaptypeprop set
to t0, which means there is no GTD support. The following provisioning session enables partial GTD
support indicated by gtdcaptypeprop = t3 for the sigpath nassrv1 by specifying only some of the GTD
parameters.
Enabling Partial GTD Support

The following MML commands enable partial GTD support indicated by gtdcaptypeprop = t3 for sigpath
nassrv1.
prov-add:extnode:name="nas1",type="AS5300",desc="NAS 1"
prov-add:naspath:name="nassrv1",desc="Service to nas1",extnode="nas1",mdo="BELL_1268_C3"
prov-add:gtdparam:name="t3",desc="GTD subset 3",
gtdparamstring="CPC,CGN,BCI,CPN,CID,OBI,OCN,RBI,CHN,HOC,RGN",
overrideString="CGN.noa,CPN.noa"
prov-add:gtdparam:name="t1",gtdparamstring="ALL"
prov-add:gtdparam:name="t5",gtdparamstring="CPN,CGN,CIC,CPC,BCI"
prov-add:sigsvcprop:name="nassrv1",gtdcaptypeprop="t3"
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.
Changing from Partial to All GTD Support

The following MML command changes GTD support from gtdcaptypeprop = t3 to gtdcaptypeprop = t1.
All GTD is supported as indicated by gtdcaptypeprop = t1 for nassrv1.
prov-ed:sigsvcprop:name="nassrv1",gtdcaptypeprop="t1"
Disabling GTD Support

The following MML command disables GTD support for nassrv1. The value of gtdcaptypeprop is set to
default (t0) for sigpath naasrv1.
prov-dlt:sigsvcprop:name="nassrv1","gtdcaptypeprop"

The configurable NOA mapping is supported in Cisco PGW 2200 Softswitch software Release 9.4(1)
and allows you to translate an external NOA value to any internal NOA value for inbound or outbound
calls. This mapping is limited to protocols (and variants) that support NOA, which are: Q.761, Q.761-97,
Q.767, and ANSI.
Configurable NOA mapping is determined by how you configure Configurable (NOA) Translation
Tables (CTT) for inbound line values to internal CC NOA values (See DefaultDNNOA in Planning
for Provisioning for internal NOA values) and internal CC NOA values to outbound line values. The
CTT can be added on a per sigpath basis.
Though the NOA is present in many parameters in different protocols, only the following numbers are
supported:
Called party number
Calling party number
OL-1110-23
5-59
Chapter 5
Original called party number
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).
Provisioning the NOA Configurable Mapping Feature

The following MML command syntax is used to add an entry to the linexlate.dat file.
mml> prov-add:linexlate:name=<MML name>,DESC=<Description>,SVC=<MML name>,PARAMETER=<param value>,
DIRECTION=<param value>,NUMBER=<param value>,INTNOA=<param value>,EXTNOA=<param value>
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>
Where MML name is the NOA translate table entry.

For example:
mml> prov-dlt:linexlate:name=noa1
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.
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.
Adding an NOA Value to the LineXlate File for Inbound Calls

Perform the following steps to provision the Configurable NOA Mapping Feature.
Step 1
Open a provisioning session by using the following MML command:

mml> prov-sta::srcver="linexlt1",dstver="mml_01"
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
Commit the changes.

mml> prov-cpy
Step 4
Use prov-rtrv:linexlate:name=noa1 to verify the property was added correctly.

mml> prov-rtrv:linexlate:name=noa1
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.
Deleting an NOA Value from the LineXlate File

Perform the following steps to delete the configured provisioned LineXlate entry dynamically.
Step 1

mml> prov-sta::srcver="01",dstver="mml_02"
Step 2
Dynamically delete the internal NOA and line NOA property for LineXlate.
mml> prov-dlt:linexlate:name=noa1
Step 3
Commit the changes.

mml> prov-cpy
Step 4
Use prov-rtrv:linexlate:name=noa1 to verify the property was deleted correctly.

Adding an NOA Value to the LineXlate File for Outbound Calls

Perform the following steps to provision the line NOA and internal NOA property for an outbound
message.
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
Commit the changes.

mml> prov-cpy
Step 4
Use prov-rtrv:linexlate:name=noa2 to verify the property was added correctly.

Deleting an NOA Value from the LineXlate File

Perform the following steps to delete the configured provisioned LineXlate entry dynamically.
Step 1

Step 2
Dynamically delete the LineXlate table entry.

mml> prov-dlt:noaxlate:name=noa2
Step 3
Commit the changes.

mml> prov-cpy
Step 4
Use prov-rtrv:linexlate:name=noa2 to verify the property is deleted correctly.

Validation Rules
Note
All parameters must be present.
The sigpath must have been provisioned.
Parameter, direction, number, intnoa, and linenoa are range validated.
A check is made to verify there is not a duplicate entry.
The Configured Translation table contains no default entries since all parameters must be entered to
create a configuration entry.
Adding M3UA and SUA Connections

This section contains the procedures to perform to add M3UA and SUA connections to your
Cisco PGW 2200 Softswitch. Provision the components that enable the Cisco PGW 2200 Softswitch to
support M3UA and SUA in the following order.
Adding a Cisco ITP External Node, page 5-63
Adding Point Codes (OPC, DPC, and APC), page 5-63
5-62
OL-1110-23
Chapter 5

Adding M3UA and SUA Routing Keys, page 5-63
Adding SS7 Signaling Services, page 5-63
Adding M3UA and SUA Routes, page 5-64
Adding SS7 Subsystems, page 5-64
Adding M3UA and SUA Signaling Gateway Processes, page 5-64
Adding IP Routes (optional), page 5-64
Adding a Cisco ITP External Node

Add a Cisco IP Transfer Point (ITP) external node named itp1 by enter the following MML command.
mml> prov-add:extnode:name="itp1",desc="2651 ITP",type="itp",group=1
Note
Only as many as two ITPs are allowed in the same group.
Adding Point Codes (OPC, DPC, and APC)

Add an OPC named opc1 by entering the following MML command.
mml> prov-add:opc:name="opc1",desc="Originating PC 1",netaddr="2.1.4",netind=2,
type="trueopc"
Note
To support M3UA and SUA interfaces, the value of the type parameter must be set to trueopc.
Add a DPC named dpc1 by entering the following MML command.

mml> prov-add:DPC:NAME="dpc1",DESC="DPC1",NETADDR="1.1.5",NETIND=2
Add an APC named apc1 by entering the following MML command.

mml> prov-add:apc:NAME="apc1",DESC="apc1",NETADDR="1.2.4",NETIND=2
Adding M3UA and SUA Routing Keys

Add an M3UA routing key named m3uakey1 by entering the following MML command.
mml> prov-add:M3UAKEY:NAME="m3uakey1",OPC="opc1",DPC="dpc1",SI="ISUP",ROUTINGCONTEXT=10
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
Adding SS7 Signaling Services

Add an SS7 signaling service named ss7svc1 by entering the following MML command.
mml> prov-add:SS7PATH:NAME="ss7svc1",DESC="OPC1 to INET DPC1",M3UAKEY="m3uakey1",
DPC="dpc1",MDO="Q761_BASE"
OL-1110-23
5-63
Chapter 5
Adding M3UA and SUA Routes

Add an M3UA route named m3uarte1 by entering the following MML command.
mml> prov-add:M3UAROUTE:NAME="m3uarte1",DESC="M3UA Rte 1",OPC="opc1",DPC="dpc1",
EXTNODE="itp1"
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
Adding SS7 Subsystems

Add an SS7 subsystem named prepaid by entering the following MML command.
mml> prov-add:SS7SUBSYS:NAME="prepaid",DESC="prepaid rte-ssn 48",SUAKEY="suakey1",
SVC="scp",PROTO="SS7-ITU",TRANSPROTO="SUA",stpscpind=2,remotessn=48
Adding M3UA and SUA Signaling Gateway Processes

Add an SGP for an SUA path named sua-sgp1 by entering the following MML command.
mml> prov-add:SGP:NAME="sua-sgp1",DESC="SUA SGP 1 - ITP1",EXTNODE="itp1"
Adding IP Routes (optional)

IP routes are required if your Cisco PGW 2200 Softswitch hosts are not on the same subnet as the Cisco
access servers.
Add an IP route named iprte1 by entering the following MML command.
mml> prov-add:IPROUTE:NAME="iprte1",DESC="IP Route 1",dest="192.0.2.17",ipaddr=IP_Addr1,
netmask="255.255.255.0",nexthop="10.82.82.1"

Add an SUA association named sua-assoc1 by entering the following MML command.
mml> prov-add:ASSOCIATION:NAME="sua-assoc1",DESC="M3UA Association 1",TYPE="SUA",
SGP="sua-sgp1",IPADDR1="IP_Addr1",IPADDR2="IP_Addr2",PEERADDR1="209.165.200.229",
PEERADDR2="209.165.201.5"
Optimizing PGW-to-ITP Routing with MAP Query

This feature allows the Cisco PGW 2200 Softswitch to optimize routing based on a subscribers location
within a mobile network. If the ItpActionRequest property is set to map-app, the system sends a
customized SIP invite to the ITP to return the location of the mobile subscriber. The customized SIP
invite causes the ITP (if it is capable) to send an SS7 Mobile Application Part (MAP) query to the service
provider home location register (HLR) for the mobile subscribers current mobile station roaming
number (MSRN). The Cisco PGW 2200 Softswitch then routes the call to the closest gateway mobile
switching center (MSC) based upon the new MSRN.
5-64
OL-1110-23
Chapter 5

Figure 5-4 shows a typical deployment for this feature.

Typical Deployment for PGW-to-ITP Routing with MAP Query
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"
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:
Display SIP MAP gateway information.

show cs7 mapua statistics [name of the MAP UA]
Display Cisco IOS SIP stack statistics.

show cs7 sip statistics
Debug the MAP gateway function.

debug cs7 map-ua {all | error | packet | api}

Using location labels allows call limiting to or from a location to ensure quality of service is maintained.
The following sections provide call limiting provisioning examples
Adding Location Labels to Trunk Groups and Sigpaths, page 5-67
Applying Call Limiting to a SIP Trunk Group, page 5-71
Applying Call Limiting to an H.323 Trunk Group, page 5-72
Applying Call Limiting to the DPNSS Trunk Groups, page 5-72
Applying Call Limiting to an SS7 ISUP Trunk Group, page 5-72
Applying Call Limiting to Digit Strings in a Dial Plan, page 5-73
Applying Call Limiting to Multiple Trunk Groups, page 5-73
Applying Call Limiting to IP Addresses, page 5-74
5-66
OL-1110-23
Chapter 5

Applying Call Limiting to an MGCP Gateway, page 5-75
Playing an Announcement when the Call Limiting Threshold is Exceeded, page 5-75
Adding Location Labels to Trunk Groups and Sigpaths

The following MML commands were used to provision examples of location labels at sigPath and trunk
group levels and is the first provisioning session started on the Cisco PGW 2200 Softswitch:
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:OPC:NAME="opc",DESC="The PGW point code",NETADDR="1.1.1",NETIND=2,TYPE="TRUEOPC"

prov-add:DPC:NAME="dpc1",DESC="Orig. point code",NETADDR="2.2.2",NETIND=2
prov-add:DPC:NAME="dpc2",DESC="Dest. point code",NETADDR="3.3.3",NETIND=2
prov-add:EXTNODE:NAME="dpnss-gw1",DESC="nas 2600 Backhaul",TYPE="C2600",
ISDNSIGTYPE="IUA",GROUP=0
prov-add:EXTNODE:NAME="eisup1",DESC="external node - eisup",TYPE="MGC",
ISDNSIGTYPE="N/A",GROUP=0
prov-add:EXTNODE:NAME="ipfas1",DESC="external node - ipfas",TYPE="C2600",
ISDNSIGTYPE="N/A",GROUP=0
prov-add:SS7PATH:NAME="ss7svc1",DESC="SS7 service to DPC-2-2-2",MDO="ANSISS7_STANDARD",
CUSTGRPID="1111",SIDE="network",DPC="dpc1",OPC="opc",M3UAKEY="",ORIGLABEL="loclbl1",
TERMLABEL="loclbl2"
prov-add:DPNSSPATH:NAME="dpnss1",DESC="backhaul to nas2600",EXTNODE="dpnss-gw1",
CUSTGRPID="1111",SIGSLOT=2,SIGPORT=1,ORIGLABEL="loclbl1", TERMLABEL="loclbl2"
prov-add:EISUPPATH:NAME="eisup-mgc01",DESC="signal service - mgc",EXTNODE="eisup1",
CUSTGRPID="1111",ORIGLABEL="loclbl1",TERMLABEL="loclbl2"
prov-add:ipfaspath:name="ipfas-sigpath",mdo="dummy",desc="IPFAS sigpath",EXTNODE="ipfas1",
ORIGLABEL="loclbl1",TERMLABEL="loclbl2"
prov-add:sippath:name="sip-sigpath",mdo="IETF_SIP",desc="SIP sigpath",ORIGLABEL="loclbl1",
TERMLABEL="loclbl2"
prov-rtrv:sippath:name="sip-path"
OL-1110-23
5-67
Chapter 5
MGC-2 - Media Gateway Controller 2005-07-06 16:22:32.107 EDT

RTRV
"session=egw-2:sippath"
/*
NAME = sip-path
DESC = sip path
MDO = IETF_SIP
ORIGLABEL =
TERMLABEL =
*/
;
M
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
"LI Radius Protocol Family"

"local label 1"
"local label 2"
The XECfgParm.dat parameter, engine.CallLimitingControl controls call limiting for the

Cisco PGW 2200 Softswitch platform. The parameter default value is 0, where 0 is false (call limiting
disabled) and 1 is true (call limiting enabled). The following provisioning examples require
engine.CallLimitingControl to be enabled (set to 1).
5-68
OL-1110-23
Chapter 5

Applying Call Limiting Over DPNSS

The following provisioning example, see Figure 5-5, shows two gateways that are configured to be
redundant with a total of 60 DS0s to PBX-2. The following sample provision shows that the service
provider sets the call limiting of 10 toward PBX-2 over DPNSS from Cisco Call Managers (CCM)
CCM-X and CCM-Y.
prov-add:loclabel:name="location2",calllimit=10
prov-add:DPNSSPATH:NAME="dpnss-path1",DESC="dpnss va-3745-2",EXTNODE="va-3745-2",
CUSTGRPID="1111",SIGSLOT=1,SIGPORT=0
prov-add:trnkgrp:name="7000",type="TDM_DPNSS",svc="dpnss_path1",clli="7000',selseq="ASC",
qable="N",origlabel="location2",termlabel="location2"
Figure 5-5
DPNSS Call Limiting Scenario
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.
Applying Call Limiting to Incoming and Outgoing Trunk Groups

The following provisioning scenario, see Figure 5-6, is useful when multiple enterprises are sending
their traffic through the same trunking media gateway. Call limiting used in this example can enforce
limits so a certain enterprise cannot use too many trunking ports to the exclusion of other enterprises
connected to the PSTN by the Cisco PGW 2200 Softswitch.
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
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:adigtree:custgrpid="1111",callside="originating",digitstring="300",
setname="set301"
Figure 5-6
Incoming and Outgoing Trunk Group Call Limiting Scenario
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
SIP
H.323
C7/SS7
Data
IMT
5-70
OL-1110-23
Chapter 5

B-number Based Call Limiting Scenario

The following provisioning scenario, see Figure 5-7, is useful when limiting the number of calls based
on B-numbers. If the B-number is 300XXX and call limiting for 300XXXX is 100.
numan-add:resultset:custgrpid=1111,name=set300
custgrpid="1111",name="resultloc300
setname="set300"
numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring=300",
setname="set300"
Figure 5-7
B-number Based Call Limiting Scenario
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
SIP
H.323
C7/SS7
Data
IMT
Applying Call Limiting to a SIP Trunk Group

The following provisioning example shows that call limiting of 10 is applied to the incoming and
outgoing SIP trunk groups.
//location label for call limiting of 10
//provision SIP path
prov-add:SIPPATH:NAME="sip-path",DESC="SIP path",MDO="IETF_SIP",ORIGLABEL="",TERMLABEL=""
//provision SIP link
prov-add:SIPLNK:NAME="sip-link",DESC="SIP link",SVC="sip-path",IPADDR="IP_Addr1",
PORT=5060,PRI=1
OL-1110-23
5-71
Chapter 5
//provision SIP route trunk

prov-add:siprttrnkgrp:name="7000",url="192.0.2.18",version="2.0",cutthrough=2,srvrr=2,
extsupport=1
//provision outgoing call limit for SIP trunk group
prov-add:trnkgrp:name="7000",type="IP_SIP",svc="sip-path",clli="",selseq="LIDL",
origlabel="location1",termlabel="location1"
//provision incoming call limit for SIP trunk group
prov-add:trnkgrp:name="7000",type="SIP_IN",svc="sip-path",clli="",selseq="LIDL",
Applying Call Limiting to an H.323 Trunk Group

The following provisioning example shows that call limiting is applied to an H.323 trunk group for both
incoming and outgoing trunk groups (for example, call limit for the H.323 side is 20).
//provision EISUP path to HSI, PGW are connected with H.323 network by HSI
prov-add:EISUPPATH:NAME="eisup-hsi",DESC="to orchid",EXTNODE="sh-hsi",CUSTGRPID="1111"
//provision call limit for H.323 trunk group
prov-add:trnkgrp:name="6000",CLLI="sh-daisy",svc="eisup-hsi",type="IP",selseq="ASC",
Note
Either the EISUP path or the HSI trunk group can be provisioned with location label.
Applying Call Limiting to the DPNSS Trunk Groups

The following provisioning example shows that call limiting is applied to the DPNSS trunk groups (for
example, call limit for DPNSS trunk group is 30) on both terminating and originating trunk groups.
prov-add:loclabel:name=location3",calllimit=30
//provision DPNSS path
prov-add:DPNSSPATH:NAME="dpnss-path2",DESC="dpnss va-3745-2",EXTNODE="va-3745-2",
CUSTGRPID="1111",SIGSLOT=1,SIGPORT=1,ORIGLABEL="",TERMLABEL=""
//provision call limit for DPNSS trunk group
prov-add:trnkgrp:name="5331",type="TDM_DPNSS",svc="dpnss-path1",clli="va-3745-2",
selseq="ASC",qable="N",origlabel="location3",termlabel="location3"
Applying Call Limiting to an SS7 ISUP Trunk Group

The following provisioning example shows that call limiting is applied to SS7 (for example, the call limit
for the SS7 trunk group is 40) either incoming or outgoing, and make an announcement when the number
of calls exceeds the call limit threshold.
//call limit is 10
//provision both incoming and outgoing call limit for SS7 trunk group
prov-add:trnkgrp:name="7000",type="TDM_ISUP",svc="ss7svc1",clli="7000',selseq="ASC",
//The following is to provision incoming call limiting
//provision incoming call limit for SS7 trunk group
qable="N",origlabel="location1",termlabel=""
//The following is to provision outgoing call limiting
5-72
OL-1110-23
Chapter 5

//provision outgoing call limit for SS7 trunk group

qable="N",origlabel="",termlabel="location1"
//The following is to play an announcement when calls are rejected due to exceeding
threshold set by limiting
//announcement provisioning
numan-add:announcement:annid=123,gwtype="AS5400",duration="60",repeat="2",interval="3",
locationstring="xyz.aud"
//provision local announcement
numan-add:resulttable:custgrpId="1111",name="result60",resulttype="ANNOUNCEMENT",
dw1="123",dw2="0",dw4="1",setname="set1"
//call limit reject internal code is "171"
numan-add:cause:custgrpid="1111",causevalue="171",setname="set1"
Applying Call Limiting to Digit Strings in a Dial Plan

The following provisioning examples show that call limiting applied to A- and B-numbers by the dial
plan and digits analysis.
1. This is the example that all incoming calls that B-numbers have prefix of 300XXX, calling limiting
for 300XXXX is set to 100.
// provision a resultset
numan-add:resultset:custgrpid=1111,name=set200
//provision call limit location label in resultset
custgrpid="1111",name="resultloc200
//provision route resulttable
setname="set200"
//provision Bdigtree for B-number 300XXX
numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring=300",
setname="set200"
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
//provision Adigtree for A-number 300XXX
numan-add:adigtree:custgrpid="1111",callside="originating",digitstring=300",
setname="set201"
Applying Call Limiting to Multiple Trunk Groups

The following provisioning example shows that one calling label can be applied to multiple trunks and
trunk groups, which are either incoming or outgoing.
//location label 3 can be used as SIP incoming trunk group 7000
origlabel="location3"
//location label 3 can be used as SIP outgoing trunk group 8000
OL-1110-23
5-73
Chapter 5
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"
Applying Call Limiting to IP Addresses

The following provisioning example shows that the call limiting feature can be applied to source and
destination IP addresses indirectly by the dial plans.
1. Call limiting to the other peer PGW IP addresses.
Assuming a peer Cisco PGW 2200 Softswitch IP address is 192.0.2.19, call limiting for EISUP is 100,
call limiting can be provisioned in EISUP for the sigPath or trunk group.
Option 1: Setting call limiting with an EISUP sigPath.
//provision call limit in EISUP path
prov-add:EISUPPATH:NAME="eisup-orkid",DESC="to orchid",EXTNODE="sh-orchid",
CUSTGRPID="1111",ORIGLABEL="location5",TERMLABEL="location5"
//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.19",PEERPORT=8001,PRI=1,IPROUTE=""
Option 2: Set call limiting with an EISUP trunk group, for example, the trunk group is 6000.
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",
//provision call limit in EISUP trunk group
prov-add:trnkgrp:name="6000",type="IP",svc="eisup-daisy",clli="sh-daisy",selseq="ASC",
2. Call limiting for other SIP servers.

Assuming a SIP proxy IP address is 192.0.2.21, call limiting is set to 100, call limiting can be
provisioned in the trunk group, for example, trunk group 7000.
//provision SIP path
prov-add:SIPPATH:NAME="sip-path",DESC="SIP path",MDO="IETF_SIP",ORIGLABEL="",TERMLABEL=""
//provision SIP link
prov-add:SIPLNK:NAME="sip-link",DESC="SIP link",SVC="sip-path",IPADDR="IP_Addr1",
PORT=5060,PRI=1
//provision SIP route trunk
prov-add:siprttrnkgrp:name="7000",url="192.0.2.21",version="2.0",cutthrough=2,srvrr=2,
extsupport=1
//provision call limit in SIP trunk group
5-74
OL-1110-23
Chapter 5

Scaling System Components
Applying Call Limiting to an MGCP Gateway

The following example shows that call limiting is applied to an MGCP gateway with IP address of
192.0.2.22, the gateway has 4 trunk groups, which are controlled by ss7svc1, and the call limiting is set
to 20.
//provision MGCP path
prov-add:MGCPPATH:NAME="mgcp530011",DESC="MGCP service to AS-5300-11",EXTNODE="va-5300-11"
//provision IP link
prov-add:IPLNK:NAME="clink11-1",DESC="MGCPlink to sh-5300-11",SVC="mgcp530011",
//provision call limit for SS7 sigPath
prov-add:ss7path:name="ss7svc1",desc="ss7 path",dpc="dpc1",opc="opc",mdo="Q761_BASE",
SIDE="network",origlabel="location8",termlabel="location8"
Playing an Announcement when the Call Limiting Threshold is Exceeded

The following example shows that an announcements can be made when calls are rejected due to
exceeding the threshold set by call limiting.
//announcement provisioning
numan-add:announcement:annid=123,gwtype="AS5400",duration="60",repeat="2",interval="3",
locationstring="xyz.aud"
//local announcement
numan-add:resulttable:custgrpId="1111",name="result60",resulttype="ANNOUNCEMENT",
dw1="123",dw2="0",dw4="1",setname="set1"
//call limit reject internal code is "171"
numan-add:cause:custgrpid="1111",causevalue="171",setname="set1"

After you have configured your system components, you can begins scaling your system. Keep the
following in mind when scaling.
Tip
A maximum of 6 OPCs can be supported per Cisco PGW 2200 Softswitch.

group of 32 links. As many as 192 links can be supported per Cisco PGW 2200 Softswitch.
Planning for future network expansion by spreading the linksets evenly across the Control Channels is
suggested. Failure to do so will require the linksets to be removed from service to add more links.
As many as 256 NASs can be supported. When creating IP links to the NASs, increment the MGC port
number after 32 links have been added. Be sure to set the NAS RLM to match the MGC RLM port value.
OL-1110-23
5-75
Chapter 5
Dynamically Configuring the Input/Output Channel Controller

When dynamically configuring the IOCC, evenly distribute number of channels associated with one
channel controller. For different signaling service, there are different rules when associating channels
with channel controllers. The number of links associated with a channel controller is configurable on a
protocol family basis through parameters contained in XECfgParm.dat. If the number of links exceeds
the limit defined in XECfgParm.dat, a new instance of channel controller is created.
The naming convention for creating a new channel controller is the first five characters of the protocol
family, plus a dash (-), and <num>, where num is number of channel controllers per protocol family
created so far.
Table 5-10
Scaling Links per Protocol Family
Signaling Protocol
Type
Family
Criteria for a Unique IOCC
Criteria for a Valid Link (Channel)
Parameter in
XECfgParm.dat (Default
maximum number of
links)
NAS
Port number.
Local port and peer port must be the same.
MaxNumLinks
Number of links.
The port number must always be an odd

number.
(32)
PRIIP
When a channel controller

is created, the RLM port
number is created as the
property port for this
channel with the value of
the actual port number
(minus 1) in
properties.dat. The format
is:
<IOCC MML Name>.port
= <port number> - 1
IPFAS
PRIL3
Number of links.
Links associated with the
same port number cannot
be split over different
channel controllers.
The number of links on the same port cannot

exceed the maximum number of links specified
in XECfgParm.dat.
Links associated with the same signaling
service must use the same port number. (that is,
redundant links).
Redundant links do not count when validating
the maximum number of links per IOCC.
The number of links on the same port cannot MaxNumPRIL3Links

exceed the maximum number of links specified
(168)
in XECfgParm.dat.
Links associated with the same signaling
redundant links).
5-76
OL-1110-23
Chapter 5

Table 5-10
Scaling Links per Protocol Family (continued)
Parameter in
XECfgParm.dat (Default
maximum number of
links)
Signaling Protocol
Type
Family
Criteria for a Unique IOCC
Criteria for a Valid Link (Channel)
MGCP
Number of links.
The number of links on the same port cannot MaxNumMGCPLinks

exceed the maximum number of links specified (1000)
in XECfgParm.dat.
MGCP
Links associated with the

same port number cannot
split over different channel Links associated with the same signaling
controllers.
redundant links).
SGCP
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
SS7-ANSI Protocol Family

SS7-UK
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)
SS7-China Number of links.

SS7-Japan
Table 5-11
Maximum Scaling Limits for the SS7 Components
Component
Scaling Limit
SS7 IOCC Instances
Linksets per SS7 IOCC
16
Links per SS7 IOCC
32
DPCs per SS7 IOCC
256
True OPCs per SS7 IOCC
* Indicates the component must be spread evenly across the

maximum number of IOCC instances.
OL-1110-23
5-77
Chapter 5
Provisioning Examples
Table 5-11
Maximum Scaling Limits for the SS7 Components (continued)
Component
Scaling Limit
Routes per SS7 IOCC
512
Protocol families per SS7 IOCC
Switch types per SS7 IOCC
Links per Cisco PGW 2200 Softswitch*
192
Linksets per Cisco PGW 2200 Softswitch*
96
True OPCs per Cisco PGW 2200 Softswitch*
DPCs per Cisco PGW 2200 Softswitch*
600
Routes per Cisco PGW 2200 Softswitch*
1200
Capability point codes (8 per IOCC)
48
M3UA true OPCs per

64
M3UA routes per OPC/DPC pair per

M3UA SGPs per Cisco PGW 2200 Softswitch
96
M3UA signaling services per

1536
* Indicates the component must be spread evenly across the

maximum number of IOCC instances.
The following sections provide provisioning examples for Cisco PGW 2200 Softswitch operating
conditions.
Configuring Two IP Addresses on the MGW to One IP Address on a NAS

When configuring an Cisco PGW 2200 Softswitch with dual Ethernet interfaces to a NAS with a single
IP address, there is not IP redundancy between the Cisco PGW 2200 Softswitch and the NAS. Even
though there are two signal paths defined from the Cisco PGW 2200 Softswitch to the NAS, in the
Solaris environment, only one path is recognized. This means only one IP address on the NAS is used
for RLM signaling. Thus, a single Ethernet interface failure at the Cisco PGW 2200 Softswitch can be
a single point of failure between the Cisco PGW 2200 Softswitch and the NAS even though the
Cisco PGW 2200 Softswitch has another Ethernet interface that could communicate with the NAS.
The reason for this is that the Solaris routing table does not use two different routes to the same
destination at the same time. The Solaris routing tables does not use the source address to determine the
path just the destination address. Since both Cisco PGW 2200 Softswitch signal channels have the same
destination, they are assigned the same route. However, since both signal channels from the NAS have
different destinations, they are assigned two different paths.
This feature allows the I/O Channel Manager process of the Cisco PGW 2200 Softswitch to change the
Solaris routing table based on the state of the Ethernet interfaces of the Cisco PGW 2200 Softswitch. If
the hme0 interface fails, then the Solaris routing table is been updated to use the hme1 interface to get
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.
OL-1110-23
5-79
Chapter 5
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
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Session Sets
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:sessionset:name="c7sset1",ipaddr1="IP_Addr1",ipaddr2="IP_Addr2",
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",
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,
nexthop="10.82.82.1",netmask="255.255.255.0"
prov-add:IPLNK:NAME="nas-lnk37b",DESC="IP link B to va-5300-37",
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
OL-1110-23
5-81
Chapter 5
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
!
controller T1 3
framing esf
linecode b8zs
!
!
!
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
server va-surrey
!
!
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.

If the A-number Nature of Address (NOA) of the following number is international, then the
Cisco PGW 2200 Softswitch can remove from 1 up to 5 leading digits (country codes):
Calling Party Number (CgPN)
Generic Number Additional Calling Party Number (GN_ACgPN)
Redirecting Number (RDN)
Original Called Number (OCN)
Presentation Number (PN)
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.
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).
CODEC Capabilities and DTMF Preferential Routing

The Cisco PGW 2200 Softswitch can influence CODEC selection to IP calls (SIP and H.323 calls).
Users can also determine that there is no common CODEC or DTMF capability between a certain ingress
and egress destination, allowing route advance to an egress destination that can either directly handle the
combination, or else an IP-IP gateway that can perform transcoding. The Cisco PGW 2200 Softswitch
supports route advance when the type of DTMF interworking does not match.
To add CODEC capabilities and DTMF preferential routing, perform the following procedure:
Step 1
Step 2
Add the DTMF capability on an egress trunk group:

mml> prov-add:trnkgrpprop:name="1111",DtmfCap="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
Add Level 1 (signaling path) CODEC capabilities:

mml> prov-add:sigsvcprop:name="mgcp1",GWDefaultCodecString="G.711a;PCMA"
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
Add two codec strings, G.729, and G.721:

mml> prov-add:codecstring:name="codec1",codecstring="G.729"
mml> prov-add:codecstring:name="codec2",codecstring="G.721"
5-84
OL-1110-23
Chapter 5

Step 9
Add the results of the CODEC result type:

mml> numan-add:resulttable:custgrpid="1111",resultype="CODEC",dw1="codec1",dw2="1",
setname="set1",name="rt1"
mml> numan-add:resulttable:custgrpid="1111",resulttype="CODEC",dw1="codec2",dw2="1",
setname="set2",name="rt1"
Step 10
Add the results of the ROUTE result type:

mml> numan-add:resulttable:custgrpid="1111",name="table10",resulttype="ROUTE",
dw1="rtlist1",setname="set1"
mml> numan-add:resulttable:custgrpid="1111",name="table10",resulttype="ROUTE",
dw1="rtlist1",setname="set2"
Step 11
Add entries in the A digit tree and the B digit tree:

mml> numan-add:adigittree:custgrpid="1111",digitstring="1",callside="originating",
setname="set1"
mml> numan-add:bdigittree:custgrpid="1111",digitstring="2",callside="originating",
setname="set2"
Step 12

A sigPath property (TBufferDigitLength) that allows you to limit the digit length of the called party
number (B-number) in the outgoing ISUP IAM and subsequent address message (SAM(s)). If the
number of digits in the next SAM is also greater than the limit, the number of digits in the SAM is limited
again, until all digits are passed in SAM(s). This is required for proper interconnection to certain
international networks.
To provision digit buffering for international gateways, perform the following steps:
Step 1
Step 2
Set the digit length limit by using the following MML command:
mml> prov-ed:sigsvcprop:name="ss7svc1",tbufferdigitlength="16"
Step 3
DPNSS Service Interworking with Cisco CallManager Over

QSIG Tunneling
This feature added a new interface for the DPNSS service interworking with Cisco CallManager using
QSIG tunneling feature. It also enhances signaling interworking and feature transparency between
Cisco CallManagers (CCM) and TDM-based PBXs over DPNSS and QSIG interfaces. The
Cisco PGW 2200 Softswitch in this application works with single or multiple clusters of CCM over
H.323 interface by using the H.323 Signaling Interface (HSI) and TDM-based private branch exchanges
OL-1110-23
5-85
Chapter 5
DPNSS Service Interworking with Cisco CallManager Over QSIG Tunneling
(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 Transit, page 5-86
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 Call Completion, page 5-91
Provisioning Message Waiting Indicator (with no QSIG Tunneling), page 5-92
Provisioning Message Waiting Indicator (with QSIG Tunneling), page 5-94
Provisioning a Customer VPN ID in a Trunk Group, page 5-95
Provisioning a Customer VPN ID in the Dial Plan, page 5-95
Provisioning Feature Transparency on QSIG Trunk Groups or sigPaths, page 5-95
Provisioning an H.323 EISUP Trunk Group or sigPaths for Transparent Annex M1 (Tunneled
QSIG), page 5-96
Provisioning Route Optimization Transit

This section describes the provisioning procedure for route optimization transit. Figure 5-8 shows a
sample diagram for DPNSS route optimization transit.
5-86
OL-1110-23
Chapter 5

Figure 5-8
DPNSS Route Optimization Transit
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
To provision DPNSS route optimization transit, perform the following steps:

Step 1
Start a provisioning session by using the following MML command:

mml> prov-sta::srcver="ro1",dstver="ROPR001"
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
Modify the signaling service properties on the DPNSS signaling path:

mml> prov-add:sigsvcprop:name="dpnss-path-1",DpnssRORoutingNumberLength="3"
mml> prov-add:sigsvcprop:name="dpnss-path-1",FeatureTransparencyDisabled="1"
mml> prov-add:sigsvcprop:name="dpnss-path-1",OwnRoutingNumber="488"
Step 4
Add MGCP signaling path to the DPNSS media gateway:

mml> prov-add:MGCPPATH:name="dpnss-mgcp1",DESC="Nothing defined",extnode="va-3745-2"
mml> prov-add:IPLNK:name="dpnss-1",DESC="mgcp link to 3745",SVC="dpnss-mgcp1",
ipaddr="IP_Addr1",port=2427,peeraddr="192.0.2.31",peerport=2427,pri=1,IPROUTE=""
mml> prov-add:SIGSVCPROP:name="dpnss-mgcp1",mgcpDomainNameRemote="S2/DS1-0/1@192.0.2.255"
OL-1110-23
5-87
Chapter 5
Step 5
Add trunk groups, and trunks to the DPNSS media gateway:

mml> prov-add:TRNKGRP:name="3100",clli="dpnss",svc="dpnss-path-1",type="TDM_DPNSS",
SELseq="LIDL"
mml> prov-add:SWITCHTRNK:name="1",trnkgrpnum="3100",span="ffff",cic=1,cu="va-3745-2",
spansize=31,endpoint="s2/ds1-0/1@192.0.2.255"
mml> prov-add:RTTRNKGRP:name="3100",type=6
mml> prov-add:RTTRNK:name="rt-dpnss-3725",trnkgrpnum=3100
mml> prov-add:RTLIST:name="rtlist-dpnss-3745",rtname="rt-dpnss-3725",distrib="OFF"
mml> prov-ed:TRNKGRPPROP:name="3100",custgrpid="1111",MGCdomain="192.0.2.40"
Step 6
Add the HSI external node, sh-bighead:

mml> prov-add:EXTNODE:name="sh-bighead",desc="HSI sh-bighead",type="H323",
isdnsigtype="N/A",GROUP=0
Step 7
Add the EISUP signaling path to the HSI:

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.31",peerport=8003,pri=1,IPROUTE=""
mml>
mml>
mml>
mml>
mml>
mml>
mml>
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"
Add trunks and trunk groups to the HSI:

mml>
mml>
mml>
mml>
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
Add the dial plan, 1111:

mml> numan-add:DIALPLAN:custgrpid="1111",overdec="NO"
Step 10
Add a result of the ROUTE result type for 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:BDIGTREE:custgrpid="1111",callside="originating",digitstring="4",
setname="eisup-set4"
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"
setname="dpnss-rs-1"
Step 12
Add a result of the RTRN_START_ANALresult type:

mml> numan-add:RESULTSET:custgrpid="1111",name="self-set02"
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"
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"
setname="446"
Step 14
Provisioning Route Optimization Initiated by the Cisco PGW 2200 Softswitch

To do route optimization originating provisioning, perform the following steps:
Step 1
Start the provisioning by using the following MML command:

mml> prov-sta::srcver="roo1",dstver="ROPR001"
Step 2
Add OPC, DPC, and the SS7 signaling path:

mml> prov-add:OPC:name="opc",desc="PGW point code",netaddr="2.5.5",netind=2,type="TRUEOPC"
mml> prov-add:DPC:name="dpc1",desc="INET point code 2.4.4",NETADDR="2.4.4",netind=2
mml> prov-add:SS7PATH:name="ss7svc1",desc="SS7 service to DPC 2.4.4",mdo="ISUPV3",
custgrpid="1111",side="network",dpc="dpc1",opc="opc",m3uakey="",origlabel="",termlabel=""
Step 3
Add the Cisco ITP-L external node:

mml> prov-add:EXTNODE:name="slt7",desc="sh-2600-7",type="SLT",isdnsigtype="N/A",group=0
mml> prov-add:LNKSET:name="linkset1",desc="Linkset 1 to INET",apc="dpc1",proto="SS7-ITU",
type="IP"
mml> prov-add:SS7ROUTE:name="ss7route1",desc="Route to DPC-2-4-4",opc="opc",dpc="dpc1",
lnkset="linkset1",PRI=1
mml> prov-add:SESSIONSET:name="c7sset7",extnode="slt7",ipaddr1="IP_Addr1",
peeraddr1="192.0.2.32",port=7000,peerport=7000,type="BSMV0"
mml> prov-add:C7IPLNK:name="ss7link1",desc="Signal link",lnkset="linkset1",slc=0,pri=1,
timeslot=2,sessionset="c7sset7"
Step 4
Add the external node, Cisco AS5300 media gateway.

mml> prov-add:EXTNODE:name="sh-5300-5",desc="mgw
sh-5300-5",type="AS5300",isdnsigtype="N/A",group=0
mml> prov-add:MGCPPATH:name="mgcppath5300-5",desc="MGCP service to AS-5300-5",
extnode="sh-5300-5"
mml> prov-add:IPLNK:name="mgcplink-5",desc="MGCP link to AS-5300-5",SVC="mgcppath5300-5",
ipaddr="IP_Addr1",port=2427,peeraddr="192.0.2.33",peerport=2427,PRI=1,iproute=""
mml> prov-add:SIGSVCPROP:name="mgcppath5300-5",mgcpDomainNameRemote="s0/ds1-1/1@sh-5300-5"
mml> prov-add:SIGSVCPROP:name="mgcppath5300-5",srcpIpPortLocal="2428"
Step 5
Add trunks, and route lists:

mml> prov-add:TRNKGRP:name="1100",clli="INET-DPC1",svc="ss7svc1",type="TDM_ISUP",
SELseq="LIDL"
mml> prov-add:SWITCHTRNK:name="1",trnkgrpnum="1100",span="ffff",cic=1,cu="sh-5300-5",
spansize=31,endpoint=s0/ds1-1/1@192.0.2.254
OL-1110-23
5-89
Chapter 5
mml>
mml>
mml>
mml>
Step 6
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"
Add the HSI external node, sh-bighead:

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",
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.33",peerport=8003,pri=1,iproute=""
mml> prov-add:SIGSVCPROP:name="eisup-bighead",AllowH323Hairpin="1"
mml> prov-add:SIGSVCPROP:name="eisup-bighead",FeatureTransparencyDisabled="1"
mml> prov-add:SIGSVCPROP:name="eisup-bighead",H323AdjunctLink="1"
mml> prov-add:SIGSVCPROP:name="eisup-bighead",OOverlap="1"
mml> prov-add:SIGSVCPROP:name="eisup-bighead",OwnRoutingNumber="545"
mml> prov-add:SIGSVCPROP:name="eisup-bighead",QSIGTunnelVariant="1"
mml> prov-add:SIGSVCPROP:name="eisup-bighead",TOverlap="0"
Step 7
Add trunk groups and rout e lists to the HSI:

mml>
mml>
mml>
mml>
prov-add:TRNKGRP:name="9300",clli="EISUP2B",svc="eisup-bighead",type="IP"
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
Add a dial plan and digit modifications:

mml>
mml>
mml>
mml>
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"
Add the result of the ROUTE result type for SS7:

mml> numan-add:RESULTSET:custgrpid="1111",name="ss7-set1"
mml> numan-add:RESULTTABLE:custgrpid="1111",name="ss7-result1",resulttype="ROUTE",
dw1="rtlist-ss7-1",setname="ss7-set1"
setname="ss7-set1"
Step 10
Add a result of the ROUTE result type for HSI:

mml> numan-add:RESULTSET:custgrpid="1111",name="eisup-set4"
mml> numan-add:RESULTTABLE:custgrpid="1111",name="eisup-result4",resulttype="ROUTE",
Step 11
Add a result of the RTRN_START_ANAL result type:

mml> numan-add:RESULTSET:custgrpid="1111",name="self-set02"
mml> numan-add:RESULTTABLE:custgrpid="1111",name="self-result02",
resulttype="RTRN_START_ANAL",dw1="02",setname="self-set02"
setname="self-set02"
Step 12
Add the result of the ROUTE result type for the Cisco PGW 2200 Softswitch whose routing number for
is 545:
5-90
OL-1110-23
Chapter 5

mml> numan-add:RESULTTABLE:custgrpid="1111",name="545",resulttype="RTRN_START_ANAL",
dw1="3",setname="545"
setname="545"
Step 13
Provisioning Route Optimization Responded by the Cisco PGW 2200 Softswitch

To do route optimization terminating provisioning, perform the following steps:
Step 1
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:
mnl> numan-add:RESULTTABLE:custgrpid="1111",name="446",resulttype="ROUTE",
dw1="rtlist-bighead",setname="446"
setname="446"
Step 3
Provisioning Call Completion

To provision call completion, perform the following steps:
Step 1
Follow Step 1 to Step 6 in the previous procedure described in Provisioning Route Optimization
Transit section on page 5-86.
Step 2
Add the EISUP signaling path to the HSI:

mml> prov-add:eisuppath:name="eisup-bighead",desc="EISUP to HSI sh-bighead",
mml> prov-add:iplnk:name="ip-bighead",desc="IP lnk to HSI sh-bighead",svc="eisup-bighead",
mml>
mml>
mml>
mml>
mml>
mml>
mml>
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"
Add trunk groups and route lists:

mml>
mml>
mml>
mml>
prov-add:trnkgrp:name="9300",clli="EISUP2B",svc="eisup-bighead",type="IP"
prov-add:rttrnk:weightedtg="OFF",name="eisup-bighead",trnkgrpnum=9300
prov-add:rtlist:name="rtlist-bighead",rtname="eisup-bighead"
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"

mml> numan-add:dialplan:custgrpid="1111",overdec="NO"
Step 5
Add the result of the ROUTE result type for HSI:

mml> numan-add:resultset:custgrpid="1111",name="eisup-set4"
mml> numan-add:resulttable:custgrpid="1111",name="eisup-result4",resulttype="ROUTE",
mml> numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="4",
Step 6
Add the result of the ROUTE result type for DPNSS:

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"
setname="dpnss-rs-1"
Step 7
Provisioning Message Waiting Indicator (with no QSIG Tunneling)

To provision message waiting indicator, with no QSIG tunneling enabled, perform the following steps:
Step 1
Start a provisioning session:

mml> prov-sta:srcver="qsig1",dstver="QSIGdis"
Step 2
Add the Cisco 5400 external node for DPNSS:

mml> prov-add:extnode:name="sh-stim-001",desc="sh-stim-3001 for dpnss",type="AS5400",
isdnsigtype="IUA",group=0
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
mml> prov-add:dpnsspath:name="dpnss-pathin1",desc="dpnss sh-001",extnode="sh-stim-001",

mdo="DPNSS_BTNR188",custgrpid="1111",sigslot=0,sigport=0
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"
mml> prov-ed:sigsvcprop:name="dpnss-pathin1",MwiStringOFF ="*58*AN*1"

mml> prov-ed:sigsvcprop:name="dpnss-pathin1",MwiStringON ="*58*AN*0"
Step 4
Add trunk groups for DPNSS:

mml> prov-add:trnkgrp:name="3600",svc="dpnss-pathin1",type="TDM_DPNSS",selseq="ASC",
qable="N"
mml> prov-add:trnkgrpprop:name="3600",CustGrpId="1111",gatewayrbtonesupport="1"
mml> prov-add:trnkgrpprop:name="3600",customervpnid="1"
mml> prov-add:trnkgrpprop:name="3600",FeatureTransparencyDisabled ="0"
mml> prov-add:switchtrnk:name="3600",trnkgrpnum="3600",spansize=31,span="ffff",cic=1,
endpoint="S0/ds1-0/1@192.0.2.250",cu="sh-stim-001"
mml> prov-add:rttrnkgrp:name="3600",type=6,reattempts=2,queuing=30,cutthrough=3
mml> prov-add:trnkgrpprop:name="3600",MwiStringOFF ="*58*AN*1"
mml> prov-add:trnkgrpprop:name="3600",MwiStringON ="*58*AN*0"
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: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
Add trunk groups and route lists for Cisco HSI:

mml>
mml>
mml>
mml>
Step 7

Step 8
Add results, a B digit tree entry, and digit modifications for Cisco HSI:
mml> numan-add:resulttable:custgrpid="1111",name="tab33",resulttype="BNBRMODMWI",
dw1="mwion", dw2="wioff",setname="rset33"
mml> numan-add:digmodstring:custgrpid="1111",name="mwioff",digstring="5719"
mml> numan-add:digmodstring:custgrpid="1111",name="mwion",digstring="5718"
OL-1110-23
5-93
Chapter 5
Step 9
Provisioning Message Waiting Indicator (with QSIG Tunneling)

The following MML commands are an example of message waiting indicator, with QSIG tunneling
enabled, provisioning.
Step 1
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:iplnk:name="ip-bighead",desc="IP lnk to HSI sh-bighead",svc="eisup-bighead",
Step 3
Modify property values of the EISUP signaling path:

mml>
mml>
mml>
mml>
mml>
mml>
mml>
Step 4
Step 5
prov-add:sigsvcprop:name="eisup-bighead",OwnRoutingNumber="545"
Add trunk groups and route lists for Cisco HSI:

mml>
mml>
mml>
mml>
mml>
mml>
mml>
mml>

Step 6
Add results and a B digit tree entry in the dial plan 1111:
Step 7
5-94
OL-1110-23
Chapter 5

Provisioning a Customer VPN ID in a Trunk Group

To provision a VPN ID in a trunk group, use the following MML commands in an open provisioning
session:
mml>
mml>
mml>
mml>
Provisioning a Customer VPN ID in the Dial Plan

To provision a VPN ID in a dial plan, perform the following steps:
Step 1
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
Add an A-number digit tree entry to the result set:

mml> numan-add:adigtree:custgrpid="T002",digitstring="0",callside="originating",
setname="VpnCul"
Step 4
Add B-number NPI and NOA results in the pre-analysis:

mml> numan-add:bnpi:custgrpid="T002",npiblock=1,setname="VpnCust1"
mml> numan-add:bnoa:custgrpid="T002",noavalue=1,npiblock=1
Step 5
Provisioning Feature Transparency on QSIG Trunk Groups or sigPaths

To provision feature transparency on QSIG trunk groups or sigPaths, perform the following steps:
Step 1
Enable feature transparency by using the following MML commands:

mml> prov-ed:sigsvcprop:name="Q-PBX-1",FeatureTransparencyDisabled="0"
Step 2
Assign a customer VPN ID and profile indexes:

mml> prov-ed:sigsvcprop:name="Q-PBX-1",CustomerVPNid="CUST-1"
mml> prov-ed:sigsvcprop:name="Q-PBX-1",CustomerVPNOnNetTblNum="5"
mml> prov-ed:sigsvcprop:name="Q-PBX-1",CustomerVPNOffNetTblNum="6"
Step 3
Enable the path replacement and route optimization:

mml> prov-ed:sigsvcprop:name="Q-PBX-1",OwnRoutingNumber="1234"
OL-1110-23
5-95
Chapter 5
Step 4
Provisioning an H.323 EISUP Trunk Group or sigPaths for Transparent Annex M1

(Tunneled QSIG)
To provision an H.323 EISUP trunk group or sigPaths for Transparent Annex M1 (Tunneled QSIG),
perform the following steps:
Step 1
Enable QSIG tunneling by using the following MML command:

mml> prov-ed:sigsvcprop:name="EISUP-HSI-1",QSIGTunnelVariant="1"
Step 2
Assign a customer VPN ID and profile indexes:

mml> prov-ed:sigsvcprop:name="EISUP-HSI-1",CustomerVPNid="CUST-1"
mml> prov-ed:sigsvcprop:name="EISUP-HSI-1",CustomerVPNOnNetTblNum="5"
mml> prov-ed:sigsvcprop:name="EISUP-HSI-1",CustomerVPNOffNetTblNum="6"
Step 3
Enable path replacement and route optimization:

mml> prov-ed:sigsvcprop:name="EISUP-HSI-1",OwnRoutingNumber="1234"
Step 4
Disable feature transparency for CCM interworking:

mml> prov-ed:sigsvcprop:name="EISUP-HSI-1",FeatureTransparencyDisabled="1"
Step 5
Note
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.

Enhanced Local Number Portability (LNP) and dial plan selection extend the table look up capability to
provide searches with longest match and partial (substring) matches for the ported number and A number
dial plan selection tables.
To provision enhanced LNP and dial plan selection, perform the following steps:
Step 1
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
Add A-number dial plan selection:
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.
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.
Add entries in B digit tree:

mml> numan-add:bdigtree:custgrpid="1111",digitstring="99812",callside="originating",
setname="rtsetlnp99812"
setname="rtsetdpsel996"
Step 7

You can find the provisioning procedure in the Provisioning Full Number Translations section of
Chapter 4, Provisioning Dial Plans with MML, in Cisco PGW 2200 Softswitch Release 9 Dial Plan
Guide (through Release 9.7).
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).
OL-1110-23
5-97
Chapter 5

The H.248 feature provides a gateway control interface between the PGW 2200 and the VXSM
gateways. It supplements the MGCP protocol. This new interface is based on the ITU-SG16/IETF
specification of H.248 which defines a decomposed gateway architecture.
Although H.248 is designed to be generic in its support for many different kinds of media, the
Cisco PGW 2200 Softswitch is mainly designed to act as an MGC and only interwork with trunking
gateways. This feature addresses only the functionality of the interworking of the
Cisco PGW 2200 Softswitch with trunking gateways. Figure 5-9 shows an overview of this system.
Figure 5-9
H.248 Protocol in the SS7 Network
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
Start the provisioning by using the following MML command:

mml> prov-sta::srcver="base1",dstver="H248"
Step 2
Follow either of the two following steps to add H.248 sigPath:
5-98
OL-1110-23
Chapter 5

H.248 sigPath based on UDP transport

mml> prov-add:EXTNODE:NAME="h248-VXSM-01",DESC="VXSM-01",TYPE="VXSM"
mml> prov-add:H248PATH:NAME="h248-sigpath-UDP",DESC="Service to H248",
EXTNODE="h248-VXSM-01"
mml> prov-add:IPLNK:NAME="h248-udp-link-1",DESC="UDP link to h248-sigpath-UDP",
SVC="h248-sigpath-UDP",IPAddr="IP_Addr1",PORT=2944,PEERADDR="192.0.2.38",
PEERPORT=2944, PRI=1
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
Add SS7 sigPaths:

mml> prov-add:OPC:NAME="opc",DESC="Own Point Code",NETADDR="1.0.1",NETIND=2,TYPE="TRUEOPC"
mml> prov-add:DPC:NAME="sp1",DESC="SP1 Point Code",NETADDR="4.0.1",NETIND=2
mml> prov-add:DPC:NAME="sp2",DESC="SP2 Point Code",NETADDR="4.0.2",NETIND=2
mml> prov-add:SS7PATH:NAME="ss7svc1",DESC="SS7SigPathtoSP1",MDO="Q761_BASE",
CUSTGRPID="1111", SIDE="network",DPC="sp1",OPC="opc",M3UAKEY=""
mml> prov-add:SS7PATH:NAME="ss7svc2",DESC="SS7SigPathtoSP2",MDO="Q761_BASE",
CUSTGRPID="1111",SIDE="network",DPC="sp2",OPC="opc",M3UAKEY=""
mml> prov-add:LNKSET:NAME="lnkset1",DESC="LinkSet to SP1",APC="sp1",PROTO="SS7-ITU",
TYPE="IP"
mml> prov-add:LNKSET:NAME="lnkset2",DESC="LinkSet to SP2",APC="sp2",PROTO="SS7-ITU",
TYPE="IP"
mml> prov-add:SS7ROUTE:NAME="route1",DESC="Route to SP1", OPC="opc",DPC="sp1",
LNKSET="lnkset1",PRI=1
mml> prov-add:SS7ROUTE:NAME="route2",DESC="Route to SP2", OPC="opc",DPC="sp2",
LNKSET="lnkset2",PRI=1
mml> prov-add:EXTNODE:NAME="sh-2600-3",DESC="SLT-2600-3",TYPE="SLT",ISDNSIGTYPE="N/A"
mml> prov-add:SESSIONSET:NAME="c7-2600-3",EXTNODE="sh-2600-3",IPADDR1="IP_Addr1",
PORT=7000,PEERADDR1="192.0.2.40", PEERPORT=7000,TYPE="BSMV0"
mml> prov-add:C7IPLNK:NAME="c7iplnk1-1",DESC="SS7Link1inLinkSet1",LNKSET="lnkset1",SLC=0,
PRI=1,TIMESLOT=0,SESSIONSET="c7-2600-3"
mml> prov-add:C7IPLNK:NAME="c7iplnk2-1",DESC="SS7Link1inLinkSet2",LNKSET="lnkset2",SLC=0,
PRI=1,TIMESLOT=1,SESSIONSET="c7-2600-3"
Step 4
Add trunk groups and trunks:

mml> prov-add:trnkgrp:name="1111",clli="NULL",svc="ss7svc1",type="TDM_ISUP"
mml> prov-ed:trnkgrpprop:name="1111",custgrpid="1111"
/* For OC3 with Descriptive Text */
mml> prov-add:switchtrnk:name="1",trnkgrpnum="1111",span="ffff",cic=1,cu="h248-vxsm-01-1",
spansize=15,endpoint="DS/OC3_1/T1_7/1"
OL-1110-23
5-99
Chapter 5
Lawful Intercept
/* For OC3 without Descriptive Text */

mml> prov-add:switchtrnk:name="1",trnkgrpnum="1111",span="ffff",cic=1,cu="h248-vxsm-01-1",
spansize=15,endpoint="DS/ 1/7/1"
/* For STM with Descriptive Text */
mml> prov-add:switchtrnk:name="16",trnkgrpnum="1111",span="ffff",cic=16,
cu="h248-vxsm-01-1",spansize=15,endpoint="DS/STM_1/T1_7/1"
/* For STM without Descriptive Text */
cu="h248-vxsm-01-1",spansize=15,endpoint="DS/1/7/1"
/* For T1 with Descriptive Text */
cu="h248-vxsm-01-1",spansize=15,endpoint="DS/T1_2/7"
/* For T1 without Descriptive Text */
cu="h248-vxsm-01-1",spansize=15,endpoint="DS/2/7"
/* For T3 with Descriptive Text */
cu="h248-vxsm-01-1",spansize=15,endpoint="DS/T3_1/T1_2/7"
/* For T3 without Descriptive Text */
cu="h248-vxsm-01-1",spansize=15,endpoint="DS/1/2/7"
Step 5
Modify H.248 related properties:

mml> prov-ed:trnkgrpprop:name="1111",H248GatewayReserveValue="0"
Note
The property H248GatewayReserveValue is deleted in Release 9.7P23 and later.
mml> prov-ed:sigsvcprop:name="h248-vxsm-01-1",GWProtocolVersion="H248 V2"

mml> prov-ed:sigsvcprop:name="h248-vxsm-01-1",h248DomainNameRemote="<VXSM.CISCO.COM>"
mml> prov-ed:sigsvcprop:name="h248-sigpath-01", h248inactivitytimer="1000"
Step 6
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.
5-100
OL-1110-23
Chapter 5

Lawful Intercept
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
H.225 CC, H.245

H.225 RAS
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
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.
Provisioning LI for the Service Provider

To provision lawful intercept on the Cisco PGW 2200 Softswitch, perform the following steps:
Step 1
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
Provision the LI Mediation Device Communication Path.
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).
OL-1110-23
5-101
Chapter 5
Location Mapping
Step 4
Add the LI mediation device as an external node in an open provisioning session:

mml> prov-add:EXTNODE:NAME="LI-node",TYPE="LIMD", DESC="LI Mediation Device"
Step 5
Add the LI mediation device signaling path:

mml> prov-add:LIPATH:NAME="LIsigPath",DESC="SigPath to the LI",EXTNODE="LI-node"
Step 6
Add the LI mediation device IP Link:
Note
This MML command defines an IP link to the LI mediation device and associates an LI sigPath
to the IP link.
mml> Prov-add:IPLNK:NAME="lilink", DESC="IP link to the LI", SVC="lipath",

IPADDR="IP_addr1", PORT="1813", PEERADDR="192.0.2.41", PEERPORT="1813"
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
Provisioning a Wiretap Entry for the Medication Device

You must be an authorized LI user and logged in as liusr to add a wiretap entry. Only one MML session
per LI user is allowed at any time to log in to the Cisco PGW 2200 Softswitch.
In the following example, the wiretap call data is sent to the LI mediation device at IP address
192.0.2.42, and port number 1813 (which was configured as an IP link to an external node of type LI).
You can use one of the following three commands to add a wiretap entry:
Add a wiretap entry for an individual number:

wiretap-add:subscriber:number="7035551234",type="calldata",cdc_ip="192.0.2.42",
cdc_port="1813"
Add a wiretap entry for a trunk group ID:

wiretap-add:trunkgroup:name="3700",type="calldata",cdc_ip="192.0.2.42",
cdc_port="1813"
Add a wiretap entry based on a partial number:

wiretap-add:partialnumber:number="partial_number",type="calldata",
cdc_ip="192.0.2.42",cdc_port="1813"
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.
5-102
OL-1110-23
Chapter 5

Location Mapping
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.
Override the default location value with a new location value.
Use the default location value if no location value is set.
Map a location value to new values without changing cause values, with the use of wildcard of cause
value.
Provisioning Location Values

To use location in the cause analysis, perform the following steps:
Step 1
Add the dial plan, Nat1, in an open provisioning session by using the following MML command:
mml> numan-add:dialplan:custgrpid="Natl"
Step 2
Add a service, TollFree:

mml> numan-add:service:custgrpid="Natl",name="TollFree"
Step 3
Add the result set, chCause, in dial plan Nat1:

mml> numan-add:resultset:custgrpid="Natl",setname="chCause"
Step 4
And cause analysis data:

mml> numan-add:resulttable:custgrpid="Natl",setname="chCause", resulttype="CAUSE",
name="cause1",dw1=8,dw2=7
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
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.
Provisioning Internal Cause Value Mapping

To map internal cause 1 (Unallocated Number) and location 3 to internal cause 36 (Number Changed),
perform the following steps:
Step 1
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
Add cause analysis data (cause value 36):

mml> numan-add:resulttable:custgrpid=" Natl",setname="chCause",resulttype="CAUSE",
name="cause1",dw1=36
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).
mml> numan-add:cause:custgrpid="Natl",causevalue=1,locationblock=1
Provisioning Cause Value Mapping

Cause Value Mapping Based on Received Cause and Location Values
To map from SIP cause 408 and 504 to SS7 cause 20 (Subscriber Absent), perform the following steps:
Step 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
Add cause analysis data (cause value 91):

mml> numan-add:resulttable:custgrpid="Natl",name="SubAbsent",resulttype="CAUSE",dw1=91,
setname="chgCause"
Step 3
Associate the result set, chgCause, with the cause value 40:
5-104
OL-1110-23
Chapter 5

Location Mapping
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.
Cause and Location Value Mapping to Different Values

To map all cause and location values of 3 to cause value 40 and location value 4, perform the following
steps:
Step 1
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).
mml> numan-add:cause:custgrpid="1111",causevalue="0",locationblock=1
Cause Value Mapping to Different Cause and Location Values

To map cause value 1 with any location value to cause value 40 and location value 4, perform the
following steps:
Step 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
Add cause analysis data (cause value 40 and location value 4)

mml> numan-add:resulttable:custgrpid="1111",setname="chCause1",resulttype="CAUSE",
name="cause1,dw1=40,dw2=4
OL-1110-23
5-105
Chapter 5
Multiple Inbound IP Trunks
Step 3
Associate the result set, chCause1, with the cause value 1:

mml> numan-add:cause:custgrpid="custid",causevalue="1",setname="chCause1"

The Multiple Inbound IP Trunks feature extends the Cisco PGW 2200 Softswitch ability to separate
Session Initiation Protocol (SIP) and Extended ISUP (EISUP) traffic into multiple inbound trunk groups
on a single interface. You can define inbound trunk groups based on source address, subnet, port number,
or a combination of these items.
Separating incoming IP traffic into distinct trunk groups allows you to apply unique provisioning
properties to each trunk group. This feature is useful in a multivendor SIP environment because it allows
you to manage multiple SIP implementations.
The Multiple Inbound IP Trunks feature also improves security by adding the option to discard new
messages that do not match the characteristics of defined inbound trunk groups. You can apply this
option to SIP INVITE, REFER, and NOTIFY messages and EISUP Initial Address Message (IAM)
messages.
This feature does not affect the provisioning commands used to create SIP and EISUP links or define
inbound trunk groups.
Creating a New Inbound SIP Trunk

The instructions to create a SIP path, SIP link, and inbound trunk group are optionalthey apply only
if you do not have existing SIP links and inbound trunk groups. This feature does not affect the
provisioning commands used to create SIP connections or inbound trunk groups.
To add a new inbound SIP trunk, 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="sippath-1",mdo="IETF_SIP",desc="SIP sigpath"
Step 2
Add SIP links:
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.
mml> prov-add:SIPLNK:NAME="sip-sigchan-1", DESC="SIP link 1",SVC="sip-sigpath",

IPADDR="Virtual_IP_Addr1",PORT=5060,PRI=1
mml> prov-add:SIPLNK:NAME="sip-sigchan-2",DESC="SIP link 2",SVC="sip-sigpath",
mml> prov-ed:SIPLNK:NAME="sip-sigchan-1",PORT=5061
mml> prov-ed:SIPLNK:NAME="sip-sigchan-2",PORT=5061
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.
5-106
OL-1110-23
Chapter 5

Step 3
(Optional) Add nonstandard port numbers:

mml> prov-add:siplnk:name="siplnk1",svc="sippath-1",ipaddr="IP_ADDR1",port=5060
mml> prov-ed:siplnk:name="siplnk1", port=5076
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.
Add new trunk groups for inbound SIP traffic:

mml> prov-add:trnkgrp:name="1000", svc="sippath-1", type=SIP_IN
Step 5
Map IP traffic to trunk groups:
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.
mml> prov-add:ipinmapping:name="sipinmapping-1", sigsvc="sippath-1",

allowedIP="192.0.2.43",sipport=5063, trnkgrpNum=1000
mml> prov-add:ipinmapping:name="sipinmapping-3", sigsvc="sippath-1", sipport=5064,
trnkgrpNum=1010
mml> prov-add:ipinmapping:name="sipinmapping-2",sigsvc="sippath-1",
allowedIP="192.0.2.44",allowedIPNetmask="255.255.255.0", trnkgrpNum=1040
mml> prov-ed:siplnk:name="siplnk1",port=5063
mml> prov-ed:siplnk:name="siplnk1",port=5064
Step 6
(Optional) Map multiple IP ranges to a single trunk group:

mml> prov-add:ipinmapping:name="sipinmapping-1",sigsvc="sippath-1",
allowedIP="209.165.200.245",allowedIPNetmask="255.255.255.224",trnkgrpNum=1040
mml> prov-add:ipinmapping:name="sipinmapping-2", sigsvc="sippath-1",
allowedIP="209.165.201.21",allowedIPNetmask="255.255.255.224", trnkgrpNum=1040
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.
OL-1110-23
5-107
Chapter 5
Support of HSI Non-RAS Mode
Creating a New Inbound ISUP Trunk

The instructions to create an external node, IP path, IP link, and inbound trunk group are optionalthey
apply only if you do not have existing EISUP links and inbound trunk groups. This feature does not affect
the provisioning commands used to create EISUP connections or inbound trunk groups.
Step 1
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
Add an EISUP signaling path:

mml> prov-add:eisuppath:name="eisuppath-1",desc="Eisuppath signalling service to PGW-1",
extnode="pgw-1",custgrpid="tr01"
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
Add a new trunk group for inbound EISUP traffic:

mml> prov-add:trnkgrp:name="2000",svc="eisuppath-1",type=IP
Step 5
Map IP traffic to a trunk group:
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.

In non-Registration, Admission, and Status (RAS) mode, the Cisco PGW 2200 Softswitch converts
called numbers into one or two IP addresses in the dial plan to support load sharing over multiple HSIs,
which supports H.323 endpoints that have multiple IP addresses. With such support, when the primary
IP address does not work, a subsequent attempt is made with the alternative IP address for the same
endpoint.
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.
Provisioning Cisco PGW 2200 Softswitch

To enable non-RAS mode on the Cisco PGW 2200 Softswitch, you must provision the sigPath/Trunk
group property identified as H323Destination. Non-RAS mode supports two destination addresses
configuration, a primary IP address and an alternative IP address.
To provision non-RAS support on the Cisco PGW 2200 Softswitch, perform the following steps:
Step 1
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
Use one of the three following options to configure IP addresses:
Configure a primary destination IP address

mml> prov-add:TRNKGRPPROP:name="111",H323Destination="192.168.80.2:1721"
Configure a primary destination IP address and an alternative destination IP address

mml> prov-add:TRNKGRPPROP:name="111",H323Destination="192.168.80.2;192.168.80.3"
mml> prov-add:rttrnkgrp:name="111",type=4,reattempts=1,queuing=0,cutthrough=2,
resincperc=0
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"
Provisioning Cisco HSI

For the Cisco HSI software configuration required to support the Non-RAS Mode of operation, see
Cisco H.323 Signaling Interface User Guide, for Release 4.2.
To enable non-RAS mode on the Cisco HSI, use the following MML command:
mml> prov-add:name=RAS,manualRAS
OL-1110-23
5-109
Chapter 5
Presentation Number Modification

The Presentation Number Modification feature enables a service provider to configure the
Cisco PGW 2200 Softswitch to modify the presentation number (PN) for calls between a PSTN network
on one side and a SIP server on the other.

Figure 5-11 presents a diagram that shows the Cisco PGW 2200 Softswitch properties that the service
provider must configured on trunk groups to enable the PN modification feature to convert PNs properly
for PSTN-to-SIP Calls.
PSTN
Trunk Group Configuration for PSTN-to-SIP Calls
Trunk group 1000

CCOrigin = 44
PGW 2200
Trunk group 2222

ADigitCCPrefix = 1
BDigitCCPrefix = 1
SIP
273682
Figure 5-11
To enable PN modification for PSTN-to-SIP calls, perform the following steps:

Step 1
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
Set the value of the MapCLItoSipHeader property to 0 on the terminating side:

mml> prov-ed:trnkgrpprop:name=2222,mapclitosipheader=0
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>

Figure 5-12 presents a diagram that shows the PGW 2200 properties that the service provider must
configure on trunk groups to enable the PN Modification feature to convert PNs properly for
SIP-to-PSTN calls.
For detailed information on property descriptions, see Chapter 6, Properties, of Cisco PGW 2200
Softswitch Release 9 MML Command Reference.
PSTN
Trunk Group Configuration for SIP to PSTN Calls
Trunk group 1000

ADigitCCRM = 44
BDigitCCRM = 44
PGW 2200
Trunk group 2000

SIP
InhibitSipFromMapping = 3
273683
Figure 5-12
To enable PN modification for SIP-to-PSTN calls, perform the following steps:

Step 1
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"
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

This feature provides RADIUS interface support on the Cisco PGW 2200 Softswitch for Call Detail
Record (CDR) data. CDR data is sent to a preconfigured RADIUS server at the end of the call. CDR data
for PSTN-to-IP calls as well as IP-to-PSTN calls is supported. The Cisco PGW 2200 Softswitch can be
configured for both RADIUS and normal CDR.
Before you provision the RADIUS enhancement, configure the following parameters in the
XECfgParm.dat file:
# Radius Accounting Parameters
#-------------------------------RadiusAccounting.output = off
RadiusAccounting.numberPort = 20
RadiusAccounting.smSize = 30
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
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
Add signal channels to the RADIUS accounting server:

mml> prov-add:RASERVER:NAME="raserver1",DESC="radius accounting server1",SVC="racluster",
IPADDR="IP_Addr1",PORT=1660,PEERADDR="192.0.2.46",PEERPORT=1660,IPROUTE=",ORDER=1,
KEY="Cisco-h323",TIMEOUT=5,RETRYCOUNT=2,username="Cisco",password="cisco123",authport=1661
mml> prov-add:RASERVER:NAME="raserver2", DESC="radius accounting server2",SVC="racluster",
IPADDR="IP_Addr1",PORT=1660,PEERADDR="192.0.2.47",PEERPORT=1660,IPROUTE=",ORDER=2,
KEY="Cisco-h323",TIMEOUT=10,RETRYCOUNT=4,username="Cisco",password="cisco123",
authport=1661
5-112
OL-1110-23
Chapter 5

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",
Step 2
Modify the signaling path properties:

mml> prov-ed:sigsvcprop:name="sip-path",callholdinterworkingenabled="1"
mml> prov-ed:sigsvcprop:name="sip-path",sipcallholdmethod="0"
Step 3
Add an external node of Cisco HSI type:

mml> prov-add:EXTNODE:NAME="HSI-1",DESC="EISUP to HSI",TYPE="H323",ISDNSIGTYPE="N/A",
GROUP=0
Step 4
Add the EISUP signaling path to the Cisco HSI:

mml> prov-add:EISUPPATH:NAME="eisup-hsi-1",DESC="Path to HSI-1",EXTNODE="HSI-1",
CUSTGRPID="4444"
mml> prov-add:IPLNK:NAME="eisuplnk-hsi-1",DESC="IP link to HSI-1",SVC="eisup-hsi-1",
Step 5
Add trunks and trunk groups to the Cisco HSI:

mml> prov-add:trnkgrp:name="7000",type="IP",svc="eisup-hsi-1"
mml> prov-add:trnkgrpprop:name="7000",CustGrpId="4444",btechprefix="null"
On the Cisco HSI, you need to do the following configurations:

SYS_CONFIG_STATIC.VSCA_IPADDR1 = 192.0.2.49
SYS_CONFIG_STATIC.VSCA_PORT_NUMBER1 = 8003
SYS_CONFIG_DYNAMIC.InitiateTCSAfterFSCall = 1
SYS_CONFIG_DYNAMIC.TransmitTCSAfterFSCall = 1
SIP Overlap Signaling

This feature supports SIP overlap signaling between the Cisco PGW 2200 Softswitch and the
Cisco BTS 10200 Softswitch product using a derivative of draft-zhang-sipping-overlap-01, a method for
overlap signaling in SIP.
Both the Cisco PGW 2200 Softswitch and the Cisco BTS 10200 support the sending and receiving of
overlap dialed digits over SIP. The Cisco PGW 2200 Softswitch also supports the sending and receiving
of overlap digits over the SS7 network.
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
Enable SIP overlap signaling on both trunk groups:

mml> prov-ed:trnkgrpprop:name=444,toverlap=1
mml> prov-ed:trnkgrpprop:name=666,ooverlap=1
Step 3
Set OMinDigits, OMaxDigits, TMinDigits, and TMaxDigits accordingly:

mml> prov-ed:trnkgrpprop:name=444,tmindigits=0,tmaxdigits=20,support183=3,
supportreliable100=SUPPORTED
mml> prov-ed:trnkgrpprop:name=666,omindigits=0,omaxdigits=20,support183=3,
supportreliable100=SUPPORTED
Step 4
Set the OverlapDigitTime property:

mml> prov-ed:trnkgrpprop:name=444,overlapdigittime=30

This feature provides support on the Cisco PGW 2200 Softswitch of the ISDN User Part
(ISUP)-to-Session Initiation Protocol (SIP) mapping of calling line identity (CLI) to the SIP Remote
Party ID header or the P-Asserted ID header. It also updates the generic handling of the SIP-to-ISUP and
ISUP-to-SIP mapping of CLI, generic number (GN), and redirecting number (RN).
For detailed information on property descriptions, see Chapter 6, Properties, of
Cisco PGW 2200 Softswitch Release 9 MML Command Reference.
Scenario 1
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
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.
5-114
OL-1110-23
Chapter 5

Step 2
Add a GRprofile with cgpninclude property value set to 0:

mml> prov-add:PROFILE:NAME="sippro",TYPE="grprofile",cgpninclude="0"
Step 3
Attach the GRprofile to the outgoing IP trunk group 5600:

mml> prov-add:TRNKGRPPROF:name="5600",grprofile="sippro"
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>.
Step 1
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.
Step 1
Step 2

Step 3

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.
Step 1
Step 2

Step 3


This feature introduces a Back to Back User Agent (B2BUA) mode of operation for SIP-to-SIP calls on
the Cisco PGW 2200 Softswitch. It also enhances the existing mid-call service handling to better
interwork SIP signaling for mid-call services. This feature allows Cisco PGW 2200 Softswitch handling
of SIP-to-SIP calls, including intrusive replacement of E.164 addresses appearing in various headers and
configurable handling of REFER and 3xx redirect messaging. In addition, this feature enhances the
Cisco PGW 2200 Softswitch mid-call service handling for interworking of SIP redirection and transfers
with SIP to SIP and SIP to other protocols.
Before you provision SIP service handling and feature interworking enhancement, configure the
*.sipModeSelectionControl parameter in the XECfgParm.dat file as follows:
*.sipModeSelectionControl = 1
# 1 - B2BUA mode, allow later selection of proxy mode via the dial plan.
# 2 - Fixed Proxy mode, always work in proxy mode.
For detailed descriptions on this parameter and configuration procedures, see

Cisco PGW 2200 Softswitch Release 9 Software Installation and Configuration Guide.
To provision SIP service handling and feature interworking enhancement, perform the following steps:
Step 1
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
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:
dw1="2",dw2="1",setname="rset1"
Always support backward transit of the redirection:

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:
Step 3
Add the entry in the B digit tree:

setname="rset1"

The Cisco PGW 2200 Softswitch is able to support the following take back and transfer functions with
TDM-based and SIP trunks as the calling party and/or the transferring party:
Basic Take Back and Transfer (TNT)
Intelligent Blind Transfer (iTNT) Under INAP Control
Network Blind Transfer (NBT) Under INAP Control
Network Consultation Transfer (NCT) Under INAP Control
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
mml> numan-add:dialplan:custgrpid="2222",overdec="yes"
Step 2
Set the value of MidCallServiceCustID to the mid-call dial plan ID:

mml> prov-add:sigsvcprop:name="sipsvc1",MidCallServiceCustID="2222"
Step 3
Add a result set for iTNT:

mml> numan-add:resultset:custgrpid="2222",name="rset-itnt"
OL-1110-23
5-117
Chapter 5
Step 4
Add the result of the DIGIT_REQ result type:

mml> numan-add:resulttable:custgrpid="2222",name="digit-len",resulttype="DIGIT_REQ",
setname="rset-itnt",dw1="7"
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.
Add an entry in the B digit tree:

mml> numan-add:bdigtree:custgrpid="2222",callside="originating",digitstring="B82",
setname="rset-itnt"
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.
Add the result set rset-err for playing announcement:

mml> numan-add:resultset:custgrpid="2222",name="rset-err"
Step 9
Add a result of the result type INC_NUMBERING:

mml> numan-add:resulttable:custgrpid="2222",name="max-len",resulttype="INC_NUMBERING",
setname="rset-err",dw1="0",dw2="2",dw3="2"
Note
Step 10
The result type INC_NUMBERING is used to return an announcement immediately.
Add a result of the ANNOUCEMENT result for playing announcement:

mml> numan-add:resulttable:custgrpid="2222",name="itnt-ann",resulttype="ANNOUNCEMENT",
setname="rset-err",dw1="33",dw2="0",dw4="2"
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.
Add an entry in the B digit tree:

mml> numan-add:bdigtree:custgrpid="2222",callside="originating",digitstring="B9",
setname="rset-err"
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.
Add the announcement ID in the TimesTen database announcement table:

mml> numan-add:announcement:annId=33,gwtype="AS5350",locationstring="ann_id_22.au",
playduration=10,repeat=1,interval=20
Step 13
End the provisioning:

mml> prov-cpy

The Cisco PGW 2200 Softswitch supports provisionable QoS over all signaling links as well as
intra-Cisco PGW 2200 Softswitch traffic.
Use the following MML command in an open provisioning session to add QoS:
mml> prov-add:tos:dscp=CS3
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.
OL-1110-23
5-119
Chapter 5
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, page A-1
Processes, page A-98
Properties, page A-99
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.
Network Element Components

All Components have a name parameter, which is the MML name, and a description, which is a text
description. They also must have a parent. If the parent is not specified then it is the root
Cisco PGW 2200 Softswitch NE component. The structure of Network Element components is shown
in Table A-1.
Table A-1
Network Element Component Structure
Parameter MML
Name
Parameter
Description
NAME
Unique ID of this
component and
component name
used in MML
commands
The name can be up to any 20

alphanumeric characters. No special
characters other than - are allowed. The
name should begin with an alphabetic
character.
DESC
Component
description

characters.
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
This component is removed in software Release 9.4(1).

The Adaptor Card component structure is shown in Table A-2.
Table A-2
Adaptor Card Component Structure
Parameter MML
Name
Parameter
Description
NAME
Unique component The name can be up to 20 alphanumeric

name used in MML characters. No special characters other
commands
than - are allowed. The name should
begin with an alphabetic character.
DESC
Component
description
The description can be up to 128

alphanumeric characters. No special
characters other than - are allowed. The
name should begin with an alphabetic
character.
TYPE
Card type
ITK, V35, EN, ATM, or PTI
SLOT
Card Slot
Integer starting at 0. The maximum value

is device dependent (0).
Adjacent Point Code

The adjacent point code (APC) component type represents an SS7 point code assigned to an STP with
which the Cisco PGW 2200 Softswitch NE needs to communicate. Its MML name is as follows:
MML NameAPC
The adjacent point code component structure is shown in Table A-3.

Table A-3
Adjacent Point Code Component Structure
Parameter MML Parameter

Name
Description
NAME
Unique component The name can be up to 20

name used in MML alphanumeric characters. No
commands
special characters other than -
are allowed. The name should
character.
A-2
OL-1110-23
Appendix A

Components
Table A-3
Adjacent Point Code Component Structure (continued)
DESC
Component
description
The description can be up to 128

alphanumeric characters. No
character.
NETADDR
Network address
String in dotted notation, for

example, 1.1.1.
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
The SCTP association component structure is shown in Table A-4.

Table A-4
Association Component Structure
Parameter MML Name
NAME
Unique component
name used in MML
commands
The name can be up to 20 alphanumeric

allowed. The name should begin with an
alphabetic character.
DESC
The description can be up to 128 alphanumeric

TYPE
Signaling Type
The type of protocol to be used. Values: M3UA,

SUA, or IUA.
SGP
MML name of an SGP

(optional)
MML name of a previously configured SGP. Used

for M3UA and SUA interfaces.
IPADDR1
First local address
IPADDR2
Second local address

(optional
IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4, or

N/A; (N/A).
PORT
Local SCTP port

number (optional)
From 1024 through 65535.
PEERADDR1
The highest priority

destination address
IP address.
PEERADDR2
The lowest priority

destination address
(optional)
IP address; (0.0.0.0).
Defaults to 9900 for IUA.

Defaults to 2905 for M3UA.
Defaults to 14001 for SUA.
OL-1110-23
A-3
Appendix A
Components
Table A-4
Association Component Structure (continued)
Parameter MML Name
PEERPORT
Destination SCTP port

number. (optional)

Defaults to 9900 for IUA.
Defaults to 2905 for M3UA.
Defaults to 14001 for SUA.
EXTNODE
MML name of an
MML name of a previously configured external
external node (optional) node. Used in IUA interfaces.
IPROUTE1
MML name of first

IPROUTE (optional)
MML name of a previously configured IPROUTE.
IPROUTE2
MML name of second

IPROUTE (optional)
RCVWIN
Number of bytes to
advertise for the local
receive window
(optional)
From 1500 through 65535; (18000).
MAXINITRETRANS
Maximum number of
times to retransmit
SCTP INIT message
(optional)
0 through 100; (10).
Maximum initial timer

retransmission value
(optional)
0, 300 through 3000; (2000).
MAXINITRTO
0 means use the SCTP internal default.
0 means use the SCTP internal default.
MAXRETRANS
From 1 through 10; (5).

Maximum number of
retransmissions over all
Note
This value must not exceed
destination addresses
MAXRETRANSDEST * the number of
before the association is
destinations.
declared failed
(optional)
CUMSACKTO
Maximum time after a From 100 through 500, in milliseconds; (300).

datagram is received
before a SCPT SACK is
sent (optional)
BUNDLETO
Maximum time SCTP

will wait for other
outgoing datagrams for
bundling (optional)
MINRTO
Minimum value allowed From 300 through 3000, in milliseconds; (300).

for the retransmission
timer (optional)
MAXRTO
Maximum value
allowed for the
retransmission timer
(optional)
From 100 through 600, in milliseconds; (100).
From 1000 through 3000, in milliseconds; (3000).
A-4
OL-1110-23
Appendix A

Components
Table A-4
Association Component Structure (continued)
Parameter MML Name
HBTO
Time between
heartbeats. The
heartbeat is this value
plus the current
retransmission timeout
value (optional)
The value can be 0, or from 300 through 10000, in

milliseconds; (2000).
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
N/A; (N/A)
MAXRETRANSDEST Maximum number of

retransmissions to
either PEERADDR1 or
PEERADDR2 before
call is declared failed
(optional)
0 means disabled.
From 1 through 10; (3).
The following parameters cannot be modified:
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.
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.
The values of IPADDR1 and IPADDR2 must be 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
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.
A-6
OL-1110-23
Appendix A

Components
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
This component is added in software Release 9.6(1).

The AXL server component structure is shown in Table A-5.
Table A-5
AXLSERVR Component Structure
Parameter MML Name Parameter Description
NAME

Unique component
name used in MML
commands for the AXL allowed. The name should begin with a letter.
server
DESC
IPADDR1
First local address
IP_Addr1, IP_Addr2, IP_Addr3, or IP_Addr4
IPADDR2

(optional)

N/A;
(N/A)
PORT
Local CTI port number

(optional)
PEERADDR1

destination address
IP address
PEERADDR2
The lowest priority

destination address
(optional)
PEERPORT
Destination CTI port

number. (optional)
Defaults to 2750.
Defaults to 2750.
CTIPATH
CTI sigpath MML name MML name of a previously configured CTI

sigpath.
IPROUTE1
MML name of first

IPROUTE (optional)
IPROUTE2
MML name of second

IPROUTE (optional)
OL-1110-23
A-7
Appendix A
Components
Table A-5
AXLSERVR Component Structure (continued)
USERNAME
User name for AXL

server authentication
N/A
PASSWORD
Password for AXL

server authentication
N/A
ISDN BRI Signaling Service

The ISDN BRI signaling service component represents a static IP route. Its MML name is as follows:
Note
MML NameBRIPATH

The ISDN BRI signaling service component structure is shown in Table A-6.
Table A-6
BRIPATH Component Structure
Parameter MML
Name
NAME
Unique component
name used in MML
commands

DESC
EXTNODE
MML name of external

node
MML name of a previously provisioned ISDN

BRI voice gateway external node.
MDO
MDO file name
A valid protocol name. You can use the following

files:
ETS_300_102
Q931
ETS_300_172
SIDE

(network).
CUSTGRPID
VNET ID
CRLEN
1 for 1-byte or 2 for 2-byte call reference length;

(0).
Note
If you are using the ETS_300_102 or

Q931 protocol files, this should be set to
1. If you are using the ETS_300_172
protocol file, this should be set to 2.
A-8
OL-1110-23
Appendix A

Components
NAME
EXTNODE
The following rules apply when you are creating or editing ISDN BRI signaling services:
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
The C7 IP link component structure is shown in Table A-7.

Table A-7
C7 IP Link Component Structure
Parameter MML
Name
NAME
Unique component name

used in MML commands

DESC

PRI
Priority
Integer greater than 0; (1)
TIMESLOT
The physical (WAN

Interface Card (WIC) slot
(serial port) information on
the ITP-L.
Valid values are: 0, 1, 2, or 3. Set to 1 when using

the signal processor; otherwise 0; (0)
SLC
Signaling link code
From 0 through 15; (1)
LNKSET
Signaling service this IP

supports
MML name of a previously defined Linkset or

index of the Linkset for SNMP.
SESSIONSET
Session Set MML name.
MML name of a previously configured Session

Set.
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
The Charge component structure is shown in Table A-7.

Table A-8
Charge Component Structure
Parameter MML
Name
NAME


DESC

CHORIG
Charge Origin (optional)
From 0 through 9999; (0)
CHDEST
Charge Destination
From 0 through 9999
DOW
Day of Week (optional)
SUNDAY, MONDAY, TUESDAY, WEDNESDAY,

THURSDAY, FRIDAY, SATURDAY, SUNDAY, or
DEFAULT; (DEFAULT)
TARIFFDESC
Tariff Description
A string of tariff and time changes in the format:

<tariff 1 timeChange 1 - tariff n timeChange n>.
The timeChange value must be divisible by 15
minutes (for example, 0030, 0315, or 2115). The
timeChange value must be 2400 if the last field is
a timeChange value.
Charge Holiday
The Charge Holiday component type is used to provision the Charge Holiday table. Its MML name is as
follows:
MML NameHOLIDAY
The Charge Holiday component structure is shown in Table A-7.
A-10
OL-1110-23
Appendix A

Components
Table A-9
Charge Holiday Component Structure
Parameter MML
Name
NAME


DESC

DATE
Date of the holiday
A valid date in the format YYYYDDMM.
HDAY
The holiday value
HOL1, HOL2, or HOL3.
CTI Manager
The CTI manager component represents the CTI manager. Its MML name is as follows:
Note
MML NameCTIMGR

The CTI manager component structure is shown in Table A-10.
Table A-10
CTIMGR Component Structure
NAME

Unique component
name used in MML
commands for the AXL allowed. The name should begin with a letter.
server
DESC
IPADDR1
First local address
IP_Addr1, IP_Addr2, IP_Addr3, or IP_Addr4
IPADDR2

(optional)

N/A;
(N/A)
Local CTI port number

(optional)
PEERADDR1

destination address
IP address
PEERADDR2
The lowest priority

destination address
(optional)
PORT
Defaults to 2750.
OL-1110-23
A-11
Appendix A
Components
Table A-10
CTIMGR Component Structure (continued)
PEERPORT
Destination CTI port

number. (optional)
Defaults to 2750.
CTIPATH
CTI sigpath MML name MML name of a previously configured CTI

sigpath.
IPROUTE1
MML name of first

IPROUTE (optional)
IPROUTE2
MML name of second

IPROUTE (optional)
USERNAME
User name for CTI

manger authentication
N/A
PASSWORD
Password for CTI

manger authentication
N/A
CTIVERSION
The Cisco CallManager The name can be as many as 20 alphanumeric

CTI protocol version
The following rules apply when creating or editing CTI Manager:
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 is specified, the IPADDR must match the IPADDR1.
When IPROUTE2 is specified, the IPADDR must match the IPADDR2.
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.
PEERADDR1 cannot be 0.0.0.0 or 255.255.255.255.
PEERADDR2 cannot be 255.255.255.255.
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
A-12
OL-1110-23
Appendix A

Components
Note

The CTI path component structure is shown in Table A-11.
Table A-11
CTIPATH Component Structure
Parameter MML
Name
NAME


DESC

EXTNODE
External node MML name
MML name of a previously defined external node

or index of the external node for SNMP
MDO
MDO file name
Valid protocol name from variants.dat.
Destination Point Code

The destination point code (DPC) component type represents an SS7destination point code with which
the Cisco PGW 2200 Softswitch NE communicates. Its MML name is as follows:
MML NameDPC
The destination point code component structure is shown in Table A-12.

Table A-12
Destination Point Code Component Structure
Parameter MML Parameter

Name
Description
NAME
Unique ID of this
component and
component name
used in MML
commands
The name can be as many as 20

alphanumeric characters. No
begin with a letter.
DESC
Component
description
The description can be up to any

128 characters.
NETADDR
Network address
String in dotted notation, for

example, 1.1.1.
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:
OL-1110-23
A-13
Appendix A
Components
MML NameDCHAN
The D-channel component structure is shown in Table A-13.

Table A-13
D-Channel Component Structure
Parameter MML
Name
NAME
Unique ID of this
component and component
name used in MML
commands

DESC
The description can be up to any 128 characters.
PRI
Priority
SVC

supports
MML name of a previously defined IPFAS service
SESSIONSET
MML Name of a previously configured Session

Set.
TCPLINK
MML name of TCP link

(restricted)
MML name of a previously provisioned TCP link.

This parameter is used only for D-channels
associated with ISDN BRI signaling services. This
SIGSLOT
Physical slot on the gateway Integer 0 through 63; (0)

where the T1/E1 is plugged
Note
Set this parameter to 0 for ISDN BRI
into
D-channels when the associated external
node is a C17xx.
SIGPORT
Physical port on the gateway Integer 0 through 167; (0)

on the slot
SUBUNIT
Required for ISDN BRI

D-channels
Integer 0 or 1; (0). This parameter is added in

software Release 9.5(2).
The following rules apply when you are creating or editing D-channels:
Backup D-channels for ISDN BRI signaling services are not supported.
The priority for ISDN BRI D-channels should be set to 1.
Session sets are used only in support of IPFAS D-channels.
TCP links are used only in support of ISDN BRI 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 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:
A-14
OL-1110-23
Appendix A

Components
MML NameDNSPARAM
The DNS component structure is shown in Table A-14.

Table A-14
DNS Component Structure
Parameter MML
Name
NAME


DESC

DNSSERVER1
IP address of primary DNS

server
This is mandatory and has no default value.
DNSSERVER2
IP address of secondary
DNS server
This is optional.
CACHESIZE
Maximum cache entries

used to hold DNS entries
TTL
The time-to-live interval for Integer greater than 0; (3600)

DNS entries (in seconds)
POLICY
Policy for selection of DNS Hierarchy or round-robin; (hierarchy)

entries
QUERYTIMEOUT The timeout interval for

DNS queries (in
milliseconds)
The time interval in seconds Integer greater than 0; (30)

to check if DNS server is
responding
KEEPALIVE
DPNSS Signaling Service

The DPNSS signaling service component type represents a DPNSS signaling path that is backhauled
over IP to/from a Network Access Server (destination). Its MML name is as follows:
MML NameDPNSSPATH
The DPNSS signaling service component structure is shown in Table A-15.

Table A-15
DPNSS Signaling Service Component Structure
Parameter MML
Name
NAME
IP route name

DESC
OL-1110-23
A-15
Appendix A
Components
Table A-15
DPNSS Signaling Service Component Structure (continued)
MDO
MDO file name

Note
DPNSS_BTNR188 is the only valid MDO

protocol variant for this signaling service.
EXTNODE
MML name of a previously defined external node.
CUSTGRPID
Customer group ID
ABFLAG
DPNSS side
a or b side, n for not applicable; (n)
SIGSLOT
Physical slot on the NAS

defining the NFAS Group
(optional)
An integer, 0 through 63; (0).
SIGPORT
Physical port on the slot of An integer, 0 through 167.

NAS defining the NFAS
Groupl. (optional)
ORIG LABEL
Originating call control

(OCC) side location label.
Used for Call Limiting
feature.
As many as 20-character alphanumeric string.

This parameter is added in software Release
9.6(1).
TERM LABEL
Terminating call control

(TCC) side location label.
feature.

9.6(1).
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
EISUP Signaling Service (sigpath)

The EISUP Signaling Service (sigpath) component is a network element that represents an EISUP
signaling service or signaling path to another NE (destination). Its MML name is as follows:
MML NameEISUPPATH
The signaling service path component structure is shown in Table A-16.
A-16
OL-1110-23
Appendix A

Components
Table A-16
Signaling Service Path Component Structure
Parameter MML
Name
NAME


DESC

EXTNODE

CUSTGRPID
Customer group ID
Four digit ID; (0000)
CUSTGRPTBL
Customer group table index Four digit index; (0101)
ORIG LABEL

feature.

9.6(1).
TERM LABEL

feature.

9.6(1).
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

The Ethernet interface component structure is shown in Table A-17.
Table A-17
Ethernet Interface Component Structure
Parameter MML
Name
NAME


OL-1110-23
A-17
Appendix A
Components
Table A-17
Ethernet Interface Component Structure (continued)
DESC

CARD
Card which supports this

Ethernet interface
MML name of a previously defined card or index

of the card for SNMP
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
External Node Component Structure
Parameter MML
Name
NAME


DESC

TYPE
The type of the External

Node
Valid values are from extNodeTypes.dat. Refer to

section on page 2-34 for a list of node types.
ISDNSIGTYPE
ISDN signaling type
Valid values are IUA or N/A (default is N/A). This

GROUP
M3UA or SUA group

number
Value is 1100 for M3UA or SUA nodes. Value is

0 for nodes that do not support M3UA or SUA.
9.4(1).
The following rules apply when creating or editing external nodes:
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:
TYPE must be one of the valid external node types.
The maximum number of external nodes with an ISDNSIGTYPE of IUA is 256.
A-18
OL-1110-23
Appendix A

Components
FAS Signaling Service (sigpath)

The FAS signaling service (sigpath) component type represents a FAS signaling service or signaling path
to a particular destination using either ISDN-PRI or DPNSS. The MML name is as follows:
Note
MML NameFASPATH

The FAS Signaling Service component structure is shown in Table A-19.
Table A-19
FAS Signaling Service Component Structure
Parameter MML
Name
NAME


DESC

SIDE

(network)
MDO
MDO file name

Note
Limited to any MDO variant from either

the ISDNPRI or DPNSS protocol families.
CUSTGRPID
Customer ID
CUSTGRPTBL
Customer Table index
Four digit index; (0101)
ABFLAG
DPNSS side
CRLEN
1 for 1 byte or 2 for 2 byte call reference length; (2

for ISDNPRI and 0 for DPNSS)
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
The Files component structure is shown in Table A-20.
OL-1110-23
A-19
Appendix A
Components
Table A-20
Files Component Structure
Parameter MML
Name
NAME
File type
TKGFile for trunk group file, BCFile for bearer

channel file, AWhiteFile for A number white list
files, ABlackFile for B number black list files,
BWhiteFile for B number white list files and
BBlackFile for B number black list files
FILE
File name
File name. File should be present in the

etc/cust_specific directory.
ACTION
Action to be performed on
the files.
Import for converting customer files into.dat files.

Export for converting .dat files into customer files.
Export is not currently supported for the screening
files.
Intelligent Network Service (INSERVICE) Table

The intelligent network service component allows MML commands to be used to provision some
elements, which are in the INSERVICE table, in the Trigger table. Its MML name is as follows:
MML Name INSERVICE
The intelligent network service table component structure is shown in Table A-21.
Table A-21
INSERVICE Table Component Structure
Parameter MML
Name
Parameter Values (default)
NAME


DESC

SKORTCV
Service key
Integer. 0 through 65535 (0). Service key value

that specifies the feature that caused the trigger to
be hit (ITU / ETSI INAP only). Otherwise it is the
trigger criteria value.
GTORSSN
Global title or Sub-System

Number.
Text string. Route by global title (ROUTEBYGT)

or route by subsystem number (ROUTEBYSSN).
0 = ROUTEBYGT (Route by global title)
1 = ROUTEBYSSN (Sub-System Number)
A-20
OL-1110-23
Appendix A

Components
Table A-21
INSERVICE Table Component Structure (continued)
Parameter MML
Name
Parameter Values (default)
GTFORMAT
Global title format
Text string. How to use Global Title; SCCP Called

Party Address, Address indicator field. User
provisions the string value. For example, NOGT.
0 = NOGT (No global title. Use this when routing
by SSN)
1 = GTTTNBRENC (Use global title translation
type numbering scheme encoding scheme)
2 = GTTT (Use global title translation type)
3 = GTONLY (Use global title only)
4 = UNKNOWN (Unknown)
MSNAME
Message Sending Name
As many as 20 alphanumeric characters.
The following rules are used to support INSERVICE table provisioning.
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.
The MSNAME must exist in the MessageSendingName table in trigger.dat.
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.
IPFAS Transport Service (previously PRI Signaling Backhaul)

The IPFAS transport service component type represents the FAS over IP transport service or signaling
path from a media gateway to a Cisco PGW 2200 Softswitch. Its MML name is as follows:
MML NameIPFASPath
The IPFAS transport service component structure is shown in Table A-22.

Table A-22
IPFAS Transport Service Component Structure
Parameter MML
Name
NAME


DESC

EXTNODE

or index of the external node for SNMP.
OL-1110-23
A-21
Appendix A
Components
Table A-22
IPFAS Transport Service Component Structure (continued)
SIDE

(network).
MDO
MDO file name
CUSTGRPID
VNET ID
CUSTGRPTBL
VNET Table index
Four digit index; (0101).
ABFLAG
DPNSS side
a or b side, n for not applicable; (n).
CRLEN
1 for 1 byte or 2 for 2 byte call reference length;

(0).
ORIG LABEL

feature.

9.6(1).
TERM LABEL

feature.

9.6(1).
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
The IP link service component structure is shown in Table A-24.

Table A-23
Ipinmapping Component Structure
Parameter MML
Name
Name
The primary key to identify

an ipinmapping entry
A unique name used to describe the ipinmapping

rule entry. This field must have a unique value.
Desc
Description
A description of the trunk group.
Sigsvc
SIP sigpath or EISUP

sigpath
The signal path to which the ipinmapping rule

applies.
AllowedIP
Allowed IP Address
The incoming SIP IP address allowed on the trunk.

This parameter is optional.
AllowedIPNet
Mask
Allowed Net Mask
The subnet mask allowed on the trunk. This

parameter is optional.
Note
If this parameter is blank, the PGW uses

the default subnet mask value of
255.255.255.255.
A-22
OL-1110-23
Appendix A

Components
Table A-23
Ipinmapping Component Structure (continued)
Parameter MML
Name
Sipport
Allowed SIP Port
The SIP TCP or UDP port number allowed on the

trunk. This parameter is for SIP sigpaths only. The
sipport parameter is optional.
Trnkgrpnum
Trunk group number
The number used to identify the trunk group.
Parameter Analysis
The PGW compares incoming traffic against ipinmapping entries in the following order:
SIP
1.
IP address and port number
2.
IP address only
3.
Port number only
EISUP
1.
IP address only
Analysis Criteria
For incoming IP traffic to match an ipinmapping entry, the following criteria must be true:
IP address and port number:

The incoming IP address falls within the address range defined by the AllowedIP and
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
the address range defined by the AllowedIP and AllowedIPNetMask values.
Port number only:

The destination port of the incoming SIP message matches the sipport defined in the
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
The IP link service component structure is shown in Table A-24.
OL-1110-23
A-23
Appendix A
Components
Table A-24
IP Link Component Structure
Parameter MML
Name
NAME
Unique ID of this
name used in MML
commands

DESC
IF
Ethernet interface MML

name
MML name of a previously defined ENETIF or

index of the ENETIF for SNMP.
PORT
Local port number
Any valid IP port number greater than 1024

(Recommended setting of 2427 for MGCP and
SGCP).
PRI
Priority
Integer greater than 0; (1).
PEERADDR
Remote IP address
IP address; (0.0.0.0). This may also be specified as

a hostname or a DNS name.
PEERPORT
Remote port

(Recommended setting of 2427 for MGCP and
SGCP)
IPADDR
IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4.
SVC

supports
MML name of a previously defined signal service

or index of the signal service for SNMP.
NEXTHOP
Next hop address
IP address or hostname of the next hop; (0.0.0.0).

This parameter is removed in software Release
9.4(1).
NETMASK
Subnet mask address
Subnet mask address; (255.255.255.255).

9.4(1).
IPROUTE
IP route MML name
MML name of a previously defined IPROUTE.

9.4(1)T.
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.
Each peer address is unique per external node.
A-24
OL-1110-23
Appendix A

Components
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.
For IP links under an MGCP service, the PRI value must be 1 or 2.
IP Route
The IP route represents a static IP route. Its MML name is as follows:
MML NameIPROUTE
The IP route component structure is shown in Table A-25.

Table A-25
IPROUTE Component Structure
Parameter MML
Name
NAME
Unique component
name used in MML
commands

DESC

DEST
Destination hostname or IP Address in decimal dot notation or hostname

IP address
that is less than or equal to 32 characters.
NETMASK
Subnet mask of
Destination (optional)
IP Address in decimal dot notation.

(255.255.255.255)
NEXTHOP
Next hop router IP

address
IP Address or hostname that is less than or equal

to 32 characters, or one of the following property
names defined in XECfgParm.dat:
IP_NextHop1, IP_NextHop2, IP_NextHop8,
IP_Addr1, IP_Addr2, or IP_Addr4.
IPADDR
Local IP address
PRI
Priority
1 through 65535; (1).
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.
Ensure the destination resolves to a non-zero address.
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 IP Route is specified in a link object (for example, IPLNK, SESSIONSET, or

ASSOCIATION), the IP address resolved from the PEERADDR attribute must be checked against
the DESTINATION and NETMASK attributes to verify the IPROUTE is valid.
When an IP Route is specified in a link object (for example, IPLNK, SESSIONSET, or

ASSOCIATION), the IPADDR must match the IPADDR of the link.
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
The LABEL component structure is shown in Table A-26.

Table A-26
LABEL Component Structure
Parameter MML
Name
NAME
Unique component
name used in MML
commands

A-26
OL-1110-23
Appendix A

Components
Table A-26
Note
LABEL Component Structure (continued)
DESC
CALL LIMIT
Maximum number of
calls allowed on one
location label
0 through 6000, integer value

0 (default)
LineXlate
The linexlate component type represents a line e number and internal number translation. Its MML name
is as follows:
MML NameLINEXLATE
The linexlate component structure is shown in Table A-27.

Table A-27
NOA Provisioning Parameters
Parameter MML
Name
NAME

commands
- are allowed. Names should begin with an
DESC

characters.
SVC

service.
PARAMETER
This indicates the parameter or

field in the protocol message to
which this entry refers.
Currently NOA is the only parameter

supported.
DIRECTION
1 = NOA
Direction in which the message 0 = in

is going, either into or out of the 1 = out
This is not ingress or egress.
NUMBER
A number representing a specific 0 = called

number type in the protocol
1 = calling
message.
2 = original called
3 = redirecting
4 = redirection
5 = generic
OL-1110-23
A-27
Appendix A
Components
Table A-27
NOA Provisioning Parameters (continued)
Parameter MML
Name
INTNOA
Internal NOA value.
Any 7-bit value, 0 through 127, no

restrictions.
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
The linkset component structure is shown in Table A-28.

Table A-28
Link Set Component Structure
Parameter MML
Name
NAME

The name can be up to 20 alphanumeric characters.

No special characters other than - are allowed.
The name should begin with an alphabetic
character.
DESC

allowed. The name should begin with an alphabetic
character.
APC
Adjacent point code
MML name of a previously defined adjacent point

code or index of the adjacent point code for SNMP.
PROTO
Protocol family
SS7-ANSI, SS7-ITU, SS7-China, SS7-Japan, or

SS7-UK.
TYPE
Transport type
TDM for TDM linksets or IP for IP linksets;

(TDM).
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
A-28
OL-1110-23
Appendix A

Components
Table A-29
Linkset Property Component Structure
Parameter MML Name
Default Value
Units
mtp2AermEmgThr
Alignment error rate monitor threshold duration for

emergency operation. Value: One message. This property is
Messages
mtp2AermNrmThr
Alignment error rate monitor threshold duration for normal

operation. Value range: 1 through 4 messages. This property
is removed in software Revision 9.3(1) and later.
Messages
mtp2CongDiscard
Discard frames upon entering congestion at MTP2. Set to true False

or false. This property is removed in software Revision 9.3(1)
and later.
mtp2LssuLen
Link status signal unit, status field length. Specify one or two. SS7-ANSI = 1
SS7-UK = 1
later.
SS7-CHINA = 1
SS7-ITU = 1
SS7-Japan = 2
Octets
mtp2MaxAlignRetries
Maximum number of attempts to align link before declaring

it out-of-service (OOS). Value range: 1 through 10 attempts.
Attempts
Note
The Cisco PGW 2200 Softswitch also reattempts link

alignment every 5 seconds.

later.
mtp2MaxMsuFrmLen
Maximum frame length of a C7 message signal unit. Specify 272

62 or 272. This property is removed in software Revision
9.3(1) and later.
Octets
mtp2MaxOutsFrames
The maximum number of outstanding frames that can be sent 127

without receiving acknowledgment. Value range: 1 through
127. This property is removed in software Revision 9.3(1) and
later.
Frames
mtp2ProvingEmgT4
Emergency proving period. Value range: 5 through 7 tenths of SS7-ANSI = 6

a second. This property is removed in software Revision
SS7-UK = 6
9.3(1) and later.
SS7-CHINA = 6
SS7-ITU = 6
SS7-Japan = 30
Tenths of a
second
mtp2ProvingNormalT4
Normal proving period. Value range: 1 through 3 seconds.

later.
SS7-ANSI = 23
SS7-UK = 23
SS7-CHINA = 23
SS7-ITU = 23
SS7-Japan = 30
Tenths of a
second
mtp2SuermThr
Signal unit error rate monitor threshold for emergency

operation. Value range: 1 through 127. This property is
64
Frames
OL-1110-23
A-29
Appendix A
Components
Table A-29
Linkset Property Component Structure (continued)
Parameter MML Name
Note
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
Maximum period in aligned/ready state before return to

out-of-service state. Value range: 12 through 16 seconds (for
ANSI) or 40 through 50 seconds (for BT, CHINA, and ITU).
later.
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
SS7-CHINA = 250
SS7-ITU = 250
SS7-Japan = 50
mtp2T3
Maximum period in aligned state before return to

out-of-service state. Value range: 5 through 14 seconds (for
ANSI) or 1 through 2 seconds (for BT, CHINA, and ITU).
later.
SS7-ANSI = 115
SS7-UK = 20
SS7-CHINA = 20
SS7-ITU = 20
SS7-Japan = 30
Tenths of a
second
mtp2T5
Period for sending a SIB1 message to far-end.

Value range: 80 through 120 seconds. This property is
Thousandths
of a second
mtp2T6
Remote congestion timer. If congestion is not cleared before

expiration of this timer, the link fails. Value range: 1 through
6 seconds (for ANSI) or 3 through 6 seconds (for BT, CHINA,
and ITU). This property is removed in software Revision
9.3(1) and later.
SS7-ANSI = 30
SS7-UK = 60
SS7-CHINA = 60
SS7-ITU = 60
SS7-Japan = 30
Tenths of a
second
mtp2T7
MTP2 acknowledgment timer. On expiration, the link fails

and an excessive delay of acknowledgment management
message is generated. Value range: 0.5 through 2 seconds (for
BT, CHINA, and ITU). This property is removed in software
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
Waiting for signaling data link connection acknowledgment. SS7-ANSI = 10

Value range: 1 through 2 seconds, or through 5 seconds when SS7-UK = 10
connecting over a Cisco ITP-L.
SS7-CHINA = 10
SS7-ITU = 10
SS7-Japan = 20
Tenths of a
second
A-30
OL-1110-23
Appendix A

Components
Table A-29
Parameter MML Name
Default Value
Units
mtp3FrcUnhT13
Waiting for force uninhibited. Value range: 0.8 through

1.5 seconds.
SS7-ANSI = 10
SS7-UK = 10
SS7-CHINA = 10
SS7-ITU = 10
SS7-Japan = 0
Tenths of a
second
mtp3InhAckT14
Waiting for inhibit acknowledgment. Value range: 2 through

3 seconds.
SS7-ANSI = 20
SS7-UK = 20
SS7-CHINA = 20
SS7-ITU = 20
SS7-Japan = 0
Tenths of a
second
mtp3LocInhTstT20

Value range: 90 through 120 seconds (for ANSI only).
SS7-ANSI = 900
Tenths of a
second
mtp3MaxSltTries
Maximum number of retries of signaling link test message. If SS7-ANSI = 2

MTP3 does not receive a response after two signaling link test SS7-UK = 2
messages, the system fails the link. Value range: 1 through 5. SS7-CHINA = 2
SS7-ITU = 2
SS7-Japan = 0
mtp3MsgPriority
Message priority of management messages for congestion

periods.
Priority 1 (default) indicates without congestion priorities.
Priorities greater than 1 indicate multiple congestion
priorities. Priority 3 is the highest priority.
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
Overall MTP restart timer at an SP adjacent to an SP whose

MTP restarts. Value range: 0 to disable, or 63 through 65
seconds.
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
This parameter is for BT, CHINA, and ITU.
mtp3LocInhTstT22

Value range: 3 through 6 minutes.
mtp3MtpRstrtT24
Overall MTP restart timer for local MTP restart. Value range SS7-ANSI = 60
is network-dependent.
Tenths of a
second
mtp3RepeatRstrtT26
Traffic restart waiting message at local MTP restart.

Tenths of a
second
SS7-ANSI = 150
OL-1110-23
A-31
Appendix A
Components
Table A-29
Parameter MML Name
Default Value
Units
mtp3TfrUsed
Transfer restricted procedure is enabled (true) or disabled

(false). Set to true or false.
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.
Tenths of a
second
mtp3tstSltmT1
Waiting for signaling link test acknowledgment message.

SS7-ANSI = 60
This must be greater than the value in mtp2T6. Value range: 4 SS7-UK = 50
through 12 seconds.
SS7-CHINA = 50
SS7-ITU = 50
SS7-Japan = 50
Tenths of a
second
mtp3tstSltmT2
Interval for sending signaling link test message.

Tenths of a
SS7-ANSI = 600
second
SS7-UK = 300
SS7-CHINA = 300
SS7-ITU = 300
SS7-Japan = 300
mtp3UnhAckTl2
Waiting for uninhibited acknowledgment.

Value range: 0.8 through 1.5 seconds.
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
Waiting for signaling data link connection acknowledgement. SS7-Japan = 20

Tenths of a
second
mtp3T12
Waiting for signaling data link connection acknowledgement. SS7-Japan = 0

Value range: 500 through 1500 milliseconds.
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
A-32
OL-1110-23
Appendix A

Components
Table A-29
Parameter MML Name
Default Value
reference
Denotes versions for protocol standards supported for MTP.

For SS7-ANSI: options ANSI92, ANSI96.
For SS7-UK, SS7-CHINA, SS7-ITU: options ITU88 and
ITU92
For SS7-JAPAN: options NTT, TTC.
SS7-ANSI =
ANSI96
SS7-UK = ITU92
SS7-CHINA =
ITU92
SS7-ITU = ITU92
SS7-Japan = NTT
rudpAck
Not used.
Enable
rudpKeepAlives
Not used.
Enable
rudpNumRetx
The maximum number for retransmission count.

rudpWindowSz
The maximum number for unacknowledged Segments in the

RUDP window.
32
rudpRetxTimer
The retransmission timeout. Value range: 2 through 100.
rudpSdm
Not used.
Enable
Units
Tenths of a
second
1. SIB = Status indication busy
M3UA Key
This component represents an M3UA routing key. The parent component of the M3UAKEY is the OPC.
MML NameM3UAKEY
The M3UA key component structure is shown in Table A-30.

Table A-30
M3UAKEY Component Structure
Parameter MML Name
NAME
M3UA key name

DESC
OPC
Associated OPC
DPC
Associated DPC
(optional)
ROUTING CONTEXT

context). Each M3UA key must have a unique
routing context.
SI
Service indicator
Service type, values are ISUP, TUP, and N/A

(N/A).
NETWORK
APPEARNCE
Network appearance
(optional)

indicates an invalid network appearance.)
OL-1110-23
A-33
Appendix A
Components
Note
None of the parameters for this command can be modified.

The following rules apply when creating M3UA keys:
You can provision a maximum of 1536 M3UA keys
Up to 64 OPCs can use M3UA signaling services.
Parent OPC must be a true OPC
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
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
The M3UA route component structure is shown in Table A-31.

Table A-31
Note
M3UAROUTE Component Structure
Parameter MML Name
NAME
M3UA route name

DESC
DPC
Associated DPC
EXTNODE
Associated external
node

node.
OPC
Associated OPC
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
Multiple DPCs with the same NETADDR cannot be routed to the same OPC
The associated OPC must be a true OPC
For a given OPC/DPC only one route can be defined through a given external node.
Up to two M3UA routes can be defined per OPC-DPC pair
The associated external node must support M3UA signaling
M3UA routes for the same OPC-DPC pair must have external nodes in the same group
A-34
OL-1110-23
Appendix A

Components
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.
MGCP Signaling Service

The MGCP Signaling Service component type represents the MGCP signaling service or signaling path
to a trunking gateway. Its MML name is as follows:
MML NameMGCPPATH
The MGCP signaling service structure is shown in Table A-32.

Table A-32
MGCP Signaling Service Component Structure
Parameter MML
Name
NAME


DESC

EXTNODE

Multiple IPFAS Services (sigpath)

The multiple IPFAS signaling service component type is used to create multiple IPFAS or IPNFAS
signaling paths and D-channels to a particular destination using either ISDN-PRI or DPNSS. Its MML
name is as follows:
MML NameMLTIPFAS
The multiple IPFAS Signaling Service component structure is shown in Table A-33.
Table A-33
MLTIPFAS Signaling Service Component Structure
Parameter MML
Name
NAME
Name used to derive IPFAS

or IPNFAS and D-channel
MML names

DESC
CUSTGRPID
Customer ID
MDO
MDO file name

Note
Limited to any MDO variant from either

the ISDNPRI or DPNSS protocol families.
OL-1110-23
A-35
Appendix A
Components
Table A-33
MLTIPFAS Signaling Service Component Structure (continued)
Parameter MML
Name
SIDE

(network)
EXTNODE

node.
PATHSIZE
SESSIONSET
MML Name of a previously configured Session

Set.
SIGSLOT
Physical slot on the gateway Integer 0 through 63; (0)

where the T1/E1 is plugged
into
SIGPORT
Physical port on the gateway Integer 0 through 167; (0)

on the slot
SIGPORTSKIP
Number of SIGPORT values Integer 0 through 167; (0)

to be skipped. (Only
required for IPNFAS.)
BACKUP
Indicates if a backup
YES or NO; (NO)
D-channel is to be created.
(Only required for IPNFAS.)
ABFLAG
DPNSS side
CRLEN
1 for 1 byte or 2 for 2 byte call reference length;

(0)
ORIG LABEL

feature.

9.6(1).
TERM LABEL

feature.

9.6(1).
Multiple Trunk Groups and Trunks

The multiple trunk groups and trunks component types represent PRI trunk groups and trunks. Its MML
name is as follows:
MML NameMLTTRNK
The multiple trunk group and trunk component structure is shown in Table A-34.
A-36
OL-1110-23
Appendix A

Components
Table A-34
MLTTRNK Component Structure
Parameter MML
Name
NAME
Starting trunk group number Any valid trunk group number.
SVC
Starting value of the

signaling service MML
name
This is the NAME parameter used in the

MLTIPFAS command.
CLLI
Common Language
Location Identification
Any alphanumeric value that is less than or equal to

11 characters.
TYPE
Trunk group type
Valid trunk group types are: TDM_GEN,

TDM_ISUP, TDM_CAS, TDM_TUP,
TDM_DPNSS, TDM_PRI, TDM_BTNUP, IP,
ATM, IP_SIP, SIP_IN, and CTI.
Trunk group type IP is used with EISUP signaling

service. TDM_PRI is used with IPFAS or FAS
signaling services with protocol family of
ISDNPRI. TDM_DPNSS is used with signaling
services with protocol family of DPNSS.
TDM_ISUP is used with SS7 signaling services
with switch types of 0, 5, 20, 23, or 40. TDM_TUP
is used with SS7 signaling services with switch
type of 5. TDM_BTNUP is used with SS7 signaling
services with SS7-UK variants with switch type of
5. TDM_GEN is used with SS7 signaling services
with switch types not equal to 0, 5, 20, 23, or 40.
TDM_CAS is currently not supported. IP_SIP is
used for SIP signaling services at the terminating
side. SIP_IN is used for SIP signaling services at
the originating side and only one such trunk group
can be configured on each
Cisco PGW 2200 Softswitch node. CTI is used for
CTI signaling.
0 = No switch-specific 23 = SS7 ANSI
logic for the signaling path.26 = DPNSS
5 = BTNUP27 = NET5
22 = NI2
SELSEQ
Select sequence
Valid select sequence values are: LIDL, MIDL,

ASC, DESC, RDM, EDESC, ODESC, EASC,
OASC, CASC, CDESC.
QABLE
Queueable
Y or N; (N).
OL-1110-23
A-37
Appendix A
Components
Table A-34
MLTTRNK Component Structure (continued)
Parameter MML
Name
VSF
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.
NUMTRNKGRP
Number of trunk groups
Integer greater than 0.
SPANSIZE
Number of trunks per span
Integer greater than 0 and less than 31; (1).
NUMSPAN
Number of spans per trunk

group
DCHAN
Reserved time slot for

D-channel in spans
DCHANSPAN
List of spans where a

D-channel is to be reserved
The format is span1, span2, , spanN or ALL;

(ALL).
TRNKMEMNUM
Starting trunk group

member number for each
trunk group
SPAN
Span
Integer from 0 through 65535 or ffff.
CIC
Circuit Identifier Code
Integer from 0 through 65535.
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
Coding Units MML name
MML name of previously defined CU.
COTPERCENTA
GE
Determines the percentage

of calls on the trunk upon
which a continuity test
(COT) is performed.
0 through 100; (0).
RINGNOANSWE
R
Ring no answer. Indicates

0 through 600 seconds; (255).
the time, in seconds, ringing
is allowed to occur.
GLARE
Glare control. Glare is a

collision that occurs when
two network nodes
simultaneously attempt to
reserve the same channel.
SATELLITEIND
Satellite indicator. Indicates Values are: 0 (no) (default) or 1 (yes).

if the trunk is going over a
satellite.
Values are: 0 (no handling) (default), 1 (always), 2

(even/odd), or 3 (no control).
A-38
OL-1110-23
Appendix A

Components
Table A-34
MLTTRNK Component Structure (continued)
Parameter MML
Name
NPA
Numbering plan area.

Indicates the NPA code
associated with the
incoming trunk group.
Value range: 0 (none) (default), or 200 through 999.
CARRIERIDENTI Trunk group property carrier Any integer of 4 digits greater than 0; (0).
TY
identity
SCREENFAILAC
TION
Trunk group property screen 1 (yes) or 0 (no); (0).

fail action
CUSTGRPID
Trunk group property

customer group ID
Any 4 alphanumeric characters; (0000).
COMPRESSIONT Compression type. Indicates Values are: 0 (none), 1 (mu-law) (default), or 2

YPE
the G.711 compression type (A-law).
used on the trunk.
ECHOCANREQU Echo cancellation. Indicates Echo Canceller Required. Specifies whether to
send a modify-connection message (MDCX) for
IRED
if echo cancellation is
required.
echo control. Enter a value of 0 or 1 for
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 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
Nailed Trunk (Bearer Channel)

The Nailed Trunk component facilitates the provisioning of the individual nailed bearer channels used
in a Cisco SS7 Interconnect for Access Servers Solution or Classic Cisco PGW 2200 Softswitch
configuration. Its MML name is as follows:
MML NameNAILEDTRNK
OL-1110-23
A-39
Appendix A
Components
Table A-35
Nailed Trunk (Bearer Channel) Component Structure
Parameter MML
Name
NAME
Trunk identifier
SRCSVC
MML name of the source

service
MML name of a previously defined signaling

service. Valid signaling services are: ISDNPRI,
DPNSS, or any SS7 signaling service.
DSTSVC
MML name of destination

service
MML name of a previously defined signaling

service. Valid signaling services are: ISDNPRI,
DPNSS, or any SS7 signaling service.
SRCSPAN
Source span
Integer from 0 through 65535 or ffff; (ffff)
DSTSPAN
Destination span
Integer from 0 through 65535 or ffff; (ffff)
SRCTIMESLOT
Source timeslot
DSTTIMESLOT
Destination timeslot
SPANSIZE
Number of trunks per span
Integer from 1 through 31; (1)
NAS Signaling Service (sigpath)

The NAS signaling service component type represents an ISDN signaling service or signaling path that
is backhauled over IP to and from a NAS (destination). Its MML name is as follows:
MML NameNASPATH
The NAS signaling service component structure is shown in Table A-36.

Table A-36
NAS Signaling Service (sigpath) Component Structure
Parameter MML
Name
NAME
NAS signaling service name The name can be as many as 20 alphanumeric

DESC
MDO
MDO file name

(BELL_1268_C3 [for software Release 9.3(1) and
earlier or BELL_1268_C2 for software Release
9.3(2) and later] is the only valid MDO variant for
this signaling service).
EXTNODE

or index of the external node for SNMP.
CUSTGRPID
Customer group ID
A-40
OL-1110-23
Appendix A

Components
Table A-36
NAS Signaling Service (sigpath) Component Structure (continued)
SIGSLOT
Physical slot on the NAS

defining the NFAS Group
(optional)
An integer, 0 through 63; (0). This parameter is

added in software Release 9.4(1).
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 maximum number of DPNSSPATHs and IUA NASPATHs is 1500.
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.
Originating Point Code

The Originating Point Code component type represents an SS7 point code used by the
Cisco PGW 2200 Softswitch NE. Its MML name is as follows:
MML NameOPC
The Originating Point Code component structure is shown in Table A-37.

Table A-37
Point Code Component Structure
Parameter MML
Name
NAME


DESC

NETADDR
Network address
String in doted notation, for example, 1.1.1.
OL-1110-23
A-41
Appendix A
Components
Table A-37
Point Code Component Structure (continued)
Parameter MML
Name
NETIND
Network indicator
; (0)
TYPE
Type of the OPC
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
The Profile component structure is shown in Table A-38.

Table A-38
Profile Component Structure
Parameter MML
Name
NAME
Profile name
The name can be as many as twenty alphanumeric

TYPE
Profile type name (as

defined in properties.dat)

characters.
PROPERTYNA Profile name (as defined in

ME
properties.dat)

characters.
The following list identifies the ISUP timers that can be provisioned for signaling service. Information
for each timer consists of:
DefaultIndicates if it is assigned to a profile. Set to 0 for no profile.
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
A-42
OL-1110-23
Appendix A

Components
Q761_BASE Default: 15000 Range=15000-60000

Q761_SINGAPORE Default: 15000 Range=15000-60000
Q761_ARGENTINA Default: 10000 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=10000-60000
*.T12
Desc:
T12
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
ISUPV2_SPANISH Default: 30000 Range=10000-60000
SS7-Japan
*.T13
Desc:
T13
Default:
Type:
OL-1110-23
A-43
Appendix A
Components
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
SS7-Japan
*.T14
Desc:
T14
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
SS7-Japan
A-44
OL-1110-23
Appendix A

Components
*.T15
Desc:
T15
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
SS7-Japan
*.T16
Desc:
T16
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
OL-1110-23
A-45
Appendix A
Components

SS7-Japan
*.T17
Desc:
T17
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
SS7-Japan
*.T18
Desc:
T18
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
A-46
OL-1110-23
Appendix A

Components
SS7-ITU
SS7-Japan
*.T19
Desc:
T19
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
SS7-Japan
*.T2
Desc:
T2
OL-1110-23
A-47
Appendix A
Components
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
SS7-Japan
*.T20
Desc:
T20
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
A-48
OL-1110-23
Appendix A

Components

SS7-Japan
*.T21
Desc:
T21
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
SS7-Japan
*.T22
Desc:
T22
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
OL-1110-23
A-49
Appendix A
Components

SS7-Japan
*.T23
Desc:
T23
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
SS7-Japan
*.T24
Desc:
T24
Default:
Type:
Components:
SigPath Profile=Yes
A-50
OL-1110-23
Appendix A

Components
SS7-ANSI
SS7-ITU
SS7-Japan
*.T25
Desc:
T25
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
SS7-Japan
OL-1110-23
A-51
Appendix A
Components
*.T26
Desc:
T26
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
SS7-Japan
*.T27
Desc:
T27
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
A-52
OL-1110-23
Appendix A

Components

SS7-Japan
*.T28
Desc:
T28
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
SS7-Japan
*.T33
Desc:
T33
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
OL-1110-23
A-53
Appendix A
Components

SS7-Japan
*.T34
Desc:
T34
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
SS7-Japan
*.T35
Desc:
T35
Default:
Type:
Components:
A-54
OL-1110-23
Appendix A

Components
SigPath Profile=Yes
SS7-ITU
SS7-Japan
*.T36
Desc:
T36
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
SS7-Japan
OL-1110-23
A-55
Appendix A
Components
*.T38
Desc:
T38
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ITU
SS7-Japan
*.T5
Desc:
T5
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
A-56
OL-1110-23
Appendix A

Components
SS7-Japan
*.T6
Desc:
T6
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
SS7-Japan
*.T7
Desc:
T7
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
OL-1110-23
A-57
Appendix A
Components

SS7-Japan
*.T8
Desc:
T8
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
SS7-ITU
SS7-Japan
*.T9
Desc:
T9
Default:
Type:
Components:
SigPath Profile=Yes
SS7-ANSI
A-58
OL-1110-23
Appendix A

Components

SS7-ITU
SS7-Japan
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:
The maximum number of RASERVERs is 5.
You must add an RAPATH before adding an RASERVER
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.
Duplicate PORT or ORDER values cause an error.
The PGW uses PORT with a value between <local-port> and <local-port + <number of port>>
The RASERVER component structure is shown in Table A-39.

Table A-39
RASERVER Component Structure
Table 1:
Parameter MML
Name
NAME

commands
- are allowed. Names should begin with an
DESC

characters.
OL-1110-23
A-59
Appendix A
Components
Table 1:
Parameter MML
Name
SVC

service.
IPADDR
This parameter is mandatory.

PORT
Local port number
1025 through 65535.

PEERADDR
Remote IP address
PEERPORT
IP address; (0.0.0.0). This may also be

specified as a hostname or a DNS name.
1025 to 65535.
The accounting port number
used on the destination server for
accounting data.
IPROUTE
MML name for first IP route

(optional)
MML name of a previously provisioned IP

route. (empty string)
ORDER
ORDER is the order of the server 1 to 99.

as primary server. The order with
the lowest value is selected as the
primary server.
KEY
KEY is the shared key for

encryption used for this server.
Alphanumeric and dash characters are

allowed. The KEY must start with a character.
The length of KEY is 1 to 99. (empty string)
TIMEOUT
TIMEOUT is the duration in

seconds before the packet is
retransmitted.
1 to 30. (6)
RETRYCOUNT
The number of times a packet is 1 to 10. (2)

re-transmitted before giving up.
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
The routing component structure is shown in Table A-40.
A-60
OL-1110-23
Appendix A

Components
Table A-40
Routing Component Structure
Component MML
Name
Parameter MML
Name
SIPRTTRNKGR NAME
P
Trunk group number
Unique name for this SIP routing

trunk group number.
1 through 9999; (none)
URL
SIP proxy service

address in the format of
IP address, hostname, or
DNS name
SIPPROXYPORT
UDP port number used

by the SIP proxy server
VERSION
SIP version of the SIP

proxy server
CUTTHROUGH
Cut through indicates

the point in a call at
which the call is
through connected.
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
SIP extension supported 0 or 1; (0)

Note
RTLIST
0 through 3; (0)
This property is 0 = False

1 = True
reserved for
future use and is
not currently
implemented.
SRVRR
Indicates if the (current) 0 or 1; (0)

SIP URL is a server
0 = False - not a Server DNS
(SRV) DNS or not
1 = True - is an SRV DNS
NAME
Route list name
20 alphanumeric
RTNAME
Route name
; (0)
NEXTRTNAME
Next route name
20 alphanumeric
DISTRIB
Indicates if random or
sequential distribution
is enabled
String: On or Off, (Off). Select Off

(default) to use sequential
selection to choose the trunk group
in the route; or On to use random
selection.
NAME
Route name
20 alphanumeric
TRNKGRPNUM
Trunk group number
; (0)
NEXTTRKGRP
Next trunk group
Integer 0 through 65535; (0)
OL-1110-23
A-61
Appendix A
Components
Table A-40
Routing Component Structure (continued)
Component MML
Name
RTTRNKGRP
Parameter MML
Name
WEIGHTEDTG
Weighted trunk group
String: ON or OFF (OFF)
NAME
Trunk group number
Unique name for this routing trunk

group number.
1 through 9999; (none)
TYPE
Trunk group 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
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
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)
A-62
OL-1110-23
Appendix A

Components
Table A-40
Routing Component Structure (continued)
Component MML
Name
Parameter MML
Name
Cut through indicates

the point in a call at
which the call is
through connected.
0 through 3; (0)
RESINCPERC
Reserve incoming
bandwidth percentage
0 through 100 (0)
BEARERCAPNA
ME
Bearer capability name
20 alphanumeric (NULL)
NAME
Used to configure
CARRIERID,
RTEOPTION, and
RTLISTNAME.
CARRIERID
2 to 5 digits (for Germany the

Mandatory parameter;
identifies the carrier ID range is 2 or 3 digits)
code
RTEOPTION
Optional parameter;
identifies the route
option
RTLISTNAME
This parameter is only 20 alphanumeric

valid if RTEOPTION is
set to CARRIER.
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
Up to 124 alphanumeric characters

providing time-ordered options to
use a specified result set (from the
dial plan result table). The format
is: setName1, setTime1,
setNamen, setTimeChangen.
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
String: DN (default), CARRIER,

or BLOCKED
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.
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
The session set component structure is shown in Table A-41.

Table A-41
Session Set Component Structure
Parameter MML
Name
NAME
Unique ID of this
name used in MML
commands

DESC
IPADDR1
IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4;
IPADDR2
IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4;
PORT
Local port number
1025 through 65535.
PEERADDR1
Remote IP address 1

PEERADDR2
Remote IP address 2

A-64
OL-1110-23
Appendix A

Components
Table A-41
Session Set Component Structure (continued)
Parameter MML
Name
PEERPORT
Remote port
1025 through 65535.
EXTNODE
External Node MML name
MML Name of a previously configured external

node.
NEXTHOP1
Next hop address 1

9.4(1).
NETMASK1
Subnet mask address 1
Subnet mask address; (255.255.255.255). This

parameter is removed in software Release 9.4(1).
NEXTHOP2
Next hop address 2

9.4(1).
NETMASK2
Subnet mask address 2

IPROUTE1
First IP route MML name

9.4(1).
IPROUTE2
Second IP route MML name MML name of a previously configured IPROUTE.

9.4(1).
TYPE
Sessionset external node

type
BSMV0 or IPFAS.
The following rules apply when you are creating or editing session sets:
The ISDNSIGTYPE of the EXTNODE must be N/A if the TYPE is IPFAS.
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.
IPADDR1 and IPADDR2 must have different values.
PEERADDR1 and PEERADDR2 must have different values except when the EXTNODE is a VISM
(MGX8850).
The maximum number of IPFAS session sets per port is 50.
The PORT attribute cannot be set to the same value as the PORT attribute of any ASSOCIATION,
IPLNK, or SIPLNK.
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.
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 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
The SGP structure is shown in Table A-42.

Table A-42
SGP Component Structure
Parameter MML
Name
NAME
Unique ID of this
name used in MML
commands

DESC
EXTNODE
MML name of the external

node

node.
Keep the following in mind when creating or editing external nodes
A maximum of four SGPs are allowed for each external node.
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
A-66
OL-1110-23
Appendix A

Components
MML NameSIPLNK
The SIP link component structure is shown in Table A-43.

Table A-43
SIP Link Component Structure
Parameter MML
Name
NAME
Unique ID of this
name used in MML
commands

DESC
IF
Ethernet interface MML

name
MML name of a previously defined Ethernet

interface. This parameter is removed in software
Release 9.4(1).
PORT
Local port number

(Recommended setting of 5060 for SIP).
PRI
Priority
IPADDR
SVC

supports
MML name of a previously defined signal service.
NEXTHOP
Next hop address

9.4(1).
NETMASK
Subnet mask address

SIP Signaling Service

This component type represents the SIP signaling service or signaling path to SIP proxy servers. Its
MML NameSIPPATH
The SIP signaling service component structure is shown in Table A-44.

Table A-44
SIP Path Component Structure
Parameter MML
Name
NAME


DESC

OL-1110-23
A-67
Appendix A
Components
Table A-44
SIP Path Component Structure (continued)
MDO
MDO file name
Valid protocol name from variants.dat (IETF_SIP

is the only valid MDO variant for this signaling
service.).
ORIG LABEL

feature.

9.6(1).
TERM LABEL

feature.

9.6(1).
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
The SS7 route component structure is shown in Table A-45.

Table A-45
SS7 Route Component Structure
Parameter MML
Name
NAME


DESC

DPC
Destination point code

MML name
MML name of a previously defined point code.
LNKSET
Linkset MML name
MML name of a previously defined linkset.
OPC
Originating point code

MML name
PRI
Priority
SS7 Signaling Service Properties

The SS7 signaling service properties component types serve as configuration parameters that you can
use to tune signaling service communications. These properties apply to all SS7 signaling services you
create. You do not have to enter these values. Its MML name is as follows:
MML component name: SIGSVCPROP
The SS7 signaling service structure is shown in Table A-46.
A-68
OL-1110-23
Appendix A

Components
Table A-46
SS7 Signaling Service Property Descriptions
Parameter MML Name
Parameter Values
adjDestinations
Number of adjacent destination point codes.

Default = 16
ANationalPrefix
BothwayWorking
CGBA2
International prefix string to be added to the

international dialed number when NOA is
enabled.
Value range: NULL or a numeric string.
National prefix string to be added to the national

dialed number when NOA is enabled.
Value range: NULL or a numeric string.
Set to 0 to disable both way release/circuit free

handling for BTNUP protocol.
Values: 0 or 1.
Determines if group (0) or individual (1) circuit

group blocking acknowledgments (CGBAs) are
required before the blocking is considered
successful. Applicable only to ANSI SS7, IBN7,
and CTUP protocols. (Only available in software
Release 9.3(2) and later.)
Values: 0 or 1.
Note
CLIDefaultAllowed
Default = NULL
Default = 1
Default = 0
When set to 1, a significant performance

impact occurs for individual circuit
supervision messages during maintenance
or during a failure condition.
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
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.
OL-1110-23
A-69
Appendix A
Components
Table A-46
Parameter MML Name
Parameter Values
COLDefaultAllowed
Sets the presentation restricted field in the

connected line identity.
Values: TRUE (1) or FALSE (0)
Default: FALSE
When set to TRUE and an incoming Q931 setup
Note
Used in all protocols that are based
on q761 except HONG_KONG,
AUSTRALIA, FRENCH, NTT,
JAPAN_JT.
presentation allowed.
When set to FALSE and an incoming Q931 setup
presentation restricted.
CotInTone
CotListenDuration
Receive tone for continuity test (COT) hardware.

The tone to listen for when doing a COT. Enter
value in Hz.
Value: 1780 or 2010.
Maximum period to listen for a COT.
Value range: 0 through 200, specified in

milliseconds (should be less than 2
seconds). The T24 timer will be set for 60.
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.
Value range: 0 through 100%.

Default = 0
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
TCAP transaction ID range (for example, 1

through 10000) for a specific subsystem.
0 = entire range.
Determines the type of COT handling for the

specified destination.
Values: 0no COT, loop, or transponder.
ExtCOT
ForwardCLIinIAM
Default = 0
Default = Loop
Set to 1 if outgoing IAM should contain the calling Values: 0 or 1.

line identity, if available. Only applicable for
Default = 0
BTNUP when interworking from other protocols.
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.
A-70
OL-1110-23
Appendix A

Components
Table A-46
Parameter MML Name
Parameter Values
GLARE
Call collision handling.
Valid values are:
Note
Note
Note
Note
0 = No glare handling; also known as

yield to all double seizures. Call
collision results in a REL sent to both
calls.
Both ends of a link can be given this
option.
1 = The Cisco PGW 2200 Softswitch
has control of all circuits, and any call
collisions are handled by this
Cisco PGW 2200 Softswitch. The
Cisco PGW 2200 Softswitch ignores
incoming IAMs and proceeds with its
own calls as normal.
Only one end of a link can be
designated with this option.
2 = Highest point code controls the
even circuits. Depending on the OPC of
the Cisco MGCs, the side that has the
higher point code controls the even
circuits, and the side that has the lower
point code controls the odd circuits.
Both ends of a link can be given this
option.
3 = No control. The
Cisco PGW 2200 Softswitch specified
with this option does not control any
circuits. The
Cisco PGW 2200 Softswitch accepts
incoming IAMs from the side with
control.
This option is usually used along
with the remote node designated
with control.
Default = 0
GRA2
Determines if paired (0) or single (1) group reset Values: 0 or 1.

acknowledgments (GRAs) are required before the
Default = 0
reset is considered successful. Only applicable to
ANSI SS7, IBN7, and CTUP protocols.
OL-1110-23
A-71
Appendix A
Components
Table A-46
Parameter MML Name
Parameter Values
GRSEnabled
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.
Values: false or true.
This property (available in software Release

9.4(1) patch 8 and above) is assigned to an SS7
point code type signal path. Enables Group Reset
on Service State Change procedure at point code
initialization.
Values: false or true.
GRSonSSCEnabled
Note
hopCount
When the far end receives the GRS

message, any active calls are released on
the point code, as per ITU-T
Recommendation Q.764.
Default hop count.
If true, GRS messages are sent for all CICs

associated with the point code.
If false, GRS messages are not sent.
Default = false
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.
Default = false
Value range: 0 or 15 (this indicates the

maximum number of hops allowed for
SCCP messages).
Default = 1
layerRetries
Number of times to resend request to adjacent

layer without getting a response.
Value range: 0 through 5. 0 = no retries.

Default = 2
layerTimer
Time (in tenths of a second) to wait for a response Value range: 0 through 10.
from adjacent layer (SS7 controller, TCAP to
SCCP); tailor when layers are not resident on same
Default = 10
processor.
maxMessageLength
Maximum length of message to MTP3.
This value must be less than the value for

mtp2MaxMsuFrmLen.
Default = 250
Determines whether or not preanalysis is

performed
Default = 0
Is used when an incoming ISDN message

containing a Channel identification information
element identifier with bit 7 of octet 3 set to 0
(Interface implicitly identified) as the implied
interface ID value.

Default = 65535

Normalization
Normalization of dialed number to unknown.
Set to 0 for disabled and 1 for enabled.

Values: 0 or 1.
Default = 0
A-72
OL-1110-23
Appendix A

Components
Table A-46
Parameter MML Name
Parameter Values
OD32DigitSupport
Values are: 0 (disabled) and 1 (enabled).

Allows 32 digits and overdecadic digits support
for the ANSI, Q.761, and Q.767 protocol variants Default = 0
for the ANSI, SS7-ITU, SS7-China, SS7-Japan,
and SS7-UK protocol families.
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.
Values are: 0 (enabled) and 1 (disabled).

OmitCgPnFromUnavailab Determines if mapping between the SIP From
le
header to the IAM calling party number is enabled
Default = 0
when the SIP message header From is
unavailable.
OOverlap
OverlapDigitTime
Set to 1 to enable overlap signaling for call

origination from this traffic path.
Overlap interdigit timer. The time to wait for the

rest of the digits.
Note
OwnClli
Default = 0
Default = 6
If OverlapDigitTimeValue timer is set to

more than thirty seconds, other timers
expire before this timer.
Specifies the common language location identifier Value range: Alphanumeric string, up to 11
(CLLI).
characters.
OL-1110-23
A-73
Appendix A
Components
Table A-46
Parameter MML Name
Parameter Values
RedirMax
Specifies the maximum allowable value of the

redirection counter parameter available in some
C7 signaling systems before the call is
force-released. Used to prevent routing loops in
certain applications.
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:
OCCAllow the specified number

(15) of redirections before the call is
force-released.
TCCReset the redirect counter to 5 if

it is < 1 or > 5.
0:
restartTimer
Time (in tenths of a second) to pause before

sending next group of messages to MTP3 after
restart.
OCCAllow the redirection counter to

have any value from 1 to 7.
TCCIf the redirection counter is set

to a value 07, set it as is; if the
redirection counter is greater than 7,
reset it to 7.
Note
OCC = Originating (side) call

control.
TCC = Terminating (side) call
control.

Default = 10
RoutePref
Determines the preferred route.

0 = No Preference (default)5 = IP
Preferred
1 = ATM Essential6 = IP
Excluded
2 = ATM Preferred7 = TDM
Essential
3 = ATM Excluded8 = TDM
Preferred
4 = IP Essential9 = TDM
Excluded
Default = 0
A-74
OL-1110-23
Appendix A

Components
Table A-46
Parameter MML Name
Parameter Values
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).

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). Default = 0

sendAfterRestart

Number of queued messages to send (in one
group) to MTP3 after restart end. This value,
Default = SS7-ANSI = 16
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.
slsTimer
Time (in tenths of a second) to maintain the same Value range: 0 through 600.
signal linkset in class 1 (connectionless)
messages. This is the type of service provided by
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.
sstTimer
Time (in tenths of a second) between the sending

of Subsystem Status Test (SST) messages to an
unavailable remote subsystem.

0 = Disabled, 300 = 30 seconds
standard
Version of protocol standard supported for this

STP/SCP.
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
Set to 1 to enable overlap signaling for call

termination to this traffic path.
Values: 0 or 1.
variant
SS7 protocol variants supported by the local

subsystem.
Default = SS7-ANSI=SS7-ANSI,SS7-ITU
VOIPPrefix
A numeric string.
Default = 0
Default = 0
OL-1110-23
A-75
Appendix A
Components
SS7 Signaling Service (sigpath)

The SS7 Signaling Service (sigpath) component type represents an SS7 signaling service or signaling
path to a particular SS7 switch (destination). Its name is as follows:
MML NameSS7PATH
The SS7 signaling service component structure is shown in Table A-47.

Table A-47
SS7 Signaling Service Component Structure
Parameter MML
Name
NAME

Unique ID of this
component and component characters. No special characters other than -
are allowed. The name should begin with a letter.
name used in MML
commands
DESC
SIDE
String user for user side and network for network

side; (network).
MDO
MDO file name
Valid protocol name from variants.dat. (This is

limited to any MDO SS7 protocol variant.)
DPC
Destination point code

MML name
CUSTGRPID
Customer group ID
OPC
Originating Point Code

MML name
ORIG LABEL

feature.

9.6(1).
TERM LABEL

feature.

9.6(1).
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
The SS7 subsystem component structure is shown in Table A-48.
A-76
OL-1110-23
Appendix A

Components
Table A-48
SS7 Subsystem Component Structure
Parameter MML
Name
NAME
Unique component
name used in MML
commands

DESC

LOCALSSN
Subsystem number
Integer from 2 through 254;(0) 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.
Adjacent point code of

the mated STP
MML name of a previously defined adjacent point

code.
(formerly SSN)
MATEDAPC
It is only used when mating STP pairs.

It is not used when creating AIN subsystems.
Originating point code
MML name of the
mated STP
MML name of a previously defined originating

point code.
PRI
Priority
Integer greater than 0; (1). Not used when mating

STP pairs.
PROTO
Protocol family
SS7-ANSI or SS7-ITU when creating an AIN

subsystem.
OPC
Not used if SUAKEY is specified.
SS7-ANSI, SS7-China, SS7-ITU, SS7-Japan, and

SS7-UK when mating an STP pair.
REMOTE SSN
Remote subsystem
number
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.
SUAKEY
MML name of
SUAKEY
MML name of previously defined routing key.

This is an optional parameter and is used only for
SUA.
Not used if OPC is specified.
SVC
MML name of Adjacent MML name of a previously defined adjacent point

point code or TCAP/IP code, or MML name of a previously defined
service
TCAP/IP service.
OL-1110-23
A-77
Appendix A
Components
Table A-48
SS7 Subsystem Component Structure (continued)
Parameter MML
Name
STPSCPIND
STP/SCP index used for Integer greater than 0; (0). Not used when mating
IN triggers
STP pairs.
TRANSPROTO Transport protocol
SCCP Use if SVC is an APC
SUA Use for Sigtran carrying TCAP over

SUA
TCPIP Use if SVC is TCAP over IP
This parameter is not needed when mating 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
The SUA key component structure is shown in Table A-49.

Table A-49
Note
SUAKEY Component Structure
Parameter MML Name
NAME
M3UA key name

DESC
OPC
Associated OPC
APC
Associated APC
(optional)
MML name of a previously configured APC.
LOCAL SSN
Associated local SSN
Number of a local SSN. Values are 0, 2-254 (0).
ROUTING CONTEXT

context). Each SUA key must have a unique
routing context.
NETWORK
APPEARNCE
Network appearance
(optional)

indicates an invalid network appearance.
None of the parameters for this command can be modified.
A-78
OL-1110-23
Appendix A

Components
The following rules apply when creating SUA keys:
You can provision up to 256 SUA keys.
Up to 64 OPCs can use SUA signaling services.
Parent OPC must be a true OPC
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
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
The SUA route component structure is shown in Table A-50.

Table A-50
Note
SUAROUTE Component Structure
Parameter MML Name
NAME
SUA route name

DESC
APC
Associated APC
MML name of a previously configured APC.
EXTNODE
Associated external
node

node.
OPC
Associated OPC
REMOTESSN
Associated remote SSN Number of a remote SSN. Values are 0, 2-254 (0).
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.
The associated OPC must be a true 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.
The associated external node must support SUA signaling.
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.
OL-1110-23
A-79
Appendix A
Components
SS7 Signaling Gateway Process

This component represents a SS7 signaling gateway process.
MML NameSGP
The SS7 signaling gateway process component structure is shown in Table A-51.
Table A-51
Note
SGP Component Structure
Parameter MML Name
NAME
M3UA route name

DESC
EXTNODE
External node that is

running the SS7
signaling gateway
process
DESC is the only parameter for this command that can be modified.
The following rules apply when creating/editing SS7 signaling gateway processes:
You can provision up to 96 M3UA SS7 signaling gateway processes.
You can provision up to 8 SUA 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.
Switched Trunk Provisioning

This is the Cisco PGW 2200 Softswitch NE component and represents a trunk (switched bearer
channels). Its MML name is as follows:
MML NameSWITCHTRNK
The switched trunk provisioning component structure is shown in Table A-52.

Table A-52
Switched Trunk Provisioning Component Structure
Parameter MML Name
Parameter
Description
NAME
Trunk group
member number
Integer greater than 0
TRNKGRPNUM
Trunk group
number
Integer from 1 through 65535. This

parameter is mandatory for all operations
SPAN
Span
Integer from 1 through 65535 or ffff
CIC
Circuit Identifier
Code.
Integer from 1 through 65535
A-80
OL-1110-23
Appendix A

Components
Table A-52
Switched Trunk Provisioning Component Structure (continued)
Parameter MML Name
Parameter
Description
CU
Coding Unit MML MML name of a previously defined CU

name
ENDPOINT
End point
End point
SPANSIZE
Number of trunks
per span.
Integer greater than 0 and less than 31; (1)
TARIFF
This is the Cisco PGW 2200 Softswitch NE component used to provision entries in the Tariff table. Its
MML NameTARIFF
The switched trunk provisioning component structure is shown in Table A-53.

Table A-53
Tariff Provisioning Component Structure
Parameter MML
Name
NAME


DESC

TARIFFID
Tariff ID
TARIFFRATE
Tariff rate
SCALEFACTOR
Scale factor
Integer; 0, 1, 2, 3, 249, 250, 251, 252, 253, 254, or

255.
Backhaul TCP Link

The Backhaul TCP link component represents a static IP route. Its MML name is as follows:
Note
MML NameTCPLINK

The Backhaul TCP link component structure is shown in Table A-54.
OL-1110-23
A-81
Appendix A
Components
Table A-54
TCPLINK Component Structure
Parameter MML
Name
NAME
Unique component
name used in MML
commands

DESC
TYPE
Signaling service type
Identifies the type of signaling service associated

with this link. Must be set to BRI.
IPADDR
Local IP address
PORT
Port number
1024 through 65535; (2428).
PEERADDR
Highest priority
destination address
IP address in dotted decimal notation.
PEERPORT
Destination port number 1024 through 65535; (2428).
EXTNODE
MML name for

MML name of a previously provisioned Cisco BRI
associated external node voice gateway.
IPROUTE
MML name for first IP

route (optional)
MML name of a previously provisioned IP route.
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
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
A-82
OL-1110-23
Appendix A

Components
Note

The TDM interface component structure is shown in Table A-55.
Table A-55
TDM Interface Component Structure
Parameter
MML Name
NAME


DESC

CARD
Card which supports this

TDM interface
MML name of a previously defined card or index

of the card for SNMP
LIFNUM
Line interface number
1 to 4 for V.35, 1 otherwise; (1)
RESIST
Resistance (in Ohms)
75 for ITK(T1), 120 for ITK (E1); otherwise 0;

(75)
DATARATE
Data rate
Used only for V.35 card. Values are 48,56, or 64.

(64)
CLOCK
Internal or external
Used only for V.35 card. Values are EXT, INT;

otherwise NA; (EXT).
DTEDCE
DTE or DCE
Used only for V.35 card. Values are DTE, DCE;

otherwise NA; (DTE).
CODING
Line coding
Used only for ITK card. AMI (alternate mark

inversion) and B8ZS (bit stuffing for clear
channel) for T1, HDB3 for E1; Default value is
B8ZS for T1, HDB3 for E1, and NA for V.35.
(B8ZS)
FORMAT
Interface Format
Used only for ITK card. ESF (extended super

frame) and D4 (super frame) for T1, CRC4 and
CCS for E1. Default value is ESF for T1, CRC4
for E1, and NA for V.35. (ESF)
SIGTYPE
Signal type
T1 for DS1 T1, CEPT for European E1, V.35 for

64KBPS digital. (T1)
HDLC
High-level Data Link

Control
DEFAULT(HDLC) and IHDLC for ITK;

otherwise not used; (DEFAULT)
TDM Link
The TDM link component type represents a TDM link used on the Cisco PGW 2200 Softswitch. Its
MML NameTDMLNK
OL-1110-23
A-83
Appendix A
Components
Note

The TDM interface component structure is shown in Table A-56.
Table A-56
TDM Link Component Structure
Parameter MML
Name
NAME


DESC

SLC
Signaling Link Code
0 to 15; (1)
PRI
Priority
SVC
Signaling service this link

supports
MML name of a previously defined signal service

or linkset or index of the signal service for SNMP
IF
TDM interface this link is on MML name of a previously defined TDMIF or

index of the TDMIF for SNMP
TIMESLOT
Timeslots this link uses
1 to 32 for E1, 1 to 24 for T1; (1)
Trunk Group Provisioning

Trunk group provisioning component type represents a trunk group. This component is supported by
MML only. Its MML name is as follows:
MML NameTRNKGRP
The trunk group provisioning interface component structure is shown in Table A-57.
Table A-57
Trunk Group Provisioning Component Structure
Parameter MML
Name
NAME
Trunk group number
Integer 1 through 9999 (none);
CLLI
CLLI
Value range: Alphanumeric string, up to 11

characters.
SVC
Signaling service
MML name of a previously defined SS7, IPFAS, or

FAS signaling service.
A-84
OL-1110-23
Appendix A

Components
Table A-57
TYPE
Trunk Group Provisioning Component Structure (continued)
Trunk group type
One of the following, ATM, CTI, IP, IP_SIP,

SIP_IN, TDM_ISUP, TDM_CAS, TDM_TUP,
TDM_GEN, TDM_DPNSS, TDM_PRI,
TDM_BTNUP.
Trunk group type IP is used with EISUP signaling
service. TDM_PRI is used with IPFAS or FAS
signaling services with the protocol family of
ISDNPRI. TDM_DPNSS is used with signaling
services with the protocol family of DPNSS.
TDM_ISUP is used with SS7 signaling services
with switch types of 0, 5, 20, 23, 40. TDM_TUP is
used with SS7 signaling services with switch type
of 5. TDM_BTNUP is used with SS7 signaling
services with SS7-UK variants with switch type of
5.TDM_GEN is used with SS7 signaling services
with switch types not equal to 0, 5, 20, 23, 40.
TDM_CAS is currently not supported. TDM_CAS
is used with CAS signaling service. IP_SIP is used
for SIP signaling services at the terminating side.
SIP_IN is used for SIP signaling services at the
originating side and only one such trunk group can
be configured on each
Cisco PGW 2200 Softswitch node. CTI is used for
CTI signaling.
0 = No switch-specific 23 = SS7 ANSI
logic for the signaling path.26 = DPNSS
5 = BTNUP27 = NET5
22 = NI2
SELSEQ
Select sequence
One of the following, LIDL, MIDL, ASC, DESC,

RDM, EDESC, ODESC, EASC, OASC, CASC,
CDESC, or ITU2.
QABLE
Timeslot this link uses
Y or N; (N)
ORIG LABEL

feature.
As many as 20-character alphanumeric string. This

TERM LABEL

feature.
As many as 20-character alphanumeric string. This

Trunk Group Profile MML Provisioning

This is used to configure the trunk group profiles. Its MML name is as follows:
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
Trunk Group Profile Provisioning Component Structure
Parameter MML
Name
NAME
Trunk group name used in

MML commands

<PROFILETYPEN Profile type name

AME>

GTD Parameter Provisioning

This is used to configure the GTD parameters. Its MML name is as follows:
MML NameGTDPARAM
The GTD provisioning component structure is shown in Table A-59.

Table A-59
GTD Parameter Provisioning Component Structure
Parameter MML
Name
NAME
GTD parameter name used

in MML commands

GTDPARAMSTRI
NG
GTD parameter string
A string with a length less than or equal to 460

characters.
OVERRIDESTRIN GTD override fields string

G
A string with a length less than or equal to 256

characters.
Table A-60 lists the GTD parameters that can be entered in the build_string in alphabetical order.
Table A-60
GTP Parameters
GTD Parameter GTD Parameter Description

ACL
Automatic Congestion Level
ADI
Access Delivery Information
APP
Application Transport
ATP
Access Transport
BCI
Backward Call Indicators
BSG
Business Group
BVN
Backward GVNS
CAI
Cause Indicators
A-86
OL-1110-23
Appendix A

Components
Table A-60
GTP Parameters (continued)

CCN
CCNR Possible Indicator
CCS
Call Completion Service Setup
CDI
Call Diversion Information
CDN
Called Directory Number
CDT
Call Diversion Treatment Indicators
CGL
Calling Geodetic Location
CGN
CHI
Call History Information
CHN
Charge Number
CIC
Circuit Identification (Call Instance) Code
CID
CIN
Called IN Number
CMI
Call Modification Indicators
CNF
Conference Treatment Indicator
CNN
Connected Number
CNR
Connection Request
COL
Collect Call Request
COR
Correlation Identity
CPC
Calling Party Category
CPN
Called Party Number
CRF
Call Reference
CSI
Carrier Selection Information
CSP
Carrier Service Provider Information
CTI
Continuity Indicators
CTN
Call Transfer Number
CTR
Call Transfer Reference
DIS
Display Information
ECI
Echo Control Information
EGR
Egress
EVI
Event Information Indicators
FAI
Facility Indicators
FCI
Forward Call Indicators
FDC
Known Field Compatibility Information
FVN
Forward GVNS
GCI
Global Call Identification
GEA
Generic Address
OL-1110-23
A-87
Appendix A
Components
Table A-60

GED
Generic Digits
GEN
Generic Name
GIC
Closed User Group Interlock Code
GNO
Generic Notification
GRF
Generic Reference
HOC
Hop Counter
HTR
Hard To Reach
INI
Information Indicators
IRI
Information Request Indicators
ISC
Originating ISC point Code
JUR
Jurisdiction
LON
Location Number
LPI
Loop Prevention Indicator
LSP
Local Service Provider Information
MCI
Message Compatibility Information
MCR
MCID Response indicator
MLP
MLPP precedence
MRI
MCID Request Indicator
NET
Network Transport
NMC
Network Management Controls
NOC
Nature of Connection Indicators
NPF
Number Portability Forward Information
NRN
Network Routing Number
NSF
Network Specific Facilities
OBI
Optional Backward Call Indicators
OCI
Original Called IN Number
OCN
OCT
Call Offering Treatment Indicators
OFI
Optional Forward Call Indicators
OLI
Originating Line Information
OSI
Operator Services Information
OTN
PBI
Pivot Backward Information
PCA
Pivot Capability
PCI
Parameter Compatibility Information
PCT
Pivot Counter
A-88
OL-1110-23
Appendix A

Components
Table A-60

CCN
CCS
CDI
CDN
CDT
CGL
CGN
CHI
CHN
Charge Number
CIC
CID
CIN
Called IN Number
CMI
CNF
CNN
Connected Number
CNR
Connection Request
COL
COR
CPC
CPN
Called Party Number
CRF
Call Reference
CSI
CSP
CTI
CTN
CTR
DIS
Display Information
ECI
EGR
Egress
EVI
FAI
Facility Indicators
FCI
FDC
FVN
Forward GVNS
GCI
GEA
Generic Address
OL-1110-23
A-89
Appendix A
Components
Table A-60

CCN
CCS
CDI
CDN
CDT
CGL
CGN
CHI
CHN
Charge Number
CIC
CID
CIN
Called IN Number
CMI
CNF
CNN
Connected Number
CNR
Connection Request
COL
COR
CPC
CPN
Called Party Number
CRF
Call Reference
CSI
CSP
CTI
CTN
CTR
DIS
Display Information
ECI
EGR
Egress
EVI
FAI
Facility Indicators
FCI
FDC
FVN
Forward GVNS
GCI
GEA
Generic Address
A-90
OL-1110-23
Appendix A

Components
Table A-60

CCN
CCS
CDI
CDN
CDT
CGL
CGN
CHI
CHN
Charge Number
CIC
CID
CIN
Called IN Number
CMI
CNF
CNN
Connected Number
CNR
Connection Request
COL
COR
CPC
CPN
Called Party Number
CRF
Call Reference
CSI
CSP
CTI
CTN
CTR
DIS
Display Information
ECI
EGR
Egress
EVI
FAI
Facility Indicators
FCI
FDC
FVN
Forward GVNS
GCI
GEA
Generic Address
OL-1110-23
A-91
Appendix A
Components
Table A-60

GED
Generic Digits
GEN
Generic Name
GIC
Closed User Group Interlock Code
GNO
Generic Notification
GRF
Generic Reference
HOC
Hop Counter
HTR
Hard To Reach
INI
Information Indicators
IRI
Information Request Indicators
ISC
Originating ISC point Code
JUR
Jurisdiction
LON
Location Number
LPI
Loop Prevention Indicator
LSP
Local Service Provider Information
MCI
Message Compatibility Information
MCR
MCID Response indicator
MLP
MLPP precedence
MRI
MCID Request Indicator
NET
Network Transport
NMC
Network Management Controls
NOC
Nature of Connection Indicators
NPF
Number Portability Forward Information
NRN
Network Routing Number
NSF
Network Specific Facilities
OBI
Optional Backward Call Indicators
OCI
Original Called IN Number
OCN
OCT
Call Offering Treatment Indicators
OFI
Optional Forward Call Indicators
OLI
Originating Line Information
OSI
Operator Services Information
OTN
PBI
Pivot Backward Information
PCA
Pivot Capability
PCI
Parameter Compatibility Information
PCT
Pivot Counter
A-92
OL-1110-23
Appendix A

Components
Table A-60

PDC
Propagation Delay Counter
PFI
Pivot Forward Information
PRI
Pivot Routing Indicator
PRN
Protocol Name
PVS
Pivot Status
QOR
Query On Release Capability
RBI
Redirect Backward Information
RCT
Redirect Counter
RDC
Redirect Capability
RDS
Redirect Status
RFI
Redirect Forward Information
RGN
Redirecting Number
RMO
Remote Operations
RNI
Redirection Information
RNN
Redirection Number
RNR
Redirection Number Restriction
SCF
SCF ID
SCI
Service Code Indicator
SEA
Service Activation
SEG
Segmentation Indicator
SPC
Signaling Point Code
SPR
Special Processing Request
SRI
Suspend/Resume Indicators
SUN
Subsequent Number
TID
Transaction ID
TMP
Transmission Medium Required Prime
TMR
Transmission Medium Required
TMU
Transmission Medium Used
TNS
TRR
Transaction Request
UCI
UID Capability Indicators
UFC
Unknown Field Compatibility Information
UID
UID Indicators
USI
User Service Information
USP
User Service Information Prime
UTI
User Teleservice Information
OL-1110-23
A-93
Appendix A
Components
Table A-60

UUI
User-To-User Indicators
UUS
User-To-User Information
VER
Version of GTD
Dial Plan Provisioning Components

All components have a name parameter, which is the MML name, and a description, which is a text
description. The dial plan provisioning components are shown in Table A-61.
Table A-61
Dial Plan Provisioning Components
Component MML
Name
Parameter MML Name
Parameter
Description
DIALPLAN
OVERDEC
Overdecadic Status
The value can be either YES, or NO. This

parameter is only used when adding a dial plan;
(NO)
ADIGTREE
SETNAME
Result Set Name
MML name of the result set; (x)
DIGITTOPRESENT
Digit
It is set to 0 if it is the next digit otherwise it is the

appropriate digit application point; (0)
CALLSIDE
string
Call side is like originating, terminating; (x)
DIGITSTRING
Digits
Could not use with NEXTNODE or DIGIT or

INDEX; (x)
SETNAME
Result Set Name
DIGITTOPRESENT
Digit
It is set to 0 if it is the next digit otherwise it is the

appropriate digit application point; (0)
CALLSIDE
string
Call side is like originating, terminating; (x)
DIGITSTRING
Digits
Could not use with NEXTNODE or DIGIT or

INDEX; (x)
NAME
Result Name
MML name of the result; (x), has to be set
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
Next result name
; (x)
SETNAME
Result Set Name
MML name of the result set; (x), has to be set
NAME
Digit Modification
Name
MML name of the digit modification string; (x)
DIGSTRING
Digit string
; (x)
BDIGTREE
RESULTTABLE
DIGMODSTRING
A-94
OL-1110-23
Appendix A

Components
Table A-61
Dial Plan Provisioning Components (continued)
Component MML
Name
Parameter MML Name
ANOA
NOAVALUE
A-number NOA
Value
; (0)
NPIBLOCK
NPI index
; (0)
SETNAME
Result Set Name
NPIBLOCK
A-number NPI block
; (0)
BLOCKVALUE
Block value
0 to 15; (-1) If the block value is not specified the

result index is applied to all block values (0 to 15).
SETNAME
Result Set Name
NOAVALUE
B-number NOA
Value
; (0)
NPIBLOCK
NPI index
; (0)
SETNAME
Result Set Name
NPIBLOCK
B-number NPI block
; (0)
BLOCKVALUE
Block value

SETNAME
Result Set Name
CAUSEVALUE
Cause Value
; (0)
LOCATIONBLOCK
Location block
; (0)
SETNAME
Result Set Name
LOCATIONBLOCK
Location Block
; (0)
SETNAME
Result Set Name
BLOCKVALUE
Block value

SERVICE
NAME
Service name
MML name of the service; (x)
RESULTSET
NAME
Result Set Name
MML name of the result set; (x), has to be set
AWHITE
CLI
Calling Line Identity
ABLACK
CLI
BWHITE
CLI
SVCNAME
Service name
CLI
SVCNAME
Service name
DIGITSTRING
Ported Number Table ; (x)
ROUTENUM
Routing Number
; (x)
DIGITSTRING
Number Termination
Table
; (x)
RTLISTNAME
Route List Name
; (x)
ANPI
BNOA
BNPI
CAUSE
LOCATION
BBLACK
PORTTBL
TERMTBL
Parameter
Description
MML name of a previously defined service; (x)

MML name of a previously defined service; (x)
OL-1110-23
A-95
Appendix A
Components
Table A-61
Component MML
Name
Parameter MML Name
ACHGORIGIN
CUSTGRPID
Customer Group
Identity
CLI
CORIGIN
Charge Origin
The charge origination field. Value range: 0 to

9999; (0)
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
New Dial Plan

Identity
Value range: Alphanumeric string, of 4 characters.
ANUMDPSEL
CLI
Calling Party Number Value range: Alphanumeric string, up to 20

characters.
NEWDP
New Dial Plan

Identity
Value range: Alphanumeric string, of 4 characters.
DATE
The date of the

holiday
Format for the date is yy.mm.dd
HDAY
Holiday day
The value can be one of the following strings:

HOL1, HOL2, or HOL3
CPCVALUE
CPC value.
Value range: 0 to 255
SETNAME
Result Set Name.
TMRVALUE
TMR value.
Value range: 0 to 255
SETNAME
Result Set Name.
TNSVALUE
TNS value.
String value range: 000 to ffffffff
SETNAME
Result Set Name.
CLISETNAME
The CLI prefix set

name.
Value range: 1- to 4-digit alphanumeric character

string.
CLIPREFIX
The CLI prefix.
Value range: 1 to 20 overdecadic digits (0-9 and

A-F) or DEFAULT.
CUSTGRPID
The Customer group

ID.
4-digit alphanumeric string.
CUSTGRPID
The Customer group

ID.
IPADDR
The IP Address.
IP address or DEFAULT.
SUBNETMASK
The Subnet mask.
IP address (255.255.255.255).
CLISETNAME
The CLI prefix set

name.

string.
DEFRESULSTSET
RTEHOLIDAY
CPC
TMR
TNS
CLIPREFIX
CLIIPADDRESS
Parameter
Description
A-96
OL-1110-23
Appendix A

Components
Table A-61
Component MML
Name
Parameter MML Name
Parameter
Description
H323IDDIVFROM
CUSTGRPID
The Customer group

ID.
H323IDDIVFROM
H323 ID, Division

header, or From field. string.
CLISETNAME
The CLI prefix set

name.


string.
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.
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
Alarm manager. It is part of the process group

XEG-01. It is an active process. If it should go
down, it causes a major out-of-service alarm.
AMDMPR-01
Alarm and measurement dumper. It is part of the

process group XEG-01. It is an active process. If it
should go down, it causes a major out-of-service
alarm.
CDRDMPR-01
CDR dumper. It is part of the process group

XEG-01. It is an active process. If it should go
CFM-01
Configuration manager. It is part of the process

group XEG-01. It is an active process. If it should
go down, it causes a major out-of-service alarm.
DSKM-01
Disk space monitor. This shell script monitors disk

space and trims back older files in case the current
amount of free space is below a specified threshold.
It is part of the process group PFMG-01. This is a
monitoring process. If it should go down, it causes
a minor out-of-service alarm.
ENG-01
Engine. It is part of the process group ENGG-01. It

is an active process. If it should go down, it causes
a critical out-of-service alarm.
FOD-01
Failover controller. It is part of the process group

FTG-01. It is a monitoring process. If it should go
down, it causes a minor out-of-service alarm.
IOCC-01
IOS channel controller. It is part of the process

group IOSG-01. It is a passive process. If it should
go down, it causes a critical out-of-service alarm.
A-98
OL-1110-23
Appendix A

Properties
Table A-62
Processes (continued)
Process
Description
IOCC-02
IOS channel controller. It is part of the process

group IOSG-01. It is a passive process. If it should
go down, it causes a critical out-of-service alarm.
IOCM-01
IOS channel manager. It is part of the process group

IOSG-01. It is a passive process. If it should go
LOG-01
Log server. It is part of the process group

LOGG-01. It is a passive process. If it should go
down, it causes a minor out-of-service alarm.
MEASAGT
Measurements SNMP agent. It is part of the process

group SNMPG-01. This is an active process. If it
should go down, this is a major out-of-service
alarm.
MM-01
Measurement manager. It is part of the process

group XEG-01. It is an active process. If it should
go down, it causes a major out-of-service alarm.
MMDB-01
TimesTen DataBase Process. It is part of the process

group XEG-01. It is a passive process. If it should
go down, it causes a minor out-of-service alarm.
OPERSAGT
Operational SNMP Agent. It is part of the process

alarm.
POM-01
Provisioning Object Manager. It is part of the

process group XEG-01. It is an active process. If it
alarm.
PROVSAGT
Provisioning SNMP Agent. It is part of the process

alarm.
Replic-01
Replicator controller. It is part of the process group

ENGG-01. It is an active process. If it should go
down, it causes a critical out-of-service alarm.
TCAP-01
TCAP and SCCP protocol handler. It is part of the

process group IOSG-01. It is a passive process. If it
alarm.
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:
OL-1110-23
A-99
Appendix A
Protocol Variants
PropertyName = PropertyValue
PropertyName can be designated either by *.propertyName or by protocolFamily.propertyName (for

example, SS7-ANSI.mtp3tstSltmT2).
In a provisioning session, those properties with the protocolFamily prefix may be overridden by a linkSet
component. The overridden property is then written to properties.dat as:
LinkSetMMLName.propertyName.
Those default properties prefixed by an * may be overridden by a signalPath (or Service) component
that is defined in sigPath.dat. The overridden property will be written to properties.dat as
SigPathMMLName.propertyName.
You can find all of the Cisco PGW 2200 Softswitch properites in Chapter 6, Properties of
Cisco PGW 2200 Softswitch Release 9 MML Command Reference.
Protocol Variants
The tables in this section list the protocol variants supported for the corresponding software release.

Table A-63 provides a snapshot of the protocol variants supported in the Cisco PGW 2200 Softswitch
software Release 9.3(2) as of February 19, 2004. For protocol variants added after that date, refer to the
Cisco PGW 2200 Softswitch software Release Notes of the software version you are using for protocol
variants added after that date.
Table A-63
Supported Protocol Variants for Software Release 9.3(2)
Protocol Variant Name
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
A-100
OL-1110-23
Appendix A

Protocol Variants
Table A-63
Supported Protocol Variants for Software Release 9.3(2) (continued)
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
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
A-102
OL-1110-23
Appendix A

Protocol Variants
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

software Release 9.4(1) as of February 19, 2004. For protocol variants added after that date, refer to the
Table A-64
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
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
A-104
OL-1110-23
Appendix A

Protocol Variants
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
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

software Release 9.5(2) as of April 19, 2006. For protocol variants added after that date, refer to the
Table A-65
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
A-106
OL-1110-23
Appendix A

Protocol Variants
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
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
A-108
OL-1110-23
Appendix A

Protocol Variants
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

software Release 9.6(1) as of January 19, 2006. For protocol variants added after that date, refer to the
Table A-66
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
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
A-110
OL-1110-23
Appendix A

Protocol Variants
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
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
A-112
OL-1110-23
A P P E N D I X
Planning Worksheets
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
Interface Card Configuration Parameters
Name
Type
Slot
Description
en-1
EN
Ethernet interface 1
Table B-2
Ethernet Interface Configuration Parameters
Name
Card
Description
OL-1110-23
B-1
Appendix B
Table B-3
Planning Worksheets
External Device Worksheet Example
Device IP Address
(x.x.x.x)
Device Name
Description
10.15.7.34
as5300-34
Media Gateway 5300-34
B-2
OL-1110-23
Appendix B
Planning Worksheets
Table B-4
Originating Point Code Configuration Parameters
Name
Netaddr
Netind
Description
OPC Type
True OPC
OPC1
22.22.23
MGC 1 OPC
TRUEOPC
OPC1
OL-1110-23
B-3
Appendix B
Table B-5
Planning Worksheets
Destination Point Code Configuration Parameters
Name
Netaddr
Netind
Description
DPC1
32.32.33
DPC 1
B-4
OL-1110-23
Appendix B
Planning Worksheets
Table B-6
Originating Point Code Configuration Parameters
Name
Netaddr
Netind
Description
Type
STP1
12.12.13
STP 1 point code
TRUEOPC
True OPC
OL-1110-23
B-5
Appendix B
Table B-7
Planning Worksheets
Adjacent Point Code Configuration Parameters
Name
Netaddr
Netind
Description
STP1
12.12.13
STP 1 point code
B-6
OL-1110-23
Appendix B
Table B-8
Planning Worksheets
QSIG/Q.931 Over BRI Backhaul Signaling Service Worksheet Example
Name
External
Node
brisvc1
va-3640-01
Q.931
Call Model
Side
MDO File
Customer
Group ID
ETS_300_102
Call
Reference
Length
Description
BRI path to va-3640-01
OL-1110-23
B-7
Appendix B
Table B-9
Planning Worksheets
Linkset Configuration Parameters
Name
Point Code
Type
Protocol
Description
Lnkset-1
DPC-1
IP
SS7-ANSI
Linkset 1 to ITP-L 1
B-8
OL-1110-23
Appendix B
Planning Worksheets
Table B-10
C7 IP Link Configuration Parameters
MML
Parameter
Name
Configuration Setting
NAME
ss7lnk1
SESSIONSET
slt1
PRIORITY
TIMESLOT
SLC
LNKSET
lnkset1
DESC
SS7 link 0 for lnkset1 to 2611-1
NAME
SESSIONSET
slt1
PRIORITY
TIMESLOT
SLC
LNKSET
DESC
OL-1110-23
B-9
Appendix B
Table B-11
IP-Link Configuration Parameters
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
B-10
OL-1110-23
Appendix B
Planning Worksheets
Table B-12
SS7 Route Worksheet Example
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
OL-1110-23
B-11
Appendix B
Table B-13
Planning Worksheets
Nailed Trunk Worksheet Example
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
B-12
OL-1110-23
Appendix B
Planning Worksheets
Table B-14
Switched Trunk Worksheet Example
Trunk ID
Trunk
Group
Number
Span
CIC
Coding
Unit
End
Point
Span
Size
10101
25535
100
signal1
fixed
OL-1110-23
B-13
Appendix B
Table B-15
Parameter
Planning Worksheets
SS7 Subsystem Worksheet Example
Parameter Value
Name of APC or apc1

TCAP/IP
service
Protocol family
APC of the
mated STP
apc2
Priority
Local SSN
STP/SCP Index
Transport
protocol
SCCP
OPC
ROUTING_KEY_ID
Routing Key
rtkey1
SUA Key
Remote SSN
Table B-16
External Node Configuration Parameters
Name
Type
Gw1
AS5300
ISDN
Signaling
Type
Group
Description
AS5300 gateway 1
B-14
OL-1110-23
Appendix B
Planning Worksheets
Table B-16
External Node Configuration Parameters (continued)
Name
Table B-17
MML Parameter
Name
Type
ISDN
Signaling
Type
Group
Description
Media Gateway Signaling Service Configuration Parameters
NAME
MDO
EXTNODE
SIDE
CUSTGRPID
CUSTGRPTBL
ABFLAG
CRLEN
DESC
PATHSIZE
PORT
PEERPORT
SIGSLOT
SIGPORT
SIGPORTSKIP
BACKUP
Table B-18
TDM Interface Configuration Parameters
NAME
CARD
Description
OL-1110-23
B-15
Appendix B
Table B-19
Planning Worksheets
MGCP Signaling Service Worksheet Example
Name
Ext Node
Description
MGCpth1
Gw1
MGCP path to Gw1
B-16
OL-1110-23
Appendix B
Table B-20
Name
Planning Worksheets
SS7 Signaling Service Configuration Parameters
Side
MDO
DPC
CustgrpId
OPC
OL-1110-23
B-17
Appendix B
Table B-21
Planning Worksheets
SS7 Signaling Service Worksheet Example
Service Type
Name
Description
Protocol Type
Customer Group ID
SS7
ss7svc1
SS7 service to
DPC1
ANSISS7_
STANDARD
7777
B-18
OL-1110-23
Appendix B
Table B-22
Planning Worksheets
Cisco ITP-L Linkset Worksheet Example
Description
Linkset
Card Interface
Linkset Type
Linkset Rate
Protocol
Cisco ITP-L IP MGC IP

Address
Address
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
OL-1110-23
B-19
Appendix B
Table B-23
Name
Planning Worksheets
IP Link Worksheet Example
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
IP link for MGCP

service to Gw1
Backhaul TCP Link Worksheet Example
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
B-20
OL-1110-23
Appendix B
Planning Worksheets
Table B-25
Card
LIFNum
Resist
Data Rate
Clock
Table B-26
TDM Link Configuration Parameters
MML
Parameter
Name
DTE/DCE
Coding
Format
Sig Type
HDLC
DESC
IF
NAME
PRI
SLC
SVC
TIMESLOT
Table B-27
Session Set Parameters
MML
Parameter
Name
Value
NAME
IPADDR1
IPADDR2
PORT
PEERADDR1
PEERADDR2
PEERPORT
EXTNODE
TYPE
OL-1110-23
B-21
Appendix B
Table B-28
Planning Worksheets
IP Route Worksheet Example
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
IP FAS Signaling Service Worksheet Example
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
BRI path to va-3640-01
DPNSS Signaling Service Worksheet Example
Name
External
Node
dpnsvc2
va-3660-20
Customer
Group ID
DPNSS
Side
Signaling
Port
Signaling
Slot
Description
IUA DPNSSpath to GW
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
D-Channel Worksheet Example
Signaling Type
brichan1 bri
Table B-32
DPNSS Signaling Service Worksheet Example (continued)
Priority
Link
Slot
Port
Subunit
Description
britcp1
bri d-channel 1
M3UA Key Worksheet Example
Name
OPC
DPC
Routing
Context
Service Indicator
Network
Appearance
Description
m3key1
opc1
dpc1
14
ISUP
700
M3UA key 1
OL-1110-23
B-23
Appendix B
Table B-33
Planning Worksheets
M3UA Route Worksheet Example
Name
DPC
External Node
OPC
Description
m3rte1
dpc1
itp1
opc1
M3UA route 1
Table B-34
SCTP Association Worksheet Example
Parameter
Parameter Value
Name
assoc1
Description
association 1
Signaling Type
M3UA
SGP name
sgp1
First local address
175.23.211.15

(optional)
n/a
Local SCTP port number

(optional)
2905
Highest priority destination

address
117.52.16.20
Lowest priority destination

address (optional)
Destination SCTP port
number (optional)
External node name
itp1
First IP route name (optional) iproute1

Second IP route name
(optional)
iproute2
Number of bytes to advertise

for the local receive window.
(optional)
Maximum number of times to
retransmit SCTP INIT
message (optional)
B-24
OL-1110-23
Appendix B
Table B-34
Planning Worksheets
SCTP Association Worksheet Example (continued)
Parameter
Parameter Value
Maximum initial timer

retransmission value
(optional)
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)
Maximum time SCTP will
wait for other outgoing
datagrams for bundling
(optional)
Minimum value allowed for
the retransmission timer
(optional)
Maximum value allowed for
the retransmission timer
(optional)
Time between heartbeats
(optional).
IP Precedence (optional)
Differential Service Code
Point (optional)
Maximum number of
retransmissions to either peer
address 1 or 2 before it is
declared failed (optional)
Table B-35
SGP Worksheet Example
Name
External Node
Description
sgp1
itp1
SGP for itp1
OL-1110-23
B-25
Appendix B
Table B-35
Name
Table B-37
SGP Worksheet Example (continued)
External Node
Table B-36
Planning Worksheets
Description
SS7 Route Worksheet Example
DPC
Linkset
OPC
Priority
dpc1
lnkset1
opc1
SS7 Signaling Service Worksheet Example
Name
Q.931 Call
Model Side
MDO File Name DPC
Customer Group ID
OPC or Route
Key ID
ss7svc1
network
ansi_ss7
0000
m3rtkey1
dpc1
Description
SS7 signaling
service 1
B-26
OL-1110-23
Appendix B
Table B-38
Planning Worksheets
SUA Key Worksheet Example
Name
OPC
APC
Local SSN
Routing Context
Network
Appearance
Description
suakey1
opc1
apc1
70
ISUP
7000
SUA key 1
Table B-39
SUA Route Worksheet Example
Name
APC
External Node
OPC
Remote SSN
Description
suarte1
apc1
itp1
opc1
100
SUA route 1
Table B-40
SIP Data Path Worksheet Example
Name
MDO File Name
Description
sipsrv1
va-3660-20
path to Unity
OL-1110-23
B-27
Appendix B
Table B-40
SIP Data Path Worksheet Example (continued)
Name
Table B-41
Planning Worksheets
MDO File Name
Description
SIP Link Worksheet Example
Name
Signaling Service
Priority
IP Address
Port
Description
brichan1
bri
britcp1
bri d-channel 1
B-28
OL-1110-23
INDEX
call limiting
5-64
call reference length

adding
card
APC
3-10
line interface parameters
Customer Group ID
DPC
3-28
changing properties, linkset
3-11
channels
FAS or NFAS over IP transport service
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
SS7 signaling service

3-20
address
3-27
4-3
list of bulk export commands
2-2
session
5-8
2-2
3-10
4-3
working with session commands
4-6
3-154
component
association
ExtNode
provisioning
4-5
4-3
committing, configuration
adding
4-6
list of provisioning commands

list of session commands
adjacent point code

APC
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
retrieving one based on service
4-30
components to add
5-2
configuration
C
C7 IP link
4-30
committing
5-13
3-154
creating a new configuration
4-7
OL-1110-23
IN-1
Index
deploying
3-154
dual MGCs
4-10
modify an existing configuration
modifying non-active configuration

retrieving session data
single MGC
Generic Transparency Descriptor
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
MGW control links
trunk group and trunk files
3-53
Customer Group ID, adding
3-99
interface
3-28
Ethernet
2-29
interface card
definition
D-channel
international network indicator
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
E-ISUP signaling service

Ethernet interface
external node
adding
A-8
5-63
5-16
5-12, 5-15
5-15
Japanese ISUP
3-54
ExtNode component
5-5
3-55
L
F
least cost routing
FAS or NFAS over IP transport service, adding

FAS over IP transport service
FAS signaling service
FILES component
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
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
4-5, 4-15, 5-4
prov-cpy
4-3, 4-9
prov-dlt
MGC Info Subfields

MGCPPATH
prov-dply
A-1, A-94
MGCP IP links, adding
4-4, 4-10
prov-ed
3-86
3-64
MGCP signaling service
4-5
5-16, 5-17
4-5, 4-16, 4-18
prov-exp
4-5, 4-6
prov-rtrv
4-5, 4-30
MGC software
prov-sta
4-3, 4-7, 4-8, 4-9
starting
prov-stp
4-5, 4-11
MGW
4-1
prov-sync
2-2
ptcode
MGW control links

adding a card
rtlist
5-15
5-3
5-28
adding a FAS signaling service
5-11, 5-18, 5-19
rttrnk
adding a NAS signaling service
5-17
rttrnkgrp
adding an EISUP signaling service

adding an ethernet interface
adding an external node
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
tips for use
5-3, 5-8
card
5-10
ss7subsystem
5-16, 5-17
1-3
apc
5-48
5-11
ss7route
5-17
MGW control links, configuring
5-47
siprttrnkgrp
5-15
adding an MGCP signaling service

components to add
5-28
5-47
sippath
5-15
adding an IPFAS transport service

adding an IP link
5-28
siplnk
5-16
4-4
5-11
iplnk
5-17
lnkset
5-8
lnksetprop
nailed bearer trunk

nailed trunk
2-6
5-27
NAS Signaling Service
5-17
national network indicator
5-27
ipfaspath
5-16
network indicator
3-12
3-12
new provisioning session, starting
3-2
5-9
OL-1110-23
IN-3
Index
dual MGC configuration
IP route
OPC
2-2
4-10
A-8
single MGC configuration
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
SS7 MTP3 backhaul

peer port
3-87
point code
1-3, 4-16, 5-1
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
2-52, 2-55, 5-42
adding a C7 IP link
5-13
Properties
A-99
adding a card
properties
4-15
adding an ethernet interface
changing
4-18
property types
protocols
adding a TDM interface
4-18
3-28
protocol variants
4-31
5-14
components to add
5-12
SigSS7 component, adding
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
adding a TDM link
prov-add
prov-dlt
5-12
5-48
2-2
span
4-5, 4-6
E1
2-7
provisioning
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
adding bearer channels

adding flat files
3-31
SS7 sginaling routes

adding an SS7 signaling service
5-11
5-27
5-27
components to add
5-17, 5-26
configuring routes
5-28
SS7 Signaling Routes

adding a link set
5-8
SS7 signaling routes
5-2
adding a link set
5-8
U
unknown MGC
adding an adjacent point code

adding an SS7 route
5-10
adding a point code
5-3
adding a SS7 subsystem

SS7 signaling service
adding
V
5-9, 5-10
3-1
5-11
2-6, 5-9
starting a new provisioning session

STP
Voice Services Provisioning Tool
3-27
SS7 subsystem
Step 4
3-5
5-8
3-2
3-162
2-2
switched bearer trunk
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
trunk group and trunk files, importing
3-99
trunk groups
OL-1110-23
IN-5
Index
IN-6
OL-1110-23

Cisco PGW 2200

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Cisco PGW 2200

Hochgeladen von

Copyright:

Verfügbare Formate

Cisco PGW 2200 Softswitch Release 9

Provisioning Guide (through Release 9.7)

Text Part Number: OL-1110-23

About this Preface

Documentation Roadmap and Documentation Suite xxi

Cisco PGW 2200 Softswitch Provisioning

Cisco PGW 2200 Softswitch Provisioning Overview

Cisco PGW 2200 Softswitch Provisioning Rules

Cisco PGW 2200 Softswitch Provisioning Tools

Planning for Provisioning 2-1

Collecting Sessionset Data 2-4

Planning for the Media Gateway Signaling Service 2-38

Route Analysis 2-87

Provisioning with the Cisco Voice Services Provisioning Tool

Manual Provisioning with Cisco VSPT

Configuring the MGC 3-2

Configuring Signaling Services 3-7

Adding External Nodes 3-54

Trunk Group Properties 3-104

Backup and Restore 3-155

Provisioning the Cisco Billing and Measurements Server

Cisco BAMS Server Configuration 3-164

Working with MML

MML Configuration Commands

Working with MML Session Commands 4-6

Adding Components with MML

Adding SS7 Signaling Route Components 5-2

Cisco PGW 2200 Softswitch Point Code Storage

Adding Signaling Link Components 5-12

Adding DPNSS Supplementary Services

Adding Trunks, Trunk Groups, and Routing 5-26

Provisioning ATM Profiles 5-46

NOA Configurable Mapping 5-59

Adding SS7 Subsystems 5-64

Adding Location Labels 5-64

Provisioning Examples 5-77

CODEC Capabilities and DTMF Preferential Routing

Full Number Translations

Provisioning H.248 Protocol

Lawful Intercept 5-99

Location Mapping 5-101

Presentation Number Modification 5-109

SIP Remote Party ID and P-Asserted Support

SIP Service Handling and Feature Interworking Enhancement

Components and Properties

SS7 Signaling Service (sigpath) A-76

Protocol Variants A-100

About this Preface

Document Objective, page xvii

Audience, page xvii

Document Organization, page xviii

Document Conventions, page xix

Syntax Conventions, page xix

Documentation Roadmap and Documentation Suite, page xxi

Obtaining Documentation and Submitting a Service Request, page xxiii

Summary History of Document Changes, page xxiii

Telecommunications network operations

Data network operations

SS7 protocols, switching, and routing

Data network hardware

In addition, the following audiences may find this document useful:

Software and hardware installers

This chapter includes a checklist of tasks to perform

Planning for Provisioning