Lucent Technologies Octel 100 Implementation And Service Manual

							6. Installing the Software
Implementation and Service ManualInstalling OS/2 W arp 4.06-5
d.  Deselect the W IN-OS/2 Support option if it is listed.
e.  Deselect the Multimedia Software Support option.
f.  Click Next. The Adv anced Options screen displays.
21.  Verify that the Add existing programs to your Desktop option is selected, then click
OK to continue. Note that if you formatted the partition, the other options on the
screen are dimmed. A series of screens display as the system transfers files to the
PC.
22.  When an OS/2 Warp Setup and Installation dialog box displays, click OK.
23.  When you are prompted that the shutdown is complete, press  to
restart the PC. When the PC restarts and the OS/2 desktop displays, the installation
is complete.
24.  If you did not create partitions in step 8, skip to step 25. If you created partitions in
step 8, you now need to format the additional partitions (the primary partition was
formatted when you installed OS/2 W arp):
a.  Double-click the OS/2 System icon on the OS/2 desktop. The OS/2 System
folder displays.
b.  Double-click the Driv es icon. The Driv es window displays.
c.  Click the right mouse button on the Driv e D icon.
d.  Select Format disk from the menu that displays. The Format Disk D box
displays.
e.  In the Volume Label field, enter Driv e D.
f.  Under File System Type, select FAT (File Allocation Table).
g.  Click Format. The Format Progress screen displays.
h.  W hen the progress bar reaches 100%, click OK. The Format Disk D box
displays.
i.  Click Cancel. The Driv es window displays.
j.  Click the right mouse button on the Driv e E icon.
k.  Select Format disk from the menu that displays. The Format Disk D box
displays.
l.  In the Volume Label field, enter Driv e E.
m.  Under File System Type, select HPFS.
n.  Click Format. The Format Progress screen displays.
o.  W hen the progress bar reaches 100%, click OK. The Format Disk E box
displays.
p.  Click Cancel. The Driv es window displays.
q.  Double-click the icon in the upper-left corner of the window to close the Driv es
folder. The OS/2 System window displays.
r.  Double-click the icon in the upper-left corner of the window to close the OS/2
System folder.
25.  Install Fix Pak 10. See the following topic, “Installing OS/2 W arp Fix Pak 10.” 
						

							6. Installing the Software
Implementation and Service ManualInstalling the Messaging System Software6-6
If you are installing Visual Mailbox in a Windows NT Server or Local Files Server
implementation, see the topic, “Installing Networking Services for OS/2,” in Chapter 19,
“Installing and Configuring Visual Mailbox.”
Installing OS/2 Warp Fix Pak 10
OS/2 W arp Fix Pak 10 must be installed on PCs running OS/2 W arp 4.0. IBM issued Fix
Pak 10 to address OS/2 W arp 4.0 operating system anomalies.
To install OS/2 Warp Fix Pak 10:
1.  Insert the messaging system CD-ROM in the CD-ROM drive. (If you are installing
Fix Pak 10 immediately following OS/2 W arp 4.0 installation, the CD-ROM should
still be in the CD-ROM drive.)
2.  Open an OS/2 window.
3.  From the C: prompt, type F: 
and press .
4.  From the F: prompt, type instfp10 
and press . The OS/2 W arp Fix Pak
10 install begins.
5.  W hen the file update is complete, the OS/2 window displays a message that the Fix
Pak 10 file transfer is complete. Press any key to continue.
6.  Remov e the CD-ROM from the CD-ROM driv e.
7.  To close the OS/2 window, type EXIT 
and press .
8.  Restart the PC:
a.
  Click the right mouse button on an empty area of the OS/2 desktop and select
Shut down from the menu that displays.
b.
  W hen you are prompted whether you want to close all windows and activ e
programs, click OK.
c.
 When prompted to shut down or reboot, press  to restart the
PC.
Installing the Messaging System Software
Before you attempt to install the messaging system software, be sure to reference the
Release Notes included with this release for information on any special considerations
pertaining to installing system software.
To complete messaging system installation, you must know what type of v oice boards
are installed in the system PC. If you are not sure what type of v oice boards is installed,
contact a technical support representativ e before proceeding.
To install the messaging system software:
1.  Turn on the PC, if it is not already running. OS/2 boots and the OS/2 Program
Manager displays.
2.  Insert the messaging system CD-ROM in the CD-ROM driv e. 
						

							6. Installing the Software
Implementation and Service ManualInstalling the Messaging System Software6-7
3.  Open an OS/2 window.
4.  From the C: prompt, type F: 
and press .
5.  From the F: prompt, type CD VM 
and press .
6.  From the \VM directory prompt, type INSTALL 
and press . The message
“Setup is initializing, please wait” displays.
  Do not attempt installation from the full screen OS/2 window, because the
