Key Voice Voice Processing System Installation And Maintenance Manual

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-367905Error  Setting Stop Bits on Port COM
See error 6901.
7906Error  Closing Port COM
See error 6901.
7907Error  Sending Data to Port COM
See error 6901.
7908Error  Reading Data From Port COM
See error 6901.
8101ACD Box  in Invalid State 
This is an internal error.  If the problem persists, contact technical support.
8201IVR Box  In Invalid State 
This is an internal error.  If the problem persists, contact technical support.
8301Account Box  In Invalid State 
This is an internal error.  If the problem persists, contact technical support.
8401Network Not Detected (Are Network Drivers Loaded?)
The VP system was programmed to communicate with VCM over a local area network (LAN).  However,
the VP system was unable to detect the network.  Make sure you have loaded the network drivers in the
AUTOEXEC.BAT file.  Make sure you have loaded the Netbios emulator for the network.  For more
information, contact the LAN administrator.
8402Unable to initialize LAN interface
The VP system was unable to initiate communication with the Local Area Network (LAN). Make sure all
required network drivers are loaded. .  For more information, contact the LAN administrator.
8501Unknown Protocol   In Use on LAN
This is an internal error.  If the problem persists, contact technical support. 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-378601Invalid Data (, ) in LAN Login Record For Line 
This is an internal error.  If the problem persists, contact technical support.
8602Not Enough Memory to Log in New User ( Logged In)
The VP system ran out of conventional memory when it tried to allow a VCM user to log in.  The
message indicates the number of users currently logged in.
8603Login Cross-Check  Failed.  Data =
This is an internal error.  If the problem persists, contact technical support.
8604Login Audit Error .  Data =
This is an internal error.  If the problem persists, contact technical support.
8701Cannot Find LAN Fax Control File 
A VCM user tried to send a fax via the VP system.  The VP system was unable to access the file that it
uses for VCM fax record-keeping.  The file was probably corrupt or missing.  The VP system created a
new version of the file.  Some pending faxes (waiting to be sent) may be lost when the new file was
created.
8801LAN Module in Invalid State 
This is an internal error.  If the problem persists, contact technical support.
8802Login Record Corrupt on Line . Stored Line = .
This is an internal error.  If the problem persists, contact technical support.
8901Cannot Create Directory File 
The VP system was unable to create the file indicated.  VCM uses this file to create its own directory of
mailboxes.  Make sure the VP system computer has network write access to the indicated directory.
8902Cannot Add Box  To Directory File 
While creating the directory file used by VCM, the VP system was unable to add the indicated box to the
file.  VCM uses this file to create its own directory of mailboxes.  Make sure the VP system computer has
network write access to the indicated directory
9101Fax-Transfer Box  In Invalid State 
This is an internal error.  If the problem persists, contact technical support. 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-389102Cannot Find File . Exit and Run EXTNS Utility
While processing a fax call, the VP system was unable to find the file containing the extension numbers
of its fax-enabled ports.  Exit to DOS, and run the EXTNS utility.  This allows you to enter the information
the VP system requires.
9201Fax-Transfer Box  In Invalid State 
This is an internal error.  If the problem persists, contact technical support.
9202Cannot Create Receive-Area For Incoming Fax on Line .
The VP system was unable to allocate a memory buffer into which it could receive a fax document.
9203Status  Reported While Receiving Fax on Line 
While receiving an incoming fax document, the VP system encountered a bad status value from the fax
hardware.  The VP system stops receiving and clears the call.  The various status values are described
below:StatusDescription1The document file has been opened.2The document file has been moved.3The document file has been deleted.9204Line  Was Receiving Fax For  Minutes (Data =)
While receiving an incoming fax document, the VP system found that the line was in a receive state for
more than a reasonable amount of time.  As a safety precaution (to prevent the lines from being tied up
under error conditions), the VP system cleared the line.  What constitutes a reasonable time can be
defined using the configuration file VM.CFG (FAX TIMEOUT parameter).
9205Result  Reported From GET_FAX on Line  (Data =)
While the VP system was receiving an incoming fax document, the fax hardware reported a completion
result indicating that there was a problem.  The various result codes are as follows:ResultCodeDescriptionResultCodeDescription4Received data lost642Bad PCX file header258File not found643Unexpected end-of-file259Path not found644Unexpected disconnect260Too many open files770Cannot find file261Access denied771Cannot find path263Memory corrupted1025Remote unit not Group 3 compatible264Insufficient memory1027Remote unit requested disconnect 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-39ResultCodeDescriptionResultCodeDescription269Invalid data1030Excessive line noise271Invalid drive1037Remote unit disconnected277Drive not ready1045Tried to receive from incompatible
hardware287General failure1055Unexpected end-of-file while receiving641Bad phone number9206Status  reported while receiving fax on line 
See error 9203.
9207Could not retrieve received fax on line 
The VP system was receiving a fax.  The fax module indicated that the fax had been received completely.
However, when the VP system tried to place the fax in the appropriate box, the fax module did not make
the document available.
9301Unknown Answer-Type  For Question  In Q-Box 
The VP system tried to play the specified answer from the Question box indicated, but the answer-type
was not valid (the valid answer types are VOICE and DIGITS).
9304Group-Box  Is Full, and Cannot Accept Messages
The specified Group box has no room for new messages. The members of the Group box should delete
old messages. A Group box message is not deleted from the Group box until all members have asked for
it to be deleted. Once all members have asked for the message to be deleted, the VP system deletes it the
following midnight.
9305Group-Box  is Full, Message Discarded
The specified Group box has no room for new messages. The members of the Group box should delete
old messages. A Group box message is not deleted from the Group box until all members have asked for
it to be deleted. Once all members have asked for the message to be deleted, the VP system deletes it the
following midnight.
9306Cannot Deliver Message To Box , Box Type  Is Invalid
An attempt was made to deliver a message to the specified box, but the box type is not a mailbox or a
Group box. The message was discarded. 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-409307Cannot Confirm Receipt of Message. Sender = , Receiver = 
While processing a message that was marked for receipt-confirmation, the VP system was unable to
notify the sender that his/her message was received.  If the problem persists, contact technical support.
9308Cannot Play Voice Menu 
The VP system was unable to play a certain voice menu. This is an internal error.  Contact technical
support.
9401Unable to Deliver Message to Box . Box Type  is Invalid
An attempt was made to deliver a message to the specified box, but the box type is not a mailbox or a
Group box. The message was discarded.
9501Netbios Error  In . Data = .
Netbios reported an error while the VP system was trying to send or receive information.  If the problem
persists, contact technical support.
9502Overflow Occurred while Sending Network Messages
The local area network was busy and was unable to keep up with the VP system’s requests to send
information.
9503Netbios Not Responding ()
The VP system was programmed to communicate with VCM over a local area network (LAN).  However,
the VP system was unable to detect the network.  Make sure you have loaded the network drivers in the
AUTOEXEC.BAT file.  Make sure you have loaded the Netbios emulator for the network.  For more
information, contact the LAN administrator.
9504Not Enough Memory to Load Network Module
The VP system ran out of conventional memory while trying to load the LAN module.
9601Not Enough Memory to Load PCIU Module
The VP system ran out of conventional memory while trying to load the PCIU module.
9602PCIU Receive Queue is Full
The VP system was unable to handle all the messages coming from users of VCM.  If the problem
persists, contact technical support. 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-419603Attempt to Send Unknown Message Type  to PCIU
This is an internal error.  If the problem persists, contact technical support.
9604Unknown Message Type  Received from PCIU
A message was received from a VCM user that the VP system did not recognize.  If the problem persists,
copy the COMDIAL.LNK file from the distribution disks into the VP system directory.  If the problem
persists, contact technical support.
9701Not Enough Memory to Load PCIU Module
The VP system ran out of conventional memory while trying to load the PCIU module.
9702Tried to Send Unknown Message Type  to PCIU
This is an internal error.  If the problem persists, contact technical support.
9801Call-Record Module in Invalid State ()
This is an internal error.  If the problem persists, contact technical support.
9901Mail box  in invalid state. Call terminated.
This is an internal error.  If the problem persists, contact technical support.
9902Unknown digit type  received on line 
The voice board reported a digit to the VP system that was neither DTMF or Dial Pulse.  If error persists,
replace the voice board.
10001Key error . Data=
An error was detected while reading the security key. Ensure the key is connected to a printer port.  If the
problem persists, contact technical support.
10002Key not detected
The security key was not detected. Ensure the key is connected to a printer port.  If the problem persists,
contact technical support.
10401Not enough conventional memory for line information
After finding that there was not enough EMS memory to hold its line-related information, the VP system
attempted to use DOS conventional memory.  However, there was not enough conventional memory
either. 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-4210402Label information corrupted
The VP system was unable to read the internal label information contained in the file ACCER.DAT.  Copy
the original (ACCER*.DAT) from the VP system CD or diskettes.
10403Label information file missing
The VP system was unable to open the file ACCER.DAT, containing the label information. Copy the
original (ACCER*.DAT) from the VP system CD or diskettes.
10404Not enough memory to run program (you need at least KB more).
The computer does not have enough conventional memory to load the VP system.  Remove any other
TSR programs and re-boot the computer.  Type MEM at the \VM directory prompt (depending on system
setup) and verify that there is 640 K bytes total conventional memory available.
10405Cannot allocate enough file handles
The VP system needs to be able to open several files at once while it is running.  DOS was unable to
guarantee that there would be enough file handles available.  Make sure the CONFIG.SYS file sets the FILES
setting to at least 40.
10501Error  Opening System-Database File 
The VP system was unable to open the database file containing the system information (SDTABASE.DVM).
If this error is encountered during start-up, the VP system automatically creates a new system-information
file, using its own default values.  You should then go to the SYSTEM INFORMATION menu, and update the
information on each screen.  (The information displayed on the LINE STATUS screen has not been
affected).  Alternatively, you can restore the latest backup of the system information database file
SDTABASE.DVM.
10502Error  Opening Line-Database File 
The VP system was unable to open the database file containing the line information (LDTABASE.DVM).  If
this error is encountered during start-up, the VP system automatically creates a new line-information file,
using its own default values.  You should then go to the LINE INFORMATION screen, and update the
information.  The information displayed on the LINE INFORMATION screen is the only information that has
been affected.
10503Error  Opening Box-Database File 
The VP system was unable to open the database file containing the box information (BDTABASE.DVM).  In
most cases, this error is generated because the file has been deleted, or there is a hard drive problem.  If
this error is encountered during start-up, the VP system automatically creates a new box information file.
This new file does not contain any of the boxes, only the system reserved boxes (those numbered between
9900 and 9999).  You must either re-enter all box information or restore the latest backup of the database
files (*.DVM).  If you are unsure of how to proceed, contact technical support before you do anything. 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-4310504Cannot open message database file  ()
The VP system was unable to open the database file containing the message information
(MDTABASE.DVM).  In most cases, this  error is generated because the file has been deleted, or there is a
hard drive problem.  If this error is encountered during start-up, the VP system automatically creates a
new file.
10505Cannot add box  to database
The VP system was unable to add the indicated box to the database.  Exit to DOS, and check that the
box’s file is not corrupt.  Also, confirm that the hard drive has sufficient space.
10506Cannot read box  information from database ()
The VP system was unable to read information from the file containing the database box information
(BDTABASE.DVM).  Exit to DOS, and check that the file is not corrupt. Also, confirm that the hard drive
has sufficient space.
10507Cannot write box information to file 
The VP system was unable to write information to the file containing the database box information
(BDTABASE.DVM).  Exit to DOS, and check that the file is not corrupt.  Also, confirm that the hard drive
has sufficient space.
10508File pointer error accessing box  (pointer = )
This error can be generated when the VP system is updating the file MDTABASE.DVM, which contains
information on messages held in each mailbox.  If the problem persists, check the hard drive for errors.  If
you do not have a backup, delete the file, and run the utility MSGAUDIT to allow the VP system to rebuild
the file.
10510Cannot rename database file  (error = )
When the VP system is compressing the database (to save hard drive space), it uses a temporary file.
When the compressing operation is complete, the VP system renames the temporary file to the proper
database filename BDTABASE.DVM.  This error message indicates that the VP system was unable to
rename the temporary file.  Exit to DOS, and rename the file yourself.  From the DOS prompt, type:
RENAME BDTABASE.TMP BDTABASE.DVM
10511Cannot re-index database (error = )
When the VP system is shutting down, it compresses the box database to make processing more efficient.
During compression, the VP system encountered an error.  Normal operation will not be affected.  If the
problem persists, contact technical support. 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-4410512Cannot allocate auxiliary buffer for box 
This error can be generated when the VP system is updating the file MDTABASE.DVM, which contains
information on the messages held in each mailbox.  If the problem persists, check the hard drive for
errors.  If you do not have a backup, delete the file, and run the utility MSGAUDIT to allow the VP system
to rebuild the file.
10513Error  reading message  info for box 
The VP system encountered an error while trying to read the database files for the specified box.  The
problem is probably localized to the database file MDTABASE.DVM.  If the problem persists, check the
hard drive for errors.  If you do not have a backup, delete the file, and run the utility MSGAUDIT to allow
the VP system to rebuild the file.
10514Cannot initialize auxiliary module
The VP system was not able to initialize its internal tables. Re-start the system.
10515Cannot delete message  in box 
Due to an internal error, the VP system was unable to delete a message from the specified box. The
problem is probably localized in the database file MDTABASE.DVM.  If the problem persists, check the
hard drive for errors.  If you do not have a backup, delete the file, and run the utility MSGAUDIT to allow
the VP system to rebuild the file.
10516File pointer error  in box 
This error can be generated when the VP system is updating the file MDTABASE.DVM, which contains
information on messages held in each mailbox.  If the problem persists, check the hard drive for errors.  If
you do not have a backup, delete the file, and run the utility MSGAUDIT to allow the VP system to rebuild
the file.
10517Error  writing box  to database
The VP system was unable to update its database with information for the specified box.  The problem is
probably localized in the BDTABASE.DVM file or the MDTABASE.DVM file.  If the problem persists, restore
backups of these files.  If that does not solve the problem, contact technical support.
10518Link error  while accessing box 
This error is encountered while updating the file MDTABASE.DVM, containing information on the
messages held in each mailbox.  If the problem persists, check the hard drive for errors.  If you do not
have a backup, delete the file, and run the utility MSGAUDIT to allow the VP system to rebuild the file.
10519File “” missing while auditing box 
During its automatic database audit, the VP system found that a voice message file was missing.  This
may be due to disk errors or a power failure, for example.  The VP system noted and corrected the 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-45problem by updating its database.  No further action is required.  If the problem persists, contact technical
support.
10520File “” missing while auditing Group box 
During its automatic database audit, the VP system found that a voice message file was missing for a
Group box message.  This may be due to disk errors or a power failure, for example.  The VP system
noted and corrected the problem by updating its database.  No further action is required.  If the problem
persists, contact technical support.
10521Link error  encountered while auditing box 
An internal error was detected during the VP system’s automatic audits.  If the problem persists, try
deleting the box, then adding it again.
10522Error  while allocating space for box 
The VP system had a problem allocating memory or disk space for a new box.  Check that the disk is not
full.
10523Error  while reading header info for box 
An error was encountered while the system was reading information about the messages in a box.  If the
problem persists, try deleting the box, and adding it again.  If that does not solve the problem, run the
utility MSGAUDIT to re-build the message database.
10524Error in new-message counts for box  ()
During its automatic database audit, the VP system found inconsistencies in the database.  It fixed these
automatically.  No further action is required.  If the problem persists, contact technical support.
10525Error in old-message counts for box  ()
During its automatic database audit, the VP system found inconsistencies in the database.  It fixed these
automatically.  No further action is required.  If the problem persists, contact technical support.
10526Cannot initialize box index
The VP system maintains an internal list of boxes while it is running.  It was unable to create this list.  If
the problem persists, contact technical support.
10527Cannot read box index
The VP system maintains an internal list of boxes while it is running.  It was unable to read this list.  If
the problem persists, contact technical support.