-- not used -- Cisco Media Gateway Controller Software Release 9 Provisioning Guide
Chapter 3 Provisioning with VSPT
Downloads: This chapterpdf (PDF - 7.07MB) The complete bookPDF (PDF - 9.74MB) | Feedback

Provisioning with the Cisco Voice Services Provisioning Tool

Table Of Contents

Provisioning with the Cisco Voice Services Provisioning Tool

Installing Cisco VSPT

Provisioning Cisco ITP-L

Manual Provisioning with Cisco VSPT

Configuring the MGC

Adding a Cisco PGW 2200 Softswitch Host

Configuring Signaling Services

Adding Point Codes

Adding Origination Point Codes

Adding Adjacent Point Codes

Adding Destination Point Codes

Adding Routing Keys

Adding M3UA Routing Keys

Adding SUA Routing Keys

Adding Location Labels

Adding Linksets

Adding and Changing Linkset Properties

Adding SS7 Subsystems

Adding SS7 Subsystems (Mating APCs)

Adding SS7 Subsystems (AIN Services)

Adding ISUP Timer Profiles

Adding an Inservice Subsystem

Configuring SS7 Paths

Adding and Changing SS7 Properties

Configuring SS7 Routes

Configuring IPRoutes

Configuring M3UA Routes

Configuring SUA Routes

Adding and Changing SS7 Signaling Properties

Adding a Line Number Translation

Adding Session Initiation Protocols

Configuring a DNS Parameter

Adding a SIP Signaling Path

Adding and Changing SIP Signaling Properties

Adding a SIP IP Link

Configuring Automatic Congestion Control

Configuring Advice of Charge

Configuring a Holiday

Configuring a Charge

Configuring a Tariff

Configuring a Meter Tariff

Configuring a Pritariff

Configuring a Pricharge

Adding GTD Parameters

Configuring TOS

Configuring Cisco MGW Control Links

Adding External Nodes

Configuring Cisco MGWs

Adding a Session Set

Adding and Changing Session Set Properties

Adding an IPFAS Signaling Service

Changing IPFAS Signaling Service Properties

Adding an MGCP Signaling Service

Adding and Changing MGCP Signaling Service Properties

Adding a DPNSS Path

Adding and Changing DPNSS Path Signaling Properties

Adding an H.248 Signaling Service

Adding and Changing H248 Signaling Properties

Adding an EISUP Signaling Service

Adding or Changing EISUP Signaling Properties

Adding an LIpath Signaling Service

Adding or Changing LI Signaling Properties

Adding a NAS Signaling Service

Adding and Changing NAS Signaling Properties

Adding a CTI Signaling Service

Adding and Changing CTI Signaling Properties

Adding an SS7 SGP

Adding a TCPLNK

Adding and Changing Tcplnk Properties

Adding a BRI Signaling Service

Adding a RAPATH

Adding a RASERVER for RAPATH

Configuring IP Links

Adding IP Links for MGCP

Adding IP Links for H248

Adding IP Links for EISUP

Adding IP Links for LI

Adding IP Links for NAS

Adding C7 IP Links

Adding an ASSOCIATION

Adding a CTI Manager

Adding an AXL Server

Configuring Bearer Traffic

Importing Trunk Groups and Trunks

Adding a Trunk Group Profile

Adding Trunk Groups

Trunk Group Properties

Adding Trunks

Deleting Trunks from a Trunk Group

Adding a CodecString

Adding a BearerCap

Adding an ATMProfile

Adding Routes

Adding Route Lists

Hierarchical View of Provisioned Components

Performing an Integrity Check

Checking Integrity for an MGC Signaling Configuration

Checking Traffic Against an MGC Configuration

Viewing Generated MML Commands

Deploying a New Configuration

Backup and Restore

Schedule a Backup or Restore

Check Status of Backup or Restore

Provisioning the Cisco Billing and Measurements Server

Starting a Cisco BAMS Provisioning Session

Cisco BAMS Server Configuration

Provisioning General BAMS Information

Provisioning Zones

Provisioning Trunk Group Information

Provisioning Measurements

Provisioning Other

Provisioning ALM-PARMS

Provisioning NODE-PARMS

Provisioning POLL

Provisioning SKIPCDB

Provisioning SKIPCDE

Provisioning P01FILTER

Provisioning SWITCHINFO

Provisioning BIN1110

Provisioning System

Provisioning MSC-PARMS

Provisioning MSC-THRES

Provisioning SYS-ALM-PARMS


Provisioning with the Cisco Voice Services Provisioning Tool


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

This chapter shows you how to use the Cisco Voice Services Provisioning Tool (VSPT), Release 2.7(3) to provision a Cisco PGW 2200 Softswitch and the Cisco Billing and Measurements Server (BAMS).

Depending on the Cisco VSPT software release you are using, the windows you see may not appear exactly as the window examples in this chapter.


Tip Before you begin provisioning, have a list of the components you want to provision, including component names, IP addresses, properties, and other parameters. These can be created using the worksheets provided in "Planning Worksheets." Descriptions of the properties and values contained in the Cisco VSPT are also included in Appendix B and in this chapter. Review this information before you begin provisioning and keep it available for reference.



NoteThe provisioning procedures described in this chapter follow the sequence for provisioning a typical Cisco PGW 2200 Softswitch configuration described in Chapter 1 "Provisioning Overview."

In this chapter, the Cisco PGW 2200 Softswitch is typically referred to by its legacy name, Cisco MGC. This name is used in most of the VSPT dialog screens.

Cisco IP Transfer Point - LinkExtender (ITP-L) is the new name for Cisco Signaling Link Terminal (SLT). Over time, Cisco ITP-L will replace Cisco SLT in publications and the product.


Installing Cisco VSPT

If you are a registered Cisco.com user, you can download the 2.6(1) and previous Cisco VSPT software from the Cisco website. For VSPT 2.7(3) and higher, VSPT is included with the licensed Cisco MGC Node Manager.

Refer to the Cisco Voice Services Provisioning Tool User's Guide for information on obtaining, installing, and operating the Cisco VSPT software.

Provisioning Cisco ITP-L

If your network contains a Cisco ITP-L, ensure that the following components are provisioned:

T1 or E1 line

IP address

IP route

Signaling System 7 (SS7) session address

ITU protocol variant

Manual Provisioning with Cisco VSPT

Provisioning a Cisco MGC is a complex process that can be logically divided into the following steps for all solutions:

Configuring the MGC

Configuring communications between the MGC and external SS7 signaling points (SPs), such as Signaling Transfer Points (STPs) or IP Transfer Points (ITPs)

Configuring call control links between the MGC, Cisco ITP-L, and the media gateways

Configuring bearer traffic

The provisioning procedures presented in this chapter follow the provisioning sequence for a typical MGC configuration.


Note The components in your solution might differ from those described in this chapter. For additional provisioning procedures, see the other chapters in this guide.


The following sections provide information on using the Cisco VSPT to provision a MGC:

Configuring the MGC

Configuring Signaling Services

Configuring Cisco MGW Control Links

Configuring Bearer Traffic


Note Provisioning or changing some properties requires a restart for the change to take effect. When you add or edit a property, Cisco VSPT notifies you if a restart is required. See Table 4-4 for a list of properties and restart information.


Configuring the MGC

To provision an MGC, configure the following basic network elements:

Active MGC host

Standby MGC host, if applicable


Note Before you begin provisioning the MGC using Cisco VSPT, be sure the MGC software is properly configured for your network. See the Cisco Media Gateway Controller Software Installation and Configuration (Release 9.7) at the following URL,
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/installation/software/SW1/97.html
or the Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6) at the following URL,
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/installation/software/SW2/pre97inst.html


Adding a Cisco PGW 2200 Softswitch Host

The MGC host is a Sun workstation that runs the MGC software. Table 3-1 lists the MGC host properties. Use this information to add an MGC host and a standby host if you are configuring a redundant MGC.

Table 3-1 MGC Properties 

Field Name
Description
Default
Valid Values

MGC Hostname

IP address or hostname that identifies the target MGC host

None

User defined

Login / Password

Specifies the valid MGC login and password

None

User defined

Protocol

Specifies the protocol to log into the MGC

SSH

SSH None (Telnet)

PGW Mode

The MGC switch mode

Depends on PGW

Switched Nailed

BAMS Version

Specifies the Cisco BAMS version for configuration

Bams V3

Bams V3

BAMS Config

Gives the name of the Cisco BAMS configuration

<UNSET>

xxxx

IP Addr:1

IP address of the MGC primary interface used for signaling and control

None

x.x.x.x

IP Addr:2

IP address of a secondary interface used for signaling or control backup

None

x.x.x.x

IP Addr:3

IP address of a third interface used for signaling or control backup

None

x.x.x.x

IP Addr:4

IP address of a fourth interface used for signaling or control backup

None

x.x.x.x

Failover

Indicates whether this is a failover configuration

None

No, Yes

Failover IP Addr:1

IP address of the primary interface for signaling on the standby MGC (if included)

None

x.x.x.x

Failover IP Addr:2

IP address of the secondary interface for signaling on the standby MGC (if included)

None

x.x.x.x

Failover IP Addr:3

IP address of the third interface for signaling on the standby MGC (if included)

None

x.x.x.x

Failover IP Addr:4

IP address of the fourth interface for signaling on the standby MGC (if included)

None

x.x.x.x


Perform the following steps to add an MGC host and a standby host, if applicable. Refer to Table 3-1 for property values.


Note If you are adding a MGC host in a fault-tolerant mode, set pom.datasync to false and SysConnectDataAccess to true in XECfgParm.dat file. By doing that, the standby MGC is not automatically synchronizing the provision from the active MGC.



Step 1 Enter your log in ID and password to log in VSPT.

Step 2 Choose File->New in the menu bar and enter the name for the new configuration.
A window similar to the one in Figure 3-1 displays.

Figure 3-1 New Configuration Wizard

Step 3 If you want to import the configuration from an existing MGC, select Import from MGC. If you want to do a manual configuration, select Perform manual configuration and after you click the OK button go to Step 6.

Step 4 Enter the hostname or IP address and the log in information for the existing MGC. Select the SSH or None radio button.

Step 5 Click the Select button and select the configuration from the existing MGC to import.
A window similar to the one in Figure 3-2 displays.

Figure 3-2 Configuration Chooser

Step 6 Make sure MGC Config radio button is selected.

Step 7 Click Unknown MGC in the left pane of the main VSPT window. A window similar to the one in Figure 3-3 displays.

Figure 3-3 Adding an MGC Host

Step 8 Enter the IP address or hostname of the MGC in the MGCHostname field (for example, 172.16.145.38).

Step 9 Enter a valid MGC login ID and password.

Step 10 Select the radio button to specify the protocol for connecting to the MGC.

Step 11 Select the radio button that corresponds to the PGW Mode you want to provision.

Step 12 Enter the network addresses (IP Addr: 1 and IP Addr: 2) in dotted notation (for example, 172.16.145.3), or click Import Settings to import the network addresses.

Step 13 Indicate whether the MGC has a failover MGC, and if it does, enter the network addresses (Failover IP Addr: 1 and Failover IP Addr: 2).

Step 14 Click Modify. The hierarchical tree display changes from "Unknown MGC" to the MGC host name you entered in Step 8 (see Figure 3-4), and "Modification complete" displays briefly on the bottom left portion of the window.


Figure 3-4 MGC Host Added

Configuring Signaling Services

Signaling services identify all signaling types processed by the MGC. To configure signaling services, use the steps provided in the sections below.

Adding Point Codes

Adding Routing Keys

Adding Location Labels

Adding Linksets

Adding SS7 Subsystems

Adding ISUP Timer Profiles

Adding an Inservice Subsystem

Configuring SS7 Paths

Configuring SS7 Routes

Configuring IPRoutes

Configuring M3UA Routes

Configuring SUA Routes

Adding and Changing SS7 Signaling Properties

Adding a Line Number Translation

Adding Session Initiation Protocols

Configuring Automatic Congestion Control

Configuring Advice of Charge

Adding GTD Parameters

Configuring TOS

Adding Point Codes

Every signaling point in the SS7 network is identified by a unique point code. To provision point codes, use the steps provided in the subsections below.

Adding Origination Point Codes

Adding Adjacent Point Codes

Adding Destination Point Codes


Note Point codes provide the addressing scheme for the SS7 network. ITU point codes contain 14 bits, and ANSI point codes contain 24 bits.


Adding Origination Point Codes

An origination point code (OPC) is an SS7 network address assigned to the MGC. You can define up to six OPCs. To provision an OPC, use the following steps:


Step 1 Click the icon next to Signaling to expand the hierarchical tree.

Step 2 Click Point Codes > OPCs. A window similar to the one shown in Figure 3-5 displays.

Figure 3-5 Adding Origination Point Codes

.

Step 3 Enter a name.

Step 4 Enter the description.

Step 5 Enter the network address.

Step 6 In the NetIndicator drop-down menu, select one of the following values:

International network—Used if the node is an international gateway.

Reserved for international use—Do not use.

National network—Used if the node routes calls through the national network.

Reserved for national use—Do not use.

Step 7 Select the OPC type. Choices are TRUEOPC and CAPOPC.
TRUEOPC defines this OPC as a primary (true) OPC within this PGW. CAPOPC defines this OPC as an point code which have primary (true) OPCs associated to.

Step 8 Select the name of the previously defined true OPC. This parameter applies only to the capability OPC.

Step 9 Click Add. The hierarchical tree changes to reflect the origination point code added.



Note In a redundant configuration, the MGCs share the same OPC but have different IP addresses.


Adding Adjacent Point Codes

Adjacent point codes (APCs) are the SS7 network addresses of the Signal Transfer Points (STPs) (or Service Switching Points[SSPs] directly connected to the Cisco ITP-L) that connect to the MGC node. The MGC node communicates with external SSPs and Service Control Points (SCPs) through an STP.

Table 3-2 lists the APC properties. Use the values in the table as you add APCs to the MGC.

Table 3-2 APC Properties 

Property
MML Parameter Name
Description
Default
Valid Values

Name

name

Identifies the adjacent point code MML name.

STP-x

Up to 20 alphanumeric characters

Description

desc

Describes the point code. Use up to 128 alphanumeric characters.

Adjacent Point Code

Up to 128 alphanumeric characters

NetAddr

netaddr

Enter the point code in this field. Valid for both ITU and North American point codes.

0.0.0

User defined

NetIndicator

netind

Identifies the type of node receiving the point code.

National

International
National
Reserved for international use
Reserved for national use


Use the following procedure to add the APCs for STPs. Refer to Table 3-2 for property values.


Step 1 Click the icon next to Signaling to expand the hierarchical tree.

Step 2 Click Point Codes > APCs. A window similar to the one shown in Figure 3-6 displays.

Figure 3-6 Adding Adjacent Point Codes

Step 3 Enter the name (for example, STP-1).

Step 4 Enter the description (for example, Adjacent Point Code).

Step 5 Enter the network address in dotted notation (for example, 2.1.2).

Step 6 In the NetIndicator drop-down menu, select one of the following values:

International network—Used if the node is an international gateway.

Reserved for international use—Do not use.

National network—Used if the node routes call through the national network.

Reserved for national use—Do not use.

Step 7 Click Add. The hierarchical tree changes to reflect the APC added (STP-1).


Adding Destination Point Codes

A destination point code (DPC) is an SS7 network address that identifies an SS7 network node, such as an STP, SSP, or media gateway with which the MGC node communicates.

Use the following procedure to add the DPCs for the ILEC and CLEC switches:


Step 1 Click the icon next to Signaling to expand the hierarchical tree.

Step 2 Click Point Codes > DPCs. A window similar to the one shown in Figure 3-7 displays.

Figure 3-7 Adding Destination Point Codes

Step 3 Enter a name.

Step 4 Enter the description.

Step 5 Enter the network address in dotted notation (for example, 1.1.2).

Step 6 Select the network numbering scheme type used:

ANSI

ETSI

Step 7 In the NetIndicator drop-down menu, select one of the following network indicators:

International network—Used if the node is an international gateway (default value).

Reserved for international use—Do not use.

National network—Used if the node routes calls through the national network.

Reserved for national use—Do not use.

Step 8 Click Add. The hierarchical tree changes to reflect the DPC added.


Adding Routing Keys

To provision routing keys, use the steps provided in the subsections below.

Adding M3UA Routing Keys

Adding SUA Routing Keys

Adding M3UA Routing Keys

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

Table 3-3 provides the structure of the M3UA key component.

Table 3-3 M3UA Key Component Structure

Parameter MML Name
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

Up to 128 characters.

OPC

Associated OPC

MML name of a previously configured OPC.

DPC

Associated DPC (optional)

MML name of a previously configured DPC.

ROUTING CONTEXT

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


The following rules apply when you are creating M3UA keys:

You can provision a maximum of 1536 M3UA keys.

Up to 64 OPCs can use M3UA signaling services.

Parent OPC must be a true OPC.

OPC and DPC cannot be deleted if it is being used by an SS7 signaling service.

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

To provision an M3UA routing key, use the following steps:


Step 1 Click the icon next to Signaling to expand the hierarchical tree.

Step 2 Click Routing Keys > M3UAs. A window similar to the one shown in Figure 3-8 displays.

Figure 3-8 Adding M3UA Routing Keys

Step 3 Enter a name.

Step 4 Enter the description.

Step 5 In the Orig. Point Code drop-down menu, select TRUEOPC.

Step 6 In the Dest. Point Code drop-down menu, select the DPC. This parameter is optional.

Step 7 Enter the Routing Context (for example, 0-2147483647).

Step 8 Select the Service Indicator. Choices are ISUP, N/A, and TUP.

Step 9 Enter the Network Appearance (for example, 0-32767).

Step 10 Click Add. The hierarchical tree changes to reflect the M3UA routing keys added.


Adding SUA Routing Keys

To provision an OPC, use the following steps:


Step 1 Click the icon next to Signaling to expand the hierarchical tree.

Step 2 Click Routing Keys > SUAs. A window similar to the one shown in Figure 3-9 displays.

Figure 3-9 Adding SUA Routing Keys

Step 3 Enter a name.

Step 4 Enter the description.

Step 5 In the Orig. Point Code drop-down menu, select TRUEOPC.

Step 6 In the Adj. Point Code drop-down menu, select the APC. This parameter is optional.

Step 7 Enter the Local Simple Security Network (SSN); for example, 2-254.

Step 8 Enter the Routing Context. To use the routing context, its value must be set to any integer other than 0 (0 indicates that there is no routing context). The routing context value for each routing key you create must be unique (for example, 0-2147483647).

Step 9 Enter the Network Appearance. This value must match the network appearance value set in your Cisco ITP (for example, 0-32767).

Step 10 Click Add. The hierarchical tree changes to reflect the SUA routing keys added.


Adding Location Labels

The location label concept is used in the Call Limiting feature. It is associated with one or more sources and destinations, so calls can be limited to or from one or more interfaces. As many as four location labels can be applied to a call, with two location labels on the inbound call leg and two location labels on the outbound call leg. The location label has a call threshold limit that can be set. If the call threshold for a location is exceeded, all other calls to or from that location are rejected.

To provision a Location Label, use the following steps:


Step 1 Click the icon next to Signaling to expand the hierarchical tree.

Step 2 Click Location Label. A window similar to the one shown in Figure 3-10 displays.

Figure 3-10 Adding Location Labels

Step 3 Enter a name.

Step 4 Enter the description.

Step 5 Enter the Call Limiting value (for example, 0-2147483647 or 9999999, which allows all calls).

Step 6 Click Add. The hierarchical tree changes to reflect the location labels added.


Adding Linksets

A linkset  is a logical group of links that transport SS7 signals to the MGC. Linksets can consist of the following:

Links from the MGC (OPC) to an adjacent STP (APC)

Links from the MGC (OPC) to a destination (a DPC acting as an APC if there is no STP)

Table 3-4 lists linkset properties. Use the values in this table as you add linksets to your MGC.

Table 3-4 Linkset Properties 

Property
MML Parameter
Description
Default
Valid Values

Name

name

Identifies the linkset MML name

Lnkset-x

Up to 20 alphanumeric characters

Description

desc

Describes the linkset

Lnkset

Up to 128 alphanumeric characters

Point Code

apc

Identifies the APC components for the SS7 node providing the linkset

<UNSET>

User defined

Protocol

proto

Identifies the protocol family associated with this linkset

SS7-ANSI

SS7-ANSI
SS7-China
SS7-ITU
SS7-Japan
SS7-UK

Type

type

Link Set Type

IP

IP
TDM


Use the following procedure to add the linksets between the MGC node and the STPs. Refer to Table 3-4 for property values.


Step 1 Click LinkSets in the left pane of the main VSPT window. A window similar to the one shown in Figure 3-11 displays.

Figure 3-11 Adding Linksets

Step 2 Enter a name (for example, Linkset-1).

Step 3 Enter the description (for example, Linkset).

Step 4 In the Point Code drop-down menu, select the desired APC or DPC component for this linkset (for example, STP-1).

Step 5 In the Protocol drop-down menu, select one of the following protocols:

SS7-ANSI

SS7-China

SS7-ITU

SS7-Japan

SS7-UK

Step 6 Select the Type. Choices are IP and TDM.

Step 7 Click Add. The hierarchical tree changes to reflect the linkset added.


Note After creating the linksets, you must create the links in each linkset by adding C7 IP Links. See the "Adding C7 IP Links" section.



Adding and Changing Linkset Properties

You can add and change the properties of a linkset after it is created, including message and timer values. Changes apply to all linksets you create. You do not have to change the default properties.

Perform the following steps to add or change linkset properties:


Step 1 Highlight the appropriate linkset in the left pane of the main Cisco VSPT window.

Step 2 Click Properties to display the list of properties. A window similar to the one shown in Figure 3-11 displays.

Figure 3-12 Adding and Changing Linkset Properties

Step 3 In the Value drop-down menu, select a property and enter a value.

Step 4 Click Add. A window similar to the one shown in Figure 3-13 displays with the property added. After a property has been added, it can be modified.

Figure 3-13 Linkset Property Added

Step 5 To modify an existing property, click the property you want to change.

Step 6 In the value field, enter the new property value.

Step 7 Click Modify.

Step 8 Click OK when you are finished modifying properties.



Note You cannot modify properties until you have created the linkset.


Adding SS7 Subsystems

An SS7 subsystem allows the MGC to route traffic over the C-links between mated STPs to increase network reliability. The links to these STPs are defined in the "Adding Routing Keys" section.

The SS7 subsystem provides local number portability (LNP) support through an SCP. Because the SS7 subsystem is an instance of an application, you need to configure a subsystem for each application type of service (for example, LNP). The SS7 subsystem is also used to connect an STP to an SCP database for advanced intelligent network (AIN) queries. In this case, there is no mated STP.

Table 3-5 lists SS7 subsystem properties. Use the values in the table as you add SS7 subsystems to your MGC.

Table 3-5 SS7 Subsystem Properties 

Property
MML Parameter
Description
Default
Valid Values

Name

name

Identifies the MML name for this SS7 subsystem.

Ss7ss-1

