Key Voice Voice Processing System Installation And Maintenance Manual

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-164002Out of Memory - Please Unload Any Resident Programs
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 and verify that there is 640 K
bytes total conventional memory available.
4101Mail Box  Cannot Find New Messages for Question Box 
Although the Question box has some new messages, the VP system was unable to find them in the
database.  Exit to DOS, and run the auditing utility program MSGAUDIT.
4102Mail Box  Cannot Find Old Messages for Question Box 
Although the Question box has some new messages, the VP system was unable to find them in the
database.  Exit to DOS, and run the auditing utility program MSGAUDIT.
4201Box  is a Member of Group Box , But is Not a Mail Box
Only mailboxes are allowed to be members of a Group box.  While performing message notification, the
VP system encountered a box that is not a mailbox, but that is a member of the specified Group box.
Remove this box from the Group box.
4202Cannot Read Information for Mail Box  in Group Box 
While performing message notification, the VP system was unable to access the specified member of the
Group box in the database.  This mailbox does not be notified of the new Group box message.  If the
problem persists, check the FILES statement in the CONFIG.SYS file.  This should be at least 40.
4401Mail Box  in Invalid OPEN State ()
This is an internal error.  If the problem persists, contact technical support.
4505Mail Box  in Invalid OPEN State  While Receiving Fax
This is an internal error.  If the problem persists, contact technical support.
4601Mail Box  in Invalid OPEN State 
This is an internal error.  If the problem persists, contact technical support.
4701Mail Box  in Invalid OPEN Supervisor State 
This is an internal error.  If the problem persists, contact technical support.
4702Invalid Supervisor-Function Request  From Mail Box 
This is an internal error.  If the problem persists, contact technical support. 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-174801Paging Module in Invalid State . Call Terminated
This is an internal error.  If the problem persists, contact technical support.
4802Not Enough Memory to Initiate Paging Module
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.
4901Delete-Queue Corrupted. Data =, , .  Queue Rebuilt.
When you ask the VP system to delete a message, the VP system does not delete the message
immediately, but places the request on a queue called delete-queue.  This queue is contained in the file
VMDELETE.Q.  When there is idle time on the system, the VP system processes entries on the delete-
queue.  As a safety precaution, the VP system regularly monitors this queue, to make sure the information
is valid.  This error message indicates that the VP system found the queue to be corrupted.  The VP
system deletes the queue, and re-creates a new (empty) delete-queue.  This results in some messages not
being deleted.  The mailbox owners find the messages are still in their mailboxes, and they can delete
them again.  The probable cause of the error is a hard drive problem.
4902Cannot Create Delete-Queue
When you ask the VP system to delete a message, the VP system does not delete the message
immediately, but places the request on a queue called delete-queue.  This queue is contained in the file
VMDELETE.Q.  When there is idle time on the system, the VP system processes entries on the delete-
queue.  As a safety precaution, the VP system regularly monitors this queue, to make sure the information
is valid.  This error message indicates that the VP system found the queue to be corrupted or missing, but
when it attempted to re-create the queue, it was unable to create the file VMDELETE.Q.  If the problem
persists, contact technical support.
4903Cannot Open Delete-Queue File  to Add Entry
When you ask the VP system to delete a message, the VP system does not delete the message
immediately, but places the request on a queue called delete-queue.  This queue is contained in the file
VMDELETE.Q.  When there is idle time on the system, the VP system processes entries on the delete-
queue.  This error indicates that the VP system was unable to add a request to the queue.  Make sure the
file VMDELETE.Q exists, and does not have its read-only attribute set.
4904Delete-Queue File Corrupted. Error =
When you ask the VP system to delete a message, the VP system does not delete the message
immediately, but places the request on a queue called delete-queue.  This queue is contained in the file
VMDELETE.Q.  When there is idle time on the system, the VP system processes entries on the delete-
queue.  As a safety precaution, the VP system regularly monitors this queue, to make sure the information
is valid.  This error message indicates that the VP system found the queue to be corrupted.  The VP
system deletes the queue, and re-creates a new (empty) delete-queue.  This results in some messages not
being deleted.  The mailbox owners find the messages are still in their mailboxes, and they can delete
them again.  The probable cause of the error is a hard drive problem. 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-184905Cannot Open Delete-Queue File  to Service it
When you ask the VP system to delete a message, the VP system does not delete the message
immediately, but places the request on a queue called delete-queue.  This queue is contained in the file
called VMDELETE.Q.  When there is some idle time on the system, the VP system processes entries on the
delete-queue.  This error indicates that the VP system was unable to access the queue to process the next
request.  Make sure the file VMDELETE.Q exists, and does not have its read-only attribute set.
5001Question Box  in Invalid State . Call Terminated
This is an internal error.  If the problem persists, contact technical support.
5003Cannot Create Data File 
While collecting digits in a Question box, the VP system was unable to create a file in which to store the
digits.  Check the FILES setting in the CONFIG.SYS file.  It should be at least 40.
5101Talking Classifieds Gateway  in Invalid State 
This is an internal error.  If the problem persists, contact technical support.
5201Event Received for Box , Whose Type is Invalid ()
The VP system tried to process the specified box, but its type is not one of the valid box types (for
example, mailbox, Routing box, etc.).  If the box number is valid, exit to DOS and run the program again.
If the problem persists, contact technical support.
5202Event  Received for Line  - No Such Line
The VP system received a request to process the specified line number.  However, there is not that many
lines connected to the system.
5203DOS Error  Reported on Line 
DOS reported an error on the specified line.  The VP system terminates the call.  If the problem persists,
contact technical support.  The most common DOS errors are listed below:Error NumberDescription2File not found3Path not found4Too many open files5Access denied6Invalid handle8Insufficient memory15Drive is invalid255Hardware problem on voice board 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-195204Event  Received on Line  is Not Valid For Outgoing Call
This is an internal error the system encounters while preparing to make an outgoing call.  If the problem
persists, contact technical support.
5205Invalid State / Event Combination on Line  ()
This is an internal error.  If the problem persists, contact technical support.
5206Line  in Invalid State 
This is an internal error.  If the problem persists, contact technical support.
5207Cannot Go To Box  - Unable To Read It From Database
The VP system attempted to route the call to the specified box, but was unable to retrieve information
about that box from the database file BDTABASE.DVM.  Make sure the box exists.  Exit to DOS, and check
the hard drive for errors.  Run the program again, and try to access the box.
5208 IVPC Port  Lost Communication With Phone System
The specified port lost communication with the phone system.  This can be due to the phone line being
disconnected or a fault in the PBX or VP system computer.
5209 IVPC Port  Re-established Communication With Phone System
The specified port lost communication with the phone system, but the problem has been corrected.
5301No Onhook-Acknowledgment From Hardware on Line 
While the VP system was clearing down a line, it did not get an acknowledgment from the voice board
that the line had returned to an on-hook state.  The VP system waits for 5 seconds for this
acknowledgment, then assumes that the line is on-hook anyway.  If the problem persists, contact technical
support.
5302Cannot Read Box  From File For Notification-Check
While performing checks for the message notification feature, the VP system was unable to retrieve
information about the specified mailbox from the database (the file in question is BDTABASE.DVM).  The
effect is that the mailbox is not notified about the message.  Make sure the box exists.  If it does, exit to
DOS, and check for hard drive errors. 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-205303Cannot Read Box  From File for Auto-Forward Check
While performing checks for the auto-forwarding feature, the VP system was unable to retrieve
information about the specified mailbox from the database (the file in question is BDTABASE.DVM).  The
effect is that a message may not be auto-forwarded from this mailbox.  Make sure the box exists.  If it
does, exit to DOS, and check for hard drive errors.
5304Line  is Not Idle, But Has Been Inactive Too Long. Forced Idle.
The VP system continually checks all lines in the system, to ensure that the lines do not get locked up due
to some error condition.  If a line is not in an idle state, but does not do anything for a 10 minutes, the VP
system assumes that the line has become locked up and forces it back to an idle state.  If the problem
persists, contact technical support.
5307No More Timer Records For Line .  Call Terminated
This is an internal error.  If the problem persists, contact technical support.
5308Key error . Data = 
The VP system encountered a problem while checking the security key.  Ensure the key is connected to
the PCs parallel port.
5309Mail box  exceeds limit of VCM users allowed (limit is )
VCM can be enabled for 10, 20, 30, or any certain number of users.  The VP system noted that although
VCM was enabled for a number of users, there was more than that number of mailboxes in the database
marked as VCM users.  Review all mailboxes in the database, and make sure you have not exceeded the
authorized number of VCM users.
5401Routing Box  in Invalid State .  Call Terminated
This is an internal error.  If the problem persists, contact technical support.
5402Unexpected End-of-File In File 
There is an error in the file format of the specified file.
5403Comma Missing in File  For Box 
There is an error in the file format of the specified file.
5404Error in Database-Look Up File , Box 
The database-lookup file format is incorrect.  See section 7 for information on the correct format. 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-215405Cannot Open Database Lookup File , Box 
The database-lookup file is missing.  Check the spelling of the filename.  Check the hard drive for errors.
5406Unknown Digit Type () Received on Line 
See error 3402.
5601Voicemail Gateway in Invalid State (). Call Terminated.
This is an internal error.  If the problem persists, contact technical support.
5602Voicemail Gateway Was Unable to Open Box 
Although the correct password was entered, the VP system was unable to open the specified box, as it was
unable to retrieve the box information from the database (file BDTABASE.DVM).  Try the operation again.
If you still cannot open the mailbox, exit to DOS, and check the hard drive for errors.
5701Message-Wait Module in Invalid State .  Call Terminated
This is an internal error.  If the problem persists, contact technical support.
5702Cannot Queue Message-Wait Request for Box 
When the VP system needs to turn on / off a message waiting lamp, it places a request on the message-
wait queue.  It then processes the queue when a line is available.  This error message means that the VP
system was unable to place a request on the queue.  This may happen if the system is extremely busy, or
if you do not have enough lines set up to allow message waiting calls.  The effect is that the message
waiting lamp associated with the specified mailbox may not be turned on or off at the appropriate time.
Also, check that there is dial tone on the lines you are using to activate message waiting lamps.
5703Msg-Wait Module Cannot Read Member  From Group Box 
While the VP system was attempting to operate a message waiting lamp for a the specified member of the
Group box, it encountered a problem retrieving information about the mailbox from the database (file
BDTABASE.DVM).  The effect is that the message waiting lamp associated with the specified mailbox does
not be turned on at the appropriate time.
5704Not enough memory for message-waiting queues
The VP system ran out of memory during initialization.
5801Not Enough Memory for Digit-Translation Tables
The VP system ran out of memory during initialization. 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-225802Too many Digit-Translation Rules, Maximum Allowed Is 
The digit-translation file (TRANS.TXT) contains too many translation rules.  Delete some of the rules.  See
section 7 for more information on the format of the digit-translation file.
5803Illegal Character # In Digit-Translation Rule: 
One of the rules in the digit-translation file (TRANS.TXT) contains an illegal character.  See section 7 for
more information on the format of the digit-translation file.
5804Left Side of Digit-Translation Rule Too Long: 
The part of the specified digit-translation rule on the left of the “=” sign is too long (in the file
TRANS.TXT).  See section 7 for more information on the format of the digit-translation file.
5805Right Side of Digit-Translation Rule Too Long: 
The part of the specified digit-translation rule on the right of the “=” sign is too long (in the file
TRANS.TXT).  See section 7 for more information on the format of the digit-translation file.
5806EQUAL Sign Missing From Digit-Translation Rule: 
The “=” sign is missing from the specified digit-translation rule in the file TRANS.TXT.  See section 7 for
more information on the format of the digit-translation file.
5807Digit-Translation Character # Not Defined on Left-Side: 
In the specified digit-translation rule in the digit-translation file (TRANS.TXT), there is an identifier on the
right side of the “=” sign that is not defined on the left side.  See section 7 for more information on the
format of the digit-translation file.
5808Wrong Format For Greeting.  Example of Correct Form is 4X=X*,*:G2
A digit-translation rule using the Greetings by Reason Code feature has been entered incorrectly.  The
correct format is a standard digit translation rule, followed by a colon (:), the letter G, and the desired
greeting number.
5901Directory-Box in Invalid State (). Call Terminated.
This is an internal error.  If the problem persists, contact technical support.
6001Invalid Response: 
When you are recording or playing a box greeting, the VP system asks you for a language number and/or
a greeting number (depending on whether you are using multiple languages and/or multiple greetings).
The language number must be within the range indicated (this can be changed via the configuration file
VM.CFG, see section 12 for details).  The greeting number must be within the specified range 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-23(configurable via the mailbox’s assigned class of service).  You may also press  to cancel the play
or record operation.
6002Cannot Open Screen Information File 
The VP system needs to read the specified file to retrieve information on the various screen layouts.  It
was unable to open the file.  Make sure the file exists.  Make sure the FILES statement in the CONFIG.SYS
file specifies at lease 40 files.
6003Error  in Screen-Information File  (data =)
The VP system needs to read the specified file to retrieve information on the various screen layouts.
While reading the file, the VP system found that its format was not correct.  Copy the file from the
distribution disks, and run the program again.
6004Not Enough Memory for Screen Information
The VP system ran out of memory while reading screen-formatting information.
6005Cannot Create New Screen ().  Probably Insufficient Memory.
The VP system was unable to allocate enough memory for its screen information.  It most likely ran out
of memory.
6006Cannot Allocate Memory for New Screen ()
The VP system was unable to allocate enough memory for its screen information.  It most likely ran out
of memory.
6101Not Enough Memory for Line Information
The VP system needs to allocate a small amount of conventional memory to hold line-related information.
There was not enough free memory to allow this allocation.
6102Label Information Corrupted
The VP system was unable to read the file containing screen formatting information (ACCER.DAT).  Copy
the file from the distribution disks.
6103Label Information File Missing
The VP system was unable to find the file containing screen formatting information (ACCER.DAT).  Copy
the file from the distribution disks. 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-246104Not 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.
6105Error in Config File - Line 
An incorrect or invalid parameter has been entered in the configuration file VM.CFG on line .
Locate the error by counting down lines of text from the top of the file (blank lines are not counted).  See
section 12.
6201Not Enough DOS 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.
6202Not Enough EMS Memory for Box Information
The VP system attempted to allocate EMS memory for its own use, but found that there was not enough
free EMS memory.
6203Internal EMS Error  on Line . 
This is an internal error.  If problem persists, contact technical support.
6204Tried to Access EMS for Line .  Highest Line is 
This is an internal error.  If problem persists, contact technical support.
6301Internal Driver-Interface Error . Data =  
Internal logic error.  If the problem persists, contact technical support.
6302Cannot Open Call-Progress File 
The VP system was unable to access the specified file, which contains information on the various call-
progress tones (for example, ring-tone, busy-tone).  Run the call-progress training program to create the
file (see section 13).  The effect of this error is that the VP system uses a default set of call-progress tone
parameters when it is making outgoing calls (for example, for call transfer or message notification).
These defaults work in most cases.  However, in some cases this may result in the VP system not being
able to tell the difference between a telephone that is ringing and one that is busy, or it may fail to detect
when the called party has answered the call. 
						

							INSTALLATION AND MAINTENANCE MANUAL 4/0018-256303Error  Reading Call-Progress File. Data = , 
