Table Of Contents

Provisioning Manager

Overview

Accessing the Provisioning Management Window

Provisioning Management Window Components

File Menu

Browse Tree Menu

Find Option

Reset Option

Refresh Option

Template Menu

Load Template Option

Save Template Option

Table of Contents Pane

Tree View Pane

Network Tab

Mgmt System Tab

Configuration Listing Pane

Listing Button

Refresh Button

Add Button

View Button

Modify Button

Delete Button

Job Status Pane

Refresh Button

View Button

Delete Button

Status and Messages Pane

Error Reporting

Configuration Management

RLM Signaling Path Configuration

GTD Configuration

Carrier Configuration

Trunk Group Configuration

Voice Port Configuration

H.323 Voice Class Configuration

IVR/Voice XML Configuration

DNIS Map Configuration

Fax Configuration

AAA Voice Class Configuration

Call Accounting Template Configuration

Voice Parameters Configuration

NTP Configuration

Security Server Group Configuration

Security Server End Point Configuration

AAA Configuration

Interface Configuration

SNMP Configuration

HSRP Configuration

Access Control List Configuration

Adding a Managed Resource

Adding a Managed Resource (Regional Administrator - Unauthorized Region)

Adding a Managed Resource (Network Operator - Unauthorized Region)

Adding a Managed Resource (Non-administrative User)

Modifying a Managed Resource

Modifying a Managed Resource (Regional Administrator - Unauthorized Region)

Modifying a Managed Resource (Network Operator - Unauthorized Region)

Modifying a Managed Resource (Non-administrative User)

Removing a Managed Resource

Removing a Managed Resource (Regional Administrator - Unauthorized Region)

Removing a Managed Resource (Network Operator - Unauthorized Region)

Removing a Managed Resource (Non-administrative User)

Saving and Loading a Configuration Parameter Template

Provisioning Manager

---

This chapter describes how to use the Provisioning Manager to provision network elements.

This chapter is organized into the following sections:

•"Overview"

•"Accessing the Provisioning Management Window"

•"Provisioning Management Window Components"

–"File Menu"

–"Browse Tree Menu"

–"Template Menu"

–"Table of Contents Pane"

–"Tree View Pane"

–"Configuration Listing Pane"

–"Job Status Pane"

–"Status and Messages Pane"

•"Configuration Management"

•"Adding a Managed Resource"

•"Modifying a Managed Resource"

•"Removing a Managed Resource"

•"Saving and Loading a Configuration Parameter Template"

---

Note System administrators can provision network elements, regardless of the region in which they reside. Regional network operators can only provision network elements in regions in which they have authorization. Non-administrative users are not permitted to provision network elements. See the "Cisco PTC User Groups" section for a detailed list of the capabilities of the various user types.

---

Overview

The Cisco PTC Provisioning Manager simplifies configuration operations by defining a set of service objects. A service object is an abstraction of a particular configuration spanning across one or more network elements. The attributes of the service object are comprised of the configuration parameters for that particular service.

Cisco PTC creates two types of service objects (Voice and Basic) and provides access to these objects through the Table of Contents pane in the Provisioning Management window:

Voice Service Objects

•RLM Signaling Path—represents a Q.931 over RLM signaling path between a gateway and a signaling controller

–GTD—represents a Generic Transparency Descriptor configuration on a Q.931/RLM signaling path between a gateway and a signaling controller

•Carrier—carrier identifier for a trunk group; for routing purposes on a gateway

•Gateway Trunk Group—represents a trunk group on a gateway

•Voice Port—represents an analog or digital voice port on a gateway

•H.323 Voice Class—represents a configuration of a voice class with parameters such as H225 timeouts on a gateway

•IVR—represents a configuration of IVR applications on a gateway

•DNIS Map—represents a configuration of DNIS Maps on a gateway

•FAX—represents a configuration of an On-Ramp or Off-Ramp Fax on a gateway

•AAA Voice Class—represents a configuration of a AAA voice class on a gateway. A AAA voice class is essentially a customized AAA profile, which defines:

–list of custom authentication servers

–list of custom authorization servers

–list of custom accounting servers

–the enabling/disabling of accounting generation

–accounting template for customized call detail reporting

•Call Accounting Template—represents a configuration of a call accounting template on a gateway. An accounting template specifies a selective set of call records to be sent to a RADIUS server.

•Voice Parameters—represents a configuration of voice parameters on a gateway.

Basic Server Objects

•NTP—represents a configuration of NTP on a gateway, gatekeeper, or directory gatekeeper

•Security Server Group—represents a configuration of a RADIUS/TACACS+ server (or group), which is used for configuring AAA on a gateway, gatekeeper, or directory gatekeeper

–Server End Point—represents a configuration of a security server end point on a gateway, gatekeeper, or directory gatekeeper

•AAA—represents the configuration of AAA (Authentication, Authorization, Accounting) on a gateway, gatekeeper, or directory gatekeeper. Also includes the security configuration required for configuring Fax on a gateway.

•Interface—represents the configuration of an Interface (Ethernet, Fast-Ethernet, Gigabit-Ethernet, Loopback) on a gateway, gatekeeper, or directory gatekeeper

•SNMP—represents the configuration of SNMP on a gateway, gatekeeper, or directory gatekeeper

•HSRP—represents the configuration of HSRP on the interfaces of gatekeepers or directory gatekeepers to form an HSRP pair

•ACL—represents the configuration of an Access Control List on a gateway, gatekeeper, or directory gatekeeper.

Each provisioning operation performed from the Provisioning Manager creates a provisioning job object and is executed in the background. Once the operation is complete, the status of the provisioning job is dynamically updated in the Provisioning Job Status pane in the Provisioning Management window.

Voice Provisioning Operations

Cisco PTC allows you to perform the following voice related provisioning operations:

•RLM Signaling Path Configuration—allows you to add, modify, and remove (complete and incomplete) an RLM signaling path to/from a gateway or signaling controller

–GTD Configuration—allows you to add and remove a Generic Transparency Descriptor configuration to/from a Q.931/RLM signaling path on a gateway or signaling controller

•Carrier Configuration—allows you to associate a carrier identifier with a trunk group, for routing purposes, on a gateway

•Gateway Trunk Group Configuration—allows you to add, modify, and remove a trunk group to/from a gateway

•Voice Port Configuration:

–Analog Voice Port—allows you to modify an analog voice port

–PRI Voice Port—allows you to add, modify, and remove a PRI voice port

–T1/E1 CAS Voice Port—allows you to add, modify, and remove a T1/E1 CAS voice port

•H.323 Voice Class Configuration—allows you to add, modify, and remove H.323 voice class parameters to/from a gateway

•IVR Configuration—allows you to add, modify, and remove an IVR configuration to/from a gateway

•DNIS Map Configuration—allows you to add, modify, and remove a DNIS map configuration to/from a gateway

•Fax Configuration—allows you to add, modify, and remove a Fax configuration to/from a gateway

•AAA Voice Class Configuration—allows you to add, modify, and remove a AAA voice class configuration on a gateway

•Call Accounting Template Configuration—allows you to add, modify, and remove a call accounting template to/from a gateway

•Voice Parameter Configuration—allows you to add and modify voice parameters on a gateway.

Basic Provisioning Operations

Cisco PTC allows you to perform the following non-voice related provisioning operations:

•NTP Configuration—allows you to add, modify, and remove an NTP configuration to/from a region, virtual zone, virtual gateway, gatekeeper, or directory gatekeeper

•Security Server Group Configuration—allows you to add and remove a RADIUS or TACACS+ configuration to/from a region, virtual zone, virtual gateway, gatekeeper, or directory gatekeeper

–Server End Point Configuration—allows you to add and remove a RADIUS or TACACS+ server end point configuration to/from a region, virtual zone, virtual gateway, gatekeeper, or directory gatekeeper

•AAA Configuration—allows you to add, modify, and remove a AAA user to/from a region, virtual zone, virtual gateway, gatekeeper, or directory gatekeeper

•Interface Configuration—allows you to add, modify, and remove an interface to/from a virtual gateway, gatekeeper, or directory gatekeeper

•SNMP Configuration—allows you to add, modify, and remove an SNMP configuration to/from a region, virtual zone, virtual gateway, gatekeeper, or directory gatekeeper

•HSRP Configuration—allows you to add, modify, and remove an HSRP configuration to/from a gatekeeper or directory gatekeeper

•ACL Configuration—allows you to add, modify, and remove an Access Control List to/from a virtual gateway, gatekeeper, or directory gatekeeper.

---

Note The Provisioning Manager allows you to specify additional commands not currently provisioned/supported by Cisco PTC through the Extra Commands tab located in the Provisioning Management window. Commands that fit this category are appended to the provisioning job you are submitting and are executed on the IOS device as part of that provisioning job. For example, if you want to enable IP routing on an IOS device, you can enter the ip routing command in the Extra Commands text box for any service object (for example, RLM, voice ports, interface) and then submit the job. The ip routing command is then applied on the selected device, along with the other commands you submitted to be provisioned by Cisco PTC on that device.

---

Accessing the Provisioning Management Window

Cisco PTC provides a Provisioning Management window for the provisioning activities. The Provisioning Manager is invoked by clicking the Provisioning button in the Cisco PTC Launch Pad window.

Figure 4-1 shows an example of the Provisioning Management window.

Figure 4-1 Provisioning Manager Window

Provisioning Management Window Components

The Provisioning Management window is comprised of the following components:

•Menu bar—contains File, Browse Tree, and Template menus:

–File—provides an Exit option

–Browse Tree—provides Find, Reset, and Refresh options

–Template—provides Load Template and Save Template options.

•Tool bar—provides icons corresponding to the Browse Tree and Template menu options

•Table of Contents pane—displays the service objects in a hierarchical representation

•Tree View pane—provides a containment hierarchy of the network elements discovered in the network

•Configuration Listing pane—the main configuration area for provisioning services. A list of service objects, based upon filtering criteria (for example, region, zone, or virtual gateway), is displayed in this pane

•Job Status pane—displays a provisioning job list. Each entry in the list provides the username of the job's submitter, a job ID, the status of the job (pending, completed, or errored), the time the job was submitted, and the time the job was completed

•Status pane—displays Provisioning Manager related messages and status information.

File Menu

The File menu contains an Exit option that allows you to exit the Cisco PTC application.

Browse Tree Menu

The Browse Tree menu provides Find, Reset, and Refresh options.

Find Option

This option allows you to search for an element in the Cisco PTC network. When found, the object is highlighted in the Tree View pane.

Reset Option

This option resets the contents of all objects in the Tree View pane by reading in all of the current network element information from the Cisco PTC database.

Refresh Option

This option resets the contents of a selected object in the Tree View pane by reading in the current network element information for that object, from the Cisco PTC database.

Template Menu

The Template menu provides Load Template and Save Template options. The Save Template option allows you to create a template containing a set of configuration parameter values you wish to replicate in other service objects. You can subsequently use the Load Template option to add these saved configuration parameter values to a selected region or network element object in the Tree View pane.

Load Template Option

This option provides a list of configuration parameter templates, that were created using the
Save Template menu option. You must first select a service object from the Tree View pane, then you select the configuration parameter template that contains the configuration parameter values you wish to have replicated in the selected service object. See the "Saving and Loading a Configuration Parameter Template" section for an example on how to use this option.

Save Template Option

This option allows you to save a set of configuration parameter values you are assigning or already have assigned to a service object, to a new configuration parameter template. You can subsequently load this configuration parameter template (through the Load Template menu option) when you want to replicate the parameter values in a service object you selected in the Tree View pane. See the "Saving and Loading a Configuration Parameter Template" section for an example on how to use this option.

---

Note The configuration parameter template does not include the parameters that are associated to a specific device, for example, an interface name.

---

Table of Contents Pane

The top left pane of the Provisioning Manager window is the Table of Contents pane. This pane is divided into two service related groups (Voice and Basic). Each group has service objects associated with them in a hierarchical manner. You obtain access to the underlying service objects by either clicking on an entry's magnifying glass icon or by double-clicking on the entry itself. For example, when the Provisioning Manager window is first displayed, only the Table of Contents entry is displayed. When you double-click on this entry, it expands and the Voice and Basic entries are displayed, as shown Figure 4-1. You can continue to expand further down into either group by clicking on an entry's magnifying glass icon or by double-clicking on the entry itself.

