Select Page
Deciphering the Resulting Status Codes in RightFax

RightFax shows a status message for each fax in Faxutil and Webutil. To learn more about why a fax transmission may have failed, the fax history includes status codes that offer concise information. This Knowledge Base article helps to decipher these Resulting status codes.

Often, with failed faxes, information on the failure can be found in the transmission record for the fax.

Resulting Status Codes

RightFax shows the line status and the fax status for T.30 (PSTN) and T.38 (FOIP) fax transmissions. These status messages can be useful in analyzing fax errors and in helping to determine the nature of a failure (to assist with issue resolution).

However, these status messages, in conjunction with troubleshooting the telephony integration, can be useful in determining the nature of failures. As the success or failure of a fax transmission is entirely dependent on the telephony transport being used, these status messages can help to determine the underlying deficiency in end-to-end communication and can be used effectively to isolate an issue when combined with further troubleshooting and error reporting in the telephony network itself.

Interpreting the Resulting Status Codes

The fax history shows a Resulting fax status code. Both the first and second sets of numbers are gathered by the Brooktrout API to report on the call progress (reflected in the first set of numbers before the semi-colon) and the fax progress (reflected in the second set of numbers after the semi-colon).

A failure to send a fax using the server computer’s telephony integration can be generally classified into one of these two categories.

Call Setup Failures

Call setup failures occur when a call cannot be successfully placed to a dialed number. The first set of numbers can be helpful in determining call setup failures. This is especially true with Analog, Analog DID, BRI, and T1 integrations. For FoIP (either TR1034 ethernet enabled fax boards or SR140 “Boardless” fax boards), the Wireshark Network capture utility is considerably more useful for troubleshooting call setup errors.

First Set of Numbers – Call Progress Status

The first set of numbers represents the RightFax call status and the call line status. The first number is typically zero (“0”) and means that the call was placed. The second number can be found in Table 1 below.

Second Set of Numbers – Fax Progress Status

(This is generally where transmission failures are reflected.)

Transmission errors occur when a call is successfully placed from the fax server to the end point fax device (or from an end point sending device to the fax server), but the overall quality of the connection between the two end points is insufficient to convey the fax data effectively to or from the remote device.

The second set of numbers in the Resulting status code reflects the outcome of the fax transmission. This information does not yield any data about why a fax failed (that is, it does not indicate the specific reason why the communication between the two end points was unsuccessful). However, it does show what happened at the time that the fax failed.

For example, a Resulting status code of “0/339; 4/75” indicates that a DCN message was received from the remote device (a DCN is the signal sent from a t.30 device that states “I’m disconnecting”). This information indicates that the remote side terminated the call, but it does not indicate specifically why the remote side terminated the call. Therefore, since this information does not explain why the remote device terminated the call, it is more useful for identifying a behavior pattern, rather than for explaining the failure of an isolated fax call.

If you are having issues with RightFax Error Codes, or any other RightFax error, please contact us at 1-866-730-1700 or [email protected]

Table 1: RightFax Call Line Status

RightFax Call Line StatusMessage in HistoryStatus in Faxutil or Webutil
258Dial Er: no dial toneError: No Dial Tone
259Dial Er: no loop currentError: Phoneline Problem
260Dial Er: local in useError: Line in Use
301Normal BusyError: Busy
302Normal BusyError: Busy
303Fast BusyError: Busy
304Recall Dial ToneError: Phoneline Problem
305Confirmation toneError: Unknown Error
306PulseError: Unknown Error
308Ringing DetectedError: No Answer
309Double Ringing DetectedError: No Answer
316Answer (probably human)Error: Human Answered
317Answered, quiet followedError: Human Answered
318Dial tone after dialingError: Phoneline Problem
324Silence, no signal or CNGError: Phoneline Problem
325Ringing, no answerError: No Answer
326Group 2 Fax MachineError: G2 Fax Machine
327Special Info ToneError: Phoneline Problem
328Dead line (after dialing)Error: Human Answered
329Vacant tone (invalid phone num?)Error: Phoneline Problem
330Reorder tone (PBX/Carrier failure)Error: Busy
331No circuit tone (dead line?)Error: Phoneline Problem
332CNG fax tone detectedError: Unknown Error
333Remote off-hookError: Unknown Error
334Special CPError: Unknown Error
339Answer Tone DetectedSuccess

Table 2: Dialogic Status Types

Call StatusDialogic Call StatusDescription
0BT_STATUS_OKNormal return
2BT_STATUS_ERRORError return
5BT_STATUS_USER_TERMINATEDUser function caused termination
6BT_STATUS_TIMEOUTTimeout occurred
7BT_STATUS_ALERTAlert occurred

Table 3: Dialogic Return Codes from the Dialogic API 6.3

Dialogic CodeValueCodeDescription
BT_STATUS_ERROR2/3APIERR_BOARDCAPABILITYHardware or firmware does not support capability.
BT_STATUS_ERROR2/4APIERR_NOTCONNECTEDChannel not in proper state.
BT_STATUS_ERROR2/6APIERR_MEMORYMemory allocation error.
BT_STATUS_ERROR2/7APIERR_BADSTATEThe channel is not in a required state.
BT_STATUS_ERROR2/8APIERR_TOOSOONDialing was attempted too soon.
BT_STATUS_ERROR2/10APIERR_DRV_OPEN_ERRORDriver open call failed, invalid channel or driver not correctly installed.
BT_STATUS_ERROR2/12APIERR_VERSIONIncompatible driver version.
BT_STATUS_ERROR2/13APIERR_INVALID_PORTInvalid port; faxinit probably not run correctly.
BT_STATUS_ERROR2/14APIERR_RINGINGRinging during dialing attempt.
BT_STATUS_ERROR2/15APIERR_INFOPKT_NESTINGIndir infopkt nesting level too deep.
BT_STATUS_ERROR2/16APIERR_MAX_TAGSMaximum number of TIFF tags exceeded.
BT_STATUS_ERROR2/17APIERR_LOCK_FAILEDAn attempt to gain a lock failed.
BT_STATUS_ERROR2/18APIERR_INSUFF_BUFFERBuffer size too small to receive data.
BT_STATUS_ERROR2/19APIERR_INVALID_DEST_ADDRDestination address not found or invalid.
BT_STATUS_ERROR2/20APIERR_PACKET_CREATIONPacket or command creation error.
BT_STATUS_ERROR2/21APIERR_PACKET_PARSEPacket or command parse error.
BT_STATUS_ERROR2/24APIERR_DATADATA encountered during command processing.
BT_STATUS_ERROR2/25APIERR_INVAL_BOARD_PARAMInvalid parameter values received from firmware.
This blog is tagged as: Error | Failures | FaxUtil | Numbers | Results | RightFax | Status Codes | WebUtil

Join Our Newsletter

Quick Links

Popular Resources

Contact Us

If you would like to learn more or speak to one of our dedicated RightFax experts, please contact us using the request button below or call us directly at 866-730-1700.

Register for Exclusive Access to the

RightFax Resource Center

Sign-up to learn the ins and outs of your RightFax system and become an expert.

  • This field is for validation purposes and should be left unchanged.