installation process will run in the background and the installation screens will not be
v isible to you. Consequently, you will not be able to follow the on-screen prompts for
entering information.
7.  A window displays, which briefly describes the installation procedure. To continue
installing, click Continue or press . The installation program presents a list of
driv es from which you can select.
 
8.  Select the driv e to which the files should be installed. Use the down arrow key to
highlight the appropriate driv e, then click OK. (Driv es A and B are disk driv es.) The
system prompts whether you want to install the system to the \CVR directory on the
specified installation driv e.
 
9.  Click Yes to install the system to the \CVR directory and continue the installation
process. If you click No, you are prompted to select a destination directory.
  To facilitate system maintenance, it is recommended that you do 
not change the
default installation directory. 
						

							6. Installing the Software
Implementation and Service ManualInstalling the Messaging System Software6-8
10.  W ait while the system prepares to load files. A dialog box with installation options
and space requirements displays. The Space Requirements section of the window
displays the disk space required, based on the selected options, the space
availability, and the installation and boot driv es.
 
11.  Under Installation Options, leav e all of the options selected:
· Program Files – Includes the executable files needed to run the messaging
system.
· Utilities – Contains the files necessary to run system modules, such as DialPlan
and Integrator.
12.  Under Voice Files, select the language(s) that you are installing. Note that the
sentinel attached to the messaging system PC controls the number of allowed
languages.
13.  Under Voice Driv ers, select the type of v oice board installed in the system PC from
the drop-down menu. For DIALOG/4 boards, select the Dialogic D41D, D42SL,
D42SX option.
14.  Under Serial Integrations, leav e at the default, None, if the system is not using serial
integration. If you are using serial integration, select the appropriate option from the
drop-down menu.
15.  Click Install to install the messaging system based on the selections.
  A small display appears to the left of the Disk Prompt window to show the
progression of the installation process. The graph represents the percent of hard
driv e space and memory being used, as well as the progression of each file as it is
copied to the hard driv e. If the Low icon comes on during installation, do not be
concerned. 
						

							6. Installing the Software
Implementation and Service ManualInstalling the Messaging System Software6-9
16.  After all of the files hav e been copied, the system loads the configuration, modifies
paths, and creates the desktop folder and program objects. The system then
prompts you to indicate whether you want the messaging system to launch
automatically upon bootup.
 
17.  Click Yes to configure the messaging system to launch each time you restart the PC.
18.  If you selected Yes in step 17, you are prompted to indicate whether you want the
UPS monitor to load automatically upon bootup. Select Yes if you are planning to
run UPS integration so the UPS monitors system status to recognize a potential
interruption in operation before it occurs. For additional information on the UPS
monitor, see Chapter 11, “Integrating with an Uninterruptible Power Supply.”
  Select No if you do not want the UPS monitor to load upon bootup.
  Programs that load prior to the desktop coming up under OS/2, such as UPS, display
a default OS/2 icon on the desktop rather than the custom icon.
19.  If you installed a serial integration, you are prompted whether you want the serial
integration to launch automatically on bootup. Click Yes.
20.  A dialog box displays when the installation is complete. Click OK to continue with
system configuration.
21.  The Installation Setup Utility dialog box displays a list of utilities you can run to help
you configure the messaging system:
· Configure – Unless the system has been preconfigured, you must run
Configure, so that the system recognizes the installed v oice and fax boards.
For information on running the Configure utility, see Chapter 7, “Setting Up
the System to Recognize Voice and Fax Boards.”
· Switch Integrator – Run Integrator to integrate the messaging system with
the phone switch installed at the customer site, unless the system was
preconfigured. For information on running the Integrator utility, see Chapter
8, “Integrating with the Phone System.”
· Dial Plan – You can run Dial Plan to identify the local area code and
associated prefixes. For information on running the Dial Plan utility, see
Chapter 12, “Determining Outdial Strings.”
· UPS – Run UPS if you are integrating with the UPS attached to the system
PC. Note that this requires a UPS with a serial connector. For information on
running the UPS utility, see Chapter 11, “Integrating with an Uninterruptible
Power Supply.”
· System Setup – Run System Setup to configure the messaging system on a
system lev el. For information on running the System Setup utility, see
Chapter 13, “Setting Up the System.” 
						

							6. Installing the Software
Implementation and Service ManualInstalling the Messaging System Software6-10
· Iconfig – If you installed a Serial integration, run the ICONFIG program. For
information on running the serial integration utility, see Chapter 10,
“Establishing a Serial Integration.”
 
  To run a utility, select it from the list and click the Run button. W hile you may access
these utilities from the program folder after installation, it is strongly recommended
that you run them now.
22.  After you run each utility, the Installation Setup Utility displays. You may select
another utility or click Done to exit the Installation Setup Utility dialog box. The
system displays a message when installation is complete and reminds you to restart
the computer for any changes to take effect.
23.  To close the dialog box and return to the OS/2 window, click OK.
24. Type EXIT 
then press  to close the OS/2 window.
25.  Remov e the CD-ROM.
26.  Restart the PC:
a.
  Click the right mouse button on an empty area of the OS/2 desktop and select
