Table Of Contents

Components and Properties

Components

Network Element Components

Adapter Card

Adjacent Point Code

Association

AXL Server

ISDN BRI Signaling Service

C7 IP Link

Charge

Charge Holiday

CTI Manager

CTI Path

Destination Point Code

D Channel

DNS Parameters

DPNSS Signaling Service

EISUP Signaling Service (sigpath)

Ethernet Interface

External Node

FAS Signaling Service (sigpath)

Files

Intelligent Network Service (INSERVICE) Table

IPFAS Transport Service (previously PRI Signaling Backhaul)

IPINMAPPING

IP Link

IP Route

LABEL

LineXlate

Linkset

Linkset Property

M3UA Key

M3UA Route

MGCP Signaling Service

Multiple IPFAS Services (sigpath)

Multiple Trunk Groups and Trunks

Nailed Trunk (Bearer Channel)

NAS Signaling Service (sigpath)

Originating Point Code

Profile

RASERVER

Routing

Session Set

SGP

SIP IP Link

SIP Signaling Service

SS7 Route

SS7 Signaling Service Properties

SS7 Signaling Service (sigpath)

SS7 Subsystem

SUA Key

SS7 Signaling Gateway Process

Switched Trunk Provisioning

TARIFF

Backhaul TCP Link

TDM Interface

TDM Link

Trunk Group Provisioning

Trunk Group Profile MML Provisioning

GTD Parameter Provisioning

Dial Plan Provisioning Components

Processes

Properties

Protocol Variants

Software Release 9.3(2) Protocol Variants

Software Release 9.4(1) Protocol Variants

Software Release 9.5(2) Protocol Variants

Software Release 9.6(1) Protocol Variants

Components and Properties

---

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

The names and values associated with Cisco PGW 2200 Softswitch components, processes, and properties are used throughout the Cisco PGW 2200 Softswitch system. Frequently, they are parameters used in MML commands. This chapter describes these names and their associated values, in the following sections:

•Components

•Processes

•Properties

Components

This section describes network element (NE) components and dial plan provisioning components. The NE components are used with the PROV commands, and the dial plan provisioning components are used with the NUMAN commands.

Network Element Components

All Components have a name parameter, which is the MML name, and a description, which is a text description. They also must have a parent. If the parent is not specified then it is the root Cisco PGW 2200 Softswitch NE component. The structure of Network Element components is shown in Table A-1.

Table A-1 Network Element Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique ID of this component and component name used in MML commands	The name can be up to any 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be as many as 128 characters.

Adapter Card

The Adapter Card component type represents a card used on the Cisco PGW 2200 Softswitch. Its MML name is as follows:

•MML Name—CARD

---

Note This component is removed in software Release 9.4(1).

---

The Adaptor Card component structure is shown in Table A-2.

Table A-2 Adaptor Card Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
TYPE	Card type	ITK, V35, EN, ATM, or PTI
SLOT	Card Slot	Integer starting at 0. The maximum value is device dependent (0).

Adjacent Point Code

The adjacent point code (APC) component type represents an SS7 point code assigned to an STP with which the Cisco PGW 2200 Softswitch NE needs to communicate. Its MML name is as follows:

•MML Name—APC

The adjacent point code component structure is shown in Table A-3.

Table A-3 Adjacent Point Code Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
NETADDR	Network address	String in dotted notation, for example, 1.1.1.
NETIND	Network indicator	; (0)

Association

The association component represents a Stream Control Transmission Protocol (SCTP) association, which is the connection between the Cisco PGW 2200 Softswitch and a Cisco access server. Its MML name is as follows:

•MML Name—ASSOCIATION

The SCTP association component structure is shown in Table A-4.

Table A-4 Association Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
TYPE	Signaling Type	The type of protocol to be used. Values: M3UA, SUA, or IUA.
SGP	MML name of an SGP (optional)	MML name of a previously configured SGP. Used for M3UA and SUA interfaces.
IPADDR1	First local address	IP_Addr1, IP_Addr2, IP_Addr3, or IP_Addr4.
IPADDR2	Second local address (optional	IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4, or N/A; (N/A).
PORT	Local SCTP port number (optional)	From 1024 through 65535. Defaults to 9900 for IUA. Defaults to 2905 for M3UA. Defaults to 14001 for SUA.
PEERADDR1	The highest priority destination address	IP address.
PEERADDR2	The lowest priority destination address (optional)	IP address; (0.0.0.0).
PEERPORT	Destination SCTP port number. (optional)	From 1024 through 65535. Defaults to 9900 for IUA. Defaults to 2905 for M3UA. Defaults to 14001 for SUA.
EXTNODE	MML name of an external node (optional)	MML name of a previously configured external node. Used in IUA interfaces.
IPROUTE1	MML name of first IPROUTE (optional)	MML name of a previously configured IPROUTE.
IPROUTE2	MML name of second IPROUTE (optional)	MML name of a previously configured IPROUTE.
RCVWIN	Number of bytes to advertise for the local receive window (optional)	From 1500 through 65535; (18000).
MAXINITRETRANS	Maximum number of times to retransmit SCTP INIT message (optional)	0 through 100; (10). 0 means use the SCTP internal default.
MAXINITRTO	Maximum initial timer retransmission value (optional)	0, 300 through 3000; (2000). 0 means use the SCTP internal default.
MAXRETRANS	Maximum number of retransmissions over all destination addresses before the association is declared failed (optional)	From 1 through 10; (5). Note This value must not exceed MAXRETRANSDEST * the number of destinations.
CUMSACKTO	Maximum time after a datagram is received before a SCPT SACK is sent (optional)	From 100 through 500, in milliseconds; (300).
BUNDLETO	Maximum time SCTP will wait for other outgoing datagrams for bundling (optional)	From 100 through 600, in milliseconds; (100).
MINRTO	Minimum value allowed for the retransmission timer (optional)	From 300 through 3000, in milliseconds; (300).
MAXRTO	Maximum value allowed for the retransmission timer (optional)	From 1000 through 3000, in milliseconds; (3000).
HBTO	Time between heartbeats. The heartbeat is this value plus the current retransmission timeout value (optional)	The value can be 0, or from 300 through 10000, in milliseconds; (2000). 0 means disabled.
IPPRECEDENCE	Internet Protocol Precedence. The binary value is placed in the IP PRECEDENCE portion of the Type Of Service field for outgoing SCTP datagrams (optional)	ROUTINE 000 PRIORITY 001 IMMEDIATE 010 FLASH 011 FLASH-OVERRIDE 100 CRITICAL 101 INTERNET 110 NETWORK; (ROUTINE) 111
DSCP	Differential Service Code Point. (Where EF is Expedited Forward, AF is Assured Forward, and DP is Drop Precedence). The binary value is placed in the DSCP portion of the Type Of Service field for outgoing SCTP datagrams (optional)	EF 101110 AF11 Class 1 Low DP 001010 AF12 Class 1 Medium DP 001100 AF13 Class 1 High DP 001110 AF21 Class 2 Low DP 010010 AF22 Class 2 Medium DP 010100 AF23 Class 2 High DP 010110 AF31 Class 3 Low DP 011010 AF32 Class 3 Medium DP 011100 AF33 Class 3 High DP 011110 AF41 Class 4 Low DP 100010 AF42 Class 4 Medium DP 100100 AF43 Class 4 High DP 100110 N/A; (N/A)
MAXRETRANSDEST	Maximum number of retransmissions to either PEERADDR1 or PEERADDR2 before call is declared failed (optional)	From 1 through 10; (3).

The following parameters cannot be modified:

•NAME

•EXTNODE

•TYPE

•SGP

The following rules apply when you are creating or editing SCTP associations:

•Only one association with a type of IUA can be assigned to an external node.

•If the type of the association is IUA, the associated external node must have its ISDN signaling type set to IUA, and that external node must be able to support IUA signaling.

•If two associations have the same port value, the values of IPADDR1 and IPADDR2 must both be the same or both different.

•The values of IPADDR1 and IPADDR2 must be different.

•If the value of IPPRECEDENCE is not ROUTINE, the value of DSCP must be N/A.

•If the value of DSCP is not N/A, the value of IPPRECEDENCE must be ROUTINE.

•The value of MAXRTO must be greater than or equal to the value of MINRTO.

•When a peer IP address (PEERADDR1 or PEERADDR2) is not on the local subnet of IPADDR1 or IPADDR2, that peer IP address cannot be on the subnet of any other local interface, even if it is not defined within the Cisco PGW 2200 Softswitch software.

•When a peer IP address (PEERADDR1 or PEERADDR2) is not on the local subnet of IPADDR1 or IPADDR2, an IP route (IPROUTE1 or IPROUTE2) must be specified. IPROUTE1 is specified for IPADDR1, and IPROUTE2 is specified for IPADDR2.

•When an IP route is specified, the values set in PEERADDR1 and PEERADDR2 are checked against the DESTINATION and NETMASK values of the IP route(s) to ensure that the IP route is valid.

•When an IP route is specified, its value for IPADDR must match the related IP address of the association. In other words, IPROUTE1 should have an IPADDR that matches IPADDR1 in the association, and IPROUTE 2 should have an IPADDR that matches IPADDR2 in the association.

•When an IP route is not specified, the IP address resolved from the PEERADDR1 or PEERADDR2 parameter is checked against the defined IP routes to see if it should be assigned to one of those IP routes. If the peer address is on the same subnet as an IP route, the link should use that IP route.

•The value of PEERADDR1 cannot be 0.0.0.0 or 255.255.255.255, and the value of PEERADDR2 cannot be 255.255.255.255.

•When a hostname is specified for a peer IP address, the hostname must resolve to an IP address.

•PEERADDR1 and PEERADDR2 can resolve to the same IP Address. If the external node only has one IP address and two IP addresses (IPADDR1 and IPADDR2) are defined, PEERADDR2 should be set to the same value as PEERADDR1.

•Associations, session sets, IP links, SIP links, and SS7 signaling gateway links that share a peer address (that is, PEERADDR, PEERADDR1, or PEERADDR2) must be assigned directly or indirectly to the same external node.

•When you are deleting an association, and a NASPATH uses the same external node, a warning message is issued to inform the you that the NASPATH must also be deleted. If it hasn't when the provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.

•The value of PORT cannot be set to the same value as the PORT attribute of any IP link, session set, SIP link, or SS7 signaling gateway link.

•If a value for IPADDR2 or PEERADDR2 is specified, values for IPADDR1 or PEERADDR1 must also be specified. In other words, you cannot have one local address and two remote addresses, or two local addresses and one remote address.

•An IP link, session set, SS7 signaling gateway link, or an association with a different external or signaling gateway node cannot use the resolved value set in PEERADDR1 or PEERADDR2.

•Only one association can be defined for an SS7 signaling gateway process (SGP).

•A value for EXTNODE can be defined only when the association type is IUA.

•A value for SGP can be defined only when the association type is M3UA or SUA.

•The maximum number of associations with a type of M3UA is defined in the XECfgParm.dat parameter, M3UA.maxSgp.

•The maximum number of associations with a type of SUA is defined in the XECfgParm.dat parameter, SUA.maxSgp.

AXL Server

The AXL server component represents the AXL server. Its MML name is as follows:

•MML Name—AXLSERVR

---

Note This component is added in software Release 9.6(1).

---

The AXL server component structure is shown in Table A-5.

Table A-5 AXLSERVR Component Structure 

Parameter MML Name	Parameter Description	Parameter Value (Default)
NAME	Unique component name used in MML commands for the AXL server	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.
IPADDR1	First local address	IP_Addr1, IP_Addr2, IP_Addr3, or IP_Addr4
IPADDR2	Second local address (optional)	IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4, or N/A; (N/A)
PORT	Local CTI port number (optional)	From 1024 through 65535. Defaults to 2750.
PEERADDR1	The highest priority destination address	IP address
PEERADDR2	The lowest priority destination address (optional)	IP address; (0.0.0.0).
PEERPORT	Destination CTI port number. (optional)	From 1024 through 65535. Defaults to 2750.
CTIPATH	CTI sigpath MML name	MML name of a previously configured CTI sigpath.
IPROUTE1	MML name of first IPROUTE (optional)	MML name of a previously configured IPROUTE.
IPROUTE2	MML name of second IPROUTE (optional)	MML name of a previously configured IPROUTE.
USERNAME	User name for AXL server authentication	N/A
PASSWORD	Password for AXL server authentication	N/A

ISDN BRI Signaling Service

The ISDN BRI signaling service component represents a static IP route. Its MML name is as follows:

•MML Name—BRIPATH

---

Note This component is added in software Release 9.5(2).

---

The ISDN BRI signaling service component structure is shown in Table A-6.

Table A-6 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 ISDN BRI voice gateway external node.
MDO	MDO file name	A valid protocol name. You can use the following files: •ETS_300_102 •Q931 •ETS_300_172
SIDE	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 ISDN BRI signaling services:

•You must define the TCPLINK parameter with the same EXTNODE attribute that its associated BRIPATH has. If the TCPLNK is not defined when the BRIPATH is added/edited, a warning is issued. If the TCPLINK is not defined when the provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.

•If the TCPLINK with the same EXTNODE value as the BRIPATH is deleted, a warning message is issued to inform you that the BRIPATH must also be deleted. If the BRIPATH is not deleted when the provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.

•A maximum of 2000 BRIPATHs can be provisioned on your Cisco PGW 2200 Softswitch.

C7 IP Link

The C7 IP Link component type represents a C7 IP link used on the Cisco PGW 2200 Softswitch. These links are used to communicate with the signal termination point (2600). Its MML name is as follows:

•MML Name—C7IPLNK

The C7 IP link component structure is shown in Table A-7.

Table A-7 C7 IP Link Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
PRI	Priority	Integer greater than 0; (1)
TIMESLOT	The physical (WAN Interface Card (WIC) slot (serial port) information on the ITP-L.	Valid values are: 0, 1, 2, or 3. Set to 1 when using the signal processor; otherwise 0; (0)
SLC	Signaling link code	From 0 through 15; (1)
LNKSET	Signaling service this IP supports	MML name of a previously defined Linkset or index of the Linkset for SNMP.
SESSIONSET	Session Set MML name.	MML name of a previously configured Session Set.

Charge

The Charge component type is used to provision the Charge table. Its MML name is as follows:

•MML Name—CHARGE

The Charge component structure is shown in Table A-7.

Table A-8 Charge Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
CHORIG	Charge Origin (optional)	From 0 through 9999; (0)
CHDEST	Charge Destination	From 0 through 9999
DOW	Day of Week (optional)	SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY, or DEFAULT; (DEFAULT)
TARIFFDESC	Tariff Description	A string of tariff and time changes in the format: "<tariff 1 timeChange 1 - tariff n timeChange n>". The timeChange value must be divisible by 15 minutes (for example, 0030, 0315, or 2115). The timeChange value must be 2400 if the last field is a timeChange value.

Charge Holiday

The Charge Holiday component type is used to provision the Charge Holiday table. Its MML name is as follows:

•MML Name—HOLIDAY

The Charge Holiday component structure is shown in Table A-7.

Table A-9 Charge Holiday Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DATE	Date of the holiday	A valid date in the format YYYYDDMM.
HDAY	The holiday value	HOL1, HOL2, or HOL3.

CTI Manager

The CTI manager component represents the CTI manager. Its MML name is as follows:

•MML Name—CTIMGR

---

Note This component is added in software Release 9.6(1).

---

The CTI manager component structure is shown in Table A-10.

Table A-10 CTIMGR Component Structure 

Parameter MML Name	Parameter Description	Parameter Value (Default)
NAME	Unique component name used in MML commands for the AXL server	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.
IPADDR1	First local address	IP_Addr1, IP_Addr2, IP_Addr3, or IP_Addr4
IPADDR2	Second local address (optional)	IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4, or N/A; (N/A)
PORT	Local CTI port number (optional)	From 1024 through 65535. Defaults to 2750.
PEERADDR1	The highest priority destination address	IP address
PEERADDR2	The lowest priority destination address (optional)	IP address; (0.0.0.0).
PEERPORT	Destination CTI port number. (optional)	From 1024 through 65535. Defaults to 2750.
CTIPATH	CTI sigpath MML name	MML name of a previously configured CTI sigpath.
IPROUTE1	MML name of first IPROUTE (optional)	MML name of a previously configured IPROUTE.
IPROUTE2	MML name of second IPROUTE (optional)	MML name of a previously configured IPROUTE.
USERNAME	User name for CTI manger authentication	N/A
PASSWORD	Password for CTI manger authentication	N/A
CTIVERSION	The Cisco CallManager CTI protocol version	The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.

The following rules apply when creating or editing CTI Manager:

•IPADDR1 and IPADDR2 must be different.

•When an IPROUTE1 and/or IPROUTE2 are specified, the IP address(es) resolved from the PEERADDR1 and PEERADDR2 attributes must be checked against the DESTINATION and NETMASK attributes of the IPROUTE(s) to verify that the IPROUTE is valid.

•When IPROUTE1 is specified, the IPADDR must match the IPADDR1.

•When IPROUTE2 is specified, the IPADDR must match the IPADDR2.

•When IPROUTE1 or IPROUTE2 is not specified, the IP address resolved from the PEERADDR1 or PEERADDR2 attribute must be checked against the defined IPROUTES to verify that it should not be assigned to one of the IPROUTEs. If the PEERADDR is on the same subnet as an IPROUTE, the link should use that IPROUTE.

•PEERADDR1 cannot be 0.0.0.0 or 255.255.255.255.

•PEERADDR2 cannot be 255.255.255.255.

•When a hostname is used for PEERADDR1 or PEERADDR2, the hostname must resolve to an IP address.

•PEERADDR1 and PEERADDR2 can resolve to the same IP address. If External node only has one IP Address, that is, IPADDR2 is defined; then set PEERADDR2 to the same value as PEERADDR1.

•If IPADDR2 or PEERADDR2 is specified, then they must both be specified. In other words, you cannot have one local address and two remote addresses, or two local addresses and one remote address.

CTI Path

The CTI path component type represents the CTI signaling service. Its MML name is as follows:

•MML Name—CTIPATH

---

Note This component is added in software Release 9.6(1).

---

The CTI path component structure is shown in Table A-11.

Table A-11 CTIPATH Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
EXTNODE	External node MML name	MML name of a previously defined external node or index of the external node for SNMP
MDO	MDO file name	Valid protocol name from variants.dat.

Destination Point Code

The destination point code (DPC) component type represents an SS7destination point code with which the Cisco PGW 2200 Softswitch NE communicates. Its MML name is as follows:

•MML Name—DPC

The destination point code component structure is shown in Table A-12.

Table A-12 Destination Point Code Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique ID of this component and 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 any 128 characters.
NETADDR	Network address	String in dotted notation, for example, 1.1.1.
NETIND	Network indicator	; (0)

D Channel

The D-channel component type represents a D-channel used on the Cisco PGW 2200 Softswitch. There can be a maximum of two channels per IPFAS (one primary and 1 backup). Its MML name is as follows:

•MML Name—DCHAN

The D-channel component structure is shown in Table A-13.

Table A-13 D-Channel Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique ID of this component and 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 any 128 characters.
PRI	Priority	Integer greater than 0; (1)
SVC	Signaling service this IP supports	MML name of a previously defined IPFAS service
SESSIONSET	Session Set MML name.	MML Name of a previously configured Session Set.
TCPLINK	MML name of TCP link (restricted)	MML name of a previously provisioned TCP link. This parameter is used only for D-channels associated with ISDN BRI signaling services. This parameter is added in software Release 9.5(2).
SIGSLOT	Physical slot on the gateway where the T1/E1 is plugged into	Integer 0 through 63; (0) Note Set this parameter to 0 for ISDN BRI D-channels when the associated external node is a C17xx.
SIGPORT	Physical port on the gateway on the slot	Integer 0 through 167; (0)
SUBUNIT	Required for ISDN BRI D-channels	Integer 0 or 1; (0). This parameter is added in software Release 9.5(2).

The following rules apply when you are creating or editing D-channels:

•Backup D-channels for ISDN BRI signaling services are not supported.

•The priority for ISDN BRI D-channels should be set to 1.

•Session sets are used only in support of IPFAS D-channels.

•TCP links are used only in support of ISDN BRI D-channels.

•Up to 1000 D-channels can be provisioned against a single IP address and port combination used by your Backhaul TCP links. Since the Cisco PGW 2200 Softswitch supports a maximum of two IP address and port combinations, you can provision a maximum of 1000 D-channels for an ISDN BRI signaling service.

DNS Parameters

This command is used to configure domain name system (DNS)-related parameters to support SIP URL. Its MML name is as follows:

•MML Name—DNSPARAM

The DNS component structure is shown in Table A-14.

Table A-14 DNS Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DNSSERVER1	IP address of primary DNS server	This is mandatory and has no default value.
DNSSERVER2	IP address of secondary DNS server	This is optional.
CACHESIZE	Maximum cache entries used to hold DNS entries	Integer greater than 0; (500)
TTL	The time-to-live interval for DNS entries (in seconds)	Integer greater than 0; (3600)
POLICY	Policy for selection of DNS entries	Hierarchy or round-robin; (hierarchy)
QUERYTIMEOUT	The timeout interval for DNS queries (in milliseconds)	Integer greater than 0; (1000)
KEEPALIVE	The time interval in seconds to check if DNS server is responding	Integer greater than 0; (30)

DPNSS Signaling Service

The DPNSS signaling service component type represents a DPNSS signaling path that is backhauled over IP to/from a Network Access Server (destination). Its MML name is as follows:

•MML Name—DPNSSPATH

The DPNSS signaling service component structure is shown in Table A-15.

Table A-15 DPNSS Signaling Service Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	IP route name	The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
DESC	Component description	The description can be up to any 128 characters.
MDO	MDO file name	Valid protocol name from variants.dat. Note DPNSS_BTNR188 is the only valid MDO protocol variant for this signaling service.
EXTNODE	External node MML name	MML name of a previously defined external node.
CUSTGRPID	Customer group ID	Four digit ID; (0000).
ABFLAG	DPNSS side	`a' or `b' side, `n' for not applicable; (n)
SIGSLOT	Physical slot on the NAS defining the NFAS Group (optional)	An integer, 0 through 63; (0).
SIGPORT	Physical port on the slot of NAS defining the NFAS Groupl. (optional)	An integer, 0 through 167.
ORIG LABEL	Originating call control (OCC) side location label. Used for Call Limiting feature.	As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).
TERM LABEL	Terminating call control (TCC) side location label. Used for Call Limiting feature.	As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).

