Brooktrout Error Codes

Link:  http://www.extracomm.com/Extracomm/FAQ.NSF/FAQs/1d85d6a58c05403b882567d8006808c4
Apply to:  ExtraFax for Exchange; ExtraFax for Domino All versions

Last Modified Date:  11/07/2019


Brooktrout Error Codes

The following is a list of general Error Return Codes for Booktrout fax boards. Reference this with the errors you are getting when sending or receiving a fax, this will aid you in the troubleshooting process.

Return Codes
Description
1
HNG_RNG_DETRing detected without a successful handshake.
2
HNG_ABORTCall aborted.
3
HNG_NO_LOOP_CURRENTNo loop current or A/B signaling bits. Note that if someone had dialed to your fax server and then hung up, then the fax server would generate this return code.
4
HNG_ISDN_DISCONNECTISDN disconnection.
5
HNG_INVAL_POLL_ATTInvalid polling attempt.
11
HNG_T1_TIMEOUTNo answer, T.30 T1 time-out.
20
HNG_XMITB_TIMEOUTUnspecified transmit Phase B error.
21
HNG_XMITB_NORMRemote cannot receive or send.
22
HNG_XMITB_MISCCOMREC error, Phase B transmit.
23
HNG_XMITB_COMREC_VCNRCOMREC invalid command received.
24
HNG_XMITB_SERSPREC error.
25
HNG_XMITB_DCS_FTCDCS send three times without response.
26
HNG_XMITB_DIS_FTCDIS/DTC received three times; DCS not recognized.
27
HNG_XMITB_TRAINFAILFailure to train.
28
HNG_XMITB_RSPREC_VCNRRSPREC invalid response received.
29
HNG_XMITB_COMREC_DCNDCN received in COMREC.
30
HNG_XMITB_RSPREC_DCNDCN received in RSPREC.
33
HNG_PHASEB_INCOMPAT_FMTIncompatible fax formats, for example, a page width mismatch.
34
HNG_XMITB_INVAL_DMACNTInvalid DMA count specified for transmitter.
35
HNG_XMITB_FTM_NOECMBinary File Transfer specified, but ECM not enabled on transmitter.
36
HNG_XMITB_INCMP_FTMBinary File Transfer mode specified, but not supported by receiver.
37
HNG_XMITB_INCMP_EFFRemote does not support EFF page options required by host.
38
HNG_XMITB_NOEFFRemote does not support EFF page coding.
40
HNG_XMITD_RR_NORESNo response to RR after three tries.
41
HNG_XMITD_CTC_NORESNo response to CTC, or response was not CTR.
42
HNG_XMITD_T5TO_RRT5 time out since receiving first RNR.
43
HNG_XMITD_NOCONT_NSTMSGDo not continue with next message after receiving ERR.
44
HNG_XMITD_ERRRES_EOREOPERR response to EOR-EOP or EOR-PRI-EOP.
45
HNG_XMITD_RTN_DCNTransmitted DCN after receiving RTN.
46
HNG_XMITD_PPR_EOREOR-MPS, EOR-EOM, EOR-NULL, EOR-PRI-MPS, or EOR-PRI-EOM sent after fourth PPR received.
51
HNG_XMITD_SERSPREC error.
52
HNG_XMITD_MPS_FTCNo response to MPS, repeated three times.
53
HNG_XMITD_MPS_VCNRInvalid response to MPS.
54
HNG_XMITD_EOP_FTCNo response to EOP repeated three times.
55
HNG_XMITD_EOP_VCNRInvalid response to EOP.
56
HNG_XMITD_EOM_FTCNo response to EOM, repeated three times.
57
HNG_XMITD_EOM_VCNRInvalid response to EOM.
60
HNG_XMITD_RSPREC_DCNDCN received in RSPREC.
61
HNG_XMITD_PPSNULL_NORESNo response received after third try for PPS-NULL.
62
HNG_XMITD_PPSMPS_NORESNo response received after third try for PPS-MPS.
63
HNG_XMITD_PPSEOP_NORESNo response received after third try for PPS-EOP.
64
HNG_XMITD_PPSEOM_NORESNo response received after third try for PPS-EOM.
65
HNG_XMITD_EORNULL_NORESNo response received after third try for EOR-NULL.
66
HNG_XMITD_EORMPS_NORESNo response received after third try for EOR-MPS.
67
HNG_XMITD_EOREOP_NORESNo response received after third try for EOR-EOP.
68
HNG_XMITD_EOREOM_NORESNo response received after third try for EOR-EOM.
70
HNG_RCVB_TIMEOUTUnspecified receive Phase B error.
71
HNG_RCVB_SERSPREC error.
72
HNG_RCVB_MISCCOMREC error.
73
HNG_T2_PNOTRECT.30 T2 time-out, expected page not received.
74
HNG_RCVB_T1_TIMEOUTT.30 T1 time-out after EOM received.
75
HNG_NORMAL_RCVDCN received in COMREC. While this value is considered by the firmware to be a successful fax receive result, if it occurs in conjunction with BT_STATUS_ERROR_HANGUP, it still indicates that an error has occurred.
76
HNG_RCVB_RSPREC_DCNDCN received in RSPREC.
77
HNG_T2_TIMEOUTT.30 T2 time-out, expected page received.
78
HNG_RCVB_INVAL_DMACNTInvalid DMA count specified for receiver.
79
HNG_RCVB_FTM_NOECMBinary File Transfer specified, but ECM not supported by receiver.
101
HNG_RCVD_SE_VCNRRSPREC invalid response received.
102
HNG_RCVD_COMREC_VCNRCOMREC invalid response received.
103
HNG_RCVD_T3TO_NORESPT3 time-out; no local response for remote voice interrupt.
104
HNG_RCVD_T2TOT2 time-out; no command received after responding RNR.
105
HNG_RCVD_DCN_COMRECDCN received for command received.
106
HNG_RCVD_COMREC_ERRCommand receive error.
107
HNG_RCVD_BLKCT_ERRReceive block count error in ECM mode.
108
HNG_RCVD_PGCT_ERRReceive page count error in ECM mode.
109
HNG_RCVD_EOREOR received in phase D.
110
HNG_RCVD_RNRTOTimeout while repeating RNR.
150
HNG_RCVC_EOL_TIMEOUTNo EOL received in a 5-second period.
151
HNG_RCVC_BAD_MMRBad MMR data received from remote.
152
HNG_RCVC_ECM_ZERO_LINESZero lines received from remote in ECM mode.
240
HNG_INTERRUPT_ACKNo interrupt acknowledges, time-out.
241
HNG_COMM_FAULTLoop current still present while playing reorder tone after timeout.
242
HNG_T30_HOLDUPT.30 holdup time-out.
243
HNG_HOLDUP_DCNDCN received from host in receive holdup section for FAX PAD mode.
244
HNG_HOLDUP_DCN_NON_FPADDCN received from host in receive holdup section for non-FAX PAD mode.
258
DIAL_NO_DIAL_TONENo dial tone detected. Try checking the line and switch.
259
DIAL_NO_LOOP_CURNo loop current detected. Try checking the line and switch.