Up to 20 alphanumeric characters

Description

desc

Describes the subsystem.

SS7 Subsystem

Up to 128 alphanumeric characters

Subsystem Type

 

Identifies the type of subsystem.

None

Mating APCs
AIN Services

TCAPIP or APC

svc

Identifies the STP (or STP pair) to be used for TCAP messages.

<UNSET>

User defined

Priority

pri

Identifies the priority value of the route. Used for load sharing.

1

1 through 16

Subsystem number

ssn

Identifies the desired SCP services. The value is provider specific.

0

x.x.x.x

STP/SCP Index

stpscpind

Identifies each SCP in a virtual switch configuration.

0

0 through 99

Transport Protocol

transproto

Identifies the transport protocol used for TCAP messages. Accessing SCPs with SS7 uses the SCCP protocol.

TCP/IP

SCCP

TCP/IP

Protocol Family

proto

Identifies the protocol family used for SS7 messages.

<UNSET>

SS7-ANSI
SS7-China
SS7-ITU
SS7-Japan
SS7-UK


To provision SS7 subsystems, use the steps provided in the subsections below.

Adding SS7 Subsystems (Mating APCs)

Adding SS7 Subsystems (AIN Services)

Adding SS7 Subsystems (Mating APCs)

To provision SS7 Subsystems (Mating APCs), use the following steps:


Step 1 Click SS7 Subsystems in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-14 displays.

Figure 3-14 Adding SS7 Subsystems (Mating APCs)

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 Select Mating APCs as the Subsystem type.

Step 5 In the OPC drop-down menu, select the OPC.

Step 6 In the APC drop-down menu, select the APC used for queries.

Step 7 In the Mated APC drop-down menu, select the APC of the second STP.

Step 8 In the Protocol Family drop-down menu, select a protocol family to use.

Step 9 Click Add. The hierarchical tree changes to reflect the SS7 Subsystems added.


Adding SS7 Subsystems (AIN Services)

To provision an SS7 Subsystem (AIN Services), use the following steps:


Step 1 Click SS7 Subsystems in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-15 displays.

Figure 3-15 Adding SS7 Subsystems (AIN Services)

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 Select AIN Services as the Subsystem type.

Step 5 In the TCAPIP or APC drop-down menu, select the APC.

Step 6 Enter the Priority.

Step 7 Enter the Local SSN.

Step 8 Enter the STP/SCP index.

Step 9 In the Transport Protocol drop-down menu, select SCCP or SUA.

Step 10 In the Protocol Family drop-down menu, select a protocol family to use.

Step 11 In the OPC drop-down menu, select the OPC.

Step 12 In the SuaKey drop-down menu, select the Suakey.

Step 13 Enter the Remote SSN.

Step 14 Click Add. The hierarchical tree changes to reflect the SS7 Subsystems added.


Note If you have multiple linksets to an STP that use different protocol families, you must also have multiple SS7 subsystems; one for each linkset that uses a specific protocol.



Adding ISUP Timer Profiles

To provision an ISUP Timer Profile, use the following steps:


Step 1 Click the icon next to Signaling to expand the hierarchical tree.

Step 2 Click ISUP Timer Profile in the left pane of the main VSPT window.

Step 3 Click Add. A window similar to the one shown in Figure 3-16 displays.

Figure 3-16 Adding ISUP Timer Profiles

Step 4 Enter a name.

Step 5 In the Variant drop-down menu, select the variant.

Step 6 In the Validation drop-down menu, select ON or OFF.

Step 7 Click OK. The ISUP timer profile window changes to reflect the ISUP timer profile added.

Step 8 Select the appropriate ISUP timer profile in the ISUP timer profile.

Step 9 In the Name drop-down menu, select the timer name.

Step 10 Enter the Value.

Step 11 Click Add. The ISUP timer profile properties window changes to reflect the properties added.


Adding an Inservice Subsystem

The structure of the Inservice component is shown in Table 3-6.

Table 3-6 Intelligent Network Service (INSERVICE)

Parameter MML Name
Parameter Description
Parameter Values (Default)

NAME

Intelligent Network Service name

As many as 20 alphanumeric characters.

SKORTCV

Service key

Integer. 0 through 214783647 (0). Service key value that specifies the feature that caused the trigger to be hit (ITU/ETSI INAP only). Otherwise, it is the trigger criteria value.

GTORSSN

Global title or subsystem number

Text string. Route by global title (ROUTEBYGT) or route by subsystem number (ROUTEBYSSN).

0 = ROUTEBYGT (route by global title)

1 = ROUTEBYSSN (subsystem number)

GTFORMAT

Global title format

Text string. How to use Global Title; SCCP Called Party Address, Address indicator field. User provisions the string value. For example, NOGT.

0 = NOGT (No global title. Use this when routing by SSN.)

1 = GTTTNBRENC (Use global title translation type numbering scheme encoding scheme.)

2 = GTTT (Use global title translation type.)

3 = GTONLY (Use global title only.)

4 = UNKNOWN (unknown).

MSNAME

Message Sending Name

As many as 20 alphanumeric characters.


The following rules are used to support Inservice table provisioning:

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

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

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

To add an Inservice subsystem, use the following steps:


Step 1 Click the icon next to Signaling to expand the hierarchical tree.

Step 2 Click Inservice in the left pane of the main VSPT window. A window similar to the one shown in Figure 3-17 displays.

Figure 3-17 Adding an Inservice Subsystem

Step 3 Enter a name.

Step 4 Enter the Service Key.

Step 5 In the Global Title drop-down menu, select one of the following global titles:

ROUTEBYGT

ROUTEBYSSN

Step 6 In the Global Title Format drop-down menu, select one of the following global title formats:

GTONLY

GTTNBRENC

GTTT

NOGT

UNKNOWN

Step 7 Enter the Message Sending Name.

Step 8 Click Add. The hierarchical tree changes to reflect the Inservice added.


Configuring SS7 Paths

An SS7 signaling service identifies the path over which the MGC node communicates using a specific protocol with a remote MGC or switch. The (Man-Machine Language) MML component name is SS7PATH. Table 3-7 lists the SS7 signaling service properties. Use the values in this table as you add SS7 paths to your MGC.

Table 3-7 SS7 Signaling Service Properties 

Property
MML Parameter
Description
Default
Valid Values

Name

name

Identifies the SS7 service path.

None

Up to 20 alphanumeric characters

Description

desc

Describes the SS7 service path.

None

Up to 128 alphanumeric characters

Orig. Point Code

opc

Specifies the orig point code of the SSP in the service path.

<UNSET>

User defined

Dest. Point Code

dpc

Specifies the dest point code of the SSP in the service path.

<UNSET>

User defined

M3UAKey m3uakey

m3uakey

M3UA Key

None

See the drop-down list Figure 3-18.

Side

side

Distinguishes the network equipment (like a switch) from the user equipment (like a terminal adapter or PBX). (Used for ISDN systems.)

network

network
user

MDO

mdo

Identifies the protocol (MDO file name) for this SS7 service path. Select the MDO file name from a drop-down list.

ANSISS7_STANDARD

See the drop-down list

Customer Group ID

custgrpid

Contains a unique identifier for the number analysis file. (Used with nailed solutions only.)

0000

000-9999; can be up to 4-digit alphanumeric characters.

ISUP Timer Profile

sigpathProf->isuptmrprofile

ISUP Timer Profile Name

None

See the drop-down list Figure 3-18.

Origination Label

origlabel

Origination Location Label

None

See the drop-down list Figure 3-18.

'Termination Label

termlabel

Termination Location Label

None

See the drop-down list Figure 3-18.


Use the following procedure to add SS7 signaling service paths to the switch (identified by the DPC). If you have a signaling service that extends from the MGC to a PSTN switch, use the SS7 path component to add the service to your configuration. Refer to Table 3-7 for property values.


Step 1 Click SS7 Paths in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-18 displays.

Figure 3-18 Adding SS7 Paths

Step 2 Enter the name of the SS7 signaling path.

Step 3 Enter the description of the SS7 signaling path.

Step 4 In the Orig. Point Code drop-down menu, select the originating point code (the point code of the MGC) for this signaling service.

Step 5 In the Dest. Point Code drop-down menu, select the destination point code (the point code of the PSTN switch) for this signaling service.

Step 6 In the M3UAKey drop-down menu, select the M3UA routing key for this route.

Step 7 In the Side drop-down menu, select the side (Q.931 call model side):

Network

User

Step 8 In the MDO drop-down menu, select the protocol for this signaling service; for example, ANSISS7_STANDARD.

Step 9 Enter the customer group ID.

Step 10 In the ISUP Timer Profile drop-down menu, select the ISUP Timer Profile for this signaling service.

Step 11 In the Origination Label drop-down menu, select the Origination Location Label for this service.

Step 12 In the Termination Label drop-down menu, select the Termination Location Label for this service.

Step 13 Click Add. The hierarchical tree changes to reflect the SS7 path added.


Adding and Changing SS7 Properties

You can add and change the properties of a SS7 path after it is created. Changes apply to all SS7 paths you create. You do not have to change the default properties.

Perform the following steps to add or change SS7 properties:


Step 1 Select the appropriate SS7 path in the left pane of the main Cisco VSPT window.

Step 2 Click Properties to display the list of properties. A window similar to the one shown in Figure 3-19 displays.

Figure 3-19 Adding and Changing SS7 Properties

Step 3 To add a property, select it from the Name drop-down menu.

Step 4 Enter a value.

Step 5 Click Add. A window similar to the one shown inFigure 3-20 displays with the property added. After a property has been added, it can be modified.

Figure 3-20 Property Added

Step 6 To modify an existing property, click the property you want to change.

Step 7 In the value field, enter the new property value.

Step 8 Click Modify.

Step 9 Click OK when you are finished modifying properties.


Note You cannot modify properties until you have created the SS7 path.



Configuring SS7 Routes

An SS7 route is a path through a linkset between the MGC node and another MGC node or a switch. In Figure 3-21, the SS7 routes indicate the linksets that carry SS7 signals between the MGC node and the ILEC Class 5 switch or the CLEC Class 5 switch. You must define a separate route for each remote switch.

Table 3-8 lists the SS7 route properties. Use the values in this table as you add SS7 routes to your MGC.

Table 3-8 SS7 Route Properties 

Property
MML Parameter
Description
Default
Valid Values

Name

name

Identifies the MML name for a route set.

Ss7r-1

Up to 20 alphanumeric characters

Description

desc

Description of the route.

SS7 Route

Up to 128 alphanumeric characters

Originating PC

opc

Selects the MML name of the MGC point code.

<UNSET>

User defined

Destination PC

dpc

Selects the point code of the destination switch delivering bearer traffic to the solution.

<UNSET>

User defined

Linkset

lnkset

Selects the linkset over which the SS7 signals travel.

<UNSET>

User defined

Priority

pri

Sets the priority value of the route. You can create load sharing by setting all routes to the same number.

1

1 through 4


You must add an SS7 route for each signaling path from the MGC to the PSTN switch through the linksets you created to the STPs.

You should create two routes to the PSTN switch, with each route passing through a different STP of a mated pair.

Use the following procedure to add SS7 routes to the MGC. Refer to Table 3-8 for property values.


Step 1 Click SS7 Routes in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-21 displays.

Figure 3-21 Adding SS7 Routes

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the Originating PC drop-down menu, select the origination point code for this route.

Step 5 In the Destination PC drop-down menu, select the signal destination point code of the PSTN switch.

Step 6 In the Linkset drop-down menu, select the linkset for this route.

Step 7 Enter the priority.


Note Routes can share signaling traffic. You can set load sharing by assigning the same priority to each route.


Step 8 Click Add. The hierarchical tree changes to reflect the SS7 route added.


Configuring IPRoutes

The IP route component is used to set the means for getting a message to a particular destination using IP.

Use the following procedure to add an IPRoute:


Step 1 Click IPRoute in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-22 displays.

Figure 3-22 Adding IPRoutes

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the IP Addr drop-down menu, select the IP address of the MGC:

IP Addr1

IP Addr2

IP Addr3

IP Addr4

Step 5 Enter the Destination Addr.

Step 6 Enter the IP Gateway.

Step 7 Enter the IP Net Mask.

Step 8 In the Priority drop-down menu, select a priority. Value range: 1 through 16. 1 is the highest priority.

Step 9 Click Add. The hierarchical tree changes to reflect the SS7 route added.


Configuring M3UA Routes

The M3UA routes component is used to set the means for getting an SS7 message to a particular destination.

The M3UA route component structure is shown in Table 3-9.

Table 3-9 M3UAROUTE Component Structure

Parameter MML Name
Parameter Description
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

Up to 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.


The following rules apply when you are creating and editing M3UA routes:

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

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

The associated OPC must be a true OPC.

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

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

The associated external node must support M3UA signaling.

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

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

Use the following procedure to add M3UA routes to the MGC:


Step 1 Click M3UA Routes in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-23 displays.

Figure 3-23 Adding M3UA Routes

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the Originating PC drop-down menu, select the origination point code for this route.

Step 5 In the Adjacent PC drop-down menu, select the signal destination point code of the PSTN switch.

Step 6 In the External Node drop-down menu, select the provisioned Cisco ITP external node for this route.

Step 7 Enter the Priority.

Step 8 Click Add. The hierarchical tree changes to reflect the M3UA route added.


Configuring SUA Routes

Use the following procedure to add SUA routes to the MGC:


Step 1 Click SUA Routes in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-24 displays.

Figure 3-24 Adding SUA Routes

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the Originating PC drop-down menu, select the origination point code for this route.

Step 5 In the Adjacent PC drop-down menu, select the signal adjacent point code of the PSTN switch.

Step 6 In the External Node drop-down menu, select the provisioned Cisco ITP external node for this route.

Step 7 Enter the Remote SSN.

Step 8 Click Add. The hierarchical tree changes to reflect the SUA route added.


Adding and Changing SS7 Signaling Properties

You can add and change the properties of a sigpath after it is created. Changes apply to all sigpaths created. You do not have to change the default properties.

Perform the following steps to add or change sigpath properties:


Step 1 Highlight the appropriate sigpath in the left pane of the main Cisco VSPT window.

Step 2 Click Properties to display the list of properties. A window similar to the one shown in Figure 3-25 displays.

Figure 3-25 Adding and Changing Sigpath Properties

Step 3 To add a property, select a property and enter a value.

Step 4 Click Add. A window similar to the one shown in Figure 3-26 displays with the property added. After a property has been added, it can be modified.

Figure 3-26 Sigpath Property Added

Step 5 To modify an existing property, select the property you want to change.

Step 6 In the value field, enter the new property value.

Step 7 Click Modify.

Step 8 Click OK when you are finished modifying properties.


Note You cannot modify properties until you have created the sigpath.



Adding a Line Number Translation

Line number translation represents a line number and an internal number translation and is dynamically reconfigurable.

To provision Line Number Translation, use the following steps:


Step 1 Click the icon next to Signaling to expand the hierarchical tree.

Step 2 Click Line Number Translation in the left pane of the main VSPT window. A window similar to the one shown in Figure 3-27 displays.

Figure 3-27 Adding a Line Number Translation

Step 3 Enter a name.

Step 4 Enter the description.

Step 5 In the SVC drop-down menu, select the configured SS7 Paths.

Step 6 In the Direction drop-down menu, select in or out.

Step 7 In the Number drop-down menu, select one of the following numbers:

Called

Calling

Generic

Original called

Redirecting

Redirection

Step 8 Enter the intNoa (for example, 0-127).

Step 9 Enter the extNoa (for example, 0-127).

Step 10 Click Add. The hierarchical tree changes to reflect the Line Number Translation added.


Adding Session Initiation Protocols

The Session Initiation Protocol (SIP) signaling service is the connection between an MGC and a SIP server. To pass calls between the MGC and a SIP domain, you must configure an SIP signaling service. Table 3-10 lists the SIP properties.

Table 3-10 SIP Properties 

Field Name
Description
Default
Valid Values

Name

Unique ID of this component.

 

Up to 20 alphanumeric characters; the name should begin with an alphabetic character. "-" is the only special character permitted.

Description

Description of the external node.

None

Up to 128 alphanumeric characters.

MDO

Identifies protocol (MDO file name) for this SIP signal path. Select the MDO file name from the drop-down menu.

UNSET

UNSET
IETF_DCS
IETF_SIP


To provision SIP, use the steps provided in the subsections below.

Configuring a DNS Parameter

Adding a SIP Signaling Path

Configuring a DNS Parameter

Use the following procedure to configure the DNS parameter:


Step 1 In the left pane of the main Cisco VSPT window, click SIP > DNS. A window similar to the one shown in Figure 3-28 displays.

Figure 3-28 Configuring a DNS Parameter

Step 2 Enter the DNS 1 IP Addr. IP address of the primary DNS server.

Step 3 Enter the DNS 2 IP Addr. IP address of the secondary DNS server.

Step 4 Enter the Cache size, which is the maximum number of cache entries used to hold the DNS cache (for example, 1-999).

Step 5 Enter the TTL, which is the time-to-live interval for DNS entries, expressed in seconds (for example, 0-10800).

Step 6 In the Policy drop-down menu, click HIERARCHY or ROUND-ROBIN to indicate the policy type used for selecting DNS entries.

Step 7 Enter the Query Timeout, which is the timeout interval for DNS queries, expressed in milliseconds (for example, 100-30000).

Step 8 Enter the Keepalive, which is the time interval to determine whether the DNS server is responding, expressed in seconds (for example, 1-30).

Step 9 Click Add. The hierarchical tree changes to reflect the DNS added.


Adding a SIP Signaling Path

Use the following procedure to add a SIP Signaling Path:


Step 1 Click SIP in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-29 displays.

Figure 3-29 Adding a SIP Signaling Path

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the MDO drop-down menu, select the protocol for this signaling service (for example, IETF_SIP).

Step 5 In the Originating Label drop-down menu, select the location label.

Step 6 In the Termination Label drop-down menu, select the location label.

Step 7 Click Add. The hierarchical tree changes to reflect the new SIP signaling path added.


Note To add and change SIP signaling properties after it is created, see the "Adding and Changing SIP Signaling Properties" section



Adding and Changing SIP Signaling Properties

You can add and change the SIP signaling properties after a SIP signaling path is created. Changes apply to all linksets created. You do not have to change the default properties.

Perform the following steps to add or change SIP signaling properties:


Step 1 Select the appropriate SIP signaling path in the left pane of the main Cisco VSPT window.

Step 2 Click Properties to display the list of properties. A window similar to the one shown in Figure 3-30 displays.

Figure 3-30 Adding and Changing SIP Signaling Properties

Step 3 To add a property, select a property and enter a value.

Step 4 Click Add. A window similar to the one shown in Figure 3-31 displays with the property added. A property can be modified after it is added.

Figure 3-31 SIP Signaling Property Added

Step 5 To modify an existing property, click the property you want to change.

Step 6 In the value field, enter the new property value.

Step 7 Click Modify.

Step 8 Click OK when you are finished modifying properties.



NoteProperties cannot be modified until you have created the SIP signaling path.

To add a SIP IP link for the SIP signaling path, see the "Adding a SIP IP Link" section.


Adding a SIP IP Link

Use the following procedure to add a SIP IP link for the SIP signaling path:


Step 1 Click SIP > SIP path > Links in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-32 displays.

Figure 3-32 Adding a SIP IP Link

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the IP Addr drop-down menu, select the IP address of the MGC:

IP Addr1

IP Addr2

IP Addr3

IP Addr4

Virtual IP Addr1

Virtual IP Addr2

Step 5 Enter the port (for example, 1025-65535).

Step 6 In the Priority drop-down menu, select a priority. Value range: 1 through 16. 1 is the highest priority.

Step 7 Click Add. The hierarchical tree changes to reflect the new SIP IP link added.


Configuring Automatic Congestion Control

Automatic congestion control (ACC) is used to configure call load balancing. Use the following procedure to configure ACC:


Step 1 In the left pane of the main Cisco VSPT window, click Auto Congestion Ctrl > Response Category. A window similar to the one shown in Figure 3-33 displays.

Figure 3-33 Response Category

Step 2 Enter the ACL name of the ACC response category.

Step 3 Enter values, in percentages, for load control types for ACL1, ACL2, and ACL3.

Step 4 Click Add. The hierarchical tree changes to reflect the response category added.

Step 5 Click MCL Thresholds. A window similar to the one shown in Figure 3-34 displays.

Figure 3-34 MCL Thresholds

Step 6 Select the Machine Congestion Level (MCL) threshold name from the drop-down menu. MCLs can be set for

Callrate

CPU

memoryaddress

queuelen

virtualmemory

Step 7 Enter MCL onset and abatement threshold values, in percentages for MCL1, MCL2, and MCL3.

Step 8 Click Add. The hierarchical tree changes to reflect the MCL threshold added.

Step 9 Click MCL Callreject. A window similar to the one shown in Figure 3-35 displays.

Figure 3-35 MCL Call Rejection

Step 10 Select the MCL name in the drop-down list.

Step 11 Enter the percentage of calls to reject at this level.

Step 12 Click Add. The hierarchical tree changes to reflect the call reject rate added.


Configuring Advice of Charge

Advice of charge (AOC) is used (typically in the European arena) where licensed operators are required to provide the capability to inform interconnecting networks of the charge rates applied to calls traversing the networks. The charge rates are determined by destination, distance, time of day, and day of year. Additionally, since tariff rates can vary through the length of a day and from day to day, calls that continue through a tariff rate change must have their charges adjusted accordingly, and the interconnecting network must be informed of the rate change.

Use the following procedures to configure AOC on the MGC:

Configuring a Holiday

Use the following procedure to configure a holiday on the MGC:


Step 1 In the left pane of the main Cisco VSPT window, click Advice of Charge> Holiday. A window similar to the one shown in Figure 3-36 displays.

Figure 3-36 Advice of Charge, Holiday

Step 2 Enter a date for the holiday by clicking the name in the drop-down list for the desired month.

Step 3 Click the up or down arrow to select the desired year.

Step 4 Click the day to select the desired day.

Step 5 Click the Holiday drop-down list to select a holiday value.

UNSET

HOL1

HOL2

HOL3

Step 6 Click Add to add the holiday date. The hierarchical tree changes to reflect the holiday added using a yy.mm.dd format (for example, 02.12.25).


Configuring a Charge

Use the following procedure to configure a charge on the MGC:


Step 1 In the left pane of the main Cisco VSPT window, click Advice of Charge> Charge. A window similar to the one shown in Figure 3-37 displays.

Figure 3-37 Advice of Charge, Charge

Step 2 Enter the charge origin (for example, 0-9999).

Step 3 Enter the charge destination (for example, 0-9999).

Step 4 Enter the day of week (for example, Sunday-Saturday or HOL1-HOL3).

Step 5 Enter a tariff description.

Step 6 Click Add to add the charge. The hierarchical tree changes to reflect the charge added using an xx-yy-day format (for example, 1-100-Sunday).


Configuring a Tariff

Use the following procedure to configure a tariff on the MGC:


