Overview

FaxMaker will call any fax that fails from phase B through phase E a call failed: 46 error, depending on the fax device. An analog or Brooktrout device will receive a handshaking error, rather than a call failed: 46 error.

The symptoms include:

• Incoming faxes are successfully received, but sending faxes gives Call Failed: 46.
• Receiving faxes gives Call Failed: 46. 

This error can be caused by many things. A shortlist is provided below, but whatever stops the transmission of the fax from completing successfully can be a cause:

• Older or degraded lines
• Electronic interference with fax lines
• Sharing fax lines for phone use 
• One line for multiple fax devices
• Incompatible fax equipment (normally deals with older devices)
• Transmission speeds higher than fax lines allow
• Network congestions if using fax over IP
• Attempting to use digital phone lines with analog fax devices
• Changes to systems used in conjunction with FaxMaker

One thing to note is that the cause may not always be within the user's control. It could be on either side of the DMARC (demarcation point) - the point at which the provider's responsibility stops and the end-users responsibility starts.

Workflow

Instructions

Review the Line Options

Check the FaxMaker Configuration > Lines and Devices area for the following items on the Line Options tab of each line:

• Verify that the Max. resolution is set to Fine (200x200dpi).
• Verify that the Max. speed is not set to "Maximum available"; start with a lower value, like 14400bps, and gradually increase according to your tests.
• Verify that a dial prefix is not needed for your environment.

Review SR140 + T38 configuration

Follow the instructions on Call Failed 46 sending faxes with SR140 when facing the issue with a combination of the SR140 and T38-Only.

Check AppendDomainToClip and UseSenderFaxNumber

When using a FoIP device and having issues while sending from email, you may need to set the AppendDomainToClip and/or UseSenderFaxNumber keys in the registry.

Review XCAPI version and licensing

When using XCAPI, review the instruction from Error 'Called Failed 46' when sending fax (XCAPI).

Configure UseLocalIdForClip

If you have a combination of XCAPI with a 3CX phone system, it may be necessary to enable UseLocalIdForClip in the registry.

Review the dialing options

The dialing options may not be correctly set. This has been noticed when sending faxes to a Microsoft Outlook business contact.

Disable ECM

If you're facing the issue when receiving faxes through a Bintec Media gateway, ensure ECM is disabled.

Activate the Fax Gateway option

When using a LANCOM device, ensure the Fax Gateway option is activated.

Review the capi.dev file

If you have a LANCOM or Bintec router behind a PABX, review the settings in the capi.dev file.

Restart the voice/media gateway

Rebooting the voice/media gateway has resolved this issue in several cases. Bintec routers, Dialogic DMGs, and others are what a FoIP fax device will connect to and may require timely reboots to ensure the voice/media continues operating quickly.  

Check for changes in your local configuration

This would include any other resources being used in conjunction with FaxMaker. There have been many instances where a change was made in the phone system at the same time the Call Failed: 46 errors started. This will, of course, vary by system and equipment.

Check for changes on the provider's side

These changes are not usually made without notification, but verifying there were no emails or notifications from the providers could also be helpful.

What to provide to Support if opening a ticket is required

If using any ISDN devices (other than Brooktrout or XCAPI devices), enable debug, reproduce the issue, and run the troubleshooter to upload the logging.

If using an XCAPI FoIP device, enable debug, collect an XCAPI trace, reproduce the issue, and run the troubleshooter to upload the logging.