Defining and Managing Dial Plan Components

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

---

You can view the general attributes of the AD in the:

• Design View—Double-click the AD and select the Attributes tab.
  
  
• Baseline View—Select the AD and the Attributes tab.
  
  

Note   You must be in the Design View to set the route type for the AD.

To set the route type for the AD, follow these steps:

Step 1   Locate the AD in the list of elements. The Attributes tab is forward.

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

Step 3   Set 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 click Cancel to cancel the procedure.

Note   You must be in the Design View to add a technology prefix.

To add a technology prefix to the AD, follow these steps:

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

Step 2   Click the Technology Prefixes tab. The technology prefixes table is displayed.

Step 3   Choose a technology prefix from the list and right-click on it.

Step 5   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 6   Click Apply to apply this prefix to the gateway or click Cancel to cancel the procedure.

Step 1   Choose either Open Design or New Design from the Design menu.

Step 2   Expand the AD to view all elements.

Step 3   Select the technology prefix you want to delete.

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

Step 5   Click OK to delete the technology prefix from the dial plan or click Cancel to cancel this procedure.

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

---

Note   You must be in the Design View to add a trunk or carrier ID to the AD.

---

To add a trunk or carrier ID to the AD, follow these steps:

Step 1   Expand the AD to view all elements.

Step 2   Click the Trunk/Carrier IDs tab.

Step 4   Enter your values in the Name and Description fields.

• 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 integer between 0 and 255.
  
  

Step 5   Click Apply to add the carrier or trunk ID to the AD or click Cancel to cancel this procedure.

Step 1   Right-click the AD.

Step 2   Choose Add and Route Server from the menu. The Add Route Server window appears.

Step 3   Enter the following 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 click Cancel to cancel the procedure.

This section contains the following topics about a region:

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.
  
  

The following VRC views allow you to view general attributes of selected regions:

• Select a region to display the Attributes tab.
  
  
• Expand the AD to view all regions.
  
  

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
  
  

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

Step 1   Choose Open Topology from the Topology menu. There are two tabs at the top of the Topology View pane: Regions tab and the Elements tab.

Step 2   Click the Regions tab. The regions that already exist in the dial plan are listed in the table (Figure 7-3).

Step 3   Right-click in the region window and choose Add from the menu. The Topology Add/Modify Region window appears.

Step 4   Enter the name of the managed region that you want to add.

Step 5   Click OK to add the new region name or click Cancel to cancel the procedure.

Note   The dial plan state of the region remains inactive until you commit the dial plan design that contains the region.

Step 1   Expand the AD to view all elements.

Step 2   Choose Add and then choose Managed Region from the menu. The Add Managed Region to Dial Plan window appears with a list of available regions.

Step 3   Select the region that you want to add to the dial plan.

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

Step 1   Expand the AD to view all elements.

Step 1   From the Topology menu, choose Open Topology and click the Regions tab.

Step 2   Select the region that you want to delete. Right-click the region and choose Delete from the menu.

The Topology Delete Region dialog box appears asking you to confirm the delete operation.

Step 3   Click OK to delete the region or click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

Step 2   Select the region that you want to delete.

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

A Confirm dialog box appears asking you to confirm the delete operation.

Step 4   Click Disable to delete the region, click Do Not Disable, or click to Cancel the procedure.

Step 1   Expand the AD to view all regions.

Step 2   Locate a region that you want to add an outgoing connection to.

Step 3   Click the Outgoing Connections tab. The right pane displays the regions and their associated outgoing connections.

Step 4   Right-click on that region and choose Add from the menu. The Add Connection dialog box appears.

Step 5   Select a 'connection to' region from the drop-down list.

---

Note   If your 'connection to region' is a foreign region, set the LRQ password, if it is known.

---

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

Deleting Outgoing Connections

Note   You must be in the Design View to delete outgoing connections for a region.

To delete an outgoing connection from a managed region, follow these steps:

Step 1   Expand the AD to view all regions.

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

Step 3   Click the Outgoing Connections tab. The window displays the regions and their associated outgoing connections.

Step 4   Select a 'connection to' region.

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

Step 6   Click OK to confirm the delete or click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

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

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

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

Enter the voice class codec attribute values in the following fields:

• 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 click Cancel to cancel the procedure.

