A problem can occur when connecting a DCE Faxbox 30 or Faxbox 2 to a Specialix MTS.

It has been found that on some systems the Faxbox will be seen to dial a number and then reset and fail to send the fax data. The faxstat command will then show a failed result message.

This failure is due to the U-Fax application trying to setup xon/xoff flow control on the TCP port used by the Faxbox. On most UNIX systems this command is ignored when it is applied to a network port, but on SVR4 MP-RAS it can cause the U-Fax application to time-out and eventually fail resulting in the failure of the fax transmission.

This problem should not occur when the Faxbox is configured on a serial port attached directly to the server. i.e. the Specialix I/O8+.

This problem can be rectified by editing the following file.

By default the variable UFXLIB will point to the /usr/lib/ufax directory.

There should be a line in the section [DCE1].

This line should be modified to read.

The T option specifies that the Faxbox is connected via a Specialix MTS.

The H option specifies that U-Fax will not try to set xon/xoff flow control on the Faxbox port.

The R option specifies that U-Fax will wait for the Faxbox to reset before it tries to send the fax data.

See the example ufax.ini file at the end of this bulletin.

To activate the new configuration, U-Fax needs to be stopped and restarted by either rebooting the server or running the following commands from the root login.

U-Fax version 3.1 will not support a Faxbox connected to a Specialix MTS.

U-Fax version 3.2 will support the MTS configuration only when an updated interface program is installed and the specials entry added to the ufax.ini file.

U-Fax version 3.3 fully supports the MTS setup and can be configured correctly during the install process.

[General]

Retries=3

Eng_Retries=10

Mshot_Stay_Time=4320

Network_Headers=no

Stderr=/tmp/stderr

Site_Id=BML Test

Status=on

Scanner=no

Specials=THR

Return to Index