Step 1 In the left pane of the main Cisco VSPT window, click Advice of Charge> Tariff. A window similar to the one shown in Figure 3-38 displays.

Figure 3-38 Advice of Charge, Tariff

Step 2 Enter the tariff ID (for example, 0-9999).

Step 3 Enter the tariff rate (for example, 0-999999).

Step 4 Enter the tariff scale (for example, 0-999999).

Step 5 Click Add to add the tariff. The hierarchical tree changes to reflect the tariff added using the tariff ID as the format (for example, 1).


Configuring a Meter Tariff

Use the following procedure to configure a meter tariff on the MGC:


Step 1 In the left pane of the main Cisco VSPT window, click Advice of Charge> Meter Tariff. A window similar to the one shown in Figure 3-39 displays.

Figure 3-39 Advice of Charge, Meter Tariff

Step 2 Enter the Tariff ID (for example, 0-9999).

Step 3 Enter the Number of Pulses on Answer (for example, 0-255).

Step 4 Enter the Interval Between Pulses (for example, 500-3600000).

Step 5 Enter the Number of Periodic Pulses (for example, 0-255).

Step 6 Enter the Periodic Charge Application (for example, 0 or 1).

Step 7 Enter the AOC Indicator (for example, 0 or 1).

Step 8 Enter the Maximum Call Length (for example, 0-240).

Step 9 Enter the Tariff Type (for example, 0-15).

Step 10 Click Add to add the tariff. The hierarchical tree changes to reflect the meter tariff added using the tariff ID as the format (for example, 1).


Configuring a Pritariff

Use the following procedure to configure a Pritariff on the MGC:


Step 1 In the left pane of the main Cisco VSPT window, click Advice of Charge > Pritariff. A window similar to the one shown in Figure 3-40 displays.

Figure 3-40 Advice of Charge, Pritariff

Step 2 Enter the Tariff ID (for example, 1-9999).

Step 3 Enter the S Charged Item (for example, 0-4).

Step 4 Enter the SCA (for example, 1-10).

Step 5 Enter the S Recorded Charge (for example, 1-6).

Step 6 Enter the D Recorded Charge (for example, 1-3).

Step 7 Enter the E Recorded Charge (for example, 1-3).

Step 8 Enter the Currency.

Step 9 Enter the Amount (for example, 1-16777215).

Step 10 Enter the Amount Multiplier (for example, 0-6).

Step 11 Enter the Time Length (for example, 0-16777215).

Step 12 Enter the Time Scale (for example, 0-6).

Step 13 Enter the Granularity Length (for example, 0-16777215).

Step 14 Enter the Granularity Time Scale (for example, 0-6).

Step 15 Enter the Volume (for example, 0-2).

Step 16 Enter the SCU (for example, 0-32767).

Step 17 Enter the Billing Id (for example, 0-6).

Step 18 Enter the Charging Units (for example, 1-16777215).

Step 19 Enter the Duration (for example, 0-16777215).

Step 20 Enter the Rate Type (for example, 0 or 1).

Step 21 Enter the Initial Tariff.

Step 22 Click Add to add the tariff. The hierarchical tree changes to reflect the pritariff added using the tariff ID as the format (for example, 1).


Configuring a Pricharge

Use the following procedure to configure a tariff on the MGC:


Step 1 In the left pane of the main Cisco VSPT window, click Advice of Charge > Pricharge. A window similar to the one shown in Figure 3-41 displays.

Figure 3-41 Advice of Charge, Pricharge

Step 2 Enter the charge origin (for example, 0-9999).

Step 3 Enter the charge destination (for example, 1-9999).

Step 4 Enter the day of week (for example, Sunday-Saturday or HOL1-HOL3).

Step 5 Enter the STariff.

Step 6 Enter the DTariff.

Step 7 Enter the ETariff.

Step 8 Click Add to add the pricharge. The hierarchical tree changes to reflect the pricharge in an xx-yy-day format (for example, 1-100-Sunday).

Adding GTD Parameters

Generic transparency descriptor (GTD) provides a means for specifying messages of various protocols used in the PSTN network in plain text format. This is so they can be easily understood by the network elements within the IP network or lie on the boundary between PSTN and IP. To provision GTD Parameters, use the following steps:


Step 1 Click the icon next to Signaling to expand the hierarchical tree.

Step 2 Click GTD Parameters in the left pane of the main VSPT window. A window similar to the one shown in Figure 3-42 displays.

Figure 3-42 Adding GTD Parameters

Step 3 Enter a name.

Step 4 Enter the GTD Params.

Step 5 Enter the Override.

Step 6 Click Add. The hierarchical tree changes to reflect the GTD Parameters added.


Configuring TOS

The type-of-service (TOS) component is used to set a global dscp value to signaling traffic. To provision TOS, use the following steps:


Step 1 Click the icon next to Signaling to expand the hierarchical tree.

Step 2 Click TOS in the left pane of the main VSPT window. A window similar to the one shown in Figure 3-43 displays.

Figure 3-43 Configuring TOS

Step 3 In the DSCP drop-down menu, select a value.

Step 4 Click Modify. The hierarchical tree changes to reflect the TOS configured.


Configuring Cisco MGW Control Links

Cisco Media Gateway (MGW) control links provide the communication path used by the signaling controller to control the bearer traffic passing through each media gateway. To configure the Cisco MGW control links, use the components outlined in the sections below.

Adding External Nodes

Adding a Session Set

Adding an IPFAS Signaling Service

Adding an MGCP Signaling Service

Adding a DPNSS Path

Adding an H.248 Signaling Service

Adding an EISUP Signaling Service

Adding an LIpath Signaling Service

Adding a NAS Signaling Service

Adding a CTI Signaling Service

Adding an SS7 SGP

Adding a TCPLNK

Adding a BRI Signaling Service

Adding a RAPATH

Adding a RASERVER for RAPATH

Configuring IP Links

Adding IP Links for MGCP

Adding IP Links for H248

Adding IP Links for EISUP

Adding IP Links for LI

Adding IP Links for NAS

Adding an ASSOCIATION

Adding a CTI Manager

Adding an AXL Server

Adding External Nodes

An external node is a node with which the MGC communicates either directly or indirectly. In the example presented below, the media gateway is the external node. lists the external node properties. Use the values in this table as you add external nodes to your MGC.

Table 3-11 External Node Properties 

Field Name
MML Parameter
Description
Default
Valid Values

Name

name

Identifies the MML name for the external node

External-1

Up to 20 alphanumeric characters; cannot start with a number

Description

desc

Describes the external node

External Node

Up to 128 alphanumeric characters

Type

type

Lists the various external nodes supported; for example, Cisco ITP-L or VISM

<UNSET>

See the drop-down list


Use the external node component to add Cisco MGWs. You must create an external node for each Cisco MGW.

Use the following procedure to add an external node to the MGC. Refer to Table 3-11 for property values.


Step 1 Click External Node in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-44 displays.

Figure 3-44 Adding External Nodes

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the Type drop-down menu, select the type of external node (for example, click MGX8850, and then click Add). The hierarchical tree changes to reflect the external node added (for example, Cisco  MGX 8850).

Step 5 In the ISDNSigType drop-down menu, select the ISDNSigtype. Choices are N/A and IUA.

Step 6 Enter the M3UA/SUA group.

Step 7 Click Add. The hierarchical tree changes to reflect the External Nodes added.


Configuring Cisco MGWs

A Cisco MGW is the interface between the QoS packet network and the PSTN/ISDN network. A gateway digitizes and compresses voice calls from the PSTN, creating IP packets for routing to another gateway for forwarding to the PSTN or to a terminal.

Use the following procedure to configure the external node as a Cisco MGW.


Step 1 Click the external node (added in the prior procedure) in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-45 displays.

Figure 3-45 Configuring a Cisco MGW

Step 2 In the MGX8850 Slot drop-down menu, select the slot.

Step 3 Enter the GW Domain.

Step 4 Enter the IP Address #1 in dotted notation.

Step 5 Enter the IP Subnet Mask #1 in dotted notation.

Step 6 Click Modify. The hierarchical tree changes to reflect the Cisco MGW added.


Note Specific components and steps to provision them vary depending on the type of external node you are provisioning.



Adding a Session Set

A session set is a pair of backhaul IP links used by the MGC to communicate with external nodes that support IP Facility Associated Signaling (IPFAS) and provide communication for IPFAS signaling service between the MGC node and a media gateway. You must configure a session set before you can add an IPFAS signaling service.

Table 3-12 lists session set properties.

Table 3-12 Session Set Properties

Field Name
Description
Default
Valid Values

Name

Unique ID of this component

None

Up to 20 alphanumeric characters; the name should begin with an alphabetic character. "-" is the only special character permitted.

IPAddr1

Local logical IP address 1

IP_Addr1

IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4.

IPAddr2

Local logical IP address 2

IP_Addr2

IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4.

Port

Local UDP port number

None

1025-65535.

PeerAddr1

Remote IP address 1

None

IP address in dotted decimal notation.

PeerAddr2

Remote IP address 2

None

IP address in dotted decimal notation.

IPRoute 1

IP Route 1 Name

None

See the drop-down list in Figure 3-46.

IPRoute 2

IP Route 2 Name

None

See the drop-down list in Figure 3-46.

PeerPort

Remote UDP port

None

1025-65535.

Extnode

MML name of external node

None

MML name of previously configured external port.

Type

Session Set Type

IPFAS

IPFAS and BSMV0.


Use the following procedure to add a session set to the MGC. Refer to Table 3-12 for property values.


Step 1 Click SESSIONSET in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-46 displays.

Figure 3-46 Adding a Session Set

Step 2 Enter a name.

Step 3 In the IP Addr 1 and IP Addr2 drop-down menus, select the appropriate IP address.

Step 4 Enter the port number.

Step 5 From the Peer Address 1 and Peer Address 2 drop-down menus, select the IP address of the peer gateway, if applicable.

Step 6 In the IP Route 1 and IPRoute 2 drop-down menus, select the appropriate IPRoute.

Step 7 Enter the Peer Port number.

Step 8 In the Type drop-down menu, select the session set type. Choices are IPFAS and BSMV0.

Step 9 Click Add. The hierarchical tree changes to reflect the session set added (see Figure 3-46).


Adding and Changing Session Set Properties

You can add and change the properties of a session set after it is created. Changes apply to all session sets created. You do not have to change the default properties.

Perform the following steps to add or change session set properties:


Step 1 Select the appropriate sessionset in the left pane of the main Cisco VSPT window.

Step 2 Click Properties to display the list of properties. A window similar to the one shown in Figure 3-47 displays.

Figure 3-47 Adding and Changing Session Set Properties

Step 3 To add a property, select a property and enter a value.

Step 4 Click Add.

Step 5 To modify an existing property, click the property you want to change.

Step 6 In the value field, enter the new property value.

Step 7 Click Modify.

Step 8 Click OK when you are finished.


Note You cannot modify properties until you have created the sessionset.



Adding an IPFAS Signaling Service

An IPFAS signaling service defines the FAS or NFAS over IP transport service or signaling path from an MGC node to a media gateway.

Table 3-13 lists the IPFAS signaling service properties.

Table 3-13 IPFAS Signaling Service Properties 

Property
MML Parameter
Description
Default
Valid Values

Name

name

Identifies the MML name of the IPFAS service path.

Ipfas-1

Up to 20 alphanumeric characters.

Description

desc

Describes the IPFAS service path.

Ipfaspath signaling service

Up to 128 alphanumeric characters.

External Node

extnode

Identifies the external node.

None

User defined.

Up to 20 alphanumeric characters; cannot start with a number.

Side

side

Distinguishes the network equipment (like a switch) from the user equipment (like a terminal adapter or PBX). (Used for ISDN systems.)

network

Network,

User.

MDO

mdo

Identifies the protocol (MDO file name) for this IPFAS service path. You select the MDO file name in a drop-down list.

Bell_1268

See list.

Customer Group ID

custgrpid

Contains a unique identifier for the number analysis file. (Used with nailed solutions only.)

0000

0000-9999.

A/B Flag

abflag

Specifies DPNSS a or b side.

(Field is ignored for ETSI.)

n

A side.
B side.
B—NA.

Call Reference Length

crlen

Identifies the field length (1 or 2 bytes) for the call reference number.

2—standard ETSI

0—DPNSS.
1—1 byte.
2—2 bytes.

Originating Label

origlabel

Origination Location Label

None

See the drop-down list in Figure 3-51.

Termination Label

termlabel

Termination Location Label

None

See the drop-down list in Figure 3-51.


Use the following procedure to add the ipfaspaths from the media gateway. The MML component name is IPFASPath. Refer to Table 3-13 for property values.


Step 1 Click IPFAS in the left pane of the main Cisco VSPT window, and click Add in the right pane. A window similar to the one shown in Figure 3-48 displays.

Figure 3-48 Adding an IPFAS Signaling Service

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the Side drop-down menu, select the side (Q.931 call model side):

Network

User

Step 5 In the MDO File Name drop-down menu, select the protocol for this signaling service; for example, ATT_41459.

Step 6 Enter the customer group ID.

Step 7 In the A/B Flag drop-down menu, select a value.

Step 8 In the Call Reference Length drop-down menu, select 0, 1, or 2.

Step 9 In the Originating Label and Termination Label drop-down menus, select the appropriate value.

Step 10 In the Session Set drop-down menu, select the name of a session set.

Step 11 In the DS1 type drop-down menu, select a value.

Step 12 In the MGW Card Slot drop-down menu, select a value.

Step 13 In the DS1 start drop-down menu, select a value.

Step 14 Enter a step interval.

Step 15 Enter the number of IPFASPATHs to create multiple IPFASPATHs.


Note You cannot have more than 168 IP links using the same UDP connection (same local port, local IP address, remote port, and remote address).


Step 16 Click Add. The top portion of the window changes to reflect the IPFAS signaling service added, and the D channel for the IPFAS signal path is displayed in the lower portion of the window (similar to the window shown in Figure 3-49).


Note Each FAS PRI defined in the Cisco MGW requires its own IPFASPath. Define an IPFASPath for each PRI D channel on the Cisco MGW.


Figure 3-49 IPFAS Signaling Service Added

Step 17 To add more D channels to an IPFAS signaling path, highlight the IPFAS signaling path in the top pane of the window, and click Add. A window similar to the one shown in Figure 3-50 displays.

Figure 3-50 Add a D Channel

Step 18 Enter a name.

Step 19 Enter the description.

Step 20 Select a priority from the Priority drop-down menu.

Step 21 Select a signal slot.

Step 22 Select a signal port.

Step 23 Select a session set.

Step 24 Click Add. The new D channel for the IPFAS signaling path displays in the lower portion of the window.

Step 25 Continue adding D channels for the IPFAS signaling paths as needed.


Changing IPFAS Signaling Service Properties

You can modify the properties of the IPFAS signaling services that you created. These properties apply to all IPFAS signaling services. You do not have to change the default properties.

Use the following procedure to add or change IPFAS signaling service properties:


Step 1 In the window shown in Figure 3-49, select an IPFAS signaling service from the top portion of the window and click Modify. A window similar to the one shown in Figure 3-51 displays.

Figure 3-51 Adding and Changing IPFAS Signaling Properties

Step 2 To modify the IPFAS path configuration, click Properties. A window similar to the one shown in Figure 3-52 displays.

Figure 3-52 IPFAS Signaling Service Property Added

Step 3 To add a property, select the property in the Name drop-down list.

Step 4 Enter the property value in the Value drop-down list.

Step 5 Click Add. The new property and value appear in the top portion of the window.

Step 6 To modify a property, click the property you want to change.

Step 7 In the value field, enter the new property value.

Step 8 Click Modify.

Step 9 Click OK when you are finished adding or modifying properties.



Note You cannot modify properties until you have created the IPFAS signaling service.


Adding an MGCP Signaling Service

The MGCP signaling service specifies the path that the MGC node uses to communicate with a media gateway. The MML component name is MGCPPATH.

Table 3-14 lists the MGC signaling service properties. Use the values in the table as you add an MGCP signaling service.

Table 3-14 MGC Signaling Service Properties

Property
MML Parameter
Description
Default
Valid Values

Name

name

Identifies the MML name for the MGCP signaling service

Mgcp-1

Up to 20 alphanumeric characters

Description

desc

Describes the service path

Mgcppath Signaling Service

Up to 128 alphanumeric characters

External Node

extnode

Identifies the gateway for this signaling service

None

User defined



Note Set the mgcpDomainNameRemote and mgcpHeartbeatInterval properties for all MGCP Signaling Services defined in your Cisco MGC. For more information, see the "Adding and Changing MGCP Signaling Service Properties" section.


Use the following procedure to add MGCP signaling service paths to the media gateway. Refer to Table 3-14 for property values.


Step 1 Click MGCP in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-53 displays.

Figure 3-53 Adding an MGCP Signaling Service

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 Click Add. The hierarchical tree changes to reflect the MGCP signaling service link added.


Adding and Changing MGCP Signaling Service Properties

You can add and change the properties of the signaling service for all the signaling services you create. You do not have to change the default properties.

Set the following properties for all MGCP signaling services defined in your Cisco MGC:

mgcpDomainNameRemote—A valid endpoint of the gateway (for example, a VISM card in a media gateway with a domain name of mgx88501.vism01 would be vism/t1-1/1@mgx88501.vism01).

The media gateway MGCP domain name is a property of the media gateway object. You can derive this from the MGCP path object, because each MGCP path object refers to an external node and each external node refers to a media gateway.

mgcpHeartbeatInterval—1.

Use the following procedure to add or change MGCP signaling service properties:


Step 1 Click Properties to display the list of properties. A window similar to the one shown in Figure 3-54 displays.

Figure 3-54 Adding and Changing MGCP Signaling Properties

Step 2 To add a property, select the property name from the drop-down menu and enter the value, and click Add. A window similar to the one shown in Figure 3-55 displays with the property added.

Figure 3-55 MGCP Signaling Service Property Added

Step 3 To modify a property, click the property you want to change.

Step 4 In the value field, enter the new property value.

Step 5 Click Modify.

Step 6 Click OK when you are finished.


Note You cannot modify properties until you have created the MGCP signaling service.



Adding a DPNSS Path

Use the following procedure to add DPNSS paths to the media gateway:


Step 1 Click DPNSS in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-56 displays.

Figure 3-56 Adding a DPNSS Path

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 Enter the Signal Port.

Step 5 Enter the Signal Slot.

Step 6 Enter the Customer Group ID.

Step 7 In the Origination Label and Termination Label drop-down menu, select the appropriate location label.

Step 8 Click Add. The hierarchical tree changes to reflect the DPNSS path added.


Adding and Changing DPNSS Path Signaling Properties

Use the following procedure to add or change DPNSS path signaling properties:


Step 1 Click Properties to display the list of properties. A window similar to the one shown in Figure 3-57 displays.

Figure 3-57 Adding and Changing DPNSS Path Signaling Properties

Step 2 To add a property, enter a name and value.

Step 3 Click Add. A window similar to the one shown in Figure 3-58 displays with the property added.

Figure 3-58 DPNSS Path Signaling Property Added

Step 4 To modify a property, click the property you want to change.

Step 5 In the value field, enter the new property value.

Step 6 Click Modify.

Step 7 Click OK when you are finished.


Note You cannot modify properties until you have created the DPNSS path.



Adding an H.248 Signaling Service

Use the following procedure to add an H.248 signaling service to the media gateway:


Step 1 Click H248 in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-59 displays.

Figure 3-59 Adding an H.248 Signaling Service

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 Click Add. The hierarchical tree changes to reflect the H248 signaling service added.


Adding and Changing H248 Signaling Properties

Use the following procedure to add or change H248 signaling properties:


Step 1 Click Properties to display the list of properties. A window similar to the one shown in Figure 3-60 displays.

Figure 3-60 Adding and Changing H248 Signaling Properties

Step 2 To add a property, enter a name and value.

Step 3 Click Add. A window similar to the one shown in Figure 3-61 displays with the property added.

Figure 3-61 H248 Signaling Property Added

Step 4 To modify a property, click the property you want to change.

Step 5 In the value field, enter the new property value.

Step 6 Click Modify.

Step 7 Click OK when you are finished.


Note You cannot modify properties until you have created the H248 signaling service.



Adding an EISUP Signaling Service

Use the following procedure to add an EISUP signaling service to the media gateway:


Step 1 Click EISUP in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-62 displays.

Figure 3-62 Adding an EISUP Signaling Service

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 Enter the Customer Group ID.

Step 5 In the Origination Label and Termination Label drop-down menus, select the appropriate location label.

Step 6 Click Add. The hierarchical tree changes to reflect the EISUP signaling service added.


Adding or Changing EISUP Signaling Properties

Use the following procedure to add or change EISUP signaling properties:


Step 1 Click Properties to display the list of properties. A window similar to the one shown in Figure 3-63 displays.

Figure 3-63 Adding and Changing EISUP Signaling Properties

Step 2 To add a property, enter a name and value.

Step 3 Click Add. A window similar to the one shown in Figure 3-64 displays with the property added.

Figure 3-64 EISUP Signaling Property Added

Step 4 To modify a property, click the property you want to change.

Step 5 In the value field, enter the new property value.

Step 6 Click Modify.

Step 7 Click OK when you are finished.


Note You cannot modify properties until you have created the EISUP signaling service.



Adding an LIpath Signaling Service

Use the following procedure to add a lawful intercept path (LIpath) signaling service to the media gateway:


Step 1 Click LI in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-65 displays.

Figure 3-65 Adding LIpath Signaling Service

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 Click Add. The hierarchical tree changes to reflect the LIpath signaling service added.


Adding or Changing LI Signaling Properties

Use the following procedure to add or change LI signaling properties:


Step 1 Click Properties to display the list of properties. A window similar to the one shown in Figure 3-66 displays.

Figure 3-66 Adding and Changing LI Signaling Properties

Step 2 To add a property, enter a name and value.

Step 3 Click Add. A window similar to the one shown in Figure 3-67 displays with the property added.

Figure 3-67 LI Signaling Property Added

Step 4 To modify a property, click the property you want to change.

Step 5 In the value field, enter the new property value.

Step 6 Click Modify.

Step 7 Click OK when you are finished.


Note You cannot modify properties until you have created the LI signaling service.



Adding a NAS Signaling Service

Use the following procedure to add a NAS signaling service to the media gateway:


Step 1 Click NAS in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-681 displays.

Figure 3-68 Adding a NAS Signaling Service

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the message definition object (MDO) drop-down menu, select BELL_1268_C2.

Step 5 Enter the Customer Group ID.

Step 6 Enter the SigSlot.

Step 7 Enter the SigPort.

Step 8 Click Add. The hierarchical tree changes to reflect the EISUP signaling service added.


Adding and Changing NAS Signaling Properties

Use the following procedure to add or change NAS signaling properties:


Step 1 Click Properties to display the list of properties. A window similar to the one shown in Figure 3-69 displays.

Figure 3-69 Adding and Changing NAS Signaling Properties

Step 2 To add a property, enter a name and value.

Step 3 Click Add. A window similar to the one shown in Figure 3-70 displays with the property added.

