[hylafax-users] RSPREC error/got DCN (code 71)
Bryan J. McBride
Insideout Networks RapidPort/4 USB modem.
I have it configured as a Class 2 modem connected to a DID line. When
configured as a Class 1, we had almost 20% error rate when receiving
faxes. ("No sender protocol (T.30 T1 timeout)" among others)
As a Class 2 modem, we are receiving faxes better. That is, we have
almost no errors when a connection is successful. However, I am getting
a lot of dropped calls, all with almost the exact same log. I am getting
this on different DIDs.
I have tried to searching the user list archive and of course applied
some googlefu which prompted the change to class 2 configuration. Any
suggestions would be greatly appreciated.
May 03 14:33:56.93: [ 1386]: SESSION BEGIN 000001849 19019016835482
May 03 14:33:56.93: [ 1386]: HylaFAX (tm) Version 6.0.3
May 03 14:33:56.93: [ 1386]: CallID: "0031"
May 03 14:33:56.93: [ 1386]: DynamicConfig: bin/dynconf.php
"/dev/ttyUSB2" "0031"
May 03 14:33:57.00: [ 1386]: DELAY 1000 ms
May 03 14:33:58.00: [ 1386]: <-- [14:AT+FCLASS=2;A\r]
May 03 14:34:44.36: [ 1386]: --> [2: ~]
May 03 14:34:44.36: [ 1386]: --> [8:+FHNG:71]
May 03 14:34:44.36: [ 1386]: REMOTE HANGUP: RSPREC error/got DCN (code
71)
May 03 14:34:44.36: [ 1386]: ANSWER: Ring detected without successful
handshake
May 03 14:34:44.36: [ 1386]: Ring detected without successful handshake
May 03 14:34:44.36: [ 1386]: SESSION END
The modem config is as follows:
CountryCode: 1
AreaCode: 901
FAXNumber: 901.683.5482
LongDistancePrefix: 1
InternationalPrefix: 011
DialStringRules: etc/dialrules
ServerTracing: 1
SessionTracing: 11
RecvFileMode: 0644
LogFileMode: 0644
DeviceMode: 0666
RingsBeforeAnswer: 1
ModemRingResponse: AT+FCLASS=8;H1
CallIDPattern: SHIELDED_DTMF
CallIDAnswerLength: 4
ModemAnswerCmd: <delay:100>AT+FCLASS=2;A
SpeakerVolume: off
GettyArgs: "-h %l dx_%s"
LocalIdentifier: "Reynolds, Bone & Griesbeck PLC"
TagLineFont: etc/lutRS18.pcf
TagLineFormat: "From %%l|%c|Page %%P of %%T"
QualifyTSI: "etc/tsi"
PercentGoodLines: 0
MaxConsecutiveBadLines: 0
MaxRecvPages: 99
#
#
# Modem-related stuff: should reflect modem command interface
# and hardware connection/cabling (e.g. flow control).
#
ModemType: Class2 # use this to supply a hint
#ModemRate: 19200 # max rate for DCE-DTE
communication
#ModemFlowControl: xonxoff # XON/XOFF flow control assumed
#ModemSetupDTRCmd: AT&D2 # setup so DTR drop resets modem
#ModemSetupDCDCmd: AT&C1 # setup so DCD reflects carrier
(or not)
#
# We can append the "@" symbol to the dial string so that
# the modem will wait 5 seconds before attempting to connect
# and return result codes that distinguish between no carrier
# and no answer. This makes it possible to avoid problems with
# repeatedly dialing a number that doesn't have a fax machine
# (kudos to Stuart Lynne for this trick.)
#
# NB: If you need to prefix phone numbers to get through a PBX,
# put it in the ModemDialCmd; e.g. "DT9%s@".
#
#ModemDialCmd: ATDT%s # T for tone dialing
#
# Other possible configuration stuff. The default strings are
# shown below. Only those that are different from the defaults
# need to be included in the configuration file.
#
#ModemResetCmds: "" # stuff to do when modem
is reset
#ModemAnswerCmd: ATA # use this to answer
phone
#ModemNoFlowCmd: AT&K # disable flow control
cmd
#ModemHardFlowCmd: AT&K3 # hardware flow control cmd
#ModemSoftFlowCmd: AT&K4 # software flow control cmd
#ModemNoAutoAnswerCmd: ATS0=0 # disable auto-answer
#
# Set modem speaker volume commands: OFF QUIET LOW MEDIUM HIGH.
# Note that we both turn the speaker on/off and set volume.
#
#ModemSetVolumeCmd: "ATM0 ATL0M1 ATL1M1 ATL2M1 ATL3M1"
#ModemEchoOffCmd: ATE0 # disable command echo
#ModemVerboseResultsCmd: ATV1 # enable verbose command
results
#ModemResultCodesCmd: ATQ0 # enable result codes
#ModemOnHookCmd: ATH0 # place phone on hook
(hangup)
#ModemSoftResetCmd: ATZ # do soft reset of modem
#ModemSoftResetCmdDelay: 3000 # pause after soft reset
#ModemWaitTimeCmd: ATS7=60 # wait 60 seconds for carrier
#ModemCommaPauseTimeCmd: ATS8=2 # comma pause time is 2
seconds
#ModemRecvFillOrder: LSB2MSB # bit order of received
facsimile
#ModemSendFillOrder: LSB2MSB # bit order modem expects for
transmit
#
# Configuration parameters for Class 2 modems.
#
Class2Cmd: AT+FCLASS=2 # command to enter class 2
Class2BORCmd: AT+FBOR=0 # bit order for phase B/C/D
(direct)
Class2RELCmd: AT+FREL=1 # byte-align EOL codes on recv
Class2CQCmd: "" # commands to enable copy
quality proc.
Class2AbortCmd: AT+FK # abort session command
Class2CQQueryCmd: AT+FCQ=? # query for copy quality
capabilities
Class2DCCQueryCmd: AT+FDCC=? # query for modem capabilities
Class2TBCCmd: AT+FTBC=0 # setup stream mode
Class2CRCmd: AT+FCR=1 # enable capability to receive
Class2PHCTOCmd: AT+FPHCTO=30 # set phase C timeout parameter
Class2BUGCmd: AT+FBUG=1 # enable HDLC frame tracing
Class2LIDCmd: AT+FLID # set local identifier command
Class2DCCCmd: AT+FDCC # set modem capabilities command
Class2DISCmd: AT+FDIS # set session parameters command
Class2DDISCmd: "" # disable pre-dial DIS command
hack
Class2CIGCmd: AT+FCIG # set polling identifier command
Class2PTSCmd: AT+FPTS # set post-page status command
Class2SPLCmd: AT+FSPL # set polling indicator command
#
# If Class2RecvDataTrigger is not set, then it is set to DC1
#
Class2RecvDataTrigger: "" # character sent to modem to
start recv
Class2XmitWaitForXON: yes # if true, wait for XON before
send
#
## AvantFAX
#
FaxRcvdCmd: bin/faxrcvd.php
DynamicConfig: bin/dynconf.php
UseJobTSI: true
Bryan J. McBride
------------------------------------------------------------------------------------------
Proudly Celebrating 95 Years in Business
Member PKF North America
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-us...@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sa...@ifax.com.*
Lee Howard
> I am using Hylafax 6.0.3 on Ubuntu 10.04 server. The modem is a
> Insideout Networks RapidPort/4 USB modem.
>
> I have it configured as a Class 2 modem connected to a DID line. When
> configured as a Class 1, we had almost 20% error rate when receiving
> faxes. ("No sender protocol (T.30 T1 timeout)" among others)
>
> As a Class 2 modem, we are receiving faxes better. That is, we have
> almost no errors when a connection is successful. However, I am getting
> a lot of dropped calls, all with almost the exact same log. I am getting
> this on different DIDs.
>
Are you getting roughly the same number of dropped calls in Class 2 as
you were getting reception failures in Class 1?
The Class 1 logs are going to be much-more revealing than will be the
Class 2.
> I have tried to searching the user list archive and of course applied
> some googlefu which prompted the change to class 2 configuration. Any
> suggestions would be greatly appreciated.
>
> May 03 14:33:56.93: [ 1386]: SESSION BEGIN 000001849 19019016835482
> May 03 14:33:56.93: [ 1386]: HylaFAX (tm) Version 6.0.3
> May 03 14:33:56.93: [ 1386]: CallID: "0031"
> May 03 14:33:56.93: [ 1386]: DynamicConfig: bin/dynconf.php
> "/dev/ttyUSB2" "0031"
> May 03 14:33:57.00: [ 1386]: DELAY 1000 ms
> May 03 14:33:58.00: [ 1386]: <-- [14:AT+FCLASS=2;A\r]
> May 03 14:34:44.36: [ 1386]: --> [2: ~]
> May 03 14:34:44.36: [ 1386]: --> [8:+FHNG:71]
> May 03 14:34:44.36: [ 1386]: REMOTE HANGUP: RSPREC error/got DCN (code
> 71)
> May 03 14:34:44.36: [ 1386]: ANSWER: Ring detected without successful
> handshake
> May 03 14:34:44.36: [ 1386]: Ring detected without successful handshake
> May 03 14:34:44.36: [ 1386]: SESSION END
The Class 2 modem is saying that it was unable to negotiate a fax due to
something like a disconnection or a hangup occurring early in Phase B
(before any DCS signal is received).
As I said before, the Class 1 log would prove much more telling, but
this seems pretty clear anyway: calls are being received but are not
handshaking. They could be voice calls. The line could have problems.
Thanks,
Lee.
Bryan J. McBride
> -----Original Message-----
> From: Lee Howard [mailto:fax...@howardsilvan.com]
> Sent: Wednesday, May 04, 2011 10:51 PM
> To: Bryan J. McBride
> Cc: hylafa...@hylafax.org
> Subject: Re: [hylafax-users] RSPREC error/got DCN (code 71)
>
> Bryan J. McBride wrote:
> > I am using Hylafax 6.0.3 on Ubuntu 10.04 server. The modem is a
> > Insideout Networks RapidPort/4 USB modem.
> >
> > I have it configured as a Class 2 modem connected to a DID line.
When
> > configured as a Class 1, we had almost 20% error rate when receiving
> > faxes. ("No sender protocol (T.30 T1 timeout)" among others)
> >
> > As a Class 2 modem, we are receiving faxes better. That is, we
have
> > almost no errors when a connection is successful. However, I am
> > getting a lot of dropped calls, all with almost the exact same log.
I
> > am getting this on different DIDs.
> >
>
> Are you getting roughly the same number of dropped calls in Class 2 as
you
> were getting reception failures in Class 1?
No I am getting far fewer errors in class 2 than class 1. However, I
got no handshake errors with class one.
>
> The Class 1 logs are going to be much-more revealing than will be the
Class 2.
>
The most common Class 1 error was "No sender protocol (T.30 T1
timeout)".
Apr 29 16:09:23.90: [ 4874]: SESSION BEGIN 000001765 19019016835482
Apr 29 16:09:23.90: [ 4874]: HylaFAX (tm) Version 6.0.3
Apr 29 16:09:23.90: [ 4874]: <-- [4:ATA\r]
Apr 29 16:09:30.20: [ 4874]: --> [7:CONNECT]
Apr 29 16:09:30.21: [ 4874]: ANSWER: FAX CONNECTION DEVICE
'/dev/ttyUSB1'
Apr 29 16:09:30.21: [ 4874]: RECV FAX: begin
Apr 29 16:09:30.21: [ 4874]: <-- data [32]
Apr 29 16:09:30.21: [ 4874]: <-- data [2]
Apr 29 16:09:30.24: [ 4874]: --> [7:CONNECT]
Apr 29 16:09:30.24: [ 4874]: <-- data [23]
Apr 29 16:09:30.24: [ 4874]: <-- data [2]
Apr 29 16:09:30.27: [ 4874]: --> [7:CONNECT]
Apr 29 16:09:30.27: [ 4874]: <-- data [13]
Apr 29 16:09:30.27: [ 4874]: <-- data [2]
Apr 29 16:09:32.46: [ 4874]: --> [2:OK]
Apr 29 16:09:32.47: [ 4874]: <-- [9:AT+FRH=3\r]
Apr 29 16:09:39.47: [ 4874]: --> [0:]
Apr 29 16:09:39.47: [ 4874]: MODEM <Empty line>
Apr 29 16:09:39.47: [ 4874]: <-- data [1]
Apr 29 16:09:39.48: [ 4874]: --> [2: ]
Apr 29 16:09:39.48: [ 4874]: --> [2:OK]
Apr 29 16:09:39.48: [ 4874]: <-- [9:AT+FRS=7\r]
Apr 29 16:09:52.10: [ 4874]: --> [2:OK]
Apr 29 16:09:52.10: [ 4874]: <-- [9:AT+FTH=3\r]
Apr 29 16:09:52.97: [ 4874]: --> [7:CONNECT]
Apr 29 16:09:52.97: [ 4874]: <-- data [32]
Apr 29 16:09:52.97: [ 4874]: <-- data [2]
Apr 29 16:09:53.01: [ 4874]: --> [7:CONNECT]
Apr 29 16:09:53.01: [ 4874]: <-- data [23]
Apr 29 16:09:53.01: [ 4874]: <-- data [2]
Apr 29 16:09:53.04: [ 4874]: --> [7:CONNECT]
Apr 29 16:09:53.04: [ 4874]: <-- data [13]
Apr 29 16:09:53.04: [ 4874]: <-- data [2]
Apr 29 16:09:55.23: [ 4874]: --> [2:OK]
Apr 29 16:09:55.23: [ 4874]: <-- [9:AT+FRH=3\r]
Apr 29 16:10:02.23: [ 4874]: --> [0:]
Apr 29 16:10:02.23: [ 4874]: MODEM <Empty line>
Apr 29 16:10:02.23: [ 4874]: <-- data [1]
Apr 29 16:10:02.25: [ 4874]: --> [2: ]
Apr 29 16:10:02.25: [ 4874]: --> [2:OK]
Apr 29 16:10:02.25: [ 4874]: <-- [9:AT+FRS=7\r]
Apr 29 16:10:02.34: [ 4874]: --> [2:OK]
Apr 29 16:10:02.34: [ 4874]: <-- [9:AT+FTH=3\r]
Apr 29 16:10:03.21: [ 4874]: --> [7:CONNECT]
Apr 29 16:10:03.21: [ 4874]: <-- data [32]
Apr 29 16:10:03.21: [ 4874]: <-- data [2]
Apr 29 16:10:03.24: [ 4874]: --> [7:CONNECT]
Apr 29 16:10:03.25: [ 4874]: <-- data [23]
Apr 29 16:10:03.25: [ 4874]: <-- data [2]
Apr 29 16:10:03.27: [ 4874]: --> [7:CONNECT]
Apr 29 16:10:03.27: [ 4874]: <-- data [13]
Apr 29 16:10:03.27: [ 4874]: <-- data [2]
Apr 29 16:10:05.47: [ 4874]: --> [2:OK]
Apr 29 16:10:05.47: [ 4874]: <-- [9:AT+FRH=3\r]
Apr 29 16:10:12.47: [ 4874]: --> [0:]
Apr 29 16:10:12.47: [ 4874]: MODEM <Empty line>
Apr 29 16:10:12.47: [ 4874]: <-- data [1]
Apr 29 16:10:12.48: [ 4874]: --> [2: ]
Apr 29 16:10:12.48: [ 4874]: --> [2:OK]
Apr 29 16:10:12.49: [ 4874]: RECV FAX: No sender protocol (T.30 T1
timeout)
Apr 29 16:10:12.49: [ 4874]: RECV FAX: end
Apr 29 16:10:12.49: [ 4874]: No sender protocol (T.30 T1 timeout)
Apr 29 16:10:12.49: [ 4874]: SESSION END
My second most common error was "T.30 T2 timeout, expected signal not
received"
Apr 16 12:37:08.59: [28553]: SESSION BEGIN 000001637 19019016835482
Apr 16 12:37:08.59: [28553]: HylaFAX (tm) Version 6.0.3
Apr 16 12:37:08.59: [28553]: CallID: "9822"
Apr 16 12:37:08.59: [28553]: DELAY 1000 ms
Apr 16 12:37:09.59: [28553]: <-- [14:AT+FCLASS=1;A\r]
Apr 16 12:37:15.81: [28553]: --> [2: ~]
Apr 16 12:37:15.81: [28553]: --> [7:CONNECT]
Apr 16 12:37:15.81: [28553]: ANSWER: FAX CONNECTION DEVICE
'/dev/ttyUSB0'
Apr 16 12:37:15.81: [28553]: RECV FAX: begin
Apr 16 12:37:15.81: [28553]: <-- data [32]
Apr 16 12:37:15.81: [28553]: <-- data [2]
Apr 16 12:37:15.85: [28553]: --> [7:CONNECT]
Apr 16 12:37:15.85: [28553]: <-- data [23]
Apr 16 12:37:15.85: [28553]: <-- data [2]
Apr 16 12:37:15.88: [28553]: --> [7:CONNECT]
Apr 16 12:37:15.88: [28553]: <-- data [13]
Apr 16 12:37:15.88: [28553]: <-- data [2]
Apr 16 12:37:18.07: [28553]: --> [2:OK]
Apr 16 12:37:18.07: [28553]: <-- [9:AT+FRH=3\r]
Apr 16 12:37:18.64: [28553]: --> [7:CONNECT]
Apr 16 12:37:20.35: [28553]: --> [2:OK]
Apr 16 12:37:20.35: [28553]: RECV recv TSI (sender id)
Apr 16 12:37:20.35: [28553]: REMOTE TSI "901 888 6305"
Apr 16 12:37:20.35: [28553]: <-- [9:AT+FRH=3\r]
Apr 16 12:37:20.37: [28553]: --> [7:CONNECT]
Apr 16 12:37:20.78: [28553]: --> [2:OK]
Apr 16 12:37:20.78: [28553]: RECV recv DCS (command signal)
Apr 16 12:37:20.78: [28553]: REMOTE wants 14400 bit/s
Apr 16 12:37:20.78: [28553]: REMOTE wants A4 page width (215 mm)
Apr 16 12:37:20.78: [28553]: REMOTE wants unlimited page length
Apr 16 12:37:20.78: [28553]: REMOTE wants 7.7 line/mm
Apr 16 12:37:20.78: [28553]: REMOTE wants 2-D MMR
Apr 16 12:37:20.78: [28553]: REMOTE wants T.30 Annex A, 256-byte ECM
Apr 16 12:37:20.78: [28553]: RECV training at v.17 14400 bit/s
Apr 16 12:37:20.78: [28553]: <-- [11:AT+FRM=145\r]
Apr 16 12:37:22.61: [28553]: --> [7:CONNECT]
Apr 16 12:37:24.07: [28553]: RECV: TCF 2672 bytes, 0% non-zero, 2661
zero-run
Apr 16 12:37:24.08: [28553]: --> [10:NO CARRIER]
Apr 16 12:37:24.08: [28553]: <-- [9:AT+FRS=7\r]
Apr 16 12:37:24.17: [28553]: --> [2:OK]
Apr 16 12:37:24.17: [28553]: TRAINING succeeded
Apr 16 12:37:24.17: [28553]: ACCEPT TSI "901 888 6305"
Apr 16 12:37:24.17: [28553]: <-- [9:AT+FTH=3\r]
Apr 16 12:37:25.04: [28553]: --> [7:CONNECT]
Apr 16 12:37:25.04: [28553]: <-- data [3]
Apr 16 12:37:25.04: [28553]: <-- data [2]
Apr 16 12:37:25.36: [28553]: --> [2:OK]
Apr 16 12:37:25.36: [28553]: <-- [11:AT+FRM=146\r]
Apr 16 12:37:26.35: [28553]: --> [7:CONNECT]
Apr 16 12:37:27.38: [28553]: RECV received frame number 0
Apr 16 12:37:27.56: [28553]: RECV received frame number 1
Apr 16 12:37:27.66: [28553]: RECV received frame number 2
Apr 16 12:37:27.84: [28553]: RECV received frame number 3
Apr 16 12:37:28.03: [28553]: RECV received frame number 4
Apr 16 12:37:28.12: [28553]: RECV received frame number 5
Apr 16 12:37:28.31: [28553]: RECV received frame number 6
Apr 16 12:37:28.49: [28553]: RECV received frame number 7
Apr 16 12:37:28.58: [28553]: RECV received frame number 8
Apr 16 12:37:28.77: [28553]: RECV received frame number 9
Apr 16 12:37:28.86: [28553]: RECV received frame number 10
Apr 16 12:37:29.05: [28553]: RECV received frame number 11
Apr 16 12:37:29.23: [28553]: RECV received frame number 12
Apr 16 12:37:29.32: [28553]: RECV received frame number 13
Apr 16 12:37:29.51: [28553]: RECV received frame number 14
Apr 16 12:37:29.60: [28553]: RECV received frame number 15
Apr 16 12:37:29.79: [28553]: RECV received frame number 16
Apr 16 12:37:29.98: [28553]: RECV received frame number 17
Apr 16 12:37:30.07: [28553]: RECV received frame number 18
Apr 16 12:37:30.25: [28553]: RECV received frame number 19
Apr 16 12:37:30.44: [28553]: RECV received frame number 20
Apr 16 12:37:30.53: [28553]: RECV received frame number 21
Apr 16 12:37:30.72: [28553]: RECV received frame number 22
Apr 16 12:37:30.81: [28553]: RECV received frame number 23
Apr 16 12:37:31.00: [28553]: RECV received frame number 24
Apr 16 12:37:31.18: [28553]: RECV received frame number 25
Apr 16 12:37:31.27: [28553]: RECV received frame number 26
Apr 16 12:37:31.46: [28553]: RECV received frame number 27
Apr 16 12:37:31.64: [28553]: RECV received frame number 28
Apr 16 12:37:38.18: [28553]: RECV received frame number 29
Apr 16 12:37:38.18: [28553]: RECV received RCP frame
Apr 16 12:37:38.19: [28553]: --> [10:NO CARRIER]
Apr 16 12:37:38.19: [28553]: <-- [9:AT+FRH=3\r]
Apr 16 12:37:38.26: [28553]: --> [7:CONNECT]
Apr 16 12:37:39.55: [28553]: --> [2:OK]
Apr 16 12:37:39.55: [28553]: RECV recv PPS (partial page signal)
Apr 16 12:37:39.55: [28553]: RECV recv MPS (more pages, same document)
Apr 16 12:37:39.55: [28553]: RECV received 30 frames of block 1 of page
1
Apr 16 12:37:39.56: [28553]: RECV: 7677 bytes of data, 2172 total lines
Apr 16 12:37:39.56: [28553]: <-- [9:AT+FRS=7\r]
Apr 16 12:37:39.74: [28553]: --> [2:OK]
Apr 16 12:37:39.74: [28553]: RECV send MCF (message confirmation)
Apr 16 12:37:39.74: [28553]: <-- [9:AT+FTH=3\r]
Apr 16 12:37:40.61: [28553]: --> [7:CONNECT]
Apr 16 12:37:40.61: [28553]: RECV FAX (000001637): from 901 888 6305,
page 1 in 0:00:24, INF, 7.7 line/mm, 2-D MMR, 14400 bit/s
Apr 16 12:37:40.61: [28553]: <-- data [3]
Apr 16 12:37:40.61: [28553]: <-- data [2]
Apr 16 12:37:40.93: [28553]: --> [2:OK]
Apr 16 12:37:40.93: [28553]: <-- [11:AT+FRM=146\r]
Apr 16 12:37:41.90: [28553]: --> [7:CONNECT]
Apr 16 12:37:42.02: [28553]: RECV assumed RCP frame with block end
Apr 16 12:37:42.02: [28553]: --> [2:OK]
Apr 16 12:37:44.02: [28553]: MODEM <Timeout>
Apr 16 12:37:46.02: [28553]: MODEM <Empty line>
Apr 16 12:37:46.02: [28553]: <-- [9:AT+FRH=3\r]
Apr 16 12:37:46.25: [28553]: --> [7:CONNECT]
Apr 16 12:37:56.25: [28553]: <-- data [1]
Apr 16 12:37:56.26: [28553]: --> [2: ]
Apr 16 12:37:56.26: [28553]: --> [2:OK]
Apr 16 12:37:56.26: [28553]: RECV FAX (000001637):
recvq/fax000001628.tif from 901 888 6305, route to <unspecified>, 1
pages in 0:00:41
Apr 16 12:37:56.26: [28553]: RECV FAX: T.30 T2 timeout, expected signal
not received
Apr 16 12:37:56.26: [28553]: <-- [9:AT+FRS=7\r]
Apr 16 12:37:56.36: [28553]: --> [2:OK]
Apr 16 12:37:56.36: [28553]: <-- [9:AT+FTH=3\r]
Apr 16 12:37:57.23: [28553]: --> [7:CONNECT]
Apr 16 12:37:57.23: [28553]: <-- data [3]
Apr 16 12:37:57.23: [28553]: <-- data [2]
Apr 16 12:37:57.55: [28553]: --> [2:OK]
Apr 16 12:37:57.55: [28553]: RECV FAX (000001637): session with 901 888
6305 terminated abnormally: T.30 T2 timeout, expected signal not
received
Apr 16 12:37:57.55: [28553]: RECV FAX: bin/faxrcvd
"recvq/fax000001628.tif" "ttyUSB0" "000001637" "T.30 T2 timeout,
expected signal not received" "9822"
Apr 16 12:37:57.55: [28553]: RECV FAX: end
Apr 16 12:37:57.55: [28553]: T.30 T2 timeout, expected signal not
received
Apr 16 12:37:57.55: [28553]: SESSION END
I thought they might be errant voice calls or line problems. However,
wouldn't I have seen the handshake errors when the modem was configured
as a class one as well?
>
> Thanks,
>
> Lee.
------------------------------------------------------------------------------------------
Proudly Celebrating 95 Years in Business
Member PKF North America
Lee Howard
> Apr 29 16:10:05.47: [ 4874]: <-- [9:AT+FRH=3\r]
> Apr 29 16:10:12.47: [ 4874]: --> [0:]
> Apr 29 16:10:12.47: [ 4874]: MODEM <Empty line>
> Apr 29 16:10:12.47: [ 4874]: <-- data [1]
> Apr 29 16:10:12.48: [ 4874]: --> [2: ]
> Apr 29 16:10:12.48: [ 4874]: --> [2:OK]
> Apr 29 16:10:12.49: [ 4874]: RECV FAX: No sender protocol (T.30 T1
> timeout)
> Apr 29 16:10:12.49: [ 4874]: RECV FAX: end
> Apr 29 16:10:12.49: [ 4874]: No sender protocol (T.30 T1 timeout)
> Apr 29 16:10:12.49: [ 4874]: SESSION END
>
> My second most common error was "T.30 T2 timeout, expected signal not
> received"
>
This is essentially the same thing as your Class 2 error... reinforcing
the idea that either you're getting a lot of voice calls on your fax
line or that there is something wrong with the line configuration.
> Apr 16 12:37:08.59: [28553]: SESSION BEGIN 000001637 19019016835482
> Apr 16 12:37:08.59: [28553]: HylaFAX (tm) Version 6.0.3
> Apr 16 12:37:08.59: [28553]: CallID: "9822"
> ....
> Apr 16 12:37:40.93: [28553]: <-- [11:AT+FRM=146\r]
> Apr 16 12:37:41.90: [28553]: --> [7:CONNECT]
> Apr 16 12:37:42.02: [28553]: RECV assumed RCP frame with block end
> Apr 16 12:37:42.02: [28553]: --> [2:OK]
> Apr 16 12:37:44.02: [28553]: MODEM <Timeout>
> Apr 16 12:37:46.02: [28553]: MODEM <Empty line>
> Apr 16 12:37:46.02: [28553]: <-- [9:AT+FRH=3\r]
> Apr 16 12:37:46.25: [28553]: --> [7:CONNECT]
> Apr 16 12:37:56.25: [28553]: <-- data [1]
> Apr 16 12:37:56.26: [28553]: --> [2: ]
> Apr 16 12:37:56.26: [28553]: --> [2:OK]
> Apr 16 12:37:56.26: [28553]: RECV FAX (000001637):
> recvq/fax000001628.tif from 901 888 6305, route to <unspecified>, 1
> pages in 0:00:41
> Apr 16 12:37:56.26: [28553]: RECV FAX: T.30 T2 timeout, expected signal
> not received
>
I'm going to guess here two things: 1) there was some kind of audio
cut-out at 12:37:42.02 at which point the carrier was lost, and 2) the
modem mistakenly "CONNECT"s on V.17 audio when looking for V.21 HDLC.
HylaFAX+ 5.5.0 will have a slightly different behavior, I believe, in
the #2 kind of scenario. It's possible that it could recover where
hylafax.org's 6.0.3 cannot.
>> They could be voice calls. The line could have problems.
>>
>
> I thought they might be errant voice calls or line problems. However,
> wouldn't I have seen the handshake errors when the modem was configured
> as a class one as well?
I believe that you did see them, as I note above.
Thanks,
Lee.