Deleting Voice Class Codecs

Note   You must be in the Design View to add a voice class codec.

Step 1   Expand the AD to view all elements.

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

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

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

Step 1   Expand the AD to view all elements.

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.

Enter the attribute information in the following fields:

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

Step 7   Click Apply to add the codec or click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

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

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

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 click Cancel to cancel the procedure.

Deleting LRQ Passwords

Prerequisite

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

Note   You must be in the Design View to delete an LRQ password.

Step 1   Expand the AD to view all regions.

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

Step 3   Click the LRQ Passwords tab. The window displays the regions and their associated LRQ passwords.

Step 4   Select the LRQ password that you want to delete from this region.

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 click Cancel to cancel the procedure.

Step 1   Expand the AD to view all regions.

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

Step 3   Click the Incoming Connections tab. The window displays the outgoing connections associated with this region.

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

Step 5   Select a 'Connection To' region from the drop-down list.

Step 6   Select the LRQ Password. This is the password used to validate any LRQs received from the specified remote zone.

---

Note   For inter-region communication, the LRQ password must be associated with an incoming region connection. If it is not set, the default regional password is used.

---

Step 7   Click Apply to add the incoming region connection to the owner region or click Cancel to cancel the procedure.

Deleting Incoming Connections

Note   You must be in the Design View to delete an incoming region connection.

Step 1   Expand the AD to view all regions.

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

Step 3   Click the Outgoing Connections tab. The window displays the regions and their associated outgoing connections.

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

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 click Cancel to cancel the procedure.

This section contains the following topics about elements:

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

You must have valid user permissions and you must be in the Topology View to add an element to the network topology.

Note   You must open a design session to add elements to a dial plan.

To add an element to the network topology, follow these steps:

Step 1   Access the Topology View. There are two tabs at the top of the Topology View pane: Regions and Elements.

Step 2   Click the Elements tab.

Step 3   Select a region from the drop-down menu. The elements that already exist in that region are listed in the table.

Step 6   When you are finished entering information, click OK to add the new element to the region or click Cancel to cancel the procedure.

Note   You cannot view element passwords from this window. You must have user permissions to modify element information.

Step 5   Click Close to close the window when you are finished viewing the element information.

Note   You must be in the Topology View to modify an element.

To modify an element, follow these steps:

Step 1   Click the Elements tab.

Step 2   Select a region from the drop-down menu. The elements that already exist in that region are listed in the table.

Step 1   Click the Elements tab.

Step 2   Select a region from the drop-down menu. The elements that already exist in that region are listed in the table.

Step 4   Select a new region from the drop-down list to move the element to.

Step 5   Click OK to move element to the new region or click Cancel to cancel the procedure.

Step 1   Click the Elements tab.

Step 2   Select a region from the drop-down menu. The elements that already exist in that region are listed in the table.

Step 3   Right-click the selected element and choose Delete from the menu. The Topology—Delete Element confirmation dialog box appears.

Step 4   Click OK to delete the element or click Cancel to cancel the procedure.

Step 1   Expand the AD to show all elements.

Step 2   Right-click the element that you want to remove and choose the Remove from Dial plan option. A confirmation dialog box appears.

Step 3   Choose either Disable or Do not Disable. If you choose:

• Disable—VRC clears the dial plan configuration on the element and removes the element from the dial plan database during the next commit process.
  
  
• Do not Disable—VRC leaves the current configuration on the element and removes the element from the dial plan database during the next commit process.
  
  

Step 4   Click OK to remove the element or click Cancel to cancel the procedure.

You can persist the configuration of a single element or all elements in a region.

If you persist:

• A single element, the running configuration is written to the startup configuration, regardless of the current state of the element.
  
  
• Elements from the region level, only elements in the volatile configuration state write the running configuration to the startup configuration.
  
  

---

Note   You must be in the Topology View to persist the configuration of an element.

---

To use the persist operation for a single element, follow these steps:

Step 1   From the Topology View, click the Elements tab.

Step 2   Select a region from the drop-down list. The elements in that region are listed in the table.

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

Step 4   Click OK to display the new configuration state in the Topology View. VRC writes the running configuration of the element to the startup configuration.

To use the persist operation for all elements in a region, follow these steps:

