Cisco PGW 2200

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)February 25, 2010

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.

OL-1110-23

Collecting SS7 Collecting MGWCollecting LinksCollecting CiscoSignaling Service Data 2-3 Signaling Service Data 2-3C O N T E N T S

Preface xvii

About this Preface xvii

Document Objective xvii

Audience xvii

Document Organization xviii

Document Conventions xix

Syntax Conventions xix

Documentation Roadmap and Documentation Suite xxiDocumentation Roadmap xxiHardware Documentation xxiiSoftware Installation and Configuration Documentation xxiiGateway Documentation xxiiTerminology xxii

Obtaining Documentation and Submitting a Service Request xxiii

Summary History of Document Changes xxiii

C H A P T E R 1 Provisioning Overview 1-1

Before You Begin 1-1

Cisco PGW 2200 Softswitch Provisioning Overview 1-2

Cisco PGW 2200 Softswitch Provisioning 1-2

Cisco PGW 2200 Softswitch Provisioning Rules 1-3

Cisco PGW 2200 Softswitch Provisioning Tools 1-3

C H A P T E R 2 Planning for Provisioning 2-1Prerequisite Provisioning Information 2-1

Collecting External Device Addresses 2-2Collecting SS7 Point Code Data 2-2Collecting External Node Information 2-2Collecting Media Gateway Controller Interface Card Data 2-2iiiCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

et Data 2-3 ITP-L Data 2-4

ContentsCollecting Sessionset Data 2-4Collecting C7 IP Link Data 2-4Collecting IP Link Data 2-5Collecting SS7 Route Data 2-5Collecting SS7 Subsystem Data 2-6Collecting Trunk Data (Nailed) 2-6Collecting Trunk Data (Switched) 2-7Collecting QSIG/Q.931 Over BRI Backhaul Path Data 2-7Collecting Backhaul TCP Link Data 2-8Collecting IP Route Data 2-8Collecting IP FAS Path Data 2-8Collecting DPNSS Path Data 2-9Collecting M3UA Key Data 2-9Collecting M3UA Route Data 2-9Collecting D-Channel Data 2-10Collecting SCTP Association Data 2-10Collecting SS7 Signaling Gateway Process Data 2-11Collecting SS7 Signaling Service Data 2-11Collecting SUA Key Data 2-11Collecting SUA Route Data 2-12Collecting SIP Path Data 2-12

Planning SS7 Signaling Routes 2-12Planning Point Codes (SS7 Network Addresses) 2-13Planning Linksets 2-15Planning Linkset Properties 2-16Planning SS7 Subsystems 2-20Planning SS7 Routes 2-21Planning the SS7 Signaling Service 2-22Changing SS7 Signaling Service Properties 2-23

Planning SS7 Signaling Links 2-28Planning Network Cards for Cisco ITP-L Communications 2-29Planning Ethernet Interfaces for Cisco ITP-L Communications 2-30Planning TDM Interfaces for Cisco ITP-L Communications 2-31Planning A-Links Through Cisco ITP-Ls 2-32Planning F-Links through Cisco ITP-Ls 2-33Planning F-Links to Signaling Points 2-34Planning PRI Backhaul Links 2-34

Planning Media Gateway Control Links 2-34Planning Media Gateway External Nodes 2-34ivCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

ContentsPlanning for the Media Gateway Signaling Service 2-38Planning Network Cards for Media Gateway Communications 2-40Planning Ethernet Interfaces for Media Gateway Communications 2-40Planning IP Links 2-41Planning Backhaul TCP Link 2-43Planning QSIG/Q.931 Over BRI Backhaul Signaling Service 2-44Planning Session Sets 2-45Planning for D-Channels 2-47Planning for NOA Line Translation 2-48Provisioning Bearer Capability 2-49

Provisioning Trunk Groups and Trunks 2-50Provisioning Trunk Groups and Trunks Using MML Commands 2-50Provisioning Trunk Groups and Trunks Using an Imported File 2-50

Provisioning a Nailed Configuration 2-51Adding Nailed Trunks 2-51Configuring Profiles 2-52Attaching a Trunk Group Profile to a Trunk Group 2-52Configuring Signaling Service Profiles 2-55Configuring ATM Profiles 2-55

AtmConnectionType 2-55GWDefaultATMProfile 2-57

Creating the Trunk Group 2-58Populating a Trunk Group File 2-58Populating a Trunk File 2-86

