Managing Dial Plan Components

Dial Plan Elements—A router with physical counterparts that are used in a VRC dial plan.
The Administrative Domain—The whole network. The highest level of administration which encompasses the entire dial plan. The AD includes all elements that participate in the VoIP call routing.
Regions - A specific partition of the network. It may contain one or more zones, gatekeeper groups, and directory gatekeepers.
Directory gatekeeper groups, gatekeeper groups, and zones—Including the elements, attributes and parameters that can be configured for each of these dial plan components.

Elements

VRC recognizes the following as network elements:

Gateways
Gatekeepers
Directory gatekeepers

The element states refer to their status in the VRC dial plan and the status of the running configuration in relation to the startup configuration.

This chapter decribes how to manage elements within a VRC dial plan. To add a specific element to the dial plan, refer to the following sections:

To add a directory gatekeeper to the dial plan, refer to"Adding a Directory Gatekeeper to the Dial Plan" section.
To add a gatekeeper to the dial plan, refer to"Adding a Gatekeeper to the Dial Plan" section.
To add a gateway to the dial plan, refer to "Adding a Gateway to the Dial Plan" section.

Element States

In the VRC dial plan, the element states refer to their status in the VRC dial plan, availability to the Discovery operation, and the status of the running configuration in relation to the startup configuration.

There are two types of element states:

Dial plan state—Indicates the element status in the VRC dial plan design. The values are:

Active—The element is currently used in the baseline dial plan.
Inactive—The element is not currently used in the baseline dial plan.
Active Pending—The element is not currently used in the baseline dial plan but is used in a design that is not yet committed.
Inactive Pending—The element is currently used in the baseline dial plan but has been removed from a design that has not been committed.

Configuration state—Indicates the status of the running configuration in relation to the network device startup configuration. Values are:

Volatile—Current running configuration is different from the startup configuration on the device. Each time you make a change to the element in the Design View and commit the design, the configuration state remains volatile until you write the new configuration to startup.
Persisted—Current running configuration has been written to the startup configuration on the device.
Unknown—The relationship between the element running configuration and startup configuration is unknown.

During the Discovery operation, all elements in the topology which have an Assigned state are added to the discovery design session. If you want to perform a Discovery on a specific network element with an Assigned state, the element is put into the discovery design session. If the element is Unassigned, discovery cannot take place.

Checking Element Accessibility

You can check the accesibility of network elements within a selected scope.

To check on elements:

Step 1 In the Design View or Baseline View, expand the dial plan tree to show all elements.

Step 2 Select the elements that you want to check the accessibility for. You can check a group of elements within a particular scope.

Step 3 Right-click the selected element and choose Check Elements from the menu.

Step 4 Choose which elements that you want to check accessibility for. Select:

Inactive—Check only elements that are in the Inactive state.
Active—Check only elements that are in the Active state.
All—Check all elements.

Step 5 You are asked to confirm your decision. Click OK.

A Checking Elements dialog box informs you that the operation is in progress. Once the checking has finished, an information dialog box (Figure 5-1) appears, telling you that the operation was successful.

Figure 5-1 Checking Elements Information Window

Step 6 Click OK to close the window, click Details to view detailed information, click No Details to hide the information, or click Display Web Browser to open a web browser window to view the information.

Reactivating an Element

When you add a network element to a dial plan design, that element is implicitly activated.

When you reactivate an element, VRC reads all dial plan configuration from a network element and updates the element topology information. This includes:

Element information that VRC does not change, such as host name, IP address for that element
Element configuration information that affects the dial plan, such as voice ports and trunk group configuration, and access lists

You can reactivate the element using the VRC client any time you suspect that there have been changes to element configuration information using the command line interface (CLI) directly.

To reactivate a gateway, gatekeeper, or directory gatekeeper:

Step 1 In the Design View, expand the dial plan tree to show all elements.

Step 2 Select the element for reactivation.

Step 3 Right-click the element and choose Reactivate from the menu.

VRC updates the dial plan configuration information for that element.

Administrative Domain

The Administrative Domain (AD) is the entire VoIP network whose dial plan is managed by VRC. The AD is made up of:

Dial plan regions (managed or foreign)
Technology prefixes
Trunk or carrier IDs (if the carrier sensitive route (CSR) route type is set to trunk-label or carrier)

Note The AD must contain at least one managed region.

To view the general attributes of the AD in the Design or Baseline Views, select the AD in the dial plan tree and click the Attributes tab. AD attrtributes include:

Name—AD.
CSR Route Type—Defines how VRC manages carrier sensitive route (CSR) related dial plan features. Values are:

None—VRC disables all CSR-related dial plan features in the AD.
Carrier—VRC assumes that all CSR-related dial plan features utilized in the dial plan are carrier based.
Trunk-Label—VRC assumes that all CSR-related dial plan features utilized in the dial plan are trunk-label based.

AD Parameters

The following sections describes how to manage the AD parameters, including:

Setting the CSR Route Type

The route type is used to define the CSR-related configuration of the dial plan design and sets the route type for the entire Administrative Domain (AD).

To set the route type for the AD:

Step 1 From the Design View, select the AD in the dial plan tree. The Attributes tab is forward.

Step 2 To change or set the route type, click Edit Attributes. The Attributes for AD dialog box appears.

Step 3 Select one of the following route types:

Carrier—VRC assumes that all CSR-related dial plan features utilized in the dial plan are carrier-based.
None—VRC disables all CSR related dial plan features in the AD.
Trunk-Label—VRC assumes that all CSR-related dial plan features utilized in the dial plan are trunk-label based.

Step 4 Click Apply to select the CSR route type or Cancel.

Adding Technology Prefixes

A technology prefix is used for technology-related routing. For example, the characters 1# are used by convention to indicate voice gateways. A technology prefix allows the gatekeeper to select a gateway with specific capabilities. The specific capabilities for a technology prefix are defined at the AD level.

To add a technology prefix to the AD:

Step 1 From the Design View, click AD in the left pane.

Step 2 Click the Technology Prefixes tab in the right pane. The technology prefixes list is displayed.

Step 3 Right-click and choose Add from the menu. The Add Technology Prefix dialog box appears (Figure 5-2).

Figure 5-2 Add Technology Prefix Dialog Box

Step 4 Enter the technology prefix attribute information:

Prefix—The technology prefix that you want to add.
Check the Default checkbox if you want this to be your default technology prefix for a gateway.
Description—Optional. A text description of the technology prefix. The maximum value is 255 characters.

Step 5 Click Apply to apply this prefix to the gateway or Cancel.

Deleting Technology Prefixes

You can delete a technology prefix from an existing design or a new design.

To delete a technology prefix from the AD:

Step 1 Select the AD and click the Technology Prefixes tab.

Step 2 Select the technology prefix you want to delete.

Step 3 Right-click and choose Delete from the menu. A confirmation dialog box appears asking you to confirm.

Step 4 Click OK to delete the technology prefix from the dial plan or Cancel.

Adding Trunk and Carrier IDs

Trunk and carrier IDs connect a carrier identifier with each inbound call by associating the call on an inbound trunk group, NFAS group, or voice port with a defined carrier.

In VRC, a trunk carrier represents a carrier ID or trunk group label supported by the AD.

The trunk ID is used to configure carrier sensitive route (CSR) functionality when the CSR route type for the AD is set to trunk-label.
The carrier ID is used to configure CSR functionality when the CSR route type for the AD is set to carrier.

To add a trunk or carrier ID to the AD:

Step 1 Select the AD and click the Trunk/Carrier IDs tab. This tab is only available when the CSR route type is either carrier or trunk-label.

Step 2 Right-click and choose Add from the menu. The Add Trunk/Carrier ID dialog box appears (Figure 5-3).

Figure 5-3 Add Trunk/Carrier ID Dialog Box

Step 3 Enter the Trunk/Carrier attribute information.

Name—The name of the trunk or carrier ID. The maximum value is 255 characters.

Enter a carrier ID if the CSR route type for this AD is set to Carrier.
Enter a trunk ID if the CSR route type for this AD is set to Trunk-Label.

Description—The description value can be an alphanumeric string, maximum value 255 characters.

Step 4 Click Apply to add the carrier or trunk ID to the AD or Cancel.

Route Servers

A route server is external to the VRC managed dial plan. A VRC managed gatekeeper is configured to communicate with a route server (route servers are used across regions) through the use of server triggers which instruct the router to forward messages of a given route server type.

Note The AD must contain at least one route server.

To add a route server to the AD:

Step 1 From the Design View, select the AD in the dial plan tree.

Step 2 Right-click and choose Add and Route Server from the menus. The Add Route Server dialog box appears.

Step 3 Enter the attribute information:

Name—Name of the route server. The maximum value is 64 characters.
IP Address—IP address of the route server.
Port—Number of the port. The value must be an integer between 1 and 65535.

Step 4 Click Apply to add the route server to the AD or Cancel.

Regions

A region is a logical division of the Administrative Domain (AD). Regions consist of network elements that are grouped for geographical or administrative reasons.

The VRC application supports:

Managed region—A managed region is a subset of the VoIP network which is configured by VRC and is defined as a collection of zones, gatekeepers groups, and zero or one associated directory gatekeeper group.
Foreign region—Exists as a peer to all other regions within the AD. It does not contain network elements that are managed by VRC, but it can contain routes that might be terminated on a region's directory gatekeeper group or gatekeeper group.
LRQ Transit region—A special type of managed region which contains only one directory gatekeeper group. This type of region is used for networks with hierarchical DGKs.

A region is either meshed or hierarchical.

Meshed—A region without a directory gatekeeper group is a meshed configuration. In a meshed configuration all gatekeepers in the region know about each other. Every gatekeeper contains its own database of all addresses and prefixes in the region.
Hierarchical—A region containing a directory gatekeeper group has a hierarchical configuration. In a hierarchical configuration, the gatekeepers only know about the directory gatekeeper.

This section contains the following topics about a region:

Managed Region

A managed region and the elements within the region are managed by the VRC. A managed region consists of network elements which are grouped for geographical or administrative reasons.

A managed region might contain:

Directory gatekeeper groups (if it is a hierarchical region)
Gatekeeper groups
Managed zones
Outgoing or incoming regional connections
Open Settlement Protocol (OSP) servers
Voice class codecs

Table 5-1 describes the attributes for a managed region.

Table 5-1 Managed Region Attributes

Entry Field	Description
Name	The name of the region. The maximum value is 64 characters.
Domain	The domain name. The maximum value is 255 characters.
Class	The class of the region. Choose meshed or hierarchical. The default is meshed. If you specify a meshed region, you cannot add directory gatekeeper groups to this region.
Role	The role for this region in the dial plan. Regular - A managed region is a subset of the VoIP network which is configured by VRC and is defined as a collection of zones, gatekeepers groups, and zero or one associated directory gatekeeper group. LRQ transit - A special type of managed region which contains only one directory gatekeeper group. This type of region is used for networks with hierarchical DGKs. Note An LRQ transit region cannot contain any managed zones or gatekeeper groups.
Default LRQ Password	The LRQ password used by all elements in this region to trap LRQs from unknown remote zones. Choose from a previously defined list of LRQ passwords. The maximum value is 1023 characters. Note A default regional LRQ password is required before any other security feature can be used. The default LRQ password creates a "catch all" clause for all regional gatekeepers and directory gatekeepers. Note If you set this parameter, you must have an incoming connection for every region that has an outgoing connection pointing to it.
Discovery Status	Determines whether a synchronization is required for this region based on VRC-generated LRQ passwords.
Discovery Details	Additional information regarding the Discovery status.
Validation State	Indicates whether the Cisco VRC server can contact the element during the Validation process.
Details	An optional text string that gives more details about the status of the region. The maximum value is 255 characters.

Foreign Region

A foreign region is outside the AD. A foreign region exists as a peer to all other regions within the AD. It does not contain network elements that are managed by the VRC, but it can contain routes that might be terminated on a region's directory gatekeeper group or gatekeeper group. A foreign region:

Has a single point of contact
Is made up of unmanaged zones

Table 5-2 describes the attributes that you must define for a foreign region.

Table 5-2 Foreign Region Attributes

Entry Field	Description
Name	The name of the region. The maximum value is 64 characters.
Domain	The domain name. The maximum value is 255 characters.
IP Address	The IP address of the gatekeeper, which is the point of contact for this foreign region.
RAS Port	The Registration, Admission, and Status signaling port. The range is 1 to 65535.
Validation State	Indicates whether the Cisco VRC server can contact the element during the Validation process
Details	An optional text string that gives more details about the status of the region. The maximum value is 255 characters.

Adding a Region to the Dial Plan

Note The region must exist in the topology before you can add it to the dial plan.

To add a managed region to a dial plan:

Step 1 Expand the dial plan tree to view all components.

Step 2 Right-click the AD and choose Add and Managed Region from the menus. The Add Managed Region to Dial Plan dialog box appears with a list of available regions.

Step 3 Select a region to add to the dial plan.

Step 4 Click Apply to add the region to the dial plan or Cancel.

To add a foreign region to a dial plan:

Step 1 Expand the dial plan tree to view all components.

