|
|
This chapter describes the installation of the Dial Plan Provisioning (DPP) tool. The installation of the telephony controller application itself is covered in a separate installation guide included with your telephony controller software.
Your dial plan application and utilities are installed on a Windows NT server. Check that this was configured during your open packet telephony controller software installation.
The dial plan software installation applies to either a single or a dual configuration.
Before software installation, the system administrator should have performed the following high-end host administrative functions:
1. Set parameters.
2. Set group ID access privileges.
3. Set user ID access privileges.
Both the Dial Plan application and the Dial Plan utilities are installed from your CD-ROM via the InstallShield wizard.
After inserting the CD-ROM, you have two choices for installation:
Before using the system, you must set the following environment variable on the UNIX side of your telephony controller software system:
The following variables are set during installation. Do not edit these.
.
.
All active dial plans are kept in the production directory /opt/TransPath/dialPlan.
Any backup dial plans are kept in the subdirectory called DPP_CONFIG_LIB/<associated config dir>.
The associated configuration directory will be created dynamically with a one-to-one relationship with the configuration directories created in /opt/TransPath/etc/CONFIG_LIB/<config dir>.
Each dial plan consists of two files:
These files are moved from the Windows NT box to the UNIX system by FTP (file transfer protocol). A directory on the Windows NT box called C:\Lightspeed\TransPathCM\DialPlan FTP is automatically created during install. You must set up the Microsoft Windows NT Internet Information Server FTP server as an alias called DialPlan that points to this directory.
Dial plans extracted from the provisioning system are placed in the subdirectory called STAGING where they are processed.
The dial plan is validated against the dialplan.dat in /opt/TransPath/etc. If the validation is successful, the routing and dialPlan files become one file. The file will be copied into the associated backup area and will be deployed and activated in the production directory.
If the validation is not successful, the dial plan is deleted from the STAGING directory.
You are now ready to create your dial plan.
Posted: Fri May 28 15:27:02 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.