Facsys Error Codes
Contents |
Demo SecurTracSecurTrac for Notes/DominoSecurEsign for Notes/DominoTestimonialsRecorded DemoRequest Demo SecurSearchSecurSearch for Notes/DominoRecorded DemoRequest Demo PurchaseContact Extracomm SalesFind an Authorized facsys local hardware error ResellerBecome an Authorized Reseller SupportExtraFax for Exchange
Facsys Support
FAQExtraFax for Notes/Domino FAQExtraTxt FAQSecurTrac FAQSupport Discussion ForumProduct DocumentationProfessional ServicesRemote Technical Support rightfax transmission error receive failure phase b DownloadExtraFax for ExchangeExtraFax for Notes/DominoExtraTxtSecurTracSecurEsignSecurSearchOut-of-Office ManagerDrivers & Utilities LanguageEnglishChineseDanishItalianPolishPortugueseRomanianRussianSwedishTurkish It appears that your browser does not support JavaScript, or rightfax status codes you have it disabled. This site is best viewed with JavaScript enabled. If JavaScript is disabled in your browser, please turn it back on then reload this page. Print this pageBrooktrout Error CodesLink: http://www.extracomm.com/Extracomm/FAQ.NSF/FAQs/1d85d6a58c05403b882567d8006808c4Apply to: ExtraFax for Exchange; ExtraFax
Resulting Status Code (0/352; 4/105): Receive Failure (phase B)
for Domino All versionsLast Modified Date: 02/04/2015 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 CodesDescription 1HNG_RNG_DETRing detected without a successful handshake. 2HNG_ABORTCall aborted. 3HNG_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. 4HNG_ISDN_DISCONNECTISDN disconnection. 5HNG_INVAL_POLL_ATTInvalid polling attempt. 11HNG_T1_TIMEOUTNo answer, T.30 T1 time-out. 20HNG_XMITB_TIMEOUTUnspecified transmit Phase B error. 21HNG_XMITB_NORMRemote cannot receive or send. 22HNG_XMITB_MISCCOMREC error, Phase B transmit. 23HNG_XMITB_COMREC_VCNRCOMREC invalid command received
HELP Contact Support Ask Question Support Plans RESOURCES System Requirements Software Updates Document Library FEEDBACK Service Feedback Support Escalation Unsustainable Connections - Connection Error Definitions Edit 5 … 0 Tags No tags Notify RSS Backlinks Source Print Export (PDF) Unsustainable rsprec error Connections - Connection Error Definitions Unsustainable Connections are generically a failure of the fax machines rightfax line broken (no loop current) or fax servers to communicate with one another. The most common cause of these errors are line impairments such as noise or echo
No Loop Current Fax Machine Error
on the line. Line impairments can be either on the fax server's line, somewhere in the telephone network (PSTN), or on the remote fax machine's line. List of Unsustainable Connection Errors Here are technical descriptions of each specific Unsustainable https://www.extracomm.com/Extracomm/FAQ.NSF/0/1D85D6A58C05403B882567D8006808C4 Connection error. The exact error code will vary depending on fax driver used. 27987 Can't Agree on Bit Rate The modem and the remote unit couldn't fall back to or agree upon any bit rate. There are two things that could cause this: - The driver was set up to connect at only certain bit rates which the remote unit wasn't capable of. For example, let's say that only 7200 and 9600 bps were enabled to prevent http://kb.faxback.com/Unsustainable+Connections+-+Connection+Error+Definitions fall back to 4800 bps or slower on a noisy line(hence keeping phone bills smaller). If a connection is made to a remote unit that only supports 2400 or 4800 bps, then a connection can not be made, so this error results. - The more likely suspect is that the telephone line is either very noisy, or the frequency response of the line is servely attenuated at the high end of the pass band. If the connection doesn't sound really "hissy" or "crunchy" when you dial that number with a regular phone, the line length compensation settings may help. 27988 Invalid Training Response After sending 1.5 seconds of training data, the remote unit should have sent a CFR or FTT frame. It sent something else. 27989 Send Max TSI DCS Training This occurs if a FTT or CFR is not received at least once after sending 3 DCS/training sequences. This is usually caused by bad loss of carrier detection on the other end and/or response syncronization. 27990 No Response After End of Page This occurs after sending 3 end of page commands without any response from the remote unit. 27991 Invalid End of Page After sending the end of page command to the remote, the remote should have sent a MCF, PIP, RTP, PIN, or RTN response. It sent something else. 27992 Unexpected Disconnect Under normal circumstances, the send
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 14 Oct 2016 01:02:51 GMT by s_ac4 (squid/3.5.20)