Step 2 Right-click the AD and choose Add and Foreign Region from the menus. The Add Foreign Region dialog box appears (Figure 5-4).

Figure 5-4 Add Foreign Region Dialog Box

Step 3 Enter the foreign region attributes. The entry fields are described in Table 5-2.

Step 4 Click Apply to add the region to the dial plan or Cancel.

Deleting a Region from the Dial Plan

Note When you remove a region from the dial plan, you remove all elements contained in that region.

To remove a region from the dial plan:

Step 1 In the Design View, expand the dial plan tree to view all components.

Step 2 Select the region you want to delete.

Step 3 Right-click and choose Delete from the menu.

Step 4 Determine the status of the dial plan configuration. If you choose:

Disable—VRC clears the dial plan configuration and removes the region from the dial plan database during the next commit process.
Do not Disable—VRC leaves the current dial plan configuration and removes the region, and all elements that reside in the region, from the dial plan database during the next commit process.
Cancel—Cancels this procedure.

Step 5 Confirm your decision.

Region Parameters

This section describes how to add or delete the following region parameters:

Outgoing Connections

Regions own their outgoing connections. You can choose the other regions to receive communication from them. These outgoing connections become the incoming connections of the receiving region. VRC allows you to add and delete outgoing connections to a region (managed or foreign).

Note If you set the Default LRQ password attribute for a given region, you must have an incoming connection for every region that has an outgoing connection pointing to it.

Adding Outgoing Connections

To add an outgoing connection for a region:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the region you want to add an outgoing connection to.

Step 3 Click the Outgoing Connections tab. The right pane displays the outgoing connections associated with this region.

Step 4 Right-click choose Add from the menu. The Add Outgoing Connection dialog box appears (Figure 5-5).

Figure 5-5 Add Outgoing Connection Dialog Box

Step 5 Enter the outgoing region attributes.

Connection To—The region to point to for this outgoing connection.
Connection Type—The relationship between a region and its outgoing connection region that reflects the desired inter-region LRQ forwarding pattern.

Peer—There is no hierarchical relationship between this region and the region being pointed to for the outgoing connection.
Up—The region being pointed to for the outgoing connection is hierarchically above this region.
Down—The region being pointed to for the outgoing connection is hierarchically beneath this region.

Foreign LRQ Password—If your 'connection to' region is a foreign region, set the LRQ password, if it is known and you want this security feature applied.
Out Via-Zone—This parameter is not supported in VRC 1.2.

Step 6 Click Apply to apply the outgoing connection to the region or Cancel.

Deleting Outgoing Connections

To delete an outgoing connection from a managed region:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select a region you want to delete the outgoing connection from.

Step 3 Click the Outgoing Connections tab. The list of regions and associated outgoing connections displays.

