Table of Contents

Release Notes for the Cisco Voice Routing Center, Software Version 1.1

Release Notes for the Cisco Voice Routing Center, Software Version 1.1

September 30, 2002

These release notes provide information about the Cisco Voice Routing Center (VRC), software Version 1.1. These release notes are updated as needed to describe new and changed information, caveats, and documentation updates.


This document contains the following sections:


The Cisco Voice Routing Center is a network management tool for dial plans in a Voice-over-IP (VoIP) network (for example, an H.323-based network). VRC can be used as a standalone application that provides basic provisioning of dial plans and configuration of the elements in a network, or integrated with the Cisco Packet Telephony Center (PTC) Solution.

With VRC, you can archive and restore dial plans and validate a configuration before you download it to the network elements. You can deploy VRC in a network with an existing dial plan or use it to create new dial plans.

Supported Hardware

The Cisco VRC is based on a server and client architecture and supports the platforms listed in Table 1.

Table 1: Supported Hardware Platforms
Component Server Client


  • Sun UltraSPARC 10 or 60

  • Sun Blade 150 or 2000

Intel Pentium III, or later

Operating System

Sun Solaris 2.7 or 2.8

Microsoft Windows NT4 or 2000

Web Browser

Microsoft IE Version 5.0 or 5.5

Table 2 lists the Cisco products that VRC supports as gateways and gatekeepers.

Table 2: Supported Cisco Gateways and Gatekeepers
Cisco Gateways Cisco Gatekeepers

1750 Access Router

3640 Multiservice Platform

Catalyst 2600 Series Switches

3660 Multiservice Platform

3600 Series Routers

7200 Series Routers

AS5300 Series Universal Access Server

AS5350 Universal Gateway

AS5400 Series Universal Gateways

AS5800 Series Universal Access Servers

AS5850 Universal Gateway

7200 Series Routers

Note   The Cisco VRC does not manage third-party gatekeepers, but it does co-exist with them.

Software Compatibility

Table 3 lists the Cisco IOS software releases supported by Cisco VRC Version 1.1

Table 3: Cisco Platform and Software Specifications
Cisco Platforms Cisco IOS Releases

Cisco IOS Gatekeeper Release—Cisco 3640, 3660, and 7200 platforms

12.2(2)XA, 12.2(2)T, 12.2(11)T,

12.2(2)XU (Cisco 3660 and 7200 only)

Cisco IOS Gateway Release—Cisco 1750 and 2600 platforms


Cisco IOS Gateway Release—Cisco 3640, 3660, and 7200 platforms

12.2.7, 12.2(2)XA, 12.2(11)T

Cisco IOS Gateway Release—Cisco 5300, 5350, 5400, 5800, and 5850 platforms

12.2.7 (no 5350 or 5850), 12.2(2)XB, 12.2(11)T

12.2(2)XU (no 5800)

Important Notes

This section describes important notes about VRC software, Version 1.1.

Feature Notes

This section describes general notes about VRC features.


The following sections list limitations for VRC software, Version 1.1.

Preconfiguration Limitations

VRC software Version 1.1 does not configure:

The following management functions are not supported by VRC software, Version 1.1:

Client/Server Limitations

Network Configuration Limitations

Ordering and Naming Limitations

The following information is not preserved during the discovery process:

Zone Management Limitations

Open Caveats

A read-only user is not prohibited from redistributing a baseline dial plan to the network.

Workaround: To maintain network security, do not configure users with read-only privileges.

If you change the description of a trunk group on a gateway, this does not set the impacted gateway flag and the change is not reflected in the new CLI that VRC generates for the gateway.

Workaround 1: Make a description change to a trunk group at the same time as another gateway parameter change so that VRC recognizes that new CLI should be sent to the gateway.

Workaround 2: Execute an element distribution to the affected gateway from the baseline dial plan. Note that this method causes VRC to shut down the gateway.

The VRC install script does not check for user permission when searching for the Perl program defined by the $PERL_EXE_PATH.

Workaround: If your system restricts the use of Perl, run the install script as a user with the privilege to execute Perl.

When you configure an answer address (ANI parameter) for an egress route, and the ANI does not begin with a number, the gateway rejects the ANI parameter when VRC distributes the configuration. During the next discovery, the trunk group label source is lost because the ANI parameter is missing from the gateway. Subsequent discoveries might also cause changes in other routes because the VRC-generated CLI does not contain the trunk group label source.

Workaround: The ANI parameter for an egress route must begin with a number to be recognized by a Cisco IOS device.

VRC cannot discover a zone circuit if the remote zone is named "remote".

Workaround: When you add a zone circuit to a gatekeeper group or a directory gatekeeper group, assign the remote zone a name other than "remote".

During the Distribution operation, you might receive an error message, which states that CLI cannot be generated for an element, even though the element passed the VRC Validation process. Under this condition, VRC might create illegal database entries which cause the Distribution process to fail because one or more elements have invalid dial plan information.


If VRC discovers that a call enters and exits the same gateway, it tries to create a hairpin ingress route. This occurs because the VRC logic assumes that outbound POTS calls have a voice port defined, but this might not be true in all cases.

Workaround: From the discovery design session, delete the route scopes with the description of Hairpin Destination, delete route scope entries with the resource ID of N/A, and delete the associated ingress routes with the ARA type of hairpin.

