Lucent Technologies Octel 100 Implementation And Service Manual

							23. Maintaining the System
Implementation and Service ManualPerforming System File Maintenance23-13
V-Tree mailboxes that do not hav e greetings or messages associates with them will not
be rebuilt.
If possible, the system restores the following information to the rebuilt mailboxes:
· Greetings – name prompt, optional prompts, personal greeting.
· Mailbox information – first and last name, extension, company, div ision, class
of serv ice number or custom class of serv ice, personal operator.
· Mailbox settings – activ e call-handling options, message notification entries,
primary fax destination, follow-me-forward destination, V-Tree, folders.
If the system cannot restore this information, it returns the mailboxes to the system
defaults, and you must manually edit the mailboxes to reenter the settings.
Messages are affected as follows:
·  All message pointers are re-indexed and placed in their respectiv e mailboxes’
new message queue.
·  Messages sent to a group list are only retained in the first recipient’s mailbox.
·  Messages that were copies of messages sent from another subscriber are not
replaced.
·  Comments attached to messages are treated as separate messages.
The following information is not restored during a rebuild all operation:
·  Outbound ev ents, such as message notification ev ents and message indicator
ev ents.
·  Distribution lists.
·  Message confirmation data.
If a mailbox’s message indicator is on when rebuild mode is run, the mailbox must go
through a complete message cycle (indicator activ ation and deactiv ation) before the
indicator is synchronized.
To rebuild system mailboxes:
1.  If the messaging system is running, select Exit from the File menu to shut it down.
2.  Double-click the QASSIST icon in the program folder. The Quick Assist dialog box
displays.
  
						

							23. Maintaining the System
Implementation and Service ManualPerforming System File Maintenance23-14
3.  Click Recov er Files. The Recov er Files dialog box displays.
 
4.  In the Driv e where \cv r1 files are located field, v erify the driv e displayed in the field
is the driv e where the \CVR1 directory is located.
5.  Under Recov ery Mode, select the Rebuild (all boxes) option.
6.  In the Mailbox to receiv e unattached messages field, enter the mailbox in which you
want the system to place messages with inv alid header information. Unattached
messages with v alid header information are placed in the new message queue of the
receiv ing mailbox.
7.  Under Recov ery Options, select the Ask before creating a mailbox option if you want
the system to prompt you for confirmation before it creates mailboxes. The system
creates mailboxes when it finds messages or greetings that are linked to a mailbox
number that does not exist. If you deselect this option, the system automatically
creates the mailboxes indicated by the message or greeting links.
8.  In the Report Filename field, enter the name of the report you want the system to
generate, if you do not want to accept the default QASSIST.RPT.
9.  Under Report Options, select the Send to File option if you want to create a report
file. W hen you select this option, the system creates a report with the specified
filename in the \CVR1 directory. If you deselect this option, the report is only
av ailable by selecting the View Report option.
10.  To begin the rebuild, click Start. A confirmation dialog box displays.
11.  To confirm that you want to start the rebuild, click OK. The Recov er Status dialog
box displays.
  
						

							23. Maintaining the System
Implementation and Service ManualPerforming System File Maintenance23-15
  The system copies the \CVR1 directory into a directory named \~REPAIR~. Do not
delete the files from the \~REPAIR~ directory until you are confident the system has
corrected any file damage.
12.  The Searching Directory and Processing Mailbox fields display the directory and
mailbox currently being processed. The Errors and W arnings fields reflect the
respectiv e number of errors and warnings the system encounters during the update.
13.  W hen the rebuild is complete, you can click Edit Mailboxes to reenter or modify
information that may hav e been lost. The Mailbox Quick Edit dialog box displays
with information for the first mailbox.
 
  This dialog box includes general identification information about each system
mailbox, including the First and Last Name, Company, and Div ision. The Messages
box displays the number of recov ered New and Sav ed messages.
  You can click the Next and Prev ious buttons to mov e through the mailboxes. Click