The following parameters cannot be modified:

•NAME

•EXTNODE

The following rules apply when creating or editing DPNSS signaling paths:

•The maximum number of combined DPNSSPATHs and IUA NASPATHs per IUA External Node is 112.

•An ASSOCIATION must be defined with same EXTNODE attribute as the DPNSSPATH. If this ASSOCIATION hasn't been defined when the DPNSSPATH is added/edited, a warning is issued. If the ASSOCIATION still hasn't been defined when provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.

•If the ASSOCIATION with the same EXTNODE value as the DPNSSPATH is deleted, a warning message is issued to inform the user that the DPNSSPATH must also be deleted. If it hasn't when the provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.

EISUP Signaling Service (sigpath)

The EISUP Signaling Service (sigpath) component is a network element that represents an EISUP signaling service or signaling path to another NE (destination). Its MML name is as follows:

•MML Name—EISUPPATH

The signaling service path component structure is shown in Table A-16.

Table A-16 Signaling Service Path Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
EXTNODE	External node MML name	MML name of a previously defined external node or index of the external node for SNMP
CUSTGRPID	Customer group ID	Four digit ID; (0000)
CUSTGRPTBL	Customer group table index	Four digit index; (0101)
ORIG LABEL	Originating call control (OCC) side location label. Used for Call Limiting feature.	As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).
TERM LABEL	Terminating call control (TCC) side location label. Used for Call Limiting feature.	As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).

Ethernet Interface

The Ethernet interface component type represents an Ethernet interface used on the Cisco PGW 2200 Softswitch. Its MML name is as follows:

•MML Name—ENETIF

---

Note This component is removed in software Release 9.4(1).

---

The Ethernet interface component structure is shown in Table A-17.

Table A-17 Ethernet Interface Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
CARD	Card which supports this Ethernet interface	MML name of a previously defined card or index of the card for SNMP

External Node

The external node component type represents another node with which the Cisco PGW 2200 Softswitch communicates. Its MML name is as follows:

•MML Name—EXTNODE

Table A-18 External Node Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
TYPE	The type of the External Node	Valid values are from extNodeTypes.dat. Refer to "Planning Media Gateway External Nodes" section for a list of node types.
ISDNSIGTYPE	ISDN signaling type	Valid values are IUA or N/A (default is N/A). This parameter is added in software Release 9.4(1).
GROUP	M3UA or SUA group number	Value is 1-100 for M3UA or SUA nodes. Value is 0 for nodes that do not support M3UA or SUA. This parameter is added in software Release 9.4(1).

The following rules apply when creating or editing external nodes:

---

Note DESC is the only parameter for this command that can be modified:

---

The following rules apply when you are creating or editing external nodes:

•TYPE must be one of the valid external node types.

•The maximum number of external nodes with an ISDNSIGTYPE of IUA is 256.

FAS Signaling Service (sigpath)

The FAS signaling service (sigpath) component type represents a FAS signaling service or signaling path to a particular destination using either ISDN-PRI or DPNSS. The MML name is as follows:

•MML Name—FASPATH

---

Note This component is removed in software Release 9.4(1).

---

The FAS Signaling Service component structure is shown in Table A-19.

Table A-19 FAS Signaling Service Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
SIDE	Q.931 call model side	User for user side and network for network side; (network)
MDO	MDO file name	Valid protocol name from variants.dat. Note Limited to any MDO variant from either the ISDNPRI or DPNSS protocol families.
CUSTGRPID	Customer ID	Four digit ID; (0000)
CUSTGRPTBL	Customer Table index	Four digit index; (0101)
ABFLAG	DPNSS side	`a' or `b' side, `n' for not applicable; (n)
CRLEN	Call reference length	1 for 1 byte or 2 for 2 byte call reference length; (2 for ISDNPRI and 0 for DPNSS)

Files

Files component type represents files used to generate .dat files on the Cisco PGW 2200 Softswitch. The MML name is as follows:

•MML Name—FILES

The Files component structure is shown in Table A-20.

Table A-20 Files Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	File type	TKGFile for trunk group file, BCFile for bearer channel file, AWhiteFile for A number white list files, ABlackFile for B number black list files, BWhiteFile for B number white list files and BBlackFile for B number black list files
FILE	File name	File name. File should be present in the etc/cust_specific directory.
ACTION	Action to be performed on the files.	Import for converting customer files into.dat files. Export for converting .dat files into customer files. Export is not currently supported for the screening files.

Intelligent Network Service (INSERVICE) Table

The intelligent network service component allows MML commands to be used to provision some elements, which are in the INSERVICE table, in the Trigger table. Its MML name is as follows:

•MML Name - INSERVICE

The intelligent network service table component structure is shown in Table A-21.

Table A-21 INSERVICE Table Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
SKORTCV	Service key	Integer. 0 through 65535 (0). Service key value that specifies the feature that caused the trigger to be hit (ITU / ETSI INAP only). Otherwise it is the trigger criteria value.
GTORSSN	Global title or Sub-System Number.	Text string. Route by global title (ROUTEBYGT) or route by subsystem number (ROUTEBYSSN). 0 = ROUTEBYGT (Route by global title) 1 = ROUTEBYSSN (Sub-System Number)
GTFORMAT	Global title format	Text string. How to use Global Title; SCCP Called Party Address, Address indicator field. User provisions the string value. For example, NOGT. 0 = NOGT (No global title. Use this when routing by SSN) 1 = GTTTNBRENC (Use global title translation type numbering scheme encoding scheme) 2 = GTTT (Use global title translation type) 3 = GTONLY (Use global title only) 4 = UNKNOWN (Unknown)
MSNAME	Message Sending Name	As many as 20 alphanumeric characters.

The following rules are used to support INSERVICE table provisioning.

•Global title format (GTFORMAT) must be set to NOGT if the GTORSSN parameter is set to ROUTEBYSSN. Otherwise, GTFORMAT must be set to a value other that NOGT.

•The MSNAME must exist in the MessageSendingName table in trigger.dat.

•Only one entry can exist in the INSERVICE table for each MSNAME.

•The inService.dat ID should be consistent. You cannot delete the current inService entry.

IPFAS Transport Service (previously PRI Signaling Backhaul)

The IPFAS transport service component type represents the FAS over IP transport service or signaling path from a media gateway to a Cisco PGW 2200 Softswitch. Its MML name is as follows:

•MML Name—IPFASPath

The IPFAS transport service component structure is shown in Table A-22.

Table A-22 IPFAS Transport Service Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
EXTNODE	External node MML name	MML name of a previously defined external node or index of the external node for SNMP.
SIDE	Q.931 call model side	User for user side and network for network side; (network).
MDO	MDO file name	Valid protocol name from variants.dat.
CUSTGRPID	VNET ID	Four digit ID; (0000).
CUSTGRPTBL	VNET Table index	Four digit index; (0101).
ABFLAG	DPNSS side	`a' or `b' side, `n' for not applicable; (n).
CRLEN	Call reference length	1 for 1 byte or 2 for 2 byte call reference length; (0).
ORIG LABEL	Originating call control (OCC) side location label. Used for Call Limiting feature.	As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).
TERM LABEL	Terminating call control (TCC) side location label. Used for Call Limiting feature.	As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).

IPINMAPPING

The ipinmapping component type allows you to define mapping between a single SIP or EISUP interface and multiple IP trunk groups using incoming IP address, subnet mask, and port number. Its MML name is as follows:

•MML Name—IPINMAPPING

The IP link service component structure is shown in Table A-24.

Table A-23 Ipinmapping Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
Name	The primary key to identify an ipinmapping entry	A unique name used to describe the ipinmapping rule entry. This field must have a unique value.
Desc	Description	A description of the trunk group.
Sigsvc	SIP sigpath or EISUP sigpath	The signal path to which the ipinmapping rule applies.
AllowedIP	Allowed IP Address	The incoming SIP IP address allowed on the trunk. This parameter is optional.
AllowedIPNetMask	Allowed Net Mask	The subnet mask allowed on the trunk. This parameter is optional. Note If this parameter is blank, the PGW uses the default subnet mask value of 255.255.255.255.
Sipport	Allowed SIP Port	The SIP TCP or UDP port number allowed on the trunk. This parameter is for SIP sigpaths only. The sipport parameter is optional.
Trnkgrpnum	Trunk group number	The number used to identify the trunk group.

Parameter Analysis

The PGW compares incoming traffic against ipinmapping entries in the following order:

SIP

1. IP address and port number

2. IP address only

3. Port number only

EISUP

1. IP address only

Analysis Criteria

For incoming IP traffic to match an ipinmapping entry, the following criteria must be true:

•IP address and port number:

–The incoming IP address falls within the address range defined by the AllowedIP and AllowedIPNetMask parameters.

–The destination port of the incoming SIP message matches the port number defined by the sipport parameter.

•IP address only:

–The incoming IP address (the SIP proxy source IP or EISUP H323SourceAddress) falls within the address range defined by the AllowedIP and AllowedIPNetMask values.

•Port number only:

– The destination port of the incoming SIP message matches the sipport defined in the ipinmapping entry.

When the PGW finds a match between incoming traffic and an ipinmapping entry, it forwards the traffic to the trunk group defined for that ipinmapping entry.

IP Link

The IP link component type represents an IP link used on the Cisco PGW 2200 Softswitch. IP links are used to communicate with the access control devices, such as a NAS. Its MML name is as follows:

•MML Name—IPLNK

The IP link service component structure is shown in Table A-24.

Table A-24 IP Link Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique ID of this component and 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.
IF	Ethernet interface MML name	MML name of a previously defined ENETIF or index of the ENETIF for SNMP.
PORT	Local port number	Any valid IP port number greater than 1024 (Recommended setting of 2427 for MGCP and SGCP).
PRI	Priority	Integer greater than 0; (1).
PEERADDR	Remote IP address	IP address; (0.0.0.0). This may also be specified as a hostname or a DNS name.
PEERPORT	Remote port	Any valid IP port number greater than 1024 (Recommended setting of 2427 for MGCP and SGCP)
IPADDR	Local logical IP address	IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4.
SVC	Signaling service this IP supports	MML name of a previously defined signal service or index of the signal service for SNMP.
NEXTHOP	Next hop address	IP address or hostname of the next hop; (0.0.0.0). This parameter is removed in software Release 9.4(1).
NETMASK	Subnet mask address	Subnet mask address; (255.255.255.255). This parameter is removed in software Release 9.4(1).
IPROUTE	IP route MML name	MML name of a previously defined IPROUTE. This parameter is added in software Release 9.4(1)T.

The following rules apply when you are creating or editing IP links:

•If the SVC is a NASPATH, then the ISDNSIGTYPE of the EXTNODE must be N/A.

•If the SVC is a NASPATH, then the port number must be an odd number.

•If the SVC is a NASPATH, then the local and remote ports must be the same.

•The maximum number of links per port is defined by the XECfgParm.dat parameter, maxNumLinks.

•Links using the same SVC must have the same port number.

•Links using the same SVC must have the same peer port number.

•You cannot have more than two links using the same SVC and port number.

•Each peer address is unique per external node.

•When an IPROUTE is specified, the IP address resolved from the PEERADDR attribute is checked against the DESTINATION and NETMASK attributes of the IPROUTE to ensure that the IPROUTE is valid.

•When an IPROUTE is specified, the IPADDR must match the IPADDR of the IP link.

•When an IPROUTE is not specified, the IP address resolved from the PEERADDR attribute is checked against the defined IPROUTES to ensure that it is not assigned to one of the IPROUTEs. If the PEERADDR is on the same subnet as an IPROUTE, the link uses that IPROUTE.

•The PORT attribute cannot have the same value as the PORT attribute of any ASSOCIATION, SESSIONSET, or SIPLNK.

•The PORT attribute cannot be set to the same value as the PORT attribute of another IPLNK with a different SVC type. That is, the PORT value of an IPLNK supporting an NASPATH SVC cannot be the same as the PORT value of an IPLNK supporting an MGCPPATH or EISUPPATH SVC.

•Another IPLNK, SESSIONSET, or ASSOCIATION with a different EXTNODE cannot use the resolved value of PEERADDR.

•For IP links under an MGCP service, the PRI value must be 1 or 2.

IP Route

The IP route represents a static IP route. Its MML name is as follows:

•MML Name—IPROUTE

The IP route component structure is shown in Table A-25.

Table A-25 IPROUTE Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DEST	Destination hostname or IP address	IP Address in decimal dot notation or hostname that is less than or equal to 32 characters.
NETMASK	Subnet mask of Destination (optional)	IP Address in decimal dot notation. (255.255.255.255)
NEXTHOP	Next hop router IP address	IP Address or hostname that is less than or equal to 32 characters, or one of the following property names defined in XECfgParm.dat: IP_NextHop1, IP_NextHop2, IP_NextHop8, IP_Addr1, IP_Addr2, or IP_Addr4.
IPADDR	Local IP address	IP_Addr1, IP_Addr2, IP_Addr3, or IP_Addr4.
PRI	Priority	1 through 65535; (1).

---

Note NAME is the only parameter for this command that cannot be modified.

---

The following rules apply when creating or editing IP Routes:

•The NETMASK attribute is validated by the system. For your provisioning set-up to work correctly, its value (when converted to binary) must have at least one leading 1 and cannot have any trailing 1s after the first 0. The values 255.255.0.0 and 255.255.255.128 are valid. The values 0.0.255.255, 255.0.0.255, and 0.0.0.0 are invalid.

•Ensure the destination resolves to a non-zero address.

•When the resolved destination address is bit ORed with the netmask value, the result is equal to the netmask (for example, a destination of 10.11.12.13 and a netmask of 255.255.0.0 would be invalid because the ORed result would be 255.255.12.13, which is not equal to 255.255.0.0).

•The combination of DESTINATION, NETMASK, and IPADDR must be unique for each IP Route.

•The combination of DESTINATION, NETMASK, and PRI must be unique for each IP Route.

•When an IP Route is specified in a link object (for example, IPLNK, SESSIONSET, or ASSOCIATION), the IP address resolved from the PEERADDR attribute must be checked against the DESTINATION and NETMASK attributes to verify the IPROUTE is valid.

•When an IP Route is specified in a link object (for example, IPLNK, SESSIONSET, or ASSOCIATION), the IPADDR must match the IPADDR of the link.

•When an IPROUTE is not specified for a link object (having that option), the IP Address resolved from the PEERADDR attribute must be checked against the defined IPROUTES to verify that it should not be assigned an IPROUTE. If the PEERADDR is on the same subnet as the DESTINATION (based on the NETMASK), and if the IPADDR matches the IPADDR of the link object, then use IPROUTE.

•If the NEXTHOP attribute is a hostname or symbolic name from XECfgParm.dat, it can resolve to the address 0.0.0.0, which indicates the IPROUTE is not used. The IPROUTE status shows up in the rtrv-iproute:all command output when in the OOS, OFF_DUTY state.

•If the resolved NEXTHOP address is not 0.0.0.0, it must be on the same subnet of the IPADDR.

LABEL

The LABEL component represents the number of calls allowed on a location. Its MML name is as follows:

•MML name—LABEL

The LABEL component structure is shown in Table A-26.