Figure 3-70 NAS Signaling Property Added

Step 4 To modify a property, click the property you want to change.

Step 5 In the Value field, enter the new property value.

Step 6 Click Modify.

Step 7 Click OK when you are finished.


Note You cannot modify properties until you have created the NAS signaling service.



Adding a CTI Signaling Service

Use the following procedure to add a CTI signaling service to the media gateway:


Step 1 Click CTI in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-71 displays.

Figure 3-71 Adding a CTI Signaling Service

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the MDO drop-down menu, select the appropriate mdo.

Step 5 Click Add. The hierarchical tree changes to reflect the EISUP signaling service added.


Adding and Changing CTI Signaling Properties

Use the following procedure to add or change CTI signaling properties:


Step 1 Click Properties to display the list of properties. A window similar to the one shown in Figure 3-72 displays.

Figure 3-72 Adding and Changing CTI Signaling Properties

Step 2 To add a property, enter a name and value.

Step 3 Click Add. A window similar to the one shown in Figure 3-73 displays with the property added.

Figure 3-73 CTI Signaling Property Added

Step 4 To modify a property, click the property you want to change.

Step 5 In the value field, enter the new property value.

Step 6 Click Modify.

Step 7 Click OK when you are finished.


Note You cannot modify properties until you have created the CTI signaling service.



Adding an SS7 SGP

Use the following procedure to add an SS7 SGP:


Step 1 Click SGP in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-74 displays.

Figure 3-74 Adding an SS7 SGP

Step 2 Enter the name.

Step 3 Enter the description.

Step 4 Click Add. The hierarchical tree changes to reflect the SS7 SGP added.


Adding a TCPLNK

Use the following procedure to add a TCPLNK:


Step 1 Click TCPLNK in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-75 displays.

Figure 3-75 Adding a TCPLNK

Step 2 Enter a name.

Step 3 In the IP Address drop-down menu, select the appropriate IP address.

Step 4 Enter the Port number.

Step 5 In the Peer Address drop-down menu, select the appropriate IP address.

Step 6 Enter the peer Port number.

Step 7 In the IP Router drop-down menu, select the appropriate IPRoute.

Step 8 Click Add. The hierarchical tree changes to reflect the Tcplnk added.


Adding and Changing Tcplnk Properties

You can add and change the properties of a Tcplnk after it is created. Changes apply to all tcplnks created. You do not have to change the default properties.

Perform the following steps to add or change tcplnk properties:


Step 1 Select the appropriate Tcplnk in the left pane of the main Cisco VSPT window.

Step 2 Click Properties to display the list of properties. A window similar to the one shown in Figure 3-76 displays.

Figure 3-76 Adding and Changing Tcplnk Properties

Step 3 To add a property, select a property and enter a value.

Step 4 Click Add.

Step 5 To modify an existing property, click the property you want to change.

Step 6 In the value field, enter the new property value.

Step 7 Click Modify.

Step 8 Click OK when you are finished modifying properties.


Note You cannot modify properties until you have created the Tcplnk.



Adding a BRI Signaling Service

Use the following procedure to add a BRI signaling service to the media gateway:


Step 1 Click BRI in the left pane of the main Cisco VSPT window.

Step 2 Click Add. A window similar to the one shown in Figure 3-77 displays.

Figure 3-77 Adding a BRI Signaling Service

Step 3 Enter a name.

Step 4 Enter the description.

Step 5 In the Side drop-down menu, select one of the following sides (Q.931 call model side):

Network

User

Step 6 In the MDO drop-down menu, select the protocol for this signaling service (for example, ATT_41459).

Step 7 Enter the customer group ID.

Step 8 In the Call Reference Length drop-down menu, select 0, 1, or 2 (0- DPNSS, 1 - 1 byte, 2 - 2 bytes).

Step 9 In the Tcplnk drop-down menu, select the appropriate Tcplnk.

Step 10 In the First Slot drop-down menu, select a value.

Step 11 In the First Subunit drop-down menu, select a value.

Step 12 In the First Port drop-down menu, select a value.

Step 13 Enter a Number To Create.

Step 14 Click Add. The top portion of the window changes to reflect the BRI signaling service added, and the D channel for the BRI signal path is displayed in the lower portion of the window (similar to the window shown in Figure 3-78).

Figure 3-78 BRI Signaling Service Added

Step 15 To modify D channels in a BRI signaling path, select the BRI signaling path in the top pane of the window, and click Add. A window similar to the one shown in Figure 3-79 displays.

Figure 3-79 Modify a D Channel

Step 16 Enter a name.

Step 17 Enter a description.

Step 18 Select a signal slot.

Step 19 Select a signal subunit.

Step 20 Select a signal port.

Step 21 Select a Tcplnk.

Step 22 Click OK. The D channel for the BRI signaling path displays in the lower portion of the window.


Adding a RAPATH

Use the following procedure to define a communication path to a RADIUS accounting server cluster. Each cluster is made up of one or multiple RADIUS servers.


Step 1 Click RAPATH in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-80 displays.

Figure 3-80 Adding a RAPATH

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 Click Add. The hierarchical tree changes to reflect the RAPATH added.


Adding a RASERVER for RAPATH

Use the following procedure to define a signal channel to the RADIUS accounting server. These procedure also associates a RADIUS accounting signal path to this channel.


Step 1 Click the icon next to RAPATH in the left pane of the main Cisco VSPT window to expand the tree, and click RASERVER. A window similar to the one shown in Figure 3-81 displays.

Figure 3-81 Adding RASERVER

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the IP Addr drop-down menu, select the IP address of the MGC:

IP Addr1

IP Addr2

IP Addr3

IP Addr4


Note The numbered address for this value is found in the XECfgParm.dat file set during your initial system configuration. See the Cisco Media Gateway Controller Software Installation and Configuration (Release 9.7) for more information.


Step 5 Enter a number for the UDP port on the MGC. You can use any unused UDP port number, but you should not use 1 through 1024; these are reserved for other applications.

Step 6 In the Peer Address drop-down menu, select the peer address.

Step 7 Enter the port number in the peer port field.

Step 8 In the IP Route drop-down menu, select the appropriate IP route.

Step 9 Enter the Order, Key, Timeout and Retrycount.

Step 10 Click Add. The hierarchical tree changes to reflect the RASERVER added.


Configuring IP Links

The last step in adding Cisco MGW control links is the configuration of the IP links. You must identify each end of each link:

At the MGC node end of each link, associate the link with an Ethernet interface, an IP address, and an IP port.

At the media gateway end of each link, identify the signaling link terminal by specifying an IP address and port.

Adding IP Links for MGCP

An IP link for MGCP IP links identifies the connection that supports the MGCP service between an MGC Ethernet interface and a media gateway. Use the following procedure to add MGCP IP links:


Step 1 Click the icon next to MGCP in the left pane of the main Cisco VSPT window to expand the tree, and click Links. A window similar to the one shown in Figure 3-82 displays.

Figure 3-82 Adding MGCP IP Links

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the IP Addr drop-down menu, select the IP address of the MGC:

IP Addr1

IP Addr2

IP Addr3

IP Addr4


Note The numbered IP address is found in the XECfgParm.dat file set during your initial system configuration. See the Cisco Media Gateway Controller Software Installation and Configuration (Release 9.7) for more information.


Step 5 In the IP Route drop-down menu, select the appropriate IP route.

Step 6 Enter a number of the UDP port on the MGC. You can enter any unused UDP port number (2427 is recommended for MGCP), but you should not use 1 through 1024; these are reserved for other applications.

Step 7 In the Priority drop-down menu, select a priority. Value range: 1 through 4. 1 is the highest priority.

Step 8 In the Peer Address drop-down menu, select the peer address.

Step 9 Enter the port number in the peer port field.

Step 10 Click Add. The hierarchical tree changes to reflect the MGCP IP link added (see Figure 3-82).


Adding IP Links for H248

An IP link for H248 IP links identifies the connection that supports the H248 service between an MGC Ethernet interface and a media gateway. Use the following procedure to add H248 IP links:


Step 1 Click the icon next to H248 in the left pane of the main Cisco VSPT window to expand the tree, and click Links. A window similar to the one shown in Figure 3-83 displays.

Figure 3-83 Adding H248 IP Links

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the IP Addr drop-down menu, select the IP address of the MGC:

IP Addr1

IP Addr2

IP Addr3

IP Addr4


Note The numbered IP address for this value is found in the XECfgParm.dat file set during your initial system configuration. See the Cisco Media Gateway Controller Software Installation and Configuration (Release 9.7) for more information.


Step 5 In the IP Route drop-down menu, select the appropriate IP route.

Step 6 Enter a number of the UDP port on the MGC. You can enter any unused UDP port number (2944 is recommended for H248), but you should not use 1 through 1024; these are reserved for other applications.

Step 7 In the Priority drop-down menu, select a priority. Value range: 1 through 4. 1 is the highest priority.

Step 8 In the Peer Address drop-down menu, select the peer address.

Step 9 Enter the port number in the peer port field.

Step 10 Click Add. The hierarchical tree changes to reflect the H248 IP link added.


Adding IP Links for EISUP

An IP link for EISUP IP links identifies the connection that supports the EISUP service between an MGC Ethernet interface and a media gateway. Use the following procedure to add EISUP IP links:


Step 1 Click the icon next to EISUP in the left pane of the main Cisco VSPT window to expand the tree, and click Links. A window similar to the one shown in Figure 3-84 displays.

Figure 3-84 Adding EISUP IP Links

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the IP Addr drop-down menu, select the IP address of the MGC:

IP Addr1

IP Addr2

IP Addr3

IP Addr4


Note The numbered IP address for this value is found in the XECfgParm.dat file set during your initial system configuration. See the Cisco Media Gateway Controller Software Installation and Configuration (Release 9.7) for more information.


Step 5 In the IP Route drop-down menu, select the appropriate IP route.

Step 6 Enter a number of the UDP port on the MGC. You can enter any unused UDP port number (5001 is recommended for EISUP), but you should not use 1 through 1024; these are reserved for other applications.

Step 7 In the Priority drop-down menu, select a priority. Value range: 1 through 4. 1 is the highest priority.

Step 8 In the Peer Address drop-down menu, select the peer address.

Step 9 Enter the port number in the peer port field.

Step 10 Click Add. The hierarchical tree changes to reflect the EISUP IP link added.


Adding IP Links for LI

An IP link for LI IP links identifies the connection that supports the LI service between an MGC Ethernet interface and a media gateway. Use the following procedure to add LI IP links:


Step 1 Click the icon next to LI in the left pane of the main Cisco VSPT window to expand the tree, and click Links. A window similar to the one shown in Figure 3-85 displays.

Figure 3-85 Adding LI IP Links

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the IP Addr drop-down menu, select the IP address of the MGC:

IP Addr1

IP Addr2

IP Addr3

IP Addr4


Note The numbered IP address for this value is found in the XECfgParm.dat file set during your initial system configuration. See the Cisco Media Gateway Controller Software Installation and Configuration (Release 9.7) for more information.


Step 5 In the IP Route drop-down menu, select the appropriate IP route.

Step 6 Enter a number of the UDP port on the MGC. You can enter any unused UDP port number (2047 is recommended for LI), but you should not use 1 through 1024; these are reserved for other applications.

Step 7 In the Priority drop-down menu, select a priority. Value range: 1 through 4. 1 is the highest priority.

Step 8 In the Peer Address drop-down menu, select the peer address.

Step 9 Enter the port number in the peer port field.

Step 10 Click Add. The hierarchical tree changes to reflect the LI IP link added.


Adding IP Links for NAS

An IP link for NAS IP links identifies the connection that supports the NAS service between an MGC Ethernet interface and a media gateway. Use the following procedure to add NAS IP links:


Step 1 Click the icon next to NAS in the left pane of the main Cisco VSPT window to expand the tree, and click Links. A window similar to the one shown in Figure 3-86 displays.

Figure 3-86 Adding NAS IP Links

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the IP Addr drop-down menu, select the IP address of the MGC:

IP Addr1

IP Addr2

IP Addr3

IP Addr4


Note The numbered IP address for this value is found in the XECfgParm.dat file set during your initial system configuration. See the Cisco Media Gateway Controller Software Installation and Configuration (Release 9.7) for more information.


Step 5 In the IP Route drop-down menu, select the appropriate IP route.

Step 6 Enter a number of the UDP port on the MGC. You can use any unused UDP port number (3001 is recommended for NAS), but you should not use 1 through 1024; these are reserved for other applications.

Step 7 In the Priority drop-down menu, select a priority. Value range: 1 through 4. 1 is the highest priority.

Step 8 In the Peer Address drop-down menu, select the peer address.

Step 9 Enter the port number in the peer port field.

Step 10 Click Add. The hierarchical tree changes to reflect the NAS IP link added.


Adding C7 IP Links

Use the following procedure to add C7 IP links.


Step 1 Click C7 in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-87 displays.

Figure 3-87 Adding a C7 IP Link

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the Priority drop-down menu, select the priority.

Step 5 In the Linkset drop-down menu, select the linkset for this link.


Note The linkset is created in the "Adding Linksets" section.


Step 6 In the SLC drop-down menu, select the SLC. This is the SLC for the line between the Cisco ITP-L and the STP. The SLC can be any integer from 0 through 15.

Step 7 In the SLT Port drop-down menu, select the time slot. This is the physical port on the Cisco ITP-L.


Note The time slot identifies the port number on the Cisco ITP-L. The time slot number must be unique for a link on a particular Cisco ITP-L. For example, if you have a 2T WAN interface card (WIC) in slot 0 of the Cisco ITP-L, you can use time slot value 0 for the first link you configure. The second link on the WIC uses the time slot value 1.


Step 8 In the Session Set drop-down menu, select the session set for this link.

Step 9 Click Add. The hierarchical tree changes to reflect the C7 IP link added.


Adding an ASSOCIATION

Use the following procedure to add an association:


Step 1 Click ASSOCIATION in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-88 displays.

Figure 3-88 Adding an ASSOCIATION for a Media Gateway

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the Type drop-down menu, select the appropriate type. Choices are H248, IUA, M3UA, and SUA.

Step 5 In the IP Addr 1 and IP Addr 2 drop-down menu, select the appropriate ip addr.

Step 6 Enter a number of the UDP port on the MGC.

Step 7 In the Peer Address 1 and Peer Address 2 drop-down menu, select the appropriate peer ip addr.

Step 8 Enter a number of the peer UDP port on the MGC.

Step 9 In the IPRoute1 and IPRoute 2 drop-down menus, select the appropriate iproute.

Step 10 Enter the Receive Window (valid value range: 1500 to 65535).

Step 11 Enter the Retransmit SCTP Msgs (valid value range: 0 to 100).

Step 12 Enter the Timer Retransmissions (valid value range: 0 to 100).

Step 13 Enter the Max Number Retransmissions (0 or a value from 300 to 3000).

Step 14 Enter the Max Time for datagram (valid value range: 100 to 500).

Step 15 Enter the SCTP Max Wait Time (valid value range: 100 to 600).

Step 16 Enter the Retrans Time Min Val (valid value range: 300 to 3000).

Step 17 Enter the Retrans Time Max Val (valid value range: 1000-3000).

Step 18 Enter the Retrans Time Out (valid value range: 0 or a value from 300 to 10000).

Step 19 In the Internet Protocol Precedence drop-down menu, select the appropriate ip precedence.

Step 20 In the Differential Service Code Point drop-down menu, select the appropriate dscp.

Step 21 Enter the Retrans Time Out (valid value range: 1 to 10).

Step 22 Click Add. The hierarchical tree changes to reflect the association added.


Adding a CTI Manager

Use the following procedure to add a CTI Manager:


Step 1 Click CTI Manager in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-89 displays.

Figure 3-89 Adding a CTI Manager

Step 2 Enter a name.

Step 3 Enter the description.

Step 4 In the IP Addr 1 and IP Addr 2 drop-down menus, select the appropriate ip addr.

Step 5 Enter the Local CTI Port.

Step 6 Enter the Peer Address 1 and Peer Address 2.

Step 7 Enter the Peer Port.

Step 8 In the Peer Address 1 and Peer Address 2 drop-down menus, select the appropriate peer ip addr.

Step 9 In the CTIPATH drop-down menu, select the appropriate citpath.

Step 10 In the IPRoute 1 and IPRoute 2 drop-down menus, select the appropriate iproute.

Step 11 Enter the UserName, Password, and CTI Version of CTI Manager.

Step 12 Click Add. The hierarchical tree changes to reflect the CTI Manager added.


Adding an AXL Server

Use the following procedure to add an AXL Server:


Step 1 Click AXL Server in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-90 displays.

Figure 3-90 Adding an AXL Server

Step 2 Enter the name.

Step 3 Enter the description.

Step 4 In the IP Addr 1 and IP Addr 2 drop-down menus, select the appropriate ip addr.

Step 5 Enter the Local CTI Port.

Step 6 Enter the Peer Address 1 and Peer Address 2.

Step 7 Enter the Peer Port.

Step 8 In the Peer Address 1 and Peer Address 2 drop-down menus, select the appropriate peer ip addr.

Step 9 In the CTIPATH drop-down menu, select the appropriate citpath.

Step 10 In the IPRoute 1 and IPRoute 2 drop-down menus, select the appropriate iproute.

Step 11 Enter the UserName and Password of the AXl Server.

Step 12 Click Add. The hierarchical tree changes to reflect the AXL Server added.


Configuring Bearer Traffic

Bearer traffic includes the trunk groups, trunks, and trunk routing information required by an MGC to direct calls. It uses this information in conjunction with a dial plan to perform number analysis and route selection.

A trunk is a speech path between any two switches. Trunks are DS0 endpoints; one trunk can ride on one DS0 or one DS0 can carry one trunk. A trunk group is a logical grouping of trunks to a switch, and a trunk route is a set of trunk groups.

The configuration example in this section uses SS7 and PRI trunks.

The two main scenarios you are likely to follow when setting up the MGC node for call routing are described in Table 3-15.

Table 3-15 Setting Up the MGC Node for Call Routing

If you want to:
Perform these steps:

Create a new configuration

Add all of the trunk groups, one by one, using the instructions in the "Adding Trunk Groups" section.

Add all of the trunks to the configured trunk groups, trunk group by trunk group, using the instructions in the "Adding Trunks" section.

Add all of the route groups, one by one, using the instructions in the "Adding Routes" section.

Build a dial plan using the instructions in the Cisco PGW 2200 Softswitch Release 9 Dial Plan Guide (through Release 9.7).

Modify an existing configuration

Load the existing configuration into the Cisco Voice Services Provisioning Tool:

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

If you are modifying a configuration on an MGC, select File > Import, and specify the configuration you want to import.

Add, modify, or delete trunk groups using the instructions in the "Adding Trunk Groups" section.

Add or delete trunks on a trunk group basis, using the instructions in the "Adding Trunks" section.

Add, modify, or delete route groups using the instructions in the "Adding Routes" section.

Build a dial plan using the instructions in the Cisco PGW 2200 Softswitch Release 9 Dial Plan Guide (through Release 9.7).



Caution SS7 components must be provisioned before you provision the PRI components. When trunk groups are provisioned by the importing of customer trunk group files, all of the existing trunk groups and trunks are deleted. PRI trunk groups and trunks are provisioned by the use of individual MML commands, which do not delete all of the existing trunk groups and trunks. If the PRI components are provisioned before SS7 components, all PRI trunk groups and trunks are deleted.

To configure bearer traffic, use the steps provided in the sections below.

Importing Trunk Groups and Trunks

Adding a Trunk Group Profile

Adding Trunk Groups

Adding Trunks

Adding a CodecString

Adding a BearerCap

Adding an ATMProfile

Adding Routes

Hierarchical View of Provisioned Components

Importing Trunk Groups and Trunks

You can import trunk groups and trunks to make them available to the MGC. Consider importing a trunk group for initial provisioning only. When you import a trunk group, all of the existing trunk groups are replaced by the imported trunk groups, and all existing trunks are deleted.


Tip The trunk file must contain all trunks, also know as Circuit Identification Codes (CICs), in a trunk group.


Perform the following steps to import a trunk group or trunk:


Step 1 Select File > Import. A window similar to the one shown in Figure 3-91 displays.

Figure 3-91 Importing Files

Step 2 Click From File, and In the File type drop-down menu, select the type of file you want to import (see Figure 3-92).

Figure 3-92 Imported File Type

Step 3 Enter the name of the file you want to import. If you do not know the name of the file, click Select. A window similar to the one shown in Figure 3-93 displays.

Figure 3-93 Specify the File to Import

Step 4 Select the file you want to import, and click Open. A window similar to the one shown in Figure 3-92 displays again, and the full path name of the file you selected displays in the file name box.

Step 5 Click OK. The file you selected is imported.


Adding a Trunk Group Profile

A trunk group profile allows you to define a collection of trunk group properties and associate trunk groups with those properties.

Use the following procedure to configure a profile:


Step 1 Select the Traffic radio button in the top portion of the main Cisco VSPT window.

Step 2 Click Profiles in the left pane.

Step 3 Click Add.

Step 4 Enter the name, and click OK. A window similar to the one shown in Figure 3-94 displays.

Figure 3-94 Trunk Group Profile Added

Step 5 To add or modify a profile property, select the profile name in the top pane of the window.

Step 6 Select a property in the name drop-down list, and enter the value.

Step 7 Click Add. The new property and value are displayed in the lower pane of the window.


Adding Trunk Groups

A trunk group is a collection of DS0 circuits arranged so that dialing a single trunk number provides access to the entire trunk group.


Tip For information about importing the trunk group file, see the "Importing Trunk Groups and Trunks" section. For a list of trunk group parameters, see Table 3-16.


Use the following procedure to add a trunk group:


Step 1 Select the Traffic radio button in the top portion of the main Cisco VSPT window.

Step 2 Click Trunk Groups in the left pane.

Step 3 Click Add. A window similar to the one shown in Figure 3-95 displays.

Figure 3-95 Defining a Trunk Group

Step 4 Enter the trunk group number.

Step 5 Enter the Common Language Location Identification (CLLI). This can be up to 11 alphanumerical digits.

Step 6 In the Signaling Service drop-down menu, select the type of signal service.

Step 7 In the Trunk Type drop-down menu, select the type of trunk.

Step 8 In the Queueable Type drop-down menu, indicate whether or not the trunk group can be queued.

Step 9 In the Select Sequence drop-down menu, select the sequence.

Step 10 In the Originating Location Label drop-down menu, select the label.

Step 11 In the Terminating Location Label drop-down menu, select the label.

Step 12 Click the Prop-1 tab. A window similar to the one shown in Figure 3-96 displays.

Figure 3-96 Trunk Group Properties

Step 13 Enter the ring no answer.

Step 14 In the Glare drop-down menu, select Always, Even/Odd, or Never.

Step 15 Enter the COT percentage.

Step 16 In the Satellite drop-down menu, select Yes or No.

Step 17 Enter the numbering plan area.

Step 18 Enter the customer group ID.

Step 19 In the Compression Type drop-down menu, select Mu-law or A-law.