Route Analysis 2-87Creating a Routing Trunk Group 2-87Provisioning a Routing Trunk Group Using MML Commands 2-87Associating a Route with a Trunk Group 2-89Weighted Trunk Group 2-89Creating a Route List 2-90An MML Example for Creating a Routing File 2-91

Planning for Session Initiation Protocol Provisioning 2-91

C H A P T E R 3 Provisioning with the Cisco Voice Services Provisioning Tool 3-1

Installing Cisco VSPT 3-1

Provisioning Cisco ITP-L 3-2

Manual Provisioning with Cisco VSPT 3-2

Configuring the MGC 3-2Adding a Cisco PGW 2200 Softswitch Host 3-3vCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

ContentsConfiguring Signaling Services 3-7Adding Point Codes 3-8

Adding Origination Point Codes 3-8Adding Adjacent Point Codes 3-10Adding Destination Point Codes 3-11

Adding Routing Keys 3-13Adding M3UA Routing Keys 3-13Adding SUA Routing Keys 3-14

Adding Location Labels 3-16Adding Linksets 3-17

Adding and Changing Linkset Properties 3-19Adding SS7 Subsystems 3-20

Adding SS7 Subsystems (Mating APCs) 3-21Adding SS7 Subsystems (AIN Services) 3-22

Adding ISUP Timer Profiles 3-23Adding an Inservice Subsystem 3-24Configuring SS7 Paths 3-27

Adding and Changing SS7 Properties 3-29Configuring SS7 Routes 3-30Configuring IPRoutes 3-32Configuring M3UA Routes 3-33Configuring SUA Routes 3-34Adding and Changing SS7 Signaling Properties 3-35Adding a Line Number Translation 3-36Adding Session Initiation Protocols 3-38

Configuring a DNS Parameter 3-38Adding a SIP Signaling Path 3-39Adding and Changing SIP Signaling Properties 3-40Adding a SIP IP Link 3-41

Configuring Automatic Congestion Control 3-43Configuring Advice of Charge 3-45

Configuring a Holiday 3-45Configuring a Charge 3-46Configuring a Tariff 3-47Configuring a Meter Tariff 3-48Configuring a Pritariff 3-49Configuring a Pricharge 3-51

Adding GTD Parameters 3-52Configuring TOS 3-53

Configuring Cisco MGW Control Links 3-53viCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

ContentsAdding External Nodes 3-54Configuring Cisco MGWs 3-55

Adding a Session Set 3-57Adding and Changing Session Set Properties 3-58

Adding an IPFAS Signaling Service 3-59Changing IPFAS Signaling Service Properties 3-63

Adding an MGCP Signaling Service 3-64Adding and Changing MGCP Signaling Service Properties 3-65

Adding a DPNSS Path 3-67Adding and Changing DPNSS Path Signaling Properties 3-68

Adding an H.248 Signaling Service 3-69Adding and Changing H248 Signaling Properties 3-69

Adding an EISUP Signaling Service 3-70Adding or Changing EISUP Signaling Properties 3-71

Adding an LIpath Signaling Service 3-72Adding or Changing LI Signaling Properties 3-73

Adding a NAS Signaling Service 3-74Adding and Changing NAS Signaling Properties 3-75

Adding a CTI Signaling Service 3-76Adding and Changing CTI Signaling Properties 3-77

Adding an SS7 SGP 3-78Adding a TCPLNK 3-79

Adding and Changing Tcplnk Properties 3-80Adding a BRI Signaling Service 3-81Adding a RAPATH 3-84Adding a RASERVER for RAPATH 3-84Configuring IP Links 3-86Adding IP Links for MGCP 3-86Adding IP Links for H248 3-87Adding IP Links for EISUP 3-89Adding IP Links for LI 3-90Adding IP Links for NAS 3-91Adding C7 IP Links 3-93Adding an ASSOCIATION 3-94Adding a CTI Manager 3-95Adding an AXL Server 3-96

Configuring Bearer Traffic 3-97Importing Trunk Groups and Trunks 3-99Adding a Trunk Group Profile 3-101Adding Trunk Groups 3-102viiCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

ContentsTrunk Group Properties 3-104Adding Trunks 3-139

Deleting Trunks from a Trunk Group 3-142Adding a CodecString 3-143Adding a BearerCap 3-145Adding an ATMProfile 3-146Adding Routes 3-147

Adding Route Lists 3-148Hierarchical View of Provisioned Components 3-149