Table A-26 LABEL Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (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.
CALL LIMIT	Maximum number of calls allowed on one location label	0 through 6000, integer value 0 (default)

---

Note NAME is the only parameter for this command that cannot be modified.

---

LineXlate

The linexlate component type represents a line e number and internal number translation. Its MML name is as follows:

•MML Name—LINEXLATE

The linexlate component structure is shown in Table A-27.

Table A-27 NOA Provisioning Parameters 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique ID of this component and component name used in MML commands	The name can be up to any 20 alphanumeric characters. No special characters other than "-" are allowed. Names 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. 1 = NOA
DIRECTION	Direction in which the message is going, either into or out of the Cisco PGW 2200 Softswitch. This is not ingress or egress.	0 = in 1 = out
NUMBER	A number representing a specific number type in the protocol message.	0 = called 1 = calling 2 = original called 3 = redirecting 4 = redirection 5 = generic
INTNOA	Internal NOA value.	Any 7-bit value, 0 through 127, no restrictions.
EXTNOA	The value of the NOA field in the protocol message.	Any 7-bit value, 0 through 127, no restrictions.

Linkset

The linkset component type represents a linkset in an SS7 network used by the Cisco PGW 2200 Softswitch to communicate with an STP. Its MML name is as follows:

•MML Name—LNKSET

The linkset component structure is shown in Table A-28.

Table A-28 Link Set Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
APC	Adjacent point code	MML name of a previously defined adjacent point code or index of the adjacent point code for SNMP.
PROTO	Protocol family	SS7-ANSI, SS7-ITU, SS7-China, SS7-Japan, or SS7-UK.
TYPE	Transport type	TDM for TDM linksets or IP for IP linksets; (TDM).

Linkset Property

The linkset property component type represents the configuration parameters that you can use to tune linkset communications. Its MML is as follows:

•MML Name—LNKSETPROP

The linkset component structure is shown in Table A-29.

Table A-29 Linkset Property Component Structure 

Parameter MML Name	Parameter Description	Default Value	Units
mtp2AermEmgThr	Alignment error rate monitor threshold duration for emergency operation. Value: One message. This property is removed in software Revision 9.3(1) and later.	1	Messages
mtp2AermNrmThr	Alignment error rate monitor threshold duration for normal operation. Value range: 1 through 4 messages. This property is removed in software Revision 9.3(1) and later.	4	Messages
mtp2CongDiscard	Discard frames upon entering congestion at MTP2. Set to true or false. This property is removed in software Revision 9.3(1) and later.	False
mtp2LssuLen	Link status signal unit, status field length. Specify one or two. This property is removed in software Revision 9.3(1) and later.	SS7-ANSI = 1 SS7-UK = 1 SS7-CHINA = 1 SS7-ITU = 1 SS7-Japan = 2	Octets
mtp2MaxAlignRetries	Maximum number of attempts to align link before declaring it out-of-service (OOS). Value range: 1 through 10 attempts. 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.	5	Attempts
mtp2MaxMsuFrmLen	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.	272	Octets
mtp2MaxOutsFrames	The maximum number of 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.	127	Frames
mtp2ProvingEmgT4	Emergency proving period. Value range: 5 through 7 tenths of a second. This property is removed in software Revision 9.3(1) and later.	SS7-ANSI = 6 SS7-UK = 6 SS7-CHINA = 6 SS7-ITU = 6 SS7-Japan = 30	Tenths of a second
mtp2ProvingNormalT4	Normal proving period. Value range: 1 through 3 seconds. This property is removed in software Revision 9.3(1) and later.	SS7-ANSI = 23 SS7-UK = 23 SS7-CHINA = 23 SS7-ITU = 23 SS7-Japan = 30	Tenths of a second
mtp2SuermThr	Signal unit error rate monitor threshold for emergency operation. Value range: 1 through 127. This property is removed in software Revision 9.3(1) and later.	64	Frames
Note All timer values are expressed in tenths of a second. For example, 130 = 13 seconds.
mtp2T1	Maximum period in aligned/ready state before return to out-of-service state. Value range: 12 through 16 seconds (for ANSI) or 40 through 50 seconds (for BT, CHINA, and ITU). This property is removed in software Revision 9.3(1) and later.	SS7-ANSI = 130 SS7-UK = 450 SS7-CHINA = 450 SS7-ITU = 450 SS7-Japan = 150	Tenths of a second
mtp2T2	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.	SS7-ANSI = 115 SS7-UK = 250 SS7-CHINA = 250 SS7-ITU = 250 SS7-Japan = 50	Tenths of a second
mtp2T3	Maximum period in aligned state before return to out-of-service state. Value range: 5 through 14 seconds (for ANSI) or 1 through 2 seconds (for BT, CHINA, and ITU). This property is removed in software Revision 9.3(1) and later.	SS7-ANSI = 115 SS7-UK = 20 SS7-CHINA = 20 SS7-ITU = 20 SS7-Japan = 30	Tenths of a second
mtp2T5	Period for sending a SIB1 message to far-end. Value range: 80 through 120 seconds. This property is removed in software Revision 9.3(1) and later.	1	Thousandths of a second
mtp2T6	Remote congestion timer. If congestion is not cleared before expiration of this timer, the link fails. Value range: 1 through 6 seconds (for ANSI) or 3 through 6 seconds (for BT, CHINA, and ITU). This property is removed in software Revision 9.3(1) and later.	SS7-ANSI = 30 SS7-UK = 60 SS7-CHINA = 60 SS7-ITU = 60 SS7-Japan = 30	Tenths of a second
mtp2T7	MTP2 acknowledgment timer. On expiration, the link fails and an "excessive delay of acknowledgment" management message is generated. Value range: 0.5 through 2 seconds (for BT, CHINA, and ITU). This property is removed in software Revision 9.3(1) and later.	SS7-ANSI = 10 SS7-UK = 10 SS7-CHINA = 10 SS7-ITU = 10 SS7-Japan = 20	Tenths of a second
Note The mtp2 parameters are used with directly connected SS7 signaling links (for example, ITK or PTI cards).
mtp3ApcMtpRstrtT28	Overall restart timer for signaling point adjacent to one whose MTP restarts. Value range: 3 through 35 seconds (for ANSI only).	SS7-ANSI = 50	Tenths of a second
mtp3DlnkConnAckT7	Waiting for signaling data link connection acknowledgment. Value range: 1 through 2 seconds, or through 5 seconds when connecting over a Cisco ITP-L.	SS7-ANSI = 10 SS7-UK = 10 SS7-CHINA = 10 SS7-ITU = 10 SS7-Japan = 20	Tenths of a second
mtp3FrcUnhT13	Waiting for force uninhibited. Value range: 0.8 through 1.5 seconds.	SS7-ANSI = 10 SS7-UK = 10 SS7-CHINA = 10 SS7-ITU = 10 SS7-Japan = 0	Tenths of a second
mtp3InhAckT14	Waiting for inhibit acknowledgment. Value range: 2 through 3 seconds.	SS7-ANSI = 20 SS7-UK = 20 SS7-CHINA = 20 SS7-ITU = 20 SS7-Japan = 0	Tenths of a second
mtp3LocInhTstT20	Waiting to repeat local inhibit test. Value range: 90 through 120 seconds (for ANSI only).	SS7-ANSI = 900	Tenths of a second
mtp3MaxSltTries	Maximum number of retries of signaling link test message. If MTP3 does not receive a response after two signaling link test messages, the system fails the link. Value range: 1 through 5.	SS7-ANSI = 2 SS7-UK = 2 SS7-CHINA = 2 SS7-ITU = 2 SS7-Japan = 0	Messages
mtp3MsgPriority	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.	SS7-ANSI = 2 SS7-UK = 1 SS7-CHINA = 1 SS7-ITU = 1 SS7-Japan = 1
mtp3MtpRstrtT20	Overall MTP restart timer at the signaling point whose MTP restarts. Value range: 0 to disable, or 59 through 61 seconds. Note This parameter is for BT, CHINA, and ITU.	SS7-UK = 900 SS7-CHINA = 0 SS7-ITU = 600 SS7-Japan = 0	Tenths of a second
mtp3ApcMtpRstrtT21	Overall MTP restart timer at an SP adjacent to an SP whose MTP restarts. Value range: 0 to disable, or 63 through 65 seconds. Note This parameter is for BT, CHINA, and ITU.	SS7-UK = 640 SS7-CHINA = 0 SS7-ITU = 640 SS7-Japan = 0	Tenths of a second
mtp3LocInhTstT22	Waiting to repeat local inhibit test. Value range: 3 through 6 minutes.	SS7-UK = 3000 SS7-CHINA = 3000 SS7-ITU = 3000 SS7-Japan = 0	Tenths of a second
mtp3MtpRstrtT24	Overall MTP restart timer for local MTP restart. Value range is network-dependent.	SS7-ANSI = 60	Tenths of a second
mtp3RepeatRstrtT26	Traffic restart waiting message at local MTP restart. Value range: 12 through 15 seconds.	SS7-ANSI = 150	Tenths of a second
mtp3TfrUsed	Transfer restricted procedure is enabled (true) or disabled (false). Set to true or false.	SS7-ANSI = false SS7-UK = false SS7-CHINA = false SS7-ITU = false SS7-Japan = false	true/false
mtp3TraSnT29	Timer started when traffic restart allowed is sent in response to unexpected traffic restart allowed or traffic restart waiting. Value range: 60 through 65 seconds.	SS7-ANSI = 600	Tenths of a second
mtp3tstSltmT1	Waiting for signaling link test acknowledgment message. This must be greater than the value in mtp2T6. Value range: 4 through 12 seconds.	SS7-ANSI = 60 SS7-UK = 50 SS7-CHINA = 50 SS7-ITU = 50 SS7-Japan = 50	Tenths of a second
mtp3tstSltmT2	Interval for sending signaling link test message. Value range: 30 through 90 seconds.	SS7-ANSI = 600 SS7-UK = 300 SS7-CHINA = 300 SS7-ITU = 300 SS7-Japan = 300	Tenths of a second
mtp3UnhAckTl2	Waiting for uninhibited acknowledgment. Value range: 0.8 through 1.5 seconds.	SS7-ANSI = 10 SS7-UK = 10 SS7-CHINA = 10 SS7-ITU = 10 SS7-Japan = 0	Tenths of a second
mtp3T0	Not used.	SS7-Japan = 200	Tenths of a second
mtp3T7	Waiting for signaling data link connection acknowledgement. Value range: 1 through 20 seconds.	SS7-Japan = 20	Tenths of a second
mtp3T12	Waiting for signaling data link connection acknowledgement. Value range: 500 through 1500 milliseconds.	SS7-Japan = 0	Tenths of a second
mtp3T13	Same as mtp3FrcUnhT13.	SS7-Japan = 0	Tenths of a second
mtp3T14	Same as mtp3InhAckT14.	SS7-Japan = 0	Tenths of a second
mtp3T20	Same as mtp3MtpRstrtT20.	SS7-Japan = 0	Tenths of a second
mtp3T21	Same as mtp3ApcMtpRstrtT21.	SS7-Japan = 0	Tenths of a second
mtp3T22	Same as mtp3LocInhTstT22.	SS7-Japan = 0	Tenths of a second
reference	Denotes versions for protocol standards supported for MTP. For SS7-ANSI: options ANSI92, ANSI96. For SS7-UK, SS7-CHINA, SS7-ITU: options ITU88 and ITU92 For SS7-JAPAN: options NTT, TTC.	SS7-ANSI = ANSI96 SS7-UK = ITU92 SS7-CHINA = ITU92 SS7-ITU = ITU92 SS7-Japan = NTT
rudpAck	Not used.	Enable
rudpKeepAlives	Not used.	Enable
rudpNumRetx	The maximum number for retransmission count. Value range: 1 through 100.	2
rudpWindowSz	The maximum number for unacknowledged Segments in the RUDP window. Value range: 2 through 64.	32
rudpRetxTimer	The retransmission timeout. Value range: 2 through 100.	6	Tenths of a second
rudpSdm	Not used.	Enable

1 SIB = Status indication busy

M3UA Key

This component represents an M3UA routing key. The parent component of the M3UAKEY is the OPC.

•MML Name—M3UAKEY

The M3UA key component structure is shown in Table A-30.

Table A-30 M3UAKEY Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	M3UA key name	The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
DESC	Component description	The description can be up to any 128 characters.
OPC	Associated OPC	MML name of a previously configured OPC.
DPC	Associated DPC (optional)	MML name of a previously configured DPC.
ROUTING CONTEXT	Routing context value	Any integer except 0 (0 indicates no routing context). Each M3UA key must have a unique routing context.
SI	Service indicator	Service type, values are ISUP, TUP, and N/A (N/A).
NETWORK APPEARNCE	Network appearance (optional)	This parameter is optional. The valid values are integers from 1 through 32767. A value of 0 indicates an invalid network appearance.)

---

Note None of the parameters for this command can be modified.

---

The following rules apply when creating M3UA keys:

•You can provision a maximum of 1536 M3UA keys

•Up to 64 OPCs can use M3UA signaling services.

•Parent OPC must be a true OPC

•Cannot be deleted if it is being used by an SS7 signaling service

•Two M3UA keys or SUA keys cannot have the same routing context value

M3UA Route

This component represents an M3UA route. It is used to determine how to get an SS7 message to a particular destination using M3UA.

•MML Name—M3UAROUTE

The M3UA route component structure is shown in Table A-31.

Table A-31 M3UAROUTE Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	M3UA route name	The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
DESC	Component description	The description can be up to any 128 characters.
DPC	Associated DPC	MML name of a previously configured DPC.
EXTNODE	Associated external node	MML name of a previously configured external node.
OPC	Associated OPC	MML name of a previously configured OPC.

---

Note NAME is the only parameter for this command that cannot be modified.

---

The following rules apply when creating/editing M3UA routes:

•The associated DPC must have an SS7 signaling service with an M3UA key defined (matches DPC attribute). If an M3UA key does not exist when the M3UA route is added/edited, a warning is issued. If an M3UA key is still not defined when the provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.

•Multiple DPCs with the same NETADDR cannot be routed to the same OPC

•The associated OPC must be a true OPC

•For a given OPC/DPC only one route can be defined through a given external node.

•Up to two M3UA routes can be defined per OPC-DPC pair

•The associated external node must support M3UA signaling

•M3UA routes for the same OPC-DPC pair must have external nodes in the same group

•When the provisioning session is saved and activated, there must be an ASSOCIATION of type M3UA using an SGP that is using the EXTNODE of each M3UAROUTE.

MGCP Signaling Service

The MGCP Signaling Service component type represents the MGCP signaling service or signaling path to a trunking gateway. Its MML name is as follows:

•MML Name—MGCPPATH

The MGCP signaling service structure is shown in Table A-32.

Table A-32 MGCP Signaling Service Component Structure

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
EXTNODE	External node MML name	MML name of a previously defined external node or index of the external node for SNMP

Multiple IPFAS Services (sigpath)

The multiple IPFAS signaling service component type is used to create multiple IPFAS or IPNFAS signaling paths and D-channels to a particular destination using either ISDN-PRI or DPNSS. Its MML name is as follows:

•MML Name—MLTIPFAS

The multiple IPFAS Signaling Service component structure is shown in Table A-33.

Table A-33 MLTIPFAS Signaling Service Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Name used to derive IPFAS or IPNFAS and D-channel MML names	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 any 128 characters.
CUSTGRPID	Customer ID	Four digit ID; (0000)
MDO	MDO file name	Valid protocol name from variants.dat. Note Limited to any MDO variant from either the ISDNPRI or DPNSS protocol families.
SIDE	Q.931 call model side	User for user side and network for network side; (network)
EXTNODE	External node MML name	MML name of a previously configured external node.
PATHSIZE	Number of IPFAS paths.	Number of IPFAS paths.
SESSIONSET	Session Set MML name.	MML Name of a previously configured Session Set.
SIGSLOT	Physical slot on the gateway where the T1/E1 is plugged into	Integer 0 through 63; (0)
SIGPORT	Physical port on the gateway on the slot	Integer 0 through 167; (0)
SIGPORTSKIP	Number of SIGPORT values to be skipped. (Only required for IPNFAS.)	Integer 0 through 167; (0)
BACKUP	Indicates if a backup D-channel is to be created. (Only required for IPNFAS.)	YES or NO; (NO)
ABFLAG	DPNSS side	`a' or `b' side, `n' for not applicable; (n)
CRLEN	Call reference length	1 for 1 byte or 2 for 2 byte call reference length; (0)
ORIG LABEL	Originating call control (OCC) side location label. Used for Call Limiting feature.	As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).
TERM LABEL	Terminating call control (TCC) side location label. Used for Call Limiting feature.	As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).

Multiple Trunk Groups and Trunks

The multiple trunk groups and trunks component types represent PRI trunk groups and trunks. Its MML name is as follows:

•MML Name—MLTTRNK

The multiple trunk group and trunk component structure is shown in Table A-34.

Table A-34 MLTTRNK Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Starting trunk group number	Any valid trunk group number.
SVC	Starting value of the signaling service MML name	This is the NAME parameter used in the MLTIPFAS command.
CLLI	Common Language Location Identification	Any alphanumeric value that is less than or equal to 11 characters.
TYPE	Trunk group type	Valid trunk group types are: TDM_GEN, TDM_ISUP, TDM_CAS, TDM_TUP, TDM_DPNSS, TDM_PRI, TDM_BTNUP, IP, ATM, IP_SIP, SIP_IN, and CTI. Trunk group type IP is used with EISUP signaling service. TDM_PRI is used with IPFAS or FAS signaling services with protocol family of ISDNPRI. TDM_DPNSS is used with signaling services with protocol family of DPNSS. TDM_ISUP is used with SS7 signaling services with switch types of 0, 5, 20, 23, or 40. TDM_TUP is used with SS7 signaling services with switch type of 5. TDM_BTNUP is used with SS7 signaling services with SS7-UK variants with switch type of 5. TDM_GEN is used with SS7 signaling services with switch types not equal to 0, 5, 20, 23, or 40. TDM_CAS is currently not supported. IP_SIP is used for SIP signaling services at the terminating side. SIP_IN is used for SIP signaling services at the originating side and only one such trunk group can be configured on each Cisco PGW 2200 Softswitch node. CTI is used for CTI signaling. Switch type values are: 0 = No switch-specific 23 = SS7 ANSI logic for the signaling path. 26 = DPNSS 5 = BTNUP 27 = NET5 10 = SS7 Japan 29 = QSIG MASTER 17 = 5ESS 30 = QSIG SLAVE 20 = SS7 Clear 40 = SS7 ITU 22 = NI2
SELSEQ	Select sequence	Valid select sequence values are: LIDL, MIDL, ASC, DESC, RDM, EDESC, ODESC, EASC, OASC, CASC, CDESC.
QABLE	Queueable	Y or N; (N).
NUMTRNKGRP	Number of trunk groups	Integer greater than 0.
SPANSIZE	Number of trunks per span	Integer greater than 0 and less than 31; (1).
NUMSPAN	Number of spans per trunk group	Integer greater than 0; (1).
DCHAN	Reserved time slot for D-channel in spans	Integer greater than 0; (0).
DCHANSPAN	List of spans where a D-channel is to be reserved	The format is "span1, span2, ..., spanN" or "ALL"; (ALL).
TRNKMEMNUM	Starting trunk group member number for each trunk group	Integer greater than 0; (1).
SPAN	Span	Integer from 0 through 65535 or ffff.
CIC	Circuit Identifier Code	Integer from 0 through 65535.
ENDPOINT	Text description of the trunk endpoint. An endpoint value is typically composed of an interface, a timeslot, and a domain name.	Enter as many as 128 characters and enclose in straight quotes.
CU	Coding Unit's MML name	MML name of previously defined CU.
COTPERCENTAGE	Determines the percentage of calls on the trunk upon which a continuity test (COT) is performed.	0 through 100; (0).
RINGNOANSWER	Ring no answer. Indicates the time, in seconds, ringing is allowed to occur.	0 through 600 seconds; (255).
GLARE	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).
SATELLITEIND	Satellite indicator. Indicates if the trunk is going over a satellite.	Values are: 0 (no) (default) or 1 (yes).
NPA	Numbering plan area. Indicates the NPA code associated with the incoming trunk group.	Value range: 0 (none) (default), or 200 through 999.
CARRIERIDENTITY	Trunk group property carrier identity	Any integer of 4 digits greater than 0; (0).
SCREENFAILACTION	Trunk group property screen fail action	1 (yes) or 0 (no); (0).
CUSTGRPID	Trunk group property customer group ID	Any 4 alphanumeric characters; (0000).
COMPRESSIONTYPE	Compression type. Indicates the G.711 compression type used on the trunk.	Values are: 0 (none), 1 (mu-law) (default), or 2 (A-law).
ECHOCANREQUIRED	Echo cancellation. Indicates if echo cancellation is required.	Echo Canceller Required. Specifies whether to send a modify-connection message (MDCX) for echo control. Enter a value of 0 or 1 for EchoCanRequired on the trunk group or sigpath. 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

Nailed Trunk (Bearer Channel)

The Nailed Trunk component facilitates the provisioning of the individual nailed bearer channels used in a Cisco SS7 Interconnect for Access Servers Solution or Classic Cisco PGW 2200 Softswitch configuration. Its MML name is as follows:

•MML Name—NAILEDTRNK

The linkset component structure is shown in Table A-35.

Table A-35 Nailed Trunk (Bearer Channel) Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Trunk identifier	Integer from 0 through 65535.
SRCSVC	MML name of the source service	MML name of a previously defined signaling service. Valid signaling services are: ISDNPRI, DPNSS, or any SS7 signaling service.
DSTSVC	MML name of destination service	MML name of a previously defined signaling service. Valid signaling services are: ISDNPRI, DPNSS, or any SS7 signaling service.
SRCSPAN	Source span	Integer from 0 through 65535 or ffff; (ffff)
DSTSPAN	Destination span	Integer from 0 through 65535 or ffff; (ffff)
SRCTIMESLOT	Source timeslot	Integer from 0 through 65535.
DSTTIMESLOT	Destination timeslot	Integer from 0 through 65535.
SPANSIZE	Number of trunks per span	Integer from 1 through 31; (1)

NAS Signaling Service (sigpath)

The NAS signaling service component type represents an ISDN signaling service or signaling path that is backhauled over IP to and from a NAS (destination). Its MML name is as follows:

•MML Name—NASPATH

The NAS signaling service component structure is shown in Table A-36.

Table A-36 NAS Signaling Service (sigpath) Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	NAS signaling service name	The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
DESC	Component description	The description can be up to 128 characters.
MDO	MDO file name	Valid protocol name from variants.dat. (BELL_1268_C3 [for software Release 9.3(1) and earlier or BELL_1268_C2 for software Release 9.3(2) and later] is the only valid MDO variant for this signaling service).
EXTNODE	External node MML name	MML name of a previously defined external node or index of the external node for SNMP.
CUSTGRPID	Customer group ID	Four digit ID; (0000).
SIGSLOT	Physical slot on the NAS defining the NFAS Group (optional)	An integer, 0 through 63; (0). This parameter is added in software Release 9.4(1).
SIGPORT	Physical Port on the slot of NAS defining the NFAS Group. (optional)	An integer, 0 through 167; (0). This parameter is added in software Release 9.4(1).

The following parameters cannot be modified:

•NAME

•EXTNODE

The following rules apply when creating or editing NAS signaling paths:

•You must have an IP link configured if the ISDNTYPE of the EXTNODE is N/A.

•The maximum number of DPNSSPATHs and IUA NASPATHs per IUA external node is 112.

•The maximum number of DPNSSPATHs and IUA NASPATHs is 1500.