Step 4 Select a `Connection To' region to delete.

Step 5 Right-click and choose Delete from the menu. A Confirm dialog box appears.

Step 6 Click OK to confirm the delete or Cancel.

Voice Class Codecs

A voice class codec is the coding scheme used for outgoing calls. VRC allows the administrator to select a valid voice encoding or decoding scheme from its list. You can add or delete voice class codecs from a managed region. A codec is the voice coder rate of speech for a dial peer.

Adding Voice Class Codecs

To add voice class codecs to a managed region:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the region you want to add the voice class codec to.

Step 3 Click the Voice Class Codecs tab. The list of voice class codecs associated with this region displays.

Step 4 Right-click and choose Add from the menu. The Add Voice Class Codecs dialog box appears.

Enter the voice class codec attributes:

Tag—Unique ID for this voice class codec. The value can be any integer between 1 and 10000.
Description—Text description of this voice class codec. The maximum value is 255 characters.

Step 5 Click Apply to add the voice class codec or Cancel.

Deleting Voice Class Codecs

To delete voice class codecs from a managed region:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the region you want to delete the voice class codec from.

Step 3 Click the Voice Class Codec tab. The list of voice class codecs associated with this region displays.

Step 4 Right-click and choose Delete from the menu. A Confirm dialog box appears.

Step 5 Click OK to confirm the deletion or Cancel.

Adding a Codec

A codec is a software algorithm used to compress/decompress speech or audio signals in Voice-over-IP (VoIP) networks.

To add a codec option to a voice class codec in a region:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the region which contains the voice class codec you want to add a codec to.

Step 3 Click the Voice Class Codecs tab.

Step 4 Double-click the voice class codec you want to add a codec to.

Step 5 Click the Codecs tab.

Step 6 Right-click and choose Add from the menu. The Add Codec dialog box appears (Figure 5-6).

Figure 5-6 Add Codec Dialog Box

Enter the codecattributes:

Name—Sets the codec options that you can use when you execute this command. See Table 5-3 for a description of codec options.
Preference—Specifies the order of preference for this codec. The range is 1 to 14, with 1 being the most preferred and 14 being the least preferred.
Bytes—Specifies the number of bytes in the voice payload of each frame. The range is 10 to 240.

Note Not all codec options are available on all gateway platforms. Check the Cisco IOS version on your gateway to see which codecs are supported.

Table 5-3 Supported Codecs

Codec Option	Description
g711alaw	G.711 a-Law at 64,000 bits per second (bps)
g711ulaw	G.711 u-Law at 64,000 bps
g723ar53	G.723.1 Annex A at 5300 bps
g723ar63	G.723.1 Annex A at 6300 bps
g723r53	G.723.1 at 5300 bps
g723r63	G.723.1 at 6300 bps
g726r16	G.726 at 16,000 bps
g726r24	G.726 at 24,000 bps
g726r32	G.726 at 32,000 bps
g728	G.728 at 16,000 bps
g729br8	G.729 Annex A and B at 8000 bps
g729r8	G729 Annex A at 8000 bps
gsmcfr	12200 bps
gsmfr	13200 bps

Step 7 Click Apply to add the codec or Cancel.

LRQ Passwords

LRQ passwords represent CAT (Cisco Access Token) exchanged between two gatekeepers or directory gatekeepers, while forwarding an LRQ.

Note We recommend that you use Network Time Protocol (NTP) when you use LRQ passwords in VRC. Elements that exchange CAT must use NTP for authentication to succeed.

LRQ Passwords can be created by a regional administrator and are associated with all LRQ paths in the network. VRC ensures that passwords are correctly configured on both the sending and the receiving end.

LRQ passwords:

Are used to validate any LRQs received from the specified remote zone.
Represents the receiving password from each element to the parent region.
Are used for incoming regional connections to the parent region and outgoing regional connections to foreign regions.

Note If you set the default LRQ password attribute for a given region, you must have an incoming connection for every region that has an outgoing connection pointing to it and you want this security feature applied.

Adding LRQ Passwords

To add an LRQ password to a region:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the region you want to add an LRQ password to.

Step 3 Click the LRQ Passwords tab. The list of LRQ passwords associated with this region displays.

Step 4 Right-click and choose Add from the menu. The Add LRQ Password dialog box appears (Figure 5-7).

Figure 5-7 Add LRQ Password Dialog Box

Step 5 Enter the LRQ attribute information:

Current Password—LRQ password used by all elements in this region to trap LRQs from unknown remote zones. Maximum value is 1023 characters.
Future Password—LRQ password to use by all elements in this region to trap LRQs from unknown remote zones at the time specified in the Future Time parameter. Maximum value is 1023 characters.
Future Time —This parameter can only be set if the Future Password parameter is set. Enter the hour, minute, month, day and year associated with the future password. The future time is Coordinated Universal Time (UTC), which is the time zone at zero degrees longitude, regardless of the time zone set on the router.

Step 6 Click Apply to add the LRQ password to the region or Cancel.

Deleting LRQ Passwords

Note You must delete all references to an LRQ password before you can delete it (for example, in incoming and outgoing connections).

To delete an LRQ password from a region:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the region you want to delete an LRQ password from.

Step 3 Click the LRQ Passwords tab. The list of LRQ passwords associated with this region displays.

Step 4 Select the LRQ password to delete.

Step 5 Right-click and choose Delete from the menu. You are asked to confirm your decision.

Step 6 Click OK to delete the LRQ password from the region or Cancel.

Incoming Connections

An incoming region connection represents the unidirectional connection from one region to the owner region.

Note You must set up an LRQ password before you can add an incoming region connection to a region.

Note You must have an incoming connection for every region that has an outgoing connection pointing to it, if the default LRQ password attribute is set and you want this security feature applied.

Adding an Incoming Connection

To add an incoming region connection from one region to another:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the region you want to add an incoming connection to.

Step 3 Click the Incoming Connections tab. The list of incoming connections associated with this region displays.

Step 4 Right-click and choose Add from the menu.

Step 5 Enter the attribute information.

Connection From—The region this incoming connection is from.
LRQ Receive Password—The password used to validate any LRQs received from the specified remote zone.
In-Via Zone—This parameter is not supported in VRC 1.2.

Step 6 Click Apply to add the incoming region connection to the owner region or Cancel.

Deleting Incoming Connections

To delete an incoming connection from a managed region:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the region to delete an outgoing connection from.

Step 3 Click the Outgoing Connections tab. The list of outgoing connections associated with this region displays.

Step 4 Select the 'Connection To' region you want to delete.

Step 5 Right-click and choose Delete from the menu. You are asked to confirm your decision.

Step 6 Click OK to delete the outgoing connection from the region or Cancel.

Directory Gatekeeper Group

A directory gatekeeper group (DGKGrp) is a set of one to five directory gatekeepers (DGKs) depending on the group type, that you configure for redundancy. This configuration is based on primary, none, Hot Standby Router Protocol (HSRP), cluster, or overlap directory gatekeepers (see Table 5-4).

You can add server triggers and zone circuits to a directory gatekeeper group.

Note You can only add a zone circuit to a directory gatekeeper group if the CSR route type is set to trunk-label or carrier and the VRC feature set is dp1.1 or later.

Directory Gatekeeper Group Attributes

You can view the general attributes of a selected directory gatekeeper group (DGKGrp) from the Baseline View or the Design View:

Expand the dial plan tree to view all components.
Locate the directory gatekeeper group and select it to view the attributes.

Note Enhanced functionality attributes can only be viewed and edited if the VRC feature set for this directory gatekeeper group is set to dp1.1 or later.

Table 5-4 describes the attributes of a directory gatekeeper group.

Table 5-4 Directory Gatekeeper Group Attributes

General Attributes	Description
Name	The name of the directory gatekeeper group. The maximum value is 64 characters.
Cluster Name	The local cluster name assigned by this directory gatekeeper group, if it is configured as clustered. The maximum value is 64 characters.
RAS Port	The registration, admission, and status signaling port. The range is 1 to 65535. The default is 1719.
Type	The type of redundancy system used for this directory gatekeeper group. The default is none. None—This directory gatekeeper group contains only one directory gatekeeper and it is the primary directory gatekeeper. HSRP—Hot Standby Router Protocol. This directory gatekeeper group contains two directory gatekeepers; one is primary and one is backup. Overlap—This directory gatekeeper group contains two directory gatekeepers; one is primary and one is overlap. Both—Both HSRP and Overlap. This directory gatekeeper group contains three directory gatekeepers; one is primary, one is backup, and one is overlap. Cluster —This directory gatekeeper group contains at least two directory gatekeepers; one is primary and the second (or all remaining directory gatekeepers) must be type cluster.
Feature Set	The VRC feature set supported by this directory gatekeeper group. The default is dp1.0.
Timeout	The timer server timeout (100-ms units). The default is none. The range is 1 to 50.
IRR Timer	Sets the IRR reporting interval which it sets on the gateway upon the gateway's registration. This value can only be set if the VRC feature set is dp1.1 or later. The range is 1 to 60.
Server Registration Port	Configures a port for the gatekeeper to communicate with a Gatekeeper Transaction Message Protocol (GKTMP) server. The range is 1 to 65535.
Server Flow Enabled	Check this box if you want to enable flow control from the VRC server to the network device. The server flow control monitors the average response time from the server to the GKTMP.
Server Flow High	Can only be set if server flow is enabled. The onset percentage of the timeout value used to mark the server as usable or unusable. The range is 1 to 100. The default is 80.
Server Flow Low	Can only be set if server flow is enabled. The abatement percentage of the timeout value used to mark the server as usable or unusable. The range is 1 to 100. The default is 50.
Max. Queue Length	Can only be set if server flow is enabled. The threshold for the length of the outbound queue on the gatekeeper. The TCP socket between the gatekeeper and GKTMP server queues messages if it has too many to transmit. If the count of outbound queue length on the server reaches this value, the server is marked unusable. The range is 1 to 2000. The default is 50.
Enhanced Functionality	Description
Server Retry Timer	Specifies the interval (in seconds) to wait between the detection of a server failure and the next attempt to connect to the failed server. This value can only be set if the VRC feature set is dp1.1 or later. The range is 1 to 300.
Disable IRQ Global Request	Disables global request or call reference value (CRV) set to zero for newly registering end-points. This value can only be set if feature set is dp1.1 or later.
LRQ Reject Unknown Circuit	Enables directory gatekeeper rejection of LRQ messages that contain unknown destination carrier IDs descriptions. This value can only be set if the VRC feature set is dp1.1 or later and the CSR route type is carrier or trunk-label.
LRJ Immediate Advance	Disables the gatekeeper from immediately sending a sequential location request (LRQ) to the next zone after it receives a location reject (LRJ) from a gatekeeper in the current zone.
LRQ Reject Resource Low	If this parameter is set, the gatekeeper rejects the inter-zone call if all gateways in that zone are marked as almost-out-of-resources.
ICZT Password	Enables generation of the interzone ClearToken (ICZT) password. The range is 6 to 8 alphanumeric characters. You can only set this parameter if the VRC feature set is dp1.1 or later.
LRQ/ARQ Handling	Description
LRQ Reject Unknown	Rejects LRQ messages for unknown zone prefixes.
LRQ Forwarding	Forwards E.164 Location Request (LRQ) messages to remote gatekeepers managing that zone prefix. Values are: Yes—The default, indicates that LRQ forwarding is enabled. No—Indicates not enabled. Note VRC does not support simultaneous LRQs being sent on a gatekeeper for a specific zone prefix (LRQ blast), when multiple gatekeepers have the same prefix.
LRQ Delay	Time interval between successive LRQ messages (100-ms units). The range is 1 to 10.
LRQ Window	Defines the time window (in seconds) during which the gatekeeper collects responses to one or more outstanding LRQs. The range is 1 to 15.
LRQ Receive Password	The LRQ password that the directory gatekeeper assigns to the zones. Set this password to specify an internal regional password for directory gatekeeper communication. If it is not set, the default regional password is used.
Validation State	Indicates whether the Cisco VRC server can contact the element during the Validation process.
Details	An optional text string that gives more details about the status of the element. The maximum value is 255 characters.

Adding a New Directory Gatekeeper Group

Use this procedure to add a new directory gatekeeper group (DGKGrp) to a managed region.

Note You can only add a directory gatekeeper group to a hierarchical region. You cannot add directory gatekeeper groups to meshed regions.

To add a directory gatekeeper group:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the managed region you want to add a directory gatekeeper group to.

Step 3 Right-click and choose Add and Directory Gatekeeper Group from the menus. The Add Directory Gatekeeper Group dialog box appears (Figure 5-8 and Figure 5-9 ).

Figure 5-8 Add Directory Gatekeeper Group Dialog Box(General Attributes)

Figure 5-9 Add Directory Gatekeeper Group Dialog Box(Enhanced Functionality and LRQ/ARQ Handling)

Step 4 Enter the attribute information. Refer to Table 5-4 for a description of each entry field.

Step 5 Click Apply to add the new directory gatekeeper group or Cancel.

Deleting a Directory Gatekeeper Group

To delete a directory gatekeeper group from the dial plan:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the directory gatekeeper group you want to delete.

Step 3 Right-click and choose Delete from the menu.

Step 4 Determine the status of the dial plan configuration. If you choose:

Disable—VRC clears the dial plan configuration and removes the directory gatekeeper group from the dial plan database during the next commit process.
Do Not Disable—VRC leaves the current dial plan configuration and removes the directory gatekeeper group, and all elements that reside in the directory gatekeeper group, from the dial plan database during the next commit process.

The directory gatekeeper group is removed from the dial plan.

Directory Gatekeeper

A directory gatekeeper is an H.323 gatekeeper that provides address translation support only for other gatekeepers. With a directory gatekeeper, individual gatekeepers do not need to know about other gatekeepers. Instead, a gatekeeper consults its routing table, which provides a default route to a directory gatekeeper. This directory gatekeeper is more knowledgeable about the topology of the network and can forward messages over to the proper gatekeeper. A directory gatekeeper is a VRC element.

A directory gatekeeper:

Has global dial plan responsibility
Creates a hierarchical architecture of regional gatekeepers
Eliminates the need for a fully meshed gatekeeper configuration
Simplifies overall dial plan management

The directory gatekeeper routes calls outside the local zones by maintaining a list of zone prefix routing tables.

The following Cisco platforms are recognized as directory gatekeepers in VRC:

Cisco 3640 Multiservice Platform
Cisco 3660 Multiservice Platform
Cisco 7200 Series Routers

Directory Gatekeeper Attributes

You can view the attributes of a directory gatekeeper (DGK) from the Design View or Baseline View:

Expand the dial plan tree to view all components.
Locate the directory gatekeeper and select it to display the Attributes tab.

Table 5-5 describes the attributes of a directory gatekeeper.

Table 5-5 Attributes of a Directory Gatekeeper

General Attributes	Description
Name	The name of the directory gatekeeper. The maximum value is 64 characters.
IP Address	IP address of the directory gatekeeper.
Standby IP	The IP address the directory gatekeeper uses to communicate with the directory gatekeeper group if the directory gatekeeper group is configured for HSRP.
IOS version	The Cisco IOS version running on this directory gatekeeper.
Feature Set	The VRC feature set supported by this directory gatekeeper. This field is populated by VRC when the directory gatekeeper is added to the dial plan.
Local Zone Name	The name of the local zone that is associated with this DGK. Maximum value is 255 characters. The local zone name must be unique with respect to all unmanaged zone names, zone alias names, other DGK local zone names in the AD. Note Exception: If this DGK has the Type parameter set to primary or backup and another DGK in the same DGK group is also a primary or backup, the local zone names must be identical for those two directory gatekeepers.
Type	The type of directory gatekeeper. Choose from primary, overlap, cluster, or backup. The default is primary. You can have only one primary and only one overlap directory gatekeeper in a directory gatekeeper group (DGKGrp). If you choose: Overlap, the directory gatekeeper group that this directory gatekeeper belongs to must be type overlap or both. Backup, the directory gatekeeper group that this directory gatekeeper belongs to must be type backup or both. If you choose backup, you must set the Standby IP value to the IP address of the primary directory gatekeeper. Cluster, the directory gatekeeper group that this directory gatekeeper belongs to must also be type cluster.
Discovery Status	Determines whether a synchronization is required for this region based on VRC-generated LRQ passwords.
Discovery Details	Additional information regarding the Discovery status.
Validation State	Indicates whether the Cisco VRC server can contact the element during the Validation process.
Details	An optional text string that gives more details about the status of the element. The maximum value is 255 characters.

Adding a Directory Gatekeeper to the Dial Plan

Use this procedure to add a directory gatekeeper to a directory gatekeeper group in the dial plan.

Note You can only add a directory gatekeeper to a directory gatekeeper group for a hierarchical region. There are no directory gatekeeper groups for meshed regions.

Note When you add an element (gateway, gatekeeper, directory gatekeeper) to the dial plan, any preexisting dial plan configuration for that element is overwritten when you commit the design.

To add a new directory gatekeeper:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the directory gatekeeper group you want to add a directory gatekeeper to.

Step 3 Right-click and choose Add and Directory Gatekeeper from the menu. The Add New Directory Gatekeeper to Dial plan dialog box appears (Figure 5-10). This dialog box lists the IP addresses of available directory gatekeepers.

Figure 5-10 Add Directory Gatekeeper Dialog Box

Step 4 Select a directory gatekeeper and click Add. VRC checks for element accessibility and adds the directory gatekeeper to the dial plan.

If the operation is not successful, click the Details button on the error dialog box to view the log.

Gatekeeper Group

A gatekeeper group is a dial plan entity composed of one or more physical gatekeepers.

One gatekeeper in each gatekeeper group must be designated as the primary gatekeeper. If a gatekeeper group contains more than one gatekeeper, you must configure the gatekeepers in a redundant manner using one of the following supported techniques:

Gatekeeper clusters
Overlap (alternate) gatekeepers
Hot Standby Router Protocol (HSRP)
Both overlap and HSRP

Gatekeeper Group Attributes

You can view the general attributes of a selected directory gatekeeper group (GKGrp) in the Design View or the Baseline View:

Expand the dial plan tree to view all components.
Select the gatekeeper group to display the Attributes tab.

Note Enhanced functionality attributes can only be viewed and edited if the VRC feature set for this gatekeeper group is set to dp1.1 or later.

Table 5-6 describes the attributes of a gatekeeper group.

Table 5-6 Gatekeeper Group Attributes

General Attributes	Description
Name	The name of the gatekeeper group. The maximum value is 64 characters.
RAS Port (Registration, Admission, Status)	The port that performs registration, admission, and status signaling. The range is 1 to 65535. The default is 1719.
Type	The type of redundancy system used for this gatekeeper group. The default is none. Values are: None—This gatekeeper group contains only one gatekeeper and it must be the primary gatekeeper. HSRP—Hot Standby Router Protocol. This gatekeeper group contains two gatekeepers; one is primary and one is backup. Cluster—This gatekeeper group contains two gatekeepers; one is primary and one is secondary. All other remaining gatekeepers must be type cluster. Overlap—This gatekeeper group contains two gatekeepers; one is primary and one is overlap. Both—Both HSRP and Overlap. This gatekeeper group contains three gatekeepers. One is primary; one is backup, and one is overlap.
Feature Set	The VRC feature set supported by this gatekeeper group. The default is dp1.0.
Timeout	The server timeout for Gatekeeper Transaction Message Protocol (GKTMP) messages. The range is 1 to 50.
Server Registration Port	Configures a port for the gatekeeper to communicate with a GKTMP server. The range is 1 to 65535.
Tech Prefix	Special characters to be included in the called number. Select from the list of predefined technology prefixes.
Server Flow Enabled	Check this box if you want to enable flow control from the VRC server to the network device. The server flow control monitors the average response time from the server to the GKTMP.
Server Flow High	Can only be set if server flow is enabled. The onset percentage of the timeout value used to mark the server as usable or unusable. The range is 1 to 100. The default is 80.
Server Flow Low	Can only be set if server flow is enabled. The abatement percentage of the timeout value used to mark the server as usable or unusable. The range is 1 to 100. The default is 50.
Max. Queue Length	Can only be set if server flow is enabled. The threshold for the length of the outbound queue on the gatekeeper. The TCP socket between the gatekeeper and GKTMP server queues messages if it has too many to transmit. If the count of outbound queue length on the server reaches this value, the server is marked unusable. The range is 1 to 2000. The default is 50.
Enhanced Functionality	Description
IRR Timer	Sets the IRR reporting interval which it sets on the gateway upon the gateway's registration. This value can only be set if the VRC feature set is dp1.1 or later. The range is 1 to 60.
Server Retry Timer	Specifies the interval (in seconds) to wait between the detection of a server failure and the next attempt to connect to the failed server. This value can only be set if the VRC feature set is dp1.1 or later. The range is 1 to 300.
Disable IRQ Global Request	Disables global requests or call reference values (CRVs) set to zero for newly registering end-points. This value can only be set if the VRC feature set is dp1.1 or later.
Enable Server Absent Reject RRQ	Configures the gatekeeper to reject new registration calls or calls when the connection to the Gatekeeper Transaction Message Protocol (GKTMP) server is down.
Enable Server Absent Reject ARQ	Configures the gatekeeper to reject admission requests when the connection to the GKTMP server is down.
LRQ Reject Unknown Circuit	Enables gatekeeper rejection of location request (LRQ) messages that contain unknown destination carrier IDs descriptions. This value can only be set if the VRC feature set is dp1.1 or later and the CSR route type is carrier or trunk-label.
LRJ Immediate Advance	Disables the gatekeeper from immediately sending a sequential LRQ to the next zone after it receives a location reject (LRJ) from a gatekeeper in the current zone.
LRQ Reject Resource Low	If this parameter is set, the gatekeeper rejects the inter-zone call if all gateways in that zone are marked as almost-out-of-resources.
High Resource Threshold	Sets high call volume thresholds in the gatekeeper for monitoring its gateway. The range is 1 to 99. This value can only be set if the VRC feature set is dp1.1 or later.
Low Resource Threshold	Sets low call volume thresholds in the gatekeeper for monitoring its gateway. The range is 1 to 99. This value can only be set if the VRC feature set is dp1.1 or later.
ICZT Password	Enables generation of the interzone ClearToken (ICZT) password. The range is 6 to 8 alphanumeric characters. You can only set this parameter if the VRC feature set is dp1.1 or later.
LRQ/ARQ Handling
LRQ Reject Unknown	Rejects LRQ messages for unknown prefixes.
ARQ Reject Unknown	Rejects ARQ messages for unknown prefixes.
LRQ Forwarding	Forwards E.164 LRQ messages to remote gatekeepers managing that zone prefix. Values are: Yes—The default, indicates that LRQ forwarding is enabled. No—Indicates not enabled. Note VRC does not support simultaneous LRQs being sent on a gatekeeper for a specific zone prefix (LRQ blast), when multiple gatekeepers have the same prefix.
LRQ Delay	Time interval between successive LRQ messages (100-ms units). The range is 1 to 10.
LRQ Window	Defines the time window (in seconds) during which the gatekeeper collects responses to one or more outstanding LRQs. The range is 1 to 15.
LRQ Receive Password	The LRQ password that the gatekeeper assigns to the zones. Set this password to specify an internal regional password for gatekeeper communication. If it is not set, the default regional password is used.
LRQ Hop-Count	The hop-count configuration for LRQ forwarding on gatekeepers in this gatekeeper group. You can only set this parameter if the VRC feature set is dp1.1 or later. The range is 1-10.
Security	Description
Security Level	The security level. Choose from registration or all. The default is no security level.
Security Type	Enable authentication and authorization on a gatekeeper. Choose from any, h323id, or e164. The default is no security type.
Security Password	The default password that the gatekeeper associates with endpoints when authenticating them with an authentication server. The maximum value is 20 characters.
Separator	The character that endpoints use to separate the H.323-ID from the piggybacked password in the registration. The character is null if H.323 is not used. The value must be one character.
Resource Management	Description
Load Balance	Specifies whether this gatekeeper group is configured for load sharing between the gatekeepers.
Max. Endpoints	Maximum number of endpoints. The range is 0 to 2147483647.
Max. Calls	Maximum number of calls. The range is 0 to 2147483647.
Max. CPU	Maximum percentage of CPU utilization. The range is 10 to 90.
Max. Memory	Maximum percentage of memory used. The range is 10 to 98.
Bandwidth Allocation	Description
Inter-Zone Bandwidth	Specifies the total amount of bandwidth for H.323 traffic from the zone to any other zone. The range is 1 to 10,000,000.
Total Bandwidth	Specifies the total amount of bandwidth for H.323 traffic allowed in the zone. The range is 1 to 10,000,000.
Remote Bandwidth	Specifies the total bandwidth for H.323 traffic between this gatekeeper and any other gatekeeper. The range is 1 to 10,000,000.
Validation State	Indicates whether the Cisco VRC server can contact the element during the Validation process.
Details	An optional text string that gives more details about the status of the element. The maximum value is 255 characters.

Adding a New Gatekeeper Group

You can add one or more gatekeeper groups to a region.

To add a gatekeeper group:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the region you want to add a gatekeeper group to.

Step 3 Right-click and choose Add and Gatekeeper Group from the menus. The Add Gatekeeper Group dialog box appears (Figure 5-11, Figure 5-12, and Figure 5-13).

Figure 5-11 Add Gatekeeper Group Dialog Box (General Attributes)

Figure 5-12 Add Gatekeeper Group Dialog Box (Enhanced Functionality and LRQ/ARQ Handling)

Figure 5-13 Add Gatekeeper Group Dialog Box (Security, Resource Management, and Bandwidth Allocation)

Step 4 Enter the gatekeeper group attribute information. See Table 5-6 for a description of the entry fields.

Step 5 Click Apply to add a new gatekeeper group or Cancel.

Deleting a Gatekeeper Group

To delete a gatekeeper group from the dial plan:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the gatekeeper group to delete.

Step 3 Right-click and choose Delete from the menu. A confirmation dialog box appears.

Step 4 Determine the status of the dial plan configuration. If you choose:

Disable—VRC clears the dial plan configuration and removes the gatekeeper group from the dial plan database during the next commit process.
Do Not Disable—VRC leaves the current dial plan configuration and removes the gatekeeper group, and all elements that reside in the gatekeeper group, from the dial plan database during the next commit process.

The gatekeeper group is removed from the dial plan.

Adding a Zone Circuit

A zone circuit is a zone foreign to VRC that is referred to in a "zone circuit-id" command on a gatekeeper or directory gatekeeper. A zone circuit assigns a trunk carrier (circuit-id) to a gateway.

You can add a zone circuit to a gatekeeper group (GKGrp) or directory gatekeeper group (DGKGrp).

Note You can only add a zone circuit to a gatekeeper group or directory gatekeeper group if the CSR route type of the AD is set to trunk-label or carrier and the VRC feature set of the gatekeeper group is dp1.1 or later.

To add a zone circuit:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the gatekeeper group or directory gatekeeper group you want to add a zone circuit to.

Step 3 Click the Zone Circuit tab.

Step 4 Right-click and select Add from the menu. The Add Zone Circuit dialog box appears (Figure 5-14).

Figure 5-14 Add Zone Circuit Dialog Box

Step 5 Enter the attribute information.

Remote Zone Name—Name of the remote zone.
Remote Zone Domain—Domain name of the remote zone. The maximum value is 255 characters.
Remote Zone IP Address—IP address of the remote zone.
Circuit ID—The trunk carrier ID associated with this remote zone.

Step 6 Click Apply to add the zone circuit or Cancel.

Gatekeeper

A gatekeeper (GK) is an H.323 component on a LAN that:

Provides address translation and control access to the LAN for H.323 terminals and gateways.
Provides other services to the H.323 terminals and gateways, such as bandwidth management and locating gateways.
Maintains a registry of devices in the multimedia network. The devices register with the gatekeeper at startup and request admission to a call from the gatekeeper. A directory gatekeeper is a VRC element.

Gatekeepers perform the following tasks:

Resource Management—Gatekeepers determine the health of H.323 gateways by monitoring registration and nonregistration messages and resource availability indicators.
Call Routing—Gatekeepers provide call routing based on destination E.164 addresses. They can use their knowledge of local gateway health levels to make routing decisions in order to increase network availability of the gateways.
Security—Gatekeepers in conjunction with an external server (for example, RADIUS) may be used for secure call admission.
CDR Generation—Gatekeepers have limited abilities to generate call detail recording (CDR) records for calls either in addition to or instead of from the gateway.

The VRC network supports primary, alternate, overlap, and clustered gatekeepers.

The Cisco VRC network supports the following Cisco products as H.323 gatekeepers:

Cisco 3640 Multiservice Platform
Cisco 3660 Multiservice Platform
Cisco 7200 Series Routers

Gatekeeper Attributes

View the general attributes of a selected gatekeeper from the Baseline View or Design View:

Expand the dial plan tree to view all components.
Locate the gatekeeper and select it to display the Attributes tab.

Table 5-7 describes the attributes of a gatekeeper.

Table 5-7 Attributes of a Gatekeeper

General Attributes	Description
Name	The VRC server contacts the host server to get the host name during discovery or distribution. The maximum value is 64 characters.
IP Address	The IP address of the element.
Standby IP	The IP address the gatekeeper uses to communicate with the gatekeeper group if the gatekeeper group is configured for HSRP.
IOS Version	The Cisco IOS version running on this gatekeeper.
Feature Set	The VRC feature set supported by this gatekeeper. This field is populated by VRC when the gatekeeper is added to the dial plan.
Type	The type of gatekeeper. Choose from secondary, cluster, overlap, or backup. The default is primary. There can be only one primary gatekeeper in a gatekeeper group. If you choose: Secondary—Gatekeeper group that this gatekeeper belongs to must be cluster. There can only be one secondary gatekeeper in a gatekeeper group. Cluster—Gatekeeper group that this gatekeeper belongs to must be type cluster. Overlap—Gatekeeper group that this gatekeeper belongs to must be overlap or both. Backup—Gatekeeper group that this gatekeeper belongs to must be type HSRP or both. There can only be one backup gatekeeper in a gatekeeper group. If you choose type backup, you must set the Standby IP value to the IP address of the primary gatekeeper.
Discovery Status	Determines whether a synchronization is required for this region based on VRC-generated LRQ passwords.
Discovery Details	Additional information regarding the Discovery status.
Validation State	Indicates whether the Cisco VRC server can contact the element during the Validation process.
Details	An optional text string that gives more details about the status of the element. The maximum value is 255 characters.

Adding a Gatekeeper to the Dial Plan

This section describes how to add a gatekeeper to a gatekeeper group in the dial plan.

Note When you add an element to the dial plan, any preexisting dial plan configuration for that element is overwritten when you commit the design.

To add a gatekeeper to a gatekeeper group in the dial plan:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the gatekeeper group you want to add the gatekeeper to.

Step 3 Right-click and choose Add and Gatekeeper from the menus. The Add Gatekeeper to Dial Plan dialog box appears (Figure 5-15).The list of available gatekeepers displays.

Figure 5-15 Add Gatekeeper Dialog Box

Step 4 Select a gatekeeper and click Add. VRC checks for element accessibility and adds the gatekeeper to the dial plan.

If the operation is not successful, click the Details button on the error dialog box to view the log.

Zones

A zone is the collection of H.323 nodes such as gateways, terminals, and multipoint control units (MCUs) registered with the gatekeeper. There can only be one active gatekeeper per zone. These zones can overlay subnets and one gatekeeper can manage gateways in one or more of these subnets.

A zone is another component of the dial plan that contains address resolution authority (ARA), a set of prefixes that are managed by the zone, and routes that are associated with the zone. Zones partition regions by grouping together gateways with the same routing characteristics.

Zones must contain:

At least one gateway
One ingress or egress route
Only one zone alias for each gatekeeper in the gatekeeper group associated with this zone

Zone types:

Managed—Zone within a managed region and consists of gateways and a set of routes. The VRC feature set of a managed zone is set by VRC and is determined by the gateway with the lowest VRC feature set. The feature set of the zone is not established until a gateway is added to the zone.
Unmanaged—Zone that is recognized by VRC but not managed by VRC. It is a zone in a foreign region.

A zone is local or remote in relation to the gatekeeper.

Local zone—Zone in the same gatekeeper group as a gatekeeper
Remote zone—Zone in the gatekeeper group of another gatekeeper

This section contains the following topics about zones in a dial plan:

Managed Zone Attributes

You can view the general attributes of a selected zone from the Design View or the Baseline View:

Expand the dial plan tree to view all components.
Locate the zone and select it to display the Attributes tab.

Table 5-8 describes the attributes of a managed zone.

Table 5-8 Managed Zone Attributes

General Attributes	Description
Name	The name of the zone. The maximum value is 64 characters.
Role	The role for the managed zone in the dial plan. This parameter is required. Regular - A subset of a managed region corresponding to an H.323 zone. You can select this parameter if the region role is regular.
Feature Set	The VRC feature set for this managed zone. The feature set of a managed zone is set by VRC and is determined by the gateway with the lowest feature set. The feature set of the zone is not established until a gateway is added to the zone.
Protocol	H.323
Domain	The domain name of the zone (for example, cisco.com). The maximum value is 255 characters.
Cost	The cost associated with the zone. The range is 1 to 99.
Priority	The priority associated with the zone. The range is 1 to 99.
Gatekeeper Group	The gatekeeper group associated with this zone. The gatekeeper group must be in the same managed region as this managed zone.
Bandwidth Allocation	Description
Inter-zone bandwidth	The maximum aggregate bandwidth for H.323 traffic between one zone and another zone. The range is 1 to 10,000,000.
Total bandwidth	The maximum aggregate bandwidth for H.323 traffic within a zone and between zones (intrazone and interzone). The range is 1 to 10,000,000.
Validation State	Indicates whether the Cisco VRC server can contact the elements during the Validation process. OK—The last validation detected no warnings or errors. Warning—The last validation detected one or more warnings that you might be required to correct before you commit the dial plan, depending on your intent of the dial plan design. Fatal—The last validation detected one or more errors that you must correct before you commit the dial plan.
Details	Additional information regarding the validation state of the zone.

Adding a Managed Zone

A managed zone is a zone within a managed region and consists of gateways and a set of routes.

The VRC feature set of a managed zone is set by VRC and is determined by the gateway with the lowest VRC feature set. The feature set of the zone is not established until a gateway is added to the zone.

Note You must reference a gatekeeper group when you add a managed zone to a managed region. See Adding a New Gatekeeper Group 5-32.

To add a managed zone to a region:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select a region from the list you want to add a zone to.

Step 3 Right-click and choose Add and Managed Zone from the menus. The Add Managed Zone dialog box appears (Figure 5-16).

Figure 5-16 Add Managed Zone Dialog Box

Step 4 Enter the attribute information. See Table 5-8 for a description of each entry field.

Step 5 Click Apply to add the managed zone to the region or Cancel.

Note A managed zone must have a zone alias for each gatekeeper in the gatekeeper group. See the "Creating Zone Aliases" section 5-69.

Unmanaged Zones

An unmanaged zone is recognized by VRC but is not managed by VRC. It is a zone within a foreign region. A foreign region is outside the Administrative Domain (AD). You can add zone prefixes or hopoff technology prefixes to unmanaged zones.

Unmanaged Zone Attributes

Table 5-9 describes the attributes for unmanaged zones.

Table 5-9 Unmanaged Zone Attributes

General Attributes	Description
Name	The name of the zone. The maximum value is 64 characters.
Domain	The domain name of the zone (for example, cisco.com). The maximum value is 255 characters.
Cost	The cost associated with the zone. Values range from 1 to 99.
Priority	The piority associated with the zone. Values range from 1 to 99.
Foreign Domain	A read-only field that indicates whether this is a foreign domain.

Adding an Unmanaged Zone

To add an unmanaged zone to the dial plan:

Step 1 Expand the dial plan tree to view all components.

Step 2 Select the foreign region you want to add a unmanaged zone to.

Step 3 Right-click and choose Add and Unmanaged Zone from the menus. The Add Unmanaged Zone dialog box appears.

Step 4 Enter the unmanaged zone attribute information (see Table 5-9).

Step 5 Click Apply to add the unmanaged zone to the foreign region or Cancel.

Deleting a Zone

To delete a zone from the dial plan:

Step 1 Expand the dial plan tree to view all components.

Step 2 Select the zone that you want to remove.

Step 3 Right-click and choose Delete. Confirm your decision.

Note When you delete a managed zone, any remaining references to the zone might prevent a successful commit of the dial plan design. To locate residual references to the deleted zone, manually validate the design.

Step 4 Click OK to remove the zone or Cancel.

Modifying Local Zone Names

During the Discovery operation, VRC preserves local zone names when you generate a dial plan for:

Alternate and cluster gatekeepers—The alternate and cluster gatekeeper's local zone names are associated with the managed zones in which the gatekeeper is the ARA.
Primary and alternate directory gatekeepers—The local zone name is associated with the directory gatekeeper it came from.

During the Distribution and Commit operations, VRC configures associated gateways to use the zone alias. In certain dial plan configurations, you might be required to modify the local zone name for gatekeepers and directory gatekeepers.

To modify the local zone name for a gatekeeper, you must create a zone alias for the zone where the gatekeeper resides.
To modify the local zone name for a directory gatekeeper, you must modify its local zone name attribute.

This section describes how to modify a local zone name for a gatekeeper.

To modify a local zone name for a gatekeeper:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the managed zone which contains the gatekeeper whose local zone name you want to change.

Step 3 Create a zone alias for this zone.

a. Click the Zone Aliases tab.

b. Right-click and choose Add from the menu. The Add Zone Alias dialog box appears.

c. Enter the following values:

Name - The local zone name for a zone for a particular gatekeeper. Maximum value is 64 characters. The name must be unique in the AD.

Note Note: If the gatekeeper referenced in this zone alias has the Type parameter set to primary or backup, and another gatekeeper in the same gatekeeper group is also a primary or backup, the zone alias in this zone must be identical for those two gatekeepers.

Gatekeeper - The gatekeeper for which the local zone name is used. You can only choose from the gatekeepers in the gatekeeper group referenced by the zone associated with this alias.

d. Create a zone alias for the managed zone. The new local zone name (or zone alias) is applied to the gatekeepers in this zone.

This section describes how to modify a local zone name for a directory gatekeeper.

To modify the local zone name for a directory gatekeeper:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the directory gatekeeper that you want to modify the local zone name for.

Step 3 Click the Attributes tab.

Step 4 Click Edit Attributes.

Step 5 Modify the Local Zone Name entry field.

Step 6 Click Apply. The new local zone name (or zone alias) is applied to the directory gatekeeper.

Zone Parameters

This section describes the zone parameters that you must configure for your dial plan.

Zone Prefixes

A zone prefix is a dialed prefix that identifies the addresses to be serviced by a given gatekeeper. Zone prefixes are area codes and serve the same purpose as the domain names in the H.323-ID address space.

Adding a Zone Prefix

To add a zone prefix to a zone:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the zone to add a zone prefix to.

For a managed zone, select a local zone.
For a unmanaged zone, select a remote zone.

Step 3 Click the Zone Prefixes tab.

Step 4 Right-click and choose Add from the menu.

Step 5 The Add Zone Prefix dialog box appears (Figure 5-17).

Figure 5-17 Add Zone Prefix Dialog Box

Step 6 Enter the attribute information.

Prefix—The zone prefix to support. The prefix field may be a string of up to 64 characters containing only digits, the asterisk (*) , or a period (.).

Note If the zone prefix is for a managed zone, it must be unique. Zone prefixes for a managed zone in the same gatekeeper group cannot be duplicated.

Default gateway priority—The priority for this prefix in the managed zone. The range is 1 to 10. This cannot be set for an unmanaged zone. To add a gateway priority, see Adding a Gateway Priority for a Zone Prefix.

Step 7 Click Apply to add a zone prefix or Cancel.

Deleting a Zone Prefix

This section describes how to delete a zone prefix from a zone.

To delete a zone prefix:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the zone to delete.

Step 3 Right-click and choose Delete from the menu. The Delete Zone Prefix dialog box appears.

Step 4 Click OK to delete the zone prefix or Cancel.

Adding a Gateway Priority for a Zone Prefix

The gateway priority defines how the gatekeeper selects gateways in its local zone for calls to numbers beginning with the associated e164-prefix.

Note Do not use this option to set priority levels for a zone prefix assigned to a remote gatekeeper.

To assign a priority value for a zone prefix on a gateway:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the zone which contains the zone prefix you want to set a priority for.

Step 3 Click the Zone Prefixes tab.

Step 4 Double-click the zone prefix to set a gateway priority.

Step 5 Click the Gateway Priorities tab.

Step 6 Right-click and choose Add from the menu. Select a gateway you want to set a priority for. Repeat this procedure to assign a zone prefix priority for multiple gateways.

Step 7 Enter the priority value. The range is 1 to 10, with 1 being the highest priority. The default is 5.

Step 8 Click Apply to assign the zone prefix priority to the gateway or Cancel.

Zone Subnets

Zone subnets are used to configure a gatekeeper to accept discovery and registration messages sent by endpoints in designated subnets.

This section describes how to add a zone subnet to a gatekeeper and delete a zone subnet from a gatekeeper.

Adding a Zone Subnet

To add a zone subnet:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select a zone to add a zone subnet to.

Step 3 Click the Zone Subnets tab.

Step 4 Right-click and choose Add from the menu. The Add Zone Subnet dialog box appears.

Step 5 Enter the attribute information:

Subnet—The IP address of the subnet. The default is blank. If this field is left blank, the local gatekeeper accepts discovery and registration requests from all subnets.
Mask—The subnet mask. The default is zero. Values must be between 0 and 32.

Step 6 Click Apply to add a new zone subnet or Cancel.

Deleting a Zone Subnet

To delete a zone subnet from the dial plan:

Step 1 Expand the dial plan tree to view all components.

Step 2 Locate the zone which contains the zone subnet to delete.

Step 3 Right-click and choose Delete from the menu. The Delete Confirmation dialog box appears.

Step 4 Click OK to remove the zone subnet or Cancel.

Server Triggers

Server triggers allow you to configure your gatekeepers to:

Connect to a specific back-end server
Listen to any server that wants to connect to it

You can also set the triggers in the gatekeeper configuration so that they send only specified messages. Servers can also dynamically register their triggers with a gatekeeper.

Note Server triggers use the Gatekeeper Transaction Message Protocol (GKTMP) to communicate with servers other than Cisco IOS servers.

Adding a Server Trigger

To add server triggers to a zone:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate a zone or directory gatekeeper group to add a server trigger to.

Step 3 Click the Server Triggers tab.

Step 4 Right-click and choose Add from the menu. The Add Server Trigger dialog box appears (Figure 5-18).

Figure 5-18 Add Server Trigger Dialog Box

Step 5 Enter the attribute information.

Table 5-10 describes the entry fields in the Server Trigger dialog box.

Table 5-10 Server Trigger Attributes

General Attributes	Description
Message	Configures triggering on RAS message types. Choose one message type from ARQ, DRQ, IRR, LCF, LRJ, LRQ, RAI, RRQ, or URQ. You can only choose IRR if one of the following conditions exists: This server trigger is contained by a directory gatekeeper group with a VRC feature set of dp1.1 or later. This server trigger is contained directly by a managed zone whose gatekeeper group attribute references a gatekeeper group with a VRC feature set of dp1.1 or later.
Priority	The priority for each trigger. The range is 1 to 20, with 1 being the highest priority.
Route Server	The route server associated with the gatekeeper for this server trigger.
Information Only	Specifies whether this server trigger is for information only. There is no need to wait for acknowledgment.
Destination Type	Choose from e-mail, e164, or h323-id. You can only set this attribute if the message type is ARQ, LRQ, LCF, IRR, or LRJ. You must also specify destination information.
Destination	The value must be an address of the type specified by the destination type attribute.
Redirect Reason	Configure a redirect reason to trigger on if the message type is ARQ, IRR, or LRQ. The range is 0 to 65535. Reserved values are: 0-unknown, 1-call forwarding busy or called DTE busy, 2-call forwarded no reply, 4-call deflection, 9-called DTE out of order, 10-call forwarding by the call DTE, and 15-call forwarding unconditionally.
Remote Ext. Address	The remote extension address. The value can be any string up to 255 characters.
Endpoint Type	Choose from gatekeeper, h320-gateway, mcu, other gateway, proxy, terminal, voice-gateway.
Technology Prefix	The default technology prefix for this server trigger if the message type is RRQ or URQ.

Step 6 Click Apply to add a new server trigger or Cancel.

Deleting a Server Trigger

This section describes how to delete a server trigger.

To delete server triggers:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the zone that contains the server trigger to delete.

Step 3 Click the Server Triggers tab.

Step 4 Select the server trigger to delete.

Step 5 Right-click and choose Delete from the menu.

Step 6 Click OK to remove the server trigger from the dial plan or Cancel.

Creating Route Scopes

A route scope is a collection of voice ports grouped for routing purposes. The collection may be in the form of a single voice port, a trunk group, a hunt group, or an entire gateway.

Route scopes are assigned to routes to specify where the routes originate or terminate. For example, if a route scope of gateway is assigned to an ingress route, all voice ports on the gateway are configured to originate calls for that route. Similarly, if a route scope of type voice port is assigned to an egress route, only that voice port is configured to terminate the route.

Note You must create a route scope for a zone before you can set up ingress and egress routes.

To create a route scope for a zone:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the zone you want to create a route scope for.

Step 3 Click the Route Scopes tab.

Step 4 Right-click and choose Add from the menu. The Add Route Scope dialog box appears (Figure 5-19).

Figure 5-19 Add Route Scope Dialog Box

Step 5 Enter the attribute information.

Name—The name of the route scope. The maximum value is 64 characters.
Feature Set—The VRC feature set supported by this route scope. The default is dp1.0.
Type—Specifies where the routes in this route scope terminate. Choose from Gateway, Voice Port, Trunk Group, or Hunt Group. Trunk Group is not available if the feature set is dp1.0.
Description—An optional text description of this route scope. The maximum value is 255 characters.

Step 6 Click Apply to create the route scope for the zone or Cancel.

Note During the Discovery operation, VRC might rename your route scope. To change the route scope name back after Discovery, you must manually edit this attribute in the Design View.

Deleting a Route Scope

When you delete a route scope, any remaining references to the route scope might prevent a successful commit of the dial plan design. To locate residual references to the deleted route scope, manually validate the design.

To delete a route scope from the dial plan:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the zone which contains the route scope that you want to delete.

Step 3 Click the Route Scope tab.

Step 4 Select the route scope to delete.

Step 5 Right-click and select Delete from the menu.

Step 6 Click OK to confirm the delete or Cancel.

Configuring Egress and Ingress Routes

This section describes egress and ingress routes, which represent the call routing paths entering or leaving a zone.

An egress route defines an internal zone behavior for a call that is received from the IP network. An egress route specifies the subset of gateways that can terminate the call and the subset of interfaces on those gateways (for example, a set of voice ports), and also any required translations.
An ingress route defines an internal zone behavior on the ingress side of the call, when the call is received from the PSTN. An ingress route specifies the address resolution authority (ARA) that is used to resolve the call destination (for example, the order might be: gatekeeper, OSP Server, and hairpinning back to the PSTN), and all required number translations.)

Note You must have a route scope defined for egress and ingress routes before you can add them to the dial plan.

Adding an Egress Route

An egress route represents the call path leaving the VoIP network to an egress gateway. You define egress routes at the zone level. An egress route:

Defines an internal zone behavior for a call that is received from the IP network.
Specifies the subset of gateways that can terminate the call and the subset of interfaces on those gateways (for example, a set of voice ports), and also any required translations.
Encapsulates parameters necessary for both carrier-sensitive and prefix-based routing and other non-dial plan parameters such as codec or DTMF-relay.

To add an egress route:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select a zone to add an egress route to.

Step 3 Click the Egress Routes tab. The Add Egress Route dialog box appears (Figure 5-20 and Figure 5-21).

Figure 5-20 Add Egress Routes Dialog Box (General Attributes)

Figure 5-21 Add Egress Routes Dialog Box (Translation Profiles and Application)

Step 4 Enter the attribute information.

Table 5-11 describes the entry fields in the Add Egress Route dialog box.

Table 5-11 Add Egress Route Attributes

General Attributes	Description
Name	The name of the egress route. This name must be unique among all ingress and egress route names in the managed zone. Maximum value 64 characters.
Dial-Peer Type	Determines the dial peers created in the VRC-generated CLI. Both - VRC configures an inbound POTS and an outbound VoIP dial peer for this route. POTS - VRC configures a single POTS dial peer for this route. VoIP - VRC configures a single VoIP dial peer for this route.
Pattern	The destination pattern, or dialed digit string supported by this route. Legal characters: ^[][0-9,ABCD#.?+%()-^]T?(\$)?$. The maximum value is 32 characters. This parameter is required if: The dial peer type is POTS or both, AND the target carrier ID is not set, AND a tech prefix is not set. The dial peer type is VoIP or both AND the DNIS is not set, AND the ANI is not set, AND the source carrier ID is not set.
ANI	The calling number for which this route is applicable. Legal characters: ^((\+)?([0-9,#ABCD]+)\.T?)$. The maximum value is 32 characters.
DNIS	The dialed number identification service (the called number). Legal characters: ^[][0-9,ABCD#.?+%()-^]T?(\$)?$. The maximum value is 32 characters.
Priority	The priority of this route. The range is 0 to 10, with 0 being the hightest priority. The default is 5.
Tech. Prefix	The technology prefix used for this route.
Feature Set	The VRC feature set supported by this egress route. The default is dp1.0.
Voice Class Codec	The Voice Class Codec used by the inbound VoIP dial peer.
Numbering Type	The numbering type. Choose from international, national, abbreviated, network, reserved, subscriber, and unknown. The default is blank.
Huntstop	Specifies whether to add a huntstop to the last dial peer in this route.
Routing Scope	The scope of this egress route. If you choose: Managed zone—Zone must be the same zone to which this egress route belongs, and the VRC feature set of the zone must be the same as or better than the feature set of this egress route. Route scope—VRC feature set of the route scope must be the same as or better than the feature set of this egress route.
Source Carrier	Specifies the carrier ID or trunk label for the inbound VoIP dial peer. This parameter can only be set if the VRC feature set is dp1.1 or later and the CSR route type of the AD is carrier or trunk-label.
Target Carrier	Specifies the carrier ID or trunk label for the outbound POTS dial peer. This parameter can only be set if the VRC feature set is dp1.1 or later and the CSR route type is carrier or trunk-label.
Description	An optional description of this egress route. The maximum value is 64 characters.
Translation Profiles	Description
Incoming Translation Profile	Associates a translation profile for the incoming side of gateway. If you set this optional parameter, the VRC feature set of this egress route must be dp1.1 or later. If you set this parameter, you must also reference a translation profile with a feature set of dp1.1 or later.
Outgoing Translation Profile	Associates a translation profile for the outgoing side of the gateway. If you set this optional parameter, the VRC feature set of the translation profile must match the VRC feature set of this egress route.
Call-Block Profile	Adds a call blocking profile to the inbound dial peer for this route. If you set this optional parameter, the VRC feature set of this egress route must be dp1.1 or later. You must also use a translation profile with a feature set of dp1.1 or later.
Disconnect Cause	You must set this if a call blocking profile is set. Choose from call-rejected, invalid-number, unassigned-number, or user-busy.
Application	Description
Inbound Application	An inbound voice application in this zone to be applied to this ingress route. You can only set this parameter if the dial peer type is set to VoIP or both.
Inbound DNIS Map	The DNIS map to apply to the inbound application. You can only set this parameter if the dial peer type is both or VoIP AND you have set an inbound application for this route.
Outbound Application	An outbound voice application in this zone to be applied to this ingress route. You can only set this parameter if the dial peer type is set to POTS or both.
Outbound DNIS Map	The DNIS map to apply to the outbound application. You can only set this parameter if the dial peer type is both or POTS AND you have set an outbound application for this route.
Validation State	Indicates whether the Cisco VRC server can contact the element during the Validation process.
Details	An optional text string that gives more details about the status of the element. The maximum value is 255 characters.

Step 5 Click Apply to add the egress route to the zone or Cancel.

Deleting an Egress Route

To delete an egress route:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the zone where the egress route resides.

Step 3 Click the Egress Routes tab.

Step 4 Select the egress route to delete.

Step 5 Right-click and choose Delete from the menu.

Step 6 Click OK to remove the egress route from the dial plan or Cancel.

Adding an Ingress Route

An ingress route represents the call path entering the VoIP network ingress gateways to their ARA. An ingress route:

Defines an internal zone behavior on the ingress side of the call, when the call is received from PSTN.
Specifies the ARA that is used to resolve the call destination (that is, it could be in the following order: gatekeeper, OSP Server, hairpinning back to PSTN), and all required number translations, such as preferred target carrier ID.
Encapsulates non-dial plan parameters such as direct inward dial (DID), applications, and codec.

To add an ingress route:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select a zone to add an ingress route to.

Step 3 Click the Ingress Routes tab.

Step 4 Right-click and choose Add from the menu. The Add Ingress Route dialog box appears (Figure 5-22 and Figure 5-23).

Figure 5-22 Add Ingress Route Dialog Box (General Attributes)

Figure 5-23 Add Ingress Route Dialog Box (Translations Profiles and Application)

Step 5 Enter the attribute information.

Table 5-12 describes the entry fields in the Add Ingress Route dialog box.

Table 5-12 Add Ingress Route Attributes

General Attributes	Description
Name	The name of the egress route. This name must be unique among all ingress and egress route names in the managed zone. Maximum value 64 characters.
Dial-Peer Type	Determines the dial peers created in the VRC-generated CLI. Both - VRC configures an inbound POTS and an outbound VoIP dial peer for this route. POTS - VRC configures a single POTS dial peer for this route. VoIP - VRC configures a single VoIP dial peer for this route.
Pattern	The destination pattern, or dialed digit string supported by this route. Legal characters: ^[][0-9,ABCD#.?+%()-^]T?(\$)?$. The maximum value is 32 characters. This parameter is required if: The dial peer type is POTS or both, AND the target carrier ID is not set, AND a tech prefix is not set. The dial peer type is VoIP or both AND the DNIS is not set, AND the ANI is not set, AND the source carrier ID is not set.
ANI	The calling number for which this route is applicable. Legal characters: ^((\+)?([0-9,#ABCD]+)\.T?)$. The maximum value is 32 characters.
DNIS	The dialed number identification service (the called number). Legal characters: ^[][0-9,ABCD#.?+%()-^]T?(\$)?$. The maximum value is 32 characters.
Priority	The priority of this route. The range is 0 to 10, with 0 being the hightest priority. The default is 5.
Tech. Prefix	The technology prefix used for this route.
Feature Set	The VRC feature set supported by this egress route. The default is dp1.0.
Voice Class Codec	The Voice Class Codec used by the inbound VoIP dial peer.
Numbering Type	The numbering type. Choose from international, national, abbreviated, network, reserved, subscriber, and unknown. The default is blank.
Huntstop	Specifies whether to add a huntstop to the last dial peer in this route.
ARA Type	The address resolution authority to use for this route. Choose from one of the following: OSP Server—OSP server associated with the zone assigns the route to a gateway. GKGrp—RAS assigns the route to a gateway. ipv4—A route parameter assigns the route to a gateway.
Routing Scope	The scope of this egress route. If you choose: Managed zone—Zone must be the same zone to which this egress route belongs, and the VRC feature set of the zone must be the same as or better than the feature set of this egress route. Route scope—VRC feature set of the route scope must be the same as or better than the feature set of this egress route.
Source Carrier	Specifies the carrier ID or trunk label for the inbound VoIP dial peer. This parameter can only be set if the VRC feature set is dp1.1 or later and the CSR route type of the AD is carrier or trunk-label.
Target Carrier	Specifies the carrier ID or trunk label for the outbound POTS dial peer. This parameter can only be set if the VRC feature set is dp1.1 or later and the CSR route type is carrier or trunk-label.
Description	An optional description of this egress route. The maximum value is 64 characters.
Translation Profiles	Description
Incoming Translation Profile	Associates a translation profile for the incoming side of gateway. If you set this optional parameter, the VRC feature set of this egress route must be dp1.1 or later. If you set this parameter, you must also reference a translation profile with a feature set of dp1.1 or later.
Outgoing Translation Profile	Associates a translation profile for the outgoing side of the gateway. If you set this optional parameter, the VRC feature set of the translation profile must match the VRC feature set of this egress route.
Call-Block Profile	Adds a call blocking profile to the inbound dial peer for this route. If you set this optional parameter, the VRC feature set of this egress route must be dp1.1 or later. You must also use a translation profile with a feature set of dp1.1 or later.
Disconnect Cause	You must set this if a call blocking profile is set. Choose from call-rejected, invalid-number, unassigned-number, or user-busy.
Application	Description
Inbound Application	An inbound voice application in this zone to be applied to this ingress route. You can only set this parameter if the dial peer type is set to VoIP or both.
Inbound DNIS Map	The DNIS map to apply to the inbound application. You can only set this parameter if the dial peer type is both or VoIP AND you have set an inbound application for this route.
Outbound Application	An outbound voice application in this zone to be applied to this ingress route. You can only set this parameter if the dial peer type is set to POTS or both.
Outbound DNIS Map	The DNIS map to apply to the outbound application. You can only set this parameter if the dial peer type is both or POTS AND you have set an outbound application for this route.
Validation State	Indicates whether the Cisco VRC server can contact the element during the Validation process.
Details	An optional text string that gives more details about the status of the element. The maximum value is 255 characters.

Step 6 Click Apply to a add a new ingress route or Cancel.

Deleting an Ingress Route

To delete an ingress route:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the zone where the ingress route resides.

Step 3 Click the Ingress Routes tab.

Step 4 Select the ingress route to delete.

Step 5 Right-click and choose Delete from the menu.

Step 6 Click OK to remove the ingress route from the dial plan or Cancel.

Rule Descriptions

Rule descriptions define sets of translation rules for a zone. The rules provide a mechanism to perform digit manipulation.

This section describes how to add and delete rule descriptions.

Adding a Rule Description

To add a rule description:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select a zone to add a rule description to.

Step 3 Click the Rule Descriptions tab.

Step 4 Right-click and choose Add from the menu.

Step 5 Enter the attribute information.

Tag—The tag number by which the rule set is referenced.

The range is 1 to 10 if the VRC feature set or the parent rule description is dp1.0.
The range is 1 to 15 if the VRC feature set of the parent rule description is dp1.1 or later.

Feature Set—The VRC feature set supported by this rule description. The default is dp1.0.

Step 6 Click Apply to add the rule description or Cancel.

Deleting a Rule Description

To delete a rule description:

Step 1 Expand the dial plan tree to view all components.

Step 2 Select the zone where the rule description resides.

Step 3 Click the Rule Descriptions tab

Step 4 Select the rule description to delete.

Step 5 Right-click and choose Delete from the menu. The delete confirmation dialog box appears.

Step 6 Click OK to remove the rule description from the dial plan or Cancel.

Adding a Translation Rule

Translation rules apply a set of rules to a calling party number (Automatic Number Identification [ANI]) or a called party number (Dial Number Information Service [DNIS]) for both incoming and outgoing calls within Cisco H.323 voice-enabled gateways.

To add a translation rule:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select the zone which contains the rule description that you want to add a translation rule to.

Step 3 Click the Rule Descriptions tab. The list of rule descriptions for this zone is displayed.

Step 4 Double-click the rule description that you want to add a translation rule to.

Step 5 Click the Rules tab.

Step 6 Right-click and choose Add from the menu.

Step 7 Enter the rule description attributes.

Table 5-13 describes the entry fields in the Add Rule dialog box.

Table 5-13 Attributes of the Add Rule Dialog Box

General Attributes	Description
Number	The number assigned to this translation rule. The range is: 1 to 10 if the VRC feature set for the parent rule description is dp1.0. 1 to 15 if the feature set of the parent rule description is dp1.1 or later.
Reject	This optional parameter can only be set if the parent translation rule has a feature set of dp1.1 or later.
Search Pattern	The maximum value is 32 characters.
Replacement Pattern	This parameter is required if the Reject parameter is not set. The maximum value is 32 characters.
Match Type	The match type for this translation rule. Choose from any, international, national, abbreviated, network, reserved, subscriber, and unknown. You must also set a replacement type.
Replacement Type	The replacement type for this translation rule. Choose from international, national, abbreviated, network, reserved, subscriber, and unknown. This parameter must be set if the Match Type parameter is set and the Reject parameter is not set.
Match Plan	Specifies the match plan for the Match Type parameter. Choose from any, data, ermes, isdn, national, private, reserved, telex, and unknown. This parameter can only be set if the parent rule description has a feature set of dp1.1 or later.
Replace Plan	Specifies the match plan for the Match Type parameter. This parameter must be set if the Match Type parameter is set and the Reject parameter is not set. Choose from data, ermes, isdn, national, private, reserved, telex, and unknown. This parameter can only be set if the parent rule description has a feature set of dp1.1 or later.
Validation State	Indicates whether the Cisco VRC server can contact the element during the Validation process.
Details	An optional text string that gives more details about the status of the element. The maximum value is 255 characters.

Step 8 Click Apply to add this translation rule to the rule description or Cancel.

Translation Profiles

Translation profiles provide a way to group ANI and DNIS translation rules together to use on ingress or egress routes.

You must have your rule descriptions set up before you can add them to a translation profile.

Adding a Translation Profile

To add a translation profile to a dial plan:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select a zone to add a translation profile to.

Step 3 Click the Translation Profiles tab.

Step 4 Right-click and choose Add from the menu. The Add Translation Profile dialog box appears (Figure 5-24).

Figure 5-24 Add Translation Profile Dialog Box

Step 5 Enter the attribute information.

Table 5-14 describes the fields in the Add Translation Profile dialog box.

Table 5-14 Translation Profile Attributes

General Attributes	Description
Tag	A unique ID for this rule description. The maximum value is 31 characters.
Feature Set	The VRC feature set for this translation profile. The default is dp1.0.
ANI Rule	The ID of the rule description meant for ANI. Choose from the available ANI rules in the drop-down list. You must reference a rule description with the same feature set as this translation profile.
DNIS Rule	The ID of the rule description meant for DNIS. You must reference a rule description with the same feature set as this translation profile.
Redirect Rule	You can set this optional parameter if the feature set of this translation profile is dp1.1 or later. You must reference a rule description with a feature set of dp1.1 or later.
Validation State	Indicates whether the Cisco VRC server can contact the element during the Validation process.
Details	An optional text string that gives more details about the status of the element. The maximum value is 255 characters.

Step 6 Click Apply to add a new translation profile or Cancel.

Deleting a Translation Profile

Note When you delete a translation profile, any remaining references to the translation profile might prevent a successful commit of the dial plan design. To locate residual references to the deleted translation profile, manually validate the design.

To delete a translation profile from a dial plan:

Step 1 Locate the zone that contains the translation profile.

Step 2 Click the Translation Profiles tab.

Step 3 Select the translation profile to delete.

Step 4 Right-click and choose Delete from the menu. The translation profile is deleted.

Managing Number Expansion Sets

In most corporate environments, the telephone network is configured so that you can reach a destination by dialing only a portion of the full telephone number. You can define an extension number as the destination pattern for a dial peer.

Adding a number expansion set enables you to define a set of digits for the router to add to the beginning of a dialed string before passing it to the remote telephony device. This reduces the number of digits that a user must dial to reach a remote location.

Adding a Number Expansion Set

Note You must specify number expansion rules for all number expansion sets added to the dial plan.

To add a number expansion set:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Select a zone to add a number expansion set to.

Step 3 Click the Number Expansion Sets tab.

Step 4 Right-click and choose Add from the menu. The Add Number Expansion Set dialog box appears.

Step 5 Enter the name of a number expansion set. The maximum value is 64 characters.

Step 6 Click Apply to add the number expansion set or Cancel.

Deleting a Number Expansion Set

To delete a number expansion set from a zone:

Step 1 Locate the zone which contains the number expansion set you want to delete.

Step 2 Click the Number Expansion Sets tab.

Step 3 Right-click and choose Delete from the menu. The number expansion set is deleted.

Adding Number Expansion Rules

To add a number expansion rule for a number expansion set:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the zone which contains the number expansion set you want to add a number expansion rule for.

Step 3 Click the Number Expansion Sets tab. The list of number expansion sets for this zone is displayed.

Step 4 Double-click the number expansion set you want to add a number expansion rule to.

Step 5 Click the Rules tab.

Step 6 Click Add Rule.

Enter the number expansion rule attribute information.

Number—Must be an integer between 0 and 2147483647.
Search Pattern—Value can be a string up to 32 characters.
Replacement Pattern—Value can be a string up to 32 characters.

Step 7 Click Apply to add the number expansion rule or Cancel.

Deleting Number Expansion Rules

Note When you delete a number expansion rule, any remaining references to the number expansion rule might prevent a successful commit of the dial plan design. To locate residual references to the deleted number expansion rule, manually validate the design.

To delete a number expansion rule:

Step 1 Select the zone which contains the number expansion set you want to delete the number expansion rule from.

Step 2 Click the Number Expansion Sets tab. The list of number expansion sets for this zone is displayed.

Step 3 Double-click the number expansion set which contains the number expansion rule you want to delete.

Step 4 Click the Rules tab. Select the number expansion rule you want to delete.

Step 5 Right-click and choose Delete from the menu. The rule is deleted from the number expansion set.

Creating Zone Aliases

A zone alias is the name a gatekeeper assigns to a local zone name. VRC creates a zone alias during the Discovery operation or you can enter a zone alias manually.

When a gateway registers with a gatekeeper, it uses the zone alias name. A managed zone must have one zone alias for every gatekeeper in the gatekeeper group.

To manually create a zone alias for a zone:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the zone that you want to create a zone alias for.

Step 3 Click the Zone Aliases tab.

Step 4 Right-click and choose Add from the menu. The Add Zone Alias dialog box appears (Figure 5-25).

Figure 5-25 Add Zone Alias Dialog Box

Step 5 Enter the attribute information.

Name—Local zone name for a zone for a particular gatekeeper. The name must be unique among connected regions. The maximum value is 64 characters.
Gatekeeper—Gatekeeper for which the local zone name is used. You can only choose from the gatekeepers in the gatekeeper group referenced by the zone associated with this alias.

Step 6 Click Apply to create the zone alias or Cancel.

Managing a Source Group

A source group is a template for setting individual voice source groups. A source group allows you to set the same parameters for all gateways in a zone. The parameters set in a zone's source group are used when you add a voice source group to the gateway.

To apply these parameters to a particular gateway in a zone, see Adding a Voice Source Group.

Creating a Source Group

To create a source group for a zone:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the zone to add a source group to.

Step 3 Click the Source Group tab.

Step 4 Right-click and select Add from the menu. The Add Source Group dialog box appears (Figure 5-26).

Figure 5-26 Add Source Group Dialog Box

Step 5 Enter the attribute information.

Table 5-15 describes the entry fields in the Add Source Group dialog box.

Table 5-15 Source Group Attributes

General Attributes	Description
Name	The name of the source group. The maximum value is 31 characters.
Disconnect Cause	Reason for disconnecting. Choose from call-rejected, invalid-number, unassigned-number, user-busy.
Incoming Translation Profile	Associates a translation profile for the incoming side of the gateway. The VRC feature set of the translation profile must be dp1.1 or later.
H.323 Zone	The maximum value is 127 characters.
Description	The maximum value is 63 characters.
Source Carrier	Specifies the inbound VoIP dial peer. Can only be set if the CSR route type of the AD is set to carrier or trunk-label.
Target Carrier	Specifies the outbound POTS dial peer. Can only be set if the CSR route type of the AD is set to carrier or trunk-label.

Step 6 Click Apply to add a source group or Cancel.

Deleting a Source Group

To delete a source group from a zone:

Step 1 Expand the dial plan tree to view all components.

Step 2 Locate the zone to delete the source group from.

Step 3 Click the Source Group tab.

Step 4 Locate the source group that you want to delete.

Step 5 Right-click and choose Delete from the menu.

Step 6 Click OK to delete the source group from a dial plan or Cancel.

Managing Hopoff Technology Prefixes

A hopoff zone is the point at which a call transitions from H.323 to a non-H.323 network. A hopoff technology prefix allows you to specify a technology prefix for a certain zone that you want to use as a hopoff zone. You can specify a hopoff technology prefix for a managed zone or an unmanaged zone.

Note You must already have a technology prefix added to the dial plan before you can specify it for a hopoff zone and you must be in the Design View.

To add a hopoff technology prefix to a zone:

Step 1 Expand the dial plan tree to view all components.

Step 2 Select a zone to add a hopoff technology prefix to.

Step 3 Click the Hopoff Tech Prefixes tab.

Step 4 Right-click and choose Add from the menu. The Add Hopoff Tech Prefix dialog box appears (Figure 5-27).

Figure 5-27 Add Hopoff Tech Prefix Dialog Box

Step 5 Enter the attribute information.

Technology Prefix—Select one predefined technology prefix from the list.

Note If you are specifying a hopoff technology prefix for a managed zone, then the managed zone must contain at least one egress route that references this same technology prefix.

Description—This optional field is a text description of this hopoff technology prefix. The maximum value is 255 characters.

Note A zone can have multiple hopoff technology prefixes.

Step 6 Click Apply to add the hopoff technology prefix or Cancel .

Gateways

This section contains the following topics about gateways:

Description

A gateway (GW) is a Network Access Server (NAS) which acts as an interface between a circuit-switched Public Switched Telephone Network (PSTN) and a packetized H.323 Voice-over-IP (VoIP) network. It is a network element in a dial plan that VRC manages.

A gateway is the point at which a circuit-switched fax or voice call is encoded (using a codec) and repackaged into IP packets, or vice versa. A gateway initiates a call setup with an H.323 gatekeeper through H.225 RAS. The originating gateway terminates the VoIP call to an appropriate destination gateway with the gatekeeper's assistance.

You can perform the following tasks when using VRC:

Add hunt groups and voice source groups to a gateway
Edit voice port and trunk group attributes

The VRC network supports the following Cisco platforms as H.323 gateways:

Cisco 1750 Access Router
Cisco Catalyst 2600 Series Routers
Cisco 3600 Series Routers
Cisco AS5300 Series Universal Access Server
Cisco AS5350 Universal Gateway
Cisco AS5400 Series Universal Gateways
Cisco AS5800 Series Universal Access Servers
Cisco AS5850 Universal Gateway
Cisco 7200 Series Routers

Gateway Attributes

To view the attributes of a gateway, select the gateway in the dial plan tree. Table 5-16 describes the attributes of a gateway.

Table 5-16 Gateway Attributes

General Attributes	Description
Name	The gateway name. This corresponds to the name part of the full DNS host name.
H.323 ID	The H.323-ID for the gateway. This is usually the fully qualified e-mail ID, with the domain name being the same as this gateway's gatekeeper.
IP Address	The IP address of the gateway. This read-only field is populated by the VRC client.
Feature Set	The VRC feature set supported by this gateway. This field is populated by VRC when the gateway is added to the dial plan.
IOS Version	The Cisco IOS version running on this gateway.
Incoming VoIP Trans. Profile	Associates a translation profile for the incoming side of gateway. The translation profile must reside in the same managed zone as the gateway. The VRC feature set of the translation profile must match the feature set of the gateway.
Number Expansion Set	The number expansion set for this gateway.
OSP Enabled	Specifies if this gateway responds to OSP servers.
Circuit	Assigns a trunk label or carrier ID (circuit-ID) to a gateway. You can only set this parameter if the gateway's VRC feature set is dp1.1 or later, the managed zone's gatekeeper group is set to a gatekeeper group with a VRC feature set of dp1.1 or later and a CSR route type of carrier or trunk-label.
Max. Calls	Specifies the maximum number of voice or data calls allowed on the trunk group. You can only set this parameter if the circuit parameter is set. The range is 1 to 10000.
Needs Reactivation	This is a read-only field and indicates whether you need to reactivate the gateway because the configuration has been changed. The default is Yes. You cannot commit a dial plan design if one or more gateways have this attribute set to Yes.
RTCP
Timer Receive RTCP	Enables the Real-Time Control Protocol (RTCP) timer and configures a multiplication factor for the RTCP timer interval. The range is 2 to 1000. This parameter can only be set if the VCR feature set for this gateway is dp1.1 or later.
IP RTCP Report Interval	Configures the average reporting interval between subsequent RTCP report transmission. The range is 1 to 65535. This parameter can only be set if the VCR feature set for this gateway is dp1.1 or later.
Status	Indicates whether the Cisco VRC server can contact the elements during the Validation process. OK—The last validation detected no warnings or errors. Warning—The last validation detected one or more warnings that you might be required to correct before you commit the dial plan, depending on your intent of the dial plan design. Fatal—The last validation detected one or more errors that you must correct before you commit the dial plan.
Details	An optional text string that gives more details about the status of the element. The maximum value is 255 characters.
Security
Access Token	A password for registration. The maximum value is 20 characters. The default is blank.
Security Level	The security level of the gateway. You must set a security level if the access token is set. Choose from endpoint, per-call, or all.
Resource Management
Resource Threshold All	Applies the high and low parameter settings to all monitored H.323 resources. This parameter can only be set if Resource Threshold High and Resource Threshold Low are set.
Resource Threshold High	A resource utilization level that triggers an RAI message that indicates that H.323 resource usage is high. The range is 1 to 100. The default is blank.
Resource Threshold Low	A resource utilization level that triggers an RAI message that indicates that H.323 resource usage has dropped below the high usage level. The range is 1 to 100. The default is blank.
Emulate H.323 Bandwidth	If checked, allows the gateway to terminate calls using H.323 bidirectional bandwidth. This parameter can only be set if the VCR feature set for this gateway is dp1.1 or later.

Adding a Gateway to the Dial Plan

A gateway must be defined in the topology before you can add it to the dial plan.

To add a gateway to the dial plan:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the managed zone to add a gateway to.

Step 3 Right-click and choose Add and Gateway from the menu. The Add Gateway to Dial Plan dialog box appears (). This dialog box lists the IP addresses of available gateways.

Figure 5-28 Add Gateway Dialog Box

Step 4 Select gateway and click the Add button. An information dialog box appears, asking you to confirm.

Step 5 Click Add to add the gateway or Cancel .

Step 6 To edit gateway attributes, click the Edit Attributes button.

Finding Terminating Gateways

You can identify and list the set of gateways which might terminate a given dial string. For more information, see Finding Terminating Gateways.

Call Path Verification

The call path verification feature in VRC is used to trace a call in a Voice-over-IP (VoIP) H.323 network. The call is traced from the originating gateway, through all gatekeepers used to resolve the destination address, and finally to the terminating gateway.

Note Routes identified with target ipv4.* or dns.* are reported but not traced or verified by VRC.

To trace the call path using VRC, you must enter the following information:

Call source—Choose the ingress gateway, or the voice port or trunk group for the ingress gateway.

The call source is the device from which the call is traced. It is always a gateway, but you can provide more details by selecting the trunk group or the voice port through which the call was received.

Rules to follow when choosing the call source:

Select the interface for which translation rules are defined so that the translation rules can be applied to the called number.
Do not define the translations for both trunk groups and voice ports. With this configuration, the router executes the voice port rules and ignores the trunk group rules. VRC does not have enough information to tie voice port rules with trunk group rules and cannot determine which rules to apply.
If there are no translation rules defined on voice ports or trunk groups, and you are using carrier-based routing, then select the trunk group. The source carrier determined by the trunk group has a direct affect on the call routing.

DNIS—The number received from the Public Switched Telephone Network (PSTN) by the originating gateway. It can contain the technology prefix, if it is present in the original number.
Target Carrier—Select from the list of target carriers defined in the Administrative Domain (AD). This is not required if the CSR route type of the AD is set to None (for prefix routing only).

Rules to follow when choosing the target carrier:

You cannot configure a target carrier on the originating gateway, but it can be added to the call path by the routing server if your system is configured to use one.
VRC cannot contact the route server to query for the target carrier information for the given entry parameters (source carrier, time of day, current traffic patterns).

However, you can presume the target carrier that the routing server would select under the current conditions. VRC verifies that all devices in the path are correctly configured to route and terminate the call. If the routing server would return, as a result of a query, the terminating gateway (thus shortening the routing path and not requiring the correct gatekeeper configuration), the system configured by VRC should have all gatekeeper connectivity in place.

Note The target carrier setting is optional. If you leave this field blank, you test the behavior of the system with the routing server down or not used.

Translation Profiles—The translation profiles applied during call path verification are determined bythe source of the call path verification request. You do not select them.
Translation Rules—The following translation rules are executed to trace a call path:

Voice port translation rules (only if you select a voice port)
Trunk group translation rules (only if you select a trunk group)

You receive a warning if there are voice port rules defined.

Ingress gateway number expansions
Ingress route inbound translation rules
Ingress route outbound translation rules
Egress gateway number expansions
Egress gateway VoIP translation rules

Note VRC call path verification does not recognize voice source groups, their translation rules, or ingress route call blocking.

Call Routing Process—After applying all ingress translation rules, the resulting called number (without associated technology prefixes) is matched against the list of zone prefixes for all zones that are accessible from the ingress gatekeeper or directory gatekeeper.

If a technology prefix is part of the called number, either as part of the original DNIS or added by the gateway (this can be set in the ingress route), it is matched against the list of hopoff zones that are accessible from the ingress gatekeeper or directory gatekeeper.

The routing between gatekeepers must be strictly prefix or technology prefix based even in the carrier-based domain. This is why the routing server usually selects the terminating zone and the gateway. Gatekeepers do not exchange the correct information to enable carrier-based routing.

When the egress gatekeeper is selected, all provided data is used to select the gateway that meets the given criteria (the prefix, technology prefix and target carrier). Gatekeepers select the terminating gateway based on the static prefix priority list (by default every gateway registered in the zone can accept the call), dynamically registered technology prefix, and dynamically registered list of trunk groups and carriers.

Every gateway that meets the specified criteria is included in the call path verification, but only the gateways with at least one egress route that matches target carrier and/or destination pattern successfully terminates the call and only those paths are listed as confirmed successful paths. The other paths are reported with the error message that indicates the call setup is initiated by the originating gateway, but it fails because of an improper configuration on the terminating gateway.

Note VRC does not validate non-dial plan parameters such as codec or DTMF-relay between the call endpoints.

Verifying Call Paths

Use call path verification to trace the full route of a call from gateway to gateway.

Note You can verify a call path from the Baseline View or the Design View.

Note You must find the terminating gateways before you verify a call path.

Note If you trace a call path from a voice port or trunk group, select a voice port or trunk group that has a translation profile defined so that the translation rules can be applied to the called number. If there are no translation rules defined and you are using carrier-based routing, trace the call path from the trunk group.

To verify a call path:

Step 1 Expand the dial plan tree to view all components.

Step 2 Locate the gateway to trace a call path from. You can also trace a call path from a voice port or trunk group on a gateway.

Step 3 Right-click the gateway (voice port or trunk group) and choose Verify Call Path from the menu.

The Verify Call Path dialog box appears (Figure 5-29).

Figure 5-29 Verify Call Path Dialog Box

Step 4 Enter the incoming dialed string that you want to find the call path for. Use only digits in your dial string, leaving out dashes and dots. You can enter only a prefix for your string.

Step 5 If the CSR route type for the AD is set to carrier or trunk-label, select a target carrier. If you leave the target carrier field blank, the call path is verified regardless of the routing server's status.

Step 6 Click OK to display the call paths from the incoming dial string or Cancel.

OSP Server

The Open Settlements Protocol (OSP) enables the call-routing infrastructure to choose the best place to terminate a phone call. During the Discovery operation, VRC checks to see if a gateway is configured for OSP.

Important Notes about OSP

For managed zones, you can have one OSP server associated with a zone. This OSP server is the default for all gateways in the zone.
For gateways, you can have one OSP server associated with a gateway. This OSP server overrides the default OSP server in the zone.
For ingress routes with an ARA type of OSP Server, follow these rules:

If the route is assigned at the managed zone level, then use the OSP server associated with the zone.
If the route is assigned at the gateway, then use the OSP server associated with the zone.

Ingress routes can terminate at OSP servers if the OSP Enabled attribute is configured on the gateway.
OSP servers are not discovered by VRC.

Gateway Parameters

This section describes the parameters that can be configured for gateways in a VRC dial plan:

Assigning an Ethernet Port

When you execute the Discovery operation for a gateway, the Ethernet port associated with the IP address specified in the topology for a gateway is identified. The baseline dial plan shows this Ethernet port for each gateway.

Use the command line interface to add or delete an Ethernet port from the gateway.

View the Ethernet ports that are assigned to a gateway in the Design View or the Baseline View. Use this procedure to assign an Ethernet port on a gateway using the VRC client.

Note You must first create the Ethernet port using the command line interface (CLI).

To assign an Ethernet port on a gateway:

Step 1 From the Design View expand the dial plan tree to view all components.

Step 2 Locate the gateway to assign an Ethernet port to.

Step 3 Click the Ethernet tab.

Step 4 Right-click and choose Add from the menu. The Add Ethernet Port dialog box appears.

Step 5 Enter the name of the Ethernet port to assign to the gateway.

Step 6 Click Apply to add the Ethernet port to the gateway or Cancel.

Editing a Trunk Group

A trunk group is a logical grouping of multiple DS1 interfaces with the same signaling characteristics that you can provision as an outbound dial peer target. You can perform the following functions:

Configure multiple trunk groups per gateway.
Edit the attributes of a trunk group using the VRC client, but you must use the command line interface to add or delete the trunk group from the gateway.
View the trunk groups that are assigned to the gateway in the Design View or the Baseline View.

Note You can only use a VRC-discovered trunk group in your dial plan if the associated gateway has a VRC feature set of dp1.1 or later.

To edit the attributes for a trunk group on a gateway:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the gateway with the trunk group that you want to edit.

Step 3 Select the trunk group.

Step 4 Click the Edit Attributes button. The Edit Trunk Group dialog box appears.

Step 5 Enter the values that you want to change.

Table 7-22 describes the entry fields in the Edit Trunk Group dialog box.

Table 5-17 Trunk Group Attributes

General Attribute	Description
Name	The name of the trunk group. A read-only field.
Hunt Scheme	Specifies the way to select an interface from a trunk group for an outgoing call. Choose from least-idle, least-used, longest-idle, random, round-robin, sequential.
Hunt Order	Choose from both, even, or odd. Do not set this parameter if Hunt Scheme is set to random.
Hunt Direction	Choose from up or down. Set this parameter if Hunt Scheme is set to least-used, round-robin, or sequential.
Incoming Translation Profile	Associates a translation profile for the incoming side of the gateway. The VRC feature set of the translation profile must be dp1.1 or later.
Outgoing Translation Profile	Associates a translation profile for the outgoing side of the gateway. The feature set of the translation profile must be dp1.1 or later.
Description	The maximum value is 63 characters.
Carrier ID	The ID for the carrier that owns this trunk group. You can set this parameter only if the CSR route type is carrier.

Step 6 Click Apply to apply the values to the trunk group or Cancel.

Adding a Hunt Group

A hunt group is a series of dial peers, with the same destination pattern but different interfaces, organized to share the load. If the first interface is busy or unavailable, the next interface is "hunted" until an available interface is found, or the hunt process is stopped.

Note To use trunk groups in a hunt group, you must first create the trunk group using the CLI. (VRC creates hunt groups but cannot provision trunk groups.)

To add hunt groups to a gateway:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the gateway that you want to add a hunt group to.

Step 3 Click the Hunt Groups tab.

Step 4 Right-click and choose Add from the menu. The Add Hunt Group dialog box appears.

Step 5 Enter the values in the entry fields.

Name—The name for this hunt group. The maximum value is 64 characters.
Choose either Trunk Group or Voice Port.

A trunk group is a group of similar trunks (shared electronic characteristics) that go between the same two geographical points. A trunk group performs the same function as a single trunk, but carries multiple conversations. You can only choose trunk group if the Cisco VRC feature set for the gateway is dp1.1 or later.
A voice port is a single voice port on a gateway.

Description—Text description for this hunt group. The maximum value is 64 characters.

Step 6 Click Apply to add the hunt group or Cancel.

Adding a Voice Source Group

A voice source group allows you to assign a name to a set of source IP group characteristics. The terminating gateway uses these characteristics to identify and translate the incoming VoIP call.

Note You must set up a source group before you can add a voice source group. The voice source group receives parameter settings from the parent source group. You can only add a voice source group to a gateway if the VRC feature set of the gateway is dp1.1 or later.

To add a unique voice source group to a gateway:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the gateway to add a voice source group to.

Step 3 Click the Voice Source Group tab.

Step 4 Right-click and choose Add from the menu. The Add Voice Source Group dialog box appears.

Step 5 Enter attribute information.

Step 6 Table 7-23 describes the fields in the Add Voice Source Group dialog box.

Table 5-18 Voice Source Group Attributes

General Attributes	Description
Name	The name of the voice source group. The maximum value is 31 characters.
Source Group	The parent source group which contains the parameter settings to use for this voice source group.
Access List	The access list number for this voice source group to be used for call blocking. You must also set a disconnect cause for call blocking. This parameter allows the voice source group to block calls from the IP address specified in the access list.

Step 7 Click Apply to add the voice source group to the gateway or Cancel.

Editing a Voice Port

A voice port is an interface that connects the gateway to the PSTN network or the customer premise equipment (CPE). You can view the voice ports that are available on a gateway in the Design View or the Baseline View. You can edit voice port attributes using the VRC client; but you must first create the voice port using the command line interface (CLI).

To edit a voice port:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the gateway with the voice port that you want to edit.

Step 3 Select the voice port.

Step 4 Click the Edit Attributes button. The Attributes for Voice Port dialog box appears.

Step 5 Enter values that you want to change.

Name—Read only field.
Incoming Translation Profile—Associates a translation profile for the incoming side of gateway. You can only set this parameter if the gateway for this voice port has a VRC feature set of dp1.1 or later. The translation profile must already be defined and the feature set of the translation profile must also be dp1.1 or later.
Outgoing Translation Profile—Associates a translation profile for the outgoing side of the gateway. You can only set this parameter if the gateway for this voice port has a feature set of dp1.1 or later. The translation profile must already be defined and the feature set of the translation profile must also be dp1.1 or later.

Step 6 Click Apply to add the translation profiles or Cancel.

Adding an Access List

An access list is kept by routers to control access to or from the router for a number of services (for example, to prevent packets with a certain IP address from leaving a particular interface on the router).

When you perform the Discovery operation on a gateway, all IP Standard (1-99) access lists for a gateway become part of the dial plan. VRC only discovers and displays access lists for gateways. VRC does not provision gateways.

The baseline and design dial plan show all access lists associated with a gateway on the gateway's Access Lists tab. The Access Lists tab is highlighted only if VRC discovers access lists provisioned on a gateway.

Use the CLI to add or delete an access list for a gateway.

Note You must first create the access list using the command line interface (CLI) before you can manually assign it to the gateway.

To add a predefined access list to a gateway:

Step 1 From the Design View, expand the dial plan tree to view all components.

Step 2 Locate the gateway that you want to assign an access list to.

Step 3 Click the Access Lists tab.

Step 4 Right-click and choose Add from the menu.

Step 5 Enter the access list number and an optional description.

Step 6 Click Apply to add the access list or Cancel.

Table of Contents