CH A P T E R
1
Planning for Provisioning
Revised: February 25, 2010, OL-1110-23
This chapter describes how to plan for your system provisioning.
This chapter includes the following sections:
•
Planning SS7 Signaling Routes, page 1-12
•
Planning SS7 Signaling Links, page 1-28
•
Planning Media Gateway Control Links, page 1-34
•
Route Analysis, page 1-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
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-1
Chapter 1
Note
Planning for Provisioning
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 1-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 1-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 1-1. Table 1-2 serves as a form you can use to record Ethernet interface card information.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-2
OL-1110-23
Chapter 1
Planning for Provisioning
Note
The CARD component is not supported in software Release 9.4(1).
Table 1-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 1-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 1-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
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-3
Chapter 1
•
Protocol (SS7-ANSI, SS7-China, SS7-ITU, SS7-Japan, or SS7-UK)
•
IP transport type
Planning for Provisioning
This linkset information can be listed in Table 1-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 1-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 1-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
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-4
OL-1110-23
Chapter 1
Planning for Provisioning
•
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 1-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 1-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 1-12.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-5
Chapter 1
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 number
The SS7 subsystem component structure is shown in Table 1-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 1-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
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-6
OL-1110-23
Chapter 1
Planning for Provisioning
(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 1-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 1-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 1-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 table
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-7
Chapter 1
•
Planning for Provisioning
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 1-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 1-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
•
Priority
The IP route component information can be listed in Table 1-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 description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-8
OL-1110-23
Chapter 1
Planning for Provisioning
•
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 1-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 1-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 1-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 node
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-9
Chapter 1
•
Planning for Provisioning
Associated OPC
The M3UA route component information can be listed in Table 1-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 subunit
D-channel component information can be listed in Table 1-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)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-10
OL-1110-23
Chapter 1
Planning for Provisioning
•
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 1-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 process
The SS7 signaling gateway process component structure is shown in Table 1-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 name
The SS7 signaling service component structure is shown in Table 1-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)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-11
Chapter 1
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 1-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 SSN
The SUA route component structure is shown in Table 1-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 supported
The SIP path component structure is shown in Table 1-40.
Planning SS7 Signaling Routes
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 1-1 shows the relationship of these components. Figure 1-2 shows the order in which these
components are to be configured.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-12
OL-1110-23
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Routes
Figure 1-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 1-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 1-2) before deploying a configuration.
Note
For properties not described in this chapter, refer to Appendix 1, “Components, Processes, 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 1-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:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-13
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Routes
•
Cisco PGW 2200 Softswitch—Within the Cisco MGC software, the Cisco PGW 2200 Softswitch
point code is called the OPC. Use Table 1-4 to plan the OPC configuration for your
Cisco PGW 2200 Softswitch.
•
STP—Within the Cisco PGW 2200 Softswitch software, the point code for each STP with which the
controller communicates is called the APC. Use Table 1-7 to plan the APCs for your
Cisco PGW 2200 Softswitch.
•
Destination switch—Within the Cisco PGW 2200 Softswitch, a remote device’s point code is called
a DPC. You need a point code for each remote switch with which the MGC node will communicate.
Use Table 1-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 1-6
•
VSPT name: Destination Point Code
•
MML name: DPC Table 1-5
•
VSPT name: Adjacent Point Code
•
MML name: APC Table 1-7
Table 1-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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-14
OL-1110-23
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Routes
Table 1-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
Cisco PGW 2200 Softswitch.
TRUEOPC
True OPC
MML name of the true OPC with which the capability OPC is associated. The MML name
of previously defined true OPC. It only applies to the capability OPC.
Planning Linksets
After you determine the point codes for your network devices, you must define the linksets that connect
each MGC node directly to a remote switch or indirectly to the remote switch through an STP. A linkset
is the group of all communication links connecting an MGC node to a specific SSP or STP. When two
STPs are defined as mates within the Cisco PGW 2200 Softswitch, the Cisco PGW 2200 Softswitch can
use either linkset to connect to the SS7 signaling network.
Table 1-3 lists the configuration parameters you define for each linkset during provisioning. Table 1-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 1-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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-15
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Routes
Table 1-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 1-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 1-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
5
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-16
OL-1110-23
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Routes
Table 1-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.
This property is removed in software Revision 9.3(1) and
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).
This property is removed in software Revision 9.3(1) and
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
property is removed in software Revision 9.3(1) and later.
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).
This property is removed in software Revision 9.3(1) and
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
Revision 9.3(1) and later.
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
removed in software Revision 9.3(1) and later.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-17
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Routes
Table 1-4
Linkset Property Descriptions (continued)
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
Waiting to repeat local inhibit test.
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.
Value range: 60 through 65 seconds.
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.
Value range: 0 through 90 seconds.
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-18
OL-1110-23
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Routes
Table 1-4
Linkset Property Descriptions (continued)
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.
Value range: 1 through 20 seconds.
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
3
The maximum number for Retransmission count.
Value range: 1 through 100.
rudpWindowSz
32
The maximum number for Unacknowledged Segments in the
RUDP window.
Value range: 2 through 64.
rudpRetxTimer
3
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
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-19
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Routes
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 1-5 lists the
configuration parameters you define for each SS7 subsystem during provisioning. Table 1-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 1-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
enclose in straight quotes. Hyphens (-) can be used.
DESC
Description
Text description of this component. Enter as many as 128 characters and enclose in
straight quotes.
LOCALSSN
Local SSN
Subsystem number. Enter an integer from 0 to 255. When mating STPs, SSN = 0. When
using Intelligent Network (IN) services, SS7-ANSI, SS7-ETSI, or SS7-ITU, Local SSN
can be set to a value greater than 0.
Default = 0.
MATEDAPC
Mated
adjacent
point code
Adjacent point code for an STP mate. Enter the MML name of previously defined APC.
Only used when mating STPs, not when creating AIN subsystems.
OPC
Originating
PC
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-20
OL-1110-23
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Routes
Table 1-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 1-6 describes the configuration parameters you use to define routes during
provisioning. Table 1-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
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-21
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Routes
Table 1-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 1-7 describes each of
the SS7 signaling service parameters and provides space for you to plan the configuration of one service.
Table 1-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 1-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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-22
OL-1110-23
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Routes
Table 1-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 1-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 1-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
1
Set to 0 to disable both way release / circuit free handling for BTNUP
protocol. Value range: 0 or 1.
CGBA2
0
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-23
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Routes
Table 1-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
0
Sets the Calling Line Identity Presentation Essential operation. 0—Do
not request CLI., 1—Request CLI if not already provided and drop the
call if CLI is not provided, or 2—Request 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
0
Statistical COT. Value range: 0 through 100%.
dialogRange
0
TCAP transaction ID range (for example, 1 through 10000) for a specific
subsystem.
0 = entire range.
ForwardCLIinIAM
0
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
1
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.
Value range: 0 or 1.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-24
OL-1110-23
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Routes
Table 1-8
SS7 Signaling Service Property Descriptions (continued)
MML Parameter Name
Default Value
Description
GLARE
0
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
0
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.
Value range: 0 or 1.
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-25
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Routes
Table 1-8
SS7 Signaling Service Property Descriptions (continued)
MML Parameter Name
Default Value
Description
hopCount
1
Default hop count. Value range: 0 or 15 (this indicates the maximum
number of hops allowed for SCCP messages).
layerRetries
2
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.
Value range: 0 through 272.
NatureOfAddrHandling
0
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.
Value range: 0 through 127.
This property is added in software Release 9.5(2).
Normalization
0
Normalization of dialed number to unknown. Set to 0 for disabled and 1
for enabled. Value range: 0 or 1.
OD32DigitSupport
0
Allows 32 digits and overdecadic digits support for the ANSI, Q.761,
and Q.767 protocol variants for the ANSI, SS7-ITU, SS7-China,
SS7-Japan, and SS7-UK protocol families. Values are: 0 (disabled) and
1 (enabled).
This property is added in software Release 9.4(1).
OMaxDigits
24
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
0
Specifies minimum number of digits to receive for overlap digit
processing for call origination from this traffic path.
Value range: 0 through system maximum.
OmitCgPnFromUnavailabl
e
0
Determines if mapping between the SIP From header to the IAM calling
party number is enabled when the SIP message header From is
“unavailable”. Values are: 0 (enabled) or 1 (disabled).
This property is added in software Release 9.5(2).
OOverlap
0
Set to 1 to enable overlap signaling for call origination from this traffic
path.
Value range: 0 through system maximum.
OverlapDigitTime
6
Overlap interdigit timer. The time to wait for the rest of the digits.
Value range: 0 through 60.
Note
If OverlapDigitTimeValue timer is set to more than 30 seconds,
other timers expire before this timer.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-26
OL-1110-23
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Routes
Table 1-8
SS7 Signaling Service Property Descriptions (continued)
MML Parameter Name
Default Value
Description
OwnClli
na
Specifies the common language location identifier (CLLI). This can be
up to 11 alphanumerical digits.
RedirMax
5
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:
1–5:
•
OCC—Allow the specified number (1–5) of redirections before the
call is force-released.
•
TCC—Reset the redirect counter to 5 if it is < 1 or > 5.
0:
•
OCC—Allow the redirection counter to have any value from 1 to 7.
•
TCC—If the redirection counter is set to a value 0–7, 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.
0 = Disabled, 10 = 1 second.
RoutePref
0
Determines the preferred route. Value range: 0 through 9.
0 = No Preference (default)
SdpXmitToH323Trigger
0
5= IP Preferred
1 = ATM Essential
6 = IP Excluded
2 = ATM Preferred
7 = TDM Essential
3 = ATM Excluded
8 = TDM Preferred
4 = IP Essential
9 = TDM Excluded
Indicates the point in a call when the Cisco PGW 2200 Softswitch sends
the Session Destination Protocol (SDP) from the terminating call leg to
the H.323 Signaling Interface (HSI). Value range: 0 through 3.
0 = terminating seizure, 1 = Address complete, 2 = Alerting or Inband
information available, or 3 = Answer.
This property is added in software Release 9.4(1).
sendAfterRestart
SS7-ANSI=16
Number of queued messages to send (in one group) to MTP3 after restart
end. This value, combined with the sendTimer, controls the amount of
data sent to MTP3 after restart ends. If too much data is sent to MTP3
after restart, MTP3 could be flooded. Value range: 0 through 256.
slsTimer
SS7-ANSI=300
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-27
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Links
Table 1-8
SS7 Signaling Service Property Descriptions (continued)
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.
Value range: 0 through 3000.
0 = Disabled, 300 = 30 seconds.
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.
Value range: 0 through system maximum.
TMinDigits
0
Specifies minimum number of digits to receive for overlap digit
processing for call termination to this traffic path.
Value range: 0 through system maximum.
TOverlap
0
Set to 1 to enable overlap signaling for call termination to this traffic
path.
Value range: 0 or 1.
variant
SS7-ANSI=SS7-A
NSI, SS7-ITU
SS7 protocol variants supported by the local subsystem.
VOIPPrefix
0
A numeric string.
Planning SS7 Signaling Links
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)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-28
OL-1110-23
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Links
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 1-9 lists the Cisco PGW 2200 Softswitch interface card parameter definitions. Table 1-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).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-29
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Links
Table 1-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 1-10 describes the configuration parameters that define an Ethernet interface. Table 1-2 serves as
a form you can use to plan the Ethernet interfaces on your Cisco PGW 2200 Softswitch.
Table 1-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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-30
OL-1110-23
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Links
Table 1-10
Ethernet Interface Configuration Parameter Descriptions
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 1-11 lists and describes the configuration parameters that define the TDM interface. Table 1-25
serves as a form you can use to plan a TDM interface.
Table 1-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
1
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
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-31
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Links
Table 1-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
Text description of this component. Enter as many as 128 characters and
enclose in straight quotes.
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-32
OL-1110-23
Chapter 1
Planning for Provisioning
Planning SS7 Signaling Links
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 1-2) before deploying a configuration.
Table 1-12 describes the C7 IP link configuration parameters that define each link. Table 1-10 serves as
a form you can use to plan a single C7 IP link.
Table 1-12
C7 IP Link 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.
DESC
Description
None
Text description of this link. Enter as many as 128 characters and
enclose in straight quotes.
PRI
Priority
1
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
1
SS7 Signaling link code. Value range: 0 through 15.
TIMESLOT
Time slot
0
Time slot field for the C7 IP link. Identifies the physical WAN interface
card (WIC) slot, that is the SS7 serial port, of the Cisco ITP-L.
Value range: 0 through 3.
Description
Planning F-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 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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-33
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
Planning F-Links to Signaling Points
After you have planned your cards and interfaces, you are ready to plan the SS7 signaling links. When
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
After you have planned your cards and interfaces, you are ready to plan the SS7 signaling links. When
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.
Planning Media Gateway Control Links
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.
Planning Media Gateway External Nodes
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-34
OL-1110-23
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
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 1-13 describes the external node configuration parameters. Table 1-16 serves as a form you can
use to plan for each media gateway.
Table 1-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
characters and enclose in straight quotes. Hyphens (-) can be used.
DESC
Description
None
Text description of an external device. Enter as many as 128 characters
and enclose in straight quotes.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-35
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
Table 1-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 1-14 for a list of Type values for
Cisco PGW 2200 Softswitch software Release 9.6(1). The right
columns show the associated signaling type:
AS3600MGCPSGCPIPFASNASIUA
AS3660MGCPSGCPIPFASNASIUA
AS5200IPFASNAS
AS5300MGCPSGCPIPFASNASIUA
AS5350MGCPSGCPIPFASNASBSMV0IUA
AS5400MGCPSGCPIPFASNASBSMV0IUA
AS5800IPFASNAS
AS5850IPFASNAS
AS7200MGCPSGCPIPFASNAS
CAT8510MGCPSGCP
CAT8540MGCPSGCP
C2600MGCPSGCP IUA
H323EISUP
ITPM3UASUA
LS1010MGCPSGCP
MC3810MGCPIPFAS
MGCEISUP
MGX8260MGCPIPFASNAS
MGX8850MGCPSGCPIPFAS
RACLUSTER
SCPTCAPIP
SLTBSMV0
UNKNOWNUNKNOWN
ISDNSIGTYPE
ISDN Sig
Type
GROUP
Group
N/A
ISDN signaling type. Valid values are IUA or N/A (default is N/A). This
parameter is added in software Release 9.4(1).
M3UA/SUA group number. Value range: 0 for nodes that do not support
M3UA or SUA, or 1 through 100 for M3UA or SUA nodes. This
parameter is added in software Release 9.4(1).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-36
OL-1110-23
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
Table 1-14
ExtNode
MML Type
External Node Types for Cisco PGW 2200 Softswitch Software Release 9.6(1)
SGCP
MGCP
AS5200
IPFAS
IUA
BRI
IPFAS
NAS
MGCP
ANNO
MGCP
IVR
SUA
Other
NAS
AS5300
SGCP
MGCP
IPFAS
IUA
NAS
MGCP
ANNO
MGCP
IVR
AS5350
SGCP
MGCP
IPFAS
IUA
NAS
MGCP
ANNO
MGCP
IVR
BSMV0
AS5400
SGCP
MGCP
IPFAS
IUA
NAS
MGCP
ANNO
MGCP
IVR
BSMV0
NAS
MGCP
ANNO
NAS
MGCP
ANNO
AS5800
IPFAS
AS5850
MGCP
IPFAS
MGCP
IPFAS
C1751
MGCP
IPFAS
IUA
BRI
C1760
MGCP
IPFAS
IUA
BRI
MGCP
IPFAS
IUA
BRI
C2610XM
MGCP
IPFAS
IUA
BRI
C2611XM
MGCP
IPFAS
IUA
BRI
C2620XM
MGCP
IPFAS
IUA
BRI
C2621XM
MGCP
IPFAS
IUA
BRI
C2650XM
MGCP
IPFAS
IUA
BRI
C2651XM
MGCP
IPFAS
IUA
BRI
C2691
MGCP
IPFAS
IUA
BRI
C2801
MGCP
IPFAS
IUA
BRI
C2811
MGCP
IPFAS
IUA
BRI
C2821
MGCP
IPFAS
IUA
BRI
C2851
MGCP
IPFAS
IUA
BRI
MGCP
IPFAS
IUA
C3640
MGCP
IPFAS
IUA
BRI
C3640A
MGCP
IPFAS
IUA
BRI
MGCP
IPFAS
IUA
BRI
C3725
MGCP
IPFAS
IUA
BRI
C3745
MGCP
IPFAS
IUA
BRI
C3825
MGCP
IPFAS
IUA
BRI
C3845
MGCP
IPFAS
IUA
BRI
AS7200
C2600
C3600
C3660
SGCP
SGCP
SGCP
SGCP
CAT8510
SGCP
MGCP
CAT8540
SGCP
MGCP
IUA
MGCP
IVR
NAS
NAS
NAS
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-37
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
Table 1-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 1-15,
each media gateway signaling service defines the parent media gateway external node and assigns a
media gateway ID to that device. Table 1-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
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-38
OL-1110-23
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
Table 1-15
Media Gateway Signaling Service Configuration Parameter Descriptions
Voice Services
Provisioning
MML Parameter Tool Parameter
Name
Name
Default Value
Description
NAME
MML name
None
Unique name for this signaling service. Enter as many as 20
alphanumeric characters and enclose in straight quotes. Hyphens (-) can
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
N
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
0
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
0
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
0
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
0
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-39
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
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
Cisco ITP-L and media gateway communications.
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 1-16 describes configuration parameters you can use to configure network cards. Table 1-1 serves
as a form you can use to plan network card configurations.
Table 1-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
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.
Value range: 0 through 15.
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
enclose in straight quotes.
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-40
OL-1110-23
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
To provision an Ethernet interface, use the following component:
Note
•
VSPT name: EnetIF
•
MML name: ENETIF
ENETIF is not supported in software Release 9.4(1).
Table 1-17 describes the configuration parameters that define an Ethernet interface. Table 1-2 serves as
a form you can use to plan the Ethernet interfaces on your Cisco PGW 2200 Softswitch.
Table 1-17
Ethernet Interface Configuration Parameter Descriptions
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
characters and enclose in straight quotes. Hyphens (-) can be used.
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
enclose in straight quotes.
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 1-18 lists and describes the configuration parameters that define each link. Table 1-23 serves as a
form you can use to plan a single IP link.
Table 1-18
IP-Link 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.
DESC
Description
None
Text description of this link. Enter as many as 128 characters and
enclose in straight quotes.
Description
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-41
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
Table 1-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
1
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
0
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-42
OL-1110-23
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
Planning Backhaul TCP Link
The Backhaul TCP link component represents a static IP route. Its MML name is as follows:
•
MML Name—TCPLINK
The Backhaul TCP link component structure is shown in Table 1-19.
Table 1-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
Component description
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
IP_Addr1, IP_Addr2, IP_Addr3, or IP_Addr4.
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
the provisioning session is copied or deployed, an error message is generated and the copy or
deployment is stopped.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-43
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
•
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 Name—BRIPATH
The QSIG/Q.931 Over BRI Backhaul signaling service component structure is shown in Table 1-20.
Table 1-20
BRIPATH 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
Component description
The description can be up to 128 characters.
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.
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:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-44
OL-1110-23
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
•
You must define the TCPLINK parameter with the same EXTNODE attribute that its associated
BRIPATH has. If the TCPLNK is not defined when the BRIPATH is added/edited, a warning is
issued. If the TCPLINK is not defined when the provisioning session is copied or deployed, an error
message is generated and the copy or deployment is stopped.
•
If the TCPLINK with the same EXTNODE value as the BRIPATH is deleted, a warning message is
issued to inform you that the BRIPATH must also be deleted. If the BRIPATH is not deleted when
the provisioning session is copied or deployed, an error message is generated and the copy or
deployment is stopped.
•
A maximum of 2000 BRIPATHs can be provisioned on your Cisco PGW 2200 Softswitch.
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.
•
The following attributes cannot be modified:
– 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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-45
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
•
IPADDR1 and IPADDR2 must be different.
•
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 1-21 lists and describes the configuration parameters that define each session set. Table 1-27
serves as a form you can use to plan a single session set.
Table 1-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
characters and enclose in straight quotes. Hyphens (-) can be used.
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
Remote IP address of link interface on media gateway.
PEERADDR2
Peer address 2
0.0.0.0
Remote IP address of link interface on media gateway.
PEERPORT
Peer port
0
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
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-46
OL-1110-23
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
Table 1-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 1-15 lists and describes the configuration parameters that
define each D-channel. Table 1-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 1-22
D-Channel Configuration Parameter Descriptions
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
Unique name for this signaling service. Enter as many as 20
alphanumeric characters and enclose in straight quotes. Hyphens (-) can
be used. The name should begin with a letter character.
DESC
Description
None
Text description of this signaling service. Enter as many as 128
characters and enclose in straight quotes.
PRI
Priority
1
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
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-47
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
Table 1-22
D-Channel Configuration Parameter Descriptions (continued)
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
SIGSLOT
Signal slot
0
Description
Signal slot. Physical slot on the MGW where the T1/E1 interface is
installed. Value range: 0 through 63.
Note
SIGPORT
Signal port
0
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
0
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 1-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
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-48
OL-1110-23
Chapter 1
Planning for Provisioning
Planning Media Gateway Control Links
Table 1-23
MML
Parameter
Name
NOA Provisioning Parameters
Parameter Description
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
Component description
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
Cisco PGW 2200 Softswitch.
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 1-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
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-49
Chapter 1
Planning for Provisioning
Provisioning Trunk Groups and Trunks
Table 1-24
Bearer Capability Configuration Parameter Descriptions
MML
Parameter
Name
Voice Services
Provisioning
Tool Parameter
Name
Default Value
NAME
MML name
None
Unique name for this signaling service. Enter as many as 20
alphanumeric characters and enclose in straight quotes. Hyphens (-) can
be used. The name should begin with a letter character.
DESC
Description
None
Text description of this component. Enter as many as 128 characters and
enclose in straight quotes.
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 1, “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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-50
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
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 1-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 1-25 lists the nailed trunk MML command parameter definitions and their associated values.
Table 1-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:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-51
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
TrunkSrcSrc Src DestDestDest
ID cmp-idSpanTime slotcmp-idSpanTime slot
101 00130002ffff6500140001
3
102 00130002ffff66
00140001
1
3
2
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 1-26 lists the profile MML command parameter definitions and their associated values.
Table 1-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
enclose in straight quotes. Hyphens (-) can be used.
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 1, “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 1-27, to be overridden for the specified
component.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-52
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-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
IAM. Acceptable values are: 0 (default) for no, or 1 for yes.
cipNonGeo
cipNonGeo
Indicates whether or not to include the CIP in the IAM on all calls to non-geographic
numbers. Acceptable values are: 0 (default) for no, or 1 for yes.
confusion
confusion
Flag indicating whether or not to send the confusion message when an unrecognized
message type is received. Acceptable values are: 0 (default) for no, or 1 for yes.
congProc
congProc
Indicates the procedure to follow when there is congestion on ISUP circuits; choices
are: alternate routing or blocking. This value is taken from the originating trunk group
and used when re-attempting occurs. Acceptable values are: BLK (default) for
blocking, or ALTRTE for alternate routing.
defaultBC
defaultBC
Indicates the default bearer capability; which pertains to incoming SS7 trunk groups.
Used to code the User Service Information parameter in the outgoing IAM message.
Acceptable values are: SPEECH (default), or 3_1_KHZ.
gapInclude
gapInclude
Indicates whether or not to allow using the Generic Address Parameter in the IAM.
Acceptable values are: 0 (default) for no, or 1 for yes.
gnInclude
gnInclude
Indicates whether or not to include the Generic Name in the IAM. Acceptable values
are: 0 (default) for no, or 1 for yes.
Note
This property applies to ANSI SS7 only. The applicable MDO files are
ANSISS7_2K, ANSISS7_92, ANSISS7_C2, ANSISS7_C3, ANSISS7_E1,
ANSISS7_STANDARD, and GR317.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-53
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-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
IAM. Acceptable values are: 0 (default) for no, or 1 for yes.
notificationInclude
notificationIncl Indicates whether or not to include the notification parameter in the Call Progress
ude
(CPG) message. Acceptable values are: 0 (default) for no, or 1 for yes.
ocnInclude
ocnInclude
redirCapInclude
redirCapInclud Indicates whether or not to include the Redirect Capability in the IAM. Acceptable
e
values are: 0 (default) for no, or 1 for yes.
Indicates whether or not to include the Original Called Number in the IAM.
Acceptable values are: 0 (default) for no, or 1 for yes.
redirCounterInclude redirCounterIn Indicates whether or not to include the Redirect Counter in the IAM. Acceptable
clude
values are: 0 (default) for no, or 1 for yes.
redirInfoInclude
redirInfoInclud Indicates whether or not to include the Redirection Info in the IAM. Acceptable
e
values are: 0 (default) for no, or 1 for yes.
rnInclude
rnInclude
serviceCodeInclude
serviceCodeInc Indicates whether or not to include the Service Code parameter in the IAM.
lude
Acceptable values are: 0 (default) for no, or 1 for yes.
transReqInclude
transReqInclud Indicates whether or not to include the transaction request parameter in the IAM.
e
Acceptable values are: 0 (default) for no, or 1 for yes.
unavailProc
unavailProc
Indicates whether or not to include the Redirecting Number in the IAM. Acceptable
values are: 0 (default) for no, or 1 for yes.
Indicates the procedure to follow when there are no available ISUP circuits; choices
are: alternate routing or blocking. This value is taken from the originating trunk group
and used when re-attempting occurs. Acceptable values are: BLK (default) for
blocking, or ALTRTE for alternate routing.
The following is an MML command format used to attach a profile to a trunk group:
prov-add:trnkgrpprof:name="1000",grprofile="profile1"
Note
A profile must be created before a trunk group can be associated with the profile.
Table 1-28 lists the profile MML command parameter definitions and their associated values.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-54
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-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
enclose in straight quotes. Hyphens (-) can be used.
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 1, “Outbound
SIP Header (OUTSIPHEADER),” 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 1, “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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-55
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
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).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-56
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Level 2
At level 2, the Cisco PGW 2200 Softswitch can apply another layer of SLA bias to profile negotiation.
This additional layer provides the capability of provisioning ATM_ORIG_PROFILE and
ATM_TERM_PROFILE results within the Cisco PGW 2200 Softswitch A-number and B-number
analysis functions. These results contain the same data words and both results deliver a profile list to
bias negotiation on either the ingress or egress gateway.
Dataword2 in the result type provides a mandatory or preferred indication for the profile list, which
determines the actions that must take place. If dataword2 is set to mandatory, then the profile list from
the previous stages is ignored and the egress gateway supports a profile from the list identified by
dataword1. If dataword2 is set to preferred, then the profile list identified by dataword1 is retrieved and
the existing list (from previous stages, if collected) is appended to the profile list, thus forming a new
list to forward to the gateway.
Note
If results are collected from A-number analysis and then from B-number analysis, B-number analysis
can further adjust or overwrite the existing profile list created by the A-number analysis. This provides
the possibility for there being two sublevels within the level 2 capability.
GWDefaultATMProfile
When the Cisco PGW 2200 Softswitch is acting as a Call Agent making ATM voice connections
between two gateways, it must provide the capability to influence the profile negotiation between the
two sides to the gateway.
To accomplish this profile negotiation, a list of profiles supported by the code image on the gateway, but
is refined by configuration according to the prevailing network Service Level Agreement (SLA). The
Cisco PGW 2200 Softswitch applies the SLA changes or refinements to the profile list rather than apply
them as configuration changes on the gateways. Thus, the gateways contain a list of profiles that their
respective code images can support. The Cisco PGW 2200 Softswitch retrieves a provisioned profile list
from the GWDefaultATMProfile trunk group property or as the ATM_ORIG_PROFILE or
ATM_TERM_PROFILE result delivered from A-number (Calling number) or B-number (Called
number) analysis. This list is then passed over MGCP to the gateway to bias profile negotiation.
While establishing the connection between two gateways, the originating gateway profile list is refined
by ANDing with a new profile sent from the Cisco PGW 2200 Softswitch in the originating side CRCX
message. The resultant profile list is passed in the Session Description Protocol (SDP) to the terminating
gateway. Also, the Cisco PGW 2200 Softswitch can optionally produce another profile choice to bias the
profile on the terminating gateway according to the SLA. This profile accompanies other data sent in the
CRCX message to the terminating gateway. Upon receiving this profile, the terminating gateway ANDs
the SDP profile with any existing received profiles and then ANDs the profile list with the existing
gateway ActiveProfileList to produce a resultant profile list. From the resultant profile list, the gateway
chooses a profile entry and passes back the profile list to the originating side.
The Cisco PGW 2200 Softswitch produces a profile choice list (ProfileList1) that is sent to the
originating gateway in the first CRCX command. The originating gateway forms a new list by ANDing
the received profile with its own ActiveProfileList and generates ProfileList2, which consists only of the
profile choices that were present in both lists. This profile information is embedded in the SDP that is
sent back to the Cisco PGW 2200 Softswitch in the CRCX Acknowledgement.
If the Cisco PGW 2200 Softswitch also has an SLA profile for the terminating gateway (ProfileList3),
it is added to the profile list in the SDP and both profiles are sent to the terminating gateway in another
CRCX message. Upon receiving this profile, the terminating gateway ANDs all three lists to produce a
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-57
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
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 file—Used to define the trunk group and the signal path controlling the trunk group
•
Trunk file—Used 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 1-29 lists the MML trunk group parameters, the corresponding VSPT names, the parameter
definitions and the associated values.
Table 1-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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-58
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-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_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 Cisco PGW 2200 Softswitch node).
CTI—Used with CTI signaling services.
Switch type values are:
0 = No switch-specific logic 23 = SS7 ANSI
for the signaling path.26 = DPNSS
5 = BTNUP27 = NET5
10 = SS7 Japan29 = QSIG MASTER
17 = 5ESS30 = QSIG SLAVE
20 = SS7 Clear40 = SS7 ITU
22 = NI2
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-59
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-29
MML
Parameter
Name
SELSEQ
Trunk Group Parameter Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
Name
Description
Selection
sequence
Specifies the trunk selection sequence. The Cisco PGW 2200 Softswitch uses the CICs
within a trunk group according to the sequence specified by the SELSEQ value. You can
provision this value to reduce the chance of glare when the system selects a trunk.
ASC = Ascending. The system selects the available CICs in ascending order starting from
the lowest CIC number (for example, 1, 2, 3 ...).
CASC = Cyclic ascending. The system selects the next available CIC in ascending order
based on the most recently selected CIC. For example, if the most recently selected CIC is
CIC 5, the system selects CIC 6, even if CIC 1 is available.
CDESC = Cyclic descending. Similar to CASC, but in descending order based on the most
recently selected CIC. For example, if the last selected CIC is number 18, the system selects
CIC 17, even if CIC 31 is available.
DESC = Descending. Similar to ASC, but in descending order starting from the highest CIC
number (for example, 31, 30, 29 ...).
EASC = Even ascending, then odd ascending. The system selects the first available even CIC
in ascending order (for example, 2, 4, 6 ...). If no even CIC is available in the trunk group,
the system selects the first available odd CIC in ascending order (for example, 1, 3, 5 ...).
EDECS = Even descending, then odd descending. Similar to EASC, but in descending order.
The system selects the first available even CIC in descending order (for example, 30, 28,
26 ...). If no even CIC is available in the trunk group, the system selects the first available
odd CIC in descending order (for example, 31, 29, 27 ...).
ITU2 = ITU method 2. The system selects the trunk according to the procedure in ITU-T
Recommendation Q.764, paragraph 2.9.1.3 Method 2.
LIDL = Least idle (default). The system selects the least idle (most recently used) CIC.
MIDL = Most idle. The system selects the most idle (least recently used) CIC.
OASC = Odd ascending, then even ascending. The system selects the first available odd CIC
in ascending order (for example, 1, 3, 5 ...). If no odd CIC is available in the trunk group,
the system selects the first available even CIC in ascending order (for example, 2, 4, 6...).
ODESC = Odd descending, then even descending. Similar to OASC, but in descending order.
The system selects the first available odd CIC in descending order (for example, 31, 29,
27 ...). If no odd CIC is available in the trunk group, the system selects the first available
even CIC in descending order (for example, 30, 28, 26 ...).
RDM = Random. The system selects a CIC at random.
Caution
When the trunk selection sequence (SELSEQ) is set to its default value, LIDL
(least idle), there is a risk that the Cisco PGW 2200 Softswitch will select a
significant number of temporarily unavailable trunks, which causes calls to fail.
This kind of call failure can happen when an overloaded media gateway responds
to the Cisco PGW 2200 Softswitch with a temporary MGCP error (400 to 499),
or the Cisco PGW 2200 Softswitch does not receive a response from the media
gateway in time. We recommend that you set SELSEQ to a value other than LIDL.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-60
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-29
Trunk Group Parameter Descriptions (continued)
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 1-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 1-41. Table 1-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 1, “Provisioning with the Cisco Voice Services
Provisioning Tool.”
Table 1-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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-61
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
Description
TYPE
Trunk Type
Identifies the trunk group type. Values:
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 Cisco PGW 2200 Softswitch node).
CTI—Used with CTI signaling services.
Switch type values are:
0 = No switch-specific logic 23 = SS7 ANSI
for the signaling path.26 = DPNSS
5 = BTNUP27 = NET5
10 = SS7 Japan29 = QSIG MASTER
17 = 5ESS30 = QSIG SLAVE
20 = SS7 Clear40 = SS7 ITU
22 = NI2
QABLE
Queuable Type Determines if queuing is used on the trunk during call processing. Value range: Y
for yes or N for no (default).
RingNoAnswer
Ring No
Answer
Ring no answer. Indicates the time, in seconds, ringing is allowed to occur. Value
range: 0 through 600, in seconds. The default setting is 255.
Note
With patch CSCOnn015 installed, this property becomes the TO-02 (Time
Out 02) timer for the BTNUP protocol variant. The TO-02 timer is for
non-receipt of the Answer message and starts upon receipt of the Answer
Complete message. The TO-02 timer interval is the time, in seconds, before
the call is released. Value range: is 1 to 12 minutes (180 seconds is the
default value). The TO-02 timer is cancelled upon receipt of the Answer
message, Clear message, or Release message.
GLARE
Glare control
Glare control. Glare is a collision that occurs when two network nodes
simultaneously attempt to reserve the same channel. Values are: 0 (no handling)
(default), 1 (always), 2 (even/odd), or 3 (no control).
CotPercentage
COT
percentage
Determines the percentage of calls on the trunk upon which a continuity test is
performed. Value range: 0 through 100.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-62
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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 ...
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-63
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
Description
Selseq
Select
Sequence
... continued:
LIDL = Least idle (default). The system selects the least idle (most recently used)
CIC.
MIDL = Most idle. The system selects the most idle (least recently used) CIC.
OASC = Odd ascending, then even ascending. The system selects the first available
odd CIC in ascending order (for example, 1, 3, 5 ...). If no odd CIC is available in
the trunk group, the system selects the first available even CIC in ascending order
(for example, 2, 4, 6...).
ODESC = Odd descending, then even descending. Similar to OASC, but in
descending order. The system selects the first available odd CIC in descending
order (for example, 31, 29, 27 ...). If no odd CIC is available in the trunk group, the
system selects the first available even CIC in descending order (for example, 30, 28,
26 ...).
RDM = Random. The system selects a CIC at random.
Caution
When the trunk selection sequence (SELSEQ) is set to its default value,
LIDL (least idle), there is a risk that the Cisco PGW 2200 Softswitch will
select a significant number of temporarily unavailable trunks, which
causes calls to fail. This kind of call failure can happen when an
overloaded media gateway responds to the Cisco PGW 2200 Softswitch
with a temporary MGCP error (400 to 499), or the Cisco PGW 2200
Softswitch does not receive a response from the media gateway in time.
We recommend that you set SELSEQ to a value other than LIDL.
SatelliteInd
Satellite
Satellite indicator. Indicates if the trunk is going over a satellite. Values are 0 (no)
(default) or 1 (yes).
Npa
Numbering
Plan Area
Numbering Plan Area. Indicates the NPA code associated with the incoming trunk
group. Value range: 0 (none) (default), or a 3-digit code from 200 through 999.
CustGrpId
Customer
group ID
Customer group ID. The ID of the customer associated with this trunk group. Value
range: 0 (if not defined) or any 4-character alphanumeric string.
CompressionType
Compression
Type
Compression type. Identifies the G.711 compression type used on the trunk. After
the fax or modem tone has been detected by the MGW, select the proper
compression type. Values are: 0 (none), 1 (mu-law) (default), 2 (A-law), or 3 (clear
channel).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-64
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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: 0—no 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).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-65
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-66
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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),
20 (OLI_CELLULAR_SVC_2),
21 (OLI_CELLULAR_SVC_ROAMING),
22 (OLI_PRIVATE_PAYSTATIONS),
23 (OLI_ACCESS_FOR_VPN_TYPES_OF_SVC),
24 (OLI_INTERLATA_RESTRICTED),
25 (OLI_TESTCALL),
26 (OLI_TOLLFREE_FROM_PAYSTATIO),
27 (OLI_CUSTOMER_SPECIFIC_1),
28 (OLI_CUSTOMER_SPECIFIC_2),
29 (OLI_INTERLATA_RESTRICTED_HOTEL), or
30 (OLI_INTERLATA_RESTRICTED_COINLESS)
DefaultOLI
Default
Originating
Line
Information
DefaultCHG
Default Charge Default charge number. Values are: 1 to 16 digits or NULL. Default: 0
Number
DefaultCHGNOA
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)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-67
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-68
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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),
27 (NOA_CELL_GLOBAL_ID_NMT_450),
28 (NOA_CELL_GLOBAL_ID_AUTONET),
29 (NOA_PORTED_NUMBER),30 (NOA_PISN_SPECIFIC_NUMBER),
31 (NOA_UK_SPECIFIC_ADDRESS),32 (NOA_SPARE),
33 (NOA_MCI_VNET),
34 (NOA_INTERNATIONAL_OPR_TO_OPR_OUTSIDE_WZI),
35 (NOA_INTERNATIONAL_OPR_TO_OPR_INSIDE_WZI),
36 (NOA_DIRECT_TERMINATION_OVERFLOW),
37 (NOA_ISN_EXTENDED_INTERNATIONAL_TERMINATION),
38 (NOA_TRANSFER_ISN_TO_ISN),39 (NOA_CREDIT_CARD),
40 (NOA_DEFINED_IN_SSUTR),41 (NOA_DEFINED_IN_SSUTR2),
42 (RESERVED),43 (NOA_DISCARDED),
44 NOA_NETWORK_RN_CONCAT_WITH_CDPN,
45 NOA_NAT_NUM_WITH_SELECT_OF_CARR,
46 NOA_INT_NUM_WITH_SELECT_OF_CARR,
47 NOA_NATIONAL_SPARE_2,
48 NOA_PORTED_NUMBER_OR_SCREENED_FOR_PORTING,
49 NOA_SPECIAL_NUMBER,
50 NOA_NATL_NUM_TRANSIT_NETWORK_SELECT,
51 NOA_INTL_NUM_TRANSIT_NETWORK_SELECT,
52 NOA_SPAIN,
53 NOA_PARTIAL_CALLING_LINE_ID,
54 NOA_NETWORK_RN_NSN_FORMAT , or
55 NOA_NETWORK_RN_NETWORK_SPECIFIC_FORMAT
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-69
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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),
8 (NPI_MARITIME_MOBILE),
9 (NPI_LAND_MOBILE), or
10 (NPI_ISDN_MOBILE)
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
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-70
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-71
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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.
AInternationalPrefix
AInternational
Prefix
A-number international prefix. Determines the prefix for outgoing calling numbers
when NOA is set to International. Value range: NULL (default) or digit string.
ANationalPrefix
ANationalPrefi A-number national prefix. Determines the prefix for outgoing calling numbers
x
when Nature of Address (NOA) is set to National. Value range: NULL (default) or
digit string.
BInternationalPrefix
BInternational
Prefix
BNationalPrefix
BNationalPrefi B-number national prefix. Determines the prefix for outgoing called numbers when
x
Nature of Address (NOA) is set to National. Value range: NULL (default) or digit
string.
ADigitCCPrefix
ADigitCCPrefi A-digit country code prefix. Controls functionality that applies a country code
x
prefix to the calling party number before sending the call forward. Values are: 0
(default) or 1, where 0 means disabled and 1 means enabled.
BDigitCCPrefix
BDigitCCPrefi B-digit country code prefix. Controls functionality that applies a country code
x
prefix to the called party number before sending the call forward. Values are 0
(default) or 1, where 0 means disabled and 1 means enabled.
B-number international prefix. Determines the prefix for outgoing called numbers
when NOA is set to International. Value range: NULL (default) or digit string.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-72
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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
Ta2TimePeriod Ta2 time period. Indicates the value for the time period Ta2, in seconds. Value
range: 1 through 180. Default: 30
Ta3TimePeriod
Ta3TimePeriod Ta3 time period. Indicates the value for the time period Ta3, in seconds. Value
range: 1 through 180. Default: 3
ExpiryWarnToneType ExpiryWarnTo
neType
String defining the tone to be applied to warn that the assigned call duration is
almost expired. Value range: Any valid MGCP event name. Default: NULL
ExpiryWarnToneDur
ExpiryWarnTo
neDuration
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-73
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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
This property is added in software Release 9.4(1).
UnsolicitedNotifyMet Unsolicited
Unsolicited Notify method. Determines if the unsolicited Notify method for
hod
Notify Method unsolicited notification of SIP DTMF digit is enabled or disabled.
Valid Values: 0 = Unsolicited Notify method disabled, 1 = Unsolicited Notify
method enabled, 2 = Unsolicited Info method enabled.
Default: 0
This property is added in software Release 9.4(1).
Option 2 is added in software Release 9.7(3) and later.
MinEventSubscribeD
uration
Min Event
Subscribe
Duration
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
This property is added in software Release 9.4(1).
MaxSubscriptionDura Max
tion
Subscription
Duration
Maximum subscription duration. Defines the maximum duration (in seconds) for
which a subscription can be made. Value range: 0 through 3600.
Default: 0
This property is added in software Release 9.4(1).
OD32DigitSupport
OD 32 Digit
Support
Overdecadic 32 digit support. Allows 32 digits and overdecadic digits support for
the ANSI, Q.761, and Q.767 protocol variants. Values are: 0 (disabled) and 1
(enabled).
Default: 0
This property is added in software Release 9.4(1).
populateSDPInfoIn
CDR
Populate SDP
Info In CDR
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
This property is added in software Release 9.4(1).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-74
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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_AcgPn—Generic number parameter containing additional Calling Party
number
•
Redirecting Number (all if more than one)
•
OCN—Original 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
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-75
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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: 0–None, 1–SIP-T supported, or 2–SIP-GTD supported.
Default: 1
Default Value: 0
This property is added in software Release 9.4(1).
EnableIPScreening
Enable IP
Screening
Enables the incoming trunk group to select a dial plan based on the IP address,
source ID, and CLI prefix tables. Valid values: 0 (no dial plan lookup) or 1 (require
dial plan lookup).
Default Value: 0
This property is added in software Release 9.4(1).
SipIPSource
SIP IP Source
Indicates for the Cisco PGW 2200 Softswitch to use the IP packet source address
or IP address from Session Description Protocol (SDP) in the INVITE message to
make the dial plan selection for SIP calls. Valid values: 0 (use the IP packet source
address) or 1 (use the IP address from SDP).
Default Value: 0
This property is added in software Release 9.4(1).
DefaultPN
Default PN
Enables the incoming trunk group to have a default PN if the incoming call does not
have one, overdecadic digits are supported. Valid values: overdecadic digit string
from 1 through 20 digits in length.
Default Value: NULL
This property is added in software Release 9.4(1).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-76
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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),
26 (NOA_CELL_GLOBAL_ID_NMT_900),
27 (NOA_CELL_GLOBAL_ID_NMT_450),
28 (NOA_CELL_GLOBAL_ID_AUTONET),
29 (NOA_PORTED_NUMBER),30 (NOA_PISN_SPECIFIC_NUMBER),
31 (NOA_UK_SPECIFIC_ADDRESS),32 (NOA_SPARE),
33 (NOA_MCI_VNET),
34 (NOA_INTERNATIONAL_OPR_TO_OPR_OUTSIDE_WZI),
35 (NOA_INTERNATIONAL_OPR_TO_OPR_INSIDE_WZI),
36 (NOA_DIRECT_TERMINATION_OVERFLOW),
37 (NOA_ISN_EXTENDED_INTERNATIONAL_TERMINATION),
38 (NOA_TRANSFER_ISN_TO_ISN),39 (NOA_CREDIT_CARD),
40 (NOA_DEFINED_IN_SSUTR),41 (NOA_DEFINED_IN_SSUTR2),
42 (RESERVED),43 (NOA_DISCARDED),
44 NOA_NETWORK_RN_CONCAT_WITH_CDPN,
45 NOA_NAT_NUM_WITH_SELECT_OF_CARR,
46 NOA_INT_NUM_WITH_SELECT_OF_CARR,
47 NOA_NATIONAL_SPARE_2,
48 NOA_PORTED_NUMBER_OR_SCREENED_FOR_PORTING,
49 NOA_SPECIAL_NUMBER,
50 NOA_NATL_NUM_TRANSIT_NETWORK_SELECT,
51 NOA_INTL_NUM_TRANSIT_NETWORK_SELECT,
52 NOA_SPAIN,
53 NOA_PARTIAL_CALLING_LINE_ID,
54 NOA_NETWORK_RN_NSN_FORMAT , or
55 NOA_NETWORK_RN_NETWORK_SPECIFIC_FORMAT
Default: 0
This property is added in software Release 9.4(1).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-77
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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),
8 (NPI_MARITIME_MOBILE),
9 (NPI_LAND_MOBILE), or
10 (NPI_ISDN_MOBILE)
Default Value: 0
This property is added in software Release 9.4(1).
DefaultPNPres
Default PN
Pres
Displays the Default Presentation Number Presentation Indicator value. Valid
values: 0 through 4.
0 (NOTUSED) (default),
1 (PRES_NO_INDICATION),
2 (PRES_ALLOWED),
3 (PRES_RESTRICT), or
4 (PRES_UNAVAIL)
Default Value: 0
This property is added in software Release 9.4(1).
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
This property is added in software Release 9.4(1).
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-78
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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.)
3 (Sets to feature transparency preferred by a nontransparent destination can be
used if necessary to complete the call.)
4 (Sets to feature transparency preferred by a nontransparent destination can be
used if necessary to complete the call.)
5 (Sets to indicate that the attempted feature will be removed from the onward
routed call, and the indicator is informed of this.)
6 (Sets to release a feature call.)
7 (Sets to release a feature call.)
8 (Sets to remove the feature string and continue.)
Default Value: 5
This property is added in software Release 9.4(1). The range changed to 1-8 and the
default changed to 5 in software Release 9.6(1).
CustomerVPNid
Customer VPN Assigns a VPN ID to a trunk group or system. Valid values: 1 through 8
ID
alphanumeric character string.
Default Value: 00000000
This property is added in software Release 9.4(1).
CustomerVPNOffNet
TblNum
Customer VPN Allows assignment of a VPN off-net profile table index to a particular trunk group.
Off Net Table Value range: 1 through 8
Num
1 (Indicates that completely transparent operation is required or the call will not
complete.)
2 (Sets to feature transparency preferred by a nontransparent destination can be
used if necessary to complete the call.)
3 (Sets to feature transparency preferred by a nontransparent destination can be
used if necessary to complete the call.)
4 (Sets to feature transparency preferred by a nontransparent destination can be
used if necessary to complete the call.)
5 (Sets to indicate that the attempted feature will be removed from the onward
routed call, and the indicator is informed of this.)
6 (Sets to release a feature call.)
7 (Sets to release a feature call.)
8 (Sets to remove the feature string and continue.)
Default Value: 0
This property is added in software Release 9.4(1). The range changed to 1-8 and the
default changed to 5 in software Release 9.6(1)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-79
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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
This property is added in software Release 9.4(1).
SdpXmitToH323Trig
ger
SDP transmit
SDP transmit to H.323 trigger. Indicates the point in a call when the
to H323 trigger Cisco PGW 2200 Softswitch sends the Session Destination Protocol (SDP) from
the terminating call leg to the H.323 Signaling Interface (HSI). Value range: 0
through 3.
0 = terminating seizure, 1 = Address complete, 2 = Alerting or Inband information
available, or 3 = Answer.
This property is added in software Release 9.4(1).
GWDefaultATMProfil GW Default
e
ATM Profile
Provides, on a per trunk group basis, an initial list of profiles for use in ATM
gateway profile negotiation. This property contains a list of profile choices
separated by semi-colons, that influences ATM gateway profile negotiation. If
GWDefaultATMProfile is set to NULL (default), then there is no profile list
negotiation bias applied from the trunk group level. Valid values: NULL,
<Profile1>;<Profile2>;<ProfileN>, where the string is 1 (minimum) to 140
(maximum) characters.
Default value: NULL
This property is added in software Release 9.5(2)
PlayAnnouncement
Play
Enables, on a per trunk group basis, playing an early announcement. This property
Announcement can either contain an Integer Announcement Identity, or, if it is set to 0 (default),
the announcement function is considered disabled at the trunk group level. Valid
values: any integer value greater than 0.
Default value: 0
This property is added in software Release 9.5(2)
AtmConnectionType
Atm.
Connection
Type
Populates the connection type parameter (ct:) in local connection option
parameters. This property is read for both originating and terminating legs of all
ATM-switched calls. Valid values: 1 (AAL1), 2 (AAL1_SDT), 3 (AAL1_UDT), 4
(AAL2), 5 (AAL 3/4), or 6 (AAL5).
Default value: 4 (AAL2)
This property is added in software Release 9.5(2)
BTechPrefix
B Tech Prefix
Provides a digit string to be used as a Tech Prefix to the B-number when sending
the call forward. Valid values: any integer.string from one digit (minimum) through
16 (maximum) digits. The Tech Prefix uses overdecadic digits B and C and maps
them to * and # respectively. The Tech Prefix and a separator are appended to the
beginning of the B-number.
This property is added in software Release 9.5(2)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-80
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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
This property is added in software Release 9.5(2)
LoopAvoidanceCount Loop
er
Avoidance
Counter
Enables the support of the loop avoidance feature in DPNSS protocol. Valid values:
0 through 25.
Default value: 0
This property is added in software Release 9.5(2)
MwiStringON
MWI String On Enables the support of MWI to the DPNSS protocol to light the MWI lamp on a
particular extension when this string is encoded in message. Valid values: Digit
string from 1 (minimum) through 32 (maximum) digits.
Default value: NULL
Note
Ensure the digit string provisioned is the same MWI string provisioned in
Cisco CallManager.
This property is added in software Release 9.5(2)
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.
This property is added in software Release 9.5(2)
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
This property is added in software Release 9.5(2)
InhibitOutgoingCallin Inhibit
gNameDisplay
Outgoing
Calling Name
Display
Enables or disables inhibit outgoing calling name display in DPNSS and EISUP
(HSI) protocols. Valid values: 0 (enable) or 1 (disable).
Default value: 0
This property is added in software Release 9.5(2)
InhibitIncomingConn
ectedNameDisplay
Inhibit
Incoming
Connected
Name Display
Enables or disables inhibit incoming connected name display in DPNSS and EISUP
(HSI) protocols. Valid values: 0 (enable) or 1 (disable).
Default value: 0
This property is added in software Release 9.5(2)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-81
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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
This property is added in software Release 9.5(2)
MidCallCPInterval
Mid Call CP
Interval
Enable s or disables mid-call checkpointing. When enabled, you can specify the
interval (in minutes) between checkpointing events in the connected state. Valid
values: 0 (disabled) (default) through 60.
Default value: 0
This property is added in software Release 9.5(2)
CliSelectionForCode
OfPractice3
Cli Selection
For Code Of
Practice 3
Provisions, on a per trunk group basis, the level of CLI selection used when sending
the calling line identities (such as Calling Party Number or Generic Number
parameter) to the succeeding exchange. Valid range: 0 through 2. Valid values:
0—Indicates no specific CLI selection (default), 1—Indicates single CLI selection,
which sends only the CLI, or 2—Indicates dual CLI selection, which ends the CLI;
or the CLI and the PN.
Default value: 0
This property is added in software Release 9.5(2)
InhibitOutgoingConn
ectedNameDisplay
Inhibit
Outgoing
Connected
Name Display
Enables or disables inhibit outgoing connected name display in DPNSS and EISUP
(HSI) protocols. Valid values: 0 (enable) or 1 (disable).
Default value: 0
This property is added in software Release 9.5(2)
InhibitOutgoingConn
ectedNumberDisplay
AOCInvokeType
Inhibit
Outgoing
Connected
Number
Display
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
This property is added in software Release 9.5(2)
Default value: 1
This property is added in software Release 9.5(2)
AOCDefaultTariffId
AOC Default
Tariff Id
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
This property is added in software Release 9.5(2)
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-82
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Table 1-30
Trunk Group File Properties Descriptions (continued)
Voice Services
Provisioning
Tool Parameter
MML Parameter Name Name
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:
0—Buffer the new offer
1—Reject 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: 0—disable, 1—enable.
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, Satellite Indicator, NPA,
Customer Group ID, Compression Type, Echo Cancellation, External COT, Detect Fax Modem Tone,
Max ACL, ACL Duration, ACC Response Control Inhibit, ISUP Transparency Disabled, AOC Enabled,
Carrier Screening, Originating Carrier ID, Notify Setup Complete, Package Type, ACC Response
Category Name, Default Carrier ID National Network ID, Default OLI, Default CHG, Default CHG
NOA, Default CHG NPI, Default DN, Default DN NOA, Default DN NPI, Default DN Pres, Default DN
SI, Default Carrier ID Net ID, Default Carrier ID Net Type, MGC Domain, MGC SIP Version, Local
Port, Invite Timer T1, Gen Timer T1, Gen Timer T2, Max Redirect Count, Support 183, From Field, In
Session Timer, Out Session Timer, Hold Timer, Expires Timer, Support Reliable 100, Retry After Timer,
Max Forwards, Gateway RB Tone Support, Wait for Answer Timer, Wait for Originating SDP Timer,
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-83
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
Wait for Terminating SDP Timer, Charge Origin, Send Address in CGPN, CGPN Presentation
Restricted, AInternationalPrefix, ANationalPrefix, BInternationalPrefix, BNationalPrefix,
ADigitCCPrefix, BDigitCCPrefix, BDigitCCrm CCOrigin, Ta1TimePeriod, Ta2TimePeriod,
Ta3TimePeriod, ExpiryWarnToneType, ExpiryWarnToneDur, CLISelect, GWDefaultCodecString,
AllowH323Hairpin, H323AdjunctLink, and FAXsupport.
The following are examples of a trunk group file #format3 text formats:
#format3 – 9.3001
1000
TTTT-SS-BB ss7svc1 TDM_ISUP
N
5 0 10 LIDL 1 0 703 7777 1 0 Loop 0 3 5 1 1 1 1 1111 0 ABC 0 0 0
703 0 0 301 0 0 0 0 202 0 vsc1 SIP2.0 5555 2000 800 6000 2 1 mgcusr 600000 300000 600000 30000 FALSE 90000 10
0 65 10 10 0 1 0 NULL NULL NULL NULL 0 0 NULL NULL 20 30 3 NULL 1
#format3 – 9.3002
2000
TTTT-SS-BB ss7svc1 TDM_ISUP
N
5 0 10 LIDL 1 0 703 7777 1 0 Loop 0 3 5 1 1 1 1 1111 0 ABC 0 0 0
703 0 0 301 0 0 0 0 202 0 vsc1 SIP2.0 5555 2000 800 6000 2 1 mgcusr 600000 300000 600000 30000 FALSE 90000 10
0 65 10 10 0 1 0 NULL NULL NULL NULL 0 0 NULL NULL 20 30 3 NULL 1 CLI NULL 0 0 0
The customer trunk group file for version 9.4001 has the following parameters in this particular order
(104 columns)
The fields are: Trunk Group Number, CLLI, Signaling Service MML Name, Trunk Group Type,
Queueable, Ring No Answer, Glare, COT percentage, Select Sequence, Satellite Indicator, NPA,
Customer Group ID, Compression Type, Echo Cancellation, External COT, Detect Fax Modem Tone,
Max ACL, ACL Duration, ACC Response Control Inhibit, ISUP Transparency Disabled, AOC Enabled,
Carrier Screening, Originating Carrier ID, Notify Setup Complete, Package Type, ACC Response
Category Name, Default Carrier ID National Network ID, Default OLI, Default CHG, Default CHG
NOA, Default CHG NPI, Default DN, Default DN NOA, Default DN NPI, Default DN Pres, Default DN
SI, Default Carrier ID Net ID, Default Carrier ID Net Type, MGC Domain, MGC SIP Version, Local
Port, Invite Timer T1, Gen Timer T1, Gen Timer T2, Max Redirect Count, Support 183, From Field, In
Session Timer, Out Session Timer, Hold Timer, Expires Timer, Support Reliable 100, Retry After Timer,
Max Forwards, Gateway RB Tone Support, Wait for Answer Timer, Wait for Originating SDP Timer,
Wait for Terminating SDP Timer, Charge Origin, Send Address in CGPN, CGPN Presentation
Restricted, AInternationalPrefix, ANationalPrefix, BInternationalPrefix, BNationalPrefix,
ADigitCCPrefix, BDigitCCPrefix, BDigitCCrm, CCOrigin,Ta1TimePeriod,
Ta2TimePeriod,Ta3TimePeriod, ExpiryWarnToneType, ExpiryWarnToneDur, CLISelect,
GWDefaultCodecString, AllowH323Hairpin, H323AdjunctLink, FAXsupport, SubscribeNotifySupport,
UnsolicitedNotifyMethod, MinEventSubscribeDuration, MaxSubscriptionDuration,
populateSDPInfoInCDR, OD32DigitSupport, Anumnormalise, Bnumnormalise, GtdCapTypeProp,
GtdMsgFmt, IsupTransEarlyBackwardDisabled, sipMimeBodySupport, EnableIPScreening,
SipIPSource, DefaultPN, DefaultPNNOA, DefaultPNNPI, DefaultPNPres,
CallForwardRerouteDisabled, CustomerVPNOnNetTblNum, CustomerVPNid,
CustomerVPNOffNetTblNum, FeatureTransparencyDisabled, SdpXmitToH323Trigger.
The customer trunk group file for version 9.5001 has the following parameters in this particular order
(122 columns)
The fields are: Trunk Group Number, CLLI, Signaling Service MML Name, Trunk Group Type,
Queueable, Ring No Answer, Glare, COT percentage, Select Sequence, Satellite Indicator, NPA,
Customer Group ID, Compression Type, Echo Cancellation, External COT, Detect Fax Modem Tone,
Max ACL, ACL Duration, ACC Response Control Inhibit, ISUP Transparency Disabled, AOC Enabled,
Carrier Screening, Originating Carrier ID, NetworkType, Package Type, ACC Response Category Name,
Default Carrier ID National Network ID, Default OLI, Default CHG, Default CHG NOA, Default CHG
NPI, Default DN, Default DN NOA, Default DN NPI, Default DN Pres, Default DN SI, Default Carrier
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-84
OL-1110-23
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
ID Net ID, Default Carrier ID Net Type, MGC Domain, MGC SIP Version, Local Port, Invite Timer T1,
Gen Timer T1, Gen Timer T2, Max Redirect Count, Support 183, From Field, In Session Timer, Out
Session Timer, Hold Timer, Expires Timer, Support Reliable 100, Retry After Timer, Max Forwards,
Gateway RB Tone Support, Wait for Answer Timer, Wait for Originating SDP Timer, Wait for
Terminating SDP Timer, Charge Origin, Send Address in CGPN, CGPN Presentation Restricted,
AInternationalPrefix, ANationalPrefix, BInternationalPrefix, BNationalPrefix, ADigitCCPrefix,
BDigitCCPrefix, BDigitCCrm, CCOrigin, Ta1TimePeriod, Ta2TimePeriod, Ta3TimePeriod,
ExpiryWarnToneType, ExpiryWarnToneDur, CLISelect, GWDefaultCodecString, AllowH323Hairpin,
H323AdjunctLink, FAXsupport, SubscribeNotifySupport, UnsolicitedNotifyMethod,
MinEventSubscribeDuration, MaxSubscriptionDuration, populateSDPInfoInCDR, OD32DigitSupport,
Anumnormalise, Bnumnormalise, GtdCapTypeProp, GtdMsgFmt, IsupTransEarlyBackwardDisabled,
sipMimeBodySupport, EnableIPScreening, SipIPSource, DefaultPN, DefaultPNNOA, DefaultPNNPI,
DefaultPNPres, CallForwardRerouteDisabled, CustomerVPNOnNetTblNum, CustomerVPNid,
CustomerVPNOffNetTblNum, FeatureTransparencyDisabled, SdpXmitToH323Trigger,
GWDefaultATMProfile, PlayAnnouncement, AtmConnectionType, BTechPrefix,
LoopAvoidanceSupport, LoopAvoidanceCounter, MwiStringOFF, MwiStringON,
InhibitIncomingCallingNameDisplay, InhibitOutgoingCallingNameDisplay,
InhibitIncomingConnectedNameDisplay, InhibitIncomingConnectedNumberDisplay,
AOCDefaultTariffId, AOCInvokeType, MidCallCPInterval, CliSelectionForCodeOfPractice3,
InhibitOutgoingConnectedNameDisplay, InhibitOutgoingConnectedNumberDisplay
The customer trunk group file for version 9.6001 will have the following parameters in this particular
order (124 columns)
The fields are: Trunk Group Number, CLLI, Signaling Service MML Name, Trunk Group Type,
Queueable, Ring No Answer, Glare, COT percentage, Select Sequence, Satellite Indicator, NPA,
Customer Group ID, Compression Type, Echo Cancellation, External COT, Detect Fax Modem Tone,
Max ACL, ACL Duration, ACC Response Control Inhibit, ISUP Transparency Disabled, AOC Enabled,
Carrier Screening, Originating Carrier ID, NetworkType, Package Type, ACC Response Category Name,
Default Carrier ID National Network ID, Default OLI, Default CHG, Default CHG NOA, Default CHG
NPI, Default DN, Default DN NOA, Default DN NPI, Default DN Pres, Default DN SI, Default Carrier
ID Net ID, Default Carrier ID Net Type, MGC Domain, MGC SIP Version, Local Port, Invite Timer T1,
Gen Timer T1, Gen Timer T2, Max Redirect Count, Support 183, From Field, In Session Timer, Out
Session Timer, Hold Timer, Expires Timer, Support Reliable 100, Retry After Timer, Max Forwards,
Gateway RB Tone Support, Wait for Answer Timer, Wait for Originating SDP Timer, Wait for
Terminating SDP Timer, Charge Origin, Send Address in CGPN, CGPN Presentation Restricted,
AInternationalPrefix, AnationalPrefix, BInternationalPrefix, BnationalPrefix, ADigitCCPrefix,
BDigitCCPrefix, BDigitCCrm,CCOrigin,Ta1TimePeriod,Ta2TimePeriod, Ta3TimePeriod,
ExpiryWarnToneType, ExpiryWarnToneDur, CLISelect, GWDefaultCodecString, AllowH323Hairpin,
H323AdjunctLink, FAXsupport, SubscribeNotifySupport, UnsolicitedNotifyMethod,
MinEventSubscribeDuration, MaxSubscriptionDuration, populateSDPInfoInCDR, OD32DigitSupport,
Anumnormalise, Bnumnormalise, GtdCapTypeProp, GtdMsgFmt, IsupTransEarlyBackwardDisabled,
sipMimeBodySupport, EnableIPScreening, SipIPSource, DefaultPN, DefaultPNNOA, DefaultPNNPI,
DefaultPNPres, CallForwardRerouteDisabled, CustomerVPNOnNetTblNum, CustomerVPNid,
CustomerVPNOffNetTblNum, FeatureTransparencyDisabled, SdpXmitToH323Trigger,
GWDefaultATMProfile, PlayAnnouncement, AtmConnectionType, BTechPrefix,
LoopAvoidanceSupport, LoopAvoidanceCounter, MwiStringOFF, MwiStringON,
InhibitIncomingCallingNameDisplay, InhibitOutgoingCallingNameDisplay,
InhibitIncomingConnectedNameDisplay, InhibitIncomingConnectedNumberDisplay,
AOCDefaultTariffId, AOCInvokeType, MidCallCPInterval, CliSelectionForCodeOfPractice3,
InhibitOutgoingConnectedNameDisplay, InhibitOutgoingConnectedNumberDisplay, oLocLabel,
tLocLabel
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-85
Chapter 1
Planning for Provisioning
Provisioning a Nailed Configuration
The following are examples of a trunk group file #format3 text formats:
#format3 – 9.4001
1000
TTTT-SS-BB ss7svc1 TDM_ISUP
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
TTTT-SS-BB ss7svc1 TDM_ISUP
N
5 0 10 LIDL 1 0 703 7777 1 0 Loop 0 3 5 1 1 1
1 1111 0 ABC 0 0 0 703 0 0 301 0 0 0 0 202 0 MGC1 SIP2.1 5555 2000 800 6000 2 1 mgcusr
600000 300000 600000 30000 FALSE 90000 10 0 65 10 10 0 1 0 NULL NULL NULL NULL 0 0 NULL
NULL 20 30 3 NULL 1 CLI NULL 0 0 0 0 0 40 0 0 1 0 0 t0 c 1 0 0 0 NULL 0 0 0 0 0 00000000 0
0 0 NULL 0 4 NULL 0 0 NULL NULL 0 0 0 0 1 1 0 0 0 0
#format3 – 9.6001
1000
TTTT-SS-BB ss7svc1 TDM_ISUP
N
5 0 10 LIDL 1 0 703 7777 1 0 Loop 0 3 5 1 1 1
1 1111 0 ABC 0 0 0 703 0 0 301 0 0 0 0 202 0 MGC1 SIP2.1 5555 2000 800 6000 2 1 mgcusr
600000 300000 600000 30000 FALSE 90000 10 0 65 10 10 0 1 0 NULL NULL NULL NULL 0 0 NULL
NULL 20 30 3 NULL 1 CLI NULL 0 0 0 0 0 40 0 0 1 0 0 t0 c 1 0 0 0 NULL 0 0 0 0 0 00000000 0
0 0 NULL 0 4 NULL 0 0 NULL NULL 0 0 0 0 1 1 0 0 0 0 0 0
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 1-31 lists the trunk MML parameter definitions and their associated values.
Table 1-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
from 1 through 65535.
CU
Coding unit
Identifies the coding unit MML name that was previously defined for the VISM card
(this is the external node created for MGCP or SGCP).
ENDPOINT
End point
Text description of the trunk end point (typically a VISM card). Enter as many as 128
characters and enclose in straight quotes.
SPANSIZE
Span size
Span size. Indicates the number of trunks per span.
Value: 1 through 24 for T1, or 1 through 31 for E1.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-86
OL-1110-23
Chapter 1
Planning for Provisioning
Route Analysis
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 1, “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 1-32 lists the routing trunk group MML command parameter definitions and their associated
values.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-87
Chapter 1
Planning for Provisioning
Route Analysis
Table 1-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
characters and enclose in straight quotes. Hyphens (-) can be used.
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_ISUP—Used with SS7 signaling services with switch types of 0, 5, 20, 23,
or 40.
2 = TDM_CAS—Currently not supported.
3 = TDM_TUP—Used with SS7 signaling services with switch type of 5.
4 = IP—Used with EISUP signaling service.
5 = ATM—Used with VSI path signaling service.
6 = TDM_DPNSS—Used with DPNSS protocol family signaling services.
7 =TDM_ PRI—Used with ISDN PRI protocol family signaling services.
8 = TDM_BTNUP—Used with SS7 signaling services with switch type of 5.
9 = IP_SIP—Used for SIP signaling services at the terminating side.
10 = SIP_IN—Used for SIP signaling services at the originating side
11 = CTI—Used for CTI signaling.
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
REATTEMPTS
Reattempts
Identifies the number of times the system reattempts to select the same trunk group
due to congestion. If, after the specified number of reattempts, a trunk group is not
selected, the call is released.
Value range: 0 (default) through 5.
QUEUING
Queuing
Identifies the duration (in seconds) the call will be queued when circuit selection on
a trunk group has failed. The value specified is the time (in seconds) the call is queued
and waits for a circuit to become free. If a circuit becomes free before the time
interval expires, the call is completed. If no circuit becomes available before the
elapsed time, the call is released.
Value range: 0 (default) through 120.
CUTTHROUGH
Cutthrough
Identifies the point in the call process where the trunk is seized from end point to end
point. Value range: 0 (default) through 3.
0 = Undefined
2 = ACM
3 = Answer
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-88
OL-1110-23
Chapter 1
Planning for Provisioning
Route Analysis
Table 1-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
characters and enclose in straight quotes. Hyphens (-) can be used.
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 1-33 lists the route trunk MML command parameter definitions.
Table 1-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
characters and enclose in straight quotes. Hyphens (-) can be used.
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:
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-89
Chapter 1
Planning for Provisioning
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:rttrnkgrp:name="2222",type=0,reattempts=5,queuing=2,cutthrough=3
prov-add:rttrnkgrp:name="3333",type=0,reattempts=1,queuing=1,cutthrough=1
prov-add:rttrnk:name="route1",trnkgrpnum=1111,weightedtg="ON"
prov-ed:rttrnk:name="route1",trnkgrpnum=2222,weightedtg="ON"
prov-ed:rttrnk:name="route1",trnkgrpnum=2222
prov-ed:rttrnk:name="route1",trnkgrpnum=2222
prov-add:rttrnk:name="route2",trnkgrpnum=3333,weightedtg="OFF"
prov-add:rttrnk:name="route3",trnkgrpnum=2222,weightedtg="OFF"
prov-add:rtlist:name="one",rtname="route2",distrib="OFF"
prov-add:rtlist:name="two",rtname="route1",distrib="ON"
prov-add:rtlist:name="three",rtname="route3",distrib="OFF"
prov-stp
Note
Additional trnkgrpnums can be added to the rttrnk with or without enabling the weightedtg parameter.
If the second weightedtg had been set to OFF, then the whole rttrnk would not allow weighted trunk
group based routing. Route1 must be connected to an rtlist with distrib ON since the weighted trunk
group was set to ON.
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 1-34 lists the route list MML command parameter definitions and their associated values.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-90
OL-1110-23
Chapter 1
Planning for Provisioning
Planning for Session Initiation Protocol Provisioning
Table 1-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
enclose in straight quotes. Hyphens (-) can be used.
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:rttrnkgrp:name="1910",type=7,reattempts=1,queuing=0,cutthrough=2
prov-add:rttrnkgrp:name="2744",type=1,reattempts=1,queuing=0,cutthrough=2
prov-add:rttrnkgrp:name="3913",type=7,reattempts=1,queuing=0,cutthrough=2
prov-add:rttrnkgrp:name="3914",type=1,reattempts=1,queuing=0,cutthrough=2
prov-add:rttrnk:name="rt1910",trnkgrpnum=1910
prov-add:rttrnk:name="rt2744",trnkgrpnum=2744
prov-add:rttrnk:name="rt3913",trnkgrpnum=3913
prov-add:rttrnk:name="rt3914",trnkgrpnum=3914
prov-add:rtlist:name="rtlist1910",rtname="rt1910"
prov-add:rtlist:name="rtlist2744",rtname="rt2744"
prov-add:rtlist:name="rtlist3913",rtname="rt3913"
prov-add:rtlist:name="rtlist3914",rtname="rt3914"
Planning for Session Initiation Protocol Provisioning
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.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
OL-1110-23
1-91
Chapter 1
Planning for Provisioning
Planning for Session Initiation Protocol Provisioning
Table 1-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
from 1 through 9999.
URL
SIP URL
SIP proxy service address in the format of IP address, host name, or DNS name.
PORTNUM
Port number
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
characters and enclose in straight quotes. Hyphens (-) can be used.
Cisco PGW 2200 Softswitch Release 9 Provisioning Guide (through Release 9.7)
1-92
OL-1110-23