Shut down from the menu that displays.
b.
  W hen you are prompted whether you want to close all windows and activ e
programs, click OK.
c.
  W hen prompted to shut down or reboot, press  to restart the
PC. If you selected Yes in step 17 to launch the messaging system on bootup,
after the computer reboots, a Quick Assist screen briefly displays; then you are
prompted to run the Call Analysis utility. For additional information on running
call analysis, see Chapter 9, “Defining Phone System Signals.”
27.  Start the system, if it is not already running, by double-clicking the messaging
system icon in the program folder.
Do not reinstall the messaging software unless you are instructed to do so by a technical
support representativ e. If you are instructed to reinstall the system software for any
reason, you must follow the upgrade procedure instead of reinstalling the software.
Otherwise, you may lose current system settings. 
						

							6. Installing the Software
Implementation and Service ManualVerifying Files After Installation6-11
Verifying Files After Installation
After you complete system software installation, v erify that the STARTUP.CMD,
CONFIG.SYS, and RUNVM.CMD files are similar to the samples prov ided here. The
CONFIG.SYS file is located on the root of the C driv e, the RUNVM.CMD file is located in
the \CVR directory, and the STARTUP.CMD file is located in the OS/2 Startup folder.
Because systems and system setups v ary, the exact contents of the files shown may
v ary. If you hav e any questions about the contents of these files, contact a technical
support representativ e.
To open the STARTUP.CMD, CONFIG.SYS, and RUNVM.CMD files:
Before modifying any of these files, create a backup so that you can restore the original
file if necessary.
1.  If the messaging system is running, select Exit from the File menu to shut it down.
For information on logging into the system and shutting it down, see Chapter 20,
“Starting, Logging Into, and Shutting Down the System.”
2.  Open an OS/2 window.
3.  Open the file you want to rev iew:
·  To open STARTUP.CMD, from the C: prompt, type
E “ C:\DESKTOP\OS!2 SYSTEM\STARTUP\STARTUP.CMD”  
and press
. An OS/2 editor window displays the file.
·  To open CONFIG.SYS, from the C: prompt, type E CONFIG.SYS 
and press
. An OS/2 editor window displays the file.
·  To open RUNVM.CMD, from the C: prompt, type CD CVR 
and press 
to change to the \CVR directory prompt. From the \CVR prompt, type
E RUNVM.CMD 
and press . An OS/2 editor window displays the file.
4.  Insert any modifications where appropriate in the open file.
5.  If you made any changes, select Sav e from the File menu. If this is the first time you
hav e sav ed the file, the Sav e Notification dialog box displays.
6.  Click Type. The Type dialog displays.
7.  Click Plain Text, then click Set. The file is sav ed.
8.  Double-click the icon in the upper-left corner of the window to close the editor.
9.  To close the OS/2 window, type EXIT 
and press . 
						

							6. Installing the Software
Implementation and Service ManualVerifying Files After Installation6-12
Sample CONFIG.SYS File
Because the CONFIG.SYS file for OS/2 is quite lengthy, only the lines affected by the
system are shown here. The CONFIG.SYS file is stored in the root directory of the drive
on which the system is installed.
LIBPATH=.;C:\OS2\DLL;C:\;C:\OS2\APPS\DLL;C:\CVR
SET PATH=C:\OS2;C:\OS2\SYSTEM;C:\C:\OS2\INSTALL;C:\CVR
FILES=20
BUFFERS=30
DEVICE=C:\CVR\OS2SNTNL.SYS
For Dialogic only:
SET DLCFGPATH=C:\CVR
SET DLFWLPATH=C:\CVR
SET TSTDIR=:C\CVR
SET SCTXTS_REQ=C:\CVR\SCTXTS.REQ
DEVICE=C:\CVR\GENLOAD.SYS
DEVICE=C:\CVR\DXSRM.DAM
DEVICE=C:\DXGENDRV.SYS
CALL=C:\CVR\SCTSMAP.EXE
For Brooktrout only:
DEVICE=C:\BFAX.SYS D1 I10
CALL=C:\FAXINIT.EXE
CALL=C:\FIRMWARE -D C:\TR114.PEX
Sample STARTUP.CMD File
If during installation you selected the option to start the messaging system automatically
upon bootup, the STARTUP.CMD file is executed each time the system reboots, similar
to the AUTOEXEC.BAT file in a DOS env ironment. W hen it loads, STARTUP.CMD first
checks the PLUS.CKP file to determine if there was a power failure. If so, Quick Assist
runs in Update Partial mode, and any unattached messages are deleted. Then, if it has
not yet been run, Call Analysis launches. Next, the UPS.EXE monitoring program
executes (prov ided that, during installation, you selected it to run automatically) and runs
in the background to monitor for power out conditions. Finally, the file that loads the
messaging, RUNVM.CMD, is executed.
The STARTUP.CMD file is stored in the OS/2 Startup folder.
C:
CD\CVR
IF EXIST C:\CVR1\PLUS.CKP CALL C:\CVR\QASSIST –A -D
IF EXIST C:\CVR\FIRST.CA CALL C:\CVR\RUNCA.CMD
START /PM /MIN UPS.EXE
START /MIN RUNVM.CMD
EXIT
See the topic, “Running Quick Assist as Part of Routine System Maintenance,” in
Chapter 23, “Maintaining the System,” for information on the parameters that can be
included in the Quick Assist command line. 
						

							6. Installing the Software
