Hi,
I tried everything suggested in the mailing list archive, nothing
works. Here is the problem:
We have a client with 2 fax machines of different makes to which all
outgoing faxes fail after EOP or PPS is sent. We can them faxes fine
use a regular fax machine just fine. I tried adding delays. no luck.
basically I get an errors like these:
Apr 01 10:33:56.55: [ 1486]: SEND send EOP (no more pages or documents)
Apr 01 10:33:56.55: [ 1486]: <-- [9:AT+FTH=3\r]
Apr 01 10:33:56.71: [ 1486]: --> [7:CONNECT]
Apr 01 10:33:56.71: [ 1486]: <-- data [3]
Apr 01 10:33:56.71: [ 1486]: <-- data [2]
Apr 01 10:33:57.88: [ 1486]: --> [2:OK]
Apr 01 10:33:57.88: [ 1486]: <-- [9:AT+FRH=3\r]
Apr 01 10:33:58.43: [ 1486]: --> [10:NO CARRIER]
Apr 01 10:28:55.04: [ 1301]: SEND send PPS (partial page signal)
Apr 01 10:28:55.04: [ 1301]: SEND send EOP (no more pages or documents)
Apr 01 10:28:55.04: [ 1301]: <-- [9:AT+FRH=3\r]
Apr 01 10:28:55.57: [ 1301]: --> [10:NO CARRIER]
Apr 01 10:18:24.89: [ 1005]: SEND send PPS (partial page signal)
Apr 01 10:18:24.89: [ 1005]: SEND send EOP (no more pages or documents)
Apr 01 10:18:24.89: [ 1005]: <-- [9:AT+FRH=3\r]
Apr 01 10:18:25.12: [ 1005]: --> [7:CONNECT]
Apr 01 10:18:25.13: [ 1005]: --> [5:ERROR]
Apr 01 10:18:25.13: [ 1005]: MODEM Command error
I'm using US Robotics modems , hylafax 6.0.4 , on CentOS 5.4 . here
is the config of the modem I've been testing with.
#
# Configuration for using the Class 1 command interface with
# a USR Courier or Sportster modem and XON/XOFF flow control.
#
#
CountryCode: 1
AreaCode: 316
FAXNumber: 316-555-5000
LongDistancePrefix: 1
InternationalPrefix: 011
DialStringRules: etc/dialrules
ServerTracing: 1
SessionTracing: 11
RecvFileMode: 0600
LogFileMode: 0600
DeviceMode: 0600
RingsBeforeAnswer: 0
SpeakerVolume: high
GettyArgs: "-h %l dx_%s"
LocalIdentifier: "WeatherData Services Inc"
TagLineFont: etc/lutRS18.pcf
TagLineFormat: "From %%l|%c|Page %%P of %%T"
MaxRecvPages: 25
JobReqBusy: 60
JobReqNoCarrier: 60
JobReqNoAnswer: 60
JobReqDataConn: 60
JobReqOther: 60
#
#
# 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.
#
Class1PPMWaitCmd: "<delay\0727>" # \072 == : to avoid awk problem
Class1TCFWaitCmd: "<delay\0727>"
Class1EOPWaitCmd: "<delay\0727>"
Class1SwitchingCmd: "<delay\0727>" # assumption: +FRS not supported
Is there a real solution to this problem other than "use class 2" or
"buy another brand of modem" ?
Switching to class 2 brings a bunch of new issues... and it's very slow.
thanks !