DEC VOICE:mail for OpenVMS VAX Installation Guide Order Number: AA-PZP7B-TE November 1995 This document contains instructions for installing VOICE:mail on the OpenVMS operating system. It applies to VOICE:mail Version 2.0 and all maintenance updates throughout that version. Revision/Update Information: This is a revised document. Operating System and Version: OpenVMS Version 5.5 and above Software Version: VOICE:mail Version 2.0 Digital Equipment Corporation Maynard, Massachusetts November 1995 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. c Digital Equipment Corporation 1995. All Rights Reserved. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DECvoice, OpenVMS, VAX, and the DIGITAL logo. The following are third-party trademarks: VOICE:mail is a trademark of VOICEsoft Corporation. Touch-Tone is a trademark of American Telephone and Telegraph. Contents Preface vii Preinstallation Requirements 1-1 Hardware Requirements 1-1 Software Requirements 1-1 Modifying System Parameters 1-2 Check SYSGEN Parameters 1-2 Modifying SYSGEN Parameters 1-4 Configuration Sheet 1-5 VOICE:mail Installation 1-5 VCSI$LOGICALS.COM Values 1-6 Int_Setup.Com 1-6 Set Up Terminals: 1-6 Set Up Channels: 1-6 Running DECvoice V2.2/V2.3 Configuration 1-7 Resource Names 1-7 List of Services to be Allocated 1-7 DTC05-Configuration 1-7 Installing VOICE:mail 2-1 Upgrading VOICE:mail 2-1 VMSINSTAL 2-3 Postinstallation Configuration 3-1 Modifying VCSI$LOGICALS.COM 3-1 Logical Name Table 3-2 Directory Location of Files 3-2 Adding Data Disk Labels 3-3 New Directory Structure Option. 3-4 VOICE:Servers 3-5 Process counts per node 3-6 Disk Space Monitoring 3-8 Envelope Presentation 3-8 DECvoice Software Resource 3-8 Message Notification Redial Specifiers 3-9 iii Call Transfer Sequences 3-9 From DECvoice Manual: 3-9 Internal Call Transfer Logicals 3-10 External Call Transfer Logicals 3-12 Message Waiting Indicator Sequences 3-13 Modem MWI Logicals 3-14 DTMF MWI Logicals 3-14 Setting Hook Flash Length 3-14 Printing from VOICE:menu 3-15 Additional Logical Definitions 3-15 INT_SETUP.COM 3-17 Lock Integration Terminal Port 3-20 VOX$CONFIG.COM 3-20 Setting the T1 Framing 3-21 Location of Hardware 3-21 Outgoing Lines 3-22 Incoming Lines 3-22 Define DTC05 Line Mode 3-23 Changing Resource Names and Signaling 3-24 Printing from VOICE:menu 3-25 Installation Verification Procedure 4-1 New Directory Structure Option. 4-1 Process Verification 4-3 Mailbox Verification 4-5 VOICE:environment Verification 4-5 Integration Verification 4-6 MWI Verification 4-7 Installation Checklist A-1 Power Requirements A-2 Grounding Requirements A-2 Miscellaneous Equipment A-2 Integration Protocol A-2 Channel Bank A-2 Hardware Connections A-3 VOICE:mail Line Verification A-3 VOICE:mail Installation A-3 VOICE:mail Initial Setup A-3 Post installation requirements. A-4 Loading the LMF PAK B-1 Sample Installation Log File C-1 iv Preface The VOICE:mail system was designed in accordance with all current voice messaging industry standards, including the March 1990 Specification Document adopted by the Voice Messaging User Interface Forum (VMUIF). VMUIF is a voluntary association of organizations in the voice messaging industry, under the sponsorship of the Information Industry Association (IIA). VMUIF has developed a series of recommendations to standardize the way that voice mail systems interact with people. The VOICE:mail product fully conforms to the VMUIF design specifications. About This Guide This document describes how to install DEC VOICE:mail for OpenVMS VAX Version 2.0 on the OpenVMS operating system. It is intended for use by the System Manager or anyone else who installs DEC VOICE:mail for OpenVMS VAX Version 2.0 software. Keep this guide with your distribution kit. You will need it to install maintenance updates or to reinstall DEC VOICE:mail for OpenVMS VAX Version 2.0 for any reason. Structure of This Guide Chapter 1, Pre-installation Requirements, describes the hardware and software required to use VOICE:mail. It also explains how to modify system parameters. v Chapter 2, Installing DEC VOICE:mail, provides the installation procedure for VOICE:mail. Chapter 3, Post-installation Configuration, explains how to modify VOICE:mail files for your specific system needs. Chapter 4, Installation Verification Procedure, verifies that the VOICE:mail software is installed and functioning properly. Appendix A, Installation Checklist, is used to verify the correct installation and operation of the VOICE:mail software and associated hardware components. Appendix B, Loading the LMF PAK, gives a step-by-step description of how to load the LMF PAK. This must be done before starting or restarting VOICE:mail. Appendix C, Sample Installation Log File, shows a log file of an actual installation of VOICE:mail. You can use this as a guide to what you should see if you install VOICE:mail correctly. VOICE:mail Information Set The DEC VOICE:mail for OpenVMS VAX documentation set consists of the following documents: o DEC VOICE:mail for OpenVMS VAX Pocket Reference Card _ A simplified guide to using the major functions of VOICE:mail. o DEC VOICE:mail for OpenVMS VAX User's Guide _ A non- technical reference manual and tutorial designed to help users open and set up their Mailbox and use all the functions and features of the system. o DEC VOICE:mail for OpenVMS VAX Telephone Attendant's Guide _ A non-technical guide to help the telephone attendant or operator learn how to transfer calls with VOICE:mail and use the General Delivery Mailbox. vi o DEC VOICE:mail for OpenVMS VAX Administrator's Guide _ A guide to help the VOICE:mail Administrator design and manage the VOICE:mail system. o DEC VOICE:mail for OpenVMS VAX Installation Guide _ A guide to installing VOICE:mail including pre- and post- installation requirements. o DEC VOICE:mail for OpenVMS VAX System Manager's Guide _ A guide to the hardware and software configuration requirements for VOICE:mail, and use of the diagnostic utilities. o DEC VOICE:mail for OpenVMS VAX Utilities Reference Manual _ A reference for using the Digital Command Language to manage the VOICE:mail system, including creating Mailboxes and converting ASCII text to voice segment files for voice synthesis. Conventions o Italicized type _ Indicates prompts that you will hear as you use VOICE:mail. o BOLD ITALIC _ Indicates commands or responses that you type. Unless otherwise stated, press Return after each command or response. o Bold centered _ Indicates prompts and messages from the computer. o lowercase text in a function call, or in a DCL command or command procedure _ Indicates that you substitute a valid expression in that place. o [ ] _ Indicates brackets are used after installation questions to enclose the default answer. Press Return to accept the default value. o 1, 2, 3 _ Indicates the order of the steps you must follow to complete a procedure. o a) b) c) _ Indicates steps within a major step in a procedure. vii o Press _ Indicates that you should make one keystroke with an editing or command key. For example, press Return. o Type _ Indicates characters that you type from the keyboard. Entering Commands DCL commands should be entered on a single line, even if shown as two lines in this manual due to page size limitations. If it is necessary to continue a long command on a second line, DCL requires a hyphen [-] at the end of the first line. viii 1 Preinstallation Requirements VOICE:mail for OpenVMS VAX is shipped on one TK50 tape. The tape label indicates the version and release number preceded by VCSI. For example, VCSI V02.1 indicates Version 2, Release 1. Hardware Requirements Following are the basic hardware requirements to run VOICE:mail: o VAX System: - VAX System 4000 series. - VAX System 3000 series. - MicroVAX: - MicroVAX 3800 and MicroVAX 3900 o VAXserver: - VAXserver 3800 and 3900 - VAX server 4000: Models 200, 300, 500, 700 o DECvoice-T1 DTCN5 Telephony Module o DECvoice DTC05 multi-line voice boards, one per eight ports Software Requirements 1-1 Following are the basic software requirements to run VOICE:mail: o OpenVMS, Versions 5.5-1 or higher o DECvoice Software, Version 2.2 or higher Modifying System Parameters If you need to change the values for the system parameters, change them before you install VOICE:mail. Otherwise, the installation will fail. Modify these parameters in the SYS$SYSTEM:MODPARAMS.DAT file and run AUTOGEN as described later in this section. You must also set the parameter "Maximum Links" to at least 2000 in the NCP (Network Control Program) database as described later in this section. The system pagefile size should be at least 150,000. To check the pagefile size, type: $ SHOW MEM At the bottom of the display, the total size of the pagefile will be displayed. If this value is less than 150,000, then extend the pagefile size by typing: $ @SYS$UPDATE:SWAPFILES Enter 150,000 for the new pagefile size. The system will have to be rebooted to recognize the extended pagefile. Check SYSGEN Parameters Ensure that the SYSGEN parameters for VOICE:mail are set to allow sufficient values for the installation. Table 1-1 shows minimum values applicable to each parameter for VOICE:mail. If you also are running VOICE:attendant, add an additional 40,000 to the values shown for GBLPAGES and GBLPAGFIL. 1-2 Table 1-1 Minimum Parameter Values Parameter Value GBLSECTIONS 400 GBLPAGES 40000 GBLPAGFIL 45000 MAXBUF 8192 RMS_DFMBFIDX 2 CHANNELCNT 1024 To determine the current settings for the SYSGEN parameters: Log in to the SYSTEM account. Invoke the SYSGEN utility by typing: $ RUN SYS$SYSTEM:SYSGEN To ensure that you retrieve values from the current system parameter file on disk, use the command: SYSGEN> USE CURRENT Type the following command to determine the quota available for the global sections: SYSGEN> SHOW GBLSECTIONS Make a note of the current value. Type the following command to determine the quota available for the global pages: SYSGEN> SHOW GBLPAGES Make a note of the current value. Type the following command to find out the quota available for the global page file: SYSGEN> SHOW GBLPAGFIL Make a note of the current value. 1-3 Type the following command to find out the quota available for maximum buffers: SYSGEN> SHOW MAXBUF Make a note of the current value. Type the following command to find out the quota available for RMS multibuffer count for indexed sequential disk operations: SYSGEN> SHOW RMS_DFMBFIDX Make a note of the current value. Type the following command to find out the quota available for Channel Count for process limits on creating connections to other processes: SYSGEN> SHOW CHANNELCNT Make a note of the current value. To exit from SYSGEN, type: SYSGEN> EXIT Next, you will need to find out how many Global Pages and Global Sections are in use on your system by using the Install utility. Type the following command to list the global sections that are in use on your system: $ INSTALL LIST/GLOBAL/SUM This displays the number of Global Sections and Global Pages used. Subtract these values from the values obtained from the SYSGEN utility. If you do not have at least 250 free Global Sections and 25,000 Global Pages remaining, you must modify either or both the GBLSECTIONS and GBLPAGES parameters to give the required quota, as described later in this section. Also, the value for GBLSECTIONS must be at least 250, and the value for GBLPAGES must be at least 25,000, regardless of how many are actually free. 1-4 If any of your SYSGEN values are not adequate, modify the parameters as described in the following section. Modifying SYSGEN Parameters To modify the value of all these parameters, edit the file SYS$SYSTEM:MODPARAMS.DAT to include the following lines: MIN_GBLSECTIONS = gblsections_value MIN_GBLPAGES = gblpages_value MIN_GBLPAGFIL = gblpagfil_value (45000) MIN_RMS_DFMBFIDX = rms_dfmbfidx_value (2) MIN_MAXBUF = maxbuf_value (8192) Edit the file to ensure that the system has at least the minimum values specified in Table 1-1. Digital also recommends that the following lines be added to the modparams.dat file: PAGEFILE = 0 SWAPFILE = 0 This will prevent the system from automatically resizing these files. Now run AUTOGEN to recalculate your system parameters. First ensure that there are no active users on the system, using the following command: $ SHOW USERS/FULL Ask the users currently on the system to log out, and disable further logins by typing: $ SET LOGINS/INTERACTIVE=0 $ REPLY/BELL/ALL "PLEASE LOG OUT" Type the following to recalculate your system parameters: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK 1-5 Modification of the current system parameters does not immediately affect the system. AUTOGEN performs an automatic shutdown and reboot when it has finished to activate the new parameters. Once the system is up, you will then need to set the "Maximum Links" parameter in NCP. To accomplish this, do the following: Invoke NCP by typing the following: $ RUN SYS$SYSTEM:NCP Check the "Maximum Links" parameter by typing the following: NCP> SHOW EXECUTOR CHARACTERISTICS A list of parameters will appear on the screen. The Maximum Links parameter is about the eighth one from the top. Make a note of this number. Reset the Maximum links parameter if it is less than 2000 by typing the following two entries: NCP> DEFINE EXECUTOR MAXIMUM LINKS 2000 NCP> SET EXECUTOR MAXIMUM LINKS 2000 NCP> EXIT Configuration Sheet This Configuration Sheet will help you define various items of each section of the installation procedure before attempting the installation. Entries shown in bold face type are the system defaults. To accurately complete this Configuration Sheet, Digital recommends that you read the VOICE:mail for OpenVMS VAX System Manager's Guide. VOICE:mail Installation o Node names___________________________________________ o Data disk name_______________________________________ 1-6 o Data disk name 2_____________________________________ o System disk name_____________________________________ o VM_Manager UIC (577,001)_____________________________ o VM_Manager password__________________________________ o VM_Service UIC (577,002)_____________________________ o VM_Service password__________________________________ o VM$Server UIC (576,003)______________________________ o VM$Server password___________________________________ o Number of ports______________________________________ VCSI$LOGICALS.COM Values o Number of VOICE:mails (1 per VOICE:mail port)______________________________ o Number of Port managers (1 per 6 VOICE:mail ports)___________________________ o Number of File Server Remotes (2 per 24 VOICE:mail ports)__________________________ o Number of message notification outdialers (0-4 based on planned use of message notification)___ o Number of DTMF integration MWI dialers (0-3 based on MWI capable extensions; 0 for SMDI or SID)__ o Number of modem integration MWI dialers (0 for SMDI)__________________________________________ o VPR Max Sleep Time (120)______________________________ o VPR Time Detect (35)__________________________________ o VPR Time Increment (5)________________________________ 1-7 o Disk Warning Percent (10)_____________________________ o Disk Limit Percent (1)________________________________ o Envelope Presentation = Combine: 1=Name, 2=Time, 3=Date_______________________ o DECvoice Software (VOX)_______________________________ o Program_1 VOICE_MAIL_________________________________ o MN Pager Redial frequency (minutes: 15, 15, 15)_______ Int_Setup.Com Set Up Terminals: o VAX Integration Port Number (TXAn or LTAn if the port is on a terminal server)_________________________ Set Up Channels: o Channel (n)___________________________________________ o Protocol ()___________________________________________ o Message Desk Number(1)________________________________ o Addressing delay time_________________________________ Running DECvoice V2.2/V2.3 Configuration o T1 Framing for T1-1, [D3, D4, ESF] (D3)_______________ o T1 Framing for T1-2, [D3, D4, ESF] (D3)_______________ o T1 Framing for T1-3, [D3, D4, ESF] (D3)_______________ o Channels to enable on T1-1 ALL, None, 1-24, or 1 to ? (ALL)______________________ o Signaling = Off, EM_WINK, EM_IMMEDIATE, FXS_LOOP, FXS_GROUND, FXO_LOOP, FXO_GROUND__________________________________ 1-8 Resource Names Outgoing Lines = VCSI$OUTGOING_1 Incoming Lines = VCSI$INCOMING Voice service for each T1 Channel [Y, N] (Y) List of Services to be Allocated Circle appropriate service: (TONE_DETECT) TEXT_DEFAULT, RECOG_DEFAULT, STORE_DEFAULT, AUDIO_DEFAULT, TONE_DEFAULT, CPD_AUDIO1, TONE_DETECT, TONE_GENERATE, RECOG_CRECOG, RECOG_WRECOG, STORE_128K_LINEAR, STORE_64K_ULAW, STORE_64K_ALAW, STORE_16K_SUBBAND, STORE_16K_ADPCM, STORE_ADPCM, TEXT_ENGLISH, CONVERT, STORE_24K_ADPCM, STORE_ADPCM, TEXT_ENGLISH, CONVERT, STORE_32K_ADPCM, STORE_ADPCM, TEXT_ENGLISH, CONVERT DTC05-Configuration DTC05 boards can be configured for eight-line or single- line operation. You must create enough multi-line boards to accommodate all VOICE:mail ports (for example, three eight- line boards for a 24-port system). Unless otherwise specified always select the default value on the installation. 1-9 2 Installing VOICE:mail This section explains how to install VOICE:mail. Before proceeding, make certain that you have made the preinstallation preparations described in the previous chapter. If this is the first installation of VOICE:mail, VMSINSTAL will automatically create OpenVMS accounts for the VOICE:mail Manager and VOICE:mail Service, and the VOICE:mail server, all of which require unique UICs. VMSINSTAL is interactive and takes you step-by-step through the installation as described in this section. If possible, use a hardcopy terminal to keep a record of the installation. As an alternative, enter the following command to keep a record of the installation: SET HOST 0/LOG This command prompts you to log in and keeps a record of the login session in a SETHOST.LOG file in your default directory. When the installation is complete, log out to return to your original login session. 2-1 Upgrading VOICE:mail If you are upgrading VOICE:mail from an existing system, make sure that the VOICE:mail Process Monitor Utility (Snooper or VPR) and all VOICE:mail processes are shut down before installing the upgrade. To shut down the VPR process, type the following to get the entry number of the VCSI$VPR process: $ SHOW QUE/ALL VCSI$BATCH* Use the entry number to stop the VPR process by typing the following: $ DELETE /ENT=n Where n is the entry number of the VCSI$VPR process. To shut down the rest of the VOICE:mail processes, type the following: $ RUN VCSI$SYSTEM:VM_SHUTDOWN Answer {N} to the question about shutting down VOX, then enter an {A} to shutdown all processes. Refer to Chapter 5 of the system managers guide for a detailed description of the VM_shutdown utility. You must register your software license before installing Version 2.0 of VOICE:mail. The license registration information you need is contained in the Product Authorization Key (PAK) that is shipped with DEC- VOICE:mail. The VOICE:Mail Software PAK is a paper certificate that contains the information about the license - information you are required to have entered into the LMF database, and have loaded into the running OpenVMS system, prior to running the software. If you have one installed from a previous version of VOICE:mail, that is all you need. The license name used by VOICE:mail is DEC-VOICE-MAIL. 2-2 It is best to register your VOICE:mail license before you perform the installation. During the installation, you are asked if you have registered the license by loading the appropriate authorization key. If you have not already done so, you can complete the installation; however, you will not be able to run either the VOICE:mail software or the Installation Verification Procedure. (IVP). Once you have performed the license registration and have loaded the authorization key, you will be able to run the IVP and use VOICE:mail. To install multiple license PAKs, you must register each PAK prior to loading. LMF only allows one license load operation for multiple units. To register a license, log in to the System Manager's account, SYSTEM. o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your Product Authorization Key. To display a list of the currently loaded licenses, use the command: $ SHOW LICENSE The VOICE:mail license, named DEC-VOICE-MAIL, will be listed near the beginning of the display, if you have loaded the license correctly. See Appendix B, Loading the LMFPAK, for complete loading instructions. You will also need a PAK loaded for DECvoice which using the VOX product name for LMF registration. Without this PAK, VOICE:mail is unable to answer calls. See the DECvoice manual for more information. VMSINSTAL Perform the following steps to install VOICE:mail for OpenVMS for VAX Version 2.0. It is strongly recommended that the installation be done from the SYSTEM account. 2-3 Load the tape labeled VOICE:mail and begin the installation. Invoke VMSINSTAL as follows: 1. Log in to the SYSTEM account. 2. Type the following command: $ @SYS$UPDATE:VMSINSTAL VCSI020 3. The installation procedure begins and displays: VAX/VMS Software Product Installation Procedure V5.5 It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. Where dd-mmm-yyyy and hh:mm are the current date and time. 4. You may receive one or more of the following warning messages: %VMSINSTAL-W-LOWQUOTA, One or more account quotas may be too low. %VMSINSTAL-W-DECNET, Your DECnet network is up and running. %VMSINSTAL-W-ACTIVE, The following processes are still active: If you receive a warning message which you are not sure is not an issue, exit the installation procedure, correct the problem as described in the previous section, then restart the installation. The VOICE:mail product is not affected by DECnet being up during installation. VOICE:mail itself must be shut down or the installation will abort. 5. If there are any active system processes, the procedure lists them and asks: * Do you want to continue anyway [NO]? It is not advisable to continue, particularly if there are any active VOICE:mail processes. Press Return to stop VMSINSTAL. Make certain that all VOICE:mail processes are stopped, then restart the installation procedure. 2-4 If there are no active system processes, or if you want to continue the installation regardless of the warning messages, type Y. 6. The procedure asks: Are you satisfied with the backup of your system disk [YES]? If the system disk has not been backed up recently, type NO to abort the installation, and make a backup copy. Otherwise, press Return to accept the default answer of YES. 7.You will then see the following displayed: The following products will be processed: VCSI: V2.0 Beginning installation of VCSI V2.0 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product saveset A Product: DEC-VOICE-MAIL Producer: DEC Version: 2.0 Release Date: June 1, 1995 Do you want to purge files replaced by this installation? [YES] Do you want to run the IVP after the installation? [YES] 8. If you are not upgrading VOICE:mail from an existing system, go to the next step. If you are upgrading, the procedure displays: VOICE:mail has been installed before. Do you wish to continue [YES]? 2-5 Press Return to continue with the installation. Skip to step 9. If you are upgrading, see the section "Upgrading VOICE:mail" at the beginning of this chapter. 9. The procedure displays: INPUT DATA DISKS List disks that can be used for VOICE:mail. These disks will store voice messages that can, over a period of time, consume large amounts of disk space. Spreading the load across several disks increases performance. 10. Type LIST for a list of the disk names on your system. * Enter the disk name [Ctrl Z] to end: Enter the name of each disk and press Return. The order of entry is not important. This prompt will continue appearing until you press Ctrl Z. When you have supplied all disk names, press Ctrl Z to indicate that you are finished. A physical device name or a logical is allowed. VOICE:mail stores all files with references to its own logicals VCSI$DISK_A, VCSI$DISK_B, etc. so devices can be changed later without defining a second layer of logicals. To cancel the installation procedure, press Ctrl Z before entering any disk names or Control Y once you've entered disk names. The OpenVMS system disk can be used as one of the disks specified. However, Digital does not recommend this - if the disk is low on free blocks, system performance may be degraded. VOICE:mail automatically keeps track of the available space on each of the disks. The system assigns voice messages to the disk with the most available space, thus balancing usage across all disks. 2-6 11. The procedure will display: INPUT VOICE:mail SOFTWARE DISK Input the disk that you wish to house the VOICE:mail system software and phrase libraries. Due to the size of phrase libraries and accompanying software, 62,000 blocks of free disk space are required. This does not have to be the VMS system disk unless you desire it. * List the disk where the software should be installed: 12. Type in the disk name that will store the VOICE:mail system software and the phrase libraries. This can be any of the disks you specified in the previous step, or another disk. The procedure will display: * Do you wish to add the Digital commands to your DCL Tables [YES]? If you have not previously installed the VOICE:mail commands into your DCL table, you will receive a message asking if you wish the commands to be added. If you answer YES, the following commands will be added to DCLTABLES.EXE in the SYS$LIBRARY directory: COS _ Used to modify the Class of Service database EXT _ Used to modify the extension to Mailbox mapping database MBX _ Used to modify voice mailbox information PORT _ Used to modify port information SEND _ Used to send voice segment files to voice mailboxes STAT _ Used to produce statistical reports on voice mailboxes SYNTHESIZE _ Used to synthesize text files into voice segment files. 2-7 USG _ Used to produce statistical and graphic reports on telephone line usage for VOICE:mail. Digital encourages users to answer YES to this question. This improves login time, and it makes these commands available to other users who may need to administer VOICE:mail. These commands will not be available until the system is rebooted. 13. Now the system will create the VM_MANAGER, VM_SERVICE and VM$SERVER accounts. The procedure will display: INPUT UIC Type in a unique UIC number in the form [xxx,xxx] or [xxx,xxx], where xxx is a site-dependent octal number. The UIC must be unique. If you do not know a UIC and do not want the default, press Ctrl Y now, use AUTHORIZE to find a suitable UIC, and restart the installation. * Enter the UIC for the VM_MANAGER account [577,001]: This UIC is used to create the VM_MANAGER account, from which all VOICE:mail activities can be managed. 14. Next, you will create the password for the VM_MANAGER account: %VCSI-I-VMMANAGER_PW, Please enter the VM_MANAGER password. Password: Verification: %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named VM_MANAGER. %UAF-I-ADDMSG, user record successfully added 2-8 %UAF-I-RDBADDMSGU, identifier VM_MANAGER value [577,002] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named VM_MANAGER. 15. Now to create the VM_SERVICE account: Type in a unique UIC in the form xxx,xxx or [xxx,xxx], where xxx is a site-dependent octal number. The UIC must be unique. If you do not know a UIC and do not want the default, press Ctrl Y now, use AUTHORIZE to find a suitable UIC, and restart the installation. Note: It is recommended that this UIC be in the same group as the VM_MANAGER account. * Enter the UIC for the VM_SERVICE account [577,002]: %VCSI-I-VMSERVICE_PW, Please enter the VM_SERVICE password. * Reenter the password for verification [VM_SERVICE]: %UAFV-I-ADDNSG, User record successfully added %UAF-I-RDBADDMSGU, identifier VM_SERVICE value [577,002] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named VM_SERVICE. %VCSI-I-FOUNDCLD, The DCL tables already contain VCSI commands. %VCSI-I-FOUNDCLD, They will be upgraded by the install routines. 16. Now to create the VM$SERVER account: Type in a unique UIC in the form xxx,xxx or [xxx,xxx], where xxx is a site-dependent octal number. The UIC must be unique. If you do not know a UIC and do not want the default, press Ctrl Y now, use AUTHORIZE to find a suitable UIC, and restart the installation. 2-9 NOTE It is recommended that this UIC be in the same group as the VM_MANAGER account. The VM$SERVER account is not intended to be used for interactive logins so the password will probably never be used. * Enter the UIC for the VM$SERVER account [576,003]: %VCSI-I-VMSERVICE_PW, Please enter the VM$SERVER password. * Reenter the password for verification VM$SERVER: %UAFV-I-ADDNSG, User record successfully added %UAF-I-RDBADDMSGU, identifier VM_SERVICE value [576,003] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named VM$SERVER. %VCSI-I-FOUNDCLD, The DCL tables already contain VCSI commands. %VCSI-I-FOUNDCLD, They will be upgraded by the install routines. You are now finished installing VOICE:mail. You will see the following messages: %VMSINSTAL-I-RESTORE, Restoring product save set B... %VCSI-I-INPROG, Installation of INT subset is in progress. %VMSINSTAL-I-RESTORE, Restoring product save set C... %VCSI-I-INPROG, Installation of MAIL subset is in progress. 2-10 %VMSINSTAL-I-RESTORE, Restoring product save set D... %VCSI-I-INPROG, Installation of VOICE subset is in progress. %VMSINSTAL-I-RESTORE, Restoring product save set E... %VCSI-I-INPROG, Installation of PHRASES subset is in progress. PLEASE READ THE RELEASE NOTES Digital places important information in SYS$HELP:VCSI020.RELEASE_NOTES No more input is required to finish this installation. The installation can take 30 minutes to 2 hours depending on the system and if you are installing from disk or tape. Please be certain to perform the following steps: 1. Edit the site-specific system startup file, which is named SYS$MANAGER:SYSTARTUP_V5.COM in OpenVMS 5.* and SYS$MANAGER:SYSTARTUP_VMS.COM in OpenVMS 6.*. Add the command "@Sys$Startup:VCSI$Startup.Com". Place this after the Vox$Startup command, toward the end of the file. 2. Incorporate the SYSGEN changes listed in the DECvoice Software Installation Manual into the file SYS$SYSTEM:MODPARAMS.DAT. If you make any changes, run AUTOGEN and REBOOT. 3. Be sure to modify the SYS$STARTUP:VCSI$LOGICALS.COM file as required by the Release Notes and Installation Manual. 4. For new installations, you must also edit VCSI$SYSTEM:INT_SETUP.COM as detailed in the Postinstallation Configuration Chapter. The VOICE:mail software will be unable to operate if any of the previous steps are not performed. 2-11 When you have completed the installation, you will see the following displayed on the screen: Installation of VCSI V2.0 completed at hh:mm 2-12 3 Postinstallation Configuration During a new installation of VOICE:mail for OpenVMS VAX Version 2.0, the following files are created automatically: SYS$STARTUP:VCSI$LOGICALS.COM VCSI$SYSTEM:INT_SETUP.COM Both of these files must be modified by the System Manager to conform to the site's system configuration. Once the files are installed, they are not overwritten if VOICE:mail is reinstalled or updated. Upgrade installs create the file SYS$STARTUP:VCSI$LOGICALS.TEMPLATE to demonstrate the currently recommended format for the file. In addition, during installation of the DECvoice Software, a file called SYS$STARTUP:VOX$CONFIG.COM is created. This file must be run by the System Manager so that the DECvoice Software interacts correctly with VOICE:mail. This chapter provides information and recommendations to help the System Administrator configure these files to run with VOICE:mail. Modifying VCSI$LOGICALS.COM The SYS$STARTUP:VCSI$LOGICALS.COM file defines the configuration parameters used by the Digital processes. The parameters define the nodes where the various VOICE:mail and VOICE:environment directories, files, and most of the site-dependent startup values are installed. 3-1 Other site-dependent parameters also are defined in this file, including: o Data disk logicals o Snooper (Process Monitor Utility) configuration o Envelope presentation o Message notification redial specifiers o Call transfer sequences o Message waiting indicator sequences o Customization logicals These parameters are defined during installation and may be modified as system requirements change. Edit this file by typing: $ EDIT SYS$STARTUP:VCSI$LOGICALS.COM Then verify or modify the following values. Logical Name Table The next lines create the VCSI Logical Name Table with the standard logicals. VOICE:mail and VOICE:environment programs rely on these logicals for program parameters. Use extreme care when changing this table. $ CREATE /NAME /PARENT=LNM$SYSTEM_DIRECTORY /EXEC /PROT=(S:RWED,O:RWED,G:RWE,W:R) VCSI The next ten entries define the disk and directories for VOICE:mail and VOICE:environment files. Verify that the disk name matches the system disk entered during installation. $ DEFINE/NOLOG/SYSTEM VCSI$VIRTUAL_SYSTEM_1 VSYSTEMD Directory Location of Files $ DEFINE/NOLOG/SYSTEM/TRANSLATE=CONCEAL VCSI$ROOT/SYS $1$dia1:[VCSI.] $ DEFINE/NOLOG/SYSTEM VCSI$ERROR $1$dia1:[VCSI.ERROR] 3-2 VCSI$ERROR _ This subdirectory contains the Error Log files (GENERAL.ERR, VADMIN.LOG), which trap various system errors to aid in troubleshooting. $ DEFINE/NOLOG/SYSTEM VCSI$SYSTEM $1$dia1:[VCSI.SYSTEM] VCSI$SYSTEM _ This subdirectory contains the VOICE:mail and .EXE, .COM and .CLD files, including all file servers and utilities. $ DEFINE/NOLOG/SYSTEM VCSI$DATA $1$dia1:[VCSI.DATA] VCSI$DATA _ This subdirectory contains systemwide data (.DAT) files that apply to all Mailboxes on all virtual systems. It also contains the .FDL (File Definition Language) files that are the basis for creation of the data files. $ DEFINE/NOLOG/SYSTEM VCSI$CONFIG $1$dia1:[VCSI.CONFIG] VCSI$CONFIG _ This subdirectory contains the English language menu phrases and menu help text. $ DEFINE/NOLOG/SYSTEM VCSI$TOOLS $1$dia1:[VCSI.TOOLS] VCSI$TOOLS _ This subdirectory contains system management tools. $ DEFINE/NOLOG/SYSTEM VCSI$_NOVICE_LIB $1$dia1:[VCSI.SYSTEM.NOVICE] VCSI$_NOVICE_LIB _ This subdirectory contains the actual voice prompts (.SEG files) for the Standard Phrase Library. $ DEFINE/NOLOG/SYSTEM VCSI$_EXPERT_LIB $1$dia1:[VCSI.SYSTEM.EXPERT] VCSI$_EXPERT_LIB _ This subdirectory contains the actual voice prompts (.SEG files) for the Expert Phrase Library. $ DEFINE/NOLOG/SYSTEM VCSI$_COMMON_LIB $1$dia1:[VCSI.SYSTEM.COMMON] 3-3 VCSI$_COMMON_LIB _ This subdirectory contains the actual voice prompts (.SEG files) for the Common Phrase Library. Adding Data Disk Labels The following entries define the disk names to be used for the storage of messages (.SEG files). These labels were assigned during VMSINSTAL and should be changed only to add new disks to the system. Each disk has a sequential letter label, beginning with A. Do not skip letters. VOICE:mail uses these identifiers to assign storage for messages. For example the following defines disks 1 and 2 on the node as disks A and B for message storage: $DEFINE/SYSTEM VCSI$DISK_A/TRANS=CONCEAL $1$DIA1: $DEFINE/SYSTEM VCSI$DISK_B/TRANS=CONCEAL $1$DIA2: There will be one such entry per data disk specified at installation. VOICE:mail assigns messages to disks based on the largest amount of available free space. In order to prevent loss of messages, do not remove a disk from the list if it contains active messages. Do not add the same disk as more than one line. To add new disks, copy the last disk define, change the label to the next letter in the sequence, and add the new device name. Then create the following directories on the new disk: [vcsi], [vcsi.vsystemd], Make certain that the owner for each directory is VM_MANAGER. New Directory Structure Option The new directory structure option will allow a site to configure the system so that the storage of messages and headers will utilize a more distributed directory structure. The original structure caused message files to be distributed across multiple disk volumes, but stored in two directories on each disk, [VCSI.VSYSTEMD.MESSAGE] and [VCSI.VSYSTEMD.MSG_HEADER]. The new mode will deposit messages across disks as before, but will distribute 3-4 the message files over more subdirectories. The new disk paths are [VCSI.MESSAGE_xx] and [VCSI.MSG_HDR_xx], where xx is an integer number between 00 and 99. OpenVMS system performance decreases as the number of files in a directory grows large. Digital recommends maintaining a maximum of 5000 files per directory. This number can vary based on the hardware configuration and disk utilities such as volume shadowing and striping. To invoke the new directory structure, the site administrator will need to create the subdirectories. VOICE:mail uses the subdirectory structure automatically if it is created. A utility is provided to create the subdirectories and optionally move all the messages and message headers from the old directory structure to the new directory structure. This conversion does not have to be run and any message in the old structure will still be retrievable. It is recomended that the conversion utility be ran so that all message are moved into the new directory structure, therefore eliminating one point of confusion when tracking a message in question. The convert utility is outlined below: To run the conversion program, define the program as foreign command: $CVTD :== $VCSI$TOOLS:CONVERT_FLAT_TO_SUBDIR Decide if an immediate conversion of your current data is desired or if a slower migration to subdirectories is desired. If neither is desired and the current method is acceptable, you can skip this section as no change is required and the system will continue to function as it does currently. If you choose to use the subdirectory structure, a system backup is recommended. If you wish to only create directories and let the old messages age out of the [VCSI.VSYSTEMD.MESSAGE] and [VCSI.VSYSTEMD.MSG_HEADER] directories, shut down the VOICE:mail environment and type: $ CVTD DIR 3-5 This should run within five minutes and VOICE:mail can be restarted upon completion. If a complete conversion of all the messages and message headers to the new directory structure is desired, shut down voicemail and type: $ CVTD ALL The ALL parameter does all the work required but it can take hours on a directory with 10000 files. If a quicker conversion is required or if you have a system where downtime is hard to schedule and you have thousands of files, multiple conversion programs can be ran at the same time to do each disk separately. All disks must be converted at the same time without accepting calls. To break up the jobs so they run quicker, run these three lines in separate command files, one for each disk. If the system has one disk, it would require three command files. For two disks, six command files would be used. Before starting the jobs, remember to run CVTD DIR to create the directories. $ CVTD DISK=A FDR $ CVTD DISK=A SEG $ CVTD DISK=A HDR An alternate way to create just the new directory structure is to run the create_vm_subdirs utility in vcsi$tools. This utility will ONLY create subdirectories, and will be automatically run if the IVP is run to verify the installation proceedure. This utility is also invoked when VCSI$STARTUP.COM is executed, and the directory structure has not been setup. The command is: $RUN VCSI$TOOLS:CREATE_VM_SUBDIRS VOICE:Servers 3-6 Each of the following lines names a server, explains what the server does, and then gives the logical which defines the node from where the server is started. o File Server Master _ Hands off mailbox information requests to remote file servers and handles non-mailbox functions. $DEF /NOLOG/TABLE=VCSI FSM_MASTER_NODE node o Phone Book Server _ Allows searching Mailboxes by DTMF spelling and allows forward and backward searching of range of matching names. $DEF /NOLOG/TABLE=VCSI PHONE_BOOK_NODE nodename o Distribution _ Delivers messages to Mailboxes, for example, resolution of distribution lists and retry on problems. $DEF /NOLOG/TABLE=VCSI DISTRIBUTION_NODE nodename o Integration Server _ Controls Message Waiting Indication and communicates with phone system for DID addressing. $DEF /NOLOG/TABLE=VCSI INTEGRATION_NODE nodename o Message Notification Server _ Checks Message Notification schedules in response to message delivery and queues up dial jobs if outdialing is required. $DEF /NOLOG/TABLE=VCSI MSG_FWD_NODE nodename o Housekeeper _ Defines node to run Housekeeper on. Housekeeper performs nightly maintenance such as cleaning out the wastebasket, resetting "logins today," and other similar chores. At Housekeep time, defined in the System Settings menu, a housekeeper process will start for each VCSI$DISK_n, process that disk, then exit. The Housekeeper itself does not exit. $DEF /NOLOG/TABLE=VCSI HOUSEKEEPER_NODE nodename 3-7 o Usage Statistics Server _ Collects data from the Usage Collectors and stores it for subsequent processing by the DCL USG command. $DEF /NOLOG/TABLE=VCSI USG_STATS_NODE nodename o Logging Server _ Takes information on system events and stores it into files for Voicemail Administrator review. $DEF /NOLOG/TABLE=VCSI LGS_SERVER_NODE nodename The servers, (except the Phrase and Usage Servers), can be set to start up on any node in the cluster. Process counts per node The following lines define the number of VOICE:mails, Port Managers, and File Server Remotes that are to be run on each node. You must create a set of the following logicals for each node to be used with the VOICE:environment. If you have two nodes of a cluster running VOICE:mail, copy the set of logicals in this section into two sets and change the node names on the latter set to the second node name. $DEF /NOLOG/TABLE=VCSI PHRASE_SERVER_ON_nodename n Valid values are 0 and 1. A phrase server is required on nodes which answer phone calls or run the distribution server. $DEF /NOLOG/TABLE=VCSI FS_REMOTES_ON_nodename n FS_REMOTES_ON_nodename _ Digital recommends that you initially create two Remote File Servers per 24 ports. This number can be changed as the needs of your system are better understood. $DEF /NOLOG/TABLE=VCSI VOICEMAILS_ON_nodename n 3-8 VOICE_MAILS_ON_nodename _ Digital recommends that you create one VOICE:mail process for each DECvoice port which will answer calls. License PAKs must be registered or the processes will not start. $DEF /NOLOG/TABLE=VCSI PORTMGRS_ON_nodename n PORTMGRS_ON_nodename _ Digital recommends that you initially create one Port Manager for each six ports on the node. A 24-port system should be set up initially with four Port Managers. This number can be changed as the needs of your system are better understood. $DEF /NOLOG/TABLE=VCSI MSG_FWD_OD_ON_nodename n MSG_FWD_OD_ON_nodename _ This is the number of Message Notification outdialers needed on the node. Message Notification Outdialers can run on any node in the cluster with voice ports. $DEF /NOLOG/TABLE=VCSI MWI_DTMF_ON_nodename n MWI_DTMF_ON_nodename _ This is the number of DTMF integration Message Waiting Indication dialers needed on the node. $DEF /NOLOG/TABLE=VCSI MWI_MODEM_ON_nodename n MWI_MODEM_ON_nodename _ This is the number of modem integration Message Waiting Indication dialers needed on the node. $DEF /NOLOG/TABLE=VCSI USG_SERVER_ON_nodename n USG_SERVER_ON_nodename _ This allows Usage statistics to be generated for the named node. Run the USG DCL command on the node to examine the data. $DEF/NOLOG/TABLE=VCSI USG_COLLECT_ON_nodename n USG_COLLECT_ON_nodename _ This should be done on every node which is running the USG_Server. Data is collected here for storage and display later. $DEF /NOLOG/TABLE=VCSI VPR_ON_nodename n 3-9 VPR_ON_nodename _ VOICE:mail Process Restarter monitors the system for processes which are supposed to be present. If one is not there or is functioning incorrectly, it attempts to remedy the situation. The following lines establish parameters for the Digital Process Monitor Utility (VPR or Snooper) program, which monitors and restarts any failed processes: $DEF /NOLOG/TABLE=VCSI VPR_MAX_SLEEP 60 $DEF /NOLOG/TABLE=VCSI VPR_TIME_DETECT 60 $DEF /NOLOG/TABLE=VCSI VPR_TIME_INCR 5 VPR_MAX_SLEEP _ The maximum number of seconds that the VPR program should sleep before checking for any failed processes. VPR initially recycles at three seconds, adding five seconds to its sleep time if no failures are found or until the System Manager presses the spacebar to awaken it. VPR will keep adding five seconds to its sleep time until it reaches the MAX_SLEEP time specified on this line. VPR_TIME_DETECT _ The number of seconds that VPR waits before recognizing that a process has failed. This value cannot be set to less than 30 seconds VPR_TIME_INCR _ The number of seconds to add to the sleep time until the maximum sleep time is reached. Disk Space Monitoring The following lines provide thresholds for monitoring available disk space: $DEF/NOLOG/TABLE=VCSI DISK_WARNING_PERCENT 10 $DEF/NOLOG/TABLE=VCSI DISK_LIMIT_PERCENT 1 DISK_WARNING_PERCENT _ The warning percent is that point at which the VOICE:mail Administrator is warned about low disk space. DISK_LIMIT_PERCENT _ The disk limit percent is the percentage of the disk at which VOICE:mail stops taking messages. 3-10 Envelope Presentation The following lines specify how the envelope information associated with a message is presented. The values 1, 2, and 3 can appear in any order such as 123, 321, 132, 312, 12, 31, 13, 2 or 3. $DEF /NOLOG/TABLE=VCSI ENVELOPE_REVIEW 123 1 for NAME _ Say sender's name. 2 for TIME _ Say time sent. 3 for DATE_ Say date sent. DECvoice Software Resource o The next line provides the DECvoice software (VOX) resource name to which calls should be handed off after they are answered: $DEF /NOLOG/TABLE=VCSI$PROGRAM_1 VOICE_MAIL If you plan to run additional applications under VOICE:environment, you can define additional logicals, for example VCSI$PROGRAM_1000, and provide the VOX resource name your program waits for. In the VCSI_Master_Menu, you can set the parameters for handing off calls to each program 1000. The first 999 program numbers are reserved for Digital. Message Notification Redial Specifiers The next lines define the number of Message Notification redials and the time interval between redials. The initial dial is not counted as a redial. o Pager Redial _ Specifies three redials with a 15-minute wait between redials for pager schedules. $DEF /NOLOG/TAB=VCSI MN_PAGER_REDIAL "15,15,15" 3-11 o No Answer Redial _ Specifies three redials with a 15- minute wait between redials or calls receiving no answer. $DEF /NOLOG/TAB=VCSI MN_CALL_NA_REDIAL "15,15,15" o Busy Redial _ Specifies three redials with a 15-minute wait between redials for calls receiving a busy status. $DEF /NOLOG/TAB=VCSI MN_CALL_BUSY_REDIAL "15,15,15" o Failure Redial _ Specifies three redials with a 15- minute wait between redials for calls receiving a failure dialing. $DEF /NOLOG/TABLE=VCSI MN_FAILURE_REDIAL "15,15,15" Call Transfer Sequences The next lines define how the telephony equipment and DECvoice interact. They specify the call transfer control sequences for all telephony equipment including the extension designated for the Attendant. This file must be modified by the System Manager to conform to the site's system configuration. XFER1_ XFER2_ XFER3_ At the beginning of each logical is the transfer group number from the port settings menu. If you have multiple transfer flash sequences because of different telephony equipment configurations, this allows you to have different control sequences for each. From DECvoice Manual: ^ ==>> Flash (switch hook flash length settable in menus). W ==>> Wait for dialtone to be present. 3-12 X ==>> Call progress (busy, no answer, answer, reorder recognized). ! ==>> Pause for one second. Define the logical "dv" to allow commands to be entered into the correct logical table. Enter the following line: $dv :==define/nolog/table=vcsi The following line defines how VOICE:mail handles call transfers when call screening is on or off for Mailboxes and extensions with no Mailbox: $dv sys_defaults "0100" First digit value: 0: Call screening is off for numbers without a Mailbox. 1: Call screening is on for numbers without a Mailbox. Second digit value: 0: Do not say CALL TRANSFERRED to recipient of transfer. 1: Say CALL TRANSFERRED to recipient of transfer. Third digit value: 0: Do not look up call transfer mailbox extension in the DID translate table. 1: Look up number in the DID translate table. Fourth digit value: 0: Use translated extension to transfer to. 1: Use original extension to transfer to. Call transfers can be supervised or unsupervised. Supervised transfers provide call progress (busy, no answer, answer, or reorder). Unsupervised transfers do not provide call progress. The default setting is for all call transfers to be supervised. To make some extensions unsupervised, add them to the unsupervised extension list. To make all call transfers unsupervised, remove the X (call progress) from the supervised transfer sequences. 3-13 There are two sets of call transfer logicals - internal and external - for each transfer group number. The logicals listed below are the defaults for internal call transfers. The logicals for external call transfers follow. Internal Call Transfer Logicals These default logicals for internal call transfers may not apply to your telephony equipment. Please refer to your installation package for specific Call Transfer sequences. VOICE:mail uses the @ symbol to specify the insertion of a PBX extension in the following Call Transfer sequences. o Valid first character in extension: $dv XFER1_VALID_EXT_CHAR "0" Removal of any character prevents call transfers to numbers beginning with that digit (for example, elimination of valid character 9 prevents transfers to outside numbers on most telephony equipment). Because of security and cost considerations, add only those characters you want others to use as the first digit of a transfer dial. o Single switch hook flash if screened transfer user had pressed 9 to refuse call: $dv XFER1_REFUSED_CALL_SEQ "^" o Double switch hook flash if line was busy: $dv XFER1_RECONNECT_BUSY "^!^" o Double switch hook flash if unknown error occurred: $dv XFER1_RECONNECT_ERROR "^!^" o Double switch hook flash if no answer by transferee: $dv XFER1_RECONNECT_NO_ANSWER "^!^" o Double switch hook flash if line had reorder (fast busy): $dv XFER1_RECONNECT_REORDER "^!^" 3-14 o Good transfer. Dial this, hang up: $dv XFER1_CONNECT_SEQ " " o Unsupervised transfer, does not provide call progress: $dv XFER1_UNSUPERVISED_TRANSFER_SEQ "^!@!" o Supervised call transfer provides call progress (busy, no answer, answer, or reorder): $dv XFER1_SUPERVISED_TRANSFER_SEQ "^!@!X" Remove the X to make all transfers unsupervised. o Screened call transfer with supervision. Remove the X to make all transfers unsupervised: $dv XFER1_SUPER_CONSULTATION_SEQ "^!@!X" o Screened call transfer without supervision: $dv XFER1_UNSUPER_CONSULTATION_SEQ "^!@!" o Phone number for daytime operator: $dv XFER1_DAY_ATTENDANT_EXT "0" o Phone number for holiday operator: $dv XFER1_HOLIDAY_ATTENDANT_EXT "0" o Phone number for nighttime operator: $dv XFER1_NIGHT_ATTENDANT_EXT "0" o Comma separated list of extensions that will use unsupervised call transfers: $dv XFER1_UNSUPERVISED_EXT_LIST "0" Ext_list has a 255-character length limit. 3-15 External Call Transfer Logicals The following is a list of the logicals for external call transfers (numbers longer than the MAX_INT_DIGITS parameter in the port settings). If you do not allow offsite transfers, these logicals are not used. o Valid first character in extension: $dv XFER1_OUT_VALID_EXT_CHAR "0" o Single switch hook flash if screened user pressed valid characters 0-9 to refuse call: $dv XFER1_OUT_REFUSED_CALL_SEQ "^" o Double switch hook flash if line was busy: $dv XFER1_OUT_RECONNECT_BUSY "^!^" o Double switch hook flash if unknown error occurred: $dv XFER1_OUT_RECONNECT_ERROR "^!^" o Double switch hook flash if no answer by transferee: $dv XFER1_OUT_RECONNECT_NO_ANSWER "^!^" o Double switch hook flash if line had reorder (fast busy): $dv XFER1_OUT_RECONNECT_REORDER "^!^" o Ok transfer. Dial this, hang up: $dv XFER1_OUT_CONNECT_SEQ " " o Unsupervised transfer, does not provide call progress: $dv XFER1_OUT_UNSUPERVISED_TRANSFER_SEQ "^!@!" 3-16 o Supervised call transfer provides call progress (busy, no answer, answer, or reorder): $dv XFER1_OUT_SUPERVISED_TRANSFER_SEQ "^!@!X" Remove the X to make all transfers unsupervised. o Screened call transfer with supervision: $dv XFER1_OUT_SUPER_CONSULTATION_SEQ "^!@!X" Remove the X to make all transfers unsupervised. o Screened call transfer without supervision: $dv XFER1_OUT_UNSUPER_CONSULTATION_SEQ "^!@!" o Phone number for daytime operator: $dv XFER1_OUT_DAY_ATTENDANT_EXT "0" o Phone number for holiday operator: $dv XFER1_OUT_HOLIDAY_ATTENDANT_EXT "0" o Phone number for nighttime operator: $dv XFER1_OUT_NIGHT_ATTENDANT_EXT "0" o Comma separated list of extensions that will use unsupervised call transfers: $dv XFER1_OUT_UNSUPERVISED_EXT_LIST "0" Message Waiting Indicator Sequences The next lines define how the MWI dialer and the modem or telephony equipment interact. If modem integration is being used, the modem logicals should be set. If DTMF integration is being used, the DTMF logicals should be set. DTMF integration also requires outgoing lines. See the Changing Resource Names and Signaling description in the VOX$CONFIG.COM section for the required modifications. 3-17 The MWI1_ and MWI2_ at the beginning of each logical is the PBX channel number from the integration channel data. A set of MWI dial sequences should be defined for each modem or DTMF integration channel assigned. The @ symbol inserts the dialed PBX extension at that location. Modem MWI Logicals The Message Waiting Indication On/Off characters in these examples are #6 and *6. These values are telephony equipment dependent and must be correct for the phone system VOICE:mail is connected to. o Defines the modem startup command string. Many modems only allow 40 characters per command string. Spaces are optional: $DV MWI1_START "ATS0=0 S7=1 S11=45 T X4 V1 E0 QO" o Defines the modem dial response to the start-up sequence sent: $DV MWI1_START_RESPONSE "OK" o Defines the modem dial response to the dial sequence sent: $DV MWI1_DIAL_RESPONSE "OK' o Defines the modem dial response maximum delay time between the start of the dial until the response is sent: $DV MWI1_DIAL_RESPONSE_WAIT 8 DTMF MWI Logicals The Message Waiting Indication On/Off characters in these examples are #6 and *6. These values are telephone system dependent and must match the telephone system VOICE:mail is to be connected to. For these commands, a W can be added at 3-18 the beginning of the command if a dialtone wait is required before dialing MWI sequences. o Defines the dial string to turn on a Message Waiting Indication: $DV MWI1_ON "#6@" o Defines the dial string to turn off a Message Waiting Indication: $DV MWI1_OFF "*6@" Setting Hook Flash Length To set the length of a valid hook flash, add a set line command for each channel to your SYS$STARTUP:VCSI$LOGICALS.COM file: $ mcr vox$cp Set line vox$node$vna1 /config /t1=x /chan=y /time_delay=(flash=z) Where: node = computers' nodename x = T1 number (1 to 3) y = channel number (1 to 24) z = hook flash length. The value of z for the hook flash length is specified in milliseconds. To set all channels on T1-1 requires 24 lines with x having a value of 1 and y counting up from 1 to 24. For a half- second hook flash length, the value of z would be 500. The default time is 500 milliseconds if no other time is specified. Many telephone systems will hang up if the hook flash length is too long. 3-19 Printing from VOICE:menu To print using [CTRL_P] from the VOICE:menu, the system manager must set up a print queue, which can be defined as any of the following: o SYS$PRINT o A queue pointed to by SYS$PRINT o A queue pointed to by the logical MENU_PRINT_QUE in the VCSI logical table. The print command will first look for the MENU_PRINT_QUE logical. If it is not defined, it then looks for SYS$PRINT. To set up the SYS$PRINT queue, see the instructions in the OpenVMS System Manager's Guide. To define the MENU_PRINT_QUE logical, add the following line to the SYS$STARTUP:VCSI$LOGICALS.COM file: $DEF/NOLOG/TABLE=VCSI MENU_PRINT_QUE print_que Replace print_que with the actual name of the print queue. Additional Logical Definitions Define the double key press mode during message playback: $DEF/NOLOG/TABLE=VCSI DOUBLE_KEY_TIMEOUT 1500 To implement double key press mode to be used during playback of messages. This would allow sites to configure their system in a way that would require users to press a key twice to invoke the desired function. If the logical is defined, the user will have to press the desired key twice to invoke a function during the playback of a message. The administrator will define a VCSI table logical denoting length of time, (milliseconds), allowed between successive key presses. $DEF/NOLOG/TABLE=VCSI DOUBLE_KEY_TIMEOUT 1500 3-20 This will cause the voice mail application to wait for 1500 milliseconds, (1 and one half seconds), after the first key is pressed. If the next key is pressed within the 1500 limit and is the same key the function will be invoked. If the key is different, the wait period starts for the new key. 1500 is a relatively high setting, but the administrator will be allowed to set this any value the wish. NOTE The playbackof messages is not paused during this wait period, so if the setting is high there is not a gap in the playback of the message. Define the double key press mode for one Class of Service. $DEF/NOLOG/TABLE=VCSI DOUBLE_KEY_COS 3 An additional feature is mainly designed for debugging, and is available for the released code. This feature allows for a Class of Service override setting. If this logical is defined in the VCSI table, then only users assigned to this class of service will have access to the DOUBLE_KEY mode during playback. $DEF/NOLOG/TABLE=VCSI DOUBLE_KEY_COS 25 This definition forces the system to invoke double key mode during playback for users assigned to class of service 25. All other users will be in normal playback mode where each key pressed during playback is processed. Define trapping of (*) key during login, and at the main menu. $DEF/NOLOG/TABLE=VCSI TRAP_PW_STAR YES This logical has two purposes: 1) If defined, the subscriber will not be allowed to use the star (*) key to exit from the main menu, and thus be prompted for another mailbox. The system will end the call for either the star or pound key when pressed form the main menu from within VOICE:mail. 3-21 2) If defined, the user will not cancel password entry if a single star is pressed, when being prompted for the password. If a single star is pressed at the password prompt, the caller is reprompted for the password. After 3 attempts, the call is terminated. Define ability to send message prior to transfer sequence if transfer is requested during a the recording of a message. XFER_DURING_RECORD in the VCSI table will allow the administrator to set the system for automatic sending of messages, when a transfer request is issued. If the logical is set to any value, and a transfer is requested during recording or editing of an outside caller message. The message is sent prior to performing the transfer. $DEF/NOLOG/TAB=VCSI XFER_DURING_RECORD Y Define, on a system wide basis, automatic message tagging with calling party, if the calling party information is known at the time of message creation, and the user is not logged into a mailbox. TAG_CALLING_PARTY in VCSI table allows the administrator to set tagging of message from the outside caller path, with the extension of the calling party id for the call. This allows messages to be tagged from users sending message via the outside caller path when using their internal extensions. $DEF/NOLOG/TAB=VCSI TAG_CALLING_PARTY Y Define a minimum length for valid messages. MINIMUM MESSAGE LENGTH in the VCSI table specifies the minimum number of milliseconds a message must be before it is considered long enough to be valid. If a message shorter than this number is recorded, the user will be prompted with "Insufficient information recorded." and asked to record their message again. The default value is 500 or one half second. The range is 500 to 5000 which is one half second to 5 seconds of message required before the message is valid. Setting this logical to longer times than 500 milliseconds causes messages to be thrown out which can be desirable if quick-hangup callers leave messages that just click and end. 3-22 Callers are informed the message is not recorded unless they hang up too rapidly such as saying: "Tim calling" then hangup. $DEF/NOLOG/TAB=VCSI MIN_MESSAGE_LENGTH 500 INT_SETUP.COM This file establishes the link between the Integration Server and the telephone equipment. It is located in the [VCSI.SYSTEM] directory on the VOICE:mail system disk. The logical VCSI$SYSTEM points to this directory, but the logical is not defined until VOICE:mail has been started. Go to the [VCSI.SYSTEM] directory and edit the INT_SETUP file by typing: $ EDIT INT_SETUP.COM Then, verify or modify the following values: o The following two lines provide a pause for the Integration Server to finish initializing and set the ICONTROL command: $ WAIT 00:00:05 $ SET COMMAND VCSI$SYSTEM:ICONTROL o The following lines define the integration terminal port setup. For a Serial Integration, remove the comment symbol so that they appear as shown below: $ SET_UP_TERMINALS: $ SET TERM /PARITY=EVEN /NOEIGHTBIT /FRAME=7 /PASTHRU /NOECHO /SPEED=1200 /NODIALUP /NOHANGUP /NOMODEM /TYPE_AHEAD/PERM TXAn Be sure to remove the $ sign and the comment sign from the second line of the terminal setup. 3-23 o For Modem Integration (Inband Signaling), remove the comment symbol from the following lines so that they appear like this: $ SET TERM/SPEED=1200/NODIALUP/NOHANGUP/NOMODEM /TYPE_AHEAD/PERM TXAn For DTMF Integration (Inband Signaling), no terminal port is used. The terminal (txan) should be changed to the correct terminal port name. NOTE Digital does not recommend LAT ports for integration. However, if the terminal port is on a LAT server, the port must be set up on the server to match the characteristics in the set term command. o The following lines define the integration channel to the Integration Server. For Serial Integration, remove the comment symbol from the following: $ ICONTROL ASSIGN /CHAN=W /TERM=TXAn /PROTOCOL=protocol /MDN=X /PAD=Y /DID_LENGTH=xx /DELAY=Z o For Modem Integration (Inband Signaling), remove the comment symbol from the following: $ ICONTROL ASSIGN /CHAN=W /TERM=TXAn /PROT=MODEM /DTMF_KEYS=YY /DID_LENGTH=XX /DELAY=Z o For DTMF Integration (Inband Signaling), remove the comment symbol from the following: $ ICONTROL ASSIGN /CHAN=W /TERM=TXAn /PROT=DTMF /DTMF_KEYS=YY /DID_LENGTH=XX /DELAY=Z 3-24 Where: W = PBX Channel number (1-31) X = Message desk number (should match telephone equipment or the SID, if one is used) XX = Number of called-party DID digits to use (from the right side) Y = Padding character of the configured telephone number as configured on switch/SID. If the padding character is a blank, enclose it in quotation marks. YY = Number of DTMF keys that will be sent through the line. Z = Addressing delay time PROTOCOL = Integration protocol being used. For inband DTMF integration, the DTMF protocol handles most cases with its default setting of DTMF. See below for details of overrides for special integration requirements. For serial integration using SMDI or a Voice Bridge, insert one of the following: VB_ATT, VB_NT, VB_ROLM, SMDI, SL100_SMDI. The default DTMF protocol does not support both called and calling party via inband signaling. If you have a phone system which provides this information, you can specify variations to the DTMF protocol by defining logicals in the VCSI table which can be done in VCSI$LOGICALS.COM or INT_SETUP.COM. To enable both called and calling party DTMF integration, define a logical CHAN_n_INT_TYPE to DTMF:DDDDGGGG where: n is the channel number from the Icontrol command. DDDD represents four digits of calleD party integration GGGG represents four digits of callinG party integration. If you have five digits of each with calling party first on channel 1, your logical definition command would be $define/table=vcsi CHAN_1_INT_TYPE "DTMF:GGGGGDDDDD" # and * can be used in the string if your telephone equipment sends them as separators or terminators. 3-25 If DECvoice picks up the integration through its ANI capabilities, you can fetch that data by using the same style command. $define/table=vcsi CHAN_1_INT_TYPE "ANI". No specification of length or position is required as DECvoice has this information already. o The following lines describe the T1 lines to the Integration Server and should match the number of lines on the license. $ icontrol define /line=nodename$vna:nn.xx /ltn=xx/chan=W Where: VNA:NN.XX is the DECvoice channel number. LTN is the VOICE:mail port number. W is the channel number of the PBX matching an Icontrol assign statement above. NOTE Sierra brand channel banks use a non-linear numbering scheme so assure your channel numbers are correct. A typical 8 port Sierra channel bank has T1 channels 1,2,3,4,13,14,15,16. For serial integrations, the LTN-to-line name mapping should correspond to the serial integration setup. If no integration is being used, the channel number must be zero. Lock Integration Terminal Port If a serial integration is being used, it is important to add the following line as early as possible in the system startup command procedure (SYS$MANAGER:SYSTARTUP_V5.COM for VMS 5.*, SYS$STARTUP:SYSTARTUP_VMS.COM for VMS 6.*) $ set term/notype_ahead/perm txan Where TXAn is the integration terminal port. This blocks any integration data coming through the serial link during system startup. This prevents the terminal port from starting a login session before VOICE:integration has completed its startup. If you are using a LAT port, this must be done after LAT$STARTUP executes. 3-26 VOX$CONFIG.COM The following section provides information on running SYS$STARTUP:VOX$CONFIG.COM to set up the Digital Equipment Corporation DECvoice software to run with VOICE:mail. Be sure to define the SCS NODE in SYSGEN before running VOX$CONFIG. Type the following DCL command from the SYSTEM or other suitable account: $ @SYS$STARTUP:VOX$CONFIG The following message will be displayed followed by a description of how to run this procedure. DECVOICE: VOX CONFIGURATION PROCEDURE Setting the T1 Framing You can set the framing type for each of the three supported T1 lines. The default should be chosen unless you know your T1 is different. All T1 connections are configured here through three questions. DECvoice DTCN5 port device: _nodename$VNA0: Type of T1 Framing (T1 1)? [def: D4] D3,D4,ESF * Framing type? D4 Location of Hardware The answers to the following country and T1 connection questions specify which regulatory volume level rules apply on each of the three T1 connections. These rules are specified by the public telephone network regulatory agency located in the country specified. Location (country) of DECvoice hardware? [def: USA] * Location (country) of DECvoice hardware? USA 3-27 Choose CHANNEL_BANK if you have one, and CSU for a direct telephone equipment to VAX T1 line. Equipment connected to T1 (T1 1)? [def: channel_bank] CSU, CHANNEL_BANK * Equipment connected to T1? channel_bank Equipment connected to T1 (T1 2)? [def: channel_bank] * Equipment connected to T1? channel_bank Equipment connected to T1 (T1 3)? [def: channel_bank] * Equipment connected to T1? channel_bank Next, describe the lines that will be used for each T1 channel. For a 24-line site, ALL can be chosen. If you plan to use 16 of the 24 lines, use the a comma-separated list, for example: "1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16" Note: Sierra brand channel banks use a non-linear numbering scheme so assure your channel numbers are correct. A typical 8 port Sierra channel bank has T1 channels 1,2,3,4,13,14,15,16. Channels to enable on T1 1? [def: NONE] [All, None, or comma separated list "1,2,3"] * Channel List? ALL Most sites will have groups of lines that will be configured identically. Answer "yes" to the following question. If necessary, you can configure each line individually. Do you wish to specify a range of channels with identical signaling and identical or similar resource names? [def: N] * Type ? for help (Y,N,?)Y 3-28 Enter list of channels in the form mm[:nn],... mm specifies a single channel mm:nn specifies the list of channels *Channels available are : (01,02,03,04,05,06,07,08,09,10,11,12, 13,14,15,16,17,18,19,20,21,22,23,24) * Channel List? 1:24 Type of T1 Signaling ? [def: EM_WINK] OFF, EM_WINK, EM_IMMEDIATE, FXS_LOOP, FXS_GROUND, FXO_LOOP, FXO_GROUND Select the signaling type that your telephony equipment is using. * Signaling type? FXS_LOOP Outgoing Lines Next, you need to set the resource name and signaling type. For outgoing lines, choose VCSI$OUTGOING_1 as your compatibility resource name. If you plan to do message notification, you must have VCSI$OUTGOING_1 defined. If you do not want VOICE:mail to dial out on a line, use VCSI$NO_OUT_DIAL. If you want DECvoice Software (VOX) to outdial but not VOICE:mail, use VOX$OUTBOUND_RESOURCE. Incoming Lines For the incoming resource, choose the following on all lines the VOICE:environment port managers should answer: VCSI$INCOMING 3-29 If you do not want the lines to be answered by the port managers, choose another name such as VOX$INCOMING Repeat the previous steps for additional T1 lines you want to configure (for example, T1-2 or T1-3). Do you wish to allocate (voice) services for each T1 channel? (Y,N) [def: N] Y Enter '?' to list all service mask keywords Enter list of services to be allocated [def:TONE_DETECT] You can preallocate VOX services for each telephone line. If you are using E and M signaling, you MUST preallocate TONE_DETECT if you want callers to hear a ring before answer. Please note that the VOX default is TONE_DETECT. Other preallocations are not required but are allowable. Following is a list of the Service Mask keywords that can be preallocated: USER1 through USER 16 TEXT_DEFAULT, RECOG_DEFAULT, STORE_DEFAULT, AUDIO_DEFAULT, TONE_DEFAULT, CDP_AUDIO1, TONE_DETECT, TONE_GENERATE, RECOG_CRECOG, RECOG_WRECOG, STORE_128K_LINEAR, STORE_64K_ULAW, STORE_64K_ALAW, STORE_16K_SUBBAND, STORE_16K_ADPCM, STORE_ADPCM, TEXT_ENGLISH, CONVERT Do you wish to define a shadow (broadcast or conversion) resource? [def: N] (Y,N) Y *Shadow resource name? $NULL$ Do you wish to allocate (voice) services for this shadow resource? [def:Y] (Y, N) N 3-30 Define DTC05 Line Mode The next step is to define which DTC05 boards are multiline and which are single line. Digital recommends that you configure multiline boards first, followed by single line boards. Choose enough multiline boards to answer all the T1 lines defined in the previous example. DECvoice DTC05 port device: _nodename$VMA0: * 1 Line or 8 Line Operations? [1 or 8,def: 1] 8 * Number of Channels with Multi-line call Progress? [0-8, def: 8] 8 DECvoice DTC05 port device: _nodename$VMB0: * 1 Line or 8 Line Operations? [1 or 8,def: 1] 1 * Enable Call Progress on single line module? [Y or N, def: Y] N * Word/Continuous Recognizer? [W or C,def: W] W VOX$CONFIG now finishes up and displays the files it has created. These will be run automatically by SYS$STARTUP:VOX$STARTUP Changing Resource Names and Signaling Once you have run VOX$CONFIG, you do not need to rerun it to change resource names. However, when adding or removing boards or changing characteristics other than resource names, you may want to rerun VOX$CONFIG. By editing SYS$STARTUP:VOX$nodename$STARTUP.COM, you can make these minor changes. (Nodename is your computer's node name.) 3-31 The VOX$CONFIG system-generates the file VOX$nodename$STARTUP.COM. In this file, you will find the resource names defined in lines such as the following: $ set line VOX$nodename$VNA1 /reso /t1=1 /chan=01 /offer=c /name=VCSI$OUTGOING_1 $ set line VOX$nodename$VNA1 /reso /t1=1 /chan=01 /offer=i /name=VCSI$INCOMING $ set line VOX$nodename$VNA1 /conf /t1=1 /chan=01 /signa=FXS_LOOP The /offer parameter tells the type of resource name. C is for compatibility or outgoing resources. I is for incoming calls. The line with the /signa parameter sets the signaling type on that T1 channel. The T1=1 and chan=01 denote T1-1.01. These set line commands can be done through VOX$CP with VOX running if you want. Changing the incoming (/offer=i) resource names is not recommended unless you do not want the port managers to answer that line. This will not busy out the line unless you change the /signaling type to OFF. DTMF integration requires one line for every six ports for Message Waiting Indication. The outgoing resource name for MWI is VCSI$MWI_n where N is the PBX channel number in the mailbox which the MWI is for. Change VCSI$OUTGOING_1 to VCSI$MWI_n on the required number of lines for MWI. If the lines are in a circular hunt group, the best performance is achieved by spacing the lines evenly. On a hunt-up, put the lines opposite the most used line. 3-32 Printing from VOICE:menu To print using CTRL_P from the VOICE:menu, the system manager must set up one of the following print queues: o SYS$PRINT o Queue pointed to by SYS$PRINT o Pointed to by the logical MENU_PRINT_QUE in the VCSI logical table The print command will first look for the MENU_PRINT_QUE logical. If it is not defined, then it looks for SYS$PRINT. To set up the SYS$PRINT queue, see the instructions in the following file: SYS$STARTUP:SYSTARTUP_V5.COM for OpenVMS 5.* or SYS$STARTUP:SYSTARTUP_VMS.COM for OpenVMS 6.*. To define the MENU_PRINT_QUE logical, add the following line to the SYS$STARTUP:VCSI$LOGICALS.COM file: $ DEFINE/NOLOG/TABLE=VCSI MENU_PRINT_QUE print_que Replace print_que with the actual name of the print queue. 3-33 4 Installation Verification Procedure The VOICE:mail Installation Verification Procedure will quickly verify that the VOICE:mail software is installed and functioning correctly. The procedure requires the following: o Terminal connected to the VAX running the VOICE: software o Touch-Tone telephone connected to VOICE:mail New Directory Structure Option The new directory structure option will allow a site to configure the system so that the storage of messages and headers will utilize a more distributed directory structure. The original structure caused message files to be distributed across multiple disk volumes, but stored in two directories on each disk, [VCSI.VSYSTEMD.MESSAGE] and [VCSI.VSYSTEMD.MSG_HEADER]. The new mode will deposit messages across disks as before, but will distribute the message files over more subdirectories. The new disk paths are [VCSI.MESSAGE_xx] and [VCSI.MSG_HDR_xx], where xx is an integer number between 00 and 99. OpenVMS system performance decreases as the number of files in a directory grows large. Digital recommends maintaining a maximum of 5000 files per directory. This number can vary based on the hardware configuration and disk utilities such as volume shadowing and striping. 4-1 To invoke the new directory structure, the site administrator will need to create the subdirectories. VOICE:mail uses the subdirectory structure automatically if it is created. A utility is provided to create the subdirectories and optionally move all the messages and message headers from the old directory structure to the new directory structure. This conversion does not have to be run and any message in the old structure will still be retrievable. It is recomended that the conversion utility be ran so that all message are moved into the new directory structure, therefore eliminating one point of confusion when tracking a message in question. The convert utility is outlined below: To run the conversion program, define the program as foreign command: $CVTD :== $VCSI$TOOLS:CONVERT_FLAT_TO_SUBDIR Decide if an immediate conversion of your current data is desired or if a slower migration to subdirectories is desired. If neither is desired and the current method is acceptable, you can skip this section as no change is required and the system will continue to function as it does currently. If you choose to use the subdirectory structure, a system backup is recommended. If you wish to only create directories and let the old messages age out of the [VCSI.VSYSTEMD.MESSAGE] and [VCSI.VSYSTEMD.MSG_HEADER] directories, shut down the VOICE:mail environment and type: $ CVTD DIR This should run within five minutes and VOICE:mail can be restarted upon completion. If a complete conversion of all the messages and message headers to the new directory structure is desired, shut down voicemail and type: $ CVTD ALL 4-2 The ALL parameter does all the work required but it can take hours on a directory with 10000 files. If a quicker conversion is required or if you have a system where downtime is hard to schedule and you have thousands of files, multiple conversion programs can be ran at the same time to do each disk separately. All disks must be converted at the same time without accepting calls. To break up the jobs so they run quicker, run these three lines in separate command files, one for each disk. If the system has one disk, it would require three command files. For two disks, six command files would be used. Before starting the jobs, remember to run CVTD DIR to create the directories. $ CVTD DISK=A FDR $ CVTD DISK=A SEG $ CVTD DISK=A HDR An alternate way to create just the new directory structure is to run the create_vm_subdirs utility in vcsi$tools. This utility will ONLY create subdirectories, and will be automatically run if the IVP is run to verify the installation proceedure. This utility is also invoked when VCSI$STARTUP.COM is executed, and the directory structure has not been setup. The command is: $RUN VCSI$TOOLS:CREATE_VM_SUBDIRS Process Verification Verify that all VOICE:mail processes are running as follows: 1. Log in to the VM_MANAGER account. 2. Run Snooper, the Process Monitor Utility by typing SNOOPER. 3. The system displays the following: Option [V] 4. Type Return. 4-3 The number of each type of process currently running is displayed at the top of the screen. The letters are in uppercase if the process should be running on this node. If the VCSI$LOGICALS.COM file dictates that the process should not be run on the node you are logged in to, then the letters will be lowercase. An example of the fields are as follows: VM (24)/(24) _ VOICE:mail processes. The number on the left is the number currently running. The number on the right is the number that should be running. These numbers should match. VM should be lowercase if no VOICE:mail processes are on this node. FR (2)/(2) _ File Server Remote processes. The number on the left is the number currently running. The number on the right is the number that should be running. These numbers should match. FR should be lowercase if no File Server Remote processes are on this node. PM (4)/(4) _ Port Manager processes. The number on the left is the number currently running. The number on the right is the number that should be running. These numbers should match. PM should be lowercase if no Port Manager processes are on this node. PS (1) _ Phrase Server process. This number should be one unless no VOICE:mails or Distribution Servers are on this node. It should be lowercase if no Phrase Server is required to run. FM (1) _ File Server Master. This number should be 1 on the node pointed to by FSM_MASTER_NODE in the VCSI table. FM should be lowercase on all other nodes. PB (1) _ Phone Book Server. This number should be 1 if the Phone Book Server runs on this node. PB should be lowercase if the Phone Book Server executes on another node. INT (1) _ Integration Server Process. This number should be 1 if the Integration Server runs on this node. INT should be lowercase if the Integration Server executes on another node. 4-4 DST (1) - Distribution Server. This number should be 1 if the Distribution Server executes on this node. DST should be lowercase if the Distribution Server executes on another node. LGS (1) - Logging Server. This number should be 1 if the Logging Server executes on this node. LGS should be lowercase if the Logging Server executes on another node. RCV (1) - Receive Agent. This number should be 1 if the Receive Agent executes on this node. RCV should be lowercase if networking is disabled or the Receive Agent executes on another node. MD (1)/(1) - Message Waiting DTMF dialers on this node. These numbers should match. If you do not run MWI DTMF dialers, the letters MD will be lowercase. MM (1) - Message Waiting Modem dialers on this node. These numbers should match. If you do not run MWI Modem dialers, the letters MM will be lowercase. MNO (1)/(1) _ Message Notification Outdialers. These numbers should match. If no Message Notification Outdialers are on this node, the letters MNO should be lowercase. MN (1) - Message Notification Server. This should be 1 if the Message Notification Server executes on this node. If the Message Notification Server executes on a different node, MN should be lowercase. HKP (1) _ Housekeeping. This number should be 1 if uppercase. If Housekeeping executes on another node, HKP should be lowercase. US (1) _ Usage Statistics Utility. This number should be 1 if USG Statistics are running on this node, lowercase if disabled USC (1) _ Usage Statistics Collector. This number should be 1 if USG Statistics are running on this node, lowercase if disabled. 4-5 VOX (1) _ DECvoice Software. This number should be 1 unless you have no voice ports on this node. VPR (1) _ Automatic restart for VOICE:mail processes. This should be 1 if VPR is running in the batch queue, lowercase if VPR is not desired. DLV (1) _ Delivery Agent. This should be 1 if the Delivery Agent is running on this node. If networking is not enabled or the Delivery Agent is running on another node, DLV should be lowercase. If the number of processes is not correct, run Snooper again, but answer A to perform automatic restarts. Snooper will then restart any stopped processes. Type E to exit Snooper when all of the required processes have been started. Type R to redraw Snooper screen if the need arises. Mailbox Verification Verify that VOICE:mail Administration is functioning correctly. Create a Mailbox using the Administrator's menu, as follows: 1. At the DCL prompt, type: Menu The VOICE:menu will be displayed. 2. Select Setup from the Main Menu. 3. Select Mailbox from the next menu. 4. Enter a Mailbox number. 5. Enter "Jones, Bill" for the name of the Mailbox and the PBX extension number of the telephone you are using. 6. Enter the password for the mailbox and press Return. You will see the message "Password Updated." 4-6 7. Press the DO key to create the Mailbox. 8. Press Ctrl Z. At the "rebuild Directory with NEW name(s)?" prompt, enter Y and press Return. 9. Press Ctrl Z twice to exit VOICE:menu. VOICE:environment Verification Verify that the VOICE:environment servers are functioning properly. 1. Dial the VOICE:mail number from a Touch-Tone telephone and log in to Mailbox by entering the Mailbox number and pressing the pound [#] key. You will hear the message "The mailbox has not been initialized." Press the star [*] key during this message. You will hear a prompt for the password. Enter the default password for Class of Service 2, then press the pound [#] key. You will hear the message, "Welcome to your new Mailbox" and then a prompt to enter a password and record your name. If you have the password wrong, check the Class of Service 2 default password via the menu command. 2. Follow the instructions to set the password to 123654 and record the name, "Bill Jones." 3. Press the star [*] key from the Main Menu to get to the prompt, "Please enter the Mailbox number of the person you are calling..." 4. Press the star [*] key again to look up the person in the directory. Press the J O N E S keys (56637) on the telephone to spell the user's name. The system will respond with, "First entry, Bill Jones." 5.Select the current name, and leave the following message in the Mailbox: "Test message for Bill Jones from outside caller." 6. Press the [1] key to accept the message. 7. Press the [2] key to mark the message urgent. 8. Press the [1] key to send the message. 4-7 9. Press the [2] key to select another Mailbox. 10. Log in to the Mailbox by entering the Mailbox number, followed by the pound key, [#], the star key[*], the password [123654], and the pound [#] key. 11. You will hear, "You have one new message. [number] seconds." 12. Press the [1] key to receive new messages. 13. You will hear, "Urgent message from outside caller." Listen to the message. 14. Press [3] to move the message to the Wastebasket. You will hear, "Moved to Wastebasket. No more messages." 15. Press the [#] key twice to disconnect. Integration Verification If VOICE:mail is integrated with the telephony equipment, verify that the integration server is functioning properly as follows: 1. Dial the extension of the telephone you are using. It should forward on busy to VOICE:mail. If the integration is functioning correctly, you should hear the default Mailbox greeting, "Please leave a message for Mailbox _____. " If you hear the company greeting, the integration is not functioning correctly. 2. Press the pound [#] key to cancel the recording. 3. Press the pound [#] key again to disconnect. MWI Verification If the Message Waiting Indication is being used, the MWI Test Utility can be used to verify that it is functioning properly as follows: 4-8 1. Log in to the VM_MANAGER account 2. Run the MWI Test Utility as follows: $ Run VCSI$SYSTEM:MWI_TEST 3. Enter the integration channel number. This number typically is 1. 4. Enter the PBX extension for the telephone associated with the Mailbox. 5. Enter [1] to turn Message Waiting Indication on. A normal status should be returned on the terminal and the Message Waiting Indication on the telephone should be on. 6. Repeat steps 3 and 4 and enter a [2] to turn Message Waiting Indication off. 7. Press [Ctrl_Z] to exit the program. 4-9 A Installation Checklist This Installation Checklist is used to verify the correct installation and operation of the VOICE:mail, VOICE:integration and VOICE:environment software and associated hardware components. It contains elements for the following: o Verification of power and grounding requirements for the hardware components. o Verification of the telephony equipment programming for the VOICE:mail system. o Verification of all physical connections for the VOICE:mail system. o Verification of all VOICE:mail ancillary equipment (Channel Bank, Software Integration Device). o Reviewing user-defined system parameters (for example, COS, MBIDs, scheduling). o Installing the VOICE:mail software. o Validation of port connections. o Validation of continuity between the VOICE:mail System, A-1 o Integration protocol and telephony equipment. o Running the Installation Verification Procedure (IVP). o Prior to installation of VOICE:mail, the following items need to be verified. Place a check mark next to the item after verification. Power Requirements The following equipment requires a stable power source conforming to the specifications in the Digital Equipment Corporation "Site Environmental Preparation Guide" (Order # EK-CSEPG-MA-001): VAX Channel Bank Administration Terminal Remote Diagnostic Modem Software Integration Device (if used) Grounding Requirements The following equipment must be properly grounded in accordance with the specifications in the Digital Equipment Corporation "Site Environmental Preparation Guide" (Order # EK-CSEPG-MA-001): VAX Channel Bank Remote Diagnostic Modem Software Integration Device (if used) Miscellaneous Equipment The following equipment may be needed: DTMF Butt set RS-232 Breakout Box Four telephones connected to the system Integration Protocol Verify that the Integration configuration is correct. A-2 Channel Bank Verify that Channel Bank configuration is correct. Verify that there is a hardcopy of the Channel Bank configuration on file. Hardware Connections Verify that all physical hardware connections are made and correct. Telephony equipment to Channel Bank Channel Bank to VAX VAX/Integration protocol to telephony equipment Remote Diagnostic Modem to VAX Remote Diagnostic Modem to telephone line VAX to Administration Terminal VOICE:mail Line Verification Verify the programming of each VOICE:mail telephone line to ensure the following: Outdial controls (message notification). Allows call transfer with hook flash or other sequence. Gives silence on disconnect. The revision level of telephony equipment integration software (needed for later). Confirm the hunt type and group of the integration port(s) and VOICE:mail ports. VOICE:mail Installation For detailed instructions on the following procedures, see the VOICE:mail System Manager's Guide (AA-PZP8B-TE). Verify that the VAX system date and time are correct. Install the VOICE:mail release tape(s). Verify VOICE:mail Integration (MWI Test and Integration Monitor utilities). Run the VOICE:mail Installation Verification Procedure (IVP). A-3 VOICE:mail Initial Setup For additional instructions on the following procedures, see the VOICE:mail Administrator's Guide (AA-PZPBB-TE). Edit VCSI$LOGICALS.COM Edit INT_SETUP.COM Run VOX$CONFIG.COM Print and review port configuration. Review and record company greetings. Set Day/Night/Holiday schedule. Set up Classes of Service. Set up initial Mailboxes. Run Phonebook Build utility. Print and review the Phonebook/Mailbox report. Print and Review Class of Service report. Print all statistics to verify that all categories are at 0 after installation. Reset statistics. Print and review all statistics to verify against previous print out. Review Day/Night/Holiday schedules. Post Installation Requirements a) Change ENVELOPE_REVIEW logical if networking is to be enabled. This will present the date before the time. Doing this will avoid the double "AT" phrase. IE: Message from Mailbox name , "AT" vmail, "AT" 3:10 am, on Nov. 12, 1990 LOGICAL NUMERIC DEFINITIONS: 1 = Say the name or mailbox of the sender. 2 = Play the TIME the message was delivered. 3 = Play the DATE the message was delivered. EXAMPLES: Default: Define/tab=vcsi envelope_review 123. (Play name, then time, then date) Define to: Default: Define/tab=vcsi envelope_review 132. (Play name, then date, then time ) A-4 NOTE This will NOT affect the specific option to review the envelope. This option is accessed from the edit message sub menu. (KEY STROKES: 5 then 0, during message review.) For specific envelope review, the order is always 123. b) Make sure the logical fsm_master_node node is added to the logicals.com file, and delete vcsi$master logical. Need to make sure that the logical VCSI$MASTER is replaced with the logical FSM_MASTER_NODE. c) lgs_node, recv_node, dlvr_node logicals to vcsi$logicals.com. Need to add the following logicals to vcsi$logicals.com file if not already in vcsi$logicals.com. DEFINE/NOLOG/TABLE=VCSI LGS_SERVER_NODE YOUR_NODE_NAME DEFINE/NOLOG/TABLE=VCSI RECV_AGENT_NODE YOUR_NODE_NAME DEFINE/NOLOG/TABLE=VCSI DLVR_AGENT_NODE YOUR_NODE_NAME d) Remove the PORT_MANAGER_NODE logical from VCSI$LOGICALS.COM. Take out line: DEFINE/NOLOG/TABLE=VCSI PORT_MANAGER_NODE e) Check MAX MESSAGE OUT: Need to insure that max message out in the class of services is not ZERO, unless there is a message sending restriction that is to be applied. Voicemail has ability to disable sending messages for designated Classes of Service. If the max outbound message is 0, the owner of the mailbox will be restricted from sending outgoing messages. User will not be prompted for send message options from any menu if their Class of Service outbound message length is 0. NOTE If outbound message length = 0, Same restrictions apply A-5 f) Reset stats: Stats for all mailboxes should be reset, so the counters are reinitialized. Enter the following command. $STATS/RESET g) Set house keep twice today Need to force a houskeeping run at this point. Enter the following: Define/table=VCSI HOUSEKEEP_TWICE_TODAY YES A-6 B Loading the LMF PAK If you re installing a new VOICE:mail system, prior to restarting VOICE:mail, you must install the LMF PAK for your system by following these steps: 1. Run the SYS$UPDATE:VMSLICENSE file: @SYS$UPDATE:VMSLICENSE 2. Choose one of the following VMS License Management Utility Options: 1. REGISTER a Product Authorization Key 2. AMEND an existing Product Authorization Key 3. CANCEL an existing Product Authorization Key 4. LIST the Product Authorization Keys 5. MODIFY an existing Product Authorization Key 6. DISABLE an existing Product Authorization Key 7. DELETE an existing Product Authorization Key 8. COPY an existing Product Authorization Key 9. MOVE an existing Product Authorization Key 10. ENABLE an existing Product Authorization Key 11. SHOW the licenses loaded on this node 12. SHOW the unit requirements for this node 99. EXIT this procedure Type ? at any prompt for a description of the information requested. Press CTRL Z at any prompt to exit this procedure. Enter one of the above choices [1] 1 B-1 3. Verify that the following information is correct as it is displayed on your system: SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB Issuer: DEC Authorization: ALS-WM-90165-203 Producer: DEC Product Name: DEC-VOICE-MAIL Units: 800 Release Date: Version: Termination Date: Availability: Activity: CONSTANT=100 Options: Token: Hardware ID: Checksum: 1-KBAB-MKOG-NJOD-DPED 4. Answer Y to the following: Is this information correct? [YES] You will then see: Registering DEC-VOICE-MAIL license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB 5. Answer NO to the following unless this is your last PAK for DEC VOICE:MAIL. Do you want to LOAD this license on this system? [YES] NO 6. Continue until all required PAKs are loaded, 1 PAK for 8 ports of VOICE:mail. 7. Once you have entered the data for the last PAK, answer Y to this question: Do you want to LOAD this license on this system? [YES] Y Load the proper number of units, for example, 2400 units for 24 ports. B-2 C Sample Installation Log File The bold text in the following is what you will see on the screen during the installation. Sections preceded by an exclamation point (!) are comments about the installation procedure. !Before installing VOICE:mail,.you must install DECvoice !Software. Run the SYS$UPDATE:VMSINSTAL file: $@sys$update:vmsinstal VAX/VMS Software Product Installation Procedure V5.4-3 It is 16-AUG-1993 at 16:04. Enter a question mark (?) at any time for help. %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: VUE$NAME_2 VUE$NAME_5 _FTA42: _FTA47: C-1 DECW$MWM DECW$TE_00CF _FTA46: * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted:DKA300:[NAME] !Enter the products to be processed from the first distribution !volume set. * Products: vox023 * Enter installation options you wish to use (none): The following products will be processed: VOX V2.3 Beginning installation of VOX V2.3 at 16:00 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. *********************************************************** *DECvoice* *VOX V2.3* *Installation Procedure* *Copyright, 1994. Digital Equipment Corporation* *All Rights Reserved.* C-2 !To save disk space, type NO to the question about loading the !VOX VOICE files. VOICE:mail installation log $ @SYS$UPDATE:VMSINSTAL VCSI020 MUA0: ! MUA0 can be replaced by the name of your tape drive or the ! name AND directory of a local on disk where the VCSI020.* ! files are stored. VAX/VMS Software Product Installation Procedure V5.5 It is 8-MAY-1995 at 20:07. Enter a question mark (?) at any time for help. %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: GARY_P * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? y The following products will be processed: VCSI V2.0 Beginning installation of VCSI V2.0 at 20:07 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. C-3 ****************************************************** * DEC VOICE:mail for Open/VMS for VAX * * Version 2.0 * * * * * * Copyright, 1995. Digital Equipment Corporation * * All Rights Reserved. * ****************************************************** * Do you want to purge files replaced by this installation [YES]? y * Do you want to run the IVP after the installation [YES]? y INPUT DATA DISKS List disks that can be used for VOICE:mail. These disks will store voice messages that can, over a period of time, consume large amounts of disk space. Spreading the load across several disks increases performance. Type "List" for a list of disk names on your system. * Enter the disk name : list Device Device Error Volume Free Name Status Count Label Blocks Count Cnt $4$DIA0: (TIGON0) Mounted 0 VMS 154608 $4$DIA1: (TIGON1) Mounted 0 DISK1 534783 $4$DIA2: (TIGON2) Mounted 0 DISK2 435072 * Enter the disk name : tigon1: * Enter the disk name : tigon2: * Enter the disk name : ^Z INPUT SYSTEM DISK Input the disk that will house the VOICE:mail system software and phrase libraries. Due to the size of phrase libraries and accompanying software, 62,000 blocks of free disk space is required. C-4 * List the disk where the software should be installed: tigon1: INPUT UIC Type in a unique UIC number in the form xxx,xxx or [xxx,xxx], where xxx is an octal number. The UIC must be unique. If you do not know a UIC and do not want the default, press control-y now and use Authorize to find a suitable UIC then restart the installation. * Enter the UIC for the VM_MANAGER account [577,001]: %VCSI-I-VMMANAGER_PW, Please enter the VM_MANAGER password. Please enter a password of at least 15 characters. * Password: (Password) Password must be a minimum of 15 characters. * Password: (Password) * Verification: > (password) %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named VM_MANAGER. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier VM_MANAGER value: [000577,000001] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named VM_MANAGER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named VM_MANAGER. %UAF-I-MDFYMSG, user record(s) updated C-5 INPUT UIC Type in a unique UIC number in the form xxx,xxx or [xxx,xxx], where xxx is an octal number. The UIC must be unique. If you do not know a UIC and do not want the default, press control-y now and use Authorize to find a suitable UIC then restart the installation. * Enter the UIC for the VM_SERVICE account [577,002]: %VCSI-I-VMSERVICE_PW, Please enter the VM_SERVICE password. Please enter a password of at least 15 characters. * Password: (Password) * Verification: (Password) %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named VM_SERVICE. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier VM_SERVICE value: [000577,000002] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named VM_SERVICE. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named VM_SERVICE. %UAF-I-MDFYMSG, user record(s) updated INPUT UIC Type in a unique UIC number in the form xxx,xxx or [xxx,xxx], where xxx is an octal number. The UIC must be unique. If you do not know a UIC and do not want the default, press control-y now and use Authorize to find a suitable UIC then restart the installation. C-6 * Enter the UIC for the VM$SERVER account [576,003]: %VCSI-I-VMSERVER_PW, Please enter the VM$SERVER password. Please enter a password of at least 15 characters. * Password: (Password) * Verification: (Password) %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named VM$SERVER. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier VM$SERVER value: [000576,000003] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named VM$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named VM$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VCSI-I-FOUNDCLD, The DCLtables already contain VCSI commands. -VCSI-I-FOUNDCLD, They will be upgraded by the install routine. No more input is required to finish this installation. The installation can take from one to two hours depending on the system and if you are installing from disk or tape. ************************************** %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VCSI-I-INPROG, Installation of INT subset is in progress. C-7 %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VCSI-I-INPROG, Installation of MAIL subset is in progress. %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VCSI-I-INPROG, Installation of VOICE subset is in progress. %VMSINSTAL-I-RESTORE, Restoring product save set E ... %VCSI-I-INPROG, Installation of PHRASES subset is in progress. PLEASE READ THE RELEASE NOTES Digital places important information in SYS$HELP:VCSI$020.RELEASE_NOTES. Please be certain to perform the following steps: o Edit the site-specific system startup file, SYS$MANAGER:SYSTARTUP_V5.COM,to include the command "@Sys$Startup:VCSI$Startup.Com". Please place this after the Vox$Startup command. If batch queues are running, it is better to "Submit sys$startup:vcsi$startup.com/user=vm_manager" after Vox has started. o Incorporate the SYSGEN changes listed in the DECvoice Software Installation Manual into the file SYS$SYSTEM:MODPARAMS.DAT. If you make any changes, run AUTOGEN and REBOOT. o Modify the SYS$STARTUP:VCSI$LOGICALS.COM file as required by the Release Notes and Installation Manual.If upgrading from a previous version, check SYS$STARTUP:VCSI$LOGICALS.TEMPLATE for examples of the changes. o For New installs, you must also edit VCSI$SYSTEM:INT_SETUP.COM as detailed in the Installation Manual. The Voice Mail Software will be unable to operate if any of the above steps are not performed. C-8 %VCSI-I-IVP, the VCSI DEC/VOICE:mail Installation Verification is executing. Copr. c Digital Equipment Corp. 1993. All Rights Reserved. The message directory structure does not exist. Creating directories. %VCSI-I-LOADLOG, Loading vcsi$logicals.com from sys$startup. %JBC-I-QUENOTMOD, modifications not made to running queue %VCSI-I-LOADDONE, Load of logicals file is done -------------------------------------------- %RMS-W-FNF, File not found: VCSI$DISK_A:[vcsi]VSYSTEMD.dir. _RMS-W-FNF, This file is needed for VOICE:mail to run. The IVP continues... %VCSI-W-NOVIRT, The above warnings are typical on New installs. After you have configured & started the software the first time, the files will be created. Upgrades from previous versions who get this message should investigate further. The IVP has completed successfully. Installation of VCSI V2.0 completed at 22:38 VMSINSTAL procedure done at 22:38 C-9