|
|
This guide contains procedures for installing and upgrading the Cisco Software Release 4 telephony controller configuration tool (CT) application, telephony controller utilities software, the dial plan tool, and Cisco telephony controller software.
These procedures are designed for a dual configuration (also called switchover or duplex configuration) system, which requires familiarity with the telephony controller system, the CT, MML (Man-Machine Language), and the UNIX, Windows 95, and Windows NT operating systems.
This guide contains the following sections:
Before you install or upgrade the Cisco Software Release 4 telephony controller configuration tool, check the following:
This version of the telephony controller requires the following hardware and software.
This section contains instructions for installing the Cisco Software Release 4 telephony controller configuration tool applications and CT utilities software for the first time and contains the following:
Install the new CT and CT utilities software as follows:
Step 1 Insert the configuration tool CD into the CD-ROM drive.
Step 2 Start Explorer by selecting the My Computer icon with the right mouse button and choosing Explore from the popup menu.
Step 3 Expand the CD-ROM drive to show the folders contained on the CD-ROM by selecting the `+' to the left of its icon in the left windowpane.
Step 4 Display the contents of the CT Utilities directory by selecting the appropriate folder in the left windowpane.
Step 5 Double-click the Setup.exe icon in the right windowpane to begin the installation of the Configuration Tool Utilities. The TransPath Configuration Tool Utilities window appears.
Step 6 Select Next in the Welcome dialog box.
Step 7 Read the terms of the licensing agreement and click Yes in the Software License Agreement dialog box to continue the installation.
Step 8 Click Next in the Choose Destination Location dialog box to accept the default installation directory (C:\Lightspeed) or select another directory.
Step 9 Acknowledge the completion of the installation by clicking Finish in the Setup Complete dialog box.
Step 10 Click the CT Application folder in the left windowpane of the Explorer window, and repeat Step 5 through Step 9 to install the CT application.
Step 11 If the application and utilities were installed in a directory other than C:\Lightspeed then edit the file server.bat. (normally C:\Lightspeed\server.bat).
LS_CONFIG = <directory chosen in step 8>
This section contains the procedure for configuring the servers.
Step 1 Copy the default database:
(a) Go to the C:\LightSpeed\TransPathCM\database directory.
(b) Copy the database file default.mdb to lpt.mdb.
Step 2 Configure the ODBC data source:
(a) From the Start menu, select Settings, then Control Panel, then ODBC (32 bit).
(b) Select Add under the System DSN tab.
(c) Double-click on Microsoft Access Driver.
(d) Press Select in the database section.
(e) Browse to the directory C:\LightSpeed\TransPathCM\database\lpt.mdb.
(f) Enter the TP2000 DataSource name.
(g) Click on Options and set the buffer size to 32768 to optimize system performance.
Step 3 Configure Microsoft Internet Server (first the WWW server, then the FTP server):
(a) Configure your WWW server:
(b) Configure your FTP server:
Step 4 Configure the startup file. Before the CT can be started, the startup files must be configured to match the current system. Two files must be edited with the correct hostname and domain name for your server. Determine the hostname and domain name for your server as follows:
(a) Click Control Panel, Network, then Protocol.
(b) Select TCPIP, Properties, then DNS. The hostname and domain name for your server are listed.
Step 5 Configure the startup files as follows:
(a) Use WordPad to modify the startup script in the server.bat file. Open WordPad by choosing Programs, Accessories, then WordPad from the Start menu.
(b) In WordPad, open the server.bat file located in the C:\Lightspeed (or alternative) directory:
File name: server.bat
(c) Change <hostname> to the hostname of your server (for example, <ctsrvr>):
IT_LOCAL_HOST= <hostname>
(d) Change <domain name> to your domain name:
IT_LOCAL_DOMAIN= <domain name>
(e) Save the file. The server.bat file is overwritten with your changes.
C:\Lightspeed\Java\bin\java LightSpeedCM.CMLightSpeedServer
%IT_LOCAL_HOST% 8000 %DATASOURCE% %LS_CONFIG_PATH% \TransPathCM\database20.
Step 6 Use WordPad to modify the HTML file used to start the CT Java Applet from Netscape Navigator (see Figure 1 in Upgrading the Telephony Controller Configuration Tool) as follows:
(a) Open the default HTML file located at C:\Lightspeed\TransPathCM\Applet (or alternative directory). Enter default.html in the File name field:
File Name: default.html
(b) Change <hostname>.<domain name> to match your host and domain name. For example:
PARAM NAME= host VALUE=<hostname>.<domain name>
(c) Save the file. The default.html file is overwritten with your changes.
Step 7 On the CT server, edit the C:\WINNT\System32\Hosts file by adding the IP address and host name for your server and each of the clients that will connect to the system:
(a) Enter IP addresses and host names similar to the following for each client:
C:\WINNT\System32\Hosts <IP Address> <servername> <servername>.<domain name> <IP Address> <Client1> <client1>.<domain name> <IP Address> <Client2> <Client2>.<domain name>
Step 8 On each client PC that will access the CT server, add the server name and the client name to the host files as follows:
C:\WINNT\System32\Hosts <IP Address> <servername> <servername.domain name> <IP Address> <Client1> <client1.domain name>
C:\Windows\System\Hosts <IP Address> <servername> <servername.domain name> <IP Address> <Client1> <Client1.domain name>
The telephony controller configuration tool installation is complete.
This section contains procedures for upgrading the Cisco Software Release 4 telephony controller CT applications and CT utilities software.
To upgrade the CT software on the telephony controller system, follow these steps:
Step 1 Stop all database access to the Windows NT server that hosts the CT application.
(a) Close Netscape Navigator.
(b) Close the Orbix nameserver (ns.exe), Orbix daemon (orbixd.exe), and Java (server.bat) server command windows.
Step 2 Make a backup copy of the access database used by the CT (lpt.mdb) by creating a backup directory into which to copy the database file. From the Windows NT Explorer, do the following:
(a) Start Windows Explorer NT by selecting the My Computer icon with the right mouse button, and choosing Explore from the popup menu (see Figure 1).
(b) With the right mouse button, click New, then Folder from the popup menus. Name the new folder Backup.
(c) Select the database folder.
(d) Select the lpt.mdb file from the contents list in the right windowpane using the right mouse button, and drag the file to the Backup folder in the left windowpane.
(e) Select Copy Here from the popup menu.
Step 3 Close the Windows NT Explorer window.
Step 4 Remove the existing CT installation as follows using uninstallShield:
(a) From the Start menu, open the Windows NT Control Panel by selecting Settings, then Control Panel.
(b) Double click the Add/Remove Programs icon. The Add/Remove Programs Properties window with the Install/Uninstall tab appears.
(c) Click the Install/Uninstall tab.
(d) Choose TransPath Configuration Tool from the list of programs displayed.
(e) Click the Add/Remove button (see Figure 2).
(f) Select Yes in the Confirm File Deletion dialog box to activate uninstallShield.
(g) Click OK on the Remove Programs From Your Computer dialog box when uninstallShield completes.
Step 5 Close the Add/Remove Program Properties window.
Step 6 Repeat Step 4 to remove the Configuration Tool Utilities package.
The CT application and its utilities packages are now removed. You can install the new CT application and CT utilities software by proceeding to Installing CT and CT Utilities Software.
After removing the existing telephony controller configuration tool application and configuration tool utilities packages, install the new CT application and CT utilities software as follows:
Step 1 Insert the configuration tool CD into the CD-ROM drive.
Step 2 Start Explorer by selecting the My Computer icon with the right mouse button and choosing Explore from the popup menu.
Step 3 Expand the CD-ROM drive to show the folders contained on the CD-ROM by selecting the `+' to the left of its icon in the left windowpane.
Step 4 Display the contents of the CT Utilities directory by selecting the appropriate folder in the left windowpane.
Step 5 Double-click the Setup.exe icon in the right windowpane to begin the installation of the Configuration Tool Utilities. The TransPath Configuration Tool Utilities window appears.
Step 6 Select Next in the Welcome dialog box.
Step 7 Read the terms of the licensing agreement and click Yes in the Software License Agreement dialog box to continue the installation.
Step 8 Click Next in the Choose Destination Location dialog box to accept the default installation directory (C:\Lightspeed) or select another directory.
Step 9 Acknowledge the completion of the installation by clicking Finish in the Setup Complete dialog box.
Step 10 Click the CT application folder in the left windowpane of the Explorer window, and repeat Step 5 through Step 9 to install the CT application.
Step 11 Edit the file server.bat (normally C:\Lightspeed\server.bat) if the application and utilities were installed in a directory other than C:\Lightspeed. For example:
LS_CONFIG = <C:\Lightspeed>
Step 12 Copy the lpt.mdb backup file into the C:\Lightspeed\TranspathCM\database directory (or alternative directory).
Step 13 Expand the C:\ Lightspeed (or alternative directory) and TransPathCM folders.
Step 14 Click the MigrateDB folder in the list in the left windowpane in order to access the migrate.bat batch file used to update the database schema.
Step 15 Double-click the migrate.bat icon in the right windowpane to update the C:\lightspeed\transpathcm\database\lpt.mdb database (or alternative directory).
Step 16 Close the Explorer window.
Step 17 Configure the startup file. Before the CT can be started, the startup files must be configured to match the current system. Two files must be edited with the correct hostname and domain name for your server. Determine the hostname and domain name for your server as follows:
(a) Click Control Panel, Network, then Protocol.
(b) Select TCPIP, Properties, then DNS. The hostname and domain name for your server are listed.
Step 18 Configure the startup files as follows:
(a) Use WordPad to modify the startup script in the server.bat file (see
Figure 3). Open WordPad by choosing Programs, Accessories, then WordPad from the Start menu.
(b) In WordPad, open the server.bat file located in the C:\Lightspeed (or alternative) directory:
File name: server.bat
(c) Change <hostname> to the hostname of your server:
IT_LOCAL_HOST= <hostname>
(d) Change <domain name> to your domain name:
IT_LOCAL_DOMAIN= <domain name>
(e) Save the file. The server.bat file is overwritten with your changes.
Step 19 Use WordPad to modify the HTML file used to start the CT Java Applet from Netscape Navigator (see Figure 4) as follows:
(a) Open the default HTML file located at C:\Lightspeed\TransPathCM\Applet (or alternative directory). Enter default.html in the File name field:
File Name: default.html
(b) Change <hostname>.<domain name> to match your host and domain name. For example:
PARAM NAME= host VALUE= <hostname>.<domain name>
(c) Save the file. The default.html file is overwritten with your changes.
It is now possible to run the server.bat file and the CT. The server.bat script starts the Orbix daemons (ns.exe and orbixd.exe) and the Java server. You can now "build and deploy" the appropriate site(s) from the CT for later retrieval on the other server.
This section contains procedures for upgrading the telephony controller software that runs on your Sun servers. These procedures are designed for a dual configuration telephony controller system.
This section contains the following:
Before you upgrade the Cisco telephony controller software, check the following:
On a dual configuration telephony controller system, each Sun server is upgraded independently of the other, so that call processing can continue during the upgrade. To upgrade the telephony controller software, you must do the following:
1. Back up your present configuration.
2. Uninstall the old software.
3. Install the new software.
4. Configure the new software.
Step 1 Determine which server is running as the primary telephony controller. In a dual system configuration, the primary system is the one running the process manager (procM) and the failover daemon (foverd). The secondary controller (or standby) is running the file replication daemon (frepld) as well as the failover daemon.
Step 2 Log in as a user who is in the transpath group (for example, sctac) on the secondary server. Cisco recommends upgrading the secondary telephony controller first, so that the primary system continues to operate while the upgrade is taking place.
Step 3 Save the current production configuration to the configuration library so that it can be restored quickly if necessary. To save the configuration in the configuration library:
(a) Change directory (cd) to the following:
cd /opt/TransPath/local
(b) Ensure that you are in the proper user environment by entering the following at the C-shell prompt (%):
source .cshrc
The user environment generally includes the following:
XE - PLATFORM_ID = 1
XE - CONFIG_FILE_1 = /opt/TransPath/etc/XECfgParm.dat
XE - HOME = /opt/TransPath/bin
XE - TABLES_FILE = /opt/TransPath/etc/tables.dat
(c) Enter config-lib and directory option number 2 from the menu displayed (see
Figure 5).
(d) Enter y at the system prompt.
(e) Create an archive of the configuration library using option number 5 from the config-lib menu. This will make a copy of the directory containing the library of configurations in the sctac directory:
/export/home/sctac /opt/TransPath/etc/CONFIG_LIB
(f) Enter q (quit) at the system prompt.
Step 1 Switch user to root (superuser) and shut down the telephony controller processes to uninstall the old software:
su -root Password
Step 2 Stop the current telephony controller application by entering the following:
sh /etc/init.d/transpath stop
Step 3 Remove the current telephony controller software to make way for the new installation. To remove the current software, you must remove any patches and utilities packages.
(a) Enter the following to determine if you have patches installed:
pkginfo | grep PF
If the system returns a response, you must remove these patches before installing the software.
(b) Remove each patch by entering the following:
pkgrm packagename
(c) Enter y at the system prompts.
For example:
# pkginfo | grep PF
application PF9900047 TransPath Patch Component
# pkgrm PF9900047
The following package is currently installed:
PF9900047 TransPath Patch Component
(sparc) P40AA DROP 4.2(18) PF9900047
Do you want to remove this package? y
## Removing installed package instance <PF9900047>
This package contains scripts which will be executed with super-user
permission during the process of removing this package.
Do you want to continue with the removal of this package [y,n,?,q] y
## Verifying package dependencies.
## Processing package information.
## Executing preremove script.
Removal of <PF9900048> was successful.
(d) Determine which utilities packages are installed on the system by entering the following:
pkginfo | grep TU
The system returns a list of utilities packages.
(e) Remove utilities packages as needed by entering the following:
pkgrm packagename
For example:
pkgrm CSCOgu001
(f) Place the telephony controller CD-ROM in the CD-ROM drive. The CD-ROM will mount automatically at /cdrom/cdrom0 by following the on-screen directions and answering y (yes) to all of the prompts.
The mounting process will take several seconds. If the CD file system does not mount automatically, it can be mounted manually by changing directory to /cdrom/application and entering this command:
mount -r -F hsfs /dev/dsk/c0t6d0s0/cdroM
(g) When the CD-ROM mounts successfully, enter the following commands:
cd cdrom/cdrom0/APPLICATION sh uninstall.sh
Step 1 Install the new software in the reverse order, beginning with the telephony controller utilities. Only one of each utility type can be installed at any given time by using the pkgadd command. The following example is for a signaling controller:
(a) To install the utilities, enter the following:
cd ../UTILITIES pkgadd -d tu00p40aa.pkg
The output will look similar to the following:
The following packages are available:
1 TU00P40AA Telephony Controller Utilities - GNU libg++
(sparc) P40AA DROP 1.0
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Processing package instance <TU00P40AA> from </cdrom/sc2200_429/utilities/tu00p40aa.pkg>
Telephony Controller Utilities - GNU libg++
(sparc) P40AA DROP 1.0
Cisco System, Inc.
Enter base directory path (default /opt) [?,q]
Using </opt> as the package base directory.
## Processing package information.
## Processing system information.
1 package pathname is already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user permission during the process of installing this package.
Do you want to continue with the installation of <TU00P40AA> [y,n,?] y
Installing Telephony Controller Utilities - GNU libg++ as <TU00P40AA>
## Executing preinstall script.
## Installing part 1 of 1.
/opt/TransPath/bin/perl
/usr/lib/libg++.so <symbolic link>
/usr/lib/libg++.so.2.7.2
/usr/lib/libstdc++.so <symbolic link>
/usr/lib/libstdc++.so.2.7.2
[ verifying class <none> ]
Installation of <TU00P40AA> was successful.
Step 2 Enter y to continue.
Step 3 Install the appropriate driver. You will need to install only one driver of several choices based on your specific network. ITK has two options depending upon the network to which you are connecting:
PTI has two options depending upon the network:
(a) To install a driver, enter the following:
cd ../DRIVERS ls
The system returns a list of the latest drivers. Install the driver for your network. For example, to install the E1/T1 (ITK) driver, enter:
pkgadd -d ITK -HDLCP40AA.pkg
In this case, 40AA represents the major version number.
Check the progress of each driver package reboot, if necessary, by using the ps -ef command.
Step 4 Install the rest of the telephony controller software by using one of the following options:
(a) Use the autoinstall.sh script to automatically install the rest of the software (excluding the utilities and drivers). This option is recommended for most installations.
To use the autoinstall.sh script, enter the following:
cd ../APPLICATION sh autoinstall.sh
(b) Use the install.sh script to install each package. This presents a list of packages as they are installed, and allows you to skip installation of a particular package.
To use the install.sh script, enter the following:
cd ../APPLICATION sh install.sh
This option prompts you to install all the application modules individually (excluding the utilities and drivers). The system displays each package and a prompt. Press Enter to install the package, or q to bypass the package. If you install the package, the system prompts you to enter a default directory. Press Enter to accept the /opt/TransPath default directory.
After the system has rebooted, you will need to log in and modify the configuration in the XECfgParm.dat file.
Step 1 Modify the execution environment.
(a) Log in as root.
(b) To stop the telephony controller software, enter:
sh /etc/init.d/transpath stop
(c) Modify the /etc/group file to add the required users into the telephony controller group. The software reload has reset the telephony controller group. User names must be added to the list in order to properly run telephony controller commands such as mml. The transpath group entry should look similar to the following:
transpath::20000:transpath,user1,user2,user3
(d) Add users to the site as appropriate. The group entry consists of the
group name:password:group ID number:comma-separated list of users.
(e) Exit from the root account, then log in again as any member of the transpath group.
Step 2 Modify the /opt/TransPath/etc/XECfgParm.dat configuration file. The XECfgParm.dat file contains a list of resources used by the telephony controller application to define its execution environment (XE).
(a) To modify the XECfgParm.dat file, enter the following:
cd /opt/TransPath/etc
Use a text editor to modify the resources listed in Table 1.
| Resource | Modification |
|---|---|
| Equals the hostname or IP address of the CT NT server. |
| Equals the ID number of the telephony controller on the TransPath Properties screen in the CT. |
| Set equal to Info to reduce the volume of information logged by syslog. |
| Can be set equal to false as module specific (procM/foverd) resources are defined later. |
| Set equal to the IP address of the machine you are logged onto. Up to three additional addresses can be configured using the resources *.IP_Addr2-4. These additional resources must be configured if additional Ethernet interfaces are installed and configured. |
procM.runAsDaemon | Defaults to true. Set to false if configuring a dual system. |
foverd.conn1AddrA | Defaults to 171.71.120.19:1050. This is the IP address and UDP port number used by this host to receive heartbeat messages from the failover peer |
foverd.conn1AddrB | Defaults to 171.71.120.19:1051. This is the IP address and UDP port number used by the failover peer to receive heartbeat messages from this host. |
foverd.conn2AddrA | Defaults to 171.71.120.19:1052. This is the IP address and UDP port number used by this host as a secondary connection to receive heartbeat messages from the failover peer. |
foverd.conn2AddrB | Defaults to 171.71.120.19:1053. This is the IP address and UDP port number used by the failover peer as a secondary connection to receive heartbeat messages from this host. |
foverd.abswitchPort | Defaults to /dev/cua/a001--- must be set to the name of the serial device used to connect to the A/B switch. |
foverd.logPrio | Defaults to Debug--- should be set to Info to reduce the quantity of messages logged. |
foverd.logDest | Defaults to all--- should be set to sysLog. A value of all means that duplicate messages are logged for foverd: Once using the syslog facility and once using the telephony controller's own internal logging mechanism. |
(b) Modify the failover configuration resources. In a dual configuration, you must modify the failover configuration resources. See Invoking Manual Failover to perform a manual failover.
Before running a failover system, check that the following remote file systems are available by entering:
ls /opt/remote/etc ls /opt/remote/dialPlan
If either command fails to give you a directory listing corresponding to the remote system, do not run the replication process (frpld) on the secondary system. See Cisco Connection Online for assistance, or contact your Cisco support representative.
A sample configuration might look similar to the following
On system1: foverd.conn1AddrA = 10.100.44.10:1050 foverd.conn1AddrB = 10.100.44.11:1051 foverd.conn2AddrA = 10.100.45.10:1052 foverd.conn2AddrB = 10.100.45.11:1053 On System2: foverd.conn1AddrA=10.100.44.11:1051 foverd.conn1AddrB=10.100.44.10:1050 foverd.conn2AddrA=10.100.45.11:1053 foverd.conn2AddrB=10.100.45.10:1052 When a second Ethernet connection is not available, it is possible to configurefoverdto send and receive heartbeats on an asynchronous serial connection. In this case, set theconnection2resources by following this example:foverd.conn2Type=serialfoverd.conn2AddrA=/dev/cua/a000foverd.conn2AddrB=/dev/cua/a000
(c) Modify conn2AddrA/B resources that pass heartbeat messages. Table 1 defines resource changes that must be made where conn2AddrA/B resources denote the name of the serial device used to pass heartbeat messages.
The execution environment configuration is complete.
Step 3 Once the execution environment (XE) is configured, retrieve the configuration from the telephony controller configuration tool.
To retrieve the latest configuration enter the following:
config-lib retrieve <version>
where <version> represents the name this configuration will have in the configuration library.
Step 4 Stop the primary telephony controller and prepare to bring the updated system into service as follows:
(a) Log in to the primary telephony controller as root and enter the following command:
/etc/init.d/transpath stop
(b) After the shutdown occurs (ps -ef | grep tran), exit from this telephony controller and start the updated software by switching user to root using the su command:
su - root
(c) To start the telephony controller software, enter:
/etc/init.d/transpath start
(d) If the software is installed correctly and the system is configured properly, the following telephony controller processes will start:
Step 5 Test the upgrade by ensuring that calls complete as they did before the upgrade.
When you are satisfied that the new system is functioning properly, proceed with updating the software on the second Sun server by returning to Upgrading the Telephony Controller Software.
This completes the telephony controller software upgrade.
Use the following procedure to invoke a manual failover from one system to the other to ensure that the ITK cards handling MTP2 software are reset correctly after call processing has stopped.
Step 1 With both platforms operating normally (primary and secondary systems), identify the platform currently running as primary and designate it "A."
va-havisu% ps -ef | grep procM transpat 9402 1 0 11:07:23 ? 0:02 procM
Step 2 Identify the remaining system as the secondary system and designate it "B."
Step 3 Log in as root.
Step 4 On system A, initiate a manual failover:
va-havisu# /opt/TransPath/local/cmd_failover.sh STOP
Step 5 Verify that system B has become the primary system and has links in service as expected by examining the output from the root command:
mml>rtrv-softw:all TransPath: TP00 Havisu 1998-12-10 13:40:44 M RTRV "CFM-01:RUNNING" "ALM-01:RUNNING" "MM-01:RUNNING" "DMPR-01:RUNNING" "DSKM-01:RUNNING" "ENG-01:RUNNING" "IOCM-01:RUNNING" "IOCC-01:RUNNING" "IOCC-02:RUNNING" ; mml>rtrv-sc:all TransPath: TP00 Havisu 1998-12-10 13:40:51 M RTRV "SC1-NAS1:SP1-IP,LID=0:IS" /* SC1-NAS1: Sig Channel 1 for IP Sig Path NAS1 */ "DC-1-0:LS-1,LID=0:IS" /* DC-1-0: ANSI SS7 */ ; mml>
Step 6 Perform any required maintenance on system A to prepare to start it as secondary.
Step 7 To start system A operating as the secondary system:
Or
# cd /opt/ITK/bin # ./ixload
ixload: Version 2.03
ixload: Device /dev/ixl,0
Loadfile for ix1-primary PCI 8MB V1.0-Release 08.12.1998 17:51 (#483)
Cisco Systems variant
Download ix1 software: ixpp.bin \|/-\|/-\|/
ixload: Run Firmware ... ok
# /etc/init.d/transpath start
To cause system A to operate as primary, stop system B using the same procedures described in Step 4 immediately after restarting.
Manual failover is invoked.
Step 8 Enter eject cdrom at the prompt to remove the CD from the Sun server.
pkgrm:ERROR: No package associated with <M711P40AA> can be ignored.
This section contains instructions for upgrading the configuration tool software from a remote central location using the SS7 Dial-up Access solution with UNIX commands.
Before beginning your remote upgrade, check the following requirements:
Begin the remote upgrade as follows:
Step 1 Follow Step 1 through Step 2 in Upgrading the Telephony Controller Software to begin your upgrade.
Step 2 Instead of executing Step 3 in Upgrading the Telephony Controller Software, remove the telephony controller packages manually using the pkgrm command in this order:
(a) Remove patches
(b) Remove drivers
(c) Remove the application
(d) Remove the utilities
(e) Verify that all telephony controller-related software has been removed using the pkginfo command.
Step 3 Insert the telephony controller upgrade CD-ROM into the drive on the central server.
Step 4 Review the contents of the CD-ROM using the appropriate commands.
Step 5 Note the directory tree where the current software packages are installed. For example:
E:\Application
E:\Drivers
E:\Patches
E:\Utilities
Step 6 Telnet in to the remote host using either your server name or an IP address:
% telnet <servername>
Step 7 Browse to the /usr directory.
Step 8 Create temporary subdirectories in a tree that mirrors the one on the host server CD-ROM. Choose directory names that are similar to the ones used on the CD-ROM for ease of relationship recognition.For example:
/usr/SC2200 Rel XXX/Application
/usr/SC2200 Rel XXX/Drivers
/usr/SC2200 Rel XXX/Patches
/usr/SC2200 Rel XXX/Utilities
Step 9 Start the FTP on the central sever.
Step 10 Use FTP in binary mode to transfer the contents of the CD-ROM directories on the central server to the corresponding directories on the remote host platform.
Step 11 Proceed with the upgrade as described in Step 1 in Installing the New Software. However, instead of using the /cdrom/cdrom0/XXX directory use the /usr/SC2200 Rel XXX/XXX directory. For example, /usr/SC2200 Rel 2.15/Utilities.
Step 12 After the installation is complete, remove the contents of the relevant
/usr/SC2200 Rel XXX subdirectories, then remove the subdirectories themselves from the remote host.
The remote upgrade is complete.
For more information about upgrading the telephony controller software from a remote central location, contact your account representative, or refer to Cisco Connection Online, and select the WWW: http://www-europe.cisco.com option.
This section contains instructions for managing your dial plan.
The dial plan management system is a program used to update your dial plan. Before using the system, you must set the following environment variables on the telephony controller system:
Use the config-lib utility of the telephony controller system to manage your dial plan.
Step 1 Log in to the telephony controller server.
Step 2 Enter cd/export/home/sctac
Step 3 Enter cp -pr CONFIG_LIB/opt/Transpath/etc
Step 4 To restore the saved dial plans, enter:
cp -pr DPP_CONFIG_LIB/opt/Transpath/dialPlan
Step 5 Enter cd /opt/TransPath/local
Step 6 To launch the config-lib utility (See Figure 6), enter:
config-lib
Step 7 Enter 1 (List Configuration Versions in Library). A list of available dial plans are displayed, followed by the list of options.
Step 8 Enter 3 (Copy Library Version to Production). The versions are listed and the current version is noted.
Step 9 Enter the desired version number. This dial plan is moved into the Production area on the telephony controller.
Step 10 Confirm that you want to overwrite the production files by entering y.
Step 11 Enter an MML Session ID between 1 and 10. Cisco recommends that you use a number from the high end of that range. This step makes this dial plan the active one.
Step 12 Enter q and press Enter. This closes the dial plan utility.
The functions and options you can use in config-lib are shown in Table 2.
| Scenario | Resolution |
|---|---|
Config-lib retrieve | Transmit a new version of configuration data files into backup and production using FTP. Dial plans in the dial plan production directory are deleted. |
Config-lib command with no dial plan directories created. | Create directories (dialPlan, dialPlan/Staging, and dialPlan/DPP_CONFIG_LIB). |
Config-lib retrievedialPlan/select 1 | Display all dial plans on the Windows NT box, transmit via FTP the selected dial plan into the Staging directory and validate it. If passed, copy into associated config directory and production directory. Otherwise, delete from Staging. |
Config-lib retrievedialPlan/select 2 | Display all dial plans in the dial plan production directory. |
Config-lib / select 1 | Display all configuration libraries and the current dial plan version in the production directory. |
Config-lib / select 2 | Saves configuration and dial plan files from the production area to a new directory. The current version is changed to the newly named configuration version. |
Config-lib / select 3 | Copy a configuration version into the production. If there is an associated dial plan, copy it into dial plan production directory. |
Config-lib / select 4 | Remove a configuration version directory. If it is the current version, it cannot be deleted. Otherwise, both configuration and dial plan directories are deleted. |
Config-lib / select 5 | Backup the configuration and dial plan. Copy all version directories into $backupDir. |
Config-lib / select 6 | This feature has not been implemented. |
For more information about dial plan management, see the Cisco document, Dial Plan Management at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/r2/dpp2/dialch05.htm
For more information about the telephony controller system, see the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/index.htm
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Posted: Thu Dec 23 08:36:48 PST 1999
Copyright 1989-1999©Cisco Systems Inc.