FaxBack Port Server - Manual - Manual (Page 49)

Chapter 15 – Error Codes
0x6D00 – IPFax Driver
6D2F Bad open ring 0 / kernel mode driver: There is another instance of the IPFax driver already loaded, or the
Windows account attempting to load the driver does not have Administrative permissions.
6D47 WsaSendTo error – The gateway address is not a valid IP address.
6D48 SIP Invite sent 7 times with no response: The gateway did not respond to SIP Invite requests. Check the
configured gateway IP address, and any firewall in between.
6D49 Timeout waiting for invite final response: Call was not answered in the configured time period.
6D4B Timeout waiting for reinvite to fax: The call connected, but the gateway failed to send a reinvite for T.38
either because there were no fax tones detected on the remote side or because the gateway does not
support T.38.
6D4F SIP bye received before fax was completed: The remote fax device hung up before the fax was completed.
The gateway also did not include a Q.850 cause code for this disconnect, otherwise this would likely be
0x7210 Normal Call Clearing instead.
6D51 No Answer, remote device did not respond to handshake: The call connected and T.38 communication was
established, but the remote device failed to respond to repeated attempts to handshake. This commonly
occurs when using T38_INVITE to initiate T.38 media without the initial RTP audio phase. The timer is 35
seconds.
6D55 Unsustainable Connection, no FTT or CFR received after 3 DCS/training sequences: The call connected and
T.38 communication was established. The receiving and sending devices exchanged CSI/DIS and
TSI/DCS/training signals. After that, the receive side is expected to send a CFR (confirmation) or FTT (failure
to train), it did neither. Handshaking was attempted and failed twice more, at which point IPFax terminated
the call.
6D56 Unsustainable Connection, no response after sending 3 end of page commands: After reaching the end of
the page, IPFax sends an end‐of‐page command (MPS) and expects to receive an acknowledgment (MCF)
from the remote device. IPFax did not receive the MCF and attempted to resend it twice more. After the
third failure to respond, IPFax terminated the call. This can be caused by the remote device hanging up
without notifying the TDM network (POTS lines lack such notification), line impairment such that the
gateway could not detect and encode the MCF command, noise such that our MPS was not detected by the
remote device, or packet loss such that either the MPS or the response MCF was lost, or latency such that
the MCF or MPS was delayed. In the case of packet loss, insure that low‐speed redundancy is enabled.
6D58 Unsustainable Connection, receiver sent DCN: Normally, the receiver should never send a DCN disconnect
signal. This could be due to line impairment causing a timeout on the receive side, or a user manually
pressing a cancel button on the receiving fax machine.
6D6D Error resolving URI to IP address: A domain name was specified as the gateway address, and could not be
resolved, either because the name is not defined or the DNS server could not be contacted.
6D77 Special Information Tone detected: A SIT has been received. This can include “number out of service” and
other PSTN errors beyond the TDM network (where Q.850 cause codes would be used instead).
6D78 Busy tone detected: The destination number is busy at a point beyond the TDM network.
6D79 Talking detected with no fax: The call connected, but either there was no reinvite for T.38, or the RTP
stream analysis indicated that there was a voice on the line. This can be caused by a human or answering
machine answering the call. Also some service providers play a recording for out‐of‐service numbers without