•The SIGPORT and SIGSLOT attributes can be defined only if the ISDNTYPE of EXTNODE is IUA.

•An ASSOCIATION must be defined with the same EXTNODE attribute as its parent NASPATH. If this ASSOCIATION is not defined when the NASPATH is added or edited, a warning is issued. If the ASSOCIATION still is not defined when the provisioning session is copied or deployed, an error message is generated, and the copy or deployment procedure is stopped.

•If the ASSOCIATION with the same EXTNODE value as the NASPATH is deleted, a warning message is issued informing the user that the NASPATH must also be deleted. If it is not deleted when the provisioning session is copied or deployed, an error message is generated and the copy or deployment procedure is stopped.

Originating Point Code

The Originating Point Code component type represents an SS7 point code used by the Cisco PGW 2200 Softswitch NE. Its MML name is as follows:

•MML Name—OPC

The Originating Point Code component structure is shown in Table A-37.

Table A-37 Point Code Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
NETADDR	Network address	String in doted notation, for example, 1.1.1.
NETIND	Network indicator	; (0)
TYPE	Type of the OPC	TRUEOPC or CAPOPC.
TRUEOPC	MML name of the true OPC with which the capability OPC is associated	The MML name of a previously defined true OPC. It only applies to the capability OPC.

Profile

The Profile component supports the ability to retrieve all entries in the table with overridden properties by specifying "all". Its MML name is as follows:

•MML Name—PROFILE

The Profile component structure is shown in Table A-38.

Table A-38 Profile Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Profile name	The name can be as many as twenty alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
TYPE	Profile type name (as defined in properties.dat)	The name can be as many as twenty alphanumeric characters.
PROPERTYNAME	Profile name (as defined in properties.dat)	The name can be as many as twenty alphanumeric characters.

The following list identifies the ISUP timers that can be provisioned for signaling service. Information for each timer consists of:

•Default—Indicates if it is assigned to a profile. Set to 0 for no profile.

•Components—Identifies the protocol variants supported, the default value, and the range for each protocol variant.

*.T1

Desc: T1

Default: 0

Type:

Components:

SigPath Profile = Yes

SS7-ANSI

ANSISS7_STANDARD Default: 4000 Range=4000-15000

SS7-ITU

Q761_BASE Default: 15000 Range=15000-60000

Q767_BASE Default: 4000 Range=4000-15000

Q761_SINGAPORE Default: 15000 Range=15000-60000

Q761_ARGENTINA Default: 10000 Range=10000-60000

ISUPV2_FINNISH96 Default: 15000 Range=15000-60000

ISUPV2_FRENCH Default: 15000 Range=15000-60000

Q761_THAILAND Default: 15000 Range=15000-60000

Q761_PERU Default: 30000 Range=15000-60000

Q761_BELG_C2 Default: 15000 Range=15000-60000

SS7-Japan

ISUPV2_JAPAN Default: 15000 Range=10000-60000

*.T12

Desc: T12

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 6000 Range=4000-15000

SS7-ITU

Q761_BASE Default: 15000 Range=15000-60000

Q767_BASE Default: 15000 Range=4000-15000

Q761_SINGAPORE Default: 60000 Range=60000-60000

Q761_ARGENTINA Default: 10000 Range=10000-60000

ISUPV2_SPANISH Default: 30000 Range=10000-60000

ISUPV2_FINNISH96 Default: 15000 Range=15000-60000

ISUPV2_FRENCH Default: 15000 Range=15000-60000

Q761_THAILAND Default: 15000 Range=15000-60000

Q761_PERU Default: 30000 Range=15000-60000

Q761_BELG_C2 Default: 15000 Range=15000-60000

SS7-Japan

ISUPV2_JAPAN Default: 15000 Range=15000-60000

*.T13

Desc: T13

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 60000 Range=60000-60000

SS7-ITU

Q761_BASE Default: 300000 Range=300000-900000

Q767_BASE Default: 60000 Range=60000-60000

Q761_SINGAPORE Default: 300000 Range=300000-900000

Q761_ARGENTINA Default: 60000 Range=60000-900000

ISUPV2_SPANISH Default: 600000 Range=60000-900000

ISUPV2_FINNISH96 Default: 300000 Range=300000-900000

ISUPV2_FRENCH Default: 300000 Range=300000-900000

Q761_THAILAND Default: 60000 Range=60000-900000

Q761_PERU Default: 600000 Range=300000-900000

Q761_BELG_C2 Default: 300000 Range=300000-900000

SS7-Japan

ISUPV2_JAPAN Default: 300000 Range=60000-900000

*.T14

Desc: T14

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 6000 Range=4000-15000

SS7-ITU

Q761_BASE Default: 15000 Range=15000-60000

Q767_BASE Default: 15000 Range=4000-15000

Q761_SINGAPORE Default: 60000 Range=60000-60000

Q761_ARGENTINA Default: 10000 Range=10000-60000

ISUPV2_SPANISH Default: 30000 Range=10000-60000

ISUPV2_FINNISH96 Default: 15000 Range=15000-60000

ISUPV2_FRENCH Default: 15000 Range=15000-60000

Q761_THAILAND Default: 15000 Range=15000-60000

Q761_PERU Default: 30000 Range=15000-60000

Q761_BELG_C2 Default: 15000 Range=15000-60000

SS7-Japan

ISUPV2_JAPAN Default: 15000 Range=15000-60000

*.T15

Desc: T15

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 60000 Range=60000-60000

SS7-ITU

Q761_BASE Default: 300000 Range=300000-900000

Q767_BASE Default: 60000 Range=60000-60000

Q761_SINGAPORE Default: 300000 Range=300000-900000

Q761_ARGENTINA Default: 6000 Range=60000-900000

ISUPV2_SPANISH Default: 600000 Range=60000-900000

ISUPV2_FINNISH96 Default: 300000 Range=300000-900000

ISUPV2_FRENCH Default: 300000 Range=300000-900000

Q761_THAILAND Default: 60000 Range=60000-900000

Q761_PERU Default: 600000 Range=300000-900000

Q761_BELG_C2 Default: 300000 Range=300000-900000

SS7-Japan

ISUPV2_JAPAN Default: 300000 Range=300000-900000

*.T16

Desc: T16

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 5000 Range=4000-15000

SS7-ITU

Q761_BASE Default: 15000 Range=15000-60000

Q767_BASE Default: 5000 Range=4000-15000

Q761_SINGAPORE Default: 60000 Range=60000-60000

Q761_ARGENTINA Default: 10000 Range=10000-60000

ISUPV2_SPANISH Default: 30000 Range=10000-60000

ISUPV2_FINNISH96 Default: 15000 Range=15000-60000

ISUPV2_FRENCH Default: 15000 Range=15000-60000

Q761_THAILAND Default: 15000 Range=15000-60000

Q761_PERU Default: 30000 Range=15000-60000

Q761_BELG_C2 Default: 15000 Range=15000-60000

SS7-Japan

ISUPV2_JAPAN Default: 15000 Range=10000-60000

*.T17

Desc: T17

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 60000 Range=60000-60000

SS7-ITU

Q761_BASE Default: 300000 Range=300000-900000

Q767_BASE Default: 60000 Range=60000-60000

Q761_SINGAPORE Default: 300000 Range=300000-900000

Q761_ARGENTINA Default: 60000 Range=60000-900000

ISUPV2_SPANISH Default: 600000 Range=60000-900000

ISUPV2_FINNISH96 Default: 300000 Range=300000-900000

ISUPV2_FRENCH Default: 300000 Range=300000-900000

Q761_THAILAND Default: 60000 Range=60000-900000

Q761_PERU Default: 600000 Range=300000-900000

Q761_BELG_C2 Default: 300000 Range=300000-900000

SS7-Japan

ISUPV2_JAPAN Default: 60000 Range=60000-900000

*.T18

Desc: T18

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 15000 Range=4000-15000

SS7-ITU

Q761_BASE Default: 15000 Range=15000-60000

Q767_BASE Default: 15000 Range=4000-15000

Q761_SINGAPORE Default: 60000 Range=60000-60000

Q761_ARGENTINA Default: 10000 Range=10000-60000

ISUPV2_SPANISH Default: 30000 Range=10000-60000

ISUPV2_FINNISH96 Default: 15000 Range=15000-60000

ISUPV2_FRENCH Default: 15000 Range=15000-60000

Q761_THAILAND Default: 15000 Range=15000-60000

Q761_PERU Default: 30000 Range=15000-60000

Q761_BELG_C2 Default: 15000 Range=15000-60000

SS7-Japan

ISUPV2_JAPAN Default: 15000 Range=15000-60000

*.T19

Desc: T19

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 60000 Range=60000-60000

SS7-ITU

Q761_BASE Default: 300000 Range=300000-900000

Q767_BASE Default: 60000 Range=60000-60000

Q761_SINGAPORE Default: 300000 Range=300000-900000

Q761_ARGENTINA Default: 60000 Range=60000-900000

ISUPV2_SPANISH Default: 600000 Range=60000-900000

ISUPV2_FINNISH96 Default: 300000 Range=300000-900000

ISUPV2_FRENCH Default: 300000 Range=300000-900000

Q761_THAILAND Default: 60000 Range=60000-900000

Q761_PERU Default: 600000 Range=300000-900000

Q761_BELG_C2 Default: 300000 Range=300000-900000

SS7-Japan

ISUPV2_JAPAN Default: 300000 Range=300000-900000

*.T2

Desc: T2

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 180000 Range=180000-180000

SS7-ITU

Q761_BASE Default: 180000 Range=180000-180000

Q767_BASE Default: 180000 Range=180000-180000

Q761_SINGAPORE Default: 180000 Range=180000-180000

Q761_ARGENTINA Default: 180000 Range=180000-180000

ISUPV2_SPANISH Default: 180000 Range=180000-180000

ISUPV2_FINNISH96 Default: 180000 Range=180000-180000

ISUPV2_FRENCH Default: 180000 Range=180000-180000

Q761_THAILAND Default: 180000 Range=180000-180000

Q761_PERU Default: 180000 Range=180000-180000

Q761_BELG_C2 Default: 180000 Range=180000-180000

SS7-Japan

ISUPV2_JAPAN Default: 180000 Range=180000-180000

*.T20

Desc: T20

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 15000 Range=4000-15000

SS7-ITU

Q761_BASE Default: 15000 Range=15000-60000

Q767_BASE Default: 15000 Range=4000-15000

Q761_SINGAPORE Default: 60000 Range=60000-60000

Q761_ARGENTINA Default: 10000 Range=10000-60000

ISUPV2_SPANISH Default: 30000 Range=10000-60000

ISUPV2_FINNISH96 Default: 15000 Range=15000-60000

ISUPV2_FRENCH Default: 15000 Range=15000-60000

Q761_THAILAND Default: 15000 Range=15000-60000

Q761_PERU Default: 30000 Range=15000-60000

Q761_BELG_C2 Default: 15000 Range=15000-60000

SS7-Japan

ISUPV2_JAPAN Default: 15000 Range=15000-60000

*.T21

Desc: T21

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 60000 Range=60000-60000

SS7-ITU

Q761_BASE Default: 300000 Range=300000-900000

Q767_BASE Default: 60000 Range=60000-60000

Q761_SINGAPORE Default: 300000 Range=300000-900000

Q761_ARGENTINA Default: 60000 Range=60000-900000

ISUPV2_SPANISH Default: 600000 Range=60000-900000

ISUPV2_FINNISH96 Default: 300000 Range=300000-900000

ISUPV2_FRENCH Default: 300000 Range=300000-900000

Q761_THAILAND Default: 60000 Range=60000-900000

Q761_PERU Default: 600000 Range=300000-900000

Q761_BELG_C2 Default: 300000 Range=300000-900000

SS7-Japan

ISUPV2_JAPAN Default: 300000 Range=300000-900000

*.T22

Desc: T22

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 15000 Range=4000-15000

SS7-ITU

Q761_BASE Default: 15000 Range=15000-60000

Q767_BASE Default: 15000 Range=4000-15000

Q761_SINGAPORE Default: 60000 Range=60000-60000

Q761_ARGENTINA Default: 10000 Range=10000-60000

ISUPV2_SPANISH Default: 30000 Range=10000-60000

ISUPV2_FINNISH96 Default: 15000 Range=15000-60000

ISUPV2_FRENCH Default: 15000 Range=15000-60000

Q761_THAILAND Default: 15000 Range=15000-60000

Q761_PERU Default: 30000 Range=15000-60000

Q761_BELG_C2 Default: 15000 Range=15000-60000

SS7-Japan

ISUPV2_JAPAN Default: 10000 Range=10000-60000

*.T23

Desc: T23

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 60000 Range=60000-60000

SS7-ITU

Q761_BASE Default: 300000 Range=300000-900000

Q767_BASE Default: 60000 Range=60000-60000

Q761_SINGAPORE Default: 300000 Range=300000-900000

Q761_ARGENTINA Default: 60000 Range=60000-900000

ISUPV2_SPANISH Default: 600000 Range=60000-900000

ISUPV2_FINNISH96 Default: 300000 Range=300000-900000

ISUPV2_FRENCH Default: 300000 Range=300000-900000

Q761_THAILAND Default: 60000 Range=60000-900000

Q761_PERU Default: 600000 Range=300000-900000

Q761_BELG_C2 Default: 300000 Range=300000-900000

SS7-Japan

ISUPV2_JAPAN Default: 60000 Range=60000-900000

*.T24

Desc: T24

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 20000 Range=20000-20000

SS7-ITU

Q761_BASE Default: 2000 Range=0-2000

Q767_BASE Default: 2000 Range=0-2000

Q761_SINGAPORE Default: 2000 Range=2000-2000

Q761_ARGENTINA Default: 2000 Range=2000-2000

ISUPV2_SPANISH Default: 1500 Range=1500-2000

ISUPV2_FINNISH96 Default: 2000 Range=0-2000

ISUPV2_FRENCH Default: 2000 Range=0-2000

Q761_THAILAND Default: 2000 Range=0-2000

Q761_PERU Default: 15000 Range=0-2000

Q761_BELG_C2 Default: 2000 Range=0-2000

SS7-Japan

ISUPV2_JAPAN Default: 2000 Range=0-2000

*.T25

Desc: T25

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 1000 Range=1000-10000

SS7-ITU

Q761_BASE Default: 2000 Range=1000-10000

Q767_BASE Default: 2000 Range=1000-10000

Q761_SINGAPORE Default: 10000 Range=1000-10000

Q761_ARGENTINA Default: 10000 Range=1000-10000

ISUPV2_SPANISH Default: 10000 Range=1000-10000

ISUPV2_FINNISH96 Default: 2000 Range=1000-10000

ISUPV2_FRENCH Default: 2000 Range=1000-10000

Q761_THAILAND Default: 2000 Range=1000-10000

Q761_PERU Default: 10000 Range=1000-10000

Q761_BELG_C2 Default: 2000 Range=1000-10000

SS7-Japan

ISUPV2_JAPAN Default: 2000 Range=1000-10000

*.T26

Desc: T26

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 120000 Range=60000-180000

SS7-ITU

Q761_BASE Default: 180000 Range=60000-180000

Q767_BASE Default: 180000 Range=60000-180000

Q761_SINGAPORE Default: 180000 Range=60000-180000

Q761_ARGENTINA Default: 120000 Range=60000-180000

ISUPV2_SPANISH Default: 120000 Range=60000-180000

ISUPV2_FINNISH96 Default: 180000 Range=60000-180000

ISUPV2_FRENCH Default: 180000 Range=60000-180000

Q761_THAILAND Default: 180000 Range=60000-180000

Q761_PERU Default: 120000 Range=60000-180000

Q761_BELG_C2 Default: 180000 Range=60000-180000

SS7-Japan

ISUPV2_JAPAN Default: 180000 Range=60000-180000

*.T27

Desc: T27

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 240000 Range=180000-240000

SS7-ITU

Q761_BASE Default: 240000 Range=240000-240000

Q767_BASE Default: 240000 Range=240000-240000

Q761_SINGAPORE Default: 240000 Range=240000-240000

Q761_ARGENTINA Default: 240000 Range=240000-240000

ISUPV2_SPANISH Default: 240000 Range=240000-240000

ISUPV2_FINNISH96 Default: 240000 Range=240000-240000

ISUPV2_FRENCH Default: 240000 Range=240000-240000

Q761_THAILAND Default: 240000 Range=240000-240000

Q761_PERU Default: 240000 Range=240000-240000

Q761_BELG_C2 Default: 240000 Range=240000-240000

SS7-Japan

ISUPV2_JAPAN Default: 240000 Range=240000-240000

*.T28

Desc: T28

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 10000 Range=10000-10000

SS7-ITU

Q761_BASE Default: 10000 Range=10000-10000

Q761_SINGAPORE Default: 10000 Range=10000-10000

Q761_ARGENTINA Default: 10000 Range=10000-10000

ISUPV2_SPANISH Default: 10000 Range=10000-10000

ISUPV2_FINNISH96 Default: 10000 Range=10000-10000

ISUPV2_FRENCH Default: 10000 Range=10000-10000

Q761_THAILAND Default: 10000 Range=10000-10000

Q761_PERU Default: 10000 Range=10000-10000

Q761_BELG_C2 Default: 10000 Range=10000-10000

SS7-Japan

ISUPV2_JAPAN Default: 10000 Range=10000-10000

*.T33

Desc: T33

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 120000 Range=120000-120000

SS7-ITU

Q761_BASE Default: 15000 Range=12000-15000

Q767_BASE Default: 120000 Range=120000-120000

Q761_SINGAPORE Default: 14000 Range=12000-15000

Q761_ARGENTINA Default: 15000 Range=12000-15000

ISUPV2_SPANISH Default: 15000 Range=12000-15000

ISUPV2_FINNISH96 Default: 15000 Range=12000-15000

ISUPV2_FRENCH Default: 15000 Range=12000-15000

Q761_THAILAND Default: 15000 Range=12000-15000

Q761_PERU Default: 15000 Range=12000-15000

Q761_BELG_C2 Default: 15000 Range=12000-15000

SS7-Japan

ISUPV2_JAPAN Default: 15000 Range=12000-15000

*.T34

Desc: T34

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 10000 Range=10000-10000

SS7-ITU

Q761_BASE Default: 2000 Range=2000-4000

Q761_SINGAPORE Default: 3800 Range=2000-4000

Q761_ARGENTINA Default: 15000 Range=2000-15000

ISUPV2_SPANISH Default: 2000 Range=2000-15000

ISUPV2_FINNISH96 Default: 2000 Range=2000-4000

ISUPV2_FRENCH Default: 4000 Range=2000-4000

Q761_THAILAND Default: 2000 Range=2000-4000

Q761_PERU Default: 2000 Range=2000-4000

Q761_BELG_C2 Default: 2000 Range=2000-4000

SS7-Japan

ISUPV2_JAPAN Default: 2000 Range=2000-4000

*.T35

Desc: T35

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ITU

Q761_BASE Default: 15000 Range=15000-20000

Q767_BASE Default: 15000 Range=15000-20000

Q761_SINGAPORE Default: 15000 Range=15000-20000

Q761_ARGENTINA Default: 15000 Range=15000-20000

ISUPV2_SPANISH Default: 15000 Range=15000-20000

ISUPV2_FINNISH96 Default: 15000 Range=15000-20000

ISUPV2_FRENCH Default: 15000 Range=15000-20000

Q761_THAILAND Default: 15000 Range=15000-20000

Q761_PERU Default: 15000 Range=15000-20000

Q761_BELG_C2 Default: 15000 Range=15000-20000

SS7-Japan

ISUPV2_JAPAN Default: 15000 Range=15000-20000

*.T36

Desc: T36

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 10000 Range=10000-10000

SS7-ITU

Q761_BASE Default: 10000 Range=10000-15000

Q767_BASE Default: 10000 Range=10000-15000

Q761_SINGAPORE Default: 10000 Range=1000-15000

Q761_ARGENTINA Default: 10000 Range=1000-15000

ISUPV2_SPANISH Default: 15000 Range=1000-15000

ISUPV2_FINNISH96 Default: 10000 Range=10000-15000

ISUPV2_FRENCH Default: 10000 Range=10000-15000

Q761_THAILAND Default: 10000 Range=10000-15000

Q761_PERU Default: 15000 Range=10000-15000

Q761_BELG_C2 Default: 10000 Range=10000-15000

SS7-Japan

ISUPV2_JAPAN Default: 10000 Range=10000-15000

