Lee (or others):
MultiTech did the trick!!!!
Another Question:
Replaced the USR's with MultiTech MT5634ZBA-V92, when using
faxaddmodem
to configure should these modems be changed to class 2 or 2.1 or
should I
take the default of class 1?
Thanks in advance,
Jim Ginn
> On 2004.11.16 14:23 Jim Ginn wrote:
>> We frequently get errors (Phase C) on multipage (ie. 6 page)
>> documents.
>> Seems smaller jobs are OK. We're running Hylafax 4.2.0-1 on Fedora
>> 2.6.8-1.521 with Digiboard Portserver II with USR Sportster modems.
>
> As Pedro mentioned, you'll see that the USR modems are the root of
all
> fax evil.
>
>> The tail of the log:
>> Nov 16 16:28:13.37: [25079]: SEND send frame number 9
>> Nov 16 16:28:13.37: [25079]: SEND send frame number 10
>> Nov 16 16:28:13.37: [25079]: SEND send frame number 11
>> Nov 16 16:28:13.37: [25079]: DELAY 200 ms
>> Nov 16 16:28:13.57: [25079]: <-- [10:AT+FTM=96\r]
>> Nov 16 16:28:43.57: [25079]: MODEM <Timeout>
>> Nov 16 16:28:43.57: [25079]: SEND end page
>> Nov 16 16:28:43.57: [25079]: Unspecified Transmit Phase C error
>> Nov 16 16:28:43.57: [25079]: <-- [9:AT+FTH=3\r]
>> Nov 16 16:28:43.85: [25079]: --> [8:AT+FTH=3]
>> Nov 16 16:28:43.85: [25079]: <-- [5:ATH0\r]
>> Nov 16 16:28:43.85: [25079]: --> [5:ERROR]
>> Nov 16 16:28:43.85: [25079]: MODEM Command error
>> Nov 16 16:28:43.87: [25079]: SESSION END
>
> The fact that you get an echo (AT+FTH=3 is echoed) indicates that
the
> modem was reset. HylaFAX didn't reset the modem, of course. The
modem
> did it on its own due to its internal firmware bugs.
>
> A lot of people have seen this kind of problem with USR modems.
Some
> people have been able to work around the Class 1 firmware flaws in
the
> USRs by not using AT+FTS/AT+FRS commands. See
> /var/spool/hylafax/config/topic for examples on what to do to your
> config file to disable AT+FTS/AT+FRS.
>
> But, a lot of people just solve the problem by getting new modems.
>
> Lee.
>
>