Step 1   Click the Regions tab.

Step 2   Right-click in the region window and choose Persist All from the menu.

VRC writes the running configuration to the startup configuration for all elements in that region.

An information dialog box appears informing you that the operation is successful.

Step 3   Click OK to confirm the persist operation or click Cancel to cancel the operation.

Step 1   Expand the AD to view 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.

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.

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

Note   You must be in the Design View to reactivate an element.

Step 1   Expand the AD to view 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.

VRC supports the use of Cisco IE2100 and the Cisco Network Security (CNS) configuration server to deliver configurations to network devices.

To use a Cisco IE2100 to access elements in your network, you must configure the device outside of VRC. A large network might have multiple Cisco IE2100 devices.

• When you are using VRC as a standalone application, VRC communicates with network elements using the Cisco IE2100 by adding its IP address as an element attribute in the VRC Topology View.
  
  
• When you are using VRC integrated with PTC, both VRC and PTC use a Cisco IE2100 to communicate with network elements.
  
  

---

Note   You must have the CNS Event Bus installed and running to use a Cisco IE2100 device in your network.

---

Step 1   Expand the AD to view all elements.

Step 2   Select and right-click the managed region that you want to add a directory gatekeeper group to.

Step 3   Choose the Add and Directory Gatekeeper Group options from the menus. The Add Directory Gatekeeper Group window appears.

Note   See Figure 7-10 for General Attributes and Figure 7-11 for Enhanced Functionality and LRQ/ARQ Handling.

Step 1   Expand the AD to view all elements.

Step 2   Locate the directory gatekeeper group that you want to delete.

Step 3   Right-click the directory gatekeeper group and choose the Delete option from the menu.

Step 4   You are asked to determine the status of the dial plan configuration:

• If you choose Disable, then VRC clears the dial plan configuration and removes the directory gatekeeper group from the dial plan database during the next commit process.
  
  
• If you choose Do not Disable, then 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.
  
  

Step 5   Click OK to remove the directory gatekeeper group and child elements from the dial plan or click Cancel to cancel the procedure.

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.

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
  
  

• Expand the Administrative Domain (AD) to view all elements.
  
  
• Locate the directory gatekeeper and select it to display the Attributes tab.
  
  

Step 1   Expand the AD to view all elements.

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

Step 3   Right-click the selected directory gatekeeper group.

Step 4   Choose the Add option and Directory Gatekeeper from the menu. The Add New Directory Gatekeeper to Dial plan dialog box appears. This dialog box lists the IP addresses of available directory gatekeepers.

Step 5   Select a directory gatekeeper and click the Add button. The directory gatekeeper is added to the dial plan. A confirmation dialog box appears. You are prompted when the operation is successful.

Step 6   Click OK to add a directory gatekeeper to the dial plan or click Cancel to cancel the procedure.

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
  
  

---

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

---

• Expand the AD to view all elements.
  
  
• Locate the gatekeeper group and select the gatekeeper group to display the Attributes tab.
  
  

---

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

---

---

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.

---

Step 1   Expand the AD to view all elements.

Step 2   Right-click the region that you want to add a gatekeeper group to.

Step 3   Choose the Add and Gatekeeper Group options from the menu. The Add Gatekeeper Group window appears.

Note   See Figure 7-12 for General Attributes, Figure 7-13 for Enhanced Functionality and LRQ/ARQ Handling, and Figure 7-14 for Security, Resource Management, and Bandwidth Allocation.

Step 4   Enter the gatekeeper group values in the fields.

Step 5   Click Apply to add a new gatekeeper group or click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

Step 2   Right-click the gatekeeper group that you want to delete.

Step 3   Choose the Delete option from the menu. A confirmation dialog box appears.

Step 4   Click Disable, Do Not Disable, or Cancel.

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.

To add a zone circuit, follow these steps:

Step 1   Expand the AD to view all elements.

Step 2   Click the gatekeeper group or directory gatekeeper group that you want to add a zone to. The Gatekeeper Group window appears.

Step 3   Right-click and select Add from the menu.

Step 5   Enter the values in the entry fields.

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

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

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
  
  

• Expand the Administrative Domain (AD) to view all elements.
  
  
• Locate the gatekeeper and select it to display the Attributes tab.
  
  

