|
This chapter describes the Design View in the Cisco Voice Routing Center (VRC) application.
The Design View is where you make administrative changes to a baseline dial plan or element list or create a new dial plan and apply those changes to the elements.
The design view reflects the active design session, whether it is a new dial plan design or a previously saved design. Use this view to introduce network elements with no previous dial plan configuration into a dial plan and modify the existing dial plan configuration in the network elements.
Use the following guidelines when manipulating a dial plan in the Design View:
From the Design View right-click menu you can:
Use the Design View to open a new design or make changes to an existing design. When you open:
This section describes how to open a previously saved dial plan design. The list of previously saved design files can be any of the following file types:
To open an existing dial plan design:
Step 2 Select a saved dial plan to open and click Open Design File. A design session opens and the saved dial plan is displayed.
Step 3 Expand the dial plan tree to view the regions and elements within.
Step 4 Modify the dial plan design.
Step 5 You can close and save the design session again complete the dial plan later.
A new dial plan design allows you to add elements, make administrative changes to a new dial plan, and apply those changes to the elements.
Before you begin, verify that all managed regions and elements affected by your new design are identified in the topology.
Note If an element is not identified in the topology, it cannot be added to a dial plan design. |
To configure a new dial plan design:
Step 2 Select a Design Scope. Choose the AD or a select a region from the list of regions in the topology.
Step 3 Click Open. A Design View session opens.
You can use the copy and paste command to add certain entities to the dial plan. For example, if you have one gatekeeper group in a region and want to add another gatekeeper group with the same attributes, use copy and paste.
The copy command creates a gatekeeper group with the same attribute information. The paste command adds this new gatekeeper group to the dial plan. After you paste the gatekeeper group, you must change the Name entry field. You cannot have two entities with the same name.
You can only use copy and paste to add like entities to the appropriate parent in the dial plan. For example, you cannot copy a server trigger and paste it into a region, you cannot copy a gatekeeper group and paste it into the AD, or you cannot copy a gatekeeper group and paste it in a region as a directory gatekeeper group.
The following dial plan entities can only be added by using the right-click menu:
To copy and paste dial plan entities:
Step 2 Select the dial plan entity that you want to duplicate.
Step 3 Right-click and choose Copy from the menu.
Step 4 Select the appropriate parent in the dial plan you want to add this duplicated entity to.
Step 5 Right-click and choose Paste from the menu.
Step 6 Click the Attributes tab.
Step 7 Right-click and choose Edit from the menu.
Step 8 Edit the attribute information. You must edit the Name attribute. You cannot have two dial plan entities with the same attribute information.
Step 9 Choose Refresh Display from the Window menu to update the design session display. The duplicated entity is added to the dial plan.
This section describes how to delete a dial plan design from the server storage.
Note You can delete a design file in any view. |
Step 2 Click the desired dial plan from the list that you want to delete.
Step 3 Click the Delete Saved Design File button. You are asked to confirm the delete. Click OK.
You can export a dial plan for the entire AD or for a region.
Note You must be in the Design View to export a design and the design must be open. |
To export a dial plan design for an AD:
Step 2 Right-click the AD and choose Export. Alternately, you can choose Export This Design from the Design menu.
The dial plan is exported to a browser window to view and save.
To export a dial plan design for a region:
Step 2 Select a region to export the dial plan from.
Step 3 Right-click the region and choose Export. A browser window opens showing the dial plan in a text format.
This section describes how to commit a dial plan design to your network and establish a baseline dial plan. We recommend that you preview the design before you commit it to the network elements. See Previewing a Dial Plan Design for more information
Note When you commit a design, VRC replaces the existing dial plan configuration for all elements in the design whose dial plan configuration has changed and updates the baseline dial plan. For example, changing a dial plan in one region might affect elements in other regions. |
Note The dial plan design that you want to validate must be open. |
To commit your dial plan to the network:
Step 2 A Confirm dialog box appears. Click OK to confirm your commit or click Cancel to return to the Design View window.
During the dial plan commit process, the VRC validates the elements and then generates a baseline dial plan for the affected elements.
During the dial plan generation process, VRC:
Note If you have one or more gateways with the Reactivate field set to Yes, you cannot commit a design. To reactivate a gateway, right-click the selected gateway and choose Reactivate from the menu. |
An information message indicates that the operation has successfully completed.
Step 3 Click OK. The Design View window closes.
Use this option to find terminating gateways, for a given dial string. You can find terminating gateways for the baseline dial plan or for the dial plan in your active design session.
A dialog box appears (Figure 5-3).
Step 2 Enter the incoming dialed string that you want to find the terminating gateway for. Use only digits in your dial string, leaving out dashes and dots. You can enter only a prefix for your string.
Step 3 If the CSR route type for the AD is set to carrier or trunk-label, select a target carrier. Choose a target carrier from the drop-down menu.
Step 4 Click OK. VRC displays the gateways used to terminate routed calls for this dial string.
Step 5 Click Cancel to return to the VRC window.
This section describes how to preview a new dial plan design before you commit the design to the elements.
Note You must be in the Design View to preview a design and the design must be open. |
To preview a new dial plan design:
Step 2 The Creating design preview window appears. Wait until the system is finished loading the design. VRC creates a design preview. The location of the preview files on the VRC server is displayed.
Validation is the mechanism by which VRC detects and prevents illegal or inconsistent data from being written to the dial plan or sent to the network elements. This action validates the entire design scope. VRC also validates the dial plan design during the Discovery and Commit operations.
Note The dial plan design that you want to validate must be open. |
To validate a dial plan design:
You are returned to the Design View to make any necessary changes.
Validation is the mechanism by which VRC detects and prevents illegal or inconsistent data from being written to the dial plan or sent to the network elements. When errors are detected by validation, messages are produced and presented to the user through the client and through the server logs (system, audit, and internal).
Validation is executed implicitly as part of some design operations and explicitly when Validate is chosen from the Design menu. The appropriate recourse for troubleshooting validation errors and warnings depends on the type of operation being performed.
To correct validation errors produced by design modifications, retry the modification in a way that addresses the conditions described in the error message.
Certain elements (gateways, gatekeepers, directory gatekeepers, managed regions, foreign regions, managed zones, ingress routes, and egress routes) have "status" attributes which indicate the severity (Fatal, Warning, Ok) of the most significant validation message produced for those components. Those in a "Fatal" or "Warning" state are flagged in the GUI dial plan tree as either red or yellow, respectively.
For network elements, you might only be able to correct certain errors by reactivating the element. For example, if a gateway has the "reactivate" attribute set as "yes", or an element has a required read-only field such as "h323id" not set at all, then an error is produced during validation. In these examples, the failed element must be explicitly reactivated by the user to set these attributes to a state in which they can be committed.
When you encounter validation error messages, use the console to set the debug of the Validation subsystem to On.
After a design validation, VRC uses color coded indicators to inform you that there is an error in the dial plan design. These indicators appear in the dial plan tree and on the tabs in the user interface.
VRC validation indicators are displayed:
Table 4-1 Validation Indicator Colors
Before Cisco VRC can send a dial plan configuration to an element, the software must convert the dial plan model to a format that an element can understand, the command line interface (CLI).
During CLI generation of an element, VRC extracts all dial plan information that is relevant to that element and dynamically creates an XML file for that element. For example, during CLI generation for a particular gateway, VRC must extract all dial plan information that directly affects the configuration of that gateway. This information can include voice class codecs assigned to the region where the gateway resides, translation rules or profiles assigned to the managed zone in which the gateway resides, and voice ports on that gateway.
A static configuration file for each element type, which is located on the VRC server, defines how the information in the XML file is translated to CLI. VRC uses this static configuration file and the information in the XML file to generate the CLI configuration. The generated CLI configuration is used to distribute the dial plan to the running configuration for that element.
VRC distributes the configuration to the network elements in the following order:
Each time you make a change to your dial plan, the CLI-generated configuration for the elements affected by the dial plan changes. To see how changes in your dial plan have affected the CLI-generated configuration, you must generate a new CLI to view.
This section describes how to view a generated CLI of an element. The generated file is displayed in text format. You can view a generated CLI for an element in the Baseline View or the Design View.
To view the VRC-generated CLI:
Step 2 Locate the element that you want to view a CLI configuration for.
Step 3 Right-click the selected element.
Step 4 Choose View Generated CLI. A generated CLI for the selected element is displayed in a separate browser window.
This section describes how to open a Telnet session to execute CLI with a specific element.
Note You must be in the Design View to open a Telnet session or CLI console for an element. |
Step 2 Locate the element that you want to open a CLI session for.
Step 3 Right-click the selected element.
Step 4 Choose Open CLI Console from the menu. A CLI console window opens and you are prompted for the password.
The Telnet application registered with your browser presents a standard Telnet session interface to allow you to perform direct administration on the selected network element.
The CLI console window closes.
When you finish working on a dial plan design, you can either store the design or discard the design.
Note You must be in the Design View and have a design open to perform this procedure. |
The Closing Design dialog box appears.
Step 2 Choose one of the following closing methods:
A message appears to indicate that the operation was successful.
Step 3 Click OK to close the Design View window.
Posted: Fri May 9 17:20:54 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.