Note:
In ExtraFax User Preferences document, there is a setting called "Fax Number" (i.e. the PersonalFaxNumber field), which allows entering of a custom fax number to be displayed in the fax cover page. By default, if a value has been specified for this setting, then ExtraFax's Pre-TransmissionProcessing agent will copy that value to the AppCallerID field of the outgoing fax job, which controls the calling party number to be used by the Brooktrout program. This will work if the specified calling party number is a valid number. However, for some telcos, setting the calling party number with an invalid value is not allowed and may cause error. If that is the case, try setting the "Disable Using Personal Fax Number as the Calling Party Number" option in ExtraFax Server Configuration document to "Yes", which is available since ExtraFax 8.0.1.
260
DIAL_LOCAL_IN_USELocal phone in use successfully.
261
DIAL_TRUNK_BUSYBusy trunk line detected.
265
DIAL_SLOT_BUSYT1 time slot busy.
266
DIAL_CALL_COLLISIONRinging detected during dialing.
267
DIAL_NO_WINK2nd or later wink missing for Feature Group D.
301
FCP_BUSY1Normal busy; remote end busy (off-hook). Busy signal received after the maximum number of retries, resend the fax at a later time.
302
FCP_BUSY2Normal busy; remote end busy (off-hook). Used instead of BUSY1 in certain countries. Busy signal received after the maximum number of retries, resend the fax at a later time.
303
FCP_ROBUSYReorder or fast busy; indicates that telephone company trunk lines are busy; on PBXs, indicates no available outside lines. No available outside lines. Try dialing the number from another phone. Try checking the line.
304
FCP_RECALLRecall dial tone detected; signal generated when calling another party while already connected to one or more parties (for example, conference calling, call waiting). Number dialed is not a fax number. Try dialing the number from another phone to verify the number is a fax number.
305
FCP_CONFIRMConfirmation tone; automated equipment acknowledges successful completion of caller requested feature (for example, call forwarding). This is not G2 confirmation tone (CFR2). This indicates there is a problem with the line, switch, or card. Try dialing the number from another phone to verify the number.
308
FCP_RING1Ringback detected; remote end is ringing. The Central Office connected to the dialled number generates this signal.
309
FCP_RING2Ringback detected; remote end is ringing. The Central Office connected to the dialed number generates this signal. Also known as double-ring, it is used in the U.K.
316
FCP_HUMANAnswer (probable human) detected; does not match any other expected call progress signal patterns.
317
FCP_ANSWERRemote end answered call; can occur immediately after a break in the ring-back cycle; like HUMAN, does not match any other call progress signal patterns, but is marked by silence. Number dialed is not a fax number. Try dialing the number from another phone to verify the number is a fax number.
318
FCP_DIALTONDial tone detected; usually indicates the dialing sequence did not break dial tone. This occurs when you did not access an outside line. Could be an invalid number or dialing configuration incorrect.
Related Support FAQ...
324
FCP_SILENCEIn VOICE mode, after dialing, no signal detected during the silence timeout. In ANSWER mode, no fax CNG tone detected after answering a call. Try dialing the number from another phone to verify the number is a fax number. Try checking the line and switch.
325
FCP_RNGNOANSIndicates the remote end was ringing but did not answer. In fax mode, this result occurs after the ced_timeout (default: 40 secs) has expired and the line continues to ring (You can adjust the value of these timeout parameters in the btcall.cfg configuration file). Try dialing the number from another phone to verify the number is a fax number.
326
FCP_G2DETCTGroup 2 fax machine detected; remote machine is capable of sending and receiving G2 facsimiles only. Try checking the line.
Related Support FAQ...
327
FCP_SITINTCIntercept tone detected; remote end originating failure; invalid telephone number or class of service restriction. With the ISDN board, this can also indicate a datalink mis-match (ptp or pmp). Possible bad number or phone service is down. Try dialing the number from another phone to verify the number is a fax number. If number is a valid fax number then try checking the line.
328
FCP_QUIETAfter dialing the number, no energy detected on the line for the wait_for_ced timeout period; possible dead line. The line is down. Try dialing the number from another phone to verify the number is a fax number.
Related Support FAQ...
329
FCP_SITVACODEVacant tone detected; remote originating failure; invalid telephone number. Possible bad number. Try dialing the number from another phone to verify the number is a fax number.

