HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
Re: [hylafax-users] Problems receiving faxes since upgrade to 4.2.0
--- Nick Baird <nick.baird@xxxxxxxxxxxxx> wrote:
> I have been using Hylafax running on Gentoo linux
> with a US Robotics
> Courier V.34 external modem. Following an upgrade
> from version 4.1.8 to
> 4.2.0 I have started to get major problems receiving
> faxes.
>
> Some faxes are getting through okay, but a large
> proportion aren't.
> Looking at the logs, the following is very typical
> and is repeated
> numeous times:
>
> Nov 24 09:39:46.42: [ 1596]: SESSION BEGIN 000001386
> 4401452507409
> Nov 24 09:39:46.42: [ 1596]: HylaFAX (tm) Version
> 4.2.0
> Nov 24 09:39:46.42: [ 1596]: <-- [13:AT+FCLASS=1A\r]
> Nov 24 09:39:51.80: [ 1596]: --> [7:CONNECT]
> Nov 24 09:39:51.80: [ 1596]: ANSWER: FAX CONNECTION
> DEVICE '/dev/ttyS0'
> Nov 24 09:39:51.80: [ 1596]: RECV FAX: begin
> Nov 24 09:39:51.80: [ 1596]: <-- data [32]
> Nov 24 09:39:51.80: [ 1596]: <-- data [2]
> Nov 24 09:39:53.68: [ 1596]: --> [7:CONNECT]
> Nov 24 09:39:53.68: [ 1596]: <-- data [23]
> Nov 24 09:39:53.68: [ 1596]: <-- data [2]
> Nov 24 09:39:54.84: [ 1596]: --> [7:CONNECT]
> Nov 24 09:39:54.84: [ 1596]: <-- data [10]
> Nov 24 09:39:54.84: [ 1596]: <-- data [2]
> Nov 24 09:39:55.65: [ 1596]: --> [2:OK]
> Nov 24 09:39:55.65: [ 1596]: <-- [9:AT+FRH=3\r]
> Nov 24 09:39:58.75: [ 1596]: --> [0:]
> Nov 24 09:39:58.75: [ 1596]: MODEM <Empty line>
> Nov 24 09:39:58.75: [ 1596]: <-- data [1]
> Nov 24 09:39:58.76: [ 1596]: --> [2:OK]
> Nov 24 09:39:58.76: [ 1596]: DELAY 1500 ms
> Nov 24 09:40:00.26: [ 1596]: <-- [9:AT+FTH=3\r]
> Nov 24 09:40:00.37: [ 1596]: --> [7:CONNECT]
> Nov 24 09:40:00.37: [ 1596]: <-- data [32]
> Nov 24 09:40:00.37: [ 1596]: <-- data [2]
> Nov 24 09:40:02.35: [ 1596]: --> [7:CONNECT]
> Nov 24 09:40:02.35: [ 1596]: <-- data [23]
> Nov 24 09:40:02.35: [ 1596]: <-- data [2]
> Nov 24 09:40:03.51: [ 1596]: --> [7:CONNECT]
> Nov 24 09:40:03.51: [ 1596]: <-- data [10]
> Nov 24 09:40:03.51: [ 1596]: <-- data [2]
> Nov 24 09:40:04.32: [ 1596]: --> [2:OK]
> Nov 24 09:40:04.32: [ 1596]: <-- [9:AT+FRH=3\r]
> Nov 24 09:40:07.42: [ 1596]: --> [0:]
> Nov 24 09:40:07.42: [ 1596]: MODEM <Empty line>
> Nov 24 09:40:07.42: [ 1596]: <-- data [1]
> Nov 24 09:40:07.43: [ 1596]: --> [2:OK]
> Nov 24 09:40:07.43: [ 1596]: DELAY 1500 ms
> Nov 24 09:40:08.93: [ 1596]: <-- [9:AT+FTH=3\r]
> Nov 24 09:40:09.04: [ 1596]: --> [7:CONNECT]
> Nov 24 09:40:09.04: [ 1596]: <-- data [32]
> Nov 24 09:40:09.04: [ 1596]: <-- data [2]
> Nov 24 09:40:11.02: [ 1596]: --> [7:CONNECT]
> Nov 24 09:40:11.02: [ 1596]: <-- data [23]
> Nov 24 09:40:11.02: [ 1596]: <-- data [2]
> Nov 24 09:40:12.18: [ 1596]: --> [7:CONNECT]
> Nov 24 09:40:12.18: [ 1596]: <-- data [10]
> Nov 24 09:40:12.18: [ 1596]: <-- data [2]
> Nov 24 09:40:12.99: [ 1596]: --> [2:OK]
> Nov 24 09:40:12.99: [ 1596]: <-- [9:AT+FRH=3\r]
> Nov 24 09:40:16.09: [ 1596]: --> [0:]
> Nov 24 09:40:16.09: [ 1596]: MODEM <Empty line>
> Nov 24 09:40:16.09: [ 1596]: <-- data [1]
> Nov 24 09:40:16.10: [ 1596]: --> [2:OK]
> Nov 24 09:40:16.10: [ 1596]: DELAY 1500 ms
> Nov 24 09:40:17.60: [ 1596]: <-- [9:AT+FTH=3\r]
> Nov 24 09:40:17.71: [ 1596]: --> [7:CONNECT]
> Nov 24 09:40:17.71: [ 1596]: <-- data [32]
> Nov 24 09:40:17.71: [ 1596]: <-- data [2]
> Nov 24 09:40:19.69: [ 1596]: --> [7:CONNECT]
> Nov 24 09:40:19.69: [ 1596]: <-- data [23]
> Nov 24 09:40:19.69: [ 1596]: <-- data [2]
> Nov 24 09:40:20.85: [ 1596]: --> [7:CONNECT]
> Nov 24 09:40:20.85: [ 1596]: <-- data [10]
> Nov 24 09:40:20.85: [ 1596]: <-- data [2]
> Nov 24 09:40:21.66: [ 1596]: --> [2:OK]
> Nov 24 09:40:21.66: [ 1596]: <-- [9:AT+FRH=3\r]
> Nov 24 09:40:24.76: [ 1596]: --> [0:]
> Nov 24 09:40:24.76: [ 1596]: MODEM <Empty line>
> Nov 24 09:40:24.76: [ 1596]: <-- data [1]
> Nov 24 09:40:24.77: [ 1596]: --> [2:OK]
> Nov 24 09:40:24.77: [ 1596]: DELAY 1500 ms
> Nov 24 09:40:26.27: [ 1596]: <-- [9:AT+FTH=3\r]
> Nov 24 09:40:26.38: [ 1596]: --> [7:CONNECT]
> Nov 24 09:40:26.38: [ 1596]: <-- data [32]
> Nov 24 09:40:26.38: [ 1596]: <-- data [2]
> Nov 24 09:40:28.36: [ 1596]: --> [7:CONNECT]
> Nov 24 09:40:28.36: [ 1596]: <-- data [23]
> Nov 24 09:40:28.36: [ 1596]: <-- data [2]
> Nov 24 09:40:29.52: [ 1596]: --> [7:CONNECT]
> Nov 24 09:40:29.52: [ 1596]: <-- data [10]
> Nov 24 09:40:29.52: [ 1596]: <-- data [2]
> Nov 24 09:40:30.33: [ 1596]: --> [2:OK]
> Nov 24 09:40:30.33: [ 1596]: <-- [9:AT+FRH=3\r]
> Nov 24 09:40:33.43: [ 1596]: --> [0:]
> Nov 24 09:40:33.43: [ 1596]: MODEM <Empty line>
> Nov 24 09:40:33.43: [ 1596]: <-- data [1]
> Nov 24 09:40:33.44: [ 1596]: --> [2:OK]
> Nov 24 09:40:33.44: [ 1596]: RECV FAX: No answer
> (T.30 T1 timeout)
> Nov 24 09:40:33.44: [ 1596]: RECV FAX: end
> Nov 24 09:40:33.44: [ 1596]: SESSION END
>
> I saw a previous post about topic modems. Is this
> the same problem, and
> is the fix the same i.e. wait for 4.2.1, patch
> current source or grab
> latest from CVS?
I think that USR modems don't use Topic chipsets. If
you search the mailling list you will found that USR
modems don't have a firmware upgrade for several years
and that cause alot of troubles. As usuall the advice
goes to droping the USR modem in favour of one with a
Rockwell chiptset. By brands you have Multitech and
Zoom for example. Cheers
Pedro
>
> Thanks,
>
> Nick.
>
>
>
> ____________________ 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*
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
____________________ 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*