---

Note   Only the gatekeeper type can be modified.

---

Step 1   Expand the AD to show all elements.

Step 2   Right-click the gatekeeper that you want to remove.

Step 3   Choose Delete from the menu. A confirmation dialog box appears asking you to confirm.

Step 4   Click Disable, Do Not Disable, or Cancel.

Note   You can only delete an element from the topology if the element is not part of the current baseline or is not being used in a design session. The dial plan state must be Inactive before you can delete it from the topology.

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
  
  

• 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
  
  

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.

• Expand the AD to view all elements.
  
  
• Locate the zone and select it to display the Attributes tab.
  
  

Step 1   Expand the AD to view all elements.

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

Step 3   Right-click the selected region.

Step 1   Expand the AD to view all elements.

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

Step 3   Right-click the foreign region.

Step 4   Choose Add and Unmanaged Zone from the menus. The Add Unmanaged Zone window appears.

Step 1   Expand the AD to show all elements.

Step 2   Right-click the zone that you want to remove.

Step 3   Choose the Delete option. A confirmation dialog box appears asking you to confirm.

---

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 click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

Step 2   Locate the managed zone associated with a gatekeeper that contains the local zone name that you must change.

Step 3   Create a zone alias for the managed zone. The new local zone name (or zone alias) is applied to the gatekeepers.

---

Note   During the Distribution and Commit operations, VRC configures associated gateways to use the zone alias.

---

Note   The local zone name is an attribute for a directory gatekeeper.

Step 1   Open a design session.

Step 2   Expand the AD to view all elements.

Step 3   Locate and select the directory gatekeeper that you want to modify the local zone name for.

Step 4   Click the Attributes tab.

Step 5   Click Edit Attributes.

Step 6   Modify the Local Zone Name field.

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

Step 1   Expand the AD to view all elements.

Step 2   Locate 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 selected zone prefix.

Step 5   Click the Gateway Priorities tab.

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

Step 7   Enter the priority value. The range is 1 to 10. The default is 5.

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

Zone prefixes are set up for a:

• Local zone in a managed zone
  
  
• Remote zone in an unmanaged zone
  
  

Step 1   Expand the AD to view all elements.

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

Step 3   Click the Zone Prefixes tab.

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

Step 6   Enter the prefix value. This value is 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 (.).

Step 7   Enter the default gateway priority. This value is the priority for this prefix in the managed zone. The range is 1 to 10. This cannot be set for an unmanaged zone.

---

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.

---

Step 8   Click Apply to add a zone prefix or click Cancel to cancel the procedure.

Note   You must be in the Design View to delete a zone prefix.

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

To delete a zone prefix, follow these steps:

Step 1   Expand the AD to view all elements.

Step 2   Select a zone.

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 click Cancel to cancel the procedure.

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

Step 1   Expand the AD to view all elements.

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

Step 3   Click the Server Triggers tab.

Step 4   Click Add Server Trigger. The Add Server Trigger window appears.

Step 5   Enter your values.

Step 6   Click Apply to add a new server trigger or click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

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

Step 3   Click the Server Triggers tab.

Step 4   Select the server trigger that you want to delete.

Step 5   Click Delete Server Trigger.

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

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 (like an ingress route).
  
  

---

Note   When an egress route is configured on Cisco gateways, it is translated into VoIP dial-peers and outbound POTS dial-peers.

---

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.
  
  

---

Note   When VRC configures an ingress route on Cisco gateways, the route is translated into outbound POTS dial-peers and VoIP dial-peers.

---

---

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

---

Step 1   Expand the AD to view all elements.

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

Step 4   Enter values in each field.

Step 5   Click Apply to add a new egress route or click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

Step 2   Select a zone that you want to remove the egress route from.

Step 3   Click the Egress Routes tab.

Step 4   Select the egress route that you want to delete.

Step 5   Click Delete Egress Route.

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

Step 1   Expand the AD to view all elements.

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

Step 4   Enter values in the entry fields.

Step 5   Click Apply to a add a new ingress route or click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

Step 2   Select a zone.

Step 3   Click the Ingress Routes tab.

Step 4   Select the ingress route that you want to delete.

Step 5   Click Delete Ingress Route. A confirm dialog box appears.

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