Note:
In ExtraFax User Preferences document, there is a setting called "Fax Number" (i.e. the PersonalFaxNumber field), which allows entering of a custom fax number to be displayed in the fax cover page. By default, if a value has been specified for this setting, then ExtraFax's Pre-TransmissionProcessing agent will copy that value to the AppCallerID field of the outgoing fax job, which controls the calling party number to be used by the Brooktrout program. This will work if the specified calling party number is a valid number. However, for some telcos, setting the calling party number with an invalid value is not allowed and may cause error. If that is the case, try setting the "Disable Using Personal Fax Number as the Calling Party Number" option in ExtraFax Server Configuration document to "Yes", which is available since ExtraFax 8.0.1.
330
FCP_SITREORDReorder tone detected; end office (PBX) or carrier originating failure. Possible problem with the line coming into the Server. This will normally be a fast busy signal. Try dialing the number from another phone to verify the number.
331
FCP_SITNOCIRNo circuit detected; end office or carrier originating failure, possible dead line. No line is detected which could be a problem with the line, switch, or card.
332
FCP_CNGDETCTCNG fax calling tone detected.
333
FCP_RMTOFFHKRemote fax machine went off-hook (also known as Answer Supervision).
339
FCP_ANSWER_TONE_DETECTFax machine detected; usually a fax CED tone, but also fax V.21 signals when the remote machine does not send a CED tone before it sends the fax protocol information. Called a fax machine but it did not send the proper protocol. Could be a problem with the fax machine that is receiving the fax. Try resending the fax.
340
FCP_UNKNOWNAn error occurred due to an unknown cause. Try Resending the fax.
348
FCP_ISDN_CALL_PROGRESSBy enabling call progress on an ISDN D channel, one of the following values will be in the second byte of the FIFO buffer:
4: CALL_PROCEEDING: Call is proceeding normally.
5: CALL_ALERTING: Ringback detected; remote end is ringing.
6: CALL_CONNECTED: Call is connected.
7: CALL_DISCONNECTED: Call was disconnected.
Try checking the line and switch.
349
FCP_ISDN_CALL_COLLISIONIndicates that a call collision occurred on the ISDN line. Indicates there is a call going out on the same line as a call coming in. Try checking the line and switch.
500
HNG_ERROR_INTERRUPTAn error interrupt occurred, indicating a problem with the board too severe to continue.
501
HNG_INTERRUPT_OVERRUNThe application was unable to process interrupts from the board fast enough, and information was lost.
502
HNG_UNEXPECTED_IRSDONEThe channel generated an unexpected 03 (reset done) or 7F interrupt, indicating the existence of a firmware or hardware problem.
503
HNG_IOCTL_ERRORAn API command to the driver returned an error value, indicating that the driver or the operating system detected an error. This error often occurs when a channel locks up.
504
HNG_OVERLAY_DLOAD_ERRError reported at termination of fax overlay download.
505
HNG_MAX_TIMEOUTMaximum timeout exceeded. This code occurs when the user configuration file parameter max_timeout has been enabled and the specified timeout has expired.

You can also try to look for additional information from the following documentation: