 HylaFAX The world's
most advanced open source fax server
|
[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]
[hylafax-users] T.30 T2 timeout, expected signal not received
- To: hylafax-users@xxxxxxxxxxx
- Subject: [hylafax-users] T.30 T2 timeout, expected signal not received
- From: Mike Warfe <jmwarfe@xxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 11 May 2006 10:25:11 -0400
Hi, can anyone help me with this problem?
DataFormat: 2-D MMR ErrCorrect: Yes ReceivedOn: ttyS0
The full document was not received because:
T.30 T2 timeout, expected signal not received
---- Transcript of session follows ----
May 11 10:22:12.99: [ 3657]: SESSION BEGIN 000000208 12163686126 May 11 10:22:12.99: [ 3657]: HylaFAX (tm) Version 4.2.5 May 11 10:22:12.99: [ 3657]: <-- [13:AT+FCLASS=1A\r] May 11 10:22:18.44: [ 3657]: --> [7:CONNECT] May 11 10:22:18.44: [ 3657]: ANSWER: FAX CONNECTION DEVICE '/dev/ttyS0' May 11 10:22:18.44: [ 3657]: RECV FAX: begin May 11 10:22:18.60: [ 3657]: --> [7:CONNECT] May 11 10:22:19.32: [ 3657]: --> [7:CONNECT] May 11 10:22:21.59: [ 3657]: --> [2:OK] May 11 10:22:21.59: [ 3657]: <-- [9:AT+FRH=3\r] May 11 10:22:22.67: [ 3657]: --> [7:CONNECT] May 11 10:22:24.29: [ 3657]: --> [2:OK] May 11 10:22:24.29: [ 3657]: REMOTE TSI "+12163684880" May 11 10:22:24.29: [ 3657]: <-- [9:AT+FRH=3\r] May 11 10:22:24.30: [ 3657]: --> [7:CONNECT] May 11 10:22:24.61: [ 3657]: --> [2:OK] May 11 10:22:24.61: [ 3657]: REMOTE wants 14400 bit/s May 11 10:22:24.61: [ 3657]: REMOTE wants A4 page width (215 mm) May 11 10:22:24.61: [ 3657]: REMOTE wants unlimited page length May 11 10:22:24.61: [ 3657]: REMOTE wants 3.85 line/mm May 11 10:22:24.61: [ 3657]: REMOTE wants 2-D MMR May 11 10:22:24.61: [ 3657]: REMOTE wants T.30 Annex A, 256-byte ECM May 11 10:22:24.61: [ 3657]: RECV training at v.17 14400 bit/s May 11 10:22:24.61: [ 3657]: <-- [11:AT+FRM=145\r] May 11 10:22:26.41: [ 3657]: --> [7:CONNECT] May 11 10:22:27.96: [ 3657]: RECV: TCF 2811 bytes, 2% non-zero, 2730 zero-run May 11 10:22:27.97: [ 3657]: --> [10:NO CARRIER] May 11 10:22:27.97: [ 3657]: DELAY 70 ms May 11 10:22:28.04: [ 3657]: TRAINING succeeded May 11 10:22:28.05: [ 3657]: <-- [9:AT+FTH=3\r] May 11 10:22:28.24: [ 3657]: --> [7:CONNECT] May 11 10:22:29.42: [ 3657]: --> [2:OK] May 11 10:22:29.42: [ 3657]: <-- [11:AT+FRM=146\r] May 11 10:22:30.52: [ 3657]: --> [7:CONNECT] May 11 10:22:30.94: [ 3657]: RECV received frame number 0 May 11 10:22:31.08: [ 3657]: RECV received frame number 1 May 11 10:22:31.22: [ 3657]: RECV received frame number 2 May 11 10:22:31.36: [ 3657]: RECV received frame number 3 May 11 10:22:31.50: [ 3657]: RECV received frame number 4 May 11 10:22:31.70: [ 3657]: RECV received frame number 5 May 11 10:22:31.84: [ 3657]: RECV received frame number 6 May 11 10:22:31.99: [ 3657]: RECV received frame number 7 May 11 10:22:32.13: [ 3657]: RECV received frame number 8 May 11 10:22:32.27: [ 3657]: RECV received frame number 9 May 11 10:22:32.41: [ 3657]: RECV received frame number 10 May 11 10:22:32.55: [ 3657]: RECV received frame number 11 May 11 10:22:32.76: [ 3657]: RECV received frame number 12 May 11 10:22:32.90: [ 3657]: RECV received frame number 13 May 11 10:22:33.04: [ 3657]: RECV received frame number 14 May 11 10:22:33.18: [ 3657]: RECV received frame number 15 May 11 10:22:33.32: [ 3657]: RECV received frame number 16 May 11 10:22:33.46: [ 3657]: RECV received frame number 17 May 11 10:22:33.60: [ 3657]: RECV received frame number 18 May 11 10:22:33.74: [ 3657]: RECV received frame number 19 May 11 10:22:33.95: [ 3657]: RECV received frame number 20 May 11 10:22:34.18: [ 3657]: RECV received frame number 21 May 11 10:22:34.18: [ 3657]: RECV frame FCS check failed May 11 10:22:34.18: [ 3657]: HDLC frame not byte-oriented. Trailing byte: 0 May 11 10:22:34.19: [ 3657]: Bad HDLC terminating flag received. May 11 10:22:34.19: [ 3657]: HDLC frame with bad address field 0x91 May 11 10:22:34.19: [ 3657]: RECV assumed RCP frame with block end May 11 10:22:34.19: [ 3657]: --> [10:NO CARRIER] May 11 10:22:34.19: [ 3657]: <-- [9:AT+FRH=3\r] May 11 10:22:38.73: [ 3657]: --> [7:CONNECT] May 11 10:22:38.90: [ 3657]: --> [5:ERROR] May 11 10:22:38.90: [ 3657]: MODEM Command error May 11 10:22:38.90: [ 3657]: FCS error May 11 10:22:38.90: [ 3657]: DELAY 70 ms May 11 10:22:38.97: [ 3657]: <-- [9:AT+FTH=3\r] May 11 10:22:39.16: [ 3657]: --> [7:CONNECT] May 11 10:22:40.34: [ 3657]: --> [2:OK] May 11 10:22:40.34: [ 3657]: RECV send CRP (command repeat) May 11 10:22:40.34: [ 3657]: <-- [9:AT+FRH=3\r] May 11 10:22:42.67: [ 3657]: --> [10:NO CARRIER] May 11 10:22:42.67: [ 3657]: MODEM No carrier May 11 10:22:42.67: [ 3657]: RECV keeping unconfirmed page May 11 10:22:42.71: [ 3657]: RECV: 5376 bytes of data, 487 total lines May 11 10:22:42.71: [ 3657]: RECV FAX (000000208): from +12163684880, page 1 in 0:24, INF, 3.85 line/mm, 2-D MMR, 14400 bit/s May 11 10:22:42.72: [ 3657]: RECV FAX (000000208): recvq/fax000000207.tif from +12163684880, route to <unspecified>, 1 pages in 0:24 May 11 10:22:42.72: [ 3657]: RECV FAX: T.30 T2 timeout, expected signal not received May 11 10:22:42.72: [ 3657]: <-- [9:AT+FTH=3\r] May 11 10:22:42.91: [ 3657]: --> [7:CONNECT] May 11 10:22:44.09: [ 3657]: --> [2:OK] May 11 10:22:44.09: [ 3657]: RECV FAX (000000208): session with +12163684880 terminated abnormally: T.30 T2 timeout, expected signal not received May 11 10:22:44.09: [ 3657]: RECV FAX: bin/faxrcvd "recvq/fax000000207.tif" "ttyS0" "000000208" "T.30 T2 timeout, expected signal not received" May 11 10:22:44.09: [ 3657]: RECV FAX: end May 11 10:22:44.09: [ 3657]: SESSION END
My Config
# $Id: usr-xon,v 1.11 2005/11/29 21:28:57 lhoward Exp $
#
# HylaFAX Facsimile Software
#
# Copyright (c) 1990-1996 Sam Leffler
# Copyright (c) 1991-1996 Silicon Graphics, Inc.
# HylaFAX is a trademark of Silicon Graphics, Inc.
# # Permission to use, copy, modify, distribute, and sell this software and # its documentation for any purpose is hereby granted without fee, provided
# that (i) the above copyright notices and this permission notice appear in
# all copies of the software and related documentation, and (ii) the names of
# Sam Leffler and Silicon Graphics may not be used in any advertising or
# publicity relating to the software without the specific, prior written
# permission of Sam Leffler and Silicon Graphics.
# # THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, # EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY # WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. # # IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR
# ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND,
# OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
# WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF # LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE # OF THIS SOFTWARE.
#
#
# Configuration for using the Class 1 command interface with
# a USR Courier or Sportster modem and XON/XOFF flow control. #
#
CountryCode: 1
AreaCode: 216
FAXNumber: +1.216.368.6126
LongDistancePrefix: 1
InternationalPrefix: 011
DialStringRules: etc/dialrules
ServerTracing: 1
SessionTracing: 11
RecvFileMode: 0600
LogFileMode: 0600
DeviceMode: 0600
RingsBeforeAnswer: 1
SpeakerVolume: off
GettyArgs: "-h %l dx_%s"
LocalIdentifier: CaseVRCC
TagLineFont: etc/lutRS18.pcf
TagLineFormat: "From %%l|%c|Page %%P of %%T"
MaxRecvPages: 100
#
#
# 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>"
____________________ 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*
- Follow-Ups:
- Re: [hylafax-users] T.30 T2 timeout, expected signal not received
- From: Lee Howard
- Re: [hylafax-users] T.30 T2 timeout, expected signal not received
- Prev by Date: Re: [hylafax-users] excessive "delay 1500 ms" errors
- Next by Date: Re: [hylafax-users] can use help upgrading....
- Previous by thread: Re: [hylafax-users] excessive "delay 1500 ms" errors
- Next by thread: Re: [hylafax-users] T.30 T2 timeout, expected signal not received
- Index(es):
Project hosted by iFAX Solutions