Step 20 In the Echo Canceller Required drop-down menu, select Yes or No.

Step 21 In the External COT drop-down menu, select Loop, Transponder, or 0.

Step 22 Select whether trunks detect fax modem tones, and then select Yes or No.

Step 23 Enter the wait interval for origination SDP Timer.

Step 24 Enter the wait interval for termination SDP Timer.

Step 25 Select Send Address in cgpn, and then select FALSE or TRUE.


Note Additional properties can be configured from the property tabs depending on the signaling service type selected. See Table 3-16 for a list of trunk group parameters.


Step 26 Click OK. A window similar to the one shown in Figure 3-97 displays with the trunk group added.

Figure 3-97 Trunk Group Added


Note After you have added a trunk group, it cannot be deleted it if there are still trunks defined in the trunk group or if there are existing route groups that refer to the trunk group. To maintain the integrity of the data in the traffic configuration branch, you have to first delete all trunks in the trunk group and remove any references from the route groups before you can delete the trunk group.



Trunk Group Properties

Table 3-16 lists the trunk group properties shown on each tab in the Trunk Group Data and Property window, along with their MML name and description. The specific appearance of the window depends on your version of Cisco VSPT. As MML features are added to MGC software, the tabs and properties are expanded.

Table 3-16 Trunk Group Properties Descriptions 

VSPT Parameter Name
MML Parameter Name
Description
TrunkGroup Tab

Trunk Group Number

Name

Unique number (up to seven digits) assigned to each trunk group that is used by route analysis. (The string "tg-" is pre-pended to this number to create the MML name of the trunk group used in components.dat yielding an MML name of no more than 10 characters.)

CLLI

CLLI

Any 11 or fewer alphanumeric characters.

Signaling Service

Signal Service

The MML name of a previously defined SS7, IPFAS, or FAS signaling service associated with or controlling the trunk group.

Trunk Type

Type

Identifies the trunk group type. Values:

TDM_GEN-Used with SS7 signaling services with switch types not equal to 0, 5, 20, 23, or 40.

TDM_ISUP-Used with SS7 signaling services with switch types of 0, 20, 23, or 40.

TDM_CAS-Currently not supported.

TDM_TUP-Used with SS7 signaling services with switch type of 5.

IP-Used with EISUP signaling service.

ATM-Used with VSI path signaling service.

TDM_DPNSS-Used with DPNSS protocol family signaling services

TDM_ PRI-Used with ISDN PRI protocol family signaling services.

TDM_BTNUP-Used with SS7 signaling services with switch type of

5.

IP_SIP-Used for SIP signaling services at the terminating side.

SIP_IN-Used for SIP signaling services at the originating side (only one such trunk group can be configured on each MGC node).

CTI-Used with CTI signaling services.

Switch type values are:

0 = No switch-specific logic 23 = SS7 ANSI

for the signaling path.26 = DPNSS

5 = BTNUP27 = NET5

10 = SS7 Japan29 = QSIG MASTER

17 = 5ESS30 = QSIG SLAVE

20 = SS7 Clear40 = SS7 ITU

22 = NI2.

Queueable Type

QABLE

Determines if queuing is used on the trunk during call processing. Value range: Y for yes or N for no (default).

Select Sequence

selseq

Specifies the trunk selection sequence. The Cisco PGW 2200 Softswitch uses the CICs within a trunk group according to the sequence specified by the SELSEQ value. You can provision this value to reduce the chance of glare when the system selects a trunk.

ASC = Ascending. The system selects the available CICs in ascending order starting from the lowest CIC number (for example, 1, 2, 3 ...).

CASC = Cyclic ascending. The system selects the next available CIC in ascending order based on the most recently selected CIC. For example, if the most recently selected CIC is CIC 5, the system selects CIC 6, even if CIC 1 is available.

CDESC = Cyclic descending. Similar to CASC, but in descending order based on the most recently selected CIC. For example, if the last selected CIC is number 18, the system selects CIC 17, even if CIC 31 is available.

DESC = Descending. Similar to ASC, but in descending order starting from the highest CIC number (for example, 31, 30, 29 ...).

EASC = Even ascending, then odd ascending. The system selects the first available even CIC in ascending order (for example, 2, 4, 6 ...). If no even CIC is available in the trunk group, the system selects the first available odd CIC in ascending order (for example, 1, 3, 5 ...).

EDECS = Even descending, then odd descending. Similar to EASC, but in descending order. The system selects the first available even CIC in descending order (for example, 30, 28, 26 ...). If no even CIC is available in the trunk group, the system selects the first available odd CIC in descending order (for example, 31, 29, 27 ...).

ITU2 = ITU method 2. The system selects the trunk according to the procedure in ITU-T Recommendation Q.764, paragraph 2.9.1.3 Method 2.

continued ....

Select Sequence (continued)

selseq

... continued:

LIDL = Least idle (default). The system selects the least idle (most recently used) CIC.

MIDL = Most idle. The system selects the most idle (least recently used) CIC.

OASC = Odd ascending, then even ascending. The system selects the first available odd CIC in ascending order (for example, 1, 3, 5 ...). If no odd CIC is available in the trunk group, the system selects the first available even CIC in ascending order (for example, 2, 4, 6...).

ODESC = Odd descending, then even descending. Similar to OASC, but in descending order. The system selects the first available odd CIC in descending order (for example, 31, 29, 27 ...). If no odd CIC is available in the trunk group, the system selects the first available even CIC in descending order (for example, 30, 28, 26 ...).

RDM = Random. The system selects a CIC at random.


Caution When the trunk selection sequence (SELSEQ) is set to its default value, LIDL (least idle), there is a risk that the Cisco PGW 2200 Softswitch will select a significant number of temporarily unavailable trunks, which causes calls to fail. This kind of call failure can happen when an overloaded media gateway responds to the Cisco PGW 2200 Softswitch with a temporary MGCP error (400 to 499), or the Cisco PGW 2200 Softswitch does not receive a response from the media gateway in time. We recommend that you set SELSEQ to a value other than LIDL.

Originating Location Label

OrigLabel

This property defines the originating label for the trunk group.

Terminating Location Label

TermLabel

This property inhibit the terminating label for the trunk group

Default

Default

This parameter dictates whether the trunk group is the default IP incoming trunk group of the SIP/EISUP path. The value 1 means this trunk group is the default IP incoming trunk of the SIP/EISUP path.

Profile

Profile

This property indicates the trunk group profile for the trunk group.

Routing Property

Reattempts

Reattempts

Indicates the number of allowed reattempts on this trunk group if congestion prevails. Value range: 0-5.

Queuing

Queuing

Indicates the length of time in milliseconds that queuing is permitted on the trunk group. Value range: 0-120.

Cutthrough

Cutthrough

Indicates the point at which a call is connected. Valid values:

0 = Undefined
1 = Seize - call is through connected a seize, not applicable
2 = ACM - call is through connected at ACM
3 = ANM - call is through connected at ANM

ResIncoming
Perc

ResIncPerc

Percentage of bandwidth reserved for incoming calls. Value range: 0-100.

BearerCap

BearerCap
Name

Defines the bearer capability of a trunk group in the route to which the Cisco PGW 2200 Softswitch can preferentially route calls with a specific bearer capability.

Prop-1 tab

Ring No Answer

RingNoAnswer

Ring no answer. Indicates the time, in seconds, ringing is allowed to occur. Value range: 0 through 255 (default), which is converted to milliseconds.

Glare

GLARE

Glare control. Glare is a collision that occurs when two network nodes simultaneously attempt to reserve the same channel. Values are: 1 (always), 2 (even/odd), or 3 (never) (default).

COT percentage

CotPercentage

Determines the percentage of calls on the trunk upon which a continuity test is performed. Value range: 0 through 100.

Satellite

SatelliteInd

Satellite indicator. Indicates if the trunk is going over a satellite. Values are 0 (no) (default) or 1 (yes).

Numbering Plan Area

Npa

Numbering Plan Area. Indicates the NPA code associated with the incoming trunk group. Value range: 0 (none) (default), or a 3-digit code from 200 through 999.

Customer group ID

CustGrpId

Customer group ID. The ID of the customer associated with this trunk group. Value range: 0 (if not defined) or any 4-character alphanumeric string.

Compression Type

CompressionType

Compression type. Identifies the G.711 compression type used on the trunk. After the fax or modem tone has been detected by the Cisco MGW, select the proper compression type. Values are: 0 (none), 1 (mu-law) (default), 2 (A-law), or 3 (clear channel).

Echo Canceller Required

EchoCanRequired

Echo Canceller Required. Specifies whether to send a modify-connection message (MDCX) for echo control. Enter a value of 0 or 1 for EchoCanRequired on the trunk group or sigpath.

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

External COT

ExtCOT

External continuity test. Indicates the type of COT handling for the specified destination. Values are: 0-no COT, loop (default), or transponder.

Detect Fax Modem Tone

DetectFaxModemTone