VRC does not generate the correct CLI for a zone prefix that has the Default Gateway Priority parameter defined.

Workaround: Use the command line interface to specify a gw-priority of 0 for each gateway in the zone that should not route the call.

VRC does not create an ingress route for a POTS dial peer that has an application (such as prepaid) defined. This occurs because the application processes two-stage dialing and VRC might not create the matching VOIP dial peer for the outbound leg of the call.

Workaround: After the initial discovery, open a VRC design session to manually create the ingress route and add the inbound application parameter to the route. This creates the POTS-VOIP combination for the route and maintains the application parameter for any subsequent discovery.

The VRC server does not stop when you issue the vnm --kill script. This occurs when you are using VRC integrated with PTC, and the DemoSysAdmin1 user password is changed.

Workaround: Do not change the DemoSysAdmin1 user password. If it changes, you must stop the server by issuing the following command:

    vnm --kill --grace/force -u <username> -p <password>
VRC does not discover HSRP configurations for gatekeepers and directory gatekeeper, but it does support them. VRC relies on PTC to configure gatekeeper and directory gatekeeper pairs for HSRP. If you change the role of the gatekeepers (primary or backup) using VRC, and that role is different from the PTC-configured gatekeeper role, you are not notified of the discrepancy.

Workaround: Manually verify that the gatekeeper and directory gatekeeper roles are correctly assigned in VRC and in PTC.

The VRC discovery operation fails and you receive the message "Error:210 - Error - Error executing the SQL." This occurs because VRC cannot read the Cisco IOS version, which is used to populate the feature set field in the MySQL database. This type of error also causes a forced discovery to stop.

Workaround: If you cannot correct the element connectivity problem, remove it from the topology.

VRC Discovery does not retain the port attribute for matching inbound dial peers. This occurs because VRC splits the bidirectional dial peers into unidirectional dial peers which provides for matching inbound dial peers only at the gateway level.

Workaround 1: Identify another characteristic to use for matching inbound dial-peers. For example, use the answer-address on the calling number or destination pattern on the called number.

Workaround 2: Reconfigure the network so that calls are accepted at the gateway level instead of the port level.

VRC allows you to define and configure trunk groups for gateways running Cisco IOS versions prior to Release 12.2(11)T. However, VRC only supports trunk groups for gateways running Cisco IOS Release 12.2(11)T and later.

Workaround: To manage trunk groups with VRC 1.1, upgrade the Cisco IOS version on the gateways to Release 12.2(11)T.

When you delete an object from the user interface and a reference to this object still exists in the dial plan, the user interface displays 'object deleted' in the value field for that reference. This causes a 'bogus reference' error during Validation.

Workaround: When you delete an object from the user interface, you must change the value field from object deleted to a blank value for any references to that object.

If you execute the Discovery operation on a directory gatekeeper hierarchical network, while a directory gatekeeper is in the shutdown mode, the Discovery process might stop and you receive the following error message:

    Reason 807 - Error - Failed to parse running-config for the element. Element Name = w.x.y.z is not active.
where w.x.y.z is the IP address of a directory gatekeeper.

Workaround: Execute a Forced Discovery, manually add the directory gatekeeper that was in shutdown mode to the dial plan, and commit the design.

The Discovery operation populates LRQ passwords for incoming connections even if the region is not configured for security. This occurs if a connecting region is configured for security.

Workaround: After the Discovery process has completed, remove the LRQ password and the Incoming connection for the region that does not have security configured.

After a VRC distribution, you receive the following message from a gateway "Can not set abatement value greater than onset." This message also appears in the user log. This occurs because the High Resource Threshold value has been set lower than the Low Resource Threshold on the VRC user interface.

Workaround: Make sure that the High Resource Threshold value on the gateway is greater than or equal to the Low Resource Threshold value, and perform another distribution.

During the discovery of a network configured for gatekeeper or directory gatekeeper redundancy, you receive error messages for the gatekeepers, directory gatekeepers, or the associated GK and DGK groups. This might occur because a gatekeeper is directly referencing the zone of another gatekeeper in a hierarchical region, rather than referencing the directory gatekeeper.

Workaround: From a VRC design session, set the appropriate redundancy type (None, HSRP, Overlap, Both, Cluster) for the directory gatekeeper group or gatekeeper group, and run the validation process to determine if the problem is corrected.

Related Documentation

This section lists documentation related to the Cisco Voice Routing Center.

Other VRC documentation:

Documentation for Cisco Packet Telephony Center (PTC):

Obtaining Documentation

These sections explain how to obtain documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at this URL:

Translated documentation is available at this URL:

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Ordering Documentation

You can order Cisco documentation in these ways:

Documentation Feedback

You can submit comments electronically on In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.

You can e-mail your comments to

You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. registered users have complete access to the technical support resources on the Cisco TAC Web Site. is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world. is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:

If you want to obtain customized information and service, you can self-register on To access, go to this URL:

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Cisco TAC inquiries are categorized according to the urgency of the issue:

The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:

If you are a registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:

If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.

Copyright ©2002, Cisco Systems, Inc.
All rights reserved.

Posted: Fri Oct 4 08:14:00 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.