Performing an Integrity Check 3-150Checking Integrity for an MGC Signaling Configuration 3-150Checking Traffic Against an MGC Configuration 3-151

Viewing Generated MML Commands 3-153

Deploying a New Configuration 3-153

Backup and Restore 3-155Schedule a Backup or Restore 3-156

Check Status of Backup or Restore 3-159

Provisioning the Cisco Billing and Measurements Server 3-160

Starting a Cisco BAMS Provisioning Session 3-162

Cisco BAMS Server Configuration 3-164Provisioning General BAMS Information 3-165Provisioning Zones 3-169Provisioning Trunk Group Information 3-175Provisioning Measurements 3-178Provisioning Other 3-180

Provisioning ALM-PARMS 3-180Provisioning NODE-PARMS 3-181Provisioning POLL 3-182Provisioning SKIPCDB 3-183Provisioning SKIPCDE 3-184Provisioning P01FILTER 3-186Provisioning SWITCHINFO 3-186Provisioning BIN1110 3-187

Provisioning System 3-188Provisioning MSC-PARMS 3-189Provisioning MSC-THRES 3-190Provisioning SYS-ALM-PARMS 3-191viiiCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

ContentsC H A P T E R 4 MML Basics 4-1

Working with MML 4-1

MML Configuration Commands 4-3

Working with MML Session Commands 4-6Starting a Provisioning Session 4-6Creating a New Provisioning Configuration 4-7Overwriting an Existing Inactive Configuration 4-8Modifying and Activating a Configuration 4-8Modifying an Existing Configuration and Saving It as Another Version 4-9Committing a Provisioning Session to a Single Cisco PGW 2200 Softswitch 4-9Deploying a Provisioning Session to Dual MGCs 4-10Synchronizing Configuration Data 4-10Stopping a Configuration Session 4-11Performing a Manual Switchover 4-12Exporting Configuration Data 4-12Importing Saved MML Configuration Data 4-13

Working with Provisioning Commands 4-15Adding a Component 4-15Modifying a Component 4-16Deleting a Component 4-17Overriding Component Properties 4-17Changing Overridden Properties 4-18Retrieving All Components 4-29Retrieving All Components of a Specific Type 4-30Retrieving an Individual Component 4-30Retrieving a Component Based on Signaling Service 4-30Retrieving Protocol Variants 4-31Retrieving Provisioning Session Information 4-33Creating a Batch File 4-33Executing a Batch File 4-34

C H A P T E R 5 Adding Components with MML 5-1

Adding SS7 Signaling Route Components 5-2Adding a Destination Point Code 5-3Adding Multiple OPCs 5-4Understanding Point Code Addressing 5-5

14-Bit Address (ITU) 5-616-Bit Address (Japan) 5-724-Bit Address (ANSI and China) 5-7ixCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

ContentsCisco PGW 2200 Softswitch Point Code Storage 5-8Adding an Adjacent Point Code 5-8Adding a Linkset 5-8Adding a Linkset Property 5-9Adding an SS7 Subsystem 5-9Adding Subsystem Numbers 5-10Adding an SS7 Route 5-10Adding an SS7 Signaling Service 5-11Adding a FAS Signaling Service 5-11

Adding Signaling Link Components 5-12Adding an Interface Card 5-12Adding an Ethernet Interface 5-12Adding a C7 IP Link 5-13Adding a TDM Interface 5-14Adding a TDM Link 5-14

Adding Media Gateway Control Links 5-14Adding an External Node 5-15Adding a Card 5-15Adding an Ethernet Interface 5-15Adding an E-ISUP Signaling Service 5-16Adding an IPFAS Transport Service 5-16Adding an MGCP Signaling Service 5-16Modifying an MGCP Signaling Service Property 5-17Adding a NAS Signaling Service 5-17Adding an IP Link 5-17Adding a Session Set 5-18Adding D-channels 5-19Adding ISDN BRI Backhaul Connections 5-19Adding IUA Connections 5-21

Verifying Next Hop Parameter Configuration 5-21Adding Cisco Access Server External Nodes 5-22Adding NAS Signaling Services 5-22Adding IP Routes (Optional) 5-22Adding SCTP Associations 5-23

Adding DPNSS Connections 5-23Verifying Next Hop Parameter Configuration 5-24Adding Cisco Access Server External Nodes 5-24Adding IP Routes (Optional) 5-25Adding SCTP Associations 5-25Adding DPNSS Signaling Services 5-26xCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

ContentsAdding DPNSS Supplementary Services 5-26

