Re: [hylafax-users] List of all hylafax error codes

["James Smith" <James.Smith@xxxxxxxxx>]

I was having quite poor performance on receiving until i updated the
firmware on my modems (all USR) - it may be worth a try checking your
firmware versions if theyre flashable



-----Original Message-----
From: hylafax-users-bounce@xxxxxxxxxxx
[mailto:hylafax-users-bounce@xxxxxxxxxxx] On Behalf Of George H
Sent: Friday, January 04, 2008 1:10 PM
To: hylafax-users@xxxxxxxxxxx
Subject: Re: [hylafax-users] List of all hylafax error codes

On Jan 3, 2008 11:01 PM, George H <george.dma@xxxxxxxxx> wrote:
>
> On Jan 3, 2008 7:53 PM, Lee Howard <faxguy@xxxxxxxxxxxxxxxx> wrote:
> > George H wrote:
> > > On Jan 3, 2008 1:07 AM, Lee Howard <faxguy@xxxxxxxxxxxxxxxx>
wrote:
> > >
> > >> George H wrote:
> > >>
> > >>> hmm the sender was HylaFAX+ 5.2.0 and the receiver is one of
those
> > >>> photocopy machines that has fax receive capability. I sent 30
faxes
> > >>> and each one consistently gave a E124 error on the first attempt
and
> > >>> then on the second attempt it successfully was received. So this
> > >>> happened 30 times.
> > >>>
> > >>> Don't know if this makes a different but it was hylafax dialing
out of
> > >>> our PSTN (PBX) going through the telco then back into our PSTN
to a
> > >>> fax machine.
> > >>>
> > >> If you send me the corresponding send and receive session logs it
would
> > >> certainly help me make sense of it.
> >
> > Here's the relevant portion of the log...
> >
> > > Dec 28 17:56:05.98: [19165]: SEND send PPS (partial page signal)
> > > Dec 28 17:56:05.98: [19165]: SEND send EOM (more documents)
> > > Dec 28 17:56:05.98: [19165]: <-- [9:AT+FRH=3\r]
> > > Dec 28 17:56:06.57: [19165]: --> [7:CONNECT]
> > > Dec 28 17:56:07.40: [19165]: --> HDLC<5:FF C8 31 45 8F>
> > > Dec 28 17:56:07.40: [19165]: --> [2:OK]
> > > Dec 28 17:56:07.40: [19165]: SEND recv MCF (message confirmation)
> > > Dec 28 17:56:07.40: [19165]: DELAY 70 ms
> > > Dec 28 17:56:07.48: [19165]: SEND end page
> > > Dec 28 17:56:07.48: [19165]: SEND FAX (000000120): FROM
> > > faxadmin@xxxxxxxxxxxxxxxxxxxxx TO 6701766200&&&&&2679 (page 1 of 1
> > > sent in 0:00:12)
> > > Dec 28 17:56:07.48: [19165]: SEND FAX (000000120): FROM
> > > faxadmin@xxxxxxxxxxxxxxxxxxxxx TO 6701766200&&&&&2679
> > > (docq/doc54.ps;f0 sent in 0:00:12)
> > > Dec 28 17:56:09.48: [19165]: SEND FAX: JOB 39 DEST
6701766200&&&&&2679
> > > COMMID 000000120 DEVICE '/dev/ttyS0' FROM 'Fax Administrator
> > > <faxadmin@xxxxxxxxxxxxxxxxxxxxx>' USER uucp
> > > Dec 28 17:56:09.48: [19165]: MODEM set XON/XOFF/FLUSH: input
ignored,
> > > output disabled
> > > Dec 28 17:56:09.48: [19165]: <-- [9:AT+FRH=3\r]
> > > Dec 28 17:56:09.54: [19165]: --> [7:CONNECT]
> > > Dec 28 17:56:09.54: [19165]: --> [2:10 03]
> > > Dec 28 17:56:09.54: [19165]: --> [5:ERROR]
> > > Dec 28 17:56:09.54: [19165]: MODEM Command error
> >
> > The translation here is ... this was a batch of jobs.  We send the
first
> > job/document and terminate it with an EOM signal... which means end
of
> > document, but more documents are coming.
> >
> > After hearing MCF to EOM the sender is supposed to just sit and
wait,
> > listening for the receiver's Phase B signalling (NSF, CSI, DIS) -
yes,
> > after EOM the fax procedures go back to step 1... EOM is merely to
save
> > ourselves from placing another call or to allow document formatting
to
> > change.
> >
> > The sender is supposed to expect to wait for maybe up to 7 or more
> > seconds of silence before hearing the receiver's Phase B... because
the
> > receiver is, per spec, instructed to just wait that long before
> > proceeding.  However, 2.14 seconds after hearing MCF the modem
reports
> > that it hears V.21 HDLC signalling (which would be okay, HylaFAX is
okay
> > with receivers who don't wait a full 7 seconds there)... but then
that
> > signalling stops... and then HylaFAX enters recovery procedures with
CRP
> > and the receiver disconnects (with DCN).
> >
> > So... either the receiver does not support batching (normally
HylaFAX
> > can detect it, remember it, and will disable batching to that
> > destination from then on - which did not happen in this case... thus
you
> > had 30 phone calls and 29 errors), or your modem is incorrectly
> > reporting V.21 HDLC detection.
> >
> > If this is a Lucent/Agere/LSI-based-chipsetted modem (Multitech 5634
or
> > Mainpine) then you need this in your modem configuration file:
> >
> > Class1HasRHConnectBug:  yes
> >
> > Thanks,
> >
> > Lee.
>
> This was using a US robotics modem, but since this seems to be a
> consistent behavior I will do the same test with one of my multitech
> modems and see if I get the same result or not.
>
> Thanks

I tried the same test with a Multitech modem not the same model as you
mentioned but a different one. I saw 2 differences.
1: The usr modem would sent 30 faxes 1 at a time, and xferfaxlog would
show 1 error per send.
2: The multitech modem sent 10 faxes in 2 batches, First 1 came, then
5 in a row, then 4 in a row. Zero errors in xferfaxlog

I guess this proves the multitechs I have outperform the USR.
I don't supposed I can return the USR modems back the manufacturer can I
? :)

> --
> "Nothing is impossible for the person that doesn't have to do it"
> "The probability of anything happening is in inverse ratio to its
desirability"
> --
> George H
> george.dma@xxxxxxxxx
>


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


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