Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] T.30 T2 timeout errors
Lee,
I do not see the "Class1SwitchingCmd" option in the hylafax config
documentation, is this new with 1.4.8?
I put the line: "Class1SwitchingCmd: <delay:7>" exactly as you typed it into
my "config.ttyS1" config file including the "<" and ">" symbols, is this
correct?
You also mentioned that this is a common problem with the USR modem. Would
you be able to recomend something better? I only used this modem because it
was given to me, but buying a new modem specificly for hylafax would not be
out of the question.
I will write back with the resaults of this configuration.
Thanks again,
steve
> On 2004.07.12 13:32 Steve Melo wrote:
>
> > Jul 12 16:20:23.38: [15990]: <-- [9:AT+FRH=3\r]
> > Jul 12 16:20:23.56: [15990]: --> [7:CONNECT]
> > Jul 12 16:20:24.57: [15990]: --> HDLC<5:FF C8 F2 AC A0>
> > Jul 12 16:20:24.57: [15990]: --> [2:OK]
> > Jul 12 16:20:24.57: [15990]: RECV recv MPS (more pages, same document)
> > Jul 12 16:20:24.57: [15990]: <-- [9:AT+FRS=7\r]
> > Jul 12 16:20:24.68: [15990]: --> [2:OK]
> > Jul 12 16:20:24.68: [15990]: <-- [9:AT+FTH=3\r]
> > Jul 12 16:20:54.68: [15990]: MODEM TIMEOUT: reading line from modem
> > Jul 12 16:20:54.68: [15990]: MODEM <Timeout>
> > Jul 12 16:20:54.68: [15990]: RECV send MCF (message confirmation)
> > Jul 12 16:20:54.68: [15990]: RECV FAX (00002399): from <UNSPECIFIED>,
> > page 2
> > in 0:54, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
> > Jul 12 16:20:54.68: [15990]: <-- HDLC<3:FF C8 31>
> > Jul 12 16:20:57.23: [15990]: --> [5:ÿO]
>
> Translated into english:
>
> (After receiving a page of image data...) We successfully raise the
> message reception carrier and receive the MPS signal indicating more
> pages of image data are yet to come. We successfully wait for 70 ms of
> silence before attempting to raise the message transmission carrier to
> send the message confirmation signal (MCF). However, the modem cannot
> raise the transmission carrier for some reason, and HylaFAX never gets
> back a response from the modem for 30 seconds, at which point it
> times-out. By this time the fax session would be lost anyway, but
> HylaFAX sends the MCF signal data anyway and gets back garbage from the
> modem. That "garbage" (actually data sent from the modem to the
> computer at a different baud rate than what we're expecting) is what
> the modem spits out when it "resets" internally.
>
> So in other words, something happened during the fax session that
> caused the modem to reset itself. This is a modem firmware bug, and is
> very commonplace with USR modems. You can choose to live with it, try
> to get USR to fix it, or get a new modem.
>
> However, this kind of problem only became noticeable recently (i.e.,
> prior to 4.1.3 I don't remember anyone complaining about stuff like
> this). So, I have suspicions that the AT+FRS=7 command may be
> influencing the modem's behavior. If so, you may be able to alleviate
> this by setting "Class1SwitchingCmd: <delay:7>" in your modem config
> file. If that works for you, please let us know.
>
> Lee.
>
____________________ 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*