Sav e to sav e any edits you make. W hen you finish making any edits, click OK to
return to the Recov er Status dialog box.
14.  Click OK. The Recov er Files dialog box displays.
15.  To display the report, click View Report. If the system detected errors or warnings
during the update, the appropriate correctiv e action is suggested in the report.
16.  W hen you finish v iewing the report, click the window icon in the upper-left corner
and select Close. The Recov er Files dialog box displays.
17.  Click Cancel. The Quick Assist dialog box displays.
18.  To close Quick Assist, click Exit.
Running Quick Assist as Part of Routine System Maintenance
A Quick Assist execute command is located in the STARTUP.CMD file. The
STARTUP.CMD file is run each time the system is launched if, during system
installation, you selected the option to launch the system automatically upon bootup.
W hen included in a batch file such as STARTUP.CMD, Quick Assist checks the
PLUS.CKP to determine if an abnormal program termination, such as a power failure,
has occurred:
·  If no abnormal termination occurred, Quick Assist does not run.
·  If an abnormal termination is detected, the specified Quick Assist mode runs. 
						

							23. Maintaining the System
Implementation and Service ManualPerforming System File Maintenance23-16
The default Quick Assist execute command in the STARTUP.CMD file (QASSIST -A -
D
) runs the following automatic power failure recov ery procedures:
1.  Quick Assist runs in Update (partial) mode. If successful, the system is
launched.
2.  If there are problems that Update (partial) cannot correct, a dialog box displays
prompting whether you want to continue. To abort the recov ery procedure, click
No. To proceed with the recov ery procedure, click Yes. If a selection is not made
within one minute, the recov ery procedures automatically begin.
3.  During recov ery, the contents of the \BACKUP1 directory are copied to the
\CVR1 directory. The backup database directories are created during the
shutdown for daily maintenance. If the Shutdown System After Daily
Maintenance parameter on the General Parameters tab in System Setup is
disabled, or the files in the \BACKUP1 directory are more than two days old, the
contents are not copied to the \CVR1 directory, the recov ery process halts, and
the system launches using the existing database.
Note that changes made to the database since the last backup, such as class of
serv ice modifications, are not retained.
4.  Quick Assist is then run again in Update Partial mode with the backup database.
If successful, the system is launched using the restored database.
5.  If the detected problems are not corrected, Quick Assist is run in Update All
mode. If the Update All is successful, the system is launched using the restored
database.
6.  If the detected problems cannot be corrected automatically, the system
relaunches using the restored database, and an entry is written to the log file.
You must manually run Quick Assist in Rebuild (all boxes) mode to attempt to
correct the detected problems.
If the v oice mail system does not start automatically upon bootup, you can modify
the RUNVM.CMD file to include a Quick Assist execute command. For further
information, contact a technical support representativ e.
You can edit the STARTUP.CMD file to specify the Quick Assist mode you want to run if
the system detects an abnormal termination. The following parameters determine the
Quick Assist mode:
-B0
Verify
-B1
Update (Partial)
-B2
Update (All Boxes)
-B3
Rebuild (All Boxes)
-A
Automatic Power Failure Recovery
You may also include the following Quick Assist command line options when specifying
the repair method:
-D
Delete unattached messages
-I
Always run the specified Quick Assist mode on bootup, regardless of
whether a power failure is detected 
						

							23. Maintaining the System
Implementation and Service ManualPerforming System File Maintenance23-17
-MnSpecifies the mailbox to receiv e unattached messages
For example, the command QASSIST-A -D 
(which is the default Quick Assist
command used in the STARTUP.CMD file) instructs the system to run Quick Assist in
Update (partial) mode when a power failure has occurred and to delete any unattached
messages. The sample command C:\QASSIST -B1 -I -M2500 
instructs the system
to run Quick Assist in Update (partial) mode at ev ery bootup and to place any
unattached messages in mailbox 2500. Make sure that the mailbox you specify to
receiv e unattached messages exists. If you do not specify a mailbox in which to place
unattached messages, the system creates a mailbox and assigns it the last av ailable
mailbox number. For example, on a system with three-digit mailboxes, the last mailbox
is 999. For security reasons, it is recommended that you always use the M
n parameter
for running Quick Assist in a batch file.
To modify the Quick Assist command in the STARTUP.CMD file:
1.  If the messaging system is running, select Exit from the File menu to shut it down.
2.  Open an OS/2 window.
5.  From the C:\ prompt, type
E “ C:\DESKTOP\OS!2 SYSTEM\STARTUP\STARTUP.CMD 
and press .
The contents of the file are displayed in an OS/2 editor window.
3.  Mov e to the line that includes the Quick Assist execute command QASSIST -A -
D
. Modify the line to include the repair mode and any options that you want Quick
Assist to run.
4.  From the File menu, select Sav e.
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. Type EXIT 
and press  to close the OS/2 window. 
						

							23. Maintaining the System