*.T38

Desc: T38

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ITU

Q761_BASE Default: 125000 Range=125000-125000

Q761_SINGAPORE Default: 125000 Range=125000-125000

Q761_ARGENTINA Default: 125000 Range=125000-125000

ISUPV2_SPANISH Default: 125000 Range=125000-125000

ISUPV2_FINNISH96 Default: 125000 Range=125000-125000

ISUPV2_FRENCH Default: 125000 Range=125000-125000

Q761_THAILAND Default: 125000 Range=125000-125000

Q761_BELG_C2 Default: 125000 Range=125000-125000

SS7-Japan

ISUPV2_JAPAN Default: 125000 Range=125000-125000

*.T5

Desc: T5

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 60000 Range=60000-60000

SS7-ITU

Q761_BASE Default: 300000 Range=300000-900000

Q767_BASE Default: 60000 Range=60000-60000

Q761_SINGAPORE Default: 300000 Range=300000-900000

Q761_ARGENTINA Default: 60000 Range=60000-900000

ISUPV2_SPANISH Default: 600000 Range=60000-900000

ISUPV2_FINNISH96 Default: 300000 Range=300000-900000

ISUPV2_FRENCH Default: 300000 Range=300000-900000

Q761_THAILAND Default: 60000 Range=60000-900000

Q761_PERU Default: 600000 Range=300000-900000

Q761_BELG_C2 Default: 300000 Range=300000-900000

SS7-Japan

ISUPV2_JAPAN Default: 60000 Range=60000-900000

*.T6

Desc: T6

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 32000 Range=10000-32000

SS7-ITU

Q761_BASE Default: 120000 Range=60000-120000

Q767_BASE Default: 120000 Range=60000-120000

Q761_SINGAPORE Default: 20000 Range=20000-130000

Q761_ARGENTINA Default: 60000 Range=10000-60000

ISUPV2_SPANISH Default: 60000 Range=10000-60000

ISUPV2_FINNISH96 Default: 120000 Range=60000-120000

ISUPV2_FRENCH Default: 60000 Range=60000-120000

Q761_THAILAND Default: 90000 Range=60000-120000

Q761_PERU Default: 15000 Range=15000-120000

Q761_BELG_C2 Default: 120000 Range=60000-120000

SS7-Japan

ISUPV2_JAPAN Default: 3000 Range=2000-4000

*.T7

Desc: T7

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 30000 Range=20000-30000

SS7-ITU

Q761_BASE Default: 30000 Range=20000-30000

Q767_BASE Default: 30000 Range=20000-30000

Q761_SINGAPORE Default: 20000 Range=20000-30000

Q761_ARGENTINA Default: 20000 Range=20000-30000

ISUPV2_SPANISH Default: 20000 Range=20000-30000

ISUPV2_FINNISH96 Default: 30000 Range=20000-30000

ISUPV2_FRENCH Default: 30000 Range=20000-30000

Q761_THAILAND Default: 30000 Range=20000-30000

Q761_PERU Default: 20000 Range=20000-30000

Q761_BELG_C2 Default: 40000 Range=20000-50000

SS7-Japan

ISUPV2_JAPAN Default: 30000 Range=20000-30000

*.T8

Desc: T8

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 10000 Range=10000-15000

SS7-ITU

Q761_BASE Default: 10000 Range=10000-15000

Q767_BASE Default: 10000 Range=10000-15000

Q761_SINGAPORE Default: 10000 Range=10000-15000

Q761_ARGENTINA Default: 15000 Range=10000-15000

ISUPV2_SPANISH Default: 15000 Range=10000-15000

ISUPV2_FINNISH96 Default: 10000 Range=10000-15000

ISUPV2_FRENCH Default: 10000 Range=10000-15000

Q761_THAILAND Default: 10000 Range=10000-15000

Q761_PERU Default: 15000 Range=10000-15000

Q761_BELG_C2 Default: 10000 Range=10000-15000

SS7-Japan

ISUPV2_JAPAN Default: 10000 Range=10000-15000

*.T9

Desc: T9

Default: 0

Type:

Components:

SigPath Profile=Yes

SS7-ANSI

ANSISS7_STANDARD Default: 120000 Range=120000-240000

SS7-ITU

Q761_BASE Default: 120000 Range=60000-120000

Q767_BASE Default: 120000 Range=60000-120000

Q761_SINGAPORE Default: 90000 Range=60000-240000

Q761_ARGENTINA Default: 120000 Range=60000-240000

ISUPV2_SPANISH Default: 60000 Range=60000-240000

ISUPV2_FINNISH96 Default: 180000 Range=120000-240000

ISUPV2_FRENCH Default: 120000 Range=60000-120000

Q761_THAILAND Default: 120000 Range=60000-120000

Q761_PERU Default: 60000 Range=60000-120000

Q761_BELG_C2 Default: 120000 Range=60000-120000

SS7-Japan

ISUPV2_JAPAN Default: 120000 Range=60000-120000

RASERVER

The RASERVER component defines a signal channel to the Radius Accounting Server. RASERVER also associates an RA SigPath to the channel.

MML Name—RASERVER

The following restrictions apply to the RASERVER component:

•The maximum number of RASERVERs is 5.

•You must add an RAPATH before adding an RASERVER

•If you want to delete a single RASERVER, you must also delete the RAPATH.

• To modify an RASERVER, the PORT parameter value must match the existing RASERVER.

•Duplicate PORT or ORDER values cause an error.

•The PGW uses PORT with a value between <local-port> and <local-port + <number of port>>

The RASERVER component structure is shown in Table A-39.

Table A-39 RASERVER Component Structure

Table 1:

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique ID of this component and component name used in MML commands	The name can be up to any 20 alphanumeric characters. No special characters other than "-" are allowed. Names 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.
IPADDR	Local logical IP address This parameter is mandatory.	IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4.
PORT	Local port number This parameter is mandatory.	1025 through 65535.
PEERADDR	Remote IP address This parameter is mandatory.	IP address; (0.0.0.0). This may also be specified as a hostname or a DNS name.
PEERPORT	The accounting port number used on the destination server for accounting data. This parameter is mandatory.	1025 to 65535.
IPROUTE	MML name for first IP route (optional)	MML name of a previously provisioned IP route. (empty string)
ORDER	ORDER is the order of the server as primary server. The order with the lowest value is selected as the primary server. This parameter is mandatory.	1 to 99.
KEY	KEY is the shared key for encryption used for this server. This parameter is mandatory.	Alphanumeric and dash characters are allowed. The KEY must start with a character. The length of KEY is 1 to 99. (empty string)
TIMEOUT	TIMEOUT is the duration in seconds before the packet is retransmitted. This parameter is optional.	1 to 30. (6)
RETRYCOUNT	The number of times a packet is re-transmitted before giving up. This parameter is optional.	1 to 10. (2)

Routing

The routing file can be moved onto the Cisco PGW 2200 Softswitch using FTP and then associated with the relevant session using SNMP. Its MML name is as follows:

•MML Name—RTTRNKGRP

The routing component structure is shown in Table A-40.

Table A-40 Routing Component Structure 

Component MML Name	Parameter MML Name	Parameter Description	Parameter Values (Default)
SIPRTTRNKGRP	NAME	Trunk group number	Unique name for this SIP routing trunk group number. 1 through 9999; (none)
	URL	SIP proxy service address in the format of IP address, hostname, or DNS name
	SIPPROXYPORT	UDP port number used by the SIP proxy server
	VERSION	SIP version of the SIP proxy server
	CUTTHROUGH	Cut through indicates the point in a call at which the call is through connected.	0 through 3; (0) 0 = Undefined 1 = Seize - call is through connected a seize, not applicable 2 = ACM - call is through connected at ACM 3 = ANM - call is through connected at ANM
	EXTSUPPORT	SIP extension supported Note This property is reserved for future use and is not currently implemented.	0 or 1; (0) 0 = False 1 = True
	SRVRR	Indicates if the (current) SIP URL is a server (SRV) DNS or not	0 or 1; (0) 0 = False - not a Server DNS 1 = True - is an SRV DNS
RTLIST	NAME	Route list name	20 alphanumeric
	RTNAME	Route name	; (0)
	NEXTRTNAME	Next route name	20 alphanumeric
	DISTRIB	Indicates if random or sequential distribution is enabled	String: On or Off, (Off). Select Off (default) to use sequential selection to choose the trunk group in the route; or On to use random selection.
RTTRNK	NAME	Route name	20 alphanumeric
	TRNKGRPNUM	Trunk group number	; (0)
	NEXTTRKGRP	Next trunk group	Integer 0 through 65535; (0)
	WEIGHTEDTG	Weighted trunk group	String: ON or OFF (OFF)
RTTRNKGRP	NAME	Trunk group number	Unique name for this routing trunk group number. 1 through 9999; (none)
	TYPE	Trunk group type	0 to 8; (0) 0 = General (default)—Used with SS7 signaling services with switch types not equal to 0, 5, or 20. 1 = ISUP—Used with SS7 signaling services with switch types of 0 or 20. 2 = CAS—currently not supported. 3 = 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 = DPNSS—Used with DPNSS protocol family signaling services 7 = PRI—Used with ISDN PRI protocol family signaling services. 8 = BTNUP—Used with SS7 signaling services with switch type 5. 9 = IP_SIP—Used with SIP signaling services at the terminating side. 10 = SIP_IN—Used with SIP signaling services at the originating side. 11 = CTI—Used with CTI signaling.
	REATTEMPTS	Number of reattempts	0 to 5; (0)
	QUEUING	Queuing time	0 to 120; (0)
	CUTTHROUGH	Cut through indicates the point in a call at which the call is through connected.	0 through 3; (0) 0 = Undefined 1 = Seize - call is through connected a seize, not applicable 2 = ACM - call is through connected at ACM 3 = ANM - call is through connected at ANM
	RESINCPERC	Reserve incoming bandwidth percentage	0 through 100 (0)
	BEARERCAPNAME	Bearer capability name	20 alphanumeric (NULL)
CARRIERTBL	NAME	Used to configure CARRIERID, RTEOPTION, and RTLISTNAME.
	CARRIERID	Mandatory parameter; identifies the carrier ID code	2 to 5 digits (for Germany the range is 2 or 3 digits)
	RTEOPTION	Optional parameter; identifies the route option	String: DN (default), CARRIER, or BLOCKED
	RTLISTNAME	This parameter is only valid if RTEOPTION is set to CARRIER.	20 alphanumeric
CONDRTE	NAME	Conditional routing name	20 alphanumeric
	DOW	Day of week	DEFAULT; (DEFAULT), SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY, HOL1, HOL2, HOL3
	RTEDESC	Conditional routing descriptor	Up to 124 alphanumeric characters providing time-ordered options to use a specified result set (from the dial plan result table). The format is: setName1, setTime1, ... setNamen, setTimeChangen.

The following rules apply when creating or editing the Routing table:

To add, modify, or delete the contents of a Routing table, an active provisioning session is required.

At the time of deploying or copying, routing files from the provisioning directory are copied to the active directory. The active directory for the routing file is: /opt/CiscoMGC/etc.

All of the TIDs, except CARRIERTBL and ROUTING, require a name. Currently it is only possible to retrieve against a name.

All the Carrier tables, route lists, route trunks, and route trunk groups information can be retrieved by using the prov:rtrv:rtlist:"ALL" command. The ALL option cannot be used with other parameters.

The NEXTRTNAME parameter is used for changing the order of routes in the route list. If not specified when a route is added to a route list, the routes are added in the order in which they are entered. NEXTRTNAME is only valid for use when modifying the route list.

The NEXTRKGRP parameter is used for changing the order of trunk groups in the route. If not specified when a trunk group is added to a route, the trunk groups are added in the order in which they are entered. NEXTRKGRP is only valid for use when modifying the route list.

The CARRIERID is not available in RTLIST in software Release 9.x.

The ROUTING TID provides the functionality to add and to delete a routing file. When adding a routing file, if there is currently no routing file one is created, otherwise an error occurs. When deleting, if a routing file exists, it is deleted, otherwise an error occurs.

Edits are not supported for the ROUTING TID and for CARRIERTBL, edits are only valid when using the RTLISTNAME with the RTOPTION "CARRIER".

When the first entry is added to a conditional route, the day of week of DEFAULT is used. Thus a default value is always set for all conditional routes. For all days of the week, the user enters as the first value in the set a conditional route name. Then the user can add up to four pair of time changes and conditional route names. The time changes can be configure in the range 0015 to 2345 and must be divisible by 15 minutes. A check is performed to ensure that the times are added only in ascending order.

Session Set

The session set component type represents a pair of backhaul IP links used on the Cisco PGW 2200 Softswitch. These links are used to communicate with external nodes that support IPFAS. Its MML name is as follows:

•MML Name—SESSIONSET

The session set component structure is shown in Table A-41.

Table A-41 Session Set Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique ID of this component and 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 any 128 characters.
IPADDR1	Local logical IP address 1	IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4;
IPADDR2	Local logical IP address 2	IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4;
PORT	Local port number	1025 through 65535.
PEERADDR1	Remote IP address 1	IP address; (0.0.0.0). This may also be specified as a hostname or a DNS name.
PEERADDR2	Remote IP address 2	IP address; (0.0.0.0). This may also be specified as a hostname or a DNS name.
PEERPORT	Remote port	1025 through 65535.
EXTNODE	External Node MML name	MML Name of a previously configured external node.
NEXTHOP1	Next hop address 1	IP address or hostname of the next hop; (0.0.0.0). This parameter is removed in software Release 9.4(1).
NETMASK1	Subnet mask address 1	Subnet mask address; (255.255.255.255). This parameter is removed in software Release 9.4(1).
NEXTHOP2	Next hop address 2	IP address or hostname of the next hop; (0.0.0.0). This parameter is removed in software Release 9.4(1).
NETMASK2	Subnet mask address 2	Subnet mask address; (255.255.255.255). This parameter is removed in software Release 9.4(1).
IPROUTE1	First IP route MML name	MML name of a previously configured IPROUTE. This parameter is added in software Release 9.4(1).
IPROUTE2	Second IP route MML name	MML name of a previously configured IPROUTE. This parameter is added in software Release 9.4(1).
TYPE	Sessionset external node type	BSMV0 or IPFAS.

The following rules apply when you are creating or editing session sets:

•The ISDNSIGTYPE of the EXTNODE must be N/A if the TYPE is IPFAS.

•The type of the session set must be BSMV0 for C7 session sets.

•The type of the session set must be IPFAS for IPFAS session sets.

•IP addresses cannot be split across session sets. For example if SET 1 has IP_Addr1 and IP_Addr2, then SET 2 cannot have IP_Addr1 and IP_Addr3.

•If IPADDR2 or PEERADDR2 is specified, they must both be specified. In other words you cannot have one local address and two remote addresses, or two local addresses and one remote address.

•IPADDR1 and IPADDR2 must have different values.

•PEERADDR1 and PEERADDR2 must have different values except when the EXTNODE is a VISM (MGX8850).

•The maximum number of IPFAS session sets per port is 50.

•The PORT attribute cannot be set to the same value as the PORT attribute of any ASSOCIATION, IPLNK, or SIPLNK.

•The PORT attribute cannot be set to the same value as the PORT attribute of another SESSIONSET with a different TYPE value. In other words the PORT value of a BSMV0 SESSIONSET cannot be the same as the PORT value of an IPFAS SESSIONSET.

•When IPROUTE1 or IPROUTE2 is specified the IP address resolved from the PEERADDR1 or PEERADDR2 attribute must be checked against the DESTINATION and NETMASK attributes to verify that the IPROUTE is valid.

•When IPROUTE1 is specified, the IPADDR must match the IPADDR1 of the session set.

•When IPROUTE2 is specified, the IPADDR must match the IPADDR2 of the session set.

•When IPROUTE1 or IPROUTE2 is not specified, the IP address resolved from the PEERADDR1 or PEERADDR2 attribute is checked against the defined IPROUTES to determine whether they should assigned to one of the IPROUTEs. If the PEERADDR is on the same subnet as an IPROUTE, the link should use that IPROUTE.

•Another IPLNK, SESSIONSET, or ASSOCIATION with a different EXTNODE cannot use the resolved value of PEERADDR.

A Session Set is a logical representation of one or two backhaul IP links. The SESSIONSET MML command generates a Session Set that is one or two (if PEERADDR2 is specified) Backhaul IP Links. The names are NAME-1 and NAME-2. The DESCRIPTIONs are Session Set NAME Backhaul Link 1 and Session Set NAME Backhaul Link 2.

All MML commands (add, edit, delete, and retrieve) are performed against the IP link pair by specifying only the NAME. Retrieving a session set displays the backhaul IP links (there may only be one) for the session set. Retrieving all session sets displays all backhaul IP links.

SGP

This is the Cisco PGW 2200 Softswitch NE component type and represents an SS7 signaling gateway process. Its MML name is as follows:

•MML Name—SGP

The SGP structure is shown in Table A-42.

Table A-42 SGP Component Structure

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique ID of this component and 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 any 128 characters.
EXTNODE	MML name of the external node	MML name of a previously configured external node.

Keep the following in mind when creating or editing external nodes

•A maximum of four SGPs are allowed for each external node.

SIP IP Link

This is the Cisco PGW 2200 Softswitch NE component type and represents a SIP IP link used on the Cisco PGW 2200 Softswitch NE. These links are used to communicate with the SIP proxy servers. Its MML name is as follows:

•MML Name—SIPLNK

The SIP link component structure is shown in Table A-43.

Table A-43 SIP Link Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique ID of this component and 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 any 128 characters.
IF	Ethernet interface MML name	MML name of a previously defined Ethernet interface. This parameter is removed in software Release 9.4(1).
PORT	Local port number	Any valid IP port number greater than 1024 (Recommended setting of 5060 for SIP).
PRI	Priority	Integer greater than 0; (1).
IPADDR	Local logical IP address	IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4.
SVC	Signaling service this IP supports	MML name of a previously defined signal service.
NEXTHOP	Next hop address	IP address or hostname of the next hop; (0.0.0.0). This parameter is removed in software Release 9.4(1).
NETMASK	Subnet mask address	Subnet mask address; (255.255.255.255). This parameter is removed in software Release 9.4(1).

SIP Signaling Service

This component type represents the SIP signaling service or signaling path to SIP proxy servers. Its MML name is as follows:

•MML Name—SIPPATH

The SIP signaling service component structure is shown in Table A-44.

Table A-44 SIP Path Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
MDO	MDO file name	Valid protocol name from variants.dat (IETF_SIP is the only valid MDO variant for this signaling service.).
ORIG LABEL	Originating call control (OCC) side location label. Used for Call Limiting feature.	As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).
TERM LABEL	Terminating call control (TCC) side location label. Used for Call Limiting feature.	As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).

SS7 Route

The SS7 route component type represents an SS7 route. It is used to determine how to get an SS7 message to a particular destination. Its MML name is as follows:

•MML Name—SS7ROUTE

The SS7 route component structure is shown in Table A-45.

Table A-45 SS7 Route Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DPC	Destination point code MML name	MML name of a previously defined point code.
LNKSET	Linkset MML name	MML name of a previously defined linkset.
OPC	Originating point code MML name	MML name of a previously defined point code.
PRI	Priority	Integer greater than 0; (1).

SS7 Signaling Service Properties

The SS7 signaling service properties component types serve as configuration parameters that you can use to tune signaling service communications. These properties apply to all SS7 signaling services you create. You do not have to enter these values. Its MML name is as follows:

•MML component name: SIGSVCPROP

The SS7 signaling service structure is shown in Table A-46.

Table A-46 SS7 Signaling Service Property Descriptions 

