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] COMREC error (code 72) with 4.4.4 + ELSA MicroLink



* Michael Bussmann <hylafax@xxxxxxxxxx> [090217 07:54]:

> 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]

So the modem reports the 9-argument responce.

> useJP is set to true
> 
> | [...]
> | 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)

But then only gives the 8-value string here...
 
> I'm not sure if the analysis is correct, though.
> 
> Does anyone know a workaround for the problem?

It looks correct.  It looks like the modem responds to +FCC=? claiming
the 9-argument format, so we expect it to be consistent.

You could use Class2DCCQueryCmd to "force" the response to be the
8-argument command (see the hylafax-config man page), so useJP doesn't
get set.

a.


-- 
Aidan Van Dyk                                             aidan@xxxxxxxx
Senior Software Developer                          +1 215 825-8700 x8103
iFAX Solutions, Inc.                                http://www.ifax.com/

Attachment: signature.asc
Description: Digital signature




Project hosted by iFAX Solutions