Note, when you click on a service object, the Configuration Listing pane is modified (that is, columns that will contain information associated with a selected network element in the Tree View pane, are displayed in the Table of Contents pane.

In order to perform a provisioning related operation on a particular service object, you must first select the appropriate service object from within this pane and then you must select a network element in the Tree View pane. Upon doing so, the Configuration Listing pane is populated with the attribute values that are currently in place for the selected network element, as shown in Figure 4-2.

Provisioning can be done on an individual network device or on a group of devices contained in a virtual entity (such as a signaling controller and a gateway contained within a virtual gateway, or a gateway, gatekeeper, and directory gatekeeper contained within a virtual zone or region).

Figure 4-2 Provisioning Management Window - Modified Configuration Listing Pane

Table 4-1 lists the Voice related service features supported on each network entity. Table 4-2 lists the Basic features supported on each network entity. The Provisioning Manager enforces platform dependencies when configuring the features on the selected network entities.

Table 4-1 Provisioning Feature to Voice Network Entity Dependencies 

Feature	Region (GW, GK, DGK)	Virtual Zone (GW, GK)	Virtual Gateway GW & SC     GW Only		GK/DGK
RLM Signaling Path			X
Generic Transparency Descriptor (GTD)			X
Gateway Trunk Group				X
Voice Port			X
H.323 Voice Class				X
IVR				X
DNIS Map				X
FAX				X
AAA Voice Class				X
Call Accounting Template				X
Voice Parameters				X

Table 4-2 Provisioning Feature to Basic Network Entity Dependencies 

Feature	Region (GW, GK, DGK)	Virtual Zone (GW, GK)	Virtual Gateway GW & SC     GW Only		GK/DGK
NTP	X	X		X	X
Security Server Group	X	X		X	X
Server End Point	X	X		X	X
AAA	X	X		X	X
Interface				X	X
SNMP	X	X		X	X
HSRP					X
ACL				X	X

Tree View Pane

The lower left pane of the Provisioning Manager window is the Tree View pane. This pane shows the discovered Cisco PTC network objects in a logical containment hierarchy in a tree-like view and is used for object browsing and selection. The hierarchy is as follows:

1. The top level contains all of the discovered network objects.

2. Under each network object—all region objects within this network.

3. Under each region object:

a. a directory gatekeeper group object.

b. virtual zone objects.

c. unassociated virtual gateway objects—virtual gateway objects that do not belong to a zone in this region.

4. Under each directory gatekeeper group object—gatekeeper objects that form this group.

5. Under each virtual zone object:

a. a gatekeeper group object—contains all of the gatekeepers that form this group

b. virtual gateway objects.

6. Under each virtual gateway object:

a. an SC2200 complex.

b. a gateway object—contains all of the DS1 lines currently configured on this gateway.

You navigate through the Tree View pane (that is, you display the children of a particular network, region, or zone object) by clicking on the magnifying glass icon or by double-clicking on a particular network, region, or virtual zone entity. You single click on an object in the Tree View pane to select that particular object.

The Table of Contents and Tree View panes are used in conjunction with one another to display and access the service related configuration parameter values that are supported on a particular network entity. Upon expanding to and then selecting the desired service object in the Table of Contents pane, you should navigate through the Tree View pane, select the desired network object, then either click on the Listing button or drag and drop the selected entry into the Listing field in the Configuration Listing pane. The mandatory, basic configuration parameter values pertaining to the service and network objects you selected in the Table of Contents and Tree View panes are displayed in the Configuration Listing pane, as shown in Figure 4-2. You can then view the optional parameter values by clicking the View button, or you can create a configuration for a new service objector by clicking the Add button, or you can modify the selected entry's parameter values by clicking the Modify button, as shown in Figure 4-3.

Network Tab

When you click on the Network tab in the Tree View pane, the network object and discovered region, virtual zone, directory gatekeeper group, gatekeeper group, virtual gateways, media gateway, and signaling controller objects are displayed in a hierarchical, tree-like display in the Tree View pane.

Mgmt System Tab

When you click on the Mgmt System tab in the Tree View pane, the devices under configuration management control of the CMNM Element Management Systems (EMSs) and the Cisco IE2100 appliances can be displayed in a hierarchical, tree-like display in the Tree View pane:

•CMNM subview—shows all of the CMNM hosts and the signaling controller complexes under configuration management control by each CMNM

•Cisco IE2100 subview—shows all of the Cisco IE2100 appliances and the gateways, gatekeepers, and directory gatekeepers that are under configuration management control of each Cisco IE2100.

Configuration Listing Pane

This pane allows you to provision services. Objects to be provisioned are selected from the Tree View pane and then dragged and dropped into the Listing field in this pane. You then choose the type of service to provision, the parameters to configure, and the operation (add/view/modify/delete) to perform.

---

Note The Provisioning Manager allows you to specify additional commands not currently provisioned/supported by Cisco PTC through the Extra Commands tab located in the Provisioning Management window. Commands that fit this category are appended to the provisioning job you are submitting and are executed on the Cisco IOS device as part of that provisioning job. For example, if you want to enable IP routing on a Cisco IOS device, you can enter the ip routing command in the
Extra Commands text box for any service object (for example, RLM, voice ports, interface) and then submit the job. The ip routing command is then applied on the selected device, along with the other commands you submitted to be provisioned by Cisco PTC on that device.

---

Listing Button

You click on this button, with an entry selected in the Tree View pane, to obtain access to that object's parameters.

Refresh Button

You click this button to refresh the information displayed in the Configuration Listing pane.

Add Button

You click this button to create a configuration for a new service object. You enter the mandatory service parameters through this option and can then enter the optional parameter values by clicking on the Next button.

View Button

You first select an object in the Configuration Listing pane, then you click this button to view the selected device's mandatory, basic parameters that are now displayed in this pane. Access to optional parameters, not shown in this pane, are available by clicking on the tabs that are displayed at the top of this pane, where applicable.

Modify Button

You first select an object in the Configuration Listing pane, then you click this button to obtain the ability to modify the selected device's mandatory, basic parameters that are now displayed in this pane. Access to optional parameters, not shown in this pane, are available by clicking on the tabs that are displayed at the top of this pane, where applicable. Also available through this feature is a read only list of the current parameters and their values for the selected object, as shown in Figure 4-3.

Figure 4-3 Provisioning Management Window - Configuration Listing Pane Showing Object Parameters

Delete Button

You first select an object in the Configuration Listing pane, then you click this button to delete the selected object.

Job Status Pane

A provisioning job is implicitly created when you apply a provisioning request. This pane displays a provisioning job list, including each job's ID, status (pending, completed, or error), submission time, and completion time. You can delete completed jobs. You can select any job and review its job content and provisioning results. For failed jobs, you can view a detailed failure report, which includes the reason for the failure, and rollback status if any.

Refresh Button

You click this button to refresh the list and status of the provisioning jobs listed in the Job Status pane.

View Button

You first select an item in the Job Status pane, then you click this button to view the selected job's content and provisioning results through the Provisioning Job Detail window. For failed jobs, details about the cause of the failure are also provided.

Delete Button

You first select an item in the Job Status pane, then you click this button to delete the selected job.

Status and Messages Pane

This pane displays error and status messages.

Error Reporting

When a provisioning failure occurs, Cisco PTC reports the configuration error to the Client. The following information is provided:

•failure date and time

•failed device(s), including the device's hostname and IP address, the software/firmware versions, and the responsible service module/card (when applicable)

•failure reason(s)—for example, device communication failure, timeout, version mismatch, and invalid parameters

•failure detail(s)—a detailed textual description of the failure

•failure state—whether the entire operation failed or partial succeeded. In the case of partial failure, report which part of the request failed.

When a failure occurs for a transactional type operation, Cisco PTC attempts to roll back to the previous configuration. The only transactional operations supported are:

•an RLM/Q.931 signal path configuration

•a virtual voice port configuration on a virtual gateway.

The other types of scope operations (such as, SNMP configuration on a region or virtual zone) are done on a best effort basis, meaning that Cisco PTC applies the configuration to as many devices as possible within the operational scope (such as a region or virtual zone).

Configuration Management

This section describes the configuration management capabilities provided by Cisco PTC.

RLM Signaling Path Configuration

This section provides information about the RLM (Redundant Link Manager) configuration capabilities on a Q.931/RLM signaling path provided by Cisco PTC. An overview of these capabilities, as well as a list of the RLM configuration parameters supported by Cisco PTC are provided.

RLM Signaling Path Configuration Overview

RLM provides a virtual link management over multiple IP networks so that the Q.931 signaling protocol and other proprietary protocols can be transported on top of multiple, redundant links between the signaling controller (SC2200) and the Network Access Server (NAS). In addition, RLM opens, maintains, and closes multiple links, manages buffers of queued signaling messages, and monitors whether links are active for link failover and signaling controller failover. The ISDN module works in conjunction with the RLM module. The RLM goes beyond Q.931, because it allows for future use of different upper layers, and more importantly, allows for multiple, redundant paths to be treated as one path by upper layers.

Note, you can create more than one IP connection between the SC2200 and the NAS. Also, if the SC2200 is configured as a redundant setup, two RLM links exist for each active and standby SC2200.

Cisco PTC supports the creation of a Q.931/RLM signaling path between the signaling controller and gateway. This involves configuring both the gateway and signaling controller as follows:

•On the gateway:

–configure an RLM group

–configure multiple RLM links under the group. An RLM link represents the gateway endpoint of the RLM backhaul. It has information about the gateway and signaling controller IP address and UDP port number used for communication.

•On the signaling controller:

–configure IP Links which represent the endpoint of the RLM backhaul on the signaling controller side

–configure NAS Path which represents the Q.931 protocol path between the signaling controller and the gateway.

Cisco PTC supports the configuration of multiple Q.931/RLM signaling paths between a signaling controller and a gateway (that is, Cisco PTC supports multiple NAS paths on the signaling controller and multiple RLM groups on a single gateway. However, only one NAS path is configured per RLM group.

Cisco PTC supports the deletion of a Q.931/RLM signaling path on a virtual gateway. This includes the deletion of an RLM group on the gateway, the NAS path, and its associated IP links on the signaling controller.

If the gateway and signaling controller are configured outside of Cisco PTC (for example, through CLI or an EMS), an RLM group can be configured on the gateway but not on the corresponding NAS path and IP links on the signaling controller, or vice versa. Such a configuration is called an incomplete Q.931/RLM signaling path on the virtual gateway.

Cisco PTC supports modification of a Q.931/RLM signaling path on the virtual gateway. If the signal path is incomplete, Cisco PTC allows you to delete this incomplete configuration.

RLM Signaling Path Configuration Parameters

Cisco PTC allows you to browse the associations between a gateway and a PGW2200/SC2200 through the Tree View pane (see the "Tree View Pane" section for a detailed description of the Tree View pane hierarchy) and to query a list of RLM (Redundant Link Manager) signaling paths that meet a filter criteria (for example, region, zone, and virtual gateway). The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for an RLM signaling path is:
region -> virtual zone -> virtual gateway -> router; PGW2200/SC2200.

The Tree View pane is used as follows:

1. You select a virtual gateway and a PGW2200/SC2200 to add an RLM signaling path between the two.

2. You select a virtual gateway, zone, or region to view all of the corresponding RLM signaling paths in the virtual gateway(s).

When you select the RLM Signaling Path entry in the Table of Contents pane, the following columns are displayed in the Configuration Listing pane:

•GW NAME—the name of the gateway associated with this RLM signaling path

•SC2200 NAME—the name of the PGW2200/SC2200 device associated with this RLM signaling path

•RLM Group—the RLM Group object on the gateway. If no RLM Group is configured on the gateway, this field has a "<no MG Component>" value.

•NAS Path—the Network Access Server Path object on the PGW2200/SC2200. If a NAS Path on the PGW2200/SC2200 is not configured for this RLM Group, this field displays a "<no SC Component>" value.

•NFAS Group—the Non-Facility Associated Signaling Groups on the gateway using this RLM Group. This field displays a "<no MG Component>" value when no NFAS Group is using this RLM Group.

When you subsequently expand the contents of the Tree View pane and either select a region, virtual zone, or virtual gateway object and click the Listing button in the Configuration Listing pane or double-click on the object in the Tree View pane, information pertaining to the underlying network elements are displayed in the above described columns in the Configuration Listing pane.

When you click the Add button in the Configuration Listing pane to add an RLM signaling path to a gateway or signaling controller, you must initially enter values for the mandatory, basic parameters listed in Table 4-3. You then click Next, at which point, optional parameters are displayed in the Configuration Listing pane. The additional optional parameters are grouped under separate tabs (for example, Basic, RUDP, GW RLM Properties, LAPD, Other, and Call Processing). You click on a particular tab to have the related optional parameters displayed. Upon entering the parameter values you desire, you click the OK button to submit a provisioning job and return to the original Configuration Listing pane. You click the Apply button to submit a provisioning job and return to the list of mandatory parameters. To have all of the parameter fields set to their default values, you click the Default button. Click the Cancel button to abort this task.

Table 4-3 Mandatory Q931/RLM Signaling Path Parameters - Add Operation 

Parameter	Value	Description
Virtual Gateway Name	int (0-255)	The name of the virtual gateway.
SC Name	enum {consisting of all of the SC2200s available in the network	The name of the signaling controller.

When you subsequently click the Modify button in the Configuration Listing pane, you can modify the optional RLM signaling path related parameters described in Table 4-4.

---

Note To modify an RLM signaling path, you must first select an RLM signaling path entry from the list displayed in the Configuration Listing pane, and then click Modify. Only a complete RLM signaling path can be modified.

---

Table 4-4 Q931/RLM Signaling Path Parameters 

Parameter	Category/Parameter Tab	Type	Value	Description	Modifiable on Router?
RLM SigPath Number	Basic & GW	GW	int (0-255)	RLM Group number on the gateway.	No
SC Primary Ethernet Interface	Basic & General	GW	enum (consisting of all of the interfaces currently configured on the SC)	Primary Ethernet interface on the PGW2200/SC2200 for the IP link.	No
SC Secondary Ethernet Interface	Basic & General	GW	enum (consisting of all of the interfaces currently configured on the SC)	Secondary Ethernet interface on the PGW2200/SC2200 for the IP link.	No
GW Primary Interface	Basic & General	GW	enum (consisting of all of the interfaces currently configured on the SC	Primary interface on the gateway for the RLM link to the PGW2200/SC2200.	No
GW Secondary Interface	Basic & General	GW	enum (consisting of all of the interfaces currently configured on the SC	Secondary interface on the gateway for the RLM link to the PGW2200/SC2200.	No
RLM UDP Port	Basic & General	GW	int (even number between 3000-65533)	The UDP port on the gateway and PGW2200/SC2200 upon which the gateway and PGW2200/SC2200 communicate RLM messages. The Q931 messages are communicated on the UDP port that numbers one more than this port number.	No
MDO	Basic & General	SC: NASPath - mdo	enum {unset, ANSISS7 CLEAR, ANSISS7 MCI, ANSISS7 SPRINT, ANSISS7 STANDARD, ATT 41459, ATT 41459 C2, BELL 1268, BELL 1268 C3, BTNUP BTNR167, BTNUP NRC, DPNSS BTNR188, EISUP, ETS 300 102, ETS 300 102 C1, ETS 300 121, ETX 300 172, ETS 300 356, FINLAND 5779, HKTA 2202, ISUPV1 POLI, ISUPV2 FRENCH, ISUPV2 GERMAN, ISUPV2 JAPAN, ISUPV2 KPNPB, ISUPV2 NTT, ISUPV2 SWISS, ISUPV2 UK, NORTEL IBN7, NTT INS 1500, Q721 BASE, Q721 CHINA, Q721 FRENCH, Q721 AUSTRL, Q761 BASE, Q761 BELG MOB1, Q761 KOREAN, Q767 BASE, Q767 ITAL, Q767 ITAL INTERCONNECT, Q767 MEXICAN, Q767 RUSS, Q767 SPAN, Q767 SWED, T113 BEL} Default: BELL 1268 C3	Message Definition Object file.	No
Description	Basic & General			Description of the RLM group and NAS path.	Yes
RLM Link1 Priority	Detail & General		int (1-100,000)	Priority of the RLM link between the gateway and PGW2200/SC2200.	No
RLM Link2 Priority	Detail & General		int (1-100,000)	Priority of the RLM link between the gateway and PGW2200/SC2200.	No
RLM Link3 Priority	Detail & General		int (1-100,000)	Priority of the RLM link between the gateway and PGW2200/SC2200.	No
RLM Link4 Priority	Detail & General		int (1-100,000)	Priority of the RLM link between the gateway and PGW2200/SC2200.	No
B Originating Start Node	Detail & Call processing	SC: NASPath - sigsvcprop	enum {no dialplan, first node in originating digit tree} Default: no dialplan	B Originating Start Node.	Yes
B Terminating Start Node	Detail & Call processing	SC: NASPath - sigsvcprop	enum {no dialplan, first node in originating digit tree} Default: no dialplan	B Terminating Start Node.	Yes
BC Initial State	Detail & Call processing	SC: NASPath - sigsvcprop	enum {In Service, Out of Service} Default: In Service	Initial status the SC places its nailed up bearer channels following an application restart. The gateway can override this status with the GSM messages.	Yes
Bothway Working	Detail & Call processing	SC: NASPath - sigsvcprop	int (0 or 1) Default: 1	Specifies if bothway release/circuit-free handling for BTNUP protocol is enabled. Set to 0 to disable.	Yes
CGBA2	Detail & Call processing	SC: NASPath - sigsvcprop	int (0 or 1) Default: 0	Determines if paired (0) or single (1) Circuit Group Blocking Acknowledgements (CGBAs) are required before the blocking is considered successful. Only applicable to ANSI SS7, IBN7, and CTUP protocols.	Yes
CLIPEss	Detail & Call processing	SC: NASPath - sigsvcprop	int (0 or 1) Default: 0	Set to 1 to force request of Calling Line Identity (CLI) if not automatically provided.	Yes
COT In Tone	Detail & Call processing	SC: NASPath - sigsvcprop	int (1780 or 2010) Default: 2010	Receive tone (in Hz) for Continuity Test (COT) hardware. The tone to listen for when doing a COT.	Yes
COT Out Tone	Detail & Call processing	SC: NASPath - sigsvcprop	int (1780 or 2010) Default: 2010	Transmit tone (in Hz) for COT hardware. The tone that is produced.	Yes
COT Percentage	Detail & Call processing	SC: NASPath - sigsvcprop	int {0-100} Default: 0	Statistical COT.	Yes
External COT	Detail & Call processing	SC: NASPath - sigsvcprop	enum {Zero, Loop, Transponder} Default: Loop	Determines the type of COT handling for the specified destination.	Yes
Fast Connect	Detail & Call processing	SC: NASPath - sigsvcprop	int (0 or 3) Default: 0	Allows you to set this property for NI2+ only (PRI BELL 1268 customer 3, Cisco MGW). The purpose of this property is to allow/disallow the signal being sent to LCM when a CALL PROCEEDING, a PROGRESS and an ALERTING message is received from the gateway. 0—Normal behavior, enabled all signals to LCM. 1—Disable signals to LCM when a Call Proceeding message is received from the gateway. 2—Disable signals to LCM when a Call Proceeding or Progress message is received from the gateway. 3—Disable signals to LCM when a Call Proceeding, or a Progress, or an Alerting message is received from the gateway.	Yes
Forward CLI in IAM	Detail & Call processing	SC: NASPath - sigsvcprop	int (0 or 1) Default: 0	Set to 1 if outgoing IAM should contain the Calling Line Identity (CLI), if available. Only applicable for BTNUP when interworking from other protocols.	Yes
Forward Segmented NEED	Detail & Call processing	SC: NASPath - sigsvcprop	int (0 or 1) Default: 1	Set to 0 to disable the forwarding of segmented NEED messages within the BTNUP_NRC protocol. If segmenting is disabled, all mandatory DPNSS information elements are packed into a single BTNUP NEED message.	Yes
Glare	Detail & Call processing	SC: NASPath - sigsvcprop	enum {no glare handling, always, even/odd, no control} Default: even/odd	Call Collision Handling. no glare handling—call collision results in a REL sent to both calls. Also known as yield to all double seizures. always—the SC has control of all circuits and the SC handles any call collisions. It ignores incoming IAMs and proceeds with its own calls as normal. even/odd—highest point code controls the even circuits. Depending on the OPC of the SC, the side that has the higher point code controls the even circuits, while the side with the lower point code controls the odd circuits. no control—The SC specified with this option does not control any circuits. The SC accepts incoming IAMs from the side with control.	Yes
GRA2	Detail & Call processing	SC: NASPath - sigsvcprop	int (0 or 1) Default: 0	Determines if paired (0) or single (1) Group Reset Acknowledgements (GRAs) are required before the reset is considered successful. Only applicable to ANSI SS7, IBN7, and CTUP protocols.	Yes
International Prefix	Detail & Call processing	SC: NASPath - sigsvcprop	int Default:0	International prefix string to be added to the international dialed number when normalization is enabled.	Yes
National Prefix	Detail & Call processing	SC: NASPath - sigsvcprop	int Default:0	National prefix string to be added to the national dialed number when normalization is enabled.	Yes
Normalization	Detail & Call processing	SC: NASPath - sigsvcprop	int (0 or 1) Default:0	Normalization of dialed number to unknown. Set to 0 for disabled or 1 for enabled.	Yes
O Maximum digits	Detail & Call processing	SC: NASPath - sigsvcprop	int Default:24	Specifies the maximum number of digits to receive for overlap digit processing for call origination from this traffic path.	Yes
O Minimum digits	Detail & Call processing	SC: NASPath - sigsvcprop	int Default:0	Specifies the minimum number of digits to receive for overlap digit processing for call origination from this traffic path.	Yes
O Overlap	Detail & Call processing	SC: NASPath - sigsvcprop	int Default:0	Set to 1 to enable overlap signaling for call origination from this traffic path.	Yes
Overlap Digit Time	Detail & Call processing	SC: NASPath - sigsvcprop	int (0-60) Default:6	Overlap inter-digit timer. The time to wait for the rest of the digits.	Yes
Propagate Service Message Block	Detail & Call processing	SC: NASPath - sigsvcprop	enum {Enable, Disable} Default: Disable	Enable—the protocols supporting group blocking send individual blocking messages. Disable—protocols supporting group blocking continue to send group messages.	Yes
Maximum Redir	Detail & Call processing	SC: NASPath - sigsvcprop	int Default:3	Specifies the maximum allowable value of the redirection counter parameter available in some C7 signaling systems before the call is force-released. Used to prevent routing loops in certain applications.	Yes
Release Mode	Detail & Call processing	SC: NASPath - sigsvcprop	enum {Asynchronous, Synchronous} Default: Synchronous	Defines the type of releasing. Asynchronous clearing allows both OCC and TCC sides to clear independently; circuits are freed earlier in the release sequence. Synchronous clearing requires that the clearing at the two sides is synchronized. Normally, nailed-up configurations use synchronous clearing and VSC configurations use asynchronous clearing.	Yes
Route Preference	Detail & Call processing	SC: NASPath - sigsvcprop	int (0-9) Default:0	Determines the preferred route.	Yes
Suppress CLI Digits	Detail & Call processing	SC: NASPath - sigsvcprop	int Default:0	Suppress the calling party number.	Yes
T309Time	Detail & Call processing	SC: NASPath - sigsvcprop	int Default:90,000	For timer NT309 (in milliseconds).	Yes
T310Time	Detail & Call processing	SC: NASPath - sigsvcprop	int Default:10,000	For timer NT310 (in milliseconds).	Yes
T Maximum Digits	Detail & Call processing	SC: NASPath - sigsvcprop	int Default:24	Specifies the maximum number of digits to receive for overlap digit processing for call termination to this traffic path.	Yes
T Minimum Digits	Detail & Call processing	SC: NASPath - sigsvcprop	int Default:0	Specifies minimum number of digits to receive for overlap digit processing for call termination to this traffic path.	Yes
T Overlap	Detail & Call processing	SC: NASPath - sigsvcprop	int (0 or 1) Default:0	Set to 1 to enable overlap signaling for call termination to this traffic path.	Yes
VoIP Prefix	Detail & Call processing	SC: NASPath - sigsvcprop	int Default:0	A numeric string.	Yes
LAPD Drop Error	Detail & LAPD	SC: NASPath - sigsvcprop	enum {Enable, Disable} Default: Disable	Boolean to determine if some LAPD sequence errors are discarded. Used in large IP networks where latency may cause LAPD sequence errors. According to Q.921, this causes the link layer to reset. This parameter allows sequence errors to be discarded without setting the link.	Yes
LAPD K Value	Detail & LAPD	SC: NASPath - sigsvcprop	int (1-127) Default:7	Number of outstanding frames in the Q.921 transmission window.	Yes
LAPD N200	Detail & LAPD	SC: NASPath - sigsvcprop	int (0-10) Default:6	Maximum number of retransmissions of a Q.921 frame.	Yes
LAPD N201	Detail & LAPD	SC: NASPath - sigsvcprop	int Default:260	Maximum number of octets in a Q.921 frame.	Yes
LAPD T200	Detail & LAPD	SC: NASPath - sigsvcprop	int (10-60) Default:10	Maximum wait time (in 1/10 seconds) for a LAPD frame acknowledgement before retransmission.	Yes
LAPD T203	Detail & LAPD	SC: NASPath - sigsvcprop	int (50-600) Default:100	Maximum time (in 1/10 seconds) the Q.921 link is idle before sending a frame.	Yes
Resume Ack Timer	Detail & Call processing	SC: NASPath - sigsvcprop	int Default:1		Yes
RUDP Ack	Detail & RUDP	SC: NASPath - sigsvcprop	enum {Enable, Disable} Default: Enable		Yes
RUDP Keep Alives	Detail & RUDP	SC: NASPath - sigsvcprop	enum {Enable, Disable} Default: Enable		Yes
RUDP Number of Retx	Detail & RUDP	SC: NASPath - sigsvcprop	int (1-100) Default:2	Maximum number of retransmissions count.	Yes
RUDP Retx Timer	Detail & RUDP	SC: NASPath - sigsvcprop	int (2-100) Default:6	The retransmission timeout value.	Yes
RUDP Sdm	Detail & RUDP	SC: NASPath - sigsvcprop	enum {Enable, Disable} Default: Enable		Yes
RUDP Window Size	Detail & RUDP	SC: NASPath - sigsvcprop	int (2-64) Default:32	Maximum number of Unacknowledged Segments in the RUDP window.	Yes
Session Pause Timer	Detail & RUDP	SC: NASPath - sigsvcprop	int Default:8		Yes
Span ID	Detail & Call processing	SC: NASPath - sigsvcprop	int Default:65535	E1/T1 ID for FAS and DPNSS, ffff for SS7.	Yes
Force-down Timer	Detail & GW RLM	GW: rlm group - timer force-down	int {1-600} Default:30	Timeout value (in seconds) to force staying in the down state.	Yes
Keep-alive Timer	Detail & GW RLM	GW: rlm group - timer keepalive	int {1-600} Default:1	Keepalive timeout value, in seconds.	Yes
Minimum Up Link Timer	Detail & GW RLM	GW: rlm group - timer minimum-up	int {1-600} Default:60	Minimum time (in seconds) to wait for the up link to stabilize.	Yes
Open-wait Timer	Detail & GW RLM	GW: rlm group - timer open-wait	int {1-600} Default:3	Open connection timeout value, in seconds.	Yes
Recovery Timer	Detail & GW RLM	GW: rlm group - timer recovery	int {1-600} Default:12	Recovery timeout value, in seconds.	Yes
Retransmit Timer	Detail & GW RLM	GW: rlm group - timer retransmit	int {2-100} Default:6	RLM command retransmission timeout value, in seconds.	Yes
Switch-link Timer	Detail & GW RLM	GW: rlm group - timer switch-link	int {1-600} Default:5	Switch to newly recovered link with higher weighting timeout value, in seconds.	Yes

GTD Configuration

This section provides information about the Generic Transparency Descriptor (GTD) configuration capabilities on a Q.931/RLM signaling path provided by Cisco PTC. An overview of these capabilities, as well as a list of the GTD configuration parameters supported by Cisco PTC are provided.

GTD Configuration Overview

Cisco PTC supports the configuration of R2/ISUP transparency on the RLM/Q.931 signaling path. This involves configuring the GTD parameters for the NAS Path component on the signaling controller. Note that the gateway requires the enabling of the R2/ISUP signal forwarding feature in order to forward the R2/ISUP signal as GTD parameters to the far end.

GTD Configuration Parameters

Cisco PTC allows you to query a list of Generic Transparency Descriptor (GTD) parameter configurations on a Q.931/RLM signaling path that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for a GTD Configuration Service object is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used to select a virtual gateway for configuring GTD parameter configuration on the gateway.

When you select the GTD service object in the Table of Contents pane, the following columns are displayed in the Configuration Listing pane:

•SC2200 Name—PGW2200/SC2200 name

•GTD—GTD name/identifier

•Param String—all of the parameter strings in this GTD configuration

•Override String—the overridden parameter strings in this GTD.

You must initially enter the mandatory parameter listed in Table 4-5 when you click the Add button in the Configuration Listing pane, to add a GTD parameter configuration. Upon entering the mandatory parameter values, you click the Next button to enter the optional parameter values.

Table 4-5 Mandatory GTD Parameter - Add Operation 

Parameter	Value	Description
SC2200 Name	enum consisting of all SC2200s available in the network	PGW2200/SC2200 name.

When you click the Modify button, you can modify the GTD related parameters listed in Table 4-6.

Table 4-6 GTD Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
GTD Name	Basic & Common	string	Name of the GTD.	No
GTD Parameters	Basic & Common	string	The parameters in this GTD.	Yes
GTD Override Parameters	Basic & Common	list {CGN.noa, CPN.noa}	The override parameters in this GTD.	Yes
Description	Basic & Common	string	Description of this GTD.	Yes

Carrier Configuration

Allows you to query a list of Carrier parameter configurations that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for a Carrier Configuration service object is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used to select a virtual gateway for configuring Carrier parameter configuration on the gateway.

When you select the Carrier service object in the Table of Contents pane, the following columns are displayed in the Configuration Listing pane:

•Carrier ID—Carrier name

•Description—Carrier description.

When you click the Add or Modify button, you can add/modify the Carrier related parameters listed in Table 4-7.

Table 4-7 Carrier Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Carrier Name	Basic & Common	string	Name of the Carrier.	No
Description	Basic & Common	string	Description of this Carrier.	Yes

Trunk Group Configuration

This section provides information about the trunk group configuration capabilities provided by Cisco PTC. An overview of these capabilities, as well as a list of the trunk group configuration parameters supported by Cisco PTC on gateways are provided.

Trunk Group Configuration Overview

The Cisco IOS XU release supports carrier sensitive routing and additional signaling interfaces on trunk groups. Cisco PTC supports the creation and deletion of a trunk group on a gateway. When a trunk group is deleted, Cisco PTC notifies the Cisco Voice Routing Center (VRC) application and requires a confirmation from Cisco VRC before committing the delete.

Cisco PTC supports the following trunk group properties:

•trunk group labeling

•associating a carrier identifier with a trunk group for routing purposes

•the maximum number of calls that a trunk group can carry simultaneously

•the maximum number of outgoing call attempts when a glare situation is encountered

•the search method for selecting an available timeslot when terminating a call

•associating a text description

Trunk Group Configuration Parameters

Cisco PTC allows you to query a list of trunk group configurations that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for a trunk group configuration service object is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used to select a virtual gateway for configuring a Trunk Group on the gateway.

When you select the Trunk Group service object in the Table of Contents pane, the following columns are displayed in the Configuration Listing pane:

•Scope—gateway name

•Trunk Group ID—trunk group number or name

•Carrier ID—carrier that owns the trunk group

•Voice Ports—carrier that owns the trunk group.

You must initially enter the mandatory parameters listed in Table 4-8 when you click the Add button in the Configuration Listing pane to add a trunk group. Upon entering the mandatory parameter values, you click the Next button to enter the optional parameter values.

Table 4-8 Mandatory Trunk Group Parameters - Add Operation 

Parameter	Value	Description
Virtual Gateway Name	string	The virtual gateway upon which this trunk group configuration needs to be applied.
Type	enum {Carrier-Id Based, Trunk Group Label Based}	The type of trunk group, depending upon the routing type used.
Trunk Group Id	string or integer depending upon the type of Trunk Group	Trunk group ID.

When you click the Modify button, you can modify the Trunk Group related parameters listed in Table 4-9.

Table 4-9 Trunk Group Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Carrier Id	Basic & General	string	The carrier that owns the trunk group.	Yes
Hunt Scheme	Basic & General	enum {Least Idle Both, Least Idle Even, Least Idle Odd, Least Used Both Up, Least Used Both Down, Least Used Even Up, Least Used Even Down, Least Used Odd Up, Least Used Odd Down, Longest Idle Both, Longest Idle Even, Longest Idle Odd, Round Robin Both Up, Round Robin Both Down, Round Robin Even Up, Round Robin Even Down, Round Robin Odd Up, Round Robin Odd Down, Sequential Both Up, Sequential Both Down, Sequential Even Up, Sequential Even Down, Sequential Odd Up, Sequential Odd Down, Random}	The search method for finding an available voice channel in the trunk group.	Yes
Max Calls Any InOut	Detail & MaxCalls	integer (0-1000)	Specifies the number of allowed incoming and outgoing calls (both data and voice).	Yes
Max Calls Any In	Detail & MaxCalls	integer (0-1000)	Specifies the number of allowed incoming calls (both data and voice).	Yes
Max Calls Any Out	Detail & MaxCalls	integer (0-1000)	Specifies the number of allowed outgoing calls (both data and voice).	Yes
Max Calls Data InOut	Detail & MaxCalls	integer (0-1000)	Specifies the number of allowed incoming and outgoing data calls.	Yes
Max Calls Data In	Detail & MaxCalls	integer (0-1000)	Specifies the number of allowed incoming data calls.	Yes
Max Calls Data Out	Detail & MaxCalls	integer (0-1000)	Specifies the number of allowed outgoing data calls.	Yes
Max Calls Voice InOut	Detail & MaxCalls	integer (0-1000)	Specifies the number of allowed incoming and outgoing voice calls.	Yes
Max Calls Voice In	Detail & MaxCalls	integer	Specifies the number of allowed incoming voice calls.	Yes
Max Calls Voice Out	Detail & MaxCalls	integer	Specifies the number of allowed outgoing voice calls.	Yes

Voice Port Configuration

This section provides information about the analog and digital Voice Port configuration capabilities provided by Cisco PTC. An overview of these capabilities, as well as a list of the Voice Port configuration parameters supported by Cisco PTC on gateways are provided.

Analog Voice Port Configuration Overview

This section provides information on how to configure an analog voice port. Cisco PTC supports the modification of an analog voice port on a gateway and also supports the voice port parameters for the different signaling types described below:

•E&M Signaling—the most common form of an analog trunk circuit is the E&M interface, which uses special signaling paths that are separate from the trunk's audio path to convey information about the calls. Like a serial port, an E&M interface has a data terminal equipment/data communications equipment (DTE/DCE) type of reference. In the telecommunications world, the trunking side is similar to the DCE, and is usually associated with CO functionality. The router acts as this side of the interface. The other side is referred to as the signaling side, such as a DTE, and is usually a device such as a PBX. It is an analog connection, although an analog E&M circuit may be emulated on a digital line.

•FXS Signaling—an FXS interface connects the router or access server to end-user equipment such as telephones, Fax machines, or modems. The FXS interface supplies ring, voltage, and dial tone to the station and includes an RJ-11 connector for basic telephone equipment, key sets, and PBXs.

•FXO Signaling—an FXO interface is used for trunk or tie line connections to a PSTN CO or to a PBX that does not support E&M signaling (when local telecommunications authority permits). This interface is of value for off-premise station applications. A standard RJ-11 modular telephone cable connects the FXO voice interface card to the PSTN or PBX through a telephone wall outlet. FXO and FXS interfaces indicate on-hook or off-hook status and the seizure of telephone lines by one of two access signaling methods: loop start or ground start.

The configurable parameters on an analog voice port are:

•E&M Signaling:

–type of signaling (either wink-start, immediate-start, or delay-dial)

–CPTone

–the number of wires used for voice transmission

–type of E&M Interface (one of TypeI, TypeII, TypeIII, TypeIV)

–voice port description

•FXS Signaling:

–type of signaling (either loop-start or ground-start)

–CPTone

–ring frequency

–ring pattern

–voice port description

•FXO Signaling:

–type of signaling (either loop-start or ground-start)

–CPTone

–dial type (DTMF or Pulse)

–ring number

–voice port description

Digital Voice Port Configuration Overview

This section provides information on how to configure a digital voice port for SS7, ISDN-PRI, T1 CAS, and E1 R2 signaling.

Digital voice ports are found at the intersection of a packet voice network and a digital, circuit- switched telephone network. The digital voice port interfaces that connect the access server to T1 or E1 lines pass voice data and signaling between the packet network and the circuit-switched network.

The T1 or E1 lines that connect a telephony network to the digital voice ports on an access server contain channels for voice calls; a T1 line contains twenty four full-duplex channels or time slots, and an E1 line contains thirty. The signal on each channel is transmitted at 64kbps, a standard known as digital
signal 0 (DS0); the channels are known as DS0 channels. Some or all of the DS0 channels are grouped into a DS0 Group (or a logical voice port) facilitating similar configuration of all the DS0 Channels in a group.

There are two aspects to consider about signaling on digital lines: one aspect is the actual information about line and device states that is transmitted, and the second aspect is the method used to transmit the information on the digital lines. The actual information about line and device states is communicated over digital lines using signaling methods that emulate the methods used in analog circuit-switched networks: FXS, FXO, and E&M. The method used to transmit the information describes the way the emulated analog signaling is transmitted over digital lines, which may be common-channel signaling (CCS) or channel-associated signaling (CAS). CCS sends signaling information down a dedicated channel and CAS takes place within the voice channel itself. CAS signaling is also called robbed-bit signaling because user bandwidth is robbed by the network for signaling. A bit is taken from every sixth frame of voice data to communicate on- or off-hook status, wink, ground start, dialed digits, and other information about the call.

Adding a digital voice port to a gateway involves:

•configuring controller settings—specific line characteristics must be configured to match those of the PSTN line that is being connected to the voice port. These are typically configured in controller configuration mode. Voice port controller configuration includes:

–specify framing formats, clock sources, and line coding

–create a group of DS0 time slots that can be either a DS0 Group or PRI Group based upon the signaling method used.

•DS0 Group—defines the DS0 channels for E1 R2 signaling and the emulated analog signaling method (E&M or FXO or FXS) the router uses to connect to the PBX or PSTN

•PRI Group—defines the DS0 channels for ISDN or SS7 signaling.

–activate the controller

•creating a logical voice port and associating it to the DS0 Group, PRI Group, or CAS Group

•for SS7 signaling, configure the serial interface corresponding to the D-Channel, by specifying the parameters such as RLM group number, ISDN switch type, protocol emulation type, incoming voice type, CDP, fair queuing.

•configure basic voice port parameters—voice port configuration mode allows many of the basic voice call attributes to be configured to match those of the PSTN or PBX connection being made on this voice port. Normally, default parameter values for voice ports are sufficient for most networks. Depending upon the specifics of your particular network, however, you may need to adjust certain parameters that are configured on voice ports. These parameters include:

–Auto Cut-Through—allows you to connect to PBXs that do not provide an M-lead response

–sent/received bit patterns

–disconnect supervision parameters—used to indicate different methods of indicating a call disconnection

–FXO supervisory disconnect tone parameters

–voice call progress tone

–companding standard

–timeout parameters

–timing parameters

–voice quality tuning parameters (includes echo)

–voice activity detection (VAD) parameters.

Cisco PTC supports the creation of a digital voice port on a gateway. The supported signaling types on a digital voice port are: SS7, ISDN-PRI, T1 CAS, and E1 R2. For SS7 signaling, Cisco PTC also configures a nailed trunk on the signaling controller for each Ds0 belonging to the voice port. A nailed trunk is the representation of a gateway voice channel (essentially a Ds0) on the signaling controller.

Cisco PTC also supports the deletion of a digital voice port on a gateway. For SS7 signaling, Cisco PTC also removes the corresponding nailed trunks on the signaling controller, if any are configured. You are required to manually take the signaling controller resource out of service before performing the delete operation.

For non-SS7 signaling, Cisco PTC supports the modification of a digital voice port on a gateway.

For SS7 signaling, if the gateway and signaling controller are configured outside of Cisco PTC (for example, through CLI or an EMS), a digital voice port can be configured on the gateway, but not on the corresponding nailed trunk(s) on the signaling controller, or vice versa. Such a configuration is called an incomplete SS7 voice port configuration on a virtual gateway.

For SS7 signaling, Cisco PTC supports modification of a digital voice port on a gateway and the corresponding nailed trunk(s) on the signaling controller. If the SS7 voice port is incomplete, Cisco PTC allows you to delete the incomplete configuration.

Cisco PTC supports the assignment of a trunk label to an ISDN-PRI interface, NFAS group, T1/E1 CAS group, or FX0/FXS/E&M voice port.

For deletion of voice ports (both digital and analog), Cisco PTC notifies the Cisco Voice Routing Center application and requires a confirmation from Cisco VRC before committing the delete.

Voice Port Configuration Parameters

Cisco PTC allows you to browse existing DS3/DS1 lines through the Tree View pane (see the "Tree View Pane" section for a detailed description of the Tree View pane hierarchy) and to query a list of voice ports that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for a voice port is:
region -> virtual zone -> virtual gateway -> router -> DS3 -> DS1.

The Tree View pane is used as follows:

1. You select a DS1 line for adding voice port or

2. You select a virtual gateway to view all of the voice ports on the virtual gateway.

When you select the Voice Port service object in the Table of Contents pane, the following columns are displayed in the Configuration Listing pane:

•GW Name—gateway name

•DS3/DS1 Number—DS3/DS1 to which this voice port belongs

•Voice Port Number—voice port number

•Signaling Type—voice port signaling type

•Time Slots—time slots belonging to this voice port

•Trunk Group—trunk group ID

•SC Name—PGW2200/SC2200 name

•CICs—Circuit Identification Codes.

You must initially enter the mandatory parameters listed in Table 4-10 when you click the Add button in the Configuration Listing pane to add a voice port. Upon entering the mandatory parameter values, you click the Next button to enter the optional parameter values.

Table 4-10 Mandatory Voice Port Parameters - Add Operation 

Parameter	Value	Description
DS1 Line	string	The DS1 line upon which the voice port is to be configured.
Voice Port Type	enum {CAS-EnM, CAS-FXO, CAS-FXS, CAS-R2, ISDN-PRI, SS7}	The type of voice port.
NFAS Group Number	string	For an SS7 voice port, the NFAS Group that corresponds to this voice port. Note, the NFAS Group Number should be the same as the RLM Group Number for NFAS configuration on the IOS GW.

Common Voice Port Parameters

When you click the Modify button, you can modify the Common Voice Port related parameters listed in Table 4-11.

Table 4-11 Common Voice Port Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
DS0 Channels	Basic & GW	int (1-24 for T1, 1-30 for E1)		No
Controller Framing	Basic & Controller	enum for T1{SF, ESF} for E1 {CRC4, NO CRC4}	Type of framing on a DS1 link.	Yes
Controller Line Coding	Basic & Controller	enum for T1{ami, b8zs} for E1 {ami, hdb3}	Line encoding method for a DS1 link.	Yes
Controller Clock Source	Basic & Controller	enum {Free Running Clock, Internal Clock, Line(Recovered) Clock - Primary, Line(Recovered) Clock - Secondary}	Clock source for a DS1 link.	Yes
Controller Cable Length	Basic & Controller	enum {Long Gain26 -15dB pulse, Long Gain26 -22.5dBpulse, Long Gain26 -7.5dBpulse, Long Gain26 0dBpulse, Long Gain36 -15dB pulse, Long Gain36 -22.5dBpulse, Long Gain36 -7.5dBpulse, Long Gain36 0dBpulse, Short 0-133ft Short 134-266ft Short 267-399ft Short 400-533ft Short 534-655ft}	Cable length for a DS1 link.	Yes
Call Progress Tone	Basic & Controller	enum {Argentina, Australia, Austria, Belgium, Brazil, Canada, China, Columbia, Cyprus, Czech Republic, Denmark, Egypt, Finland, France, Germany, Ghana, Greece, Hong Kong, Iceland, India, Indonesia, Ireland, Israel, Italy, Japan, Jordan, Kenya, Korea Republic, Lebanon, Luxembourg, Malaysia, Mexico, Nepal, Netherlands, New Zealand, Nigeria, Norway, Pakistan, Panama, Peru, Philippines, Poland, Portugal, Russian Federation, Saudi Arabia, Singapore, Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, Taiwan, Thailand, Turkey, United Kingdom, United States, Venezuela, Zimbabwe} Default: United States		Yes
Companding Type	Basic & General	enum {u-law, a-law}		Yes
Description	Basic & General	string		Yes
Call Disconnect Timeout	Detail & Timeouts	int (0-120) Default: 60	Call disconnect time out value, in seconds.	Yes
Initial Digit Timeout	Detail & Timeouts	int (0-120) Default: 10	Number of seconds the system waits between the caller input of the initial digit and the subsequent digit of the dialed string.	Yes
Inter Digit Timeout	Detail & Timeouts		Number of seconds the system waits after the caller input of the initial digit or a subsequent digit of the dialed strings.	Yes
Ringing Timeout	Detail & Timeouts	int (5-60000), infinity) Default: 180	Duration, in seconds, the voice port allows ringing to continue if a call is not answered.	Yes
Wait Release Timeout	Detail & Timeouts	int (5-3600, infinity) Default: 30	Duration, in seconds, the voice port stays in the call failure state.	Yes
Clear Wait Timing	Detail & Timing	int (200-2000) Default:400	Minimum amount of time, in seconds.	Yes
Delay Duration Timing	Detail & Timing	int (100-5000) Default: 2000	Delay duration, in milliseconds, for delay dial signaling.	Yes
Delay Start Timing	Detail & Timing	int (20-2000) Default: 300	Minimum delay, in milliseconds, from outgoing seizure to out-dial address.	Yes
Digit Timing	Detail & Timing	int (50-100) Default: 100	DTMF digit signal duration, in milliseconds.	Yes
Guard OutTiming	Detail & Timing	int (300-3000) Default: 2000	Duration of the guard out period that prevents this port from seizing a remote FXS port before the remote port detects a disconnected signal.	Yes
Hookflash Out Timing	Detail & Timing	int (50-500) Default: 300	Hookflash duration, in milliseconds.	Yes
Inter Digit Timing	Detail & Timing	int (50-500) Default: 100	DTMF inter-digit duration, in milliseconds.	Yes
Pulse Timing	Detail & Timing	int (10-20) Default: 20	Pulse dialing rate, in pulses per second.	Yes
Pulse Digit Timing	Detail & Timing	int (10-20) Default: 20	Pulse digit signal duration, in milliseconds.	Yes
Pulse Inter-digit Timing	Detail & Timing	int (10-1000) Default: 500	Pulse dialing inter-digit duration, in milliseconds.	Yes
Wink Duration Timing	Detail & Timing	int (100-400) Default: 200	Maximum wink signal duration, in milliseconds, for a wink-start signal.	Yes
Wink Wait Timing	Detail & Timing	int (100-5000) Default: 200	Maximum wink wait duration, in milliseconds, for a wink-start signal.	Yes
Music Threshold	Detail & VAD	int (-70 to -30) Default: -38	Minimum decibel level of music played when calls are put on hold.	Yes
Comfort Noise	Detail & VAD	enum {enable, disable} Default: enable	Enable comfort noise creates background noise to fill silent gaps during the calls when VAD is enabled on voice dial peers.	Yes
Playout Delay Mode	Detail & Voice Quality	enum {adaptive, fixed} Default: adaptive	Mode in which the jitter buffer will operate for calls on this voice port.	Yes
Playout Nominal Delay	Detail & Voice Quality	int (0-250) Default: 10	Amount of playout delay, in milliseconds, applied at the beginning of a call by the jitter buffer in the gateway.	Yes
Playout Maximum Delay	Detail & Voice Quality	int (0-250) Default: 80	The jitter buffer upper limit or highest value to which the adaptive delay is set.	Yes
Playout Minimum Delay	Detail & Voice Quality	enum {default, low, high} Default: default	The jitter buffer lower limit or lowest value to which the adaptive delay is set.	Yes
Echo Cancellation	Detail & Voice Quality	enum {enable, disable} Default: enable	The cancellation of voice that is sent and received on the same interface.	Yes
Echo Cancellation Coverage	Detail & Voice Quality	enum {8, 16, 24, 32} Default: 16	Adjust the echo cancellation by this number.	Yes
Nonlinear Processing	Detail & Voice Quality	enum {enable, disable} Default: enable	Enable nonlinear processing in the echo canceller which shuts off any signal if no near-end speech is detected.	Yes
Input Gain	Detail & Voice Quality	int (-6 to 14) Default:0	The amount of gain, in decibels, to be inserted at the receiver side of the interface, increasing or decreasing the signal.	Yes
Output Attenuation	Detail & Voice Quality	int (-6 to 14) Default:0	The amount of attenuation, in decibels, at the transmit side of the interface, decreasing the signal.	Yes
Impedance	Detail & Voice Quality	enum {600c, 600r, 900c, complex1, complex2} Default: 600r	The terminating impedance of a voice port interface, which must match the specifications from the specific telephony system to which it is connected.	Yes

E1 R2 Specific Voice Port Parameters

When you click the Modify button, you can modify the E1 R2 Voice Port related parameters listed in Table 4-12.

Table 4-12 E1 R2 Voice Port Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Signaling Type	Basic & General	enum {E&M FGB, E&M FGD, E&M Immediate Start, FXS Ground Start, FXS Loop Start, R2 Analog, R2 Digital, and R2 Pulse} Default: E&M FGB	The type of CAS signaling.	No
DNIS Address Info	Basic & General	enum {enable, disable} Default: enable	DNIS address information.	No
Minimum ANI Digits	Detail & CAS Custom	int (0-64) Default: 0	Minimum number of collected ANI digits.	Yes
Maximum ANI Digits	Detail & CAS Custom	int (0-64) Default: 0	Maximum number of collected ANI digits.	Yes
Answer Signal Group	Detail & CAS Custom	enum {Group A, Group B} Default: Group B	Answer Signal Group.	Yes
Answer Signal Number	Detail & CAS Custom	int (1-15) Default: 6	Answer Signal number.	Yes
Caller Digits	Detail & CAS Custom	int (1-10) Default: 1	Number of digits the gateway needs to collect before it requests ANI or CallerID information.	Yes
CAS Custom Category	Detail & CAS Custom	int (1-15) Default: 1	Type of incoming call, which is mapped to a group signal number.	Yes
Country	Detail & CAS Custom	enum {Argentina, Australia, Brazil, Columbia, CostaRica, East Europe, Ecuador ITU, Ecuador LME, Greece, Guatemala, Honkkong China, Indonesia, Israel, ITU, Korea, Malaysia, New Zealand, Paraguay, Peru, Philippines, Saudi Arabia, Singapore, South Africa - PanAfTel, Telmex, Telnor, Thailand, Uruguay, Venezuela, Vietnam} Default: ITU	The local country settings to use with R2 signaling.	Yes
Minimum DNIS Digits	Detail & CAS Custom	int (0-64) Default: 0	Maximum number of collected DNIS digits.	Yes
Maximum DNIS Digits	Detail & CAS Custom	int (0-64) Default: 0	Maximum number of collected DNIS digits.	Yes
Group A Caller-id End	Detail & CAS Custom	enum {enable, disable} Default: disable	Send Group-A Caller ID End.	Yes
KA Signal Code	Detail & CAS Custom	int (0-15) Default: 0	KA signal code.	Yes
KD Signal Code	Detail & CAS Custom	int (0-15) Default: 0	KD signal code.	Yes
Metering	Detail & CAS Custom	enum {Enable, Disable} Default: Disable	Specifies sending a metering pulse when the gateway is making an outgoing call.	Yes
Non Compelled Congestion	Detail & CAS Custom	enum {B4} Default: B4	The noncompelled congestion signal which is sent to the central office when the gateway is congested and cannot accept the call.	Yes
ANI Timeout	Detail & CAS Custom	int (1-15)		Yes
Answer Guard Time	Detail & CAS Custom	int (1-1000)	Answer Guard Timer, in milliseconds.	Yes
Requested DNIS Digits	Detail & CAS Custom	int (1-65) Default: 1	The DNIS Digits to be collected before requesting category.	Yes
Caller Digits	Detail & CAS Custom	int (1-64) Default: 1	Specifies the number of digits the gateway needs to collect before it requests ANI or CallerID information.	Yes
DNIS Complete	Detail & CAS Custom	enum {default, enable, disable}		Yes
Call Guard Timer	Detail & CAS Custom	int (1000-2000) Default: 1000	Guard Timer value, in milliseconds.	Yes
Action on Guard Timer Expiry	Detail & CAS Custom	enum {Accept, Reject} Default: Reject	Action upon expiration of Guard Timer.	Yes
Debounce Time	Detail & CAS Custom	int (10-40) Default: 10	Debounce time, in milliseconds.	Yes
Double Answer	Detail & CAS Custom	enum {Enable, Disable} Default: Disable	Send Double Answer to block connect calls.	Yes
Invert ABCD A Bit	Detail & CAS Custom	enum {default, 0, 1}	Invert the A bits before transmit and after receive.	Yes
Invert ABCD B Bit	Detail & CAS Custom	enum {default, 0, 1}	Invert the B bits before transmit and after receive.	Yes
Invert ABCD C Bit	Detail & CAS Custom	enum {default, 0, 1}	Invert the C bits before transmit and after receive.	Yes
Invert ABCD D Bit	Detail & CAS Custom	enum {default, 0, 1}	Invert the D bits before transmit and after receive.	Yes
Suppress Proceed to Send Signal	Detail & CAS Custom	enum {Enable, Disable} Default: Disable	Suppress proceed-to-send signal for pulse line signaling.	Yes
Reanswer Time	Detail & CAS Custom	int (1000-120000) Default: 1000	Reanswer time, in milliseconds.	Yes
Release ACK to Clear Forward	Detail & CAS Custom	enum {Enable, Disable} Default: Disable	Send Release Acknowledgement to Clear Forward.	Yes
Release Guard Time	Detail & CAS Custom	int (1-2000) Default: 1	Released Guard timer, in milliseconds.	Yes
Seizure ACK Time	Detail & CAS Custom	int (2-100) Default: 2	Seizure to acknowledge time, in milliseconds.	Yes
Unused ABCD A Bit	Detail & CAS Custom	enum {default, 0, 1}	Specifies unused ABCD A bit values which can have a 0 or 1 value.	Yes
Unused ABCD B Bit	Detail & CAS Custom	enum {default, 0, 1}	Specifies unused ABCD B bit values which can have a 0 or 1 value.	Yes
Unused ABCD C Bit	Detail & CAS Custom	enum {default, 0, 1}	Specifies unused ABCD C bit values which can have a 0 or 1 value.	Yes
Unused ABCD D Bit	Detail & CAS Custom	enum {default, 0, 1}	Specifies unused ABCD D bit values which can have a 0 or 1 value.	Yes

CAS-E&M Specific Parameters

When you click the Modify button, you can modify the CAS-E&M Voice Port related parameters listed in Table 4-13.

Table 4-13 CAS-E&M Voice Port Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Signaling Type	Basic & General	enum {E&M FGB, E&M FGD, E&M Immediate Start, EnM FGB DTMF, EnM FGB DTMF DNIS, EnM FGB MF, EnM FGB MF DNIS} Default: E&M FGB	The type of E&M signaling.	No
Auto Cut Through	Basic & EnM	enum {enable, disable} Default: enable	Enables call completion when a PBX does not provide an M-lead response.	Yes
Signal Operation	Basic & EnM	enum {2-wire, 4-wire} Default: 2-wire	Selects a specific cabling scheme for EnM ports.	Yes
Interface Type	Basic & EnM	enum {Type I, Type II, Type III, Type V} Default: Type I	Specifies the EnM interface for a particular voice port.	Yes
ANI Type	Basic & EnM		Specifies ANI to be sent out when the T1-CAS signaling type is E&M-FGD.	Yes
Rx A Bit Condition	Basic & EnM	enum {Invert, Off, On}	Specifies the condition of the Receive A Bit.	Yes
Rx B Bit Condition	Basic & EnM	enum {Invert, Off, On}	Specifies the condition of the Receive B Bit.	Yes
Rx C Bit Condition	Basic & EnM	enum {Invert, Off, On}	Specifies the condition of the Receive C Bit.	Yes
Rx D Bit Condition	Basic & EnM	enum {Invert, Off, On}	Specifies the condition of the Receive D Bit.	Yes
Tx A Bit Condition	Basic & EnM	enum {Invert, Off, On}	Specifies the condition of the Transmit A Bit.	Yes
Tx B Bit Condition	Basic & EnM	enum {Invert, Off, On}	Specifies the condition of the Transmit B Bit.	Yes
Tx C Bit Condition	Basic & EnM	enum {Invert, Off, On}	Specifies the condition of the Transmit C Bit.	Yes
Tx D Bit Condition	Basic & EnM	enum {Invert, Off, On}	Specifies the condition of the Transmit D Bit.	Yes
Transmit Idle Bit Pattern	Basic & EnM	enum {0000, 0001, 0010, 0011, 0100, 0101, 0111, 1000, 1001, 1010, 1011, 1100, 1101, 1111} Default:T1 - 0000, E1 - 0001	Specifies the bit pattern applies to the transmit signaling bits for the idle state.	Yes
Transmit Seize Bit Pattern	Basic & EnM	enum {0000, 0001, 0010, 0011, 0100, 0101, 0111, 1000, 1001, 1010, 1011, 1100, 1101, 1111} Default:1111	Specifies the bit pattern applies to the transmit signaling bits for the seized state.	Yes
Receive Idle Bit Pattern	Basic & EnM	enum {0000, 0001, 0010, 0011, 0100, 0101, 0111, 1000, 1001, 1010, 1011, 1100, 1101, 1111} Default:0000	Specifies the bit pattern applies to the receive signaling bits for the idle state.	Yes
Receive Seize Bit Pattern	Basic & EnM	enum {0000, 0001, 0010, 0011, 0100, 0101, 0111, 1000, 1001, 1010, 1011, 1100, 1101, 1111} Default:1111	Specifies the bit pattern applies to the receive signaling bits for the seized state.	Yes
Ignore Rx A Bit	Basic & EnM	enum {YES, NO} Default: NO		Yes
Ignore Rx B Bit	Basic & EnM	enum {YES, NO} Default: NO		Yes

ISDN Specific Parameters

When you click the Modify button, you can modify the ISDN Voice Port related parameters listed in Table 4-14.

Table 4-14 ISDN Voice Port Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
NFAS D-Channel Role	Basic & ISDN	enum {none, primary, backup}	The operation of the D-Channel timeslot.	No
NFAS Interface Id	Basic & ISDN	int (0-8)	Provisioned NFAS interface value.	No
NFAS Group Id	Basic & ISDN	int (0-31)	Provisioned NFAS group value.	No
ISDN Switch Type	Basic & ISDN	enum {Primary 4ESS switch, Primary 5ESS switch, NorTel DMS-100, NETS, National ISDN, NTT, QSIG} Default: National ISDN	ISDN Interface switch type.	No
ISDN Protocol Emulation	Basic & ISDN	enum {Network, User} Default: User	Protocol (L2/L3) emulation network/user side.	No
ISDN Incoming Voice	Basic & ISDN	enum {data, modem} Default: data	Options for incoming calls.	No
ISDN Outgoing Voice	Basic & ISDN	enum {3.1 KHz-audio, speech}	Information transfer capability for voice calls.	No
ISDN BChannel Negotiate	Basic & ISDN	enum {disable, enable, enable-resend-setup} Default: disable	Enables the router to accept a B channel that is different from the B channel requested in the outgoing call setup message.	No
ISDN Send Alerting	Basic & ISDN	enum {disable, enable} Default: disable	Specifies that an Alerting message be sent before a Connect message when making ISDN calls.	No
ISDN Sending Complete	Basic & ISDN	enum {disable, enable} Default: disable	Specifies that the Sending Complete information element (IE) is included in the outgoing Setup message.	No
ISDN BChan Number Order	Basic & ISDN	enum {Ascending, Descending} Default: Descending		No
ISDN T310 Timer	Basic & ISDN	int (1-400000)	Number of milliseconds the router waits before disconnecting a call after receiving a Call Proceeding message.	No
ISDN TEI Negotiation	Basic & ISDN	enum {default, first-call, powerup}		No
ISDN Address Map: Address	Basic & ISDN	string	ISDN address to map.	No
ISDN Address Map: Plan	Basic & ISDN	enum {Data, ISDN, National, Reserved extension, Reserved value 10, Reserved value 11, Reserved value 12, Reserved value 13, Reserved value 14, Reserved value 2, Reserved value 5, Reserved value 6, Reserved value, TELEX, Unknown}		No
ISDN Address Map: Type	Basic & ISDN	enum {Abbreviated, International, National, Network, Reserved, Reserved value 5, Subscriber, Unknown}		No

SS7 Specific Parameters

When you click the Modify button, you can modify the SS7 Voice Port related parameter listed in Table 4-15.

Table 4-15 SS7 Voice Port Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
RLM Group Number	Basic & ISDN	int	RLM Group Number for this PRI.	No
SS7Path on SC2200	Basic & General	enum {consisting of the SS7 paths currently configured}	Specifies the SS7Path to be used as the source service for this PRI.	No
CIC Range	Basic & General	string	Specifies the range of CICs to be used for this PRI. The range is separated by "," or "-".	No
Trunk Number Range	Basic & General	string	Specifies the range of trunk numbers to be used for this PRI. The range is separated by "," or "-".	No

H.323 Voice Class Configuration

This section provides information about the H.323 Voice Class configuration capabilities provided by Cisco PTC. An overview of these capabilities, as well as a list of the H.323 configuration parameters supported by Cisco PTC on gateways are provided.

H.323 Configuration Overview

Cisco PTC supports the configuration of H.323 parameters on a gateway. This includes:

•H.323 SETUP timeout

•H.323 TCP timeout

H.323 Configuration Parameters

Cisco PTC allows you to query a list of H.323 Voice Class configurations that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for an H.323 Voice Class service object is:
region -> unassigned gateway, directory gatekeeper, virtual zone -> virtual gateway -> PGW2200/SC2200, router -> DS1 lines.

The Tree View pane is used to select a virtual gateway for configuring the H.323 Voice Class parameters on the gateway.

When you select the H.323 Voice Class service object in the Table of Contents pane, the following columns are displayed in the Configuration Listing pane:

•GW Name—gateway name

•Voice Class ID—H.323 voice class ID

•H225 Setup Timeout—H225 SETUP timeout value, in seconds

•H225 TCP Establish Timeout—H225 TCP connection timeout value, in seconds.

When you click the Modify button, you can modify the H.323 Voice Class related parameters listed in Table 4-16.

Table 4-16 H.323 Voice Class

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
H323 Voice Class ID	Basic & Common	int (1-10000)	H.323 Voice Class ID.	No
H225 Setup Timeout	Basic & Common	int (0-30)	H225 SETUP timeout value, in seconds.	Yes
H225 TCP Establish Timeout	Basic & Common	int (0-30)	H225 TCP connection timeout value, in seconds.	Yes

IVR/Voice XML Configuration

This section provides information about the IVR (Interactive Voice Response) configuration capabilities provided by Cisco PTC. An overview of these capabilities, as well as a list of the IVR configuration parameters supported by Cisco PTC on gateways are provided.

IVR Configuration Overview

IVR consists of simple voice prompts and digit collection to gather caller information for authenticating the user and identifying the destination. IVR applications can be customized to present different interfaces to the caller. IVR functionality includes the ability to:

•play out customized prompts

•collect account numbers and PIN numbers

•collect destination phone numbers

•perform AAA authentication using a variety of servers

•place calls

Voice XML allows you to write applications through XML pages. Similar to a web browser which presents the page contents visually, the Voice Browser on gateways can read VXML pages and can then run IVR applications which follow the links in the VXML. The VXML engine on the gateway recognizes that a particular E.164 address maps to a VXML web page and not a real PSTN device, fetches the page, and presents it in an audio fashion, through prompt-playing, RTSP streaming, or text-to-speech generation. It can also collect inputs through DTMF or speech recognition for further HTTP Get/Post operations.

Cisco PTC supports IVR/Voice XML configurations on a gateway that allow you to:

•create a voice application that interacts with the appropriate IVR script or HTTP URL

•specify parameters for the application, such as language, pin-length, retry-count, uid- length, and set-location.

IVR Configuration Parameters

Cisco PTC allows you to query a list of IVR configurations that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for an IVR Configuration service object is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used to select a virtual gateway for configuring the IVR on the gateway.

When you select the IVR service object in the Table of Contents pane, the following columns are displayed in the Configuration Listing pane:

•GW Name—gateway name

•Application—name of the application

•Location—location of the TCL file in URL format. Valid storage locations are: TFTP, FTP, and Flash

•Redirect Number—telephone number to which a call will be redirected (for example, the operator telephone number of the service provider) for the designated application.

When you click the Modify button, you can modify the IVR related parameters listed in Table 4-17.

Table 4-17 IVR Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
IVR Application Name	Basic & Common	string	Name of the application.	No
Location	Basic & Common	string (valid prefix - tftp:// and http://)	Location of the TCL file, in URL format.	Yes
Pin Length	Basic & Common	int (0-10)	Number of characters in the PIN for the designated application.	Yes
Retry Count	Basic & Common	int (1-5)	Number of times a caller is permitted to reenter the PIN for a designated application.	Yes
UID Length	Basic & Common	int (1-20)	Number of characters in the UID for the designated application and passes this information to the application.	Yes
Redirect Number	Basic & Common	string	Telephone number to which a call will be redirected (for example, the operator telephone number of the service provider) for the designated application.	Yes
Warning Time	Basic & Common	int (10-600)	Length of the warning period, in seconds, before the allowed calling time runs out.	Yes
IVR Application - tag	Basic & Common	int (0-9)		Yes
IVR Application - Language	Basic & Common	enum {English, Spanish, Mandarin, All}	Language of the audio file for the designated application and passes this information to the application.	Yes
IVR Application - Category	Basic & Common	int (0-4)	Category for the audio files for this location.	Yes
IVR Application - Location	Basic & Common	string (prefix - tftp:// or http:// and postfix - /)	Location of the TCL file in URL format. Valid storage locations are TFTP, FTP, and Flash.	Yes

DNIS Map Configuration

This section provides information about the DNIS (Dialed Number Identification Service) Map configuration capabilities provided by Cisco PTC. An overview of these capabilities, as well as a list of the DNIS Map configuration parameters supported by Cisco PTC on gateways are provided.

DNIS Map Configuration Overview

An Voice XML application can be created for each URL, and this application can be used in a Dial-peer configuration, similar to a TCL IVR application. However, creating Dial-peers for each DNIS (party number) is very expensive and does not scale. A DNIS Maps configuration provides an alternative to this problem. A DNIS Map is conceptually the same as a destination pattern of {A|B|C|D....} where A, B,... are a set of different DNISs. In other words, a set of E.164 numbers are mapped to VXML URLs under a single DNIS Map. Subsequently, during the dial peer configuration, these DNIS Maps can be used in a like manner as IVR TCL applications.

DNIS Map Configuration Parameters

Cisco PTC allows you to query a list of DNIS Map configurations that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for a DNIS Map Configuration service object is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used to select a virtual gateway for configuring the DNIS Map on the gateway.

When you select the DNIS Map service object in the Table of Contents pane, the following columns are displayed in the Configuration Listing pane:

•GW Name—gateway name

•DNIS Map Name—name of the DNIS map

•Type—one of: internal or external.

When you click the Modify button, you can modify the DNIS Map related parameters, for Internal Mode, listed in Table 4-18. You also can modify the DNIS Map related parameters, for External Mode, listed in Table 4-19.

Internal Mode

Table 4-18 DNIS Map Parameters - Internal Mode 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
DNIS Map Name	Basic & Common	string	Name of the DNIS Map.	No
DNIS Name URL - DNIS	Basic & Common	string	DNIS name.	Yes
DNIS Name URL - URL	Basic & Common	string (valid prefix: http:// or tftp:// or ftp:// valid postfix: .xml or .vxml)	URL.	Yes

External Mode

Table 4-19 DNIS Map Parameters - External Mode 

Parameter	Category	Values	Description	Modifiable on Router?
DNIS Map Name	Basic & Common	string	Name of the DNIS Map.	No
Subcommands File Location	Basic & Common	string (valid prefix: http:// or tftp:// or ftp://)	URL to a file containing subcommands.	Yes

Fax Configuration

This section provides information about the Fax configuration capabilities provided by Cisco PTC. An overview of these capabilities, as well as a list of the Fax configuration parameters supported by
Cisco PTC are provided.

Fax Configuration Overview

Cisco PTC support s the configuration of a T.37/T.38 Fax application on a gateway. This includes:

•On-ramp gateway—configure the Called, Subscriber Number, and Sending MTA (Mail Transfer Agent); gateway security; MDN (Message Delivery Notifications)

•Off-ramp gateway—configure the transmitting Subscriber Number, Fax transmission speed, receiving MTA, Fax header, and Fax cover page attributes; gateway security; MDN

•Both On-ramp and Off-ramp gateways—configure DSN (Delivery Status Notification); T.37/T.38 Fax gateway features such as Fax interface type and Fax protocol.

Fax Configuration Parameters

Cisco PTC allows you to query a list of Fax configurations that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for a Fax Configuration service object is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used to select a virtual gateway for configuring Fax support on the gateway.

When you select the Fax service object in the Table of Contents pane, the following columns are displayed in the Configuration Listing pane:

•GW Name—gateway name

•Operation Mode—gateway role; one of: On-ramp or Off-ramp

•Fax Interface—specifies the interface type; one of: modem or VFC

•Fax Protocol—specifies the global default fax protocol; one of: Cisco or T.38.

Fax On Ramp

When you click the Modify button, you can modify the Fax On Ramp related parameters listed in Table 4-20.

Table 4-20 Fax On Ramp Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Fax Interface	Basic & General	enum {Fax-Mail} For AS5300: enum {Modem, Fax-Mail} Default: Fax-Mail	Interface type.	Yes
Fax Protocol	Basic & General	enum {T.38} For AS5300: enum {Cisco, T.38} Default: T.38	Global default Fax protocol.	Yes
High Speed Redundancy	Basic & General	For AS5300: int (0-2) For AS5350 and 5400: int (0-3) Default: 0	The redundancy for sending redundant T.38 Fax packets in the high-speed V.17, V.27, V.29 T.4, or T.6 Fax machine image data.	Yes
Low Speed Redundancy	Basic & General	For AS5300: int (0-5) For AS5350 and 5400: int (0-7) Default: 0	The redundancy for sending redundant T.38 Fax packets in the low-speed V.21-based T.30 Fax machine protocol.	Yes
Called Subscriber Id	Basic & MTA	string Default: $d$	Number (called subscriber ID) that is displayed in the LCD of the sending Fax machine.	Yes
Host Name Sent	Basic & MTA	string	Originator host name of the E-mail Fax message.	Yes
User Name Sent	Basic & MTA	string Default: $s$	Originator username of the E-mail Fax message.	Yes
Destination Server	Basic & MTA	string	Destination server.	Yes
E-Mail Subject Sent	Basic & MTA	string	Text that appears in the Subject field of the E-mail Fax message.	Yes
Post Master	Basic & MTA	string	The sending address if the evaluated string is blank.	Yes
originPrefix	Basic & MTA	string	Additional identifying information to be prepended to the E-mail header.	Yes
Return Receipt Host Name	Basic & MTA	string	Address where MDNs are sent, if MDNs are requested.	Yes
Return Receipt User Name	Basic & MTA	string	User name where MDNs are sent, if MDNs are requested.	Yes

Fax Off Ramp

When you click the Modify button, you can modify the Fax Off Ramp related parameters listed in Table 4-21.

Table 4-21 Fax Off Ramp Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Fax Interface	Basic & General	For AS5300: enum {Modem, Fax-Mail} For AS5350 and 5400: enum {Fax-Mail} Default: Fax-Mail	Interface type.	Yes
Fax Protocol	Basic & General	For AS5300: enum {Cisco, T.38} For AS5350 and 5400: enum {T.38} Default: T.38	Global default Fax protocol.	Yes
High Speed Redundancy	Basic & General	For AS5300: int (0-2) For AS5350 and 5400: int (0-3) Default: 0	The redundancy for sending redundant T.38 Fax packets in the high-speed V.17, V.27, V.29 T.4, or T.6 Fax machine image data.	Yes
Low Speed Redundancy	Basic & General	For AS5300: int (0-5) For AS5350 and 5400: int (0-7) Default: 0	The redundancy for sending redundant T.38 Fax packets in the low-speed V.21-based T.30 Fax machine protocol.	Yes
Transmitting Subscriber Id	Basic & General	string Default: $d$	Number (transmitting subscriber ID) that is displayed in the LCD of the receiving Fax machine.	Yes
Fax Transmission Speed	Basic & General	enum {2400, 4800, 7200, 7600, 12000, 14400}	Maximum Fax speed.	Yes
Receive Aliases	Basic & MTA	Sequence of Aliases	Host name to be used as an alias for the off-ramp Cisco AS5300 universal access server device. Up to ten different aliases can be specified.	Yes
Generate MDN	Basic & MTA	enum {disable, enable} Default: disable	Configures the Cisco AS5300 universal access server to generate an MDN message when requested to do so.	Yes
Maximum Recipients	Basic & MTA	integer	Number of simultaneous SMTP recipients handled by this device. This is intended to limit the number of resources (modems) allocated for Fax transmissions.	Yes
Host Name Sent	Basic & MTA	string	Originator host name of the E-mail Fax message.	Yes
User Name Sent	Basic & MTA	string Default: $s$	Originator username of the E-mail Fax message.	Yes
Return Receipt Host Name	Basic & MTA	string	Address where MDNs are sent, if MDNs are requested.	Yes
Return Receipt User Name	Basic & MTA	string	User name where MDNs are sent, if MDNs are requested.	Yes
Center Header	Basic & FaxHeader	string	Defines the header information to be displayed in the center position. The keywords and arguments are: $d$—destination address. $s$—sender address $p$—page count. $t$—transmission time. string—inserts a personalized text string.	Yes
Right Header	Basic & FaxHeader	string	Defines the header information to be displayed in the right position. The keywords and arguments are: $d$—destination address. $s$—sender address. $p$—page count. $t$—transmission time. string—inserts a personalized text string.	Yes
Left Header	Basic & FaxHeader	string	Defines the header information to be displayed in the left position. The keywords and arguments are: $d$—destination address. $s$—sender address. $p$—page count. $t$—transmission time. string—inserts a personalized text string.	Yes
Cover Page Comment	Basic & CoverPage	string	Adds personalized text in the title field of the Fax cover sheet.	Yes
Show Detail	Basic & CoverPage	enum {Disable, Enable} Default: Disable	Prints all of the E-mail header information as part of the Fax cover sheet.	Yes
E-Mail Control	Basic & CoverPage	string	Configures the router to defer to the cover page setting in the E-mail header. For example, if the address has a parameter set to "cover=no" or "cover=yes", it will override the setting for the Fax send coverpage enable command.	Yes

AAA Voice Class Configuration

This section provides information about the AAA voice class configuration capabilities provided by Cisco PTC. An overview of these capabilities, as well as a list of the AAA voice class configuration parameters supported by Cisco PTC are provided.

AAA Voice Class Configuration Overview

Cisco PTC supports the configuration of AAA voice class on all the gateways within a region. A AAA voice class is essentially a customized AAA profile, that defines:

•a list of custom authentication servers

•a list of custom authorization servers

•a list of custom accounting servers

•the enabling/disabling of accounting generation for an incoming or outgoing call. When no option is specified, it applies to for both directions.

•accounting template for customized call detail reporting.

Note, a dial-peer references a voice class through its tag name.

AAA Voice Class Configuration Parameters

Allows you to query a list of AAA Voice Class configurations that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for a AAA Voice Class Configuration service object is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used to select a virtual gateway for configuring a AAA Voice Class on the gateway.

When you select the AAA Voice Class service object in the Table of Contents pane, the following columns are displayed in the Configuration Listing pane:

•Scope—region, zone, gateway, or gatekeeper

•Voice Class ID—AAA Voice Class Name

•Authentication Method—AAA Authentication Method List name used in this Voice Class

•Authorization Method—AAA Authorization Method List name used in this Voice Class

•Accounting Method—AAA Accounting Method List name used in this Voice Class.

You must initially enter the mandatory parameter listed in Table 4-22 when you click the Add button in the Configuration Listing pane to add a AAA Voice Class. Upon entering the mandatory parameter values, you click the Next button to enter the optional parameter values.

Table 4-22 Mandatory AAA Voice Class Parameter - Add Operation 

Parameter	Value	Description
Virtual Gateway Name	string	The virtual gateway upon which this AAA Voice Class configuration needs to be applied.

When you click the Modify button, you can modify the AAA Voice Class related parameters listed in Table 4-23.

Table 4-23 AAA Voice Class Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Voice Class Id	Basic & Common	integer	The Voice Class ID.	No
Authentication Method	Basic & Common	enum of all AAA Authentication Methods configured	Authentication method list name to be used for this voice class.	Yes
Authorization Method	Basic & Common	enum of all AAA Authorization Methods configured	Authorization method list name to be used for this voice class.	Yes
Accounting Method	Basic & Common	enum of all AAA Accounting Methods configured	Accounting method list name to be used for this voice class.	Yes
Accounting Template	Basic & Common	enum of all Call Accounting Templates configured	Accounting template list name to be used for this voice class.	Yes
Suppress Accounting	Basic & Common	enum {disable-inbound, disable-outbound, disable-both, enable}	Enables or disables accounting suppression for inbound, outbound, or both directions.	Yes

Call Accounting Template Configuration

This section provides information about the Call Accounting Template configuration capabilities provided by Cisco PTC. An overview of these capabilities, as well as a list of the Call Accounting Template configuration parameters supported by Cisco PTC are provided.

Call Accounting Template Configuration Overview

An accounting template specifies a selective set of call records to be sent to the RADIUS server. An accounting template is referenced by a AAA voice class or AAA gateway accounting by its accounting template tag.

Cisco PTC supports the configuration of an accounting template on all gateways within a region and allows you to force all gateways within the region to load or reload an accounting template.

Call Accounting Template Configuration Parameters

Cisco PTC allows you to query a list of Call Accounting Template configurations that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for a Call Accounting Template Configuration service object is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used to select a virtual gateway for configuring a Call Accounting Template on the gateway.

When you select the Call Accounting Template service object in the Table of Contents pane, the following columns are displayed in the Configuration Listing pane:

•Scope—gateway name

•CallAcctTemplate Name—Call Accounting Template name

•CallAcctTemplate URL—Call Accounting Template URL.

You must initially enter the mandatory parameter listed in Table 4-24 when you click the Add button in the Configuration Listing pane to add a Call Accounting Template. Upon entering the mandatory parameter values, you click the Next button to enter the optional parameter values.

Table 4-24 Mandatory Call Accounting Template Parameter - Add Operation 

Parameter	Value	Description
Virtual Gateway Name	string	The virtual gateway upon which this Call Accounting Template configuration needs to be applied.

When you click the Modify button, you can modify the Call Accounting Template related parameters listed in Table 4-25.

Table 4-25 Call Accounting Template Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Call Accounting Template: Name	Basic & Common	string	The name of the call accounting template.	No
Call Accounting Template: URL	Basic & Common	string	The location of this accounting template. Should start with ftp://, tftp:// or http:// and end with cdr.	Yes

Voice Parameters Configuration

Allows you to query a list of Voice Parameters configurations that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for a Voice Parameters Configuration service object is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used to select a virtual gateway for configuring Voice Parameters on the gateway.

When you select the Voice Parameters service object in the Table of Contents pane, the following columns are displayed in the Configuration Listing pane:

•Scope—gateway name

•Signaling Forward Type—global setting for signal forwarding

•Call Start Type—global setting for H.323 call start procedures

You must initially enter the mandatory parameter listed in Table 4-26 when you click the Add button in the Configuration Listing pane to add Voice Parameters to a gateway. Upon entering the mandatory parameter values, you click the Next button to enter the optional parameter values.

Table 4-26 Mandatory Voice Parameters Parameter - Add Operation 

Parameter	Value	Description
Virtual Gateway Name	string	The virtual gateway upon which this Voice Parameters configuration needs to be applied.

When you click the Modify button, you can modify the Voice Parameters related parameters listed in Table 4-27.

Table 4-27 Voice Parameters Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Signaling Forward	Basic & Common	enum {None, Unconditional}	Global setting for signal forwarding.	Yes
H323 Call Start	Basic & Common	enum {Fast-Start, Slow-Start} Default: Fast-Start	Global setting for H.323 Call Start procedures.	Yes
Gateway Accounting	Basic & Common	list {H323, H3232-VSA, VoIP, Syslog}	Type of VoIP gateway accounting.	Yes
Accounting Method	Basic & Common	enum of all AAA Accounting Methods configured Default: h323	Accounting method used for gateway accounting.	Yes
Call Accounting Template	Basic & Common	enum of all Call Accounting Templates configured	Accounting template used for gateway accounting. Use callhistory-detail to send all voice attributes for accounting.	Yes
Accounting Session Id	Basic & Common	enum {enable, disable}	Overload acct-session-id attribute with voice VSAs.	Yes
H323 Remote Id Resolved	Basic & Common	enum {enable, disable}	Resolve H323-remote-id attribute and send.	Yes
Suppress Accounting	Basic & Common	enum {POTS, VoIP, Both}	Enables or disables accounting for a call leg on POTs or VoIP dial peer.	Yes

NTP Configuration

This section provides information about the Network Time Protocol (NTP) configuration capabilities provided by Cisco PTC. An overview of these capabilities, as well as a list of the NTP configuration parameters supported by Cisco PTC are provided.

NTP Configuration Overview

NTP is a protocol designed to time-synchronize a network of machines. NTP services are disabled on all interfaces by default. Cisco PTC supports NTP configuration on a region. The NTP configurations are applied to all of the gateways, gatekeepers, and directory gatekeepers within the region.

The following NTP configurations are supported:

•configuring NTP Associations - An NTP association can be a peer association (meaning that this system is willing to either synchronize to the other system or to allow the other system to synchronize to it), or it can a server association (meaning that only this system will synchronize to the other system, and not the other way around). NTP association can be either Poll-Based or Broadcast-Based.

•configuring an NTP Access Group - based on IP addresses grant or deny certain access privileges to an entire network, a subnet within a network, or a host within a subnet

•configuring NTP Authentication - encrypted authentication scheme using authentication keys

•updating the hardware clock (system calendars) periodically with the software clock.

NTP Configuration Parameters

Cisco PTC allows you to browse a list of NTP configurations that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for an NTP configuration is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used as follows:

1. You select a virtual gateway for configuring the NTP on the gateway.

2. You select a virtual gateway to view the NTP configuration on the gateway.

When you select the NTP service object in the Table of Contents pane, the following columns are displayed in the Configuration Listing pane:

•Scope—region, zone, gateway, or gatekeeper

•NTP ID—NTP configuration ID

•Association Mode—one of: NTP-Client-Poll, NTP-Client-Broadcast, NTP-Peer-Poll, NTP-Server-Broadcast, NTP-Server, Manual

•NTP IP Address—NTP server IP address.

You must initially enter the mandatory parameters listed in Table 4-28 when you click the Add button in the Configuration Listing pane to add an NTP configuration. Upon entering the mandatory parameter values, you click the Next button to enter the optional parameter values.

Table 4-28 Mandatory NTP Parameters - Add Operation 

Parameter	Value	Description
Scope	string {Region, Virtual Zone, Virtual Gateway, Gatekeeper}	The scope onto which this NTP configuration is to be applied.
Type	enum {Client-Poll, Peer-Poll, Client-Broadcast, Server, Server-Broadcast, Manual}	The type of NTP configuration.

NTP Client Poll or Peer Poll

When you click the Modify button, you can modify the NTP Client Poll or Peer Poll related parameters listed in Table 4-29.

Table 4-29 NTP Client Poll or Peer Poll Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Server IPAddress	Basic & GW	string (IPAddress)	The IP address of the server providing the clock synchronization.	No
NTP Version	Basic & General	enum {1-3) Default: 3	NTP protocol version number.	No
Authentication Key	Basic & General	int	Authentication key.	No
Source Interface	Basic & General	enum {all interfaces on router} For Operations on Zone and Region: enum {Any Ethernet, Any FastEthernet, Any Ethernet or FastEthernet}	Interface from which to pick up the IP source address.	No
Prefer	Basic & General	enum {enabled, disabled}	Prefer this peer when possible.	Yes
Access Group Table - Access Group Mode	Detail & General	enum {queryOnly, serverOnly, server, peer}	Access control to the NTP services.	Yes
Access Group Table - Access List	Detail & General	int (1- 99)	Number of a standard IP access list.	Yes
Authentication Table - Authentication Key	Detail & General	int (0-4294967295000)	Authentication key number.	Yes
Authentication Table - MD5 Key	Detail & General	integer	MD5 key value.	Yes
Authentication Table - Authentication Type	Detail & General	integer	Authentication type.	Yes
Trust Key	Detail & General	list of integers	Key number of the authentication key to be trusted.	Yes
Update Calendar	Basic & General	enum {enable, disable}	Update the software calendar or not.	Yes

NTP Client Broadcast

When you click the Modify button, you can modify the NTP Client Broadcast related parameters listed in Table 4-30.

Table 4-30 NTP Client Broadcast Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Source Interface	Basic & General	enum {all interfaces on router}	The interface from which to pick up the IP source address.	No
Broadcast Delay	Basic & General	int (0-999999) Default: 3000	Round-trip time for NTP broadcasts.	Yes
Access Group Table - Access Group Mode	Detail & General	enum {queryOnly, serverOnly, server, peer}	Access control to the NTP services.	Yes
Access Group Table - Access List	Detail & General	int (1- 99)	Number of a standard IP access list.	Yes
Authentication Table - Authentication Key	Detail & General	int (0-4294967295000)	Authentication key number.	Yes
Authentication Table - MD5 Key	Detail & General	integer	MD5 key value.	Yes
Authentication Table - Authentication Type	Detail & General	integer	Authentication type.	Yes
Trust Key	Detail & General	list of integers	Key number of the authentication key to be trusted.	Yes
Update Calendar	Basic & General	enum {enable, disable}	Update the software calendar or not.	Yes

NTP Server Broadcast

When you click the Modify button, you can modify the NTP Server Broadcast related parameters listed in Table 4-31.

Table 4-31 NTP Server Broadcast Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Server Broadcast Table - NTP Version	Basic & General	enum {1-3} Default: 3	NTP protocol version number.	Yes
Server Broadcast Table - Server Broadcast Key	Basic & General	integer	Broadcast authentication key.	Yes
Server Broadcast Table - Destination IP Address	Basic & General	string (IPAddress)	Destination broadcast IP address.	Yes
Source Interface	Basic & General	enum {all interfaces on router} For Operations on Zone and region: enum {Any Ethernet, Any FastEthernet, Any Ethernet or FastEthernet}	Interface from which to pick up the IP source address.	No
Broadcast Delay	Basic & General	int (0-999999) Default: 3000	Round-trip time for NTP broadcasts.	Yes
Access Group Table - Access Group Mode	Detail & General	enum {queryOnly, serverOnly, server, peer}	Access control to the NTP services.	Yes
Access Group Table - Access List	Detail & General	int (1- 99)	Number of a standard IP access list.	Yes
Authentication Table - Authentication Key	Detail & General	int (0-4294967295000)	Authentication key number.	Yes
Authentication Table - MD5 Key	Detail & General	integer	MD5 key value.	Yes
Authentication Table - Authentication Type	Detail & General	integer	Authentication type.	Yes
Trust Key	Basic & General	list of integers	Key number of the authentication key to be trusted.	Yes
Update Calendar	Basic & General	enum {enable, disable} Default: disable	Update the software calendar or not.	Yes

NTP Server

When you click the Modify button, you can modify the NTP Server related parameters listed in Table 4-32.

Table 4-32 NTP Server Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Access Group Table - Access Group Mode	Detail & General	enum {queryOnly, serverOnly, server, peer}	Access control to the NTP services.	Yes
Access Group Table - Access List	Detail & General	int (1- 99)	Number of a standard IP access list.	Yes
Authentication Table - Authentication Key	Detail & General	int (0-4294967295000)	Authentication key number.	Yes
Authentication Table - MD5 Key	Detail & General	integer	MD5 key value.	Yes
Authentication Table - Authentication Type	Detail & General	integer	Authentication type.	Yes
Trust Key	Basic & General	int	Key number of the authentication key to be trusted.	Yes
NTP Stratum	Basic & General	int (0-15)	NTP stratum number.	Yes
Update Calendar	Basic & General	enum {enable, disable} Default: disable	Update the software calendar or not.	Yes

Security Server Group Configuration

Allows you to query a list of Security Server Group configurations that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for a Security Server Group configuration service object is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used to select a virtual gateway for configuring a Security Server Group on the gateway.

When you select the Security Server Group service object in the Table of Contents pane, the following columns are displayed in the Configuration Listing pane:

•Scope—region, zone, gateway, or gatekeeper

•Server Group—RADIUS/TACACS+ Server Group name

•Protocol—RADIUS or TACACS+

•Hosts—RADIUS or TACACS+ hosts belonging to this Server Group.

You must initially enter the mandatory parameters listed in Table 4-33 when you click the Add button in the Configuration Listing pane, to add a Security Server Group. Upon entering the mandatory parameter values, you click the Next button to enter the optional parameter values.

Table 4-33 Mandatory Security Server Group Parameters - Add Operation 

Parameter	Value	Description
Scope	string {Region, Virtual Zone, Virtual Gateway, Gatekeeper}	The scope onto which this Security Server Group configuration is to be applied.
Type	enum {Server-Group, No Server-Group}	The type of Security Server configuration.
Protocol	enum {RADIUS, TACACS+}	The security protocol.

When you click the Modify button, you can modify the Security Server Group - RADIUS related parameters listed in Table 4-34.

Table 4-34 Security Server Group - RADIUS Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
RADIUS Hosts - HostName	Basic & General	string	Hostid/IP address of the remote RADIUS server host.	No
RADIUS Hosts - Authentication Port	Basic & General	integer	UDP port on the RADIUS server to be used solely for authentication.	No
RADIUS Hosts - Accounting Port	Basic & General	integer	UDP port on the RADIUS server to be used solely for accounting.	No
RADIUS Hosts - Timeout	Basic & General	int (1-1000)	The number of seconds a router waits for a reply to a RADIUS request before retransmitting the request.	No
RADIUS Hosts - RetransmitRetries	Basic & General	int (1-1000) Default: 3	The number of times the router transmits each RADIUS request to the server before giving up.	No
RADIUS Hosts - KeyType	Basic & General	enum {unencrypted, encrypted, none}	Use the unencrypted option to configure an unencrypted shared secret. Use the encrypted option to configure an encrypted shared secret.	No
RADIUS Hosts - Key	Basic & General	string	The shared secret text string used between the router and a RADIUS server.	No
RADIUS Server Group Deadtime	Basic & General	integer	The deadtime value, in minutes.	Yes

When you click the Modify button, you can modify the Security Server Group - TACACS+ related parameters listed in Table 4-35.

Table 4-35 Security Server Group - TACACS+ Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
TACACS+ Hosts - HostName	Basic & General	string	Hostid/IP address of the remote RADIUS server host.	No
TACACS+ Hosts - Timeout	Basic & General	int (1-1000)	The number of seconds a router waits for a reply to a RADIUS request before retransmitting the request.	No
TACACS+ Hosts - Key	Basic & General	string	The shared secret text string used between the router and a RADIUS server.	No

Security Server End Point Configuration

Allows you to query a list of Security Server End Point configurations that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for a Security Server End Point configuration service object is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used to select a virtual gateway for configuring a Security Server End Point on the gateway.

When you select the Security Server End Point service object in the Table of Contents pane, the following columns are displayed in the Configuration Listing pane:

•Scope—region, zone, gateway, or gatekeeper

•Protocol—RADIUS or TACACS+

•Host Name—host name of the RADIUS or TACACS+ server

•Authentication Port—host name of the RADIUS or TACACS+ server

•Accounting Port—accounting port

•Server Group—Security Server Group name if this end point belongs to a Security Server Group.

You must initially enter the mandatory parameters listed in Table 4-36 when you click the Add button in the Configuration Listing pane, to add a Security Server End Point. Upon entering the mandatory parameter values, you click the Next button to enter the optional parameter values.

Table 4-36 Mandatory Security Server End Point Parameters - Add Operation 

Parameter	Value	Description
Scope	string {Region, Virtual Zone, Virtual Gateway, Gatekeeper}	The scope onto which this RADIUS Group configuration is to be applied.
Type	enum {Server-Group, No Server-Group}	The type of Security Server configuration.
Protocol	enum {RADIUS, TACACS+}	The security protocol.

When you click the Modify button, you can modify the Security Server End Point RADIUS related parameters listed in Table 4-37.

Table 4-37 Security Server End Point - RADIUS Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
RADIUS Hosts - HostName	Basic & General	string	Hostid/IP address of the remote RADIUS server host.	No
RADIUS Hosts - Authentication Port	Basic & General	integer	UDP port on the RADIUS server to be used solely for authentication.	No
RADIUS Hosts - Accounting Port	Basic & General	integer	UDP port on the RADIUS server to be used solely for accounting.	No
RADIUS Hosts - Timeout	Basic & General	int (1-1000)	The number of seconds a router waits for a reply to a RADIUS request before retransmitting the request.	No
RADIUS Hosts - RetransmitRetries	Basic & General	int (1-1000) Default: 3	The number of times the router transmits each RADIUS request to the server before giving up.	No
RADIUS Hosts - KeyType	Basic & General	enum {unencrypted, encrypted, none}	Use the unencrypted option to configure an unencrypted shared secret. Use the encrypted option to configure an encrypted shared secret.	No
RADIUS Hosts - Key	Basic & General	string	The shared secret text string used between the router and a RADIUS server.	No
RADIUS Server Group Deadtime	Basic & General	integer	The deadtime value, in minutes.	Yes

When you click the Modify button, you can modify the Security Server End Point TACACS+ related parameters listed in Table 4-34.

Table 4-38 Security Server End Point - TACACS+ Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
TACACS+ Hosts - HostName	Basic & General	string	Hostid/IP address of the remote RADIUS server host.	No
TACACS+ Hosts - Timeout	Basic & General	int (1-1000)	The number of seconds a router waits for a reply to a RADIUS request before retransmitting the request.	No
TACACS+ Hosts - Key	Basic & General	string	The shared secret text string used between the router and a RADIUS server.	No

AAA Configuration

This section provides information about the AAA configuration capabilities provided by Cisco PTC. An overview of these capabilities as well as a list of the AAA configuration parameters supported by
Cisco PTC are provided.

AAA Configuration Overview

AAA represents Authentication, Authorization, and Accounting features which are required in a VoIP gateway:

•Authentication—is based on RADIUS and is performed on a gateway (as opposed to a gatekeeper). User account and PIN information is collected by the IVR application and is passed to the AAA interface. The AAA interface then makes a RADIUS authentication request with the given information and returns to the IVR application a status of success or failure. RADIUS is an IETF protocol based on UDP. It functions by exchanging a set of attribute/value pairs between the client, here a VoIP gateway and a RADIUS server. Standard RADIUS server implementations include Cisco Secure, Cisco UCP, Livingston, and Merit.

•Authorization—an authenticated user is authorized. There is no authorization of specific user capabilities for the service provider voice applications.

•Accounting—uses a basic start-stop method and standard RADIUS attributes where possible. Data items are collected for each call leg that gets created on the gateway. Each call that is made through the gateway consists of an incoming and an outgoing call leg. The call leg information that is sent by the gateway(s) can be correlated by their connection ID, which is the same for all call legs of a connection.

Cisco PTC supports RADIUS configuration on all the gateways, gatekeepers, and directory gatekeepers in a region. Cisco PTC supports the following RADIUS configurations:

•enabling or disabling of AAA security services globally on the device

•creation and removal of RADIUS server groups

•defining the RADIUS server IP address and parameters such as deadtime, radius server key, retransmit, and timeout.

Cisco PTC supports the following Authentication configurations:

•login authentication method

•only h.323 method-list name with RADIUS as the method type on Cisco devices running the Cisco IOS XU release. With the Cisco IOS XU release, the method-list name is not limited to just h.323, any string is acceptable.

•supports the use of all or a group of RADIUS servers (called Security Server Group) for authentication.

Cisco PTC supports the following Authorization configurations:

•supports authorization types: network, exec, commands, reverse-access

•supports only h.323 method-list name with RADIUS as the method type

•supports the use of all or group of RADIUS servers for authorization.

Cisco PTC supports the following Accounting configurations:

•accounting types: system, network, exec, connection, commands

•only h.323 method-list name with RADIUS as the method type on Cisco devices running the Cisco IOS XU release. With the Cisco IOS XU release, the method-list name is not limited to just h.323, any string is acceptable.

•broadcast accounting that allows accounting information to be sent to multiple AAA/Billing servers simultaneously. This functionality allows service providers to send accounting information to their own private AAA/Billing servers and to the AAA/Billing servers of their end customers. It also provides redundant billing information for voice applications.

•accounting record types: start-stop, stop-only, none

•the use of all or a group of RADIUS/Billing servers for accounting.

AAA Configuration Parameters

Cisco PTC allows you to query a list of AAA (Authentication, Authorization, Accounting) configurations that meet a filter criterion. The query results are displayed in a tabular format in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for a AAA Configuration service object is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used to select a virtual gateway for configuring AAA on the gateway.

When you select the AAA service object in the Table of Contents pane, the following information is displayed in the Configuration Listing pane:

•Scope—region, zone, gateway, or gatekeeper

•Method Name—AAA Method List Name

•Method Type—one of: Login Authentication, Authorization, Accounting, or Fax Security

•Methods—list of RADIUS hosts (separated by semi-colons, if more than one).

You must initially enter the mandatory parameters listed in Table 4-39 when you click the Add button in the Configuration Listing pane, to add a AAA configuration. Upon entering the mandatory parameter values, you click the Next button to enter the optional parameter values.

Table 4-39 Mandatory AAA Parameters - Add Operation 

Parameter	Value	Description
Scope	string {Region, Virtual Zone, Virtual Gateway, Gatekeeper}	The scope onto which this AAA configuration is to be applied.
AAA Type	enum {Server-Group, No Server-Group}	The type of AAA.
Fax Security Type	enum {On-Ramp, Off-Ramp}	The type of Fax security.

AAA Login Authentication

When you click the Modify button, you can modify the Login Authentication related AAA parameters listed in Table 4-40.

Table 4-40 AAA - Login Authentication Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Login Authentication Method List Name	Basic & Authentication	string	A local authentication list.	No
Login Authentication Methods	Basic & Authentication	list {all RADIUS Server Groups configured on the router, RADIUS, enable, line, local, local-case, none}		No
Login Authentication Password Prompt	Basic & Authentication	string	The default text displayed when a user is prompted to enter a password.	Yes
Authentication Banner	Basic & Authentication	string	Personalized login banner.	Yes
Authentication Fail Banner	Basic & Authentication	string	Personalized authentication fail message.	Yes

AAA Authorization

When you click the Modify button, you can modify the Authorization related AAA parameters listed in Table 4-41.

Table 4-41 AAA - Authorization Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Authorization Method List Name	Basic & Authorization	string		No
Authorization Type	Basic & Authorization	enum {Network, Auth-proxy, Commands, EXEC, Network, Reverse Access, Configuration, IP Mobile} Default: Network		No
Command Level	Basic & Authorization	int (1-12)	If the Authorization Type is Commands, a Command Level value must be specified.	No
Authorization Methods	Basic & Authorization	list {all RADIUS Server Groups configured on the router, RADIUS, enable, line, local, local-case, none}		No

AAA Accounting

When you click the Modify button, you can modify the Accounting related AAA parameters listed in Table 4-42.

Table 4-42 AAA - Accounting Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Accounting Method List Name	Basic & Accounting	string		No
Accounting Type	Basic & Accounting	seqof {Network, Commands, Connection, EXEC, Resource, System} Default: Network		No
Accounting Methods	Basic & Accounting	list {all RADIUS Server Groups configured on the router, RADIUS}		No
Accounting Record Type	Basic & Accounting	enum {start-stop, stop-only, none} Default: stop-only	For minimal accounting, use stop-only, which instructs the specified method (RADIUS or TACACS+) to send a stop record accounting notice at the end of the requested user process. For more accounting information, use start-stop to send a start accounting notice at the beginning of the requested event and a stop accounting notice at the end of the event. To stop all accounting activities on this line or interface, use none.	No
Broadcast Mode	Basic & Accounting	enum {enable, disable} Default: disable		No

Interface Configuration

This section provides information about the Interface configuration capabilities provided by Cisco PTC. An overview of these capabilities, as well as a list of the Interface configuration parameters supported by Cisco PTC are provided.

Interface Configuration Overview

Cisco PTC supports Interface configurations on gateways. The interface properties described below are configurable by Cisco PTC.

Interfaces are configured as part of the first time configuration of any Cisco IOS device. Cisco routers support the following Interface configurations:

•IP address for that interface

•LAN interface type (Ethernet, Fast Ethernet, or Gigabit Ethernet)

•Media type (aui or 10 baseT for Ethernet; aui or 100 baseX for Fast Ethernet)

•Duplex (full for Ethernet; full, half, or auto for Fast Ethernet; or Gigabit Ethernet)

•Speed (10, 100, or auto for Fast Ethernet)

•Parameters common to all interface types, such as description, MOP (Maintenance Operation Protocol), hold-queue length, bandwidth, delay, keepalive, transmit queue size, MTU (Maximum Transmission Unit), and encapsulation type (arpa, sap or snap).

Interface Configuration Parameters

Cisco PTC allows you to query a list of Interface configurations (Ethernet, Fast-Ethernet, Gigabit-Ethernet, Loopback) that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for an Interface Configuration service object is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used to select a virtual gateway for configuring the appropriate interface on the gateway.

When you select the Interface service object in the Table of Contents pane, the following information is displayed in the Configuration Listing pane:

•GW Name—gateway name

•Interface ID—Unique interface ID

•Interface Type—one of: Ethernet, Fast-Ethernet, Gigabit-Ethernet, Loopback

•Interface IP Address—interface IP address.

You must initially enter the mandatory parameters listed in Table 4-43 when you click the Add button in the Configuration Listing pane, to add an interface. Upon entering the mandatory parameter values, you click the Next button to enter the optional parameter values.

Table 4-43 Mandatory Interface Parameters - Add Operation 

Parameter	Value	Description
GW/GK Name	string	The scope onto which this interface configuration is to be applied.
Type	enum {Ethernet, Fast-Ethernet, Gigabit-Ethernet, Loopback}	The type of interface.

Ethernet Interface

When you click the Modify button, you can modify the Ethernet related Interface parameters listed in Table 4-44.

Table 4-44 Ethernet Interface Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Interface Id	Basic & Common	integer	Interface ID.	No
In Hold Q Length	Basic & Common	int (0-4096)	Maximum number of packets allowed in the In Hold queue.	Yes
Out Hold Q Length	Basic & Common	int (0-4096)	Maximum number of packets allowed in the Out Hold queue.	Yes
Bandwidth	Basic & Common	int (1-10000000)	Bandwidth value, in kilobytes.	Yes
Delay	Basic & Common	int (1-16777215)	Delay value for the interface.	Yes
Keepalive Timer	Basic & Common	int (0-32767)	Adjusts the frequency that Cisco IOS sends messages to itself (Ethernet and Token Ring) or to the other end (HDLC-serial and PPP-serial links) to ensure that a network interface is alive for a specified interface.	Yes
IP Address	Basic & LAN	string	IP address for this interface.	Yes
Subnet Mask	Basic & LAN	string	Subnet mask for this interface.	Yes
Media Type	Basic & LAN	enum {AUI, 10baseT} Default: AUI	Physical connection on the interface.	Yes
Squelch	Basic & LAN	enum {Normal, Reduced} Default: Normal	Specifies whether to extend the Ethernet twisted-pair 10BASE-T capability beyond the standard 100 meters.	Yes

Fast Ethernet Interface

When you click the Modify button, you can modify the Fast Ethernet related Interface parameters listed in Table 4-45.

Table 4-45 Fast Ethernet Interface Parameters 

Parameter	Category	Values	Description	Modifiable on Router?
Interface ID	Basic & Common	integer	Interface ID.	No
In Hold Q Length	Basic & Common	int (0-4096)	Maximum number of packets allowed in the in hold queue.	Yes
Out Hold Q Length	Basic & Common	int (0-4096)	Maximum number of packets allowed in the out hold queue.	Yes
Bandwidth	Basic & Common	int (1-10000000)	Bandwidth value, in kilobytes.	Yes
Delay	Basic & Common	int (1-16777215)	Delay value for the interface.	Yes
Keepalive Timer	Basic & Common	int (0-32767)	Adjusts the frequency that Cisco IOS sends messages to itself (Ethernet and Token Ring) or to the other end (HDLC-serial and PPP-serial links) to ensure that a network interface is alive for a specified interface.	Yes
MTU	Basic & Common	integer	Adjusts the maximum packet size or MTU size, in bytes.	Yes
IP Address	Basic & LAN	string (IPAddress)	IP address for this interface.	No
Subnet Mask	Basic & LAN	string (IPAddress)	Subnet mask for this interface.	No
Media Type	Basic & LAN	enum {100baseX, MII (Media Independent Interface} 5800: enum {MII} Default: MII	Physical connection on the interface.	Yes
Duplex	Basic & LAN	enum {auto, full, half} Default: half	Duplex operation on the interface.	Yes
Speed	Basic & LAN	enum {10, 100, auto} Default: 100	Speed of a Fast Ethernet interface.	Yes

Gigabit Ethernet Interface

When you click the Modify button, you can modify the Gigabit Ethernet related Interface parameters listed in Table 4-46.

Table 4-46 Gigabit Ethernet Interface Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Interface Id	Basic & Common	integer	Interface ID.	No
In Hold Q Length	Basic & Common	int (0-4096)	Maximum number of packets allowed in the In Hold queue.	Yes
Out Hold Q Length	Basic & Common	int (0-4096)	Maximum number of packets allowed in the Out Hold queue.	Yes
Bandwidth	Basic & Common	int (1-10000000)	Bandwidth value, in kilobytes.	Yes
Delay	Basic & Common	int (1-16777215)	Delay value for the interface.	Yes
Keepalive Timer	Basic & Common	int (0-32767)	Adjusts the frequency that Cisco IOS sends messages to itself (Ethernet and Token Ring) or to the other end (HDLC-serial and PPP-serial links) to ensure that a network interface is alive for a specified interface.	Yes
MTU	Basic & Common	integer	Adjusts the maximum packet size or MTU size, in bytes.	No
IP Address	Basic & LAN	string	IP address for this interface.	No
Subnet Mask	Basic & LAN	string	Subnet mask for this interface.	No
Media Type	Basic & LAN	enum {AUI, 10baset, 100baset, and Media Independent Interface (MII)} Default: AUI	Physical connection on the interface.	Yes
Duplex	Basic & LAN	enum {auto, full, half} Default: half	Duplex operation on the interface.	Yes

Loopback Interface

When you click the Modify button, you can modify the Loopback related Interface parameters listed in Table 4-47.

Table 4-47 Loopback Interface Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Interface Id	Basic & Common	integer	Interface ID.	No
In Hold Q Length	Basic & Common	int (0-4096)	Maximum number of packets allowed in the In Hold queue.	Yes
Out Hold Q Length	Basic & Common	int (0-4096)	Maximum number of packets allowed in the Out Hold queue.	Yes
Bandwidth	Basic & Common	int (1-10000000)	Bandwidth value, in kilobytes.	Yes
Delay	Basic & Common	int (1-16777215)	Delay value for the interface.	Yes
Keepalive Timer	Basic & Common	int (0-32767)	Adjusts the frequency that Cisco IOS sends messages to itself (Ethernet and Token Ring) or to the other end (HDLC-serial and PPP-serial links) to ensure that a network interface is alive for a specified interface.	Yes
IP Address	Basic & LAN	string	IP address for this interface.	No
Subnet Mask	Basic & LAN	string	Subnet mask for this interface.	No

SNMP Configuration

This section provides information about the SNMP (Simple Network Management Protocol) configuration capabilities provided by Cisco PTC. An overview of these capabilities, as well as a list of the SNMP configuration parameters supported by Cisco PTC are provided.

SNMP Configuration Overview

Cisco PTC supports SNMP configurations on a region. The SNMP configurations are applied to all gateways, gatekeepers, and directory gatekeepers within the region.

The following SNMP configurations are supported by Cisco PTC:

•create or modify access control for an SNMP Community—the community string defines the relationship between the SNMP manager and the agent. Optionally, you can specify one or more of the following characteristics associated with the community string:

–a MIB view that defines the subset of all MIB objects accessible to the given community

–read and write or read-only permission for the MIB objects accessible to the community

•create or modify an SNMP view record—allows you to assign views to community strings to limit which MIB objects an SNMP manager can access

•enable the SNMP agent shutdown mechanism—using SNMP packets, a network management tool can send messages to users on virtual terminals and the console. The SNMP request that causes the message to be issued to the users also specifies the action to be taken after the message is delivered. One possible action is a shutdown request. After a system is shut down, typically it is reloaded. Because the ability to cause a reload from the network is a powerful feature, it is protected by the snmp-server system- shutdown global configuration operation. If you do not issue this operation, the shutdown mechanism is not enabled.

•establish the contact, location, and serial number of the SNMP Agent

•define the maximum SNMP agent packet size

•limit the TFTP servers used through SNMP—used for saving and loading configuration files through SNMP to the servers specified in an access list

•define SNMP trap operations—the SNMP trap operations allow a system administrator to configure the agent router to send information to an SNMP manager when a particular event occurs.

SNMP Configuration Parameters

Cisco PTC allows you to query a list of SNMP configurations that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for an SNMP Configuration service object is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used to select a virtual gateway for configuring the SNMP on the gateway.

When you select the SNMP service object in the Table of Contents pane, the following information is displayed in the Configuration Listing pane:

•Scope—region or zone or gateway or gatekeeper

•Management Host—hosts to receive SNMP notifications

•Community String—SNMPv1/v2c community string or SNMPv3 user name.

When you click the Modify button, you can modify the SNMP related parameters listed in Table 4-48.

Table 4-48 SNMP Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Server Hosts	Basic & Common	List of IP addresses	IP addresses of the hosts to receive SNMP notifications.	Yes
Notifications Mode	Basic & Common	enum {Default, Informs, Traps}	Mode of notifications.	Yes
SNMP Version	Basic & Common	enum {Default, v1, v2c, v3}	SNMP version number.	Yes
Community String	Basic & Common	string	SNMPv1/v2c community string or SNMPv3 user name.	Yes
Notification Type	Basic & Common	Selection of {Default, AAA, BGP State Change, Call Tracker, Config, DLSW, DNIS, DS0-Busyout, DS1-Loopback, DSP, DSPU Event, Entity, Environmental Monitor, Frame Relay, HSRP, IP Multicast, ISDN, Modem, MSDP, RSRB Event, RSVP Flow Change, RTR, SDLC Event, SDLLC Event, Stun Event, Syslog, TCP Connection, Voice, x25 Event, XGCP}	Types of traps that trigger a notification.	Yes
Server Host UDP Port	Basic & Common	string	Notification host's UDP port number.	Yes
Server Host Trap Source	Basic & Common	enum {Async, Bridge-Group Virtual, CTunnel, Dialer, Ethernet - IEEE 802.3, FastEthernet - IEEE 802.3, Lex, Loopback, Multilink-group, Null, Tunnel, PGM Multicast Host, Virtual Template, and Virtual TokenRing}	Interface for the source address of all traps.	Yes
Trap Source Interface Id	Basic & Common	integer	Interface for the source address of all traps.	Yes
Message Queue Length	Basic & Common	int (1-1000) Default: 10	Message queue length for each notification.	Yes
Server Timeout	Basic & Common	int (1-1000) Default: 30	How often to resend notifications on the retransmission queue.	Yes

HSRP Configuration

This section provides information about the HSRP (Hot Standby Redundancy Protocol) configuration capabilities provided by Cisco PTC. An overview of these capabilities, as well as a list of the HSRP configuration parameters supported by Cisco PTC are provided.

HSRP Configuration Overview

Cisco PTC supports HSRP configuration on gatekeepers and directory gatekeepers.

HSRP provides high network availability because it routes IP traffic from hosts on Ethernet, FDDI, or Token Ring networks without relying on the availability of any single router. HSRP is used in a group of routers for selecting an active router and a standby router. When HSRP is configured on a network segment, it provides a virtual Media Access Control (MAC) address and an IP address that is shared among routers in a group of routers that are running HSRP. One of these devices is selected by the protocol to be the active router. The active router receives and routes packets destined for the group's MAC address.

Configuring HSRP involves:

•configuring HSRP on the interface

•specifying HSRP parameters such as:

–hold time before other routers declare the active router to be down

–the time between hello packets

–hot standby priority used in choosing the active router

–authentication string to be carried in all HSRP messages.

HSRP Configuration Parameters

Cisco PTC allows you to query a list of HSRP (Hot Standby Redundancy Protocol) configurations that meet a filter criteria. The query results are displayed in the Configuration Listing pane (see the "Configuration Listing Pane" section for a detailed description). The entries in the Configuration Listing pane can then be used for modify and delete operations.

The Tree View pane hierarchy for an HSRP Configuration service object is:
region -> virtual zone -> virtual gateway -> router.

The Tree View pane is used to select a virtual gateway for configuring the HSRP on the gateway.

When you select the HSRP service object in the Table of Contents pane, the following information is displayed in the Configuration Listing pane:

•HSRP Group Number—HSRP group number (0-255)

•Routers—list of the routers that form an HSRP pair

•HSRP IP Address—HSRP virtual IP address (A,B,C,D).

When you click the Modify button, you can modify the HSRP related parameters listed in Table 4-49.

Table 4-49 HSRP Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
Primary Router's Interface	Basic & General	enum {all interfaces configured on the router}	Primary router's interface to be used for HSRP.	No
Secondary Router's Interface	Basic & General	enum {all interfaces configured on the router}	Secondary router's interface to be used for HSRP.	No
Primary Router Priority	Basic & General	int (1-255)	Sets the Hot Standby priority used in choosing the active router, where 1 denotes the lowest priority and 255 denotes the highest priority.	No
Secondary Router Priority	Basic & General	int (1-255)	Sets the Hot Standby priority used in choosing the active router, where 1 denotes the lowest priority and 255 denotes the highest priority.	No
Primary Authentication String	Detail & Primary	string	Authentication string to be carried in all HSRP messages.	Yes
Secondary Authentication String	Detail & Secondary	string	Authentication string to be carried in all HSRP messages.	Yes
HSRP Preempt Delay	Detail	int (0-3600)	Preemption delay time value after which the Hot Standby router preempts and becomes the active router.	Yes
HSRP Min Preempt Delay	Detail	int (0-3600) Default: 0	Minimum time to wait before preempting.	Yes
HSRP Preempt Sync Delay	Detail	int (0-3600) Default: 0	Minimum time to wait for a synchronization to complete.	Yes
Interface Tracked	Detail	enum {all interfaces configured on the router}	Configures the interface to track other interfaces so that if one of the other interfaces goes down, the Hot Standby priority of the device is lowered.	Yes
Tracked Interface Priority	Basic & General	int (1-255) Default: 10	Configures the priority.	Yes
HSRP Hello Time	Basic & General	int (20-255000) Default: 3000	Time (in msec) between hello packets.	Yes
HSRP Hold Time	Basic & General	int (20-255000) Default: 3000	Hold time (in msec) before other routers declare the active router to be down.	Yes

Access Control List Configuration

This section provides information about the Access Control List (ACL) configuration capabilities provided by Cisco PTC. An overview of these capabilities, as well as a list of the ACL configuration parameters supported by Cisco PTC are provided.

ACL Configuration Overview

Access lists filter network traffic by controlling whether routed packets are forwarded or blocked at the router's interfaces. The router examines each packet to determine whether to forward or drop the packet on the basis of the criteria specified within the access lists. Access list criteria could be the source address of the traffic, the destination of the traffic, the upper layer protocol, or other information.

Cisco routers support the following Access List configurations:

•creation and deletion of access lists

•assign a unique name or number to an access list

•define criteria for forwarding or blocking packets. Typical criteria are packet source addresses, packet destination addresses, and upper layer protocol of the packet.

•configure multiple criteria statements on an access list.

When an access list is deleted, Cisco PTC notifies the Cisco VRC application about the delete event, and requires a confirmation acknowledgement from Cisco VRC before committing the delete.

For standard access lists with an ID in the range of 1 through 99, Cisco PTC allows you to associate descriptions called remarks. These serve as reminder for Cisco VRC users for later use in a
source ip group configuration.

ACL Configuration Parameters

Cisco PTC allows you to query a list of ACL configurations that meet a filter criteria on the gateways, gatekeepers, and directory gatekeepers. When you select the ACL service object in the Table of Contents pane, the following information is displayed in the Configuration Listing pane:

•GW Name—gateway name

•ACL ID—access control list ID

•ACL Type—access control list type.

When you click the Modify button, you can modify the Standard Access Control List related parameters listed in Table 4-50.

Standard Access Control List Parameters

Table 4-50 Standard Access Control List Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
ACL Number	Basic & General	int (1-99)	IP Access Control List number.	No
ACL Entries - Mode	Basic & General	enum (deny, permit)	deny—specifies to reject packets. permit—specifies to forward packets.	Yes
ACL Entries - Source Host Id	Basic & General	string	IP address or hostname or keyword any.	Yes
ACL Entries - Source Wildcard	Basic & General	string	Source wild card such as A.B.C.D	Yes
ACL Entries - Protocol	Basic & General	enum {IPv4, IPv6, IP, Authentication Header Protocol (ahp), EIGRP, Encapsulation Security Payload (esp), GRE tunneling, ICMP, IGMP, ipinip, KA9Q NOS compatible IP over IP tunneling (nos), ospf, Payload Compression Protocol (pcp), Protocol Independent Multicast (pim), TCP, UDP}		Yes
ACL Entries - Destination Host ID	Basic & General	string	IP address or hostname or keyword any.	Yes
ACL Entries - Destination Wildcard	Basic & General	string	Destination wild card such as A.B.C.D	Yes
ACL Entries - Precedence	Basic & General	enum {0 - Routine, 1 - Priority, 2 - Immediate, 3 - Flash, 4 - Flash Override, 5 - Critical, 6 - Internet, 7 - Network}		Yes
ACL Entries - TOS	Basic & General	enum {0 - Normal, 1 - Min Monetary Cost, 2 - Max Reliability, 3, 4 - Max Throughput, 5, 6, 7, 8 - Min Delay, 9, 10, 11, 12, 13, 14, 15}	Match packets with specified TOS value.	Yes
ACL Entries - Time Range	Basic & General	string	Time range.	Yes
ACL Entries - Logging	Basic & General	enum (None, Log, Log-input)	Log matches against this entry.	Yes
ACL Entries - Remark	Basic & General	string	Access Control List entry comment.	Yes

Extended Access Control List Parameters

When you click the Modify button, you can modify the Extended Access Control List related parameters listed in Table 4-51.

Table 4-51 Extended Access Control List Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
ACL Number	Basic & General	int (1-99)	IP Access Control List number.	No
Dynamic List Name	Basic & General	string	Name of a dynamic list.	No
ACL Entries - Timeout	Basic & General	int	Maximum time for the dynamic ACL to exist.	Yes
ACL Entries - Mode	Basic & General	enum (deny, permit)	deny—specifies to reject packets. permit—specifies to forward packets.	Yes
ACL Entries - Source Host ID	Basic & General	string	IP address or hostname or keyword any.	Yes
ACL Entries - Source Wildcard	Basic & General	string	Source wild card such as A.B.C.D	Yes
ACL Entries - Protocol	Basic & General	enum {IPv4, IPv6, IP, Authentication Header Protocol (ahp), EIGRP, Encapsulation Security Payload (esp), GRE tunneling, ICMP, IGMP, ipinip, KA9Q NOS compatible IP over IP tunneling (nos), ospf, Payload Compression Protocol (pcp), Protocol Independent Multicast (pim), TCP, UDP}		Yes
ACL Entries - Destination Host ID	Basic & General	string	IP address or hostname or keyword any.	Yes
ACL Entries - Destination Wildcard	Basic & General	string	Destination wild card such as A.B.C.D	Yes
ACL Entries - Precedence	Basic & General	enum {0 - Routine, 1 - Priority, 2 - Immediate, 3 - Flash, 4 - Flash Override, 5 - Critical, 6 - Internet, 7 - Network}		Yes
ACL Entries - TOS	Basic & General	enum {0 - Normal, 1 - Min Monetary Cost, 2 - Max Reliability, 3, 4 - Max Throughput, 5, 6, 7, 8 - Min Delay, 9, 10, 11, 12, 13, 14, 15}	Match packets with specified TOS value.	Yes
ACL Entries - Time Range	Basic & General	string	Time range.	Yes
ACL Entries - Logging	Basic & General	enum {None, Log, Log-input}	Log matches against this entry.	Yes
ACL Entries - Remark	Basic & General	string	Access Control List entry comment.	Yes

Dynamic Access Control List Parameters

When you click the Modify button, you can modify the Dynamic Access Control List related parameters listed in Table 4-52.

Table 4-52 Dynamic Access Control List Parameters 

Parameter	Category/Parameter Tab	Value	Description	Modifiable on Router?
ACL Number	Basic & General	int (1-99)	IP Access Control List number.	No
Dynamic List Name	Basic & General		Name of a dynamic list.	No
ACL Entries - Timeout	Basic & General		Maximum time for a dynamic Access Control List to live.	No
ACL Entries - Mode	Basic & General	enum (deny, permit)	deny—specifies to reject packets. permit—specifies to forward packets.	No
ACL Entries - Source Host ID	Basic & General	string	IP address or hostname or keyword any.	No
ACL Entries - Source Wildcard	Basic & General	string	Source wild card such as A.B.C.D	No
ACL Entries - Protocol	Basic & General	enum {IPv4, IPv6, IP, Authentication Header Protocol (ahp), EIGRP, Encapsulation Security Payload (esp), GRE tunneling, ICMP, IGMP, ipinip, KA9Q NOS compatible IP over IP tunneling (nos), ospf, Payload Compression Protocol (pcp), Protocol Independent Multicast (pim), TCP, UDP}		No
ACL Entries - Destination Host ID	Basic & General	string	IP address or hostname or keyword any.	No
ACL Entries - Destination Wildcard	Basic & General	string	Destination wild card such as A.B.C.D	No
ACL Entries - Precedence	Basic & General	enum {0 - Routine, 1 - Priority, 2 - Immediate, 3 - Flash, 4 - Flash Override, 5 - Critical, 6 - Internet, 7 - Network}		No
ACL Entries - TOS	Basic & General	enum {0 - Normal, 1 - Min Monetary Cost, 2 - Max Reliability, 3, 4 - Max Throughput, 5, 6, 7, 8 - Min Delay, 9, 10, 11, 12, 13, 14, 15}	Match packets with specified TOS value.	No
ACL Entries - Time Range	Basic & General	string	Time range.	No
ACL Entries - Logging	Basic & General	enum {None, Log, Log-input}	Log matches against this entry.	No
ACL Entries - Remark	Basic & General	string	Access Control List entry comment.	No

Adding a Managed Resource

This section describes how to add a managed resource (an RLM signaling path in the following example) to the network.

---

Note System administrators can add managed resources to the network, regardless of the region in which the resource is to be created. Regional network operators can only add managed resources to regions in which they have authorization. Non-administrative users are not permitted to add managed resources. See the "Cisco PTC User Groups" section for a detailed list of the capabilities of the various user types.

---

Prerequisites

1. Initial discovery of the complete network topology should have been successful prior to attempting to add a managed resource.

2. The system administrator has been authenticated.

3. The Cisco MGC Node Manager (CMNM) of interest has discovered all network elements and the information was uploaded to Cisco PTC as part of the initial discovery process.

4. The PGW2200/SC2200 of interest can be seen in the Cisco PTC Topology Management window.

Execution

---

Step 1 From the Cisco PTC Launch Pad window, click the Provisioning button. The Provisioning Management window is displayed.

Step 2 From the Provisioning Management window, double-click on the Table of Contents object in the
Table of Contents pane.

Step 3 Double-click on the Voice object in the Table of Contents pane.

Step 4 Double-click on the RLM Signaling Path object in the Table of Contents pane. The contents of the Configuration Listing pane is modified with columns pertaining to the RLM Signaling Path service objects.

Step 5 Drill down in the Tree View pane until the gateway you wish to add the RLM signaling path to is visible, then click the Add button.

Step 6 Select the desired gateway in the Tree View pane, then drag and drop the selected gateway into the Gateway Name field.

Step 7 Select a PGW2200/SC2200 from the SC2200 Name drop-down list.

Step 8 Click Next.

Step 9 Enter the Basic Group Parameter values, then:

a. Click OK when you are finished adding resources of the same type (for example, RLM).

b. Click Apply when you plan on adding multiple resources of the same type (you are returned to the original screen where the objects you initially selected are redisplayed (you don't have to drag and drop these objects from the Tree View pane again).

c. If desired, choose the Templates -> Save Template menu option to save the added parameters to a template with a name of your choosing, through the Save Template window. You provide a name for the template and, optionally, a description of the template in the corresponding fields in the Save Template window, then you click the OK button.

You can then use this parameter template at a later time, to avoid having to reenter the same parameter values for a service object, by choosing the Templates -> Load Template menu option. You enter the name of the template in the Load Template window, then you click the OK button.

---

Verification

1. Permission to add the RLM path should have been granted. Internally, the resource would have been propagated up to the region level to determine whether the current user has privileges to this region in which the resource is being added.

2. The status of the provisioning job as seen in the Provisioning Management window should be complete.

3. The object should be created in the Tree View pane.

4. The gateways should show the RLM signaling path parameters in the running configuration.

5. The PGW2200/SC2200, using man-machine language (MML), should show the RLM signaling parameters.

Adding a Managed Resource (Regional Administrator - Unauthorized Region)

Permission to add a managed resource to an unauthorized region by a regional administrator is not permitted as a regional administrator does not have this privilege.

Adding a Managed Resource (Network Operator - Unauthorized Region)

Permission to add a managed resource to an unauthorized region by a network operator is not permitted as a network operator does not have this privilege.

Adding a Managed Resource (Non-administrative User)

Permission to add a managed resource to the network by a non-administrative user is not permitted as a non-administrative user has read only privileges.

Modifying a Managed Resource

This section describes how to modify a managed resource (an RLM signaling path in the following example).

---

Note System administrators can modify managed resources regardless of the region in which the resource resides. Regional network operators can only modify managed resources in regions in which they have authorization. Non-administrative users are not permitted to modify managed resources. See the "Cisco PTC User Groups" section for a detailed list of the capabilities of the various user types.

---

Prerequisites

1. Initial discovery of the complete network topology was successfully completed.

2. The system administrator has been authenticated.

3. The Cisco MGC Node Manager (CMNM) of interest has discovered all network elements and the information was uploaded to Cisco PTC as part of the initial discovery process.

4. The PGW2200/SC2200 of interest can be seen in the Cisco PTC Topology Management window.

Execution

---

Step 1 From the Cisco PTC Launch Pad window, click the Provisioning button. The Provisioning Management window is displayed.

Step 2 From the Provisioning Management window, double-click on the Table of Contents object in the
Table of Contents pane.

Step 3 Double-click on the Voice object in the Table of Contents pane.

Step 4 Double-click on the RLM Signaling Path object in the Table of Contents pane. The contents of the Configuration Listing pane is modified with columns pertaining to the RLM Signaling Path service objects.

Step 5 Drill down in the Tree View pane until the gateway containing the RLM Q.931 signaling path object you wish to modify is visible, then drag and drop the gateway into the Listing field in the Configuration Listing pane.

The gateway's RLM Q.931 signaling path parameters are displayed in the Configuration Listing pane.

Step 6 Select the newly displayed entry in the Configuration Listing pane.

Step 7 Click the Modify button.

Step 8 Make the desired modifications, then click OK.

---

Verification

1. Permission to modify the RLM path should have been granted. Internally, the resource would have been propagated up to the region level to determine whether the current user has privileges to this region in which the resource is being modified.

2. You can see the status of the provisioning job through the Provisioning Management window. When the job is complete, the listing object is automatically added to the Configuration Listing pane.

3. The object with its modified values should be reflected in the Tree View pane.

4. The gateways should show the modified RLM signaling path parameter in the running configuration.

5. The PGW2200/SC2200, using MML, should show an RLM modified signaling parameter.

Modifying a Managed Resource (Regional Administrator - Unauthorized Region)

Permission to modify a managed resource in an unauthorized region by a regional administrator is not permitted as a regional administrator does not have this privilege.

Modifying a Managed Resource (Network Operator - Unauthorized Region)

Permission to modify a managed resource in an unauthorized region by a network operator is not permitted as a network operator does not have this privilege.

Modifying a Managed Resource (Non-administrative User)

Permission to modify a managed resource by a non-administrative user is not permitted as a non-administrative user has read only privileges.

Removing a Managed Resource

This section describes how to remove a managed resource (an RLM signaling path in the following example) from the network.

---

Note System administrators can remove managed resources from the network, regardless of the region in which the resource resides. Regional network operators can only remove managed resources from regions in which they have authorization. Non-administrative users are not permitted to remove managed resources. See the "Cisco PTC User Groups" section for a detailed list of the capabilities of the various user types.

---

Prerequisites

1. Initial discovery of the complete network topology was successfully completed.

2. The system administrator has been authenticated.

3. The Cisco MGC Node Manager (CMNM) of interest has discovered all network elements and the information was uploaded to Cisco PTC as part of the initial discovery process.

4. The PGW2200/SC2200 of interest is seen in the Cisco PTC Topology Management window.

Execution

---

Step 1 From the Cisco PTC Launch Pad window, click the Provisioning button. The Provisioning Management window is displayed.

Step 2 From the Provisioning Management window, double-click on the Table of Contents object in the
Table of Contents pane.

Step 3 Double-click on the Voice object in the Table of Contents pane.

Step 4 Double-click on the RLM Signaling Path object in the Table of Contents pane. The contents of the Configuration Listing pane is modified with columns pertaining to the RLM Signaling Path service objects.

Step 5 Drill down in the Tree View pane until the gateway containing the RLM Q.931 signaling path object you wish to remove is visible in the Tree View pane, then drag and drop the gateway into the Listing field in the Configuration Listing pane.

The gateway's RLM Q.931 signaling path parameters are displayed in the Configuration Listing pane.

Step 6 Select the newly displayed entry in the Configuration Listing pane.

Step 7 Click the Delete button.

Step 8 Click OK.

---

Verification

1. Permission to remove the RLM path should have been granted. Internally, the resource would have been propagated up to the region level to determine whether the current user has privileges to this region in which the resource is being removed.

2. You can see the status of the provisioning job through the Provisioning Management window. When the job is complete, the listing object is automatically added to the Configuration Listing pane.

3. The object corresponding to the deleted component should be removed from the Tree View pane.

4. The gateways should no longer show the RLM signaling path parameters in the running configuration.

5. The PGW2200/SC2200, using MML, should no longer show RLM signaling parameters.

Removing a Managed Resource (Regional Administrator - Unauthorized Region)

Permission to remove a managed resource in an unauthorized region by a regional administrator is not permitted as a regional administrator does not have this privilege.

Removing a Managed Resource (Network Operator - Unauthorized Region)

Permission to remove a managed resource in an unauthorized region by a network operator is not permitted as a network operator does not have this privilege.

Removing a Managed Resource (Non-administrative User)

Permission to remove a managed resource by a non-administrative user is not permitted as a non-administrative user has read only privileges.

Saving and Loading a Configuration Parameter Template

This section describes how to save a configuration parameter template. After entering the values for several parameters for adding a service object, you can save this set of parameter as a parameter template. This parameter template can be later used to add another service object with the parameter values defined in the parameter template or the parameter template can be applied to all devices within a region.

---

Step 1 From the Cisco PTC Launch Pad window, click the Provisioning button. The Provisioning Management window is displayed.

Step 2 From the Provisioning Management window, double-click on the Table of Contents object in the
Table of Contents pane.

Step 3 Double-click on the Basic object in the Table of Contents pane.

Step 4 Double-click on the SNMP object in the Table of Contents pane. The contents of the Configuration Listing pane is modified with columns pertaining to the SNMP service objects.

Step 5 To create this parameter template for use on all objects within a region, select a region object in the Tree View pane.

The SNMP related service objects are displayed in the Configuration Listing pane.

Step 6 Select an entry from the list of displayed service objects, whose parameters you would like to use as the basis of the template, in the Configuration Listing pane.

Step 7 Click the Modify button.

The selected entry's SNMP parameters are displayed in the Configuration Listing pane.

Step 8 Choose the Template -> Save Template menu option or click on the Save Template icon in the tool bar.

Step 9 Enter the name of the new template in the Name field in the Save Template window. You can also provide a template description in the Description field if you desire.

Step 10 Click Save.

The parameter template is saved for later use.

Step 11 To apply the saved parameter template to all devices within a region, make sure the desired region object is selected in the Tree View pane.

Step 12 Select an entry from the list of displayed service objects, whose parameters you would like replaced by a previously created template, in the Configuration Listing pane.

Step 13 Click the Modify button.

The selected entry's SNMP parameters are displayed in the Configuration Listing pane.

Step 14 Choose the Template -> Load Template menu option or click on the Load Template icon in the tool bar.

Step 15 Select the template entry you wish to use from the Load Template window.

Step 16 Click OK to replace the current parameter values with the template values. Click Cancel to cancel the load operation. Click Delete to delete the load template entry from the Load Template window.

Step 17 Having clicked the OK button in the Load Template window, the parameter template values are now displayed in the Configuration Listing pane. To apply these values to all of the devices within the selected region, click the OK button in the Configuration Listing pane.

---