Implementation and Service ManualRunning the Lister Utility23-18
Running the Lister Utility
The Lister utility allows you to view the contents of files on the PC. This utility is useful
for rev iewing system files, such as RUNVM.CMD or SET_UP.CFG.
To run the Lister utility to view the contents of a file:
1.  If the messaging system is running, select Exit from the File menu to shut it down.
2.  Double-click the Listen icon in the program folder. The Specify Parameters dialog
box displays.
 
3.  In the field, enter the path, filename, and extension of the file you want to v iew. For
example, to v iew the SET_UP.CFG file, type C:\CVR1\SET_UP.CFG
.
4.  Click Open. The system displays a window containing the specified file. Use the
scroll bars if necessary to v iew the entire contents.
 
5.  W hen you finish v iewing the file, double-click the icon in the upper-left corner of the
window. 
						

							23. Maintaining the System
Implementation and Service ManualAdding Modules and Ports to a System23-19
Adding Modules and Ports to a System
You can purchase optional modules and additional ports to upgrade a system at any
time. The sentinel unit attached to the PC’s parallel port controls access to port licenses
and optional modules such as AMIS.
W hen you purchase additional port licenses or optional modules, you receiv e a disk
containing a utility that upgrades the system’s sentinel protection dev ice to support the
utilities or ports purchased. This sentinel upgrade utility eliminates the need for you to
RMA the current sentinel in exchange for a new one each time you purchase an
upgrade.
Be aware of the following issues before installing the upgrade disk:
·  The data file prov ided in the sentinel upgrade is keyed to work exclusiv ely on the
system sentinel assigned the serial number specified when you ordered the
upgrade. A separate sentinel upgrade disk, therefore, must be used for each
system.
·  W hen the upgrade utility executes, it reads the system’s sentinel. It then checks
both the serial number and the current sentinel settings against the data file on
the disk. If the settings do not match, the error message, “Inv alid data file for this
sentinel,” is written to a file named ERROR.LOG on the disk and the upgrade
process is terminated. If this occurs, call a technical support representativ e
immediately. If the upgrade process is terminated, you will still be able to run the
system using the prev ious v ersion—neither the sentinel nor the system is
disabled.
·  The sentinel for which the upgrade was ordered should be the only sentinel
attached to the system. Any attempt to upgrade multiple sentinels at the same
time will result in the additional sentinels being disabled.
To perform the sentinel upgrade:
1.  If the messaging system is running, select Exit from the File menu to shut it down.
2.  Insert the upgrade disk in the A: driv e.
3.  Open an OS/2 window.
4.  At the C: prompt, type A: 
and press .
5.  At the A: prompt, type SUU 
and press .
6.  W hen the upgrade procedure is finished, the message, “Sentinel upgrade complete,”
displays. Restart the software and test the new features or ports to ensure they are
av ailable. 
						

							23. Maintaining the System
Implementation and Service ManualVerifying File Version Information23-20
Verifying File Version Information
The Check Version utility provides a convenient method of determining the exact v ersion
number and date of any of the v oice mail system’s *.EXE, *.DLL, or *.P files. Knowing
which file v ersions the system is running allows you to determine whether newer files are
av ailable and helps technical support representativ es serv e you more efficiently. Check
Version can only be used for modules dev eloped for the system; it cannot be used on
third-party utilities such as RSM.
To run the Check Version utility:
1.  Double-click the Check Version icon in the program folder. The utility reads the
ORIGINAL.REG file from the \CVR directory. This file contains information such as
last modified date, size, description on the v oice mail system’s *.EXE, *.DLL, and *.P
files as they were when you originally purchased the system.
2.  If this file is not found, the utility displays an error message informing you that it
cannot open the ORIGINAL.REG file, and the utility is not run. Click OK to close the
dialog box. If you encounter this error message, contact a technical support
representativ e.
3.  The utility checks each of the files listed in the ORIGINAL.REG file to the files in the
\CVR directory. If a file listed in ORIGINAL.REG cannot be found, a dialog box
displays the name of the missing file. Click OK to continue or Cancel to abort the
utility. If you encounter a missing file error, contact a technical support
representativ e.
4.  The utility obtains the system’s serial number from the sentinel. If a sentinel is not
found, an error message displays. Click OK to continue the Check Version utility.
The Check Version dialog box displays any updated files the utility found are listed,
along with each file’s last modified date, file size, v ersion number, and description.
 
