12.07.2015 Views

Avaya IR Install and Troubleshooting Guide - Avaya Support

Avaya IR Install and Troubleshooting Guide - Avaya Support

Avaya IR Install and Troubleshooting Guide - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Investigating operations problemsExecute UNIX comm<strong>and</strong> failedMost likely, the problem is with the comm<strong>and</strong> or shell script. Make sure that the comm<strong>and</strong> orshell script that was attempted works when executed manually. If it does, make sure that itsfull path name is provided to the script.Fax file or text file not foundTake action depending on whether the problem occurred in transmission or receipt of the fax:• If the request to transmit a fax file to the caller failed, verify that the fax file exists either inthe Fax Loading <strong>and</strong> Printing screen or at the full path specified in the voice responseapplication.• The caller did not receive the fax requested, consider manually transmitting the faxmessage requested by the caller using the delivery number contained in the errormessage.Out-of-call fax transmission failedYou learn of this problem through the fax report. Follow the repair procedure provided for theFAX001 message.Interpreting negative fax valuesWhen a negative return value of a FAX action indicates that an error has occurred, use thefollowing list of return values to determine the cause of the error. These values are found inthe fax_tool.h file.Value Meaning-1 Another faxit comm<strong>and</strong> is executing.-2 Fax transmission failed (internal).-3 Channel was denied (internal).-4 File cannot be opened or does not exist-5 There are no previous queued faxes.-6 No background file was found (obsolete).-7 No foreground file was found (obsolete).-8 faxit comm<strong>and</strong> timed out (internal).-9 File linking failed (obsolete).-10 File opening failed (obsolete).-11 File queued before fax (obsolete).Issue 3 March 2003 77

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!