Adding Trunks, Trunk Groups, and Routing 5-26Adding Files 5-27Adding a Nailed Trunk (Bearer Channel) 5-27Adding a Trunk Group 5-27Adding Mapping to Multiple Trunk Groups 5-28Routing 5-28Provisioning Reserving Incoming Bandwidth 5-28Provisioning Bearer Capability 5-29Provisioning Least Cost Routing 5-30Overriding the Trunk Group Property 5-32Enabling Overdecadic 32 Digit Operation 5-32

Provisioning the Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping Feature 5-35Verifying the Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping Feature 5-36

Provisioning SUBSCRIBE/NOTIFY Methods 5-36Enabling SUBSCRIBE/NOTIFY Methods 5-36Disabling SUBSCRIBE/NOTIFY Methods 5-37

Provisioning Unsolicited Notifications 5-37Enabling Unsolicited Notifications 5-37Disabling Unsolicited Notifications 5-38

Provisioning Subscription Duration 5-38Provisioning Minimum Subscription Duration for Telephony Event 5-38Provisioning Maximum Duration for SUBSCRIBE 5-39

Enabling/Disabling Information Extraction from SDP 5-39Enabling Support of Information Extraction from Sockets Direct Protocol (SDP) 5-39Disabling Support of Information Extraction from SDP 5-39

Adding a Switched Trunk (Multiple Switched Trunks) 5-40Retrieving Multiple Switched Trunks 5-40Adding Multiple Nailed Trunks 5-41Retrieving Multiple Nailed Trunks 5-41Adding Multiple Trunk Groups and Bearer Channels 5-41Removing Multiple Trunk Groups and Bearer Channels 5-42Creating a Profile 5-42Adding a Trunk Group Profile 5-42Deleting a Trunk Group Profile 5-42Adding an ISUP Timer Profile 5-43Suppressing Caller ID in a SIP Environment 5-43Adding an ATM Profile 5-45xiCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

ContentsProvisioning ATM Profiles 5-46Provisioning ATM Profiles Result Types 5-46Provisioning Trunk Group Properties 5-46Provisioning SigPath Properties 5-46

Adding SIP Components 5-46Adding a SIP Signaling Service 5-47Adding a SIP Signaling Link 5-47Adding a SIP Trunk Group 5-47Adding SIP Trunk Group Properties 5-47Adding Mapping to Multiple IP Trunks 5-48Adding SIP Routing Trunk Group Properties 5-48Adding SIP Domain Name System Properties 5-48Modifying a SIP Signaling Service 5-49Modifying Session Timers 5-50

Modifying Session Timer for Incoming SIP Trunk Groups 5-50Modifying Session Timer for Outgoing SIP Trunk Groups 5-50

Adding Dual Presentation CLI 5-50Adding Automatic Switchover Using Dual-VLAN 5-50

Verifying Parameter Settings and Re-configuring Cisco PGW 2200 Softswitch Software 5-51Enabling SIP Automatic Switchover Using Dual-VLAN 5-52Disabling SIP Automatic Switchover Using Dual-VLAN 5-53

Adding SIP-T and SIP-GTD Support 5-55Adding SIP-T and SIP-GTD Support 5-55Enabling the Early Backward ISUP Message 5-56

GTD NOA Override 5-56GTD Provisioning Examples 5-59

NOA Configurable Mapping 5-59Provisioning the NOA Configurable Mapping Feature 5-60

Adding an NOA Value to the LineXlate File for Inbound Calls 5-61Deleting an NOA Value from the LineXlate File 5-61Adding an NOA Value to the LineXlate File for Outbound Calls 5-61Deleting an NOA Value from the LineXlate File 5-62Validation Rules 5-62

Adding M3UA and SUA Connections 5-62Adding a Cisco ITP External Node 5-63Adding Point Codes (OPC, DPC, and APC) 5-63Adding M3UA and SUA Routing Keys 5-63Adding SS7 Signaling Services 5-63Adding M3UA and SUA Routes 5-64xiiCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

ContentsAdding SS7 Subsystems 5-64Adding M3UA and SUA Signaling Gateway Processes 5-64Adding IP Routes (optional) 5-64Adding SCTP Associations 5-64