Parameter MML Name	Parameter Description	Parameter Values
adjDestinations	Number of adjacent destination point codes.	Value range: 1 through 256. Default = 16
AInternationalPrefix	International prefix string to be added to the international dialed number when NOA is enabled.	Value range: NULL or a numeric string. Default = NULL
ANationalPrefix	National prefix string to be added to the national dialed number when NOA is enabled.	Value range: NULL or a numeric string. Default = NULL
BothwayWorking	Set to 0 to disable both way release/circuit free handling for BTNUP protocol.	Values: 0 or 1. Default = 1
CGBA2	Determines if group (0) or individual (1) circuit group blocking acknowledgments (CGBAs) are required before the blocking is considered successful. Applicable only to ANSI SS7, IBN7, and CTUP protocols. (Only available in software Release 9.3(2) and later.) Note When set to 1, a significant performance impact occurs for individual circuit supervision messages during maintenance or during a failure condition.	Values: 0 or 1. Default = 0
CLIDefaultAllowed	Sets the presentation restricted field in the calling line identity (CLI). When set to TRUE and an incoming Q931 setup message has the presentation restricted indicator absent, then the presentation restricted indicator in the outgoing message (IAM or setup) is set to presentation allowed. When set to FALSE and an incoming Q931 setup message has the presentation restricted indicator absent, then the presentation restricted indicator in the outgoing message (IAM or setup) is set to presentation restricted.	Values: TRUE (1) or FALSE (0) Default: FALSE Note Used in all protocols that are based on Q761. Note Only valid for ISDN PRI inbound to either C7 ISUP outbound or ISDN PRI outbound.
CLIPEss	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.	Values: 0, 1, or 2. Default = 0
COLDefaultAllowed	Sets the presentation restricted field in the connected line identity. When set to TRUE and an incoming Q931 setup message has the presentation restricted indicator absent, then the presentation restricted indicator in the outgoing message (IAM or setup) is set to presentation allowed. When set to FALSE and an incoming Q931 setup message has the presentation restricted indicator absent, then the presentation restricted indicator in the outgoing message (IAM or setup) is set to presentation restricted.	Values: TRUE (1) or FALSE (0) Default: FALSE Note Used in all protocols that are based on q761 except HONG_KONG, AUSTRALIA, FRENCH, NTT, JAPAN_JT.
CotInTone	Receive tone for continuity test (COT) hardware. The tone to listen for when doing a COT. Enter value in Hz.	Value: 1780 or 2010. Default = 2000 ± 20
CotListenDuration	Maximum period to listen for a COT.	Value range: 0 through 200, specified in milliseconds (should be less than 2 seconds). The T24 timer will be set for 60. Default = 60
CotOutTone	Transmit tone for COT hardware. The tone that is produced.	Enter value in Hz. Value: 1780 or 2010. Default = 2000 ± 20
CotPercentage	Statistical COT.	Value range: 0 through 100%. Default = 0
CotPlayDuration	Maximum period in not aligned state before return to out-of-service state (should be less than or equal to the CotListenDuration).	Value range: 1 through 200, specified in milliseconds. Default = 60
dialogRange	TCAP transaction ID range (for example, 1 through 10000) for a specific subsystem.	0 = entire range. Default = 0
ExtCOT	Determines the type of COT handling for the specified destination.	Values: 0—no COT, loop, or transponder. Default = Loop
ForwardCLIinIAM	Set to 1 if outgoing IAM should contain the calling line identity, if available. Only applicable for BTNUP when interworking from other protocols.	Values: 0 or 1. Default = 0
ForwardSegmentedNEED	Set to 0 to disable the forwarding of segmented NEED messages within the BTNUP_NRC protocol. If segmenting is disabled, all mandatory DPNSS information elements are packed into a single BTNUP NEED message.	Values: 0 or 1. Default = 1
GLARE	Call collision handling.	Valid values are: •0 = No glare handling; also known as yield to all double seizures. Call collision results in a REL sent to both calls. Note Both ends of a link can be given this option. •1 = The Cisco PGW 2200 Softswitch has control of all circuits, and any call collisions are handled by this Cisco PGW 2200 Softswitch. The Cisco PGW 2200 Softswitch ignores incoming IAMs and proceeds with its own calls as normal. Note Only one end of a link can be designated with this option. •2 = Highest point code controls the even circuits. Depending on the OPC of the Cisco MGCs, the side that has the higher point code controls the even circuits, and the side that has the lower point code controls the odd circuits. Note Both ends of a link can be given this option. •3 = No control. The Cisco PGW 2200 Softswitch specified with this option does not control any circuits. The Cisco PGW 2200 Softswitch accepts incoming IAMs from the side with control. Note This option is usually used along with the remote node designated with control. Default = 0
GRA2	Determines if paired (0) or single (1) group reset acknowledgments (GRAs) are required before the reset is considered successful. Only applicable to ANSI SS7, IBN7, and CTUP protocols.	Values: 0 or 1. Default = 0
GRSEnabled	This property is assigned to an SS7 point code type signal path. Enables group reset and blocking procedure at point code initialization. Synchronizes the Cisco PGW 2200 Softswitch bearer channel blocking state with that of the end office.	Values: false or true. If true, GRS messages are sent for all CICs associated with the point code. If false, GRS messages are not sent. Default = false
GRSonSSCEnabled	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.	Values: false or true. If true, the GRS message is sent to the far end point code for all CICs associated with the point code after the point code was put in-service again. If false, the GRS message is not sent. Default = false
hopCount	Default hop count.	Value range: 0 or 15 (this indicates the maximum number of hops allowed for SCCP messages). Default = 1
layerRetries	Number of times to resend request to adjacent layer without getting a response.	Value range: 0 through 5. 0 = no retries. Default = 2
layerTimer	Time (in tenths of a second) to wait for a response 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. Default = 10
maxMessageLength	Maximum length of message to MTP3.	This value must be less than the value for mtp2MaxMsuFrmLen. Value range: 0 through 272. Default = 250
NatureOfAddrHandling	Determines whether or not preanalysis is performed	Default = 0
NFASImplicitInterfaceId	Is used when an incoming ISDN message containing a Channel identification information element identifier with bit 7 of octet 3 set to 0 (Interface implicitly identified) as the implied interface ID value. This property is added in software Release 9.5(2).	Value range: 0 through 127. Default = 65535
Normalization	Normalization of dialed number to unknown.	Set to 0 for disabled and 1 for enabled. Values: 0 or 1. Default = 0
OD32DigitSupport	Allows 32 digits and overdecadic digits support for the ANSI, Q.761, and Q.767 protocol variants for the ANSI, SS7-ITU, SS7-China, SS7-Japan, and SS7-UK protocol families. This property is added in software Release 9.4(1).	Values are: 0 (disabled) and 1 (enabled). Default = 0
OMaxDigits	Specifies maximum number of digits to receive for overlap digit processing for call origination from this traffic path.	Value range: 0 through system maximum. Default = 24
OMinDigits	Specifies minimum number of digits to receive for overlap digit processing for call origination from this traffic path.	Value range: 0 through system maximum. Default = 0
OmitCgPnFromUnavailable	Determines if mapping between the SIP From header to the IAM calling party number is enabled when the SIP message header From is "unavailable". This property is added in software Release 9.5(2).	Values are: 0 (enabled) and 1 (disabled). Default = 0
OOverlap	Set to 1 to enable overlap signaling for call origination from this traffic path.	Value range: 0 through system maximum. Default = 0
OverlapDigitTime	Overlap interdigit timer. The time to wait for the rest of the digits. Note If OverlapDigitTimeValue timer is set to more than thirty seconds, other timers expire before this timer.	Value range: 0 through 60. Default = 6
OwnClli	Specifies the common language location identifier (CLLI).	Value range: Alphanumeric string, up to 11 characters.
RedirMax	Specifies the maximum allowable value of the redirection counter parameter available in some C7 signaling systems before the call is force-released. Used to prevent routing loops in certain applications.	Default: 5 Value range prior to Release 9.7(3) S22P22: 0 to system maximum. Value range for Release 9.7(3) S22P22 and later: 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 OCC = Originating (side) call control. TCC = Terminating (side) call control.
restartTimer	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. Default = 10
RoutePref	Determines the preferred route.	Value range: 0 through 9. 0 = No Preference (default) 5 = IP Preferred 1 = ATM Essential 6 = IP Excluded 2 = ATM Preferred 7 = TDM Essential 3 = ATM Excluded 8 = TDM Preferred 4 = IP Essential 9 = TDM Excluded Default = 0
SdpXmitToH323Trigger	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). This property is added in software Release 9.4(1).	Value range: 0 through 3. 0 = terminating seizure, 1 = Address complete, 2 = Alerting or Inband information available, or 3 = Answer. Default = 0
sendAfterRestart	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. Default = SS7-ANSI = 16
slsTimer	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. Default = SS7-ANSI = 300
srtTimer	Time (in tenths of a second) between the sending of Subsystem Route Test message (SRT) to remote subsystems.	Value range: 0 through 3000. 0 = disabled, 300 = 30 seconds. Default = SS7-ANSI = 300
sstTimer	Time (in tenths of a second) between the sending of Subsystem Status Test (SST) messages to an unavailable remote subsystem.	Value range: 0 through 3000. 0 = Disabled, 300 = 30 seconds Default = SS7-ANSI = 300
standard	Version of protocol standard supported for this STP/SCP.	SS7-ANSI = ANSI96, SS7-ITU = ITU96, ANSI96, ITU96, ANSI92, ITU92
TMaxDigits	Specifies maximum number of digits to receive for overlap digit processing for call termination to this traffic path.	Value range: 0 through system maximum. Default = 24
TMinDigits	Specifies minimum number of digits to receive for overlap digit processing for call termination to this traffic path.	Value range: 0 through system maximum. Default = 0
TOverlap	Set to 1 to enable overlap signaling for call termination to this traffic path.	Values: 0 or 1. Default = 0
variant	SS7 protocol variants supported by the local subsystem.	Default = SS7-ANSI=SS7-ANSI,SS7-ITU
VOIPPrefix	A numeric string.	Default = 0

SS7 Signaling Service (sigpath)

The SS7 Signaling Service (sigpath) component type represents an SS7 signaling service or signaling path to a particular SS7 switch (destination). Its name is as follows:

•MML Name—SS7PATH

The SS7 signaling service component structure is shown in Table A-47.

Table A-47 SS7 Signaling Service Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique ID of this component and 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 any 128 characters.
SIDE	Q.931 call model side	String user for user side and network for network side; (network).
MDO	MDO file name	Valid protocol name from variants.dat. (This is limited to any MDO SS7 protocol variant.)
DPC	Destination point code MML name	MML name of a previously defined point code.
CUSTGRPID	Customer group ID	Four digit ID; (0000).
OPC	Originating Point Code MML name	MML name of a previously defined point code.
ORIG LABEL	Originating call control (OCC) side location label. Used for Call Limiting feature.	As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).
TERM LABEL	Terminating call control (TCC) side location label. Used for Call Limiting feature.	As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).

SS7 Subsystem

The SS7 subsystem component type represents an SS7 subsystem. It is used for specifying mated STPs and to provide LNP support through a SCP. Its MML name is as follows:

•MML Name—SS7SUBSYS

The SS7 subsystem component structure is shown in Table A-48.

Table A-48 SS7 Subsystem Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
LOCALSSN (formerly SSN)	Subsystem number	Integer from 2 through 254;(0) When mating STPs, SSN = 0. When using Intelligent Network (IN) services, SS7-ANSI, SS7-ETSI, or SS7-ITU, Local SSN can be set to a value greater than 0. Default = 0.
MATEDAPC	Adjacent point code of the mated STP	MML name of a previously defined adjacent point code. It is only used when mating STP pairs. It is not used when creating AIN subsystems.
OPC	Originating point code MML name of the mated STP	MML name of a previously defined originating point code. Not used if SUAKEY is specified.
PRI	Priority	Integer greater than 0; (1). Not used when mating STP pairs.
PROTO	Protocol family	SS7-ANSI or SS7-ITU when creating an AIN subsystem. SS7-ANSI, SS7-China, SS7-ITU, SS7-Japan, and SS7-UK when mating an STP pair.
REMOTE SSN	Remote subsystem number	Integer from 2 through 254;(0). Can be set to non-zero only for SS7-ANSI, SS7-ETSI, or SS7-ITU. If set to 0, the subsystem is used for mating two STPs. Use LOCALSSN if not specified. Can only be set to non-zero for SS7-ANSI, SS7-ETSI, or SS7-ITU.
SUAKEY	MML name of SUAKEY	MML name of previously defined routing key. This is an optional parameter and is used only for SUA. Not used if OPC is specified.
SVC	MML name of Adjacent point code or TCAP/IP service	MML name of a previously defined adjacent point code, or MML name of a previously defined TCAP/IP service.
STPSCPIND	STP/SCP index used for IN triggers	Integer greater than 0; (0). Not used when mating STP pairs.
TRANSPROTO	Transport protocol	•SCCP— Use if SVC is an APC •SUA— Use for Sigtran carrying TCAP over SUA •TCPIP— Use if SVC is TCAP over IP This parameter is not needed when mating STP pairs.

---

Note SSN has been renamed LOCALSSN to clarify the intent of the parameter. There is continued support of SSN for the MML command line. If both SSN and LOCALSSN are specified, LOCALSSN is used. When using the prov-exp command, LOCALSSN is used.

---

SUA Key

This component represents a SUA Routing key. The parent component for the SUAKEY is the OPC.

•MML Name—SUAKEY

The SUA key component structure is shown in Table A-49.

Table A-49 SUAKEY Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	M3UA key name	The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
DESC	Component description	The description can be up to any 128 characters.
OPC	Associated OPC	MML name of a previously configured OPC.
APC	Associated APC (optional)	MML name of a previously configured APC.
LOCAL SSN	Associated local SSN	Number of a local SSN. Values are 0, 2-254 (0).
ROUTING CONTEXT	Routing context value	Any integer except 0 (0 indicates no routing context). Each SUA key must have a unique routing context.
NETWORK APPEARNCE	Network appearance (optional)	This parameter is optional. The valid values are integers from 1 through 32767. A value of 0 indicates an invalid network appearance.

---

Note None of the parameters for this command can be modified.

---

The following rules apply when creating SUA keys:

•You can provision up to 256 SUA keys.

•Up to 64 OPCs can use SUA signaling services.

•Parent OPC must be a true OPC

•Cannot be deleted if it is being used by an SS7 signaling service

•Two M3UA keys or SUA keys cannot have the same routing context value

SUA Route

This component represents a SUA route. It is used to determine how to get an SS7 message to a particular destination using SUA.

• MML Name—SUAROUTE

The SUA route component structure is shown in Table A-50.

Table A-50 SUAROUTE Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	SUA route name	The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
DESC	Component description	The description can be up to any 128 characters.
APC	Associated APC	MML name of a previously configured APC.
EXTNODE	Associated external node	MML name of a previously configured external node.
OPC	Associated OPC	MML name of a previously configured OPC.
REMOTESSN	Associated remote SSN	Number of a remote SSN. Values are 0, 2-254 (0).

---

Note NAME is the only parameter for this command that cannot be modified.

---

The following rules apply when creating/editing SUA routes:

•The associated APC must have an SS7 subsystem with an SUA key defined. If an SUA key is not defined when the provisioning session is saved and activated, an error message is generated and the operation is stopped.

•Multiple APCs with the same NETADDR cannot be routed to the same OPC.

•The associated OPC must be a true OPC.

•For a given OPC, DPC, and remote SSN set, only one route can be defined through a given external node.

•Up to two SUA routes can be defined per OPC, APC, and remote SSN set.

•The associated external node must support SUA signaling.

•SUA routes for the same OPC-APC pair must have external nodes in the same group.

•When the provisioning session is saved and activated, there must be an ASSOCIATION of type SUA using an SGP that is using the EXTNODE of each SUAROUTE.

SS7 Signaling Gateway Process

This component represents a SS7 signaling gateway process.

•MML Name—SGP

The SS7 signaling gateway process component structure is shown in Table A-51.

Table A-51 SGP Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	M3UA route name	The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
DESC	Component description	The description can be up to any 128 characters.
EXTNODE	External node that is running the SS7 signaling gateway process	MML name of a previously defined external node

---

Note DESC is the only parameter for this command that can be modified.

---

The following rules apply when creating/editing SS7 signaling gateway processes:

•You can provision up to 96 M3UA SS7 signaling gateway processes.

•You can provision up to 8 SUA SS7 signaling gateway processes.

•For the provisioning session to be copied or deployed without error, an SCTP association must be using the SS7 signaling gateway process.

Switched Trunk Provisioning

This is the Cisco PGW 2200 Softswitch NE component and represents a trunk (switched bearer channels). Its MML name is as follows:

•MML Name—SWITCHTRNK

The switched trunk provisioning component structure is shown in Table A-52.

Table A-52 Switched Trunk Provisioning Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Trunk group member number	Integer greater than 0
TRNKGRPNUM	Trunk group number	Integer from 1 through 65535. This parameter is mandatory for all operations
SPAN	Span	Integer from 1 through 65535 or ffff
CIC	Circuit Identifier Code.	Integer from 1 through 65535
CU	Coding Unit MML name	MML name of a previously defined CU
ENDPOINT	End point	End point
SPANSIZE	Number of trunks per span.	Integer greater than 0 and less than 31; (1)

TARIFF

This is the Cisco PGW 2200 Softswitch NE component used to provision entries in the Tariff table. Its MML name is as follows:

•MML Name—TARIFF

The switched trunk provisioning component structure is shown in Table A-53.

Table A-53 Tariff Provisioning Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
TARIFFID	Tariff ID	Integer from 1 through 9999.
TARIFFRATE	Tariff rate	Integer from 1 through 999999.
SCALEFACTOR	Scale factor	Integer; 0, 1, 2, 3, 249, 250, 251, 252, 253, 254, or 255.

Backhaul TCP Link

The Backhaul TCP link component represents a static IP route. Its MML name is as follows:

•MML Name—TCPLINK

---

Note This component is added in software Release 9.5(2).

---

The Backhaul TCP link component structure is shown in Table A-54.

Table A-54 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 associated external node	MML name of a previously provisioned Cisco BRI 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 ISDN BRI signaling services:

•You must define the TYPE parameter as PRI. If the TYPE parameter is not defined as PRI when the TCPLINK is added/edited, a warning is issued. If the TYPE parameter is not defined as PRI when the provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.

•You must define the TCPLINK parameter with the same EXTNODE attribute that its associated BRIPATH has. If the TCPLNK is not defined when the BRIPATH is added/edited, a warning is issued. If the TCPLINK is not defined when the provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.

•If the TCPLINK with the same EXTNODE value as the BRIPATH is deleted, a warning message is issued to inform you that the BRIPATH must also be deleted. If the BRIPATH is not deleted when the provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.

•Only two combinations of local IP address and port number can be used per Cisco PGW 2200 Softswitch. Once you have identified two unique local IP address and port number combinations, all subsequent Backhaul TCP links must use one of those combinations.

TDM Interface

The TDM interface component type represents a TDM interface used on the Cisco PGW 2200 Softswitch. Its MML name is as follows:

•MML Name—TDMIF

---

Note This component is removed in software Release 9.4(1).

---

The TDM interface component structure is shown in Table A-55.

Table A-55 TDM Interface Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
CARD	Card which supports this TDM interface	MML name of a previously defined card or index of the card for SNMP
LIFNUM	Line interface number	1 to 4 for V.35, 1 otherwise; (1)
RESIST	Resistance (in Ohms)	75 for ITK(T1), 120 for ITK (E1); otherwise 0; (75)
DATARATE	Data rate	Used only for V.35 card. Values are 48,56, or 64. (64)
CLOCK	Internal or external	Used only for V.35 card. Values are EXT, INT; otherwise NA; (EXT).
DTEDCE	DTE or DCE	Used only for V.35 card. Values are DTE, DCE; otherwise NA; (DTE).
CODING	Line coding	Used only for ITK card. AMI (alternate mark inversion) and B8ZS (bit stuffing for clear channel) for T1, HDB3 for E1; Default value is B8ZS for T1, HDB3 for E1, and NA for V.35. (B8ZS)
FORMAT	Interface Format	Used only for ITK card. ESF (extended super frame) and D4 (super frame) for T1, CRC4 and CCS for E1. Default value is ESF for T1, CRC4 for E1, and NA for V.35. (ESF)
SIGTYPE	Signal type	T1 for DS1 T1, CEPT for European E1, V.35 for 64KBPS digital. (T1)
HDLC	High-level Data Link Control	DEFAULT(HDLC) and IHDLC for ITK; otherwise not used; (DEFAULT)

TDM Link

The TDM link component type represents a TDM link used on the Cisco PGW 2200 Softswitch. Its MML name is as follows:

•MML Name—TDMLNK

---

Note This component is removed in software Release 9.4(1).

---

The TDM interface component structure is shown in Table A-56.

Table A-56 TDM Link Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Unique component name used in MML commands	The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
DESC	Component description	The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
SLC	Signaling Link Code	0 to 15; (1)
PRI	Priority	Integer greater than 0; (1)
SVC	Signaling service this link supports	MML name of a previously defined signal service or linkset or index of the signal service for SNMP
IF	TDM interface this link is on	MML name of a previously defined TDMIF or index of the TDMIF for SNMP
TIMESLOT	Timeslots this link uses	1 to 32 for E1, 1 to 24 for T1; (1)

