Mitel MiVoice Business Troubleshooting Manual page 253

Hide thumbs Also See for MiVoice Business:
Table of Contents

Advertisement

ERROR
NUMBER
SEVERITY
4720
ERROR
4721
4722
4723
ERROR
4724
ERROR
4726
INFO
4718
ERROR
DESCRIPTION
Incorrect File Handle for Erase
In all cases, a message could not be deleted due to one
of the following with respect to the corresponding MSG
file:
• bad file handle
• message number is out of range of the system default
MSG tag is incorrect
x_keep(handle,msg_no,function) returning ret
This error is displayed if something goes wrong with
saving a message after it has been listened to.
handle DOS handle to the MSG file of the mailbox in
question.
msg_no - Which message do we want to keep for the
mailbox in question
function 0=Keep, 1=Mark Unread
ret return value of x_keep()
-1 = lseek() or read() into MSG file failed
-2 = file handle bad, or bad tag in MSG file
x_stamp Corrupted Directory
The attempt to time stamp a message failed because the
associated MSG file did not have the proper tag inside of
it.
deleting 0 length file: f
This message is generated when a file that was opened
to receive a recording is closed and is of zero length. For
example, when leaving a message, if the user hangs up
before the beep, this will leave around a zero length file.
Hence when this file is deleted, the above message
occurs.
x_copy(filename,start,len,dfh,dstart),r=bytes_read,w=
bytes_written
This function is used to copy parts of a message from one
file to another. Mostly in the case of adding a comment to
a forwarded message or appending to a message just
recorded.
This error occurs if the number of bytes_read does not
equal the number of bytes_written. Or, if the number of
bytes_written does not equal the length.
Using Logs
SOLUTION/ACTION
Contact your service
representative.
If isolated incident, no
action required. If it
continues with only the
same mailboxes,
listen to all messages
in mailbox and then
delete the MSG file.
Leave a new message
to test.
If this does not help,
contact your service
representative
If isolated incident, no
action required. If it
continues with only the
same mailboxes, listen
to all messages in
mailbox and then
delete the MSG file.
Leave a new message
to test.
If this does not help,
contact your service
representative
No action required
Page 11 of 16
245

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents