Re: [hylafax-users] Frame Number Errors

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

On 2005.01.18 10:27 Adam Engel wrote:

> Jan 18 13:10:40.59: [ 4775]: RECV received frame number 98
> Jan 18 13:10:40.77: [ 4775]: RECV received frame number 99
> Jan 18 13:10:40.95: [ 4775]: RECV received frame number 100
> Jan 18 13:10:41.05: [ 4775]: Bad HDLC terminating flag received.
> Jan 18 13:10:41.16: [ 4775]: RECV assumed RCP frame with block end
> Jan 18 13:10:41.16: [ 4775]: --> [10:NO CARRIER]
> Jan 18 13:10:41.16: [ 4775]: <-- [9:AT+FRH=3\r]
> Jan 18 13:10:43.96: [ 4775]: --> [7:CONNECT]
> Jan 18 13:10:48.97: [ 4775]: --> [2:OK]
> Jan 18 13:10:48.97: [ 4775]: RECV keeping unconfirmed page

Well, the logging isn't turned up high enough for me to know what HDLC 
message was received between the CONNECT and the OK, but I'm guessing 
that it was DCN.

Looking at things we see the sender cut-off its data transmission 
abnormally at 13:10:41.05.  And then a long pause (3 seconds) before 
the assumed DCN signal, and, well, it looks like the sender simply 
screwed up... at least on HylaFAX's viewpoint.  Maybe something went 
wrong with the line or the modem or yes maybe the serial port.

Is the problem with the same sender each time?

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@xxxxxxxxx*