Trunk Group Provisioning

Trunk group provisioning component type represents a trunk group. This component is supported by MML only. Its MML name is as follows:

•MML Name—TRNKGRP

The trunk group provisioning interface component structure is shown in Table A-57.

Table A-57 Trunk Group Provisioning Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Trunk group number	Integer 1 through 9999 (none);
CLLI	CLLI	Value range: Alphanumeric string, up to 11 characters.
SVC	Signaling service	MML name of a previously defined SS7, IPFAS, or FAS signaling service.
TYPE	Trunk group type	One of the following, ATM, CTI, IP, IP_SIP, SIP_IN, TDM_ISUP, TDM_CAS, TDM_TUP, TDM_GEN, TDM_DPNSS, TDM_PRI, TDM_BTNUP. Trunk group type IP is used with EISUP signaling service. TDM_PRI is used with IPFAS or FAS signaling services with the protocol family of ISDNPRI. TDM_DPNSS is used with signaling services with the protocol family of DPNSS. TDM_ISUP is used with SS7 signaling services with switch types of 0, 5, 20, 23, 40. TDM_TUP is used with SS7 signaling services with switch type of 5. TDM_BTNUP is used with SS7 signaling services with SS7-UK variants with switch type of 5.TDM_GEN is used with SS7 signaling services with switch types not equal to 0, 5, 20, 23, 40. TDM_CAS is currently not supported. TDM_CAS is used with CAS signaling service. IP_SIP is used for SIP signaling services at the terminating side. SIP_IN is used for SIP signaling services at the originating side and only one such trunk group can be configured on each Cisco PGW 2200 Softswitch node. CTI is used for CTI signaling. Switch type values are: 0 = No switch-specific 23 = SS7 ANSI logic for the signaling path. 26 = DPNSS 5 = BTNUP 27 = NET5 10 = SS7 Japan 29 = QSIG MASTER 17 = 5ESS 30 = QSIG SLAVE 20 = SS7 Clear 40 = SS7 ITU 22 = NI2
SELSEQ	Select sequence	One of the following, LIDL, MIDL, ASC, DESC, RDM, EDESC, ODESC, EASC, OASC, CASC, CDESC, or ITU2.
QABLE	Timeslot this link uses	Y or N; (N)
ORIG LABEL	Originating call control (OCC) side location label. Used for Call Limiting feature.	As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).
TERM LABEL	Terminating call control (TCC) side location label. Used for Call Limiting feature.	As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).

Trunk Group Profile MML Provisioning

This is used to configure the trunk group profiles. Its MML name is as follows:

•MML Name—TRNKGRPROF

The trunk group profile provisioning component structure is shown in Table A-58.

Table A-58 Trunk Group Profile Provisioning Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	Trunk group name used in MML commands	The name can be as many as twenty alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
<PROFILETYPENAME>	Profile type name	The name can be as many as twenty alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.

GTD Parameter Provisioning

This is used to configure the GTD parameters. Its MML name is as follows:

•MML Name—GTDPARAM

The GTD provisioning component structure is shown in Table A-59.

Table A-59 GTD Parameter Provisioning Component Structure 

Parameter MML Name	Parameter Description	Parameter Values (Default)
NAME	GTD parameter name used in MML commands	The name can be as many as twenty alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
GTDPARAMSTRING	GTD parameter string	A string with a length less than or equal to 460 characters.
OVERRIDESTRING	GTD override fields string	A string with a length less than or equal to 256 characters.

Table A-60 lists the GTD parameters that can be entered in the build_string in alphabetical order.

Table A-60 GTP Parameters 

GTD Parameter	GTD Parameter Description
ACL	Automatic Congestion Level
ADI	Access Delivery Information
APP	Application Transport
ATP	Access Transport
BCI	Backward Call Indicators
BSG	Business Group
BVN	Backward GVNS
CAI	Cause Indicators
CCN	CCNR Possible Indicator
CCS	Call Completion Service Setup
CDI	Call Diversion Information
CDN	Called Directory Number
CDT	Call Diversion Treatment Indicators
CGL	Calling Geodetic Location
CGN	Calling Party Number
CHI	Call History Information
CHN	Charge Number
CIC	Circuit Identification (Call Instance) Code
CID	Carrier Identification
CIN	Called IN Number
CMI	Call Modification Indicators
CNF	Conference Treatment Indicator
CNN	Connected Number
CNR	Connection Request
COL	Collect Call Request
COR	Correlation Identity
CPC	Calling Party Category
CPN	Called Party Number
CRF	Call Reference
CSI	Carrier Selection Information
CSP	Carrier Service Provider Information
CTI	Continuity Indicators
CTN	Call Transfer Number
CTR	Call Transfer Reference
DIS	Display Information
ECI	Echo Control Information
EGR	Egress
EVI	Event Information Indicators
FAI	Facility Indicators
FCI	Forward Call Indicators
FDC	Known Field Compatibility Information
FVN	Forward GVNS
GCI	Global Call Identification
GEA	Generic Address
GED	Generic Digits
GEN	Generic Name
GIC	Closed User Group Interlock Code
GNO	Generic Notification
GRF	Generic Reference
HOC	Hop Counter
HTR	Hard To Reach
INI	Information Indicators
IRI	Information Request Indicators
ISC	Originating ISC point Code
JUR	Jurisdiction
LON	Location Number
LPI	Loop Prevention Indicator
LSP	Local Service Provider Information
MCI	Message Compatibility Information
MCR	MCID Response indicator
MLP	MLPP precedence
MRI	MCID Request Indicator
NET	Network Transport
NMC	Network Management Controls
NOC	Nature of Connection Indicators
NPF	Number Portability Forward Information
NRN	Network Routing Number
NSF	Network Specific Facilities
OBI	Optional Backward Call Indicators
OCI	Original Called IN Number
OCN	Original Called Number
OCT	Call Offering Treatment Indicators
OFI	Optional Forward Call Indicators
OLI	Originating Line Information
OSI	Operator Services Information
OTN	Outgoing Trunk Group Number
PBI	Pivot Backward Information
PCA	Pivot Capability
PCI	Parameter Compatibility Information
PCT	Pivot Counter
PDC	Propagation Delay Counter
PFI	Pivot Forward Information
PRI	Pivot Routing Indicator
PRN	Protocol Name
PVS	Pivot Status
QOR	Query On Release Capability
RBI	Redirect Backward Information
RCT	Redirect Counter
RDC	Redirect Capability
RDS	Redirect Status
RFI	Redirect Forward Information
RGN	Redirecting Number
RMO	Remote Operations
RNI	Redirection Information
RNN	Redirection Number
RNR	Redirection Number Restriction
SCF	SCF ID
SCI	Service Code Indicator
SEA	Service Activation
SEG	Segmentation Indicator
SPC	Signaling Point Code
SPR	Special Processing Request
SRI	Suspend/Resume Indicators
SUN	Subsequent Number
TID	Transaction ID
TMP	Transmission Medium Required Prime
TMR	Transmission Medium Required
TMU	Transmission Medium Used
TNS	Transit Network Selection
TRR	Transaction Request
UCI	UID Capability Indicators
UFC	Unknown Field Compatibility Information
UID	UID Indicators
USI	User Service Information
USP	User Service Information Prime
UTI	User Teleservice Information
UUI	User-To-User Indicators
UUS	User-To-User Information
VER	Version of GTD

Dial Plan Provisioning Components

All components have a name parameter, which is the MML name, and a description, which is a text description. The dial plan provisioning components are shown in Table A-61.

Table A-61 Dial Plan Provisioning Components 

Component MML Name	Parameter MML Name	Parameter Description	Parameter Values (Default)
DIALPLAN	OVERDEC	Overdecadic Status	The value can be either YES, or NO. This parameter is only used when adding a dial plan; (NO)
ADIGTREE	SETNAME	Result Set Name	MML name of the result set; (x)
	DIGITTOPRESENT	Digit	It is set to 0 if it is the next digit otherwise it is the appropriate digit application point; (0)
	CALLSIDE	string	Call side is like originating, terminating; (x)
	DIGITSTRING	Digits	Could not use with NEXTNODE or DIGIT or INDEX; (x)
BDIGTREE	SETNAME	Result Set Name	MML name of the result set; (x)
	DIGITTOPRESENT	Digit	It is set to 0 if it is the next digit otherwise it is the appropriate digit application point; (0)
	CALLSIDE	string	Call side is like originating, terminating; (x)
	DIGITSTRING	Digits	Could not use with NEXTNODE or DIGIT or INDEX; (x)
RESULTTABLE	NAME	Result Name	MML name of the result; (x), has to be set
	RESULTTYPE	Result type	; (0)
	DW1	Data word 1	; (x)
	DW2	Data word 2	; (x)
	DW3	Data word 3	; (x)
	DW4	Data word 4	; (x)
	NEXTRESULT	Next result name	; (x)
	SETNAME	Result Set Name	MML name of the result set; (x), has to be set
DIGMODSTRING	NAME	Digit Modification Name	MML name of the digit modification string; (x)
	DIGSTRING	Digit string	; (x)
ANOA	NOAVALUE	A-number NOA Value	; (0)
	NPIBLOCK	NPI index	; (0)
	SETNAME	Result Set Name	MML name of the result set; (x)
ANPI	NPIBLOCK	A-number NPI block	; (0)
	BLOCKVALUE	Block value	0 to 15; (-1) If the block value is not specified the result index is applied to all block values (0 to 15).
	SETNAME	Result Set Name	MML name of the result set; (x)
BNOA	NOAVALUE	B-number NOA Value	; (0)
	NPIBLOCK	NPI index	; (0)
	SETNAME	Result Set Name	MML name of the result set; (x)
BNPI	NPIBLOCK	B-number NPI block	; (0)
	BLOCKVALUE	Block value	0 to 15; (-1) If the block value is not specified the result index is applied to all block values (0 to 15).
	SETNAME	Result Set Name	MML name of the result set; (x)
CAUSE	CAUSEVALUE	Cause Value	; (0)
	LOCATIONBLOCK	Location block	; (0)
	SETNAME	Result Set Name	MML name of the result set; (x)
LOCATION	LOCATIONBLOCK	Location Block	; (0)
	SETNAME	Result Set Name	MML name of the result set; (x)
	BLOCKVALUE	Block value	0 to 15; (-1) If the block value is not specified the result index is applied to all block values (0 to 15).
SERVICE	NAME	Service name	MML name of the service; (x)
RESULTSET	NAME	Result Set Name	MML name of the result set; (x), has to be set
AWHITE	CLI	Calling Line Identity
ABLACK	CLI	Calling Line Identity
BWHITE	CLI	Calling Line Identity
	SVCNAME	Service name	MML name of a previously defined service; (x)
BBLACK	CLI	Calling Line Identity
	SVCNAME	Service name	MML name of a previously defined service; (x)
PORTTBL	DIGITSTRING	Ported Number Table	; (x)
	ROUTENUM	Routing Number	; (x)
TERMTBL	DIGITSTRING	Number Termination Table	; (x)
	RTLISTNAME	Route List Name	; (x)
ACHGORIGIN	CUSTGRPID	Customer Group Identity
	CLI	Calling Line Identity
	CORIGIN	Charge Origin	The charge origination field. Value range: 0 to 9999; (0)
DEFRESULSTSET	RESULTTYPE	Result Type	; (0)
	DW1	Data Word 1	; (x)
	DW2	Data Word 2	; (x)
	DW3	Data Word 3	; (x)
	DW4	Data Word 4	; (x)
DPSEL	NEWDP	New Dial Plan Identity	Value range: Alphanumeric string, of 4 characters.
ANUMDPSEL	CLI	Calling Party Number	Value range: Alphanumeric string, up to 20 characters.
	NEWDP	New Dial Plan Identity	Value range: Alphanumeric string, of 4 characters.
RTEHOLIDAY	DATE	The date of the holiday	Format for the date is yy.mm.dd
	HDAY	Holiday day	The value can be one of the following strings: HOL1, HOL2, or HOL3
CPC	CPCVALUE	CPC value.	Value range: 0 to 255
	SETNAME	Result Set Name.	MML name of the result set; (x)
TMR	TMRVALUE	TMR value.	Value range: 0 to 255
	SETNAME	Result Set Name.	MML name of the result set; (x)
TNS	TNSVALUE	TNS value.	String value range: 000 to ffffffff
	SETNAME	Result Set Name.	MML name of the result set; (x)
CLIPREFIX	CLISETNAME	The CLI prefix set name.	Value range: 1- to 4-digit alphanumeric character string.
	CLIPREFIX	The CLI prefix.	Value range: 1 to 20 overdecadic digits (0-9 and A-F) or DEFAULT.
	CUSTGRPID	The Customer group ID.	4-digit alphanumeric string.
CLIIPADDRESS	CUSTGRPID	The Customer group ID.	4-digit alphanumeric string.
	IPADDR	The IP Address.	IP address or DEFAULT.
	SUBNETMASK	The Subnet mask.	IP address (255.255.255.255).
	CLISETNAME	The CLI prefix set name.	Value range: 1- to 4-digit alphanumeric character string.
H323IDDIVFROM	CUSTGRPID	The Customer group ID.	4-digit alphanumeric string.
	H323IDDIVFROM	H323 ID, Division header, or From field.	Value range: 1- to 32-digit alphanumeric character string.
	CLISETNAME	The CLI prefix set name.	Value range: 1- to 4-digit alphanumeric character string.

To add, modify, or delete the contents of a dial plan table, an active provisioning session is required. At the time of deploying or copying, dial plan files from the provisioning directory are copied to the active directory. Active directory for dial plan files is: /opt/MGC/dialPlan.

All the TIDs, with the exception of DIALPLAN, need a customer group ID and a name. DIALPLAN only needs customer group ID. The verb ED cannot be used with the DIALPLAN. The verb RTRV can be used with DIALPLAN to determine all of the dialplans currently configured.

Routes and digit modification string table should be provisioned before result and digit tree tables.

When an index is added to a table the missing indices are also added with default values. For example, if index 10 is added to A digit tree table, and indexes 4 to 9 are missing, they are added with default values.

