HylaFAX The world's
most advanced open source fax server
|
Hi,
After upgrading my system to Debian Lenny (with Hylafax 4.4.4
(Debian version 2:4.4.4-10.1)), my ELSA MicroLink 56k can no longer receive
incoming fax transmissions. Error message is
| [...]
| Feb 16 14:38:33.99: [ 3358]: STATE CHANGE: ANSWERING -> RECEIVING
| Feb 16 14:38:38.98: [ 3358]: --> [27:+FTI:" b.com Computer AG"]
| Feb 16 14:38:38.98: [ 3358]: REMOTE TSI "b.com Computer AG"
| Feb 16 14:38:38.98: [ 3358]: --> [20:+FCS:0,5,0,2,0,0,0,0]
| Feb 16 14:38:38.98: [ 3358]: MODEM protocol botch, can not parse "0,5,0,2,0,0,0,0"
| Feb 16 14:38:38.98: [ 3358]: REMOTE HANGUP: COMREC error (code 72)
| ...
I browsed the source code and I think this problem could be caused by
"useJP" incorrectly set to true.
In Class2Modem::parseRange, where +FCC is checked:
Feb 17 10:39:20 tardis FaxGetty[18561]: <-- [9:AT+FCC=?\r]
Feb 17 10:39:20 tardis FaxGetty[18561]: --> [45:(0,1),(0-5),(0-2),(0-2),(0),(0),(0),(0-7),(0)]
Feb 17 10:39:20 tardis FaxGetty[18561]: --> [2:OK]
useJP is set to true
# masked = 1;
# if (vparseRange(cp, masked, 9, &n,&n,&n,&n,&n,&n,&n,&n,&p.jp)) {
# useJP = true;
In Class2Modem::parseClass2Capabilities
when useJP is true, it requires 9 arguments for +FCS. The modem only
returns 8
| [20:+FCS:0,5,0,2,0,0,0,0]
Modem type:
| "MicroLink 56k","Revision "Version 1.66 / 11.06.1999"
I'm not sure if the analysis is correct, though.
Does anyone know a workaround for the problem?
Thanks in advance,
Cheers,
Michael
--
Michael Bussmann <bus@xxxxxxxxxx>
BOFH excuse #97:
Small animal kamikaze attack on power supplies
Attachment:
signature.asc
Description: Digital signature