For example, if a route scope of a gateway is assigned to an ingress route, all voice ports on the gateway will be 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 will be configured to terminate the route.

Step 1   Expand the AD to view all elements.

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

Step 3   Click the Route Scope tab.

Step 5   Enter values in the entry fields.

---

Note   A trunk is a logical grouping of POTS interfaces of similar signaling type. This is useful for associating common attributes such as rule descriptions, carrier-id, and so on.

---

---

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.

---

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

Step 1   Expand the AD to view all elements.

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 that you want to delete.

Step 5   Right-click and select Delete from the menu. The Confirm dialog box appears.

Step 6   Click OK to confirm the delete or click Cancel to cancel this procedure.

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

Step 1   Expand the AD to view all elements.

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   Right-click and choose Add from the menu.

Step 6   Enter the rule description attribute values in the entry fields.

Step 7   Click Apply to add this translation rule to the rule description or click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

Step 2   Select a zone that you want to add a translation profile to.

Step 3   Click the Translation Profiles tab.

Step 5   Enter the values in the entry fields.

Step 6   Click Apply to add a new translation profile or click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

Step 2   Locate the zone that you want to remove the translation profile from.

Step 3   Click the Translation Profiles tab.

Step 4   Select the translation profile that you want to delete.

Step 5   Click the Delete Translation Profile button.

Step 6   Click OK to remove the translation profile or click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

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

Step 3   Click the Number Expansion Sets tab.

Step 4   Click the Add Number Expansion Set button. The Add Number Expansion Set dialog box appears.

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

---

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

---

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

Step 1   Expand the AD to view all elements.

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

Step 3   Click the Number Expansion Sets tab.

Step 4   Click Delete Number Expansion Set to delete the number expansion set from the dial plan or click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

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 click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

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

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 which contains the number expansion rule you want to delete.

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

Step 6   Click Delete Rule to remove the number expansion rule from the dial plan or click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

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

Step 3   Click the Zone Aliases tab.

Step 5   Enter the following values in the entry fields:

• 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 click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

Step 2   Locate the zone that you want to add a source group to.

Step 3   Click the Source Group tab.

Step 5   Enter the values in the entry fields.

Step 6   Click Apply to add a source group or click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

Step 2   Locate the zone that you want to delete the source group from.

Step 3   Click the Source Group tab.

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

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

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

Step 1   Expand the AD to view all elements.

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

Step 3   Click the Hopoff Tech Prefixes tab.

Step 5   Enter the following values:

• 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 click Cancel to cancel the procedure.

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
  
  

You can view the general attributes of a selected gateway in the following views:

• Design View allows you to:
  
  
• Double-click the gateway to view the attributes.
  
  
• Expand the Administrative Domain (AD) to view all elements.
  
  
• Baseline View allows you to select a gateway to display the Attributes tab.
  
  

Step 1   Expand the AD to view all elements.

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

Step 3   Right-click the selected zone and choose Add to Dial Plan and Gateway from the menu. The Add Gateway to Dial Plan window appears. This window lists the IP addresses of available gateways.

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

Step 5   If you choose OK, the gateway is added to the dial plan.

Step 6   If you choose Cancel, the gateway is not added and you are returned to the Add Gateway to Dial plan window.

Step 7   To edit the attributes of the new gateway, select the new gateway and then click the Edit Attributes button.

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

---

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 click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

Step 2   Locate the gateway that you want 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 window appears.

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

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

To edit the attributes for a trunk group on a gateway, follow these steps:

Step 1   Expand the AD to view all elements.

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 window appears.

Step 5   Enter the values that you want to change.

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

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

Note   In order 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, follow these steps:

Step 1   Expand the AD to view all elements.

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 window 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.
  
  
• 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 click Cancel to cancel the procedure.

Step 1   Expand the AD to view all elements.

Step 2   Locate the gateway that you want 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 window appears.

Step 5   Enter values in the entry fields.

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

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

Step 1   Expand the AD to view all elements.

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 window 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. The translation profile must already be defined and the feature set of the translation profile must also be dp1.1.
  
  
• 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. The translation profile must already be defined and the feature set of the translation profile must also be dp1.1.
  
  

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

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.

Step 1   Expand the AD to view all elements.

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 click Cancel to cancel the procedure.