When an index is deleted from a result or digit tree table, all the elements in the index are made 0s. When an index is deleted from routes or digit modification string table all the elements in the index are made `x'. When an index is deleted from any table and if there are no indexes with non-default values following this index, all the indexes following this index are deleted.

The modify command is not supported for result sets as modifications would be done at the result table level.

The modify command is not supported for the service table.

When an entry is added to the result table, the corresponding entry is added to the result set table.

When an entry is deleted from the result set table, the corresponding entries are deleted from the result table.

Index is no longer required to perform any operations on the result table, service table, or digit modification table.

The result set cannot be modified for a result table.

The TIDs dialplan, resulttable, digmodstring, noa, npi, cause, location, service, and resultset support the ability to retrieve all entries in the table by specifying "all". For example:

numan-rtrv:resultset:custgrpid="T001","all".

The TIDs adigtree and bdigtree support the ability to retrieve all entries in the table by either not specifying a digitstring or specifying an empty digitstring. For example:

numan-rtrv:adigtree:custgrpid= "T001",digitstring=""

·Configuring a result set as the default result set replaces the previous result set.

·The default result set can only have one of the following result types: BLACKLIST, ROUTE, or CAUSE.

Processes

This section describes every process that the Cisco PGW 2200 Softswitch is responsible for monitoring. Three different monitoring levels are offered:

•Active Process—A process identified in the record that is controlled and monitored directly by the Process Manager.

•Passive Process—A process identified in the record that does not communicate with the Process Manager.

•Monitoring Process—A process that periodically runs an executable or script and sets or clears an alarm based on the return code. This type of process may monitor other processes or tasks that can be checked programmatically. Examples include the amount of disk space, system daemon existence, and established process dependency.

Table A-62 contains an alphabetical listing of process names and their descriptions.

Table A-62 Processes 

Process	Description
"ALM-01"	Alarm manager. It is part of the process group XEG-01. It is an active process. If it should go down, it causes a major out-of-service alarm.
"AMDMPR-01"	Alarm and measurement dumper. It is part of the process group XEG-01. It is an active process. If it should go down, it causes a major out-of-service alarm.
"CDRDMPR-01"	CDR dumper. It is part of the process group XEG-01. It is an active process. If it should go down, it causes a major out-of-service alarm.
"CFM-01"	Configuration manager. It is part of the process group XEG-01. It is an active process. If it should go down, it causes a major out-of-service alarm.
"DSKM-01"	Disk space monitor. This shell script monitors disk space and trims back older files in case the current amount of free space is below a specified threshold. It is part of the process group PFMG-01. This is a monitoring process. If it should go down, it causes a minor out-of-service alarm.
"ENG-01"	Engine. It is part of the process group ENGG-01. It is an active process. If it should go down, it causes a critical out-of-service alarm.
"FOD-01"	Failover controller. It is part of the process group FTG-01. It is a monitoring process. If it should go down, it causes a minor out-of-service alarm.
"IOCC-01"	IOS channel controller. It is part of the process group IOSG-01. It is a passive process. If it should go down, it causes a critical out-of-service alarm.
"IOCC-02"	IOS channel controller. It is part of the process group IOSG-01. It is a passive process. If it should go down, it causes a critical out-of-service alarm.
"IOCM-01"	IOS channel manager. It is part of the process group IOSG-01. It is a passive process. If it should go down, it causes a major out-of-service alarm.
"LOG-01"	Log server. It is part of the process group LOGG-01. It is a passive process. If it should go down, it causes a minor out-of-service alarm.
"MEASAGT"	Measurements SNMP agent. It is part of the process group SNMPG-01. This is an active process. If it should go down, this is a major out-of-service alarm.
"MM-01"	Measurement manager. It is part of the process group XEG-01. It is an active process. If it should go down, it causes a major out-of-service alarm.
"MMDB-01"	TimesTen DataBase Process. It is part of the process group XEG-01. It is a passive process. If it should go down, it causes a minor out-of-service alarm.
"OPERSAGT"	Operational SNMP Agent. It is part of the process group SNMPG-01. This is an active process. If it should go down, this is a major out-of-service alarm.
"POM-01"	Provisioning Object Manager. It is part of the process group XEG-01. It is an active process. If it should go down, it causes a major out-of-service alarm.
"PROVSAGT"	Provisioning SNMP Agent. It is part of the process group SNMPG-01. This is an active process. If it should go down, this is a major out-of-service alarm.
"Replic-01"	Replicator controller. It is part of the process group ENGG-01. It is an active process. If it should go down, it causes a critical out-of-service alarm.
"TCAP-01"	TCAP and SCCP protocol handler. It is part of the process group IOSG-01. It is a passive process. If it should go down, it causes a major out-of-service alarm.

Properties

Properties are configurable entities within the Cisco PGW 2200 Softswitch system. These entities can be equipment, circuits, protocols, or software.

Properties take the following syntax:

PropertyName = PropertyValue

PropertyName can be designated either by *.propertyName or by protocolFamily.propertyName (for example, SS7-ANSI.mtp3tstSltmT2).

In a provisioning session, those properties with the protocolFamily prefix may be overridden by a linkSet component. The overridden property is then written to properties.dat as: LinkSetMMLName.propertyName.

Those default properties prefixed by an "*" may be overridden by a signalPath (or Service) component that is defined in sigPath.dat. The overridden property will be written to properties.dat as SigPathMMLName.propertyName.

You can find all of the Cisco PGW 2200 Softswitch properites in Chapter 6, "Properties" of Cisco PGW 2200 Softswitch Release 9 MML Command Reference.

Protocol Variants

The tables in this section list the protocol variants supported for the corresponding software release.

Software Release 9.3(2) Protocol Variants

Table A-63 provides a snapshot of the protocol variants supported in the Cisco PGW 2200 Softswitch software Release 9.3(2) as of February 19, 2004. For protocol variants added after that date, refer to the Cisco PGW 2200 Softswitch software Release Notes of the software version you are using for protocol variants added after that date.

Table A-63 Supported Protocol Variants for Software Release 9.3(2) 

Protocol Variant Name	Protocol Family	Switch Supported
ETS_300_102	ISDNPRI	27
ETS_300_102_C2	ISDNPRI	27
ATT_41459	ISDNPRI	17
ATT_41459_C2	ISDNPRI	17
BELL_1268	ISDNPRI	22
ETS_300_172	ISDNPRI	29
BELL_1268_C2	ISDNPRI	22
ETS_300_121	SS7-ITU	0
Q931_AUSTRALIA	ISDNPRI	19
Q931	ISDNPRI	27
Q931_SINGAPORE	ISDNPRI	27
GR317	SS7-ANSI	0
ANSISS7_92	SS7-ANSI	0
ANSISS7_STANDARD	SS7-ANSI	0
ANSISS7_C2	SS7-ANSI	20
ANSISS7_C3	SS7-ANSI	0
ANSISS7_E1	SS7-ANSI	23
ANSISS7_2K	SS7-ANSI	0
BTNUP_BTNR167	SS7-UK	5
BTNUP_IUP	SS7-UK	5
HONGKONG	SS7-ITU	0
ETS_300_356	SS7-ITU	0
ISUPV2_FRENCH	SS7-ITU	0
ISUPV2_AUSTRIAN	SS7-ITU	0
ISUPV2_SWISS	SS7-ITU	0
ISUPV2_SWISS_C2	SS7-ITU	0
ISUPV2_GERMAN	SS7-ITU	0
ISUPV2_FINNISH96	SS7-ITU	0
ISUPV1_POLI	SS7-ITU	0
ISUPV2_POLISH	SS7-ITU	0
ISUPV2_DUTCH	SS7-ITU	0
ISUPV2_JAPAN	SS7-Japan	10
ISUPV2_JAPAN_C2	SS7-Japan	0
ISUPV2_CZECH	SS7-ITU	0
ISUPV3	SS7-ITU	0
ISUPV3_UK	SS7-UK	0
ISUPV3_UK_C2 SS7-UK	SS7-UK	15
ISUPV3_UK_C3 SS7-UK	SS7-UK	0
ISUPV3_UK_C4	SS7-UK	15
ISUPV2_SPANISH_C2	SS7-ITU	0
ISUPV2_SPANISH	SS7-ITU	0
ISUPV2_32DIG	SS7-ITU	0
ISUPV2_VIETNAM	SS7-ITU	0
ISUPV2_NORWEGIAN	SS7-ITU	0
ISUPV2_ISRAEL	SS7-ITU	40
Q721_FRENCH	SS7-ITU	5
Q721_CHINA	SS7-China	5
Q721_BASE	SS7-ITU	5
Q721_PHILLIPINE	SS7-ITU	5
Q721_BRAZILIAN	SS7-ITU	5
Q761_97VER	SS7-ITU	0
Q761_CHINA	SS7-China	0
Q761_CHINA_C2	SS7-China	0
Q761_BELG_C2	SS7-ITU	0
Q761_BELG_C3	SS7-ITU	0
Q761_DANISH	SS7-ITU	0
Q761_INDIA	SS7-ITU	0
Q761_MALAYSIAN	SS7-ITU	0
Q761_JAPAN	SS7-Japan	10
Q761_KOREAN	SS7-ITU	0
Q761_TAIWAN	SS7-ITU	0
Q761_CHILE	SS7-ITU	0
Q761_SINGAPORE	SS7-ITU	0
Q761_SINGAPORE_C2	SS7-ITU	0
Q761_THAILAND	SS7-ITU	0
Q761_ARGENTINA	SS7-ITU	0
Q761_ARGENTINA_C2	SS7-ITU	0
Q761_BELG	SS7-ITU	0
Q761_AUSTRL	SS7-ITU	0
Q761_AUSTRL_C2	SS7-ITU	0
Q761_NEWZEALAND	SS7-ITU	0
Q761_BASE	SS7-ITU	0
Q761_PORTUGAL	SS7-ITU	0
Q761_GERMAN	SS7-ITU	0
Q761_PERU	SS7-ITU	0
Q767_BASE	SS7-ITU	0
Q767_SPAN	SS7-ITU	0
Q767_ITAL	SS7-ITU	0
Q767_RUSS	SS7-ITU	0
Q767_SWED	SS7-ITU	0
Q767_ITAL_C2	SS7-ITU	0
Q767_MEXICAN	SS7-ITU	0
Q767_AUSTRALIA	SS7-ITU	0
Q767_COLOMBIA	SS7-ITU	0
Q767_INDONESIA	SS7-ITU	0
Q767_BRAZIL	SS7-ITU	0
Q767_GUATEMALA	SS7-ITU	0
Q767_TURKISH	SS7-ITU	0
Q767_SINGAPORE	SS7-ITU	0
Q767_NIGERIAN	SS7-ITU	0
EISUP	EISUP	0
BELL_SGCP	MGCP	0
MGCPCAS	CAS	0
dummy	SGCP	0
dummy	MGCP	0
dummy	TCAPOverIP	0
dummy	VSI	0
dummy	AVM	0
IETF_SIP	SIP	0
IETF_DCS	SIP	0

Software Release 9.4(1) Protocol Variants

Table A-64 provides a snapshot of the protocol variants supported in the Cisco PGW 2200 Softswitch software Release 9.4(1) as of February 19, 2004. For protocol variants added after that date, refer to the Cisco PGW 2200 Softswitch software Release Notes of the software version you are using for protocol variants added after that date.

Table A-64 Supported Protocol Variants for Software Release 9.4(1) 

Protocol Variant Name	Protocol Family	Switch Supported
DPNSS_BTNR188	DPNSS	26
ETS_300_102	ISDNPRI	27
ETS_300_102_C2	ISDNPRI	27
ATT_41459	ISDNPRI	17
ATT_41459_C2	ISDNPRI	17
BELL_1268	ISDNPRI	22
ETS_300_172	ISDNPRI	29
BELL_1268_C2	ISDNPRI	22
ETS_300_121	SS7-ITU	0
Q931_AUSTRALIA	ISDNPRI	19
Q931	ISDNPRI	27
Q931_SINGAPORE	ISDNPRI	27
GR317	SS7-ANSI	0
ANSISS7_92	SS7-ANSI	0
ANSISS7_STANDARD	SS7-ANSI	0
ANSISS7_C2	SS7-ANSI	20
ANSISS7_C3	SS7-ANSI	0
ANSISS7_E1	SS7-ANSI	23
ANSISS7_2K	SS7-ANSI	0
BTNUP_BTNR167	SS7-UK	5
BTNUP_IUP	SS7-UK	5
HONGKONG	SS7-ITU	0
ETS_300_356	SS7-ITU	0
ISUPV2_FRENCH	SS7-ITU	0
ISUPV2_AUSTRIAN	SS7-ITU	0
ISUPV2_AUSTRIAN_C2	SS7-ITU	0
ISUPV2_SWISS	SS7-ITU	0
ISUPV2_SWISS_C2	SS7-ITU	0
ISUPV2_GERMAN	SS7-ITU	0
ISUPV2_FINNISH96	SS7-ITU	0
ISUPV1_POLI	SS7-ITU	0
ISUPV2_POLISH	SS7-ITU	0
ISUPV2_DUTCH	SS7-ITU	0
ISUPV2_JAPAN	SS7-Japan	10
ISUPV2_JAPAN_C2	SS7-Japan	0
ISUPV2_CZECH	SS7-ITU	0
ISUPV3	SS7-ITU	0
ISUPV3_UK	SS7-UK	0
ISUPV3_UK_C2	SS7-UK	15
ISUPV3_UK_C3	SS7-UK	0
ISUPV3_UK_C4	SS7-UK	15
ISUPV2_SPANISH_C2	SS7-ITU	0
ISUPV2_SPANISH	SS7-ITU	0
ISUPV2_32DIG	SS7-ITU	0
ISUPV2_VIETNAM	SS7-ITU	0
ISUPV2_NORWEGIAN	SS7-ITU	0
ISUPV2_ISRAEL	SS7-ITU	40
Q721_FRENCH	SS7-ITU	5
Q721_CHINA	SS7-China	5
Q721_BASE	SS7-ITU	5
Q721_PHILLIPINE	SS7-ITU	5
Q721_BRAZILIAN	SS7-ITU	5
Q761_CHINA	SS7-China	0
Q761_CHINA_C2	SS7-China	0
Q761_DANISH	SS7-ITU	0
Q761_INDIA	SS7-ITU	0
Q761_MALAYSIAN	SS7-ITU	0
Q761_JAPAN	SS7-Japan	10
Q761_KOREAN	SS7-ITU	0
Q761_TAIWAN	SS7-ITU	0
Q761_CHILE	SS7-ITU	0
Q761_SINGAPORE	SS7-ITU	0
Q761_SINGAPORE_C2	SS7-ITU	0
Q761_THAILAND	SS7-ITU	0
Q761_ARGENTINA	SS7-ITU	0
Q761_ARGENTINA_C2	SS7-ITU	0
Q761_BELG	SS7-ITU	0
Q761_BELG_97VER	SS7-ITU	0
Q761_AUSTRL	SS7-ITU	0
Q761_AUSTRL_C2	SS7-ITU	0
Q761_NEWZEALAND	SS7-ITU	0
Q761_BASE	SS7-ITU	0
Q761_PORTUGAL	SS7-ITU	0
Q761_GERMAN	SS7-ITU	0
Q761_PERU	SS7-ITU	0
Q767_BASE	SS7-ITU	0
Q767_SPAN	SS7-ITU	0
Q767_ITAL	SS7-ITU	0
Q767_RUSS	SS7-ITU	0
Q767_SWED	SS7-ITU	0
Q767_ITAL_C2	SS7-ITU	0
Q767_MEXICAN	SS7-ITU	0
Q767_AUSTRALIA	SS7-ITU	0
Q767_COLOMBIA	SS7-ITU	0
Q767_INDONESIA	SS7-ITU	0
Q767_BRAZIL	SS7-ITU	0
Q767_GUATEMALA	SS7-ITU	0
Q767_TURKISH	SS7-ITU	0
Q767_SINGAPORE	SS7-ITU	0
Q767_NIGERIAN	SS7-ITU	0
EISUP	EISUP	0
BELL_SGCP	MGCP	0
MGCPCAS	CAS	0
dummy	SGCP	0
dummy	MGCP	0
dummy	TCAPOverIP	0
dummy	VSI	0
dummy	AVM	0
IETF_SIP	SIP	0
IETF_DCS	SIP	0

Software Release 9.5(2) Protocol Variants

Table A-64 provides a snapshot of the protocol variants supported in the Cisco PGW 2200 Softswitch software Release 9.5(2) as of April 19, 2006. For protocol variants added after that date, refer to the Cisco PGW 2200 Softswitch software Release Notes of the software version you are using for protocol variants added after that date.

Table A-65 Supported Protocol Variants for Software Release 9.5(2) 

Protocol Variant Name	Protocol Family	Switch Supported
DPNSS_BTNR188	DPNSS	26
ETS_300_102	ISDNPRI	27
ETS_300_102_C2	ISDNPRI	27
ATT_41459	ISDNPRI	17
ATT_41459_C2	ISDNPRI	17
BELL_1268	ISDNPRI	22
ETS_300_172	ISDNPRI	29
BELL_1268_C2	ISDNPRI	22
ETS_300_121	SS7-ITU	0
Q931_AUSTRALIA	ISDNPRI	19
Q931	ISDNPRI	27
Q931_SINGAPORE	ISDNPRI	27
GR317	SS7-ANSI	0
ANSISS7_92	SS7-ANSI	0
ANSISS7_STANDARD	SS7-ANSI	0
ANSISS7_C2	SS7-ANSI	20
ANSISS7_C3	SS7-ANSI	0
ANSISS7_E1	SS7-ANSI	23
ANSISS7_2K	SS7-ANSI	0
BTNUP_BTNR167	SS7-UK	5
BTNUP_IUP	SS7-UK	5
HONGKONG	SS7-ITU	0
ETS_300_356	SS7-ITU	0
ISUPV2_FRENCH	SS7-ITU	0
ISUPV2_AUSTRIAN	SS7-ITU	0
ISUPV2_AUSTRIAN_C2	SS7-ITU	0
ISUPV2_SWISS	SS7-ITU	0
ISUPV2_SWISS_C2	SS7-ITU	0
ISUPV2_GERMAN	SS7-ITU	0
ISUPV2_FINNISH96	SS7-ITU	0
ISUPV1_POLI	SS7-ITU	0
ISUPV2_POLISH	SS7-ITU	0
ISUPV2_DUTCH	SS7-ITU	0
ISUPV2_JAPAN	SS7-Japan	10
ISUPV2_JAPAN_C2	SS7-Japan	0
ISUPV2_CZECH	SS7-ITU	0
ISUPV3	SS7-ITU	0
ISUPV3_UK	SS7-UK	0
ISUPV3_UK_C2	SS7-UK	15
ISUPV3_UK_C3	SS7-UK	0
ISUPV3_UK_C4	SS7-UK	15
ISUPV2_SPANISH_C2	SS7-ITU	0
ISUPV2_SPANISH	SS7-ITU	0
ISUPV2_VIETNAM	SS7-ITU	0
ISUPV2_NORWEGIAN	SS7-ITU	0
ISUPV2_ISRAEL	SS7-ITU	40
Q721_FRENCH	SS7-ITU	5
Q721_CHINA	SS7-China	5
Q721_BASE	SS7-ITU	5
Q721_PHILLIPINE	SS7-ITU	5
Q721_BRAZILIAN	SS7-ITU	5
Q721_BRAZILIAN_C2	SS7-ITU	5
Q761_97VER_BASE	SS7-ITU	0
Q761_99VER_BASE	SS7-ITU	0
Q761_CHINA	SS7-China	0
Q761_CHINA_C2	SS7-China	0
Q761_DANISH	SS7-ITU	0
Q761_INDIA	SS7-ITU	0
Q761_MALAYSIAN	SS7-ITU	0
Q761_KOREAN	SS7-ITU	0
Q761_TAIWAN	SS7-ITU	0
Q761_CHILE	SS7-ITU	0
Q761_SINGAPORE	SS7-ITU	0
Q761_SINGAPORE_C2	SS7-ITU	0
Q761_THAILAND	SS7-ITU	0
Q761_ARGENTINA	SS7-ITU	0
Q761_ARGENTINA_C2	SS7-ITU	0
Q761_BELG	SS7-ITU	0
Q761_BELG_97VER	SS7-ITU	0
Q761_AUSTRL	SS7-ITU	0
Q761_AUSTRL_C2	SS7-ITU	0
Q761_99VER_AUSTRL_C3	SS7-ITU	0
Q761_97VER_RUSS	SS7-ITU	0
Q761_NEWZEALAND	SS7-ITU	0
Q761_BASE	SS7-ITU	0
Q761_PORTUGAL	SS7-ITU	0
Q761_GERMAN	SS7-ITU	0
Q761_PERU	SS7-ITU	0
Q767_BASE	SS7-ITU	0
Q767_SPAN	SS7-ITU	0
Q767_ITAL	SS7-ITU	0
Q767_RUSS	SS7-ITU	0
Q767_RUSS_C2	SS7-ITU	0
Q767_SWED	SS7-ITU	0
Q767_ITAL_C2	SS7-ITU	0
Q767_MEXICAN	SS7-ITU	0
Q767_AUSTRALIA	SS7-ITU	0
Q767_COLOMBIA	SS7-ITU	0
Q767_INDONESIA	SS7-ITU	0
Q767_BRAZIL	SS7-ITU	0
Q767_BRAZIL_C2	SS7-ITU	0
Q767_GUATEMALA	SS7-ITU	0
Q767_TURKISH	SS7-ITU	0
Q767_SINGAPORE	SS7-ITU	0
Q767_NIGERIAN	SS7-ITU	0
EISUP	EISUP	0
dummy	SGCP	0
dummy	MGCP	0
dummy	TCAPOverIP	0
dummy	VSI	0
dummy	AVM	0
dummy	LI	0
IETF_SIP	SIP	0

Software Release 9.6(1) Protocol Variants

Table A-64 provides a snapshot of the protocol variants supported in the Cisco PGW 2200 Softswitch software Release 9.6(1) as of January 19, 2006. For protocol variants added after that date, refer to the Cisco PGW 2200 Softswitch software Release Notes of the software version you are using for protocol variants added after that date.

Table A-66 Supported Protocol Variants for Software Release 9.6(1) 

Protocol Variant Name	Protocol Family	Switch Supported
ANSISS7_2K	SS7-ANSI	0
BTNUP_BTNR167	SS7-UK	5
BTNUP_IUP	SS7-UK	5
HONGKONG	SS7-ITU	0
ETS_300_356	SS7-ITU	0
ISUPV2_FRENCH	SS7-ITU	0
ISUPV2_AUSTRIAN	SS7-ITU	0
ISUPV2_AUSTRIAN_C2	SS7-ITU	0
ISUPV2_SWISS	SS7-ITU	0
ISUPV2_SWISS_C2	SS7-ITU	0
ISUPV2_GERMAN	SS7-ITU	0
ISUPV2_FINNISH96	SS7-ITU	0
ISUPV1_POLI	SS7-ITU	0
ISUPV2_POLISH	SS7-ITU	0
ISUPV2_DUTCH	SS7-ITU	0
ISUPV2_JAPAN	SS7-Japan	10
ISUPV2_JAPAN_C2	SS7-Japan	0
ISUPV2_CZECH	SS7-ITU	0
ISUPV3	SS7-ITU	0
ISUPV3_UK	SS7-UK	0
ISUPV3_UK_C2	SS7-UK	15
ISUPV3_UK_C3	SS7-UK	0
ISUPV3_UK_C4	SS7-UK	15
ISUPV2_SPANISH_C2	SS7-ITU	0
ISUPV2_SPANISH	SS7-ITU	0
ISUPV2_VIETNAM	SS7-ITU	0
ISUPV2_NORWEGIAN	SS7-ITU	0
ISUPV2_ISRAEL	SS7-ITU	40
Q721_FRENCH	SS7-ITU	5
Q721_CHINA	SS7-China	5
Q721_BASE	SS7-ITU	5
Q721_PHILLIPINE	SS7-ITU	5
Q721_BRAZILIAN	SS7-ITU	5
Q721_BRAZILIAN_C2	SS7-ITU	5
Q761_97VER_BASE	SS7-ITU	0
Q761_99VER_BASE	SS7-ITU	0
Q761_CHINA	SS7-China	0
Q761_CHINA_C2	SS7-China	0
Q761_DANISH	SS7-ITU	0
Q761_INDIA	SS7-ITU	0
Q761_MALAYSIAN	SS7-ITU	0
Q761_KOREAN	SS7-ITU	0
Q761_TAIWAN	SS7-ITU	0
Q761_CHILE	SS7-ITU	0
Q761_SINGAPORE	SS7-ITU	0
Q761_SINGAPORE_C2	SS7-ITU	0
Q761_THAILAND	SS7-ITU	0
Q761_ARGENTINA	SS7-ITU	0
Q761_ARGENTINA_C2	SS7-ITU	0
Q761_BELG	SS7-ITU	0
Q761_BELG_97VER	SS7-ITU	0
Q761_AUSTRL	SS7-ITU	0
Q761_AUSTRL_C2	SS7-ITU	0
Q761_99VER_AUSTRL_C3	SS7-ITU	0
Q761_NEWZEALAND	SS7-ITU	0
Q761_BASE	SS7-ITU	0
Q761_PORTUGAL	SS7-ITU	0
Q761_GERMAN	SS7-ITU	0
Q761_PERU	SS7-ITU	0
Q767_BASE	SS7-ITU	0
Q767_SPAN	SS7-ITU	0
Q767_ITAL	SS7-ITU	0
Q767_RUSS	SS7-ITU	0
Q767_RUSS_C2	SS7-ITU	0
Q767_SWED	SS7-ITU	0
Q767_ITAL_C2	SS7-ITU	0
Q767_MEXICAN	SS7-ITU	0
Q767_AUSTRALIA	SS7-ITU	0
Q767_COLOMBIA	SS7-ITU	0
Q767_INDONESIA	SS7-ITU	0
Q767_BRAZIL	SS7-ITU	0
Q767_BRAZIL_C2	SS7-ITU	0
Q767_GUATEMALA	SS7-ITU	0
Q767_TURKISH	SS7-ITU	0
Q767_SINGAPORE	SS7-ITU	0
Q767_NIGERIAN	SS7-ITU	0
EISUP	EISUP	0
dummy	SGCP	0
dummy	MGCP	0
dummy	TCAPOverIP 0
dummy	VSI	0
dummy	AVM	0
dummy	LI	0
IETF_SIP	SIP	0
QBE	CTI-QBE	0