Detect Fax modem tone. Indicates if Fax modem tone is to be detected. Used for MGCP connection protocol. Values are: 0 (no tone detection notification) or 1 (request fax or modem tone detection from the Cisco MGW.

Wait OrigSDP Timer

WaitOrigSDPTimer

Wait for originating SDP timer. On H.323 originated calls, the MGC transits the answer message and starts this timer when the originating SDP information has not been received. Value range: 0 to 50 (in seconds).

Wait TermSDP Timer

WaitTermSDPTimer

Wait for terminating SDP timer. On H.323 terminated calls, the MGC transits the answer message and starts this timer when the terminating SDP information has not been received. Value range: 0 to 50 (in seconds).

Send Address in Cgpn

SendAddressnCgpn

Send address in the calling party number. Determines if the CLI digits are sent in the outgoing calling party number parameter. Value is 0 (False) for do not include address digits in calling party number parameter, or 1 (True) (default) for including address digits in calling party number parameter.

Prop-2

Maximum ACL

MaxACL

Maximum automatic congestion level. The MGC indicates its congestion level (if it is greater than 0) in the ISUP release message. Values: 0, 2, or 3 (default).

ACL Duration

ACLDuration-

Automatic congestion level duration. When MGC receives ACL indication from a linked switch, the MGC assumes ACL is in effect for the duration specified (in seconds). Value range: Any value greater than 0 (5 is the default).

ACC Response Control Inhibit

ACCRespCntlInhibit

Automatic congestion control response inhibit. Enables or disables the ACC control procedures based on the ACL value received by MGC from a linked switch. Values are: 0 (default) or 1.

ISUP Transparency Disabled

IsupTransparencyDisabled

ISUP transparency disable function. Permits disabling the ISUP transparency feature for a specified trunk group. Values are: 0 (ISUP transparency enabled), or 1 (ISUP transparency disabled) (default).

AOC Enabled

AOCEnabled

Advice of charge (AOC). Determines whether or not AOC handling is applied to the current call. Values are: 0 (AOC not enabled) (default) or 1 (AOC enabled).

Carrier Screening

CarrierScreening

Carrier screening. Defines whether or not carrier screening and selection is to be applied on the current call (using the Carrier Translation table). Values are: 0 (do not apply screening) (default), or 1 (do apply screening).

Originating Carrier ID

OrigCarrierId

Originating carrier ID. Supports the Carrier Screening capability as handled in the protocol. This property supplies the CarrierID digit string for the trunk group that can be referenced to any CarrierID received in the incoming message. Value range is: 0 through 99999 (00 is the default).

Notify Setup Complete

NotifySetupComplete

Notify setup complete. Used for notifying the Asynchronous Notification task. When the MGC detects that the property NotifySetupComplete is set to true, it then waits for both ChanSeized and ChanNotify on the terminating side before sending ChanSeizeAck to the internal call manager. Values are: 0 (default) or 1.

Package Type

PackageType

Package type. Determines MDL MGCP message handling according to the CAS trunk group package. Value range: any alphabetical string.

Default: BL

ACC Response Category

ACCRespCatName

Automatic congestion control response category name. Specifies the ACC Response Controls listed in the ACC Response Category table. Value range: any character string. Default: default.

Default Carrier ID NatNet ID Plan

DefaultCARIDNatNetIdPlan

Default Carrier Identification national network identification plan. Values are: 0 (NOTUSED) (default),
1 (NATIONAL_NETWORK_ID_NATIONAL CARRIER_ACCESS_CODE),
2 (NATIONAL_NETWORK_ID_PLAN_2_DIGIT),
3 (NATIONAL_NETWORK_ID_PLAN_3_DIGIT), or
4 (NATIONAL_NETWORK_ID_PLAN_4_DIGIT).

Default Originating Line Information

DefaultOLI

Default originating line information. Maps to trunk group property DefaultOLI. Values: 0 (NOTUSED) (default),
1 (OLI_POTS),
2 (OLI_MULTIPARTY_LINE),
3 (OLI_ANI_FAILURE),
4 (OLI_STATION_LEVEL_RATING),
5 (OLI_SPECIAL_OPERATOR_REQ),
6 (OLI_AIOD),
7 (OLI_COIN_DATABASE),
8 (OLI_800_SERVICE_CALL),
9 (OLI_COIN),
10 (OLI_PRISON_INMATE_SERVICE),
11 (OLI_INTERCEPT_BLANK),
12 (OLI_INTERCEPT_TROUBLE),
13 (OLI_INTERCEPT_REGULAR),
14 (OLI_TELCO_OPERATOR_CALL),
15 (OLI_OUTWATS),
16 (OLI_TRS_1),
17 (OLI_TRS_2),
18 (OLI_TRS_3),
19 (OLI_CELLULAR_SVC_1),
20 (OLI_CELLULAR_SVC_2),
21 (OLI_CELLULAR_SVC_ROAMING),
22 (OLI_PRIVATE_PAYSTATIONS),
23 (OLI_ACCESS_FOR_VPN_TYPES_OF_SVC),
24 (OLI_INTERLATA_RESTRICTED),
25 (OLI_TESTCALL),
26 (OLI_TOLLFREE_FROM_PAYSTATIO),
27 (OLI_CUSTOMER_SPECIFIC_1),
28 (OLI_CUSTOMER_SPECIFIC_2),
29 (OLI_INTERLATA_RESTRICTED_HOTEL), or
30 (OLI_INTERLATA_RESTRICTED_COINLESS)

CgpnPresRes

CgpnPresRes

Calling party number restricted Determines if the incoming called number presentation indication is to be overridden. Value range: 0 (False) (default) for leave as-is, or 1 (True) for set to presentation restricted.

Prop-3 tab

Default Charge Number

DefaultCHG

Default charge number. Values are: 1 to 16 digits or NULL. Default: 0.

Default Charge Number NOA

DefaultCHGNOA

Default charge NOA. Values are: 0 (NOTUSED) (default),
1 (CHNOA_ANI_CGSUB_SUB_NUM),
2 (CHNOA_ANI_NOT_AVAIL),
3 (CHNOA_ANI_CGSUB_NAT_NUM),
4 (CHNOA_ANI_CDSUB_SUB_NUM),
5 (CHNOA_ANI_CDSUB_NO_NUM), or
6 (CHNOA_ANI_CDSUB_NAT_NUM)

Default Charge Number NPI

DefaultCHGNPI

Default charge number NPI. Values are: 0 (NOTUSED) (default),
1 (NPI_NONE),
2 (NPI_E164),
3 (NPI_DATA),
4 (NPI_TELEX),
5 (NPI_PNP),
6 (NPI_NATIONAL),
7 (NPI_TELEPHONY),
8 (NPI_MARITIME_MOBILE),
9 (NPI_LAND_MOBILE), or
10 (NPI_ISDN_MOBILE)

Default Directory Number

DefaultDN

Default directory number. This property is needed on the Trunk Group if it is a switched call and on the SigPath if it is a nailed call. Values are: 1 to 14 digits or NULL. Default = 0.

Default Directory Number NOA

Default
DNNOA

Default directory number NOA. Values are
0 (NOTUSED (default))
1 (NOA_NONE)
2 (NOA_UNKNOWN)
3 (NOA_SUBSCRIBER)
4 (NOA_NATIONAL)
5 (NOA_INTERNATIONAL)
6 (NOA_NETWORK)
7 (NOA_MERIDIAN)
8 (NOA_ABBR)
9 (NOA_UNIQUE_3DIG_NAT_NUM), 10 (NOA_ANI)
11 (NOA_NO_ANI_RECD)
12 (NOA_NON_UNIQUE_SUBSCRIBER)
13 (NOA_NON_UNIQUE_NATIONAL)
14 (NOA_NON_UNIQUE_INTERNATIONAL)
15 (NOA_OPRREQ_TREATED)
16 (NOA_OPRREQ_SUBSCRIBER)
17 (NOA_OPRREQ_NATIONAL)
18 (NOA_OPRREQ_INTERNATIONAL)
19 (NOA_OPRREQ_NO_NUM)
20 (NOA_CARRIER_NO_NUM)
21 (NOA_950_CALL)
22 (NOA_TEST_LINE_CODE)
23 (NOA_INT_INBOUND)
24 (NOA_NAT_OR_INTL_CARRIER_ACC_CODE_INC)
25 (NOA_CELL_GLOBAL_ID_GSM)
26 (NOA_CELL_GLOBAL_ID_NMT_900)
27 (NOA_CELL_GLOBAL_ID_NMT_450)
28 (NOA_CELL_GLOBAL_ID_AUTONET)
29 (NOA_PORTED_NUMBER)
30 (NOA_PISN_SPECIFIC_NUMBER)
31 (NOA_UK_SPECIFIC_ADDRESS)
32 (NOA_SPARE), 33 (NOA_MCI_VNET)
34 (NOA_INTERNATIONAL_OPR_TO_OPR_OUTSIDE_WZI)
35 (NOA_INTERNATIONAL_OPR_TO_OPR_INSIDE_WZI)
36 (NOA_DIRECT_TERMINATION_OVERFLOW)
37 (NOA_ISN_EXTENDED_INTERNATIONAL_TERMINATION)
38 (NOA_TRANSFER_ISN_TO_ISN)
39 (NOA_CREDIT_CARD)
40 (NOA_DEFINED_IN_SSUTR)
41 (NOA_DEFINED_IN_SSUTR2)
42 (RESERVED)
43 (NOA_DISCARDED)

Default Directory Number NPI

DefaultDNNPI

Default directory number NPI. Values are: 0 (NOTUSED) (default),
1 (NPI_NONE),
2 (NPI_E164),
3 (NPI_DATA),
4 (NPI_TELEX),
5 (NPI_PNP),
6 (NPI_NATIONAL),
7 (NPI_TELEPHONY),
8 (NPI_MARITIME_MOBILE),
9 (NPI_LAND_MOBILE), or
10 (NPI_ISDN_MOBILE)

Default Directory Presentation Indicator

DefaultDNPres

Default directory presentation indicator. Values are: 0 (NOTUSED) (default),

1 (PRES_NO_INDICATION),
2 (PRES_ALLOWED),
3 (PRES_RESTRICT), or
4 (PRES_UNAVAIL)

Default Directory Screening Indicator

DefaultDNSI

Default directory screening indicator (SI). Values are: 0 (NOTUSED) (default),

200 (SI_NONE),
201 (SI_USER_PROVIDED_NOT_VERIFIED),
202 (SI_USER_PROVIDED_VERIFIED_PASSED),
203 (SI_USER_PROVIDED_VERIFIED_FAILED), or
204 (SI_NETWORK_PROVIDED)

Default Carrier Identifier Network Identifier

DefaultCARIDNetID

Default carrier identifier network identifier. Values are: a 2 to 4 digit string, or NULL (default).

Default Carrier Identifier Network Type

DefaultCARIDNetType

Default carrier identifier network type. Values are: 0 (NOTUSED) (default),
1 (NETWORK_USER_SPECIFIED),
2 (NETWORK_NATIONAL),
3 (NETWORK_INTERNATIONAL), or
4 (NETWORK_CCITT)

Gateway RB Tone Support

GatewayRBToneSupport

Gateway ring back tone support. Indicates the support or non-support of ringback tone application within the gateway that hosts the trunk group and the connection method that is applied. Values are: 0 (No local tone application support) (default),
1 (Local tone application support using MDCX connection method), or
2 (Local tone application support using RQNT connection method)

Note Failure to configure this property correctly may result in calls terminating in the H.323 network failing to have ring back tones applied.

Wait Answer Timer

WaitAnswerTimer

Wait answer timer. This timer is started when the MGC instructs the Media Gateway to apply ring back tone upon the receipt of Alerting. This timer is stopped when the MGC receives the Answer message. Values are: 0 through 300 (in seconds). Default: 65.

Charge Origin

ChargeOrigin

Charge origin. The charge origin value may be defaulted (0) when the charging tariff rates are not origin dependent. The craftperson decides what value of charge origin is to be used, up to a 4-digit integer value. Value range: 0 (default) through 9999.

AInternationalPrefix

AInternationalPrefix

A-number international prefix. Determines the prefix of the outgoing calling number when NOA is set to International. Value range: NULL (default) or a numeric string.

ANationalPrefix

ANationalPrefix

A-number international prefix. Determines the prefix of the outgoing calling number when NOA is set to National. Value range: NULL (default) or a numeric string.

Prop-4

BInternationalPrefix

BInternationalPrefix

B-number international prefix. Determines the prefix for outgoing called numbers when NOA is set to International. Value range: NULL (default) or digit string.

BNationalPrefix

BNationalPrefix

B-number national prefix. Determines the prefix for outgoing called numbers when Nature of Address (NOA) is set to National. Value range: NULL (default) or digit string.

ADigitCCPrefix

ADigitCCPrefix

A-digit country code prefix. Controls functionality that applies a country code prefix to the calling party number before sending the call forward. Values are: 0 (default) or 1, where 0 means disabled and 1 means enabled.

BDigitCCPrefix

BDigitCCPrefix

B-digit country code prefix. Controls functionality that applies a country code prefix to the called party number before sending the call forward. Values are 0 (default) or 1, where 0 means disabled and 1 means enabled.

BDigConnecteditCCrm

BDigitCCrm

Country code remove. Provides a country code digit string to which the called party Number leading digits can be compared, and if matched have those digits removed from the front of the number. This modification is made before sending the call forward. Values are: NULL (default) or null, or a maximum 5-digit string.

CCOrigin

CCOrigin

Country code origin. Provides against the origin trunk group of a call the country code digits, which if needed can be prefixed on a number before sending the call forward. Only required when the property domain is SigPath or LinkSet. Values: NULL (default) or a maximum 5 digit string.

Ta1TimePeriod

Ta1TimePeriod

Ta1 time period. Indicates the value for the time period Ta1, in seconds. Value range: 1 through 180. Default: 20.

Ta2TimePeriod

Ta2TimePeriod

Ta2 time period. Indicates the value for the time period Ta2, in seconds. Value range: 1 through 180. Default: 30.

Ta3TimePeriod

Ta3TimePeriod

Ta3 time period. Indicates the value for the time period Ta3, in seconds. Value range: 1 through 180. Default: 3.

ExpiryWarnToneType

ExpiryWarnToneType

String defining the tone to be applied to warn that the assigned call duration is almost expired. Value range: Any valid MGCP event name. Default: NULL.

ExpiryWarnToneDuration

ExpiryWarnToneDur

Expiry warning tone duration, in seconds. Value range: 1 through 5. Default: 1.

CLISelect

CLISelect

Calling line identification. Determines whether or not the additional calling party number is presented in the incoming IAM. Values are: GENERICNUM (the additional calling party number is presented in the incoming IAM as generic number and the additional calling party number is used as the CLI and is passed to the access network) or CLI (additional calling party number is not presented in the incoming IAM). Default: CLI.

GWDefaultCodecString

GWDefault CodecString

Gateway default codec string. Enables the IOCC-MGCP to send the ordered series of codec choices separated by semicolons. Refer to your gateway documentation for a list of supported codec names. The following values represent some of the more common codec names.

Values: NULL, G.711a, G.711u, G.729, G.729a, and G.729b

Default: NULL

AllowH323Hairpin

AllowH323Hairpin

Allow H.323 hairpinning. Allows the MGC to interconnect H.323-originated and H.323-terminated calls by the HSI component. Valid values: 0 (not allowed) or 1 (allowed). Default: 0.

EISUP link to H323 Platform

H323AdjunctLink

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

Note Removed from trunk group properties and added to SigPath properties in software Release 9.4(1).

Incoming Trkgrp Fax support

FAXSupport

FAX support. Indicates if T.38 FAX calls are supported on the trunk group. This property must be enabled on the incoming and outgoing trunk groups for T.38 fax calls to be successfully routed. Valid values: 0 (no FAX support) or 1 (T.38 FAX support). Default: 0.

Prop-5 tab

Subscribe Notify Support

SubscribeNotifySupport

SIP Subscribe/Notify methods. Determines if the SIP Subscribe/Notify methods for solicited notification of SIP DTMF digits is enabled or disabled. Valid Values: 0 = Subscribe/Notify methods disabled or 1 = Subscribe/Notify methods enabled.

Default: 0

This property is added in software Release 9.4(1).

Unsolicited Notify Method

UnsolicitedNotifyMethod

Unsolicited Notify method. Determines if the unsolicited Notify method for unsolicited notification of SIP DTMF digit is enabled or disabled. Valid Values: 0 = Unsolicited Notify method disabled, 1 = Unsolicited Notify method enabled, 2 = Unsolicited Info method enabled.

Default: 0

This property is added in software Release 9.4(1).

Option 2 is added in software Release 9.7(3) and later

MinEvent Subscribe Duration

MinEventSubscribeDuration

Minimum event subscribe duration. Defines the minimum duration (in milliseconds) for which a telephony event can be subscribed. Value range: 40 through 3600.

Default: 40

This property is added in software Release 9.4(1).

Max Subscription Duration

MaxSubscriptionDuration

Maximum subscription duration. Defines the maximum duration (in seconds) for which a subscription can be made. Value range: 0 through 3600.

Default: 0

This property is added in software Release 9.4(1).

PopulateSDPInfo
InCDR

PopulateSDP
InfoInCDR

Enables or disables the extraction of SDP information from SDP. Extracted SDP information is placed in call detail records (CDRs). Valid values: 0 (Disable SDP information extraction) or 1 (Enable SDP information extraction). Default: 0.

OD32Digit
Support

OD32Digit
Support

OD 32 Digit Support. Allows 32 digit and overdecadic digit support for the ANSI, Q.761, and Q.767 protocol variants for the ANSI, SS7-ITU, SS7-China, SS7-Japan, and SS7-UK protocol families. Values are 0 (disabled) and 1 (enabled).

This property is added in software Release 9.4(1).

Anumnormalise

Anumnormalise

A Number Normalise. Anumnormalise indicates that calling party number (A-number) normalization is appropriate based on the NOA value and the leading digits of the A-number. Leading digits 0 or 00 are the only accepted digits. Valid values: 0 (disabled) or 1 (enabled).

Default: 0

When this property is provisioned, any normalization action is applied to the A-number and the following numbers, if present (stored internally):

GN_AcgPn—Generic number parameter containing additional calling party number

Redirecting number (or all redirecting numbers if there is more than one)

OCN—Original called number

The actions apply only if the NOA of the number is set to UNKNOWN or SUBSCRIBER. If if is, check the initial digits of the number to see if they are 0 or 00. The following applies:

If the leading digit is 0, remove the 0 and set the NOA to NATIONAL.

If the leading digits are 00, remove both 0s and set the NOA to INTERNATIONAL.

This property is added in software Release 9.4(1) and is a European feature only.

Bnumnormalise

Bnumnormalise

B Number Normalise. Bnumnormalise indicates that called party number (B-number) normalization is appropriate based on the NOA value and the leading digits of the B-number. Leading digits 0 or 00 are the only accepted digits. Valid values: 0 (disabled) or 1 (enabled).

Default: 0

The actions apply only if the NOA of the number is set to UNKNOWN or SUBSCRIBER. If it is, check the initial digits of the number to see if they are 0 or 00. The following applies:

If the leading digit is 0, remove the 0 and set the NOA to NATIONAL.

If the leading digits are 00, remove both 0s and set the NOA to INTERNATIONAL.

This property is added in software Release 9.4(1) and is a European feature only.

GtdCapTypeProp

GtdCapType
Prop

GTD Cap Type Properties. The Cisco PGW 2200 Softswitch uses this parameter as a pointer to the subset of GTD parameters that the user desires to support. Values are t0 (no GTD support) (default) or any GTD parameter string from 1 to 20 characters.

GtdMsgFmt

GtdMsgFmt

GTD Message Format. Indicates the GTD message format mode. The format can be only compact mode. Compact mode is the short format and the field names are not passed in the GTD parameter string. Valid value: c (compact) or v (verbose). Default: c

IsupTransEarly
BackwardDisabled

IsupTransEarlyBackwardDisabled

ISUP Transparency Early Backward Disabled. Indicates if the egress Cisco PGW 2200 Softswitch is to send an end-to-end message, called Early Backward Call Setup message, immediately after receiving the call setup message with GTD information about the outgoing protocol variant. Valid values: 0 (enable) or 1 (disable). Default: 1

sipMimeBodySupport

sipMimeBodySupport

Determines if SIP-T or SIP-GTD special data processing is supported on a trunk group. Valid Values: 0-None, 1-SIP-T supported, or 2-SIP-GTD supported.

Default Value: 0

This property is added in software Release 9.4(1).

Enable IP Screening

EnableIPScreening

Enables the incoming trunk group to select a dial plan based on the IP address, source ID, and CLI prefix tables. Valid values: 0 (no dial plan lookup) or 1 (require dial plan lookup).

Default Value: 0

This property is added in software Release 9.4(1).

SIP IP Source

SipIPSource

Indicates for the Cisco PGW 2200 Softswitch to use the IP packet source address or IP address from Session Description Protocol (SDP) in the INVITE message to make the dial plan selection for SIP calls. Valid values: 0 (use the IP packet source address) or 1 (use the IP address from SDP).

Default Value: 0

This property is added in software Release 9.4(1).

Prop-6 tab

Default PN

DefaultPN

Enables the incoming trunk group to have a default PN if the incoming call does not have one; overdecadic digits are supported. Valid values: overdecadic digit string of 1 to 20 characters. Default Value: NULL

This property is added in software Release 9.4(1).

Default Presentation Number NOA

DefaultPN
NOA

Enables the default Presentation Number NOA value. Valid values: 0 through 43. Values are
0 (NOT USED)— default
1 (NOA_NONE)
2 (NOA_UNKNOWN)
3 (NOA_SUBSCRIBER)
4 (NOA_NATIONAL)
5 (NOA_INTERNATIONAL)
6 (NOA_NETWORK)
7 (NOA_MERIDIAN)
8 (NOA_ABBR)
9 (NOA_UNIQUE_3DIG_NAT_NUM)
10 (NOA_ANI)
11 (NOA_NO_ANI_RECD)
12 (NOA_NON_UNIQUE_SUBSCRIBER)
13 (NOA_NON_UNIQUE_NATIONAL)
14 (NOA_NON_UNIQUE_INTERNATIONAL)
15 (NOA_OPRREQ_TREATED)
16 (NOA_OPRREQ_SUBSCRIBER)
17 (NOA_OPRREQ_NATIONAL)
18 (NOA_OPRREQ_INTERNATIONAL)
19 (NOA_OPRREQ_NO_NUM)
20 (NOA_CARRIER_NO_NUM)
21 (NOA_950_CALL)
22 (NOA_TEST_LINE_CODE)
23 (NOA_INT_INBOUND)
24 (NOA_NAT_OR_INTL_CARRIER_ACC_CODE_INC)
25 (NOA_CELL_GLOBAL_ID_GSM)
26 (NOA_CELL_GLOBAL_ID_NMT_900)
27 (NOA_CELL_GLOBAL_ID_NMT_450)
28 (NOA_CELL_GLOBAL_ID_AUTONET)
29 (NOA_PORTED_NUMBER)
30 (NOA_PISN_SPECIFIC_NUMBER)
31 (NOA_UK_SPECIFIC_ADDRESS)
32 (NOA_SPARE)
33 (NOA_MCI_VNET)
34 (NOA_INTERNATIONAL_OPR_TO_OPR_OUTSIDE_WZI)
35 (NOA_INTERNATIONAL_OPR_TO_OPR_INSIDE_WZI)
36 (NOA_DIRECT_TERMINATION_OVERFLOW)
37 (NOA_ISN_EXTENDED_INTERNATIONAL_TERMINATION)
38 (NOA_TRANSFER_ISN_TO_ISN)
39 (NOA_CREDIT_CARD)
40 (NOA_DEFINED_IN_SSUTR)
41 (NOA_DEFINED_IN_SSUTR2)
42 (RESERVED)
43 (NOA_DISCARDED)

Default Presentation Number NPI

DefaultPNNPI

Displays the default Presentation Number NPI value. Valid values: 0 through 10.

0 (NOTUSED)
1 (NPI_NONE)
2 (NPI_E164)
3 (NPI_DATA)
4 (NPI_TELEX)
5 (NPI_PNP)
6 (NPI_NATIONAL)
7 (NPI_TELEPHONY)
8 (NPI_MARITIME_MOBILE)
9 (NPI_LAND_MOBILE)
10 (NPI_ISDN_MOBILE)

Default value: 0.

This property is added in software Release 9.4(1).

Default Presentation Number Indicator

DefaultPNPres

Displays the Default Presentation Number Presentation Indicator value. Valid values: 0 through 4.

0 (NOTUSED)
1 (PRES_NO_INDICATION)
2 (PRES_ALLOWED)
3 (PRES_RESTRICT)
4 (PRES_UNAVAIL)

Default value: 0.

This property is added in software Release 9.4(1).

CallForwardRerouteDisabled

CallForwardReroute
Disabled

Disables Call Forwarding rerouting for all calls on the Cisco PGW 2200 Softswitch. Valid values: 0 (reroute enabled) or 1 (reroute disabled).

Default value: 0.

This property is added in software Release 9.4(1).

CustomerVPNOnNetTblNum

CustomerVPNOnNetTblNum

Allows assignment of a VPN on-net profile table index to a particular trunk group. Value range: 1 through 8.

1—Completely transparent operation is required for the call to complete.
2—The Cisco PGW 2200 Softswitch can use feature transparency preferred by a nontransparent destination if necessary to complete the call.
3—The Cisco PGW 2200 Softswitch can use feature transparency preferred by a nontransparent destination if necessary to complete the call.
4—The Cisco PGW 2200 Softswitch can use feature transparency preferred by a nontransparent destination if necessary to complete the call.
5—The Cisco PGW 2200 Softswitch removed the attempted feature from the onward-routed call and informs the indicator of the change.
6—The Cisco PGW 2200 Softswitch releases a feature call.
7—The Cisco PGW 2200 Softswitch releases a feature call.
8—The Cisco PGW 2200 Softswitch removes the feature string and continues.

Default value: 5.

This property is added in software Release 9.4(1). The range changed to 1-8 and the default changed to 5 in software Release 9.6(1).

CustomerVPNid

CustomerVPN
id

Assigns a VPN ID to a trunk group or system. Valid values: 1 through 8 numeric character string.

Default value: 00000000

This property is added in software Release 9.4(1).

CustomerVPNOffNetTblNum

CustomerVPNOffNet
TblNum

Allows assignment of a VPN off-net profile table index to a particular trunk group. Value range: 1 through 8.

1—Completely transparent operation is required for the call to complete.
2—The Cisco PGW 2200 Softswitch can use feature transparency preferred by a nontransparent destination if necessary to complete the call.
3—The Cisco PGW 2200 Softswitch can use feature transparency preferred by a nontransparent destination if necessary to complete the call.
4—The Cisco PGW 2200 Softswitch can use feature transparency preferred by a nontransparent destination if necessary to complete the call.
5—The Cisco PGW 2200 Softswitch removed the attempted feature from the onward-routed call and informs the indicator of the change.
6—The Cisco PGW 2200 Softswitch releases a feature call.
7—The Cisco PGW 2200 Softswitch releases a feature call.
8—The Cisco PGW 2200 Softswitch removes the feature string and continues.

Default value: 0.

This property is added in software Release 9.4(1). The range changed to 1-8 and the default changed to 5 in software Release 9.6(1)

Feature
Transparency
Disabled

Feature
Transparency
Disabled

Disables QSIG feature transparency for all calls on the Cisco PGW 2200 Softswitch. Valid values: 0 (Feature Transparency enabled) or 1 (Feature Transparency disabled).

Default value: 0

This property is added in software Release 9.4(1).

SdpXmitToH323
Trigger

SdpXmitTo
H323Trigger

SDP transmit to H.323 trigger. Indicates the point in a call when the Cisco PGW 2200 Softswitch sends the SDP from the terminating call leg to the H.323 Signaling Interface (HSI). Value range: 0 through 3.

0 = terminating seizure
1 = Address complete
2 = Alerting or inband information available
3 = Answer

This property is added in software Release 9.4(1).

GWDefaultATM
Profile

GWDefault
ATMProfile

Defines an initial list of profiles that the Cisco PGW 2200 Softswitch uses to control ATM profile negotiation between two MGWs.

When setting up an ATM voice connection, the originating and terminating MGWs communicate via the Cisco PGW 2200 Softswitch. The MGWs must negotiate to establish what ATM profiles to use for the connection.

When you set the GWDefaultATMProfile properties, the Cisco PGW 2200 Softswitch sends the list of supported profiles to the MGW via MGCP. The MGW then combines these values with its list of supported profiles to produce a list of profiles supported by both the MGW and the Cisco PGW 2200 Softswitch. The MGW sends the profile list to the terminating MGW via SDP. Thus, the GWDefaultATMProfile values control the profiles that the MGWs can negotiate for an ATM voice connection.

Valid values:

A list of profile names separated by semicolons such as <Profile1>;<Profile2>;<ProfileN>.

NULL

Default value: NULL.

This property is added in software Release 9.5(2).

PlayAnnouncement Id

PlayAnnouncement

Enables, on a per trunk group basis, the playing of an early announcement. This property can either contain an integer announcement identity, or, if it is set to 0 (default), the announcement function is considered disabled at the trunk group level. Valid values: any integer value.

Default value: 0.

This property is added in software Release 9.5(2).

AtmConnection
Type

Atm
Connection
Type

Populates the connection type parameter (ct:) in local connection option parameters. This property is read for both originating and terminating legs of all ATM-switched calls. Valid values: 1 (AAL1), 2 (AAL1_SDT), 3 (AAL1_UDT), 4 (AAL2), 5 (AAL 3/4), or 6 (AAL5).

Default value: 4 (AAL2)

This property is added in software Release 9.5(2).

BTechPrefix

BTechPrefix

Provides a digit string that the Cisco PGW 2200 Softswitch uses as a Tech Prefix to the B-number when sending the call forward. Valid values: any integer.string from one digit (minimum) through 16 (maximum) digits. The Tech Prefix uses overdecadic digits B and C and maps them to * and # respectively. The Tech Prefix and a separator are appended to the beginning of the B-number.

This property is added in software Release 9.5(2).

Prop-7 tab

Loop Avoidance Support

LoopAvoidance
Support

Enables support of the loop avoidance feature in DPNSS protocol. Valid values: 0 (disable) or 1 (enable).

Default value: 0

This property is added in software Release 9.5(2).

Loop Avoidance Counter

LoopAvoidance
Counter

Enables support of the loop avoidance feature in DPNSS protocol. Valid values: 0 (disable) or 1 (enable).

Default value: 0

This property is added in software Release 9.5(2).

MWI Off String

MwiStringOFF

Enables support for a Message Waiting Indication (MWI) string in a DPNSS protocol message. The message instructs a particular extension to extinguish its MWI LED (also known as the MWI lamp).

Valid values: Digit string from 1 through 32 digits.

Default value: NULL.

Note Ensure that the digit string provisioned is the same MWI string provisioned in Cisco CallManager.

This property is added in software Release 9.5(2).

MWI On String

MwiStringON

Enables support for a Message Waiting Indication (MWI) string in a DPNSS protocol message. The message instructs a particular extension to light its MWI LED (also known as the MWI lamp).

Valid values: Digit string from 1 through 32 digits.

Default value: NULL.

Note Ensure that the digit string provisioned is the same MWI string provisioned in Cisco CallManager.

This property is added in software Release 9.5(2).

InhibitIncomingCallingNameDisplay

InhibitIncomingCallingNameDisplay

Enables or disables the inhibiting of the incoming calling name display in DPNSS and EISUP (HSI) protocols. Valid values: 0 (enable) or 1 (disable).

Default value: 0.

This property is added in software Release 9.5(2).

InhibitOutgoingCallingNameDisplay

InhibitOutgoingCallingNameDisplay

Enables or disables the inhibiting of the outgoing calling name display in DPNSS and EISUP (HSI) protocols. Valid values: 0 (enable) or 1 (disable).

Default value: 0.

This property is added in software Release 9.5(2).

InhibitIncomingConnectedNameDisplay

InhibitIncomingConnectedNameDisplay

Enables or disables the inhibiting of the incoming connected name display in DPNSS and EISUP (HSI) protocols. Valid values: 0 (enable) or 1 (disable).

Default value: 0.

This property is added in software Release 9.5(2).

InhibitIncomingConnectedNumberDisplay

InhibitIncomingConnectedNumberDisplay

Enables or disables the support of incoming connected number display in DPNSS and EISUP (HSI) protocols. Valid values: 1 (inhibit incoming connected number display) or 0 (enable incoming connected number display).

Default value: 0

This property is added in software Release 9.5(2).

AOC Default Tariff Id

AOCDefaultTariffId

Allows configuration of the default tariff ID to be applied when AOCInvokeType is configured for all calls (that is, AOCInvokeType = 2). Value range: 1 (default) through 9999.

Default value: 1

This property is added in software Release 9.5(2).

AOC Invoke Type

AOCInvokeType

Allows configuration of whether or not the AOC Supplementary services are applicable on a per call basis or for all calls. Values: 1 (on a per call basis, the default) or 2 (for all calls).

Default value: 1

This property is added in software Release 9.5(2).

MidCallCPInterval

MidCallCPInterval

Enables or disables mid-call checkpointing. When it is enabled, you can specify the interval (in minutes) between checkpointing events in the connected state. Valid values: 0 (disabled) (default) through 60.

Default value: 0

This property is added in software Release 9.5(2).

CliSelectionFor
CodeOfPractice3

CliSelection
ForCodeOf
Practice3

Provisions, on a per trunk group basis, the level of CLI selection that the Cisco PGW 2200 Softswitch uses when sending the calling line identities (such as Calling Party Number or Generic Number parameter) to the succeeding exchange. Valid range: 0 through 2.

Valid values:

0—No specific CLI selection (default).

1—Single CLI selection, which sends only the CLI.

2—Dual CLI selection, which sends the CLI; or the CLI and the PN.

Default value: 0

This property is added in software Release 9.5(2).

InhibitOutgoingConnectedNameDisplay

InhibitOutgoingConnectedNameDisplay

Enables or disables inhibit outgoing connected name display in DPNSS and EISUP (HSI) protocols. Valid values: 0 (enable) or 1 (disable).

Default value: 0

This property is added in software Release 9.5(2).

InhibitOutgoingConnectedNumberDisplay

InhibitOutgoingConnectedNumberDisplay

Enables or disables inhibit outgoing connected number display in DPNSS and EISUP (HSI) protocols. Valid values: 0 (enable) or 1 (disable).

Default value: 0

This property is added in software Release 9.5(2).

H323 Destination

H323Destination

Identifies the primary and alternative IP Address and Port of the H323 destination.

Valid Values:

The primary and the alternative IP address and port of the H323 destination, in the format xxx.xxx.xxx.xxx[:port][xxx.xxx.xxx.xxx:port]

Default value:

NULL

This value indicates the Non-RAS feature is inactive on this trunk group.

Dynamically reconfigurable: Yes

This property is added in software Release 9.7(3).

ADigitCCrm

ADigitCCrm

Provides a country code digit string to which leading digits of CgPN, GN_ACgPN, RDN, OCN and PN can be compared. If the digits match, those digits are removed from the front of that number. The NOA code of that number is set to National. This modification is made before the call is sent forward. Values are NULL (default) or null, or a maximum 5-digit string. Valid values: 1 through 99999.

Default: NULL

This property is added in software Release 9.6(1).

Prop-8 tab

Own Routing Number

OwnRouting
Number

Defines the routing or network number of the PGW in a PBX network that requires Route Optimization or Path Replacement capabilities. The presence or absence of this property indicates if this service is enabled or disabled for a signalling path.

Valid range: Alphanumeric string up to 32 characters.

Default: NULL

This property was added in software Release 9.6(1).

QSIG Tunnel Variant

QSIGTunnelVariant

Controls the QSIG tunnel capability across outbound EISUP (HSI) interfaces and specifies which protocol variant is used.

Valid Values:

0—QSIG tunneling is disabled

1—QSIG tunneling is enabled

Default Value: 0

Disable QSIG Release Method

DisableQSIGReleaseMethod

Indicates the QSIG release method. An H.225 signaling connection can be released with a single Release Complete message instead of a three-stage QSIG release sequence. This is only applicable to release procedures initiated by the PGW 2200. The PGW accepts receipt of either type of release method.

Valid Values:

0 —Normal QSIG release is enabled for QSIG tunneling

1 —Normal QSIG release is disabled for QSIG tunneling

Default Value: 0

DPNSS RO RoutingNumber Length

DpnssRORoutingNumberLength

For DPNSS-QSIG PR ROO interworking, the DPNSS RO routing number and call reference are concatenated and in QSIG they are separate fields. An indication of where the divide point is between the fields is an optional parameter in the DPNSS specification. It is therefore necessary to provide a configurable definition of how to split these two fields.

Valid values: 2-10

Default value: 4

Enable CCBS Path Reservation

EnableCCBSpathReservation

Allows configuration of the Path Reservation option for each QSIG destination. In the case of EISUP, this is valid for HSI destinations only.

Valid values:

0—CCBS with Path Reservation is disabled

1—CCBS with Path Reservation is enabled

Default value: 0

TrunkGroupTag
Label

TrunkGroup
TagLabel

This property gives the name of the trunk group from which a call comes.

Value: A string of 1-63 characters.

Default: Null

Dynamically Reconfigurable: Yes

Note This property does not support some special characters like #, >, and white space. MML does not allow you to use these characters for the TrunkGroupTagLabel.

TrunkGrpTagLabel
TransEnable

TrunkGrpTagLabelTransEnable

Indicates how the PGW handles the ingress trunk group tag label (if present) in the outgoing SIP INVITE message. This property is dynamically reconfigurable.

Values:

0: The PGW does not send the ingress trunk group tag label

1: The PGW sends the ingress trunk group tag label in the x-route-tag parameter

2: The PGW sends the ingress trunk group tag label in the tsp parameter

Default: 0

Dynamically Reconfigurable: Yes

H248Gateway
ReserveValue

H248GatewayReserveValue

Note This property is deleted in Release 9.7S23P23 and later.

This property allows H.248 to send ADD commands with the ReserveValue on or off to indicate whether the media gateway (MG) should reverse resource or not. This property applies only to the originating MG; for the terminating side, the ReserveValue is always off.

Valid values (boolean):

0—Do not reserve resource

1—Reserve resource

Default value: 0

Dynamically reconfigurable: yes

This property is removed since Cisco VSPT Release 2.7(3) patch 5.

MapRNMethod

MapRNMethod

Determines the mappings between the EISUP or ISUP RN and the SIP message headers or EISUP RN.

Valid Values:

0—Do not map the RN to the SIP header. Do not map the RN to the EISUP RN parameter.

1—Map the RN to the Diversion header. Map the RN to the EISUP RN parameter.

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

Default Value: 1

Itp Action Request

ItpActionRequest

The ItpActionRequest property indicates that the PGW should send a customized SIP invite to the ITP to return the location of a mobile subscriber. Setting this property to map-app indicates that the PGW should send a customized SIP invite to the ITP to return the location of a mobile subscriber. The customized SIP invite causes the ITP to send a MAP query to the service provider HLR for the mobile subscriber's current mobile station roaming number (MSRN). The PGW then routes the call to the closest Gateway MSC based upon the new MSRN.

If the PGW is unable to optimize the call routing based on the MSRN, it continues to route calls based on using the mobile subscriber's MSISDN (telephone number). The PGW routes calls based on an MSISDN using cause analysis.

Values: Null or map-app

Default: Null

TOverlap

TOverlap

Set to 1 to enable overlap signaling for call termination to this traffic path. Values are 0 or 1.

Default: 0

TMinDigits

TMinDigits

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

Default: 0

TMaxDigits

TMaxDigits

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

Default: 24

Prop-9 tab

OOverlap

OOverlap

Set to 1 to enable overlap signaling for call origination from this traffic path. Value range: 0 through system maximum.

Default: 0

OMinDigits

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

OMaxDigits

OMaxDigits

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

Default: 24

OverlapDigitTime

OverlapDigitTime

Overlap interdigit timer. The time to wait for the rest of the digits.

Value range: 0 through 60, in seconds.

Default: 6

DTMF Capability

DtmfCap

Defines the DTMF capability of the egress trunk group.

Valid values:

0—Ignore DTMF capability

1—RFC 2833 DTMF capability

2—Out of band DTMF capability

Default Value: 0

MapCLItoSipHeader

MapCLItoSipHeader

Determines the mappings from the ISUP calling party number to the outgoing SIP message.

Valid Values:

0—The calling party number is put in the outgoing SIP From header if number presentation is allowed. If the calling party number presentation is restricted, then the SIP outgoing From header is also controlled by the cgpnInclude property.

If cgpnInclude = 0, and the SIP network is untrusted, the From header has SIP URI as: Anonymous <sip:Anonymous@anonymous.invalid>

If cgpnInclude = 1, and the SIP network is trusted, and honors the anonymous setting by not passing the CLI to the SIP end point, the From header has URI as Anonymous <sip:CGPN@PGW_HOST>

1—The calling party number is mapped to the remote party ID, with screen and privacy values. If an additional calling party number is present in the generic number, it is mapped to the SIP From header.

2—Map the calling party number to the Remote-Party-ID header only when the calling party number presentation is allowed. For handling the additional calling party number in the generic number, the operation is the same as for a value of 1.

3—The calling party number is mapped to the P-Asserted ID, with privacy header value ID, if necessary. If an additional calling party number is present in the generic number, it is mapped to the SIP From header.

Note If the calling party number presentation is allowed, there is no privacy header. If the calling party number presentation is restricted, there is a privacy header with a value ID.

4—Map the calling party number to the P-Asserted ID header only when the calling party number presentation is allowed. For handling the additional calling party number in the generic number, the operation is the same as for a value of 3.

Default Value: 0

Note In Release 9.6(1), mapclitosipheader is a sigpath property only. In Release 9.7(3), it is a sigpath and a trunk group property.

InhibitSipFrom
Mapping

InhibitSipFrom
Mapping

Determines the mapping from the incoming SIP message to the ISUP CLI.

If the remote party ID or P-Asserted-ID header is present and the InhibitSipFromMapping property = 1, then disable mapping the SIP From header to the generic number. If the remote party ID or P-Asserted-ID header is not present and the InhibitSipFromMapping property = 1, then disable mapping the SIP From header to the calling party number.

Valid Values:

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

1— Ignore the From header, map PAID/RPID E164 number to CgPN.

2—Ignore the PAID/RPID, map the E164 number in username in From header to CgPN.

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

4—If the PAID/RPID E164 number is present, map the PAID/RPID to CgPN, map the E164 number in username in From header to GN (additional CgPN). If the PAID/RPID E164 number is not present, ignore the From header.

Note The 4 value is only available in Release 9.7(3).

Default Value: 0

ReferRedirecting
NOA

Refer
Redirecting
NOA

NOA value of redirection number in ITU SS7 REL message for blind transfer by SIP REFER. Use internal NOA value.

Value range:

1—NOA_NONE

2—NOA_UNKNOWN

3—NOA_SUBSCRIBER

4—NOA_NATIONAL

5—NOA_INTERNATIONAL

ReferRedirecting
Ind

Refer
RedirectingInd

Redirecting indicator of Redirection Information in ITU SS7 REL message for blind transfer by SIP REFER.

Value range:

0—No redirection

1—Call rerouted

2—Call rerouted, all redirection information presentation restricted

3—Call diverted

4—Call diverted, all redirection information presentation restricted

5—Call rerouted, redirection number presentation restricted

6—Call diversion, redirection number presentation restricted

SipDtmfContentType

SipDtmfContentType

This property determines the Content-Type header and the SDP content of INFO requests PGW sends out.

Valid values:

0 = Sets the Content-Type header to audio/telephone-event

1 = Sets the Content-Type header to application/dtmf-relay

Default value: 0

RejectOfferForResourcePending

RejectOfferForResourcePending

Specifies how the Cisco PGW 2200 Softswitch treats new offers when the resource is temporarily unavailable.

Valid values:

0—Buffer the new offer

1—Reject the new offer

Default value: 1

IsdnNSF

IsdnNSF

Indicates the network specific facilities parameter for ISDN PRI.

Specify an integer from 0-256.

0-255: Directly mapping to 0x00-0xFF in the outgoing message.

256: No NSF in the outgoing message.

Default: 256.

This property is added in software release 9.7(3) S22P22.

MidCallCodecSelect

MidCallCodecSelect

Enable/disable codec selection for Mid-Call. It works only on the originating

side. Valid values: 0—disable, 1—enable.

UseGtdCalledPartyNumber

UseGtdCalledPartyNumber

Enables the Cisco PGW 2200 Softswitch to use embedded calledPartyNumber field of GTD in the invite message instead of url/number contained in the request line. Valid values: 0—disable, 1—enable.

SIP-1 tab

MGC Domain Name

MGCdomain

MGC domain name. Indicates the MGC domain name used in SIP messages. Value range: Any valid domain name or NULL (default).

MGC SIP Version

MGCSipVersion

MGC SIP version. The version of SIP protocol supported by the MGC. Value range: Any valid SIP version.

Default: 2.0

Note For MGC software earlier than Release 9.7, set this value to SIP/2.0.

Local SIP Port

LocalPort

Local port. Indicates the UDP port used by MGC to send or receive SIP messages. Valid range: any valid port number greater than 1024. Default: 5060.

Invite Timer T1

InviteTimerT1

Invite T1 timer. Indicates the T1 timer (in milliseconds) for the INVITE message, as specified for SIP. Value range: any value greater than 0. Default: 1000

Gen Timer T1

GenTimerT1

Generic timer T1. The T1 timer value (in milliseconds) for SIP messages other than INVITE. Value range: any value greater than 0. Default: 500.

Gen Timer T2

GenTimerT2

Generic timer T2. The T2 timer value (in milliseconds) for SIP messages other than INVITE. Value range: any value greater than 0. Default: 4000.

Maximum Redirection Count

MaxRedirectCnt

Maximum redirect count. Indicates the maximum number of SIP message redirections allowed. Value range: any value greater than 0.

Default: 5

Support 183

Support183

Support 183. Indicates if the MGC supports 183 response code. Valid values: 0 (not supported), 3 (supported) (default), or 4 (always send).

SIP-2 tab

From Field

FromField

From field. Displays the name used in the SIP "From" field when the calling party number is marked private. Value range: any alphanumeric string. Default: anonymous.

In Session Timer

InSessionTimer

In session timer. Indicates the maximum session time (in milliseconds) allowed for a SIP call that originated by the MGC. Maps to trunk group property InSessionTimer. This value may require being increased to 1800000 to reduce performance impact. Value range: any value greater than 0. Default: 1800000.

Out Session Timer

OutSessionTimer

Out session timer. The maximum session time (in milliseconds) allowed for a SIP call terminated by the MGC. This value may require being increased to reduce performance impact. Valid range: any value greater than 0. Default: 1800000.

Hold Timer

HoldTimer

Hold timer. Indicates the maximum time length (in milliseconds) a SIP call can be put on hold. Value range: any value greater than 0. Default: 300000.

Expires Timer

ExpiresTimer

Expires timer. The timer value (in milliseconds) used in the Expire header of SIP messages. Value range: any value greater than 0. Default: 60000.

Support Reliable 100

SupportReliable100

Support reliable 100. Indicates if the MGC support reliable100 response code. Values are: TRUE (default) or FALSE.

Retry After Timer

RetryAfterTimer

Retry after timer. Indicates the time (in milliseconds) the MGC waits before successfully retrying a SIP call. Value range: any value greater than 0. Default: 90000.

Max. Forwards

MaxForwards

Maximum forwards. Indicates the maximum number of SIP forwards allowed. Value range: any value greater than 0. Default: 70.

Mid Call Service CustID

MidCallServiceCustID

This is a 4-character, alphanumeric string that indicates which dial plan is used for mid-call service analysis. If this property value is 0000, no mid-call service is supported. Valid range: 0000 or any 4-character alphanumeric string.

Valid Values: 0000 or any 4-character alphanumeric string.

Default: 0000

Invite Attempts

InviteAttempts

Specifies the transmission times for SIP INVITE request. Value range: from 1 to 15. Default: 7.

NonInvite Req Attempts

NonInviteReqAttempts

Specifies the transmission times for SIP Non-INVITE request.Value range: from 1 to 15. Default: 11.

Response Attempts

ResponseAttempts

Specifies the transmission times for SIP response.Value range: from 1 to 15. Default: 11.

Retrans Method

RetransMethod

Specifies the re-transmission mode for SIP messages. Value: 1(exponential),2(linear). Default: 1.

Invite Wait Timer

InviteWaitTimer

Specifies the timer value (in milliseconds) for SIP waiting for final response of INVITE request.Value range: from 10000 to 500000. Default: 200000.

SIP Ingress Routing Control

sipIngressRoutingControl

Maps to trunk group property sipIngressRoutingControl. Defines the preferred SIP header used for initial routing decisions. Values are: 1 - Explicit Route header; 2 - Request Line ; 3: To: header. Default: 1.

SIP Egress Routing Control

sipEgressRoutingControl

Maps to trunk group property sipEgressRoutingControl. Defines the preferred SIP header used for initial routing decisions during sending of the initial INVITE. Values are: 1 - 5. Default: 0.

respectSipUriUserParm

respectSipUriUserParm

Determines whether or not respect user=phone in p-asserted-id and remote-party-id header. Values: 0 (no) or 1 (yes). Default: 0.


Adding Trunks

Use the following procedure to add trunks to a trunk group:


Step 1 Click Trunks in the left pane of the main Cisco VSPT window. A window similar to the one shown in Figure 3-98 displays.

Figure 3-98 Trunk Window

Step 2 Click Add. A window similar to the one shown in Figure 3-99 displays.

Figure 3-99 Adding a Trunk

Step 3 In the Trunk Group Number drop-down menu, select the number of the trunk groups you are configuring.

Step 4 In the Media Gateway Name drop-down menu, select the gateway (external node). This step might not be required if the gateway can be determined by trunk group signaling.

Step 5 Enter the MCGP Domain.

Step 6 Enter the first trunk CIC Number.

Step 7 Select DS Format (optional).

Step 8 In the Slot Number drop-down menu, select the slot number.

Step 9 In the Subunit Number drop-down menu, select the subunit where you want to add trunks.

Step 10 Enter the DS1 number.

Step 11 Enter the first DS0 number.

Step 12 Enter the DS1 type. The trunk type is displayed.

Step 13 Select SS7, PRI FAS, or PRI NFAS and enter the appropriate properties:

SS7—Enter the number of trunk members.

PRI FAS or PRI NFAS—Enter the number of trunk members and the number of the DS1 with the D channel.


Note For PRI, one channel is reserved for signaling (D channel). For FAS, it is channel 24. For NFAS, it is channel 24, but on only one DS1.


Step 14 Enter the number of trunk members in the trunk group.

Step 15 Click More to add more trunks to other trunk groups.

Step 16 When you are done adding trunks to trunk groups, click Finish. You are asked if you want to overwrite the trunks in the existing trunk groups, and a window similar to the one shown in Figure 3-100 displays.

Figure 3-100 Trunks Added


Deleting Trunks from a Trunk Group

Use the following procedure to delete individual trunks from a trunk group:


Step 1 In the Trunk window (similar to the one shown in Figure 3-100) select from the Trunk Group Number drop-down menu the trunk group where you want to delete trunks.

Step 2 Select the individual trunks you want to delete:

To delete all the trunks in a trunk group, click Delete All.

To select a range of trunks, click on the first trunk in the range, hold down the Shift key, and click the last trunk in the range.

To select nonsequential trunks, hold down the Control key, and click each trunk.

Step 3 When you have finished selecting trunks, click Delete to delete the selected trunks. A window similar to the one shown in Figure 3-101.

Figure 3-101 Trunks Deleted


Adding a CodecString

Use the following procedure to add a CodecString:


Step 1 Click CodecString in the left pane of the main Cisco VSPT window.

Step 2 Click Add. A window similar to the one shown in Figure 3-101 displays.

Figure 3-102 Adding a CodecString

Step 3 Enter a name.

Step 4 Enter the Codec String.

Step 5 Click Finish. A window similar to the one shown in Figure 3-103 displays.

Figure 3-103 CodecString Added


Adding a BearerCap

Use the following procedure to add a BearerCap:


Step 1 Click BearerCap in the left pane of the main Cisco VSPT window.

Step 2 Click Add. A window similar to the one shown in Figure 3-104 displays.

Figure 3-104 Adding a BearerCap

Step 3 Enter a name.

Step 4 Enter the Bearer Cap.

Step 5 Click Finish. A window similar to the one shown in Figure 3-105 displays.

Figure 3-105 BearerCap Added


Adding an ATMProfile

Use the following procedure to add an ATMProfile:


Step 1 Click ATMProfile in the left pane of the main Cisco VSPT window.

Step 2 Click Add. A window similar to the one shown in Figure Figure 3-106 displays.

Figure 3-106 Adding an ATMProfile

Step 3 Enter a name.

Step 4 Enter the profile value.

Step 5 Click OK. A window similar to the one shown in Figure Figure 3-107 displays.

Figure 3-107 ATMProfile Added


Adding Routes

A route is a collection of trunk groups associated with the same set of dialed digits. Use the following procedure to add a route and associate a trunk group with the route added:


Step 1 Click Routing > Routes in the left pane of the main Cisco VSPT window.

Step 2 Click Add. A window similar to the one shown in Figure 3-108 displays.

Figure 3-108 Adding a Route

Step 3 Enter a route name.

Step 4 Select whether the Weighted Trunk Group is on or off.

Step 5 To associate the route with a previously defined trunk group, select a group in the Available box, and click Select >>.


Tip To select more than one trunk group, hold down the Control key while selecting each group.


Step 6 When you are done adding trunk groups, click OK. A window similar to the one shown in Figure 3-109 displays with the routes added.

Figure 3-109 Route Group Added


Adding Route Lists

A route list is a collection of routes that go to the same endpoint. Use the following procedure to add route lists:


Step 1 Click Route Lists in the left pane of the main Cisco VSPT window.

Step 2 Click Add. A window similar to the one shown in Figure 3-110 displays.

Figure 3-110 Adding Route Lists

Step 3 Enter a route group name.

Step 4 To associate the route with a route group, select a route in the Available box.

Step 5 Click Select >>.


Tip To select more than one route group, hold down the Control key while selecting each group.


Step 6 When you are done adding routes to the route group, click OK. A window similar to the one shown in Figure 3-111 displays.


Hierarchical View of Provisioned Components

The results of the provisioning session you completed are visible in the hierarchical tree in the left pane of the main Cisco VSPT window. You can expand the branches to view individual components (see Figure 3-111).

Figure 3-111 Hierarchical Tree of Components

Performing an Integrity Check

When provisioning is complete, you can perform an integrity check to prevent possible configuration errors. The integrity check involves examining the following:

Integrity of MGC signaling configuration

Traffic against MGC configuration

Dial plan results

Each integrity check is explained in more detail in the following subsections.

Checking Integrity for an MGC Signaling Configuration

When you perform an integrity check for an MGC signaling configuration, the Cisco VSPT does the following:

Checks that the hostname is specified for an MGC

Checks that login/passwords are specified for an MGC

Checks that MGC ipaddrs are specified

Checks that if MGC failover is specified, the failover IPs are specified

Checks that the MGX hostname is specified

Checks that MGX logins and passwords are specified

Checks the MGX IPaddrs

For EXTNODES where it refers to an MGX, checks PeerAddrs on IPLNK to ensure that they are addresses on the specified MGX

For IPFAS IPLNKS:

Ensures that SigSlot/SigPort are specified

Checks SigSlots and SigPorts on the MGX to ensure that they are valid as specified on the MGX

Ensures that MGC ports and MGX ports match on the IPLNK

Checks that all IPLNKs under a single IPFASPATH map to the same port number


Note The number of IPFAS sessions utilizing a given port is displayed because some IPLNKs might use different port IDs.


Checking Traffic Against an MGC Configuration

When you perform an integrity check of traffic against an MGC configuration, the Cisco VSPT does the following:

When D channels are defined as FAS and NFAS PRI in the trunk group or trunk section, VSPT verifies that there are corresponding IPFASPATH signaling services.

Checks if there are any defined IPFASPATH signaling services defining a D channel but no corresponding trunk group/trunk in the traffic information with a corresponding NFAS or FAS PRI.

Checks that signaling services defined for trunk groups exist in the configuration

For information about an integrity check of dial plan results, see the Cisco PGW 2200 Softswitch Release 9 Dial Plan Guide (through Release 9.7).

Use the following procedure to perform an integrity check of your configuration:


Step 1 Select Tools > Integrity Check on the main Cisco VSPT menu bar. A window similar to the one shown in Figure 3-112 displays.

Figure 3-112 Integrity Check

Step 2 Indicate the tests you want to run, and click Start.

When the tests are finished, a window similar to the one shown in Figure 3-113 displays with the results of the integrity checks performed.

Figure 3-113 Integrity Check Results


Viewing Generated MML Commands

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

Figure 3-114 First Generated MML Window

Deploying a New Configuration

When you finish defining a configuration, you must deploy that configuration to the MGC. A new configuration should not be deployed during times of peak load on the MGC.

The new configuration can be deployed completely or in parts (incremental deployment). Deploying incrementally allows you to verify each component type configuration before proceeding to the next component deployment.

If you want to delete a component and plan to reuse the component name, first delete the component, deploy the session, and verify that the component name has been deleted before reusing the name.

Use the following procedure to deploy a new configuration:


Step 1 Select Tools > Deploy from the main Cisco VSPT menu. A window similar to the one shown in Figure 3-115 displays.

Figure 3-115 Deploying a Configuration

Step 2 Enter the configuration name on the destination MGC.

Step 3 To incrementally deploy a configuration component type, click Advanced. A window similar to the one shown in Figure 3-116 displays.

Figure 3-116 Incremental Deployment Component Selector

Step 4 Select one or more component types to deploy, and click OK.

Step 5 Indicate how you want to deploy the configuration:

If you want to send the configuration to the MGC but not activate it, select the radio button Send Configuration to MGC Only.

If you want to send the configuration to the MGC and activate it, select the radio button Send and Activate Configuration.

If you have a continuous-service configuration with two MGC hosts, select the radio button Send, Activate and Synchronize failover. The configuration is saved on the active host and copied to the standby host. You must restart the standby server after reconfiguration to apply changes.

Step 6 Select the gateways you want to deploy, if applicable.

Step 7 Click OK. A window similar to the one shown in Figure 3-117 displays, showing the status, as the current provisioning session is deployed.

Figure 3-117 Deployment Progress


Note In a continuous-service configuration, the XECfgParm.dat file on each machine must be configured. If you experience problems, verify that the XECfgParm.dat files on both machines are correct by following the instructions in Chapter 2, "Installing Cisco Media Gateway Controller Software," in the Cisco Media Gateway Controller Software Installation and Configuration (Release 9.7).



Backup and Restore

The Cisco VSPT backup and restore tool allows a user to create, modify, and delete scheduled backups and restores on a hourly, daily, weekly, or monthly basis, or on demand. Backup and restore activities can be performed on any of the following devices that have been configured for the MGC:

MGC Host—Active configuration

HSI—Active configuration

CAT6509—Configuration and image on flash

CAT5500—Configuration and image on flash

CAT2900XL—Running-config and image on flash

ITPL2600—Active configuration

BAMS P3—Active configuration

The backup and restore tool also provides the status of each activity and generates user-viewable status logs.


Note This tool operates in coordination with the MGC server operating system and can be used by only one UNIX login. The login is specified during the installation process


Schedule a Backup or Restore

Use the following procedure to open the Cisco VSPT backup and restore tool and to schedule an activity:


Step 1 Select Tools > Backup and Restore on the main Cisco VSPT menu bar. A window similar to the one shown in Figure 3-118 displays:

Figure 3-118 Backup and Restore Utility

Step 2 Click the component for which you want to schedule a backup or restore. The following example shows a backup for the MGC. A window similar to the one shown in Figure 3-119 displays.

Figure 3-119 Scheduling a Backup or Restore


Note If you want to perform a restore, a backup file must already be created and available on the MGC.


Step 3 To schedule a backup or restore, click the component you want to back up or restore in the left pane of the main backup and restore tool window, and click Add. A window similar to the one shown in Figure 3-120 displays:

Figure 3-120 Schedule an Activity


Note Available fields vary depending on the component selected.


Step 4 Select the action you want to perform in the Activity field. Valid choices include backup and restore.

Step 5 Enter the IP address of the MGC.

Step 6 Enter the MGC login and password.

Step 7 Enter a name for the backup file.

Step 8 Enter the IP address of the TFTP server.

Step 9 Enter the TFTP login and password.

Step 10 Specify whether or not to use verbose log mode. Verbose mode records all commands issued by the Cisco VSPT and any system responses.

Step 11 Specify whether or not to use ssh connect.

Step 12 Select the schedule type. Valid choices include

Monthly

Daily

Hourly

Weekly

Now

Later

Step 13 Select the hour and minute when the backup is to begin.

Step 14 Click OK. The backup activity is scheduled, and a window similar to the one shown in Figure 3-121 displays.

Figure 3-121 Display Activity Schedule

After the backup is complete, the status of the activity becomes available immediately, and the backup file with the name specified is available for use with the Cisco VSPT to perform a restore.


Check Status of Backup or Restore

The Cisco VSPT generates status logs that provide information about each scheduled activity. The status log displays the following information for the activity:

Date and time

Success or failure

File name on the TFTP server

Directory of configuration files

Image file name

If a user has specified verbose log mode, the status log also displays the sequence of commands issued by the Cisco VSPT and any system responses.

Use the following procedure to check the status of a backup or restore activity:


Step 1 Click the device that has been backed up or restored in the left pane of the backup and restore tool window, and click the Status tab in the right pane.

Step 2 Click the backup or restore for which you want information.

Step 3 Select the appropriate button for the action you want to perform. Choices are:

Show status

Acknowledge

Clear


Provisioning the Cisco Billing and Measurements Server

The Cisco BAMS provides enhanced billing and measurement functions corresponding to those found in a traditional class 4 tandem switch. The Cisco BAMS server collects, formats, and stores billing and measurement data from the MGC. The data can then be processed by a billing system and other measurement collection and reporting systems. Cisco BAMS runs on a standalone server designed to interface with the MGC.

.Figure 3-122 provides an overview of the Cisco BAMS components and their relationship to the MGC.

Figure 3-122 Cisco BAMS Overview

Use the Cisco VSPT to create, copy, modify, and deploy a configuration for the BAMS server. The Cisco BAMS provisioning session can exist as a standalone provisioning application using MML.

The VSPT performs the following tasks when you are configuring the Cisco BAMS:

Generates an MML batch file either from scratch or based on a preexisting configuration

Imports configuration information from a host and exports it to the host

Deploys the current configuration to a host

Supports incremental deployment

Displays the current MML batch file

Imports the TrunkGroup file from the MGC host to keep trunk group information synchronized

Performs an integrity check to ensure that the current configuration check is valid

The Cisco VSPT provisions a Cisco BAMS by using the following:

General provisioning

Defines country codes

Defines map types

Defines tollfree prefixes

Zone provisioning

Creates zones in the Zone_Information for separate rating zones

Assigns NPA-NXX prefixes to appropriate zones

For each From/To Zone pair, define the appropriate rating type for that zone pair

Defines rating exceptions in the Rate-Exc table

Trunk group provisioning

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

Defines SigPath table for a Dial configuration, because Dial configurations have no trunk groups, routing files, or dial plans. Map SigpathID/Bearer Channel Numbers to Trunk Group Number/Member Numbers.

Measurements provisioning—Configure thresholding alarms by means of the Threshold Crossing Alarms table (TCA-TBL).

The following tags for BAMS 3.0 are available:

Other

ALM-PARMS

NODE-PARMS

POLL

SKIPCDB

SKIPCDE

P01FILTER

SWITCHINFO

BIN1110

System

MSC-MASK

MSC-THRES

SYS-ALM-PARMS

For information on provisioning these tags, see the Cisco Media Gateway Controller Software Release 9 Billing Interface Guide. For more details on which tags are fully supported, see the documentation for your release of Cisco BAMS.

Starting a Cisco BAMS Provisioning Session

Use the following procedure to start a Cisco VSPT BAMS provisioning session:


Step 1 Start and log in to the Cisco VSPT.

Step 2 Select File > Open on the menu bar to open an existing configuration, and go to Step 4. If you want to start a new configuration, go to the next step. For more information, see the Cisco Voice Services Provisioning Tool User's Guide for the software release you are using.

Step 3 Select Tools > BAMS Config on the menu bar. A window similar to the one shown in Figure 3-123 displays.

Figure 3-123 Cisco BAMS Configuration Window

Step 4 Select File > New from the menu bar.

Step 5 Enter a name for the provisioning session you are creating, and click OK. A window similar to the one shown in Figure 3-124 displays.

Figure 3-124 New Configuration Wizard

Step 6 If you want to import an existing configuration from a Cisco BAMS, select the Import from BAMS radio button. Enter the host name, login, password, and the configuration you want to import. If you do not know the name of the configuration, click Select, select the configuration you want, and click OK.

If you want to manually configure the Cisco BAMS, select the Perform manual configuration radio button, and click OK. A window similar to the one shown in Figure 3-125 displays.

Figure 3-125 Cisco BAMS Configuration

Step 7 Enter a BAMS IP address in the BAMS Hostname field.

Step 8 Enter a Cisco BAMS login ID and password.

Step 9 Optionally, enter the network addresses (IP Addr: 1 and IP Addr: 2) in dotted notation; for example, 172.16.145.3.

Step 10 Click Modify, and begin the Cisco BAMS provisioning.


Cisco BAMS Server Configuration

This section provides directions for using the Cisco VSPT to configure a Cisco BAMS server. The Cisco VSPT performs the following procedures:

Provisioning General BAMS Information

Provisioning Zones

Provisioning Trunk Group Information

Provisioning Measurements

Provisioning Other

Provisioning System


Note For more information on Cisco BAMS parameter definitions and values, see the Cisco Billing and Measurements Server User's Guide for the Cisco BAMS release you are using.


Provisioning General BAMS Information

Provisioning general Cisco BAMS information includes defining country codes, map types, and tollfree prefixes. Use the following procedure to provision general Cisco BAMS information:


Step 1 Click the icon next to General in the left pane of the BAMS Configuration window to expand the hierarchical tree.

Step 2 Click Country Codes. A window similar to the one shown in Figure 3-126 displays.

Figure 3-126 Cisco BAMS Configuration, Country Codes

Step 3 Click Add. A window similar to the one shown in Figure 3-127 displays.

Figure 3-127 Add Country Code

Step 4 Enter the country code and country name, and click OK. A window similar to the one shown in Figure 3-128 displays.

Figure 3-128 Country Code Added

Step 5 Click Maptypes. A window similar to the one shown in Figure 3-129 displays.

Figure 3-129 Cisco BAMS Configuration, Maptype

Step 6 Click Get Default. A window similar to the one shown in Figure 3-130 displays.

Figure 3-130 Maptype Information Added

Step 7 Click Tollfree. A window similar to the one shown in Figure 3-131displays.

Figure 3-131 Cisco BAMS Configuration, Tollfree

Step 8 Click Get Default. A window similar to the one shown in Figure 3-132 displays.

Figure 3-132 Tollfree Information Added

Step 9 If you want to add more toll-free prefixes, click Add.

Step 10 Enter the toll-free code, and click OK. Repeat Step 9 and Step 10 for each toll-free prefix you want to configure for the Cisco BAMS.


Provisioning Zones


Note If your MGC system does not need BAF output, proceed to the "Provisioning Measurements" section.


Zoning provides a mechanism for differentiating between rating types. Each supported NPANXX combination must be a member of a zone.

Use the following procedure to provision zones:


Step 1 Click the icon next to Zones in the left pane of the BAMS Configuration window to expand the hierarchical tree.

Step 2 Click Identification. A window similar to the one shown in Figure 3-133 displays.

Figure 3-133 Cisco BAMS Configuration, Identification

Step 3 Click Add. A window similar to the one shown in Figure 3-134 displays.

Figure 3-134 Add Zone Information

Step 4 Enter the zone number and description, and click OK. A window similar to the one shown in Figure 3-135 displays.

Figure 3-135 Zone Identification Added

Step 5 Click Membership. A window similar to the one shown in Figure 3-136 displays.

Figure 3-136 Cisco BAMS Configuration, Membership

Step 6 Click Add. A window similar to the one shown in Figure 3-137 displays.

Figure 3-137 Add Npanxx

Step 7 Enter the 6-digit NPANXX numbers. You can enter several numbers by separating them with commas, for example, 123456,345678,567890. You can obtain A/Bdig numbers from the MGC by clicking Look up. A window displaying the dial plans defined on the MGC displays.

Step 8 Select a dial plan, and click OK. A window displaying all A/Bdig numbers displays.

Step 9 Select one or more, and click OK.

Step 10 A window similar to the one shown in Figure 3-137 redisplays. Enter the LATA, and select the zone.

Step 11 Click OK. A window similar to the one shown in Figure 3-138 displays.

Figure 3-138 Membership Information Added

Step 12 Click Relationships. A window similar to the one shown in Figure 3-139 displays.

Figure 3-139 Cisco BAMS Configuration, Relationships

Step 13 Click Add. A window similar to the one shown in Figure 3-140 displays.

Figure 3-140 Add Rating Type

Step 14 Select the origination zone, termination zone, and rate type. Indicate whether or not the relationship is bidirectional. If you select bidirectional, two entries are added to the table.

Step 15 Click OK. A window similar to the one shown in Figure 3-141 displays.

Figure 3-141 Rating Type Information Added

Step 16 Click Exceptions. A window similar to the one shown in Figure 3-142 displays.

Figure 3-142 Cisco BAMS Configuration, Exceptions

Step 17 Click Add. A window similar to the one shown in Figure 3-143 displays.

Figure 3-143 Add RateExc

Step 18 Select the origination NPANxx, termination NPANxx, and rate type. Indicate whether or not the exception is bidirectional.

Step 19 Click OK. A window similar to the one shown in Figure 3-144 displays.

Figure 3-144 Exceptions Added


Provisioning Trunk Group Information

Provisioning trunk group information includes

Defining trunk groups that map to trunk groups on the MGC

Specifying default origination and termination NPAs and the number of circuits in the trunk group

Defining a SigPath table for dial configurations

Use the following procedure to provision trunk group information:


Step 1 Click the icon next to Trunk Group Info in the left pane of the BAMS Configuration window to expand the hierarchical tree.

Step 2 Click Trunk Group. A window similar to the one shown in Figure 3-145 displays.

Figure 3-145 Cisco BAMS Configuration, Trunk Groups

Step 3 To import trunk groups from the MGC, click Import, and then click OK at the confirmation prompt.

If you previously defined individual trunk groups, a message displays warning that they will be removed. If you did not previously define individual trunk groups, this message does not display.

Step 4 Click OK. All trunk groups on the MGC display on the trunk group window.

Step 5 To add individual trunk groups, click Add. A window similar to the one shown in Figure 3-146 displays.

Figure 3-146 Add Trunkgrp

Step 6 Enter the trunk group name, select the connection type, and enter the origination NPA, termination NPA, circuits, and prefix.

Step 7 Click OK. A window similar to the one shown in Figure 3-147 displays.

Figure 3-147 Trunk Group Added

Step 8 Click Sigpath. A window similar to the one shown in Figure 3-148 displays.

Figure 3-148 Cisco BAMS Configuration, Sigpath

Step 9 Add a Sigpath if the MGC is nailed up. You can import from the MGC by clicking Import.

Step 10 To add a Sigpath, click Add. A window similar to the one shown in Figure 3-149 displays.

Figure 3-149 Add Sigpath Set

Step 11 Enter the Sigpath ID in hexadecimal, select the trunk group number, and click OK. A window similar to the one shown in Figure 3-150 displays.

Figure 3-150 Sigpath Added


Provisioning Measurements

Cisco BAMS generates and maintains measurements and performance indicators. It maintains a history of traffic statistics on a network. Each measurement represents an accumulation of activity that took place during a specific interval.

Use the following procedure to provision measurement types and properties:


Step 1 Click the icon next to Measurements in the left pane of the BAMS Configuration window to expand the hierarchical tree.

Step 2 Click Thresholds A window similar to the one shown in Figure 3-151 displays.

Figure 3-151 Cisco BAMS Configuration, Thresholds

Step 3 You can set thresholds for the item displayed in the drop-down menu next to VSCID/TRK/[IC]. Select a value from the drop-down menu next to the threshold you want to change. When you have finished setting thresholds, click Modify.

Step 4 To add an item to the drop-down menu next to VSCID/TRK/[IC], click Add. A window similar to the one shown in Figure 3-152 displays.

Figure 3-152 Add TcaTbl

Step 5 Enter the VSCID, select the trunk group, and enter the carrier ID.

Step 6 Cisco BAMS generates and maintains measurements and performance indicators. It maintains a history of traffic statistics on a network. Each measurement represents an accumulation of activity that took place during a specific interval.

Step 7 Click OK. The item added is now accessible in the drop-down menu next to VSCID/TRK/[IC].


After the Cisco BAMS server is provisioned, you must deploy the new configuration. See the Cisco Voice Services Provisioning Tool User's Guide for the software release you are using for complete instructions.

Provisioning Other

Provisioning other Cisco BAMS information includes information for provisioning Tag ID parameters for the following tags:

ALM-PARMS

NODE-PARMS

POLL

SKIPCDB

SKIPCDE

P01FILTER

SWITCHINFO

BIN1110


Note For more information on provisioning Cisco BAMS Tag ID parameter definitions and values, see the Cisco Billing and Measurements Server User's Guide at http://www.cisco.com/en/US/products/sw/voicesw/ps522/products_user_guide_list.html.


Provisioning ALM-PARMS

Use the following procedure to provision Cisco BAMS alarm parameter information:


Step 1 Click the icon next to Other in the left pane of the main BAMS Configuration window to expand the hierarchical tree.

Step 2 Click ALM-PARMS. A window similar to the one shown in Figure 3-153 displays.

Figure 3-153 Cisco BAMS Configuration, ALM-PARMS

Step 3 Enter a value for Maxlines (1 through 99999) indicating the maximum number of lines in a log file.

Step 4 Select the Message forward level value (0 through 6) by clicking the desired item displayed in the drop-down menu.

Step 5 Select the Message discovery level value (0 through 6) by clicking the desired item displayed in the drop-down menu.

Step 6 Click Modify. The BAMS configuration for the ALM-PARMS is set.


Provisioning NODE-PARMS

Use the following procedure to provision Cisco BAMS node parameter information:


Step 1 Click the icon next to Other in the left pane of the BAMS Configuration window to expand the hierarchical tree.

Step 2 Click NODE-PARMS. A window similar to the one shown in Figure 3-154 displays.

Figure 3-154 Cisco BAMS Configuration, NODE-PARMS

Step 3 Select the desired value from the drop-down menu for each node parameter you wish to set.

Step 4 Click Modify. The BAMS configuration for the NODE-PARMS is set.


Provisioning POLL

Use the following procedure to provision Cisco BAMS poll parameter information:


Step 1 Click the icon next to Other in the left pane of the BAMS Configuration window to expand the hierarchical tree.

Step 2 Click POLL. A window similar to the one shown in Figure 3-155 displays.

Figure 3-155 Cisco BAMS Configuration, POLL

Step 3 Select the desired value from the drop-down menu for each node parameter you wish to set.

Step 4 Click Modify. The BAMS configuration for the POLL parameter is set.


Provisioning SKIPCDB

Use the following procedure to provision Cisco BAMS skip call data block (CDB) parameter information:


Step 1 Click the icon next to Other in the left pane of the BAMS Configuration window to expand the hierarchical tree.

Step 2 Click SKIPCDB.

Step 3 Click Add. A window similar to the one shown in Figure 3-156 displays.

Figure 3-156 Adding the SKIPCDB Code

Step 4 Enter the desired identifier value in the dialog box for the new CDB being created by the MGC for which Cisco BAMS is to skip processing.

Step 5 Click OK. A window similar to the one shown in Figure Figure 3-157 displays.

Figure 3-157 Cisco BAMS Configuration, SKIPCDB


Provisioning SKIPCDE

Use the following procedure to provision Cisco BAMS skip call data element (CDE) parameter information:


Step 1 Click the icon next to Other in the left pane of the BAMS Configuration window to expand the hierarchical tree.

Step 2 Click SKIPCDE.

Step 3 Click Add. A window similar to the one shown in Figure 3-158 displays.

Figure 3-158 Adding the SKIPCDE Code

Step 4 Enter the desired identifier value in the dialog box for the new CDE being created by the MGC for which Cisco BAMS is to skip processing.

Step 5 Click OK. A window similar to the one shown in Figure 3-159 displays.

Figure 3-159 Cisco BAMS Configuration, SKIPCDE


Provisioning P01FILTER

Use the following procedure to provision Cisco BAMS P01Filter parameter information:


Step 1 Click the icon next to Other in the left pane of the BAMS Configuration window to expand the hierarchical tree.

Step 2 Click P01Filter. A window similar to the one shown in Figure 3-160 displays.

Figure 3-160 BAMS Configuration, P01Filter

Step 3 In the Answered drop-down menu, select Set(1), Filter(0), or Ignore.

Step 4 In the No Answer drop-down menu, select Set(1), Filter(0), or Ignore.

Step 5 In the Busy drop-down menu, select Set(1), Filter(0), or Ignore.

Step 6 In the Other drop-down menu, select Set(1), Filter(0), or Ignore.

Step 7 Click Modify. The BAMS configuration for the P01Filter is set.


Provisioning SWITCHINFO

Use the following procedure to provision the Cisco BAMS switch information parameters:


Step 1 Click the icon next to Other in the left pane of the BAMS Configuration window to expand the hierarchical tree.

Step 2 Click SWITCHINFO. A window similar to the one shown in Figure 3-161 displays.

Figure 3-161 Cisco BAMS Configuration, SWITCHINFO

Step 3 Enter the switch information value in the dialog box for the switch you are using.

Step 4 Click Modify. The BAMS configuration for the SWITCHINFO is set.


Provisioning BIN1110

Use the following procedure to provision BAMS BIN1110 information parameters:


Step 1 Click the icon next to Other in the left pane of the BAMS Configuration window to expand the hierarchical tree.

Step 2 Click BIN1110. A window similar to the one shown in Figure 3-162 displays.

Figure 3-162 Cisco BAMS Configuration, BIN1110

Step 3 In the Enable 1070 CDB Output drop-down menu, select disable or enable.

Step 4 In the Enable 1060 CDB Output drop-down menu, select disable or enable.

Step 5 Enter the select File Suffix name.

Step 6 Click Modify. The BAMS configuration for the BIN1110 is set.


Provisioning System

Provisioning system Cisco BAMS information includes information for provisioning Tag ID parameters for the following tags:

MSC-PARMS

MSC-THRES

SYS-ALM-PARMS

MSC-PARMS tag ID is used to update the Mass Storage Control (MSC) Parameters table. This table maintains definitions of conditions that generate alarms or events, based on parameters such as file type, size, and age.

MSC-THRES tag ID is used to update the Mass Storage Thresholds table. This table maintains the sytem-level MSC thresholds that determine when the MSC task generates alarms based on the disk-capacity thresholds, and when it begins and stops deleting specific types of files to free up disk space.

ALM-PARMs tag ID is used to update the Alarm Parameters table. The maxlines field is used to set the size of the system log (syslog) file. The default value is 10, 000 lines. When the maxlines threshold is surpassed, BAMS begins deleting lines from the syslog, starting with the oldest entries. The msgdisclvl field is to set the level (for example, minor, major, critical) of alarms written to the syslog. The msgfwdlvl field to set the level (for example, critical) of alarms forwarded to a network management platform.

Provisioning MSC-PARMS

Use the Mass Storage Control (MSC) Parameters (Parms) tag ID to update the MSC-PARMS table. This table maintains definitions of conditions that generate alarms or events based on parameters such as file type, size, and age.

Use the following procedure to provision Cisco BAMS MSC parameter information:


Step 1 Click the icon next to System in the left pane of the BAMS Configuration window to expand the hierarchical tree.

Step 2 Click MSC-PARMS. A window similar to the one shown in Figure 3-163 displays.

Figure 3-163 Cisco BAMS Configuration, MSC-PARMS

Step 3 Click the Add button. A window simialar to the one in Figure 3-164 displays.

Step 4 Enter the desired MSC-PARMS values in the dialog box.

Figure 3-164 Adding MSC-PARMS

Step 5 Click OK.

Step 6 When you have finished entering the desired parameter value, click Add.


Provisioning MSC-THRES

Use the Mass Storage Control Thresholds (MSC-THRES) tag ID to update the MSC-THRES table. This table maintains the system-level MSC thresholds that determine when the MSC task generates alarms based on disk-capacity, and when it starts and stops deleting specific file types to free up disk space.

Use the following procedure to provision Cisco BAMS MSC threshold parameter information:


Step 1 Click the icon next to System in the left pane of the BAMS Configuration window to expand the hierarchical tree.

Step 2 Click MSC-THRES. A window similar to the one shown in Figure 3-165 displays.

Figure 3-165 Cisco BAMS Configuration, MSC-THRES

Step 3 Enter the desired MSC-THRES value in the dialog box.

Step 4 Click Modify. The BAMS configuration for the MSC-THRES is set.


Provisioning SYS-ALM-PARMS

Use the Alarm Parameters (ALM-PARMS) tag ID to update the SYS-ALM-PARMS table. Use the maxlines field to set the size of the system log (syslog) file. The default value is 10,000 lines. When the maxlines threshold is surpassed, the Cisco BAMS begins deleting lines from the syslog, starting with the oldest entries.

Use the msgdisclvl field to set the level (for example, minor, major, critical) of alarms written to the syslog. Use the msgfwdlvl field to set the level (for example, critical) of alarms forwarded to a network management platform.

Use the following procedure to provision the Cisco BAMS system alarm parameter information:


Step 1 Click the icon next to System in the left pane of the BAMS Configuration window to expand the hierarchical tree.

Step 2 Click SYS-ALM-PARMS. A window similar to the one shown in Figure 3-166 displays.

Figure 3-166 Cisco BAMS Configuration, SYS-ALM-PARMS

Step 3 Enter the desired SYS-ALM-PARMS value in the dialog box.

Step 4 Enter a value for Maxlines (1 through 99999), which indicates the maximum number of lines in a log file.

Step 5 Select the Message forward level value (0 through 6) by clicking the desired item displayed in the drop-down menu.

Step 6 Select the Message discovery level value (0 through 6) by clicking the desired item displayed in the drop-down menu.

Step 7 Click Modify. The BAMS configuration for the SYS-ALM-PARMS is set.