5.  If updated files are found and you want to sav e the report to a file, click Sav e. A
dialog box displays for you to specify a destination to which to sav e the file. Specify
a destination for the file, then click OK.
6.  If updated files are found and you want to print the report to the system PC’s
attached printer, click Print. A dialog box displays confirming that the file has been
sent to the printer. Click OK to close the dialog box.
7.  Click Exit to close the Check Version utility. 
						

							23. Maintaining the System
Implementation and Service ManualRefreshing Message Indicators23-21
Refreshing Message Indicators
The Messaging Indicator Refresh utility updates or resets the message indicators for all
or specified mailboxes. This utility is useful in situations where message indicators have
been reset (for example, after a switch upgrade or a switch hardware replacement).
WARNING:You should only run this utility under the circumstances described above,
where all of the message indicators have been reset. It is strongly
recommended that you not run this utility under other circumstances, as
this may cause adverse reactions, depending on the switch.
To run the Message Indicator Refresh utility:
1.  If the messaging system is currently running, select Exit from the File menu to shut it
down.
2.  Open an OS/2 window.
3.  From the C: prompt, type C:\CVR\REFRESH 
and press . The system
displays the results onscreen. The results are also copied to a REFRESH.LOG file in
the \CVR1 directory.
4.  To close the OS/2 window, type EXIT 
and press .
The following command line options are av ailable for the Message Indicator Refresh
utility.
Command Usage
REFRESH
Refreshes message indicators for all
mailboxes.
REFRESH –I
Runs the utility in Information mode. In this
mode, the utility lists the message indicator
ev ents that are currently scheduled and
prov ides message indicator information for
each mailbox, including the current
messaging indicator status.
REFRESH –N 
Refreshes message indicators for the
mailbox specified after the –N
 command.
For example, typing
REFRESH –N 1001 
will refresh mailbox
1001.
REFRESH –NN 
Refreshes message indicators for the range
of mailboxes specified after the –N
command. For example, typing
REFRESH –NN 1001-1020 
refreshes
mailboxes 1001 through 1020.
-E
W hen inserted after one of the commands,
the utility runs without deleting and re-
creating the message indicator ev ents
currently scheduled. 
						

							23. Maintaining the System
Implementation and Service ManualProtecting Your System23-22
Protecting Your System
Voice messaging toll fraud has risen dramatically in recent years. Now more than ev er, it
is imperativ e that you take steps to secure your system. Callers into the v oice
messaging/automated attendant system may transfer to an outgoing trunk if adequate
security measures are not implemented. Callers who hav e unauthorized access to a
v oice mailbox can use it as a message drop for communications at your expense on
your 800 numbers. Securing your system means protecting the switch, protecting the
v oice messaging system, and protecting any automated attendant applications.
Please rev iew and implement, as appropriate, the following security measures to:
·  Prev ent callers from transferring to extensions not assigned system mailboxes
·  Impede callers from gaining access to the Quick Assist maintenance mailbox
·  Assign randomly generated passwords to system mailboxes
·  Require passwords at least one digit longer than mailbox numbers
·  Require subscribers to regularly change their passwords
·  Monitor uninitialized mailboxes
·  Use extended password security
·  Prov ide notification of unsuccessful mailbox login attempts
·  Lock subscriber mailboxes after unsuccessful login attempts
·  Monitor unsuccessful login attempts
·  Hav e subscribers record their Name prompts
·  Delete unused mailboxes immediately
·  Require callers to enter passwords to proceed in V-Trees
·  Secure the system PC
· Utilize phone system security features
·  Use superv isor passwords to restrict system management access
·  Use the Auto Logoff feature to restrict system management access
It is recommended that these security features be rev iewed and implemented as
appropriate. A Security Checklist is prov ided at the end of this section to help you
implement these features.
Preventing Callers from Transferring to Extensions Not
Assigned System Mailboxes
On some phone systems, callers can transfer to a system extension and then use that
extension to access an outside line. This is most relev ant for system ports used for
outcalls for networking or message notification to a beeper. By prev enting callers from
accessing system extensions not assigned system mailboxes, you can substantially
reduce the risk of outside callers accessing an outside line.
The parameters on the Inv alid Mailbox tab in System Setup can prev ent callers from
accessing non-assigned extensions for this purpose:
·  Transfer Inv alid Mailboxes During Hours
·  Transfer Inv alid Mailboxes After Hours