Instruction manual

Voice Prompts
120 025-9416
Make sure that Silence Compression is turned on (set by way of raw oparams). See the
Model 640 Operating and Programming Manual (Part No. 025-9417) for details.
Programming is simplified if VoxDisconnect is enabled. (Set in the Telephone Line Data-
bases.) This ensures that the recording will time out after a specified interval of silence.
Five short beeps indicate successful completion of a command.
Three short beeps indicate the paging terminal is waiting to accept another command.
A slow busy signal indicates an incorrect command code.
After speaking the new prompt, wait quietly until a confirmation tone is played.
RESTORING VOICE PROMPTS
The original factory prompts are stored on the PC hard drive when MCU is installed. These
prompts should be kept in the event that the custom prompts are deleted or corrupted.
Customized Prompts
Follow the steps below to restore custom voice prompts to the paging terminal:
Note: Custom prompts can only be restored if backup copies of the files were previously
made. Do backups every time the prompts are modified! Refer to “Backing Up Voice
Prompts” on page 117.
q
1. Enter the Model 640 Communications Utility (MCU) program.
q
2. Move the cursor to the Restore menu using the arrow keys ( and ).
q
3. Press <Enter> to view the menu choices.
q
4. Highlight vOice Prompts and press <Enter>.
q
5. MCU links to the paging terminal and transfers copies of each voice prompt file
automatically. The screen shows status information about each file and the success of
the restoration.
Factory-Recorded Prompts
Follow the steps below to restore the original system voice prompts to the paging terminal:
q
1. If custom prompts currently reside in the paging terminal, you may want to make
backup copies now. Refer to “Backing Up Voice Prompts” on page 117.
q
2. Check the current contents of the site subdirectory (C:\MCU\<sitename>) for voice
files. This can be accomplished by way of the DOS “dir” and “ls” commands or
using the Windows “File Manager” utility. There are 16 voice files identified by an
underscore character (_) within the file name. For example, ‘bad_numb.er’ and
‘sys_busy’. Refer to Table 16 for the description and name of each voice file. If the
site subdirectory already contains voice files, delete them now or move them to
another directory for safekeeping (not C:\MCU\PROMPTS).