Start a conversation

Call Failed 46 sending faxes with SR140

Overview

You may notice that receiving incoming faxes works fine, but sending faxes fails with Call Failed 46 error.

This has been observed with Brooktrout SR140.

Diagnosis

This solution applies to the Brooktrout SR140 when it's configured to use the T38 protocol only.

We'll assume the files are in the default path: C:\Program Files (x86)\GFI\FaxMaker\brooktrout\TR1034\Boston\config

First, verify that the callctrl.cfg file shows fax_transport_protocol=t38_only, which means the SR140 is set to T38 only.

Next, confirm from a Wireshark capture that the switch to T38 never occurs as a T38 invitation is never received from the gateway (123.102.50.121, in this example):

no-t38-switch.png

Solution

Make a backup of the files btcall.cfg and callctrl.cfg, and then edit them as follows.

Change the btcall.cfg file so it contains these values:

ced_timeout 8000
v34_ci_enable 0
v34_2400_baud_ctrl 0
v34_enable 0
debug_options 3
debug_control 9 1

Change the callctrl.cfg file so it contains these values (if any of these lines has a # in front of it, remove the # so the line can have an effect):

l3l4_trace=verbose
l4l3_trace=verbose
api_trace=verbose
internal_trace=verbose
host_module_trace=verbose
ip_stack_trace=verbose
trace_file=C:\Program Files (x86)\GFI\FaxMaker\logs\ecc.log
max_trace_files=5
max_trace_file_size=80
media_renegotiate_delay_outbound=5000
sip_From=<PhoneNumber>@<FaxMaker server IP address>

Note that for the sip_From line the values should be replaced with the actual values, e.g.: 5554321@192.168.10.90

Save the files, restart FaxMaker's and Brooktrout Boston services, and try sending the faxes again.

Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted 16 days ago

Comments