Re: [hylafax-users] Sedlbauer ISDN card

[Lee Howard <faxguy@deanox.com>]

At 06:04 PM 8/16/01 +0200, Moritz Both wrote:
>
>
>Lee Howard <faxguy@deanox.com> worte on Donnerstag, 16. August 2001:
>
>> [...]
>> Please turn SessionTracing to 0xFFF and resend a new log.
>
>Here it is.
>
>The lines
>
>    Aug 16 17:51:39.93: [ 5012]: <-- [10:AT+FRM=96\r]
>    Aug 16 17:51:43.34: [ 5012]: --> [7:FCERROR]
>
>seem to suggest something goes wrong. Possibly this has to do with the
>fact that this - really old - fax machine has to do with polling in
>the next sheet and the hylafax (or the isdn modem emulation) expects a
>somewhat quicker peer?

Actually, FCERROR and ERROR are normal ways for a modem to tell us "!OK".
Usually they don't mean that there was an error, but rather that the
previous command, being used as a boolean test, produces a false result
rather than a true result (which usually would be OK or CONNECT).  So
nobody needs to worry about seeing FCERROR in their logs.

....
>Aug 16 17:51:00.46: [ 5012]: TRAINING succeeded
>Aug 16 17:51:00.46: [ 5012]: MODEM input buffering enabled
>Aug 16 17:51:00.46: [ 5012]: MODEM set XON/XOFF/FLUSH: input ignored,
output generated
>Aug 16 17:51:00.46: [ 5012]: <-- [10:AT+FRM=96\r]
>Aug 16 17:51:01.73: [ 5012]: --> [7:CONNECT]

We know that everything is okay at this point because +FRM=96 requires for
us to hear the carrier from the sender.

>Aug 16 17:51:01.73: [ 5012]: RECV: begin page
>Aug 16 17:51:38.60: [ 5012]: RECV/CQ: Bad 1D pixel count, row 1158, got 0,
expected 1728
>Aug 16 17:51:38.60: [ 5012]: RECV/CQ: Bad 1D pixel count, row 1159, got 0,
expected 1728
>Aug 16 17:51:38.60: [ 5012]: RECV/CQ: Bad 1D pixel count, row 1160, got 0,
expected 1728
>Aug 16 17:51:38.60: [ 5012]: RECV/CQ: Bad 1D pixel count, row 1161, got 0,
expected 1728
>Aug 16 17:51:38.60: [ 5012]: RECV/CQ: Bad 1D pixel count, row 1162, got 0,
expected 1728

All of this is an exhibition of cqtest's inability to recognize RTC before
we see all of it, which is picked up in this next line.  So these are not a
concern.

>Aug 16 17:51:38.60: [ 5012]: RECV/CQ: Adjusting for RTC found at row 1157
>Aug 16 17:51:38.60: [ 5012]: RECV: 1157 total lines, 0 bad lines, 0
consecutive bad lines

This is an indication that the communication is good between the systems.

>Aug 16 17:51:38.60: [ 5012]: RECV: end page
>Aug 16 17:51:38.60: [ 5012]: --> [10:NO CARRIER]
>Aug 16 17:51:38.60: [ 5012]: MODEM set XON/XOFF/DRAIN: input ignored,
output disabled
>Aug 16 17:51:38.60: [ 5012]: MODEM input buffering disabled
>Aug 16 17:51:38.60: [ 5012]: <-- [9:AT+FRH=3\r]
>Aug 16 17:51:38.71: [ 5012]: --> [7:CONNECT]
>Aug 16 17:51:39.78: [ 5012]: --> HDLC<5:FF C8 F2 AC A0>
>Aug 16 17:51:39.78: [ 5012]: --> [2:OK]
>Aug 16 17:51:39.78: [ 5012]: RECV recv MPS (more pages, same document)

We're still connected here...

>Aug 16 17:51:39.78: [ 5012]: DELAY 150 ms
>Aug 16 17:51:39.93: [ 5012]: <-- [9:AT+FTH=3\r]
>Aug 16 17:51:39.93: [ 5012]: --> [10:NO CARRIER]

Now we're not connected.  My guess would be that the remote didn't like our
150 ms delay.  Try setting Class1SwitchingDelay to lesser settings (75, 0),
restart faxgetty, and then try again.  If this turns out to be the case,
please report what the greatest value was that functioned for you.

>Aug 16 17:51:39.93: [ 5012]: RECV send MCF (message confirmation)
>Aug 16 17:51:39.93: [ 5012]: RECV FAX (00000026): from +49 511 713496,
page 1 in 0:39, INF, 3.85 line/mm, 1-D MR, 9600 bit/s
>Aug 16 17:51:39.93: [ 5012]: MODEM input buffering enabled
>Aug 16 17:51:39.93: [ 5012]: MODEM set XON/XOFF/FLUSH: input ignored,
output generated
>Aug 16 17:51:39.93: [ 5012]: <-- [10:AT+FRM=96\r]
>Aug 16 17:51:43.34: [ 5012]: --> [7:FCERROR]

And by this time (17:51:39.93) the remote has hung up, so we get FCERROR...
and then we hang up, too.

Lee.



____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null