Implementation and Service ManualVerifying Files After Installation6-13
Sample RUNVM.CMD File
The RUNVM.CMD file, located in the \CVR directory, is the file that launches the system.
:START
START /C /MIN SMDI.EXE 
(only if using SMDI)
CALL START /MIN RUNVFS.CMD 
(only if using Visual Mailbox)
CALL CALLPERF PLUS
IF ERRORLEVEL == 64 GOTO ERRORLOG
IF ERRORLEVEL == 50 GOTO DOW
GOTO END
:DOW
APFR
ALLDAY
IF ERRORLEVEL==7 GOTO SAT
IF ERRORLEVEL==6 GOTO FRI
IF ERRORLEVEL==5 GOTO THURS
IF ERRORLEVEL==4 GOTO WED
IF ERRORLEVEL==3 GOTO TUE
IF ERRORLEVEL==2 GOTO MON
IF ERRORLEVEL==1 GOTO SUN
GOTO START
:SUN
ECHO TODAY IS SUNDAY
REM REFRESH
CALL LOGPURGE
GOTO START
:MON
ECHO TODAY IS MONDAY
REM REFRESH
CALL LOGPURGE
CALL C:\GU20\GU.CMD 
(example of third-party Graham Utilities option)
GOTO START
:TUE
ECHO TODAY IS TUESDAY
REM REFRESH
CALL LOGPURGE
GOTO START
:WED
ECHO TODAY IS WEDNESDAY
REM REFRESH
CALL LOGPURGE
GOTO START
:THURS
ECHO TODAY IS THURSDAY
REM REFRESH
CALL LOGPURGE
GOTO START
:FRI
ECHO TODAY IS FRIDAY
REFRESH
CALL LOGPURGE
GOTO START
:SAT
ECHO TODAY IS SATURDAY
REM REFRESH
CALL LOGPURGE
GOTO START
:ERRORLOG
ECHO | DATE >> RUNVM.LOG
ECHO | TIME >> RUNVM.LOG
ECHO ERRORLEVEL IS 64 OR GREATER >> RUNVM.LOG
:END
EXIT 
						

							6. Installing the Software
Implementation and Service ManualVerifying Files After Installation6-14
W hen the system launches, the RUNVM.CMD file monitors for error codes. If the
RUNVM.CMD receiv es an error code 50, indicating shutdown based on the System
Setup parameter Shutdown System after Daily Maintenance, control is passed to the
DOW  label (Day of W eek routines). The ALLDAY program determines the day of the
week, and control is then passed to the appropriate label in the file. Under these labels,
you can run other programs, such as a disk maintenance utility. For example, in the
sample RUNVM.CMD file, the third-party Graham Utilities program is run Monday
morning. After any specified utilities run, control is returned to the top of the file, and the
system relaunches.
If you are running the UPS Monitor utility, and it detects an error code 15 (low battery),
control drops to the :END label, and the system goes through a shutdown, where both
idle and occupied ports are immediately disabled. W hen the UPS determines that the
power has been restored, the UPS.EXE program calls RUNVM.CMD, which restarts the
system.
The following command line options can be added to the CALL CALLPERF PLUS
command line in the RUNVM.CMD file:
-SX Specifies that the system is using D/42-SX (or equiv alent) v oice boards. -SX
can be used only with Mitel SX Series systems that hav e the special
integration Dialogic boards.
Example:  CALL CALLPERF PLUS -SX
-SL  Specifies that the system is using D/42-SL or D/42-NS (or equiv alent) v oice
boards. -SL can be used only with Northern Telecom SL Series systems or
Norstar systems that hav e the special integration Dialogic boards. This
option should also be used with the 1005 software on the Mitel SX200 Light
switch.
Example:  CALL CALLPERF PLUS -SL
-NS Specifies that the system is using D/42-NS (or equiv alent) v oice boards. -NS
can be used only with Norstar systems that hav e the special integration
Dialogic boards.
Example:  CALL CALLPERF PLUS -NS