Adding Location Labels 5-64Adding Location Labels to Trunk Groups and Sigpaths 5-65Applying Call Limiting Over DPNSS 5-67Applying Call Limiting to Incoming and Outgoing Trunk Groups 5-68B-number Based Call Limiting Scenario 5-69Applying Call Limiting to a SIP Trunk Group 5-70Applying Call Limiting to an H.323 Trunk Group 5-70Applying Call Limiting to the DPNSS Trunk Groups 5-71Applying Call Limiting to an SS7 ISUP Trunk Group 5-71Applying Call Limiting to Digit Strings in a Dial Plan 5-72Applying Call Limiting to Multiple Trunk Groups 5-72Applying Call Limiting to IP Addresses 5-72Applying Call Limiting to an MGCP Gateway 5-73Playing an Announcement when the Call Limiting Threshold is Exceeded 5-73

Scaling System Components 5-74Dynamically Configuring the Input/Output Channel Controller 5-74

Provisioning Examples 5-77Configuring Two IP Addresses on the MGW to One IP Address on a NAS 5-77

A-number Country Code Digit Removal 5-82

Call Reporting 5-82

CODEC Capabilities and DTMF Preferential Routing 5-83

Digit Buffering for International Gateways 5-84

DPNSS Service Interworking with Cisco CallManager Over QSIG Tunneling 5-84Provisioning Route Optimization Transit 5-85Provisioning Route Optimization Initiated by the Cisco PGW 2200 Softswitch 5-87Provisioning Route Optimization Responded by the Cisco PGW 2200 Softswitch 5-89Provisioning Call Completion 5-89Provisioning Message Waiting Indicator (with no QSIG Tunneling) 5-90Provisioning Message Waiting Indicator (with QSIG Tunneling) 5-92Provisioning a Customer VPN ID in a Trunk Group 5-93Provisioning a Customer VPN ID in the Dial Plan 5-93Provisioning Feature Transparency on QSIG Trunk Groups or sigPaths 5-94Provisioning 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-95xiiiCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

ContentsFull Number Translations 5-96

Global Titles 5-96

Provisioning H.248 Protocol 5-96

Lawful Intercept 5-99Provisioning LI for the Service Provider 5-100Provisioning a Wiretap Entry for the Medication Device 5-101

Location Mapping 5-101Provisioning Location Values 5-102Provisioning Internal Cause Value Mapping 5-103Provisioning Cause Value Mapping 5-103

Cause Value Mapping Based on Received Cause and Location Values 5-103Cause and Location Value Mapping to Different Values 5-104Cause Value Mapping to Different Cause and Location Values 5-104

Multiple Inbound IP Trunks 5-105Creating a New Inbound SIP Trunk 5-105Creating a New Inbound ISUP Trunk 5-107

Support of HSI Non-RAS Mode 5-107Provisioning Cisco PGW 2200 Softswitch 5-108Provisioning Cisco HSI 5-108

Presentation Number Modification 5-109Provisioning PN Modification for PSTN to SIP Calls 5-109Provisioning PN Modification for PSTN to SIP Calls 5-110

RADIUS Enhancement for Accounting 5-111

SIP and ISUP Interworking for Call Hold and Terminal Portability 5-112

SIP Overlap Signaling 5-112

SIP Remote Party ID and P-Asserted Support 5-113

SIP Service Handling and Feature Interworking Enhancement 5-115

Take Back and Transfer 5-116

QoS for Signaling Traffic 5-118

A P P E N D I X A Components and Properties A-1

Components A-1Network Element Components A-1

Adapter Card A-2Adjacent Point Code A-2Association A-3AXL Server A-7ISDN BRI Signaling Service A-8xivCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

ContentsC7 IP Link A-9Charge A-10Charge Holiday A-10CTI Manager A-11CTI Path A-12Destination Point Code A-13D Channel A-13DNS Parameters A-14DPNSS Signaling Service A-15EISUP Signaling Service (sigpath) A-16Ethernet Interface A-17External Node A-18FAS Signaling Service (sigpath) A-19Files A-19Intelligent Network Service (INSERVICE) Table A-20IPFAS Transport Service (previously PRI Signaling Backhaul) A-21IPINMAPPING A-22IP Link A-23IP Route A-25LABEL A-26LineXlate A-27Linkset A-28Linkset Property A-28M3UA Key A-33M3UA Route A-34MGCP Signaling Service A-35Multiple IPFAS Services (sigpath) A-35Multiple Trunk Groups and Trunks A-36Nailed Trunk (Bearer Channel) A-39NAS Signaling Service (sigpath) A-40Originating Point Code A-41Profile A-42RASERVER A-59Routing A-60Session Set A-64SGP A-66SIP IP Link A-66SIP Signaling Service A-67SS7 Route A-68SS7 Signaling Service Properties A-68xvCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