The VP system was unable to read the information in the specified file, which contains information on the
various call-progress tones (for example, ring-tone, busy-tone).  The file may be corrupted.  Run the call-
progress training program to re-create the file (see section 13).  The effect of this error is that the VP
system uses a default set of call-progress tone parameters when it is making outgoing calls (for example,
for call transfer or message notification).  These defaults work in most cases.  However, in some cases
this may result in the VP system not being able to tell the difference between a telephone that is ringing
and one that is busy, or it may fail to detect when the called party has answered the call.
6304Error  in Global-Parameters File 
In the specified file, the VP system expected to find special setup information, but the format of the
information was not correct.  The file may have become corrupted.  Restore the latest backup copy of the
file, or contact technical support.
6305Error  in Channel-Parameters File 
In the specified file, the VP system expected to find special setup information, but the format of the
information was not correct.  The file may have become corrupted.  Restore the latest backup copy of the
file, or contact technical support.
6306Error  Reported from Get Event
The Rhetorex RDSP driver reported an error while the VP system was polling it for events.  If the
problem persists, contact technical support.  The most common errors are listed below:Error NumberDescription4System not active5Hardware error9Bad line number16Insufficient buffer memory34EMS memory error6307Unknown Digit Type  on Line 
A digit was received on the specified line, but it was invalid.  If the problem persists, contact technical
support.
6308DOS Seek Error During Play / Record Operation on Line 
DOS reported an error to the VP system when it tried to start a play or record operation on the specified
line.  The effect is that the particular prompt does not play, but the call continues.  If the problem persists,
contact technical support.