[hylafax-users] ERR Remote has no T.4 receiver capability

[alex@xxxxxxxxxxxx]

I'm working with a small non-profit advocacy organization, and we 
recently sent a fax to all 540 members of Congress on an issue of 
concern to us. For the most part, it went excellently; I'm currently 
cleaning up < 25 or so faxes that have failed due to excessive busy 
signals, etc.

One that's really got me stuck, though, is a job that returned the 
error in the subject line. Here's the trace from the failure message:

Jul 01 20:51:27.90: [24556]: SESSION BEGIN 000003160 17037012022255652
Jul 01 20:51:27.90: [24556]: HylaFAX (tm) Version 4.3.0
Jul 01 20:51:27.90: [24556]: SEND FAX: JOB 1809 DEST *701-202-225-5652 
COMMID 000003160 DEVICE '/dev/ttyS0' FROM 'alex <alex@xxxxxxxxxxxx>' 
USER alex
Jul 01 20:51:27.90: [24556]: <-- [12:AT+FCLASS=1\r]
Jul 01 20:51:28.03: [24556]: --> [2:OK]
Jul 01 20:51:28.03: [24556]: DIAL *7012022255652
Jul 01 20:51:28.03: [24556]: <-- [19:ATDT*7012022255652\r]
Jul 01 20:51:51.47: [24556]: --> [7:CONNECT]
Jul 01 20:51:53.38: [24556]: --> [2:OK]
Jul 01 20:51:53.38: [24556]: REMOTE NSF "00 00 11 80 00 8A 49 10 55 2E 
53 2E 20 52 45 50 2E 20 4B 41 54 48 59 20 00 53 00 80 80 80 0C 01 02"
Jul 01 20:51:53.38: [24556]: NSF remote fax equipment: Canon Laser 
Class 9000 Series
Jul 01 20:51:53.38: [24556]: NSF remote station ID: "U.S. REP. KATHY "
Jul 01 20:51:53.38: [24556]: <-- [9:AT+FRH=3\r]
Jul 01 20:51:53.40: [24556]: --> [7:CONNECT]
Jul 01 20:51:54.08: [24556]: --> [2:OK]
Jul 01 20:51:54.08: [24556]: REMOTE CSI "202 225 5652"
Jul 01 20:51:54.08: [24556]: <-- [9:AT+FRH=3\r]
Jul 01 20:51:54.09: [24556]: --> [7:CONNECT]
Jul 01 20:51:54.50: [24556]: --> [2:OK]
Jul 01 20:51:54.50: [24556]: Remote has no T.4 receiver capability
Jul 01 20:51:54.50: [24556]: SEND FAILED: JOB 1809 DEST 
*701-202-225-5652 ERR Remote has no T.4 receiver capability
Jul 01 20:51:54.50: [24556]: <-- [9:AT+FTH=3\r]
Jul 01 20:51:54.70: [24556]: --> [7:CONNECT]
Jul 01 20:51:55.87: [24556]: --> [2:OK]
Jul 01 20:51:55.87: [24556]: <-- [5:ATH0\r]
Jul 01 20:51:56.11: [24556]: --> [2:OK]
Jul 01 20:51:56.11: [24556]: SESSION END

The only thing I could think of was that it might be a Class 1 related 
issue...but I'm already set to Class 1. Here's my config, which is 
running on an external USR Sportster 33.6 (which was advertised as 
having the 56K-enabling BIOS flash or whatever when I bought it from 
eBay, though I've never really seen it run much above 14.4):

alex@home: ~$ sudo cat /var/spool/hylafax/etc/config.ttyS0
...<trimming copyright for readability>...
# Configuration for using the Class 1 command interface with
# a USR Courier or Sportster modem and XON/XOFF flow control.
#
#
CountryCode:            1
AreaCode:               703
FAXNumber:              +1.703.778.6214
LongDistancePrefix:     1
InternationalPrefix:    011
DialStringRules:        etc/dialrules
ServerTracing:          0xFFF
SessionTracing:         11
RecvFileMode:           0600
LogFileMode:            0600
DeviceMode:             0600
RingsBeforeAnswer:      10
SpeakerVolume:          off
GettyArgs:              "-h %l dx_%s"
LocalIdentifier:        "703.778.6214"
TagLineFont:            etc/lutRS18.pcf
TagLineFormat:          "From %%l|%c|Page %%P of %%T"
MaxRecvPages:           25
#
#
# Modem-related stuff: should reflect modem command interface
# and hardware connection/cabling (e.g. flow control).
#
ModemType:              Class1          # use class 1 interface
ModemRate:              19200           # rate for DCE-DTE communication
ModemFlowControl:       xonxoff         # software flow control
#
ModemSetupDTRCmd:       ATS13=1&D2      # setup so DTR drop resets modem
ModemSetupDCDCmd:       AT&C1           # setup so DCD reflects carrier 
(or not)
ModemNoFlowCmd:         AT&H0&I0&R1     # setup modem for no flow control
ModemHardFlowCmd:       AT&H1&I0&R2     # setup modem for hardware flow 
control
ModemSoftFlowCmd:       AT&H2&I2&R1     # setup modem for software flow 
control
ModemResultCodesCmd:    ATQ0X4          # enable result codes
#
ModemMfrQueryCmd:       !USR
ModemModelQueryCmd:     ATI3
ModemRevQueryCmd:       ATI7            # XXX returns a multi-line result
#
# When AT+FCLASS=1 is issued the modem automatically switches
# to software flow control; these parameters let the fax software
# reset flow control as needed after entering Class 1.
#
Class1NFLOCmd:          AT&H0&I0&R1     # setup modem for no flow control
Class1HFLOCmd:          AT&H1&I0&R2     # setup modem for hardware flow 
control
Class1SFLOCmd:          ""              # modem does this automatically
#
# This should resolve "DIS/DTC received 3 times" errors:
#
Class1ResponseWaitCmd:  AT+FRS=1        # wait after sending TCF for response
#
# The remainder of this configuration is included so that the
# modem "idles" in Class 0 while not sending or receiving facsimile.
#
ModemSetupAACmd:        AT+FCLASS=0     # leave modem idling in class 0
ModemAnswerCmd:         AT+FCLASS=1A    # answer in Class 1
#
# When using AT+FRS=n we see USR modems reset themselves in the middle 
of sessions
# this is not good.  So, we seem to work-around that problem by not using the
# command.  Unfortunately, this isn't an ideal thing.
#
Class1SwitchingCmd:     "<delay\0727>"

The big problem here is that I can't really call up the remote side and 
tell them that their fax machine is having problems. Any ideas what 
might be going on here?

Thanks,
Alex Kirk


____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*