ContentsSS7 Signaling Service (sigpath) A-76SS7 Subsystem A-76SUA Key A-78SS7 Signaling Gateway Process A-80Switched Trunk Provisioning A-80TARIFF A-81Backhaul TCP Link A-81TDM Interface A-82TDM Link A-83Trunk Group Provisioning A-84Trunk Group Profile MML Provisioning A-85GTD Parameter Provisioning A-86

Dial Plan Provisioning Components A-94

Processes A-98

Properties A-99

Protocol Variants A-100Software Release 9.3(2) Protocol Variants A-100Software Release 9.4(1) Protocol Variants A-103Software Release 9.5(2) Protocol Variants A-106Software Release 9.6(1) Protocol Variants A-109

A P P E N D I X B Planning Worksheets B-1

I N D E XxviCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Preface

Revised: February 25, 2010, OL-1110-23

About this PrefaceThis 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 ObjectiveThis 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.

AudienceThe primary audience for this document is network operators and administrators who have experience xviiCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

in the following areas: Telecommunications network operations Data network operations

SS7 protocols, switching, and routing

Preface

Telecommunications hardware

Data network hardwareIn addition, the following audiences may find this document useful: Software and hardware installers Network designers

Document OrganizationThis document contains the chapters listed in Table 1.

Table 1 Document Organization

Chapter Title Description

Chapter 1 Provisioning Overview 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: Before You Begin Cisco PGW 2200 Softswitch Provisioning

Overview Cisco PGW 2200 Softswitch Provisioning Cisco PGW 2200 Softswitch Provisioning Tools

Chapter 2 Planning for Provisioning 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

MMLThis chapter describes how to use MML commands to add system components.

Appendix A Components and Properties This appendix lists the component names and properties.

Appendix B Planning Worksheets This appendix contains worksheets to use for provisioning.xviiiCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

PrefaceDocument 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 ConventionsIn 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 interfaceYou 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.xixCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Preface

Table 2 Conventions (continued)Conventions used in the Cisco PGW 2200 Softswitch system (such as in MML commands) are shown in Table 3.

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

command [ abc { def | ghi } ]You have three options:

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

Convention Meaning Description / CommentsxxCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

PrefaceHexadecimal and integer fields in files may have different widths (number of characters) for column alignment.

Documentation Roadmap and Documentation SuiteConsult 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 RoadmapYou can find the Cisco PGW 2200 Softswitch Documentation Map at the following URL:

Table 3 Data Types

Data Type Definition Example

Integer A series of decimal digits from the set of 0 through 9 that represents a positive integer. An integer may have one or more leading zero digits (0) added to the left side to align the columns. Leading zeros are always valid as long as the number of digits is less than or equal to ten digits. Values of this type have a range of zero through 4294967295.

1230001234200000000

Signed integer

This data type has the same basic format as the integer but can be either positive or negative. When negative, it is preceded by the sign character (-). As with the integer data type, this data type can be as many as ten digits in length, not including the sign character. The value of this type has a range of 0 minus 2147483647 through 2147483647.

123-000123-2100000000l

Hexadecimal A series of 16-based digits from the set of 0 through 9, a through f, or A through F. The hexadecimal number may have one or more leading zeros (0) added to the left side. For all hexadecimal values, the maximum size is 0xffffffff (eight hexadecimal digits).

1f301f3000

Text A series of alphanumeric characters from the ASCII character set, where defined. Tab, space, and double 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.

EntityIDLineSES_Threshold999

String A series of alphanumeric characters and white-space characters. A string is surrounded by double quotes ( ). 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.

This is a descriptive string.xxiCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

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 PGW 2200 Softswitch Release 9 Provisioning 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 DocumentationCisco DAS and H.323 VoIP Gateway Installation and Configuration Guide

TerminologyThe 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.xxiiCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

PrefaceObtaining Documentation and Submitting a Service RequestFor 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 athttp://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.htmlSubscribe 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.

Summary History of Document ChangesTable 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 Summary History of Document Changes

SubjectDocument Number and Change Date Change Summary

Provisioning procedures for PGW-to-ITP routing with MAP query

OL-1110-23, February 25, 2010 Added the Optimizing PGW-to-ITP Routing with MAP Query section on page 64 in Chapter 5, Adding Components with MML.

Provisioning procedures for features

