Lucent Technologies CentreVu Call Management System Release 3 Version 8 Software Installation And Setup Manual

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Installing Feature Packages2-163
4. Access the CMS Administration menu by entering:
cmsadm
The program responds:
5. Select the pkg_install option. The program responds:
The system displays only feature packages that are authorized 
but not yet installed.
6. Enter the number that corresponds to the External Call History 
package (in this example, 2). The program responds:
Lucent Technologies CentreVu(R) Call Management System 
Administration Menu
Select a command from the list below.
1) acd_create Define a new ACD 
2)  acd_remove Remove all administration and data for an ACD 
3) backup Filesystem backup 
4) pkg_install Install a feature package
5) pkg_remove Remove a feature package 
6) run_cms Turn CentreVu CMS on or off 
7) port_admin Administer Modems, Terminals, and Printers
Enter choice (1-10) or q to quit: 
The CMS Features that can be installed are 
1) forecasting
2) external call history 
Enter choice (1-2) or q to quit: 
NOTE
Enter name of computer to which to send call records
(up to 256 characters): 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Installing Feature Packages2-164
7. Enter the name of the computer where call records will be collected. 
The program responds:
8. Press Enter. The program responds:
9. Press Enter. The program responds:
10. Enter the password for nuucp of the receiving computer that was 
administered in uucp. The program responds:
11. Enter the CMS port administered for the Call History Reporting 
machine. This port can either be on one of the 64-port NTS patch 
panels or on one of the 8- or 16-port NTSs. For more information on 
administering the ports on the NTS, see 
CentreVu® CMS Terminals, 
Printers, and Modems
 (585-215-874). The program responds:
Enter full path of the program to transmit the external 
call history files: (default: /cms/dc/chr/uucp_copy)
Enter full path of the program to check the external call 
history file transmission: (default: 
/cms/dc/chr/uucp_check)
Enter password for nuucp login on computer (up to 8 
characters)
Enter CMS port for connection to computer (s_pdevxxx):
Select a speed for this connection 
1) 19200 
2) 38400
Enter choice (1-2): 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Installing Feature Packages2-165
12. Enter the speed that the connection between the CMS and Call 
History Reporting machine will be using. The program responds:
13. Enter the number of call records to be held in the buffer if the Call 
History machine cannot accept the data. (This step reserves disk 
space; therefore, sufficient disk space must be available.)
This step is repeated for each administered A.
The program responds:
If the setup determines that you do not have enough file space, you 
will get the following warning message:
14. Verify that the installation completed successfully by entering:
tail /cms/install/logdir/admin.log
Number of call segments to buffer for ACD xxxxx (0-99999):
NOTE
Computing space requirements and file system space 
availability.
External Call History package installed.
Failed to find sufficient file space for CMS data.
WARNING: You do not currently have sufficient file space 
for your existing CMS data. At this point you should turn 
on CMS, go to the “Data Storage Allocation” screen, and 
verify/modify the administration, or go to the “Free 
Allocation” screen and verify/modify your existing free 
space.
External call history package installed with warnings. 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Installing Feature Packages2-166
If the External Call History package is installed successfully, the 
program responds: 
You may edit this file in order to add comments about the packages 
that were installed or authorized.
If you need to install Forecasting, go to “Installing the Forecasting 
Package” on Page 2-157.
If you are not installing any other feature packages, do the following to 
turn on CMS:
1. Access the CMS Services menu by entering cmssvc.
The menu appears.
2. Enter 3 to select the run_cms option.
3. Enter 1 to turn on CMS.
CMS turns on.
External Call History package installed (date/time ) 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Setting Up the Remote Console2-167
Setting Up the Remote ConsoleB
OverviewBThis section describes how to redirect the remote console port using the 
Solaris software package. Redirecting the console allows the TSC to dial 
in and do remote maintenance. The port used for remote console access 
differs depending on the hardware platform:
Platform 
Considerations
B
lAll platforms.
Administering 
the Remote 
Console Port
B
To administer the remote console port on the back of the CMS computer, 
do the following:
1. Remove the current port administration by entering:
/cms/install/bin/abcadm -r ttyX 
(where X is “a” or “b”)
The program responds:Hardware Platform Port A Port B
SPARCserver 
Enterprise 3000 
Enterprise 3500
Remote 
ConsoleSwitch Link
Ultra 5 Switch LinkRemote 
Console
ttyX is currently set to be incoming
Are you sure you want to change it? [y,n,?] 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Setting Up the Remote Console2-168
2. Enter y. The program responds:
3. Enter the following
 to administer the remote console port:
