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] failed fax reception



On 2003.09.07 08:10 George Bell wrote:

My fax modem: MT5645ZPX-PCI in mode 2.0
In config.ttySN I have
MaxConsecutiveBadLines:    5
PercentGoodLines:               95
Class2CQCmd:                    AT+FCQ=1,0
Class2CQQueryCmd:            AT+FCQ=?

The person at the Panasonic machine tried to send me the fax twice
with
nearly the same resulting errors.  I've included the first attempt  in

"firstfax.log".   Thanks any idea what happened and what the "A2"
error
means.  Hylafax does not seem to know what it means either.

....
Sep 06 21:19:29.02: [  785]: --> [7:CONNECT]
Sep 06 21:19:29.02: [  785]: RECV: begin page
Sep 06 21:19:29.02: [  785]: RECV: send trigger 022
Sep 06 21:19:29.02: [  785]: <-- data [1]
Sep 06 21:19:33.78: [  785]: RECV: 1784 bytes of data, 3 total lines
Sep 06 21:19:33.78: [  785]: --> [14:+FPS:2,0,2,2,0]
Sep 06 21:19:37.85: [  785]: --> [7:+FHS:A2]
Sep 06 21:19:37.85: [  785]: REMOTE HANGUP: COMREC invalid response
received (code A2)

HylaFAX knows exactly what it means and it is saying it: "COMREC invalid response received". This is defined by ITU T.32.


This basically means that we, as the receiver, sent some signal to the sender, say perhaps, RTN, and instead got an invalid response, say perhaps DCN.

Because you're running Class 2.0 it's quite impossible for us to determine exactly what those signals were, but based on your session paramters and the +FPS: response, I'd say RTN and DCN are the likely candidates. So if that's the case then the signal behavior is actually "proper" by both the modem and the fax machine, but the real issue lies in the discovery of why the modem is rejecting page quality... or, rather, why the modem isn't "hearing" any lines at all (that seems to be indicated by the +FPS: response).

So, at this point, you can try Class 1 and see how you fare there. If it works repeatedly without RTN appearing in the log at all when using Class 1 and if this error appears repeatedly when using Class 2.0, then you'd need to bring up the matter with MultiTech. If RTN appears regularly in Class 1 logs, then you should probably try to determine why the data is becoming distorted/lost between the sender and the receiver.

Lee.

____________________ 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@xxxxxxxxxxxx*




Project hosted by iFAX Solutions