Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] Howto enforce Hylafax to correctly encode incoming faxes?
....
>Sep 25 15:17:03 linux1 FaxGetty[29666]: <-- [12:AT+FCLASS=?\r]
>Sep 25 15:17:04 linux1 FaxGetty[29666]: --> [7:0,1,2.0]
>Sep 25 15:17:04 linux1 FaxGetty[29666]: --> [2:OK]
>Sep 25 15:17:04 linux1 FaxGetty[29666]: MODEM Supports "Data"
>Sep 25 15:17:04 linux1 FaxGetty[29666]: MODEM Supports "Class 1"
>Sep 25 15:17:04 linux1 FaxGetty[29666]: MODEM Supports "Class 2.0"
>Sep 25 15:17:04 linux1 FaxGetty[29666]: <-- [14:AT+FCLASS=2.0\r]
>Sep 25 15:17:04 linux1 FaxGetty[29666]: --> [2:OK]
>Sep 25 15:17:04 linux1 FaxGetty[29666]: <-- [8:AT+FMI?\r]
>Sep 25 15:17:04 linux1 FaxGetty[29666]: --> [23:U.S. Robotics 56K Voice]
>Sep 25 15:17:04 linux1 FaxGetty[29666]: --> [2:OK]
>Sep 25 15:17:04 linux1 FaxGetty[29666]: MODEM: Mfr U.S. Robotics 56K Voice
Bernd, my recommendation would be that of Dmitry's, which is: use Class 1.
You'll avoid some serious timing issues that cropped up on me every once in
a while.
....
>Sep 25 15:17:06 linux1 FaxGetty[29666]: <-- [9:AT+FAP=?\r]
>Sep 25 15:17:06 linux1 FaxGetty[29666]: --> [5:ERROR]
This is that darn Class2APQueryCmd which has a coded default of "AT+FAP=?".
I've never seen this terminate a fax, and I think that HylaFAX ignores the
ERROR here, but I think you'd be best to put 'Class2APQueryCmd: "" ' in
your config file.
>Sep 25 15:17:08 linux1 FaxGetty[29666]: <-- [9:AT+FBU=1\r]
>Sep 25 15:17:09 linux1 FaxGetty[29666]: --> [5:ERROR]
>Sep 25 15:17:09 linux1 FaxGetty[29666]: MODEM Command error
I've been complaining about this during the past week. The coded default
HylaFAX setting for Class2BUGCmd is "AT+FBU=1", which won't work on many
modems. So, in your config file, put: 'Class2BUGCmd: AT+FBU=0' or
'Class2BUGCmd: AT'
>> Oh, USR Sportster in Class 2.0 mode. Are you really looking for
>> trouble? :-)
>This is just for testing client software, no need in good performance over
>the phone line.
>
>BTW, is USR receiving with Class 2.0 as bad as sending?
The receiving is worse than the sending, in my opinion. Its performance is
fair... it will work in 2.0 fairly well, but errors will be common.
Lee.
____________________ HylaFAX(tm) Users Mailing List _______________________
To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null