Re: [hylafax-users] expected signal not received

[Stephen Carville <stephen@xxxxxxxxxxxxxx>]

On Fri August 6 2004 1:02 pm, Lee Howard wrote:
> On 2004.08.06 12:32 Stephen Carville wrote:
> > <sigh>
> >
> > A new error has cropped up.  I upgraded to 4.2.0rc2 and now all my
> > modems are
> > USR.
>
> Well, at least you're openly honest about it ;-)  Such honesty will
> make rehab that much easier for you. :-)

The deal was I had to show hylafax could do the job with what was on hand.  If 
I can prove it, then teh boss will probably spring for the commercial version 
which has drivers for the Brooktrout cards I already have.  At the very least 
he'll buy a Multitech card.

If I cannot prove hylafax will work, the  money will go to upgrade the Windows 
software we used to use.  It would either crash or go off into LaLa land two 
or three times a day but it did deliver the faxes

> > Now I get a complete fax but hylafax tells  the sende their was
> > an
> > error. Is this fixable:
>
> What error message did the sender see?

Dunno.  I'll ask client services Monday for more details.

> > Aug 06 12:18:43.14: [10220]: RECV received frame number 62
> > Aug 06 12:18:43.22: [10220]: RECV received RCP frame
> > Aug 06 12:18:43.37: [10220]: --> [10:NO CARRIER]
> > Aug 06 12:18:43.37: [10220]: <-- [9:AT+FRH=3\r]
> > Aug 06 12:18:44.28: [10220]: --> [7:CONNECT]
> > Aug 06 12:18:44.53: [10220]: --> [5:ERROR]
> > Aug 06 12:18:44.53: [10220]: MODEM Command error
> > Aug 06 12:18:44.53: [10220]: FCS error
> > Aug 06 12:18:44.53: [10220]: <-- [9:AT+FRH=3\r]
> > Aug 06 12:18:44.58: [10220]: --> [7:CONNECT]
> > Aug 06 12:18:45.78: [10220]: --> [5:ERROR]
> > Aug 06 12:18:45.78: [10220]: MODEM Command error
> > Aug 06 12:18:45.78: [10220]: FCS error
> > Aug 06 12:18:45.78: [10220]: <-- [9:AT+FRH=3\r]
> > Aug 06 12:18:47.83: [10220]: --> [10:NO CARRIER]
> > Aug 06 12:18:47.83: [10220]: MODEM No carrier
>
> ....
>
> > Aug 06 12:19:20.63: [10220]: <-- [9:AT+FRH=3\r]
> > Aug 06 12:19:22.68: [10220]: --> [10:NO CARRIER]
> > Aug 06 12:19:22.68: [10220]: MODEM No carrier
> > Aug 06 12:19:22.68: [10220]: RECV keeping unconfirmed page
> > Aug 06 12:19:22.75: [10220]: RECV: 16128 bytes of data, 1074 total
> > lines
>
> Well, if you were to turn off TracingMask and SessionTracing to 0xFFF
> then we'd be able to see those HDLC frames that caused the FCS error in
> the first place, hopefully they'd give us an idea of what the problem
> was.

SessionTrackingI know about but where is TracingMask set?

> But what it looks like is that we only caught part of the HDLC frame
> (post-page message signal, PPS), and this threw the timing off, and the
> sender did not repeat the signal as much as it should.  Maybe there was
> a disconnection.

That's what I figure.  The sender disconnects and the modem gets confued

> Is this error frequent?

About one out of every 20 faxes.

> Lee.

-- 
Stephen Carville
Unix and Network Adminstrator
DPSI
6033 W.Century Blvd.
Los Angeles, CA 90045
310-342-3602

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