|
|
This chapter describes how to start, use, and stop the Dial Plan Provisioning (DPP) application and generate the output files required by the telephony controller application.
This procedure assumes you have correctly installed the DPP application in the directory C:\Lightspeed\TransPathCM\DialPlan. For more information about installing this tool, see "Installation."
The dial plan process contains the following steps:
Step 1 Create the text file in any text editor. (See "Dial Plan Provisioning Tool.")
Step 2 Use the DPP software to import and generate the dial plan.
Step 3 Use config-lib on the telephony controller to deploy the routing tables for processing.
 | Caution The dial plan text file must be on the Windows NT server, and the import process must be initiated on the Windows NT server. |
You can use the graphical user interface (GUI) for the following DPP services:
To start the DPP application using the GUI, use the following procedure:
Step 1 Go to your dial plan directory (for example, C:\Lightspeed\TransPathCM\DialPlan).
Step 2 Double-click on nextdp.tcl.
This launches the Dial Plan Provisioning System tool.
Step 3 Click on the Commands button for a menu of available utilities.
The Dial Plan Provisioning System main screen contains the Commands button. (See Figure 4-1.)
The DPP utilities perform the following functions, accessible from the Commands menu. (See Figure 4-2):
After you create the dial plan text file, you must import it into the DPP using the DPP utilities. This process loads the text file into the database and verifies that the file follows DPP rules. (See Figure 4-3.)
Text file errors are written to the screen in place of the message shown in Figure 4-3 before the message "Completed." An error in the text file causes the text file load to fail. For example:
C:\Lightspeed\TransPathCM\DialPlan> C:\Lightspeed\JRE\bin\jre -mx32m -ms16m -cp C:\Lightspeed\JRE\lib;C:\Lightspeed\TransPathCM\DialPlan -noverify LightSpeed.DialPlanProvision.DPP -db DPP -load example.txt
Illegal HEADER Format in Plan \rtg1\ansi\deff0\deftab720{\fonttbl{\f0\fswiss Sans
To import a dial plan, use the following procedure:
Step 1 Open the C:\Lightspeed\TransPathCM\DialPlan directory.
Step 2 Double-click on the nextdp.tcl icon to open the DPP software.
The DPP window displays.
Step 3 Type your dial plan file name and extension (in Figure 4-1, example.txt) in the Command Arguments field. (See Figure 4-1.)
Step 4 Click on the Commands button and select Import DP.
The DPP software imports the text file. The DPP results window displays a message indicating specifics of the import. (See Figure 4-3.)
Your dial plan can now create tables from the system's routing data and perform number analysis.
After you import your dial plan, you must generate the tables that the Cisco VSC2700 system uses for number translation.
Perform the following steps to generate a dial plan. You must do this to be able to format the dial plan and routing flat files before they are sent to the telephony controller for further processing.
Step 1 Type TR01 0 in the Command Argument box (Your customer ID and version number). (See Figure 4-1.)
Step 2 Click on the Commands button and select Generate Dial Plan. (See Figure 4-1.)
The DPP generates the dial plan and routing tables, then returns a message in the message area of the DPP window, similar to the message shown in Figure 4-3.
The DPP tool cannot push data files to the telephony controller; the telephony controller pulls data files from a data repository. The DPP data files are saved along with the configuration tool data files as ASCII files (flat files) so they can be accessed for use via the configuration library.
Once the flat files have been created by generating the dial plan, you can retrieve (deploy) them using the config-lib utility.
Step 1 Log onto the telephony controller. (Be sure you are in a C shell.)
Step 2 Type id and press Enter.
If the group is set to transpath, go to Step 4. If the group is not set to transpath, perform Step 3.
Step 3 Type newgrp transpath and press Enter.
Step 4 Type config-lib retrieveDialPlan and press Enter.
This puts you into the config-lib tool.
Step 5 Type 1 and press Enter. (1 is for the option Get Dial Plan from Provisioning System.)
A list of available dial plans will be displayed.
Step 6 Type the number of your dial plan and press Enter.
This validates the dial plan against the dialPlan.dat file and replaces the route name you set up in the DPP text file with the component ID located in the dialPlan.dat file. It also puts this dial plan in the Production area of the telephony controller.
The functions and options you can exercise in the configuration library are shown in Table 4-1.
| Scenario | Resolution |
|---|---|
config-lib command with no dial plan directories created. | Create directories:
|
config-lib retrievedialplan/select 1 | Step 1 Display all dial plans on the Windows NT box. Step 2 Transmit via FTP the selected dial plan into the STAGING directory and validate it. Step 3 If passed, copy into associated config directory and production directory. Step 4 If not passed, delete from STAGING. |
config-lib retrievedialplan/select 2 | Display all dial plan versions in the dial plan production directory. |
When a dial plan is moved onto the telephony controller or a configuration tool configuration is updated, the routing tables must be validated against the configuration files.
For example: for VNET ID T123, version 0, the file is T123.0.dialPlan.
This section provides the procedures for adding another telephony controller to your system.
Adding an open packet telephony controller to your network requires that you create another dial plan. Both dial plans must include routing information for communication between them. This information is part of the IPROUTE data you enter in your outgoing numbering plan.
You must look up the VNET ID of the extended ISUP link and create the dial plan using this ID.
For example: To designate the telephony controller with transpath ID 411, the link is "L411."
In our example, we used the following routing information (refer to "Dial Plan Provisioning Tool"):
B_NUMBER {
523xxx, IPROUTE (1, SC-1);
722xxx, IPROUTE (1, SC-2);
}
If a second open packet telephony controller is part of this configuration, the dial plan would have to include routing data from the first open packet telephony controller to the second open packet telephony controller. The routing information would then look like the following example:
B_NUMBER {
523xxxx, IPROUTE (1, SC-1);
722xxxx, IPROUTE (1, DPC-PRIM);
533xxxx, IPROUTE (2, 0111-0112)
}
Where 0111 represents the first telephony controller and 0112 represents the second. These numbers are actually the names of the telephony controllers you created using the configuration tool. They can be found in the associated dialplan.dat file.
The telephony controller uses certain data that appears in both the DPP output files and the configuration tool output files. To ensure the data matches between the two, you must perform the following tasks:
The routing information in the DPP and the data provisioned using the configuration tool are synchronized in the telephony controller.
Posted: Fri May 28 16:00:20 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.