/cms/install/bin/abcadm -i -b 9600 ttyX 
(where X is “a” or “b”)
The program responds:
The remote console port has been administered.
Using the 
Remote Console 
Port
B
Use the remote console port functions on a CMS computer by:
lredirecting the console from the local console to the remote console
lredirecting the console back to the local console
1. Dial in from the remote console to the remote console modem on 
the CMS computer and log in as 
root.
2. Remove the port monitor by entering:
/cms/install/bin/abcadm -r ttyX 
(where X is “a” or “b”)
The program responds:
ttyX administration removed
ttyX set to incoming port 9600 baud
#
ttyX is currently set to be incoming
Are you sure you want to change it? [y,n,?] 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Setting Up the Remote Console2-169
3. Enter y. The program responds:
4. Redirect the console to the remote console port by entering the 
following:
/cms/install/bin/abcadm -c -b 9600 ttyX
The program responds:
5. Enter y. The system will automatically reboot, and the remote 
console port will come up as the console.
As the system reboots, shut down messages appear on the local 
console. When the system starts to come back up, the local console 
should go blank and the system boot diagnostics should appear on 
the remote console. When the system is restarted, a login prompt 
should appear on the remote console.
6. Log in to the remote console as 
root. An OpenWindows login 
window should appear on the local console.
If you enter Control-D from the remote console to exit the system 
without first redirecting control back to the local console, you may 
lock yourself from using the console locally or remotely.
7. Redirect the console back to the local console by entering:
/cms/install/bin/abcadm -c local
ttyX administration removed
This change requires a reboot to take affect
Are you ready to reboot? [y,n,?]
!CAUTION: 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Setting Up the Remote Console2-170
The program responds:
8. Enter y. The system automatically reboots and the remote console 
port comes up as a regular dial-in port with the login: prompt 
displayed.
As the system reboots, the shutting-down messages appears on the 
remote console. When the system starts to come back up, the 
system boot diagnostics should appear on the local console. After 
the system reboots, a login prompt should appear on the local 
console.
9. Log into the local console as 
root.
The console has been redirected from the remote console to the 
local console.
Console set to local
This change requires a reboot to take affect
Are you ready to reboot? [y,n,?] 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Setting Up the NTS2-171
Setting Up the NTSB
OverviewBEach Network Terminal Server (NTS) needs to be set up so it will be 
recognized on the network. The following networking items need to be 
set up:
lInternet address
lSubnet mask
lPreferred load host internet address (the address of one or more 
CMS computer)
lBroadcast address
lType of IP packet encapsulation.
This procedure needs to be completed on each NTS being installed. 
If you set up more than one NTS for the system, the IP addresses 
must be unique (see the table in Prerequisites section, below).
Platform 
Considerations
B
lAll platforms.
NOTE: 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Setting Up the NTS2-172
PrerequisitesBObtain the network IP address and NTS IP address for each NTS you are 
administering. The NTS number depends on the total number of ports 
required for the system and the type of NTS.
ProcedureB1. Edit the hosts file by entering the following:
vi /etc/hosts
2. Add a separate line in this file for each NTS that corresponds to the 
addresses from the Prerequisites table. The following is an example 
hosts file:
This example shows the default IP address for the CMS computer 
and the factory defaults for the NTS units.
3. Press the Esc key to leave the edit mode.
4. Enter :w! to overwrite the existing file.
5. Enter :q to quit editing the file.Device IP Address* Network Name
Host Computer 192.168.2.1
hostname
First NTS 192.168.2.101 cmsterm1
Second NTS 192.168.2.102 cmsterm2
Third NTS 192.168.2.103 cmsterm3
Nth NTS 192.168.2.1xxcmstermX
* The IP addresses shown here are the factory defaults. 
Use the actual system addresses if available.
192.168.2.1 cmshost
192.168.2.101 cmsterm1
192.168.2.102 cmsterm2
192.168.2.103 cmsterm3
192.168.2.104 cmsterm4