OL-1110-22, January 29, 2010 Added provisioning procedures for features in Release 9.7(3) in Chapter 5, Adding Components with MML.

Replaced property tables with a reference to another book

OL-1110-21, December 17, 2009 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 a property

OL-1110-19, October 2, 2009 Inserted an additional acceptable value (2) for the UnsolicitedNotifyMethod property. (Modified Table 2-30, Table 3-16, Table A-68, Table A-69).xxiiiCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Preface

Table 4 Summary History of Document Changes (continued)Added clarifications OL-1110-18, August 25, 2009 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.


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.

SubjectDocument Number and Change Date Change Summary xxivCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Preface

Table 4 Summary History of Document Changes (continued)Added feature information

OL-1110-14, February, 2009 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.


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.

Updated for Release 9.7

OL-1110-13, November, 2007 Added new information for Release 9.7 features.

SubjectDocument Number and Change Date Change Summary xxvCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Preface


OL-1110-12, October, 2007 Modified CDR 4239, added CDR 4065 for Redirect Server feature.


OL-1110-12, October, 2007 Added the following properties for the SIP Loose Routing feature: *.sipEgressRoutingControl *.sipIngressRoutingControl


OL-1110-12 June 27, 2007 Added the *.ItpActionRequest property for the Optimize Routing with MAP Query feature.


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.


OL-1110-10 June 28, 2004 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.

SubjectDocument Number and Change Date Change Summary xxviCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Preface


OL-1110-10 June 28, 2004 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


OL-1110-09 October 30, 2003 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

SubjectDocument Number and Change Date Change Summary xxviiCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Preface

Table 4 Summary History of Document Changes (continued)Added text for property changes

OL-1110-08 March 30, 2003 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.


OL-1110-07 December 9, 2002 Added variable ISUP timers. Added software Release 9.3(2) information. Revised property information.


OL-1110-06 September 19, 2002 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. Added software Release 9.3(1) information. Removed obsoleted MML commands (SGCPPATH,

CASPATH, and TCAPIPPATH).Provisioning changes OL-1110-05 March 22, 2002 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.

SubjectDocument Number and Change Date Change Summary xxviiiCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Preface

Table 4 Summary History of Document Changes (continued)Provisioning rules

MML names re-ordered for routing

Parameter values

OL-1089-02, December 3, 2001 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.

OL-1110-01, October 16, 2001 Initial release

SubjectDocument Number and Change Date Change Summary xxixCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Preface xxxCisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Cisco PGW 2200 Softswitch OL-1110-23C H A P T E R 1Provisioning Overview


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-3The 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 BeginYou 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 Guide1-1Release 9 Provisioning Guide (through Release 9.7)

Chapter 1 Provisioning Overview Cisco PGW 2200 Softswitch Provisioning OverviewCisco PGW 2200 Softswitch Provisioning OverviewAll 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

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 gatewaysYou establish these connections by specifying parameter values for each of the entities illustrated in Figure 1-1 (Cisco PGW 2200 Softswitch hosts, ITP-Ls, STPs, media gateways, and all their associated links).

Cisco PGW 2200 Softswitch ProvisioningProvisioning 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

3306

6

Controlsignalingnetwork

Cisco PGW 2200Softswitch

CiscoPGW 2200Softswitch

Media gateway

Cisco ITP-Ls

Mediagateway

SS7

STP

Cisco ITP-Ls

QoS packetnetwork

V

PSTN

Controlsignalingnetwork

STP

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

OL-1110-23

Chapter 1 Provisioning Overview Cisco PGW 2200 Softswitch Provisioning Rules

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)

Cisco PGW 2200 Softswitch Provisioning RulesWhen 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.

Cisco PGW 2200 Softswitch Provisioning ToolsThe 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.1-3Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Chapter 1 Provisioning Overview Cisco PGW 2200 Softswitch Provisioning ToolsNote 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-4Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Chapter 1 Provisioning Overview Cisco PGW 2200 Softswitch Provisioning Tools

Figure 1-2 Sample Cisco Voice Services Provisioning Tool WindowYou 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=trueopcprov-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=1prov-add:apc:name="apc2",netaddr="777.333.333",desc="STP 2 APC pointcode",netind=2prov-add:apc:name="apc3",netaddr="888.777.777",desc="STP 3 APC pointcode",netind=3prov-stp1-5Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Chapter 1 Provisioning Overview Cisco PGW 2200 Softswitch Provisioning ToolsNote 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.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.

Runs on the Cisco PGW 2200 Softswitch host server.

Batch File Support No YesBest Used For Setting up a single configuration

or few configurations on individual machines.

Modifying an existing configuration.

Creating batch files to configure many Cisco PGW 2200 Softswitch servers or to retrieve measurements.

Modifying configurations. Scaling large configurations. Troubleshooting.1-6Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Cisco PGW 2200 Softswitch OL-1110-23

External nodes Media gateway controller interface card infor Trunk identification datamationC H A P T E R 2Planning for Provisioning


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 InformationBefore you can complete the provisioning planning tables in this chapter, you must collect the following information:

Device addresses SS7 point codes2-1Release 9 Provisioning Guide (through Release 9.7)

Chapter 2 Planning for Provisioning 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 numberTable 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-2Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Chapter 2 Planning for ProvisioningNote The CARD component is not supported in software Release 9.4(1).

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

SideThis 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

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 required for Ethernet cards.)

Used for connections to Cisco ITP-Ls and MGWs. 2-3Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Chapter 2 Planning for Provisioning

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 addressThis 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: Description2-4Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23


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 maskThis 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 OPCThis SS7 route information can be listed in Table B-12.2-5Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Chapter 2 Planning for Provisioning 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 numberThe 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 sizeTo 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-6Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23


(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 sizeTo 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

Component description 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 table2-7Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23


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

Component description Destination hostname or IP address Subnet mask of Destination (optional) Next hop router IP address Local IP address PriorityThe 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

Component description2-8Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23


MML name of the associated external node

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 Component description MML name of the associated external node 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 Component description 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 Component description Associated DPC Associated external node2-9Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23


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

Description of this component 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 subunitD-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 Description of this component

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-10Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23


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 Component description External node that is running the SS7 signaling gateway processThe 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: Unique ID of this component and component name used in MML commands Component description MDO file name Destination point code MML name Customer group ID M3UA Routing key ID MML nameThe 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 Component description Associated OPC Associated APC (optional)2-11Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23

Chapter 2 Planning for Provisioning Planning SS7 Signaling Routes

Associated local SSN

Routing context value Network appearance (optional)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 Component description Associated APC Associated external node Associated OPC Associated remote SSNThe 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: Unique ID of this component and component name used in MML commands Component description Local port number Priority Local logical IP address Signaling service supportedThe SIP path component structure is shown in Table B-40.

Planning SS7 Signaling RoutesTo 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-12Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23


Figure 2-1 SS7 Signaling Route Configuration ComponentsFigure 2-2 SS7 Signaling Route Component Hierarchy

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:

3306

7

Route A

Destinationpointcode

(DPC)

Route ALinkset

Media gatewaycontroller

Virtual switch zone

SS7signalingservice

External switch

Originationpointcode

(OPC)

3306

8

OPCDPC

SS7signalingservice

SS7signalingserviceproperties

Linkset

Linksetproperties

SS7 route2-13Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)

OL-1110-23


Cisco PGW 2200 SoftswitchWithin the Cisco MGC software, the Cisco PGW 2200 Softswitch

point code is called the OPC. Use Table B-4 to plan the OPC configuration for your Cisco PGW 2200 Softswitch.

STPWithin the Cisco PGW 2200 Softswitch software, the point code for each STP with which the controller communicates is called the APC. Use Table B-7 to plan the APCs for your Cisco PGW 2200 Softswitch.

Destination switchWithin the Cisco PGW 2200 Softswitch, a remote devices point code is called a DPC. You need a point code for each remote switch with which the MGC node will communicate. Use Table B-5 to plan the DPCs for your Cisco PGW 2200 Softswitch.

When configuring a Cisco PGW 2200 Softswitch, you must enter a point code and a point code type for each Cisco PGW 2200 Softswitch, along with the network address and the network indicator. The point code type is OPC and the point code address is a value in the form of x.x.x. For example, 8.232.72. The two periods separating the three numeric labels are required, and the numeric labels must be entered in decimal values. If your service provider issues these numbers using binary or hexadecimal values, you must convert them to decimal.

Note The point code examples used in this document follow the ANSI SS7 (8bits.8bits.8bits) point code format. However, the Cisco PGW 2200 Softswitch can also support ITU point codes.

For configuring point codes for remote switches, the point code type is DPC. Each point code for an STP is an APC, and the STP point code type is APC. The point code values for DPCs and APCs use the same format (x.x.x) as for OPCs.To define SS7 network addresses, use the following components: VSPT name: Originating Poi

Documents

Cisco PGW 2200