Re: [hylafax-users] Class1 vs. Class2

To: John Darrington <john@cellform.com.au>
Subject: Re: [hylafax-users] Class1 vs. Class2
From: Lee Howard <faxguy@howardsilvan.com>
Cc: hylafax-users@hylafax.org
Date: Sun, 5 Jan 2003 13:52:07 -0800

On 2003.01.04 19:26 John Darrington wrote:

> Jan 03 13:17:06.28: [ 9115]: SESSION BEGIN 00000027 6185555555
> Jan 03 13:17:06.28: [ 9115]: HylaFAX (tm) Version 4.1.1

Firstly, allow me to recommend an upgrade.  I don't think it has 
anything to do with the problem, but pre-4.1.3 releases have security 
problems.

> Jan 03 13:17:06.28: [ 9115]: SEND FAX: JOB 4 DEST 5555555 COMMID
> 00000027 DEVICE '/dev/ttyS2'
....
> Jan 03 13:17:14.26: [ 9115]: <-- [12:AT+FCLASS=1\r]
> Jan 03 13:17:14.39: [ 9115]: --> [2:OK]
> Jan 03 13:17:14.39: [ 9115]: DIAL 5555555
> Jan 03 13:17:14.39: [ 9115]: <-- [13:ATDT5555555\r]
> Jan 03 13:17:23.57: [ 9115]: --> [7:CONNECT]
> Jan 03 13:17:23.57: [ 9115]: MODEM input buffering disabled
> Jan 03 13:17:25.34: [ 9115]: --> HDLC<45:FF C0 04 00 00 9E 00 00 00 69
> FE 90 C8 00 08 00 48 A1 03 0B 1F 01 A2 80 92 40 0C 0C 6C 8C 1C 04 9C
> 2C 4C 9C 04 AC 1C 4C 9C 04 C0 F0 0C>
> Jan 03 13:17:25.36: [ 9115]: --> [2:OK]
> Jan 03 13:17:25.36: [ 9115]: REMOTE NSF "00 00 79 00 00 00 96 7F 09 13
> 00 10 00 12 85 C0 D0 F8 80 45 01 49 02 30 30 36 31 38 20 39 34 32 39
> 20 35 38 32 39 20 03 0F"
> Jan 03 13:17:25.36: [ 9115]: NSF remote fax equipment: Panasonic

Okay, this actually tells us something.  The remote system is a 
Panasonic.  This is relevant.

> Jan 03 13:17:25.36: [ 9115]: NSF remote station ID: "00618 9555 5555 "
> Jan 03 13:17:25.36: [ 9115]: <-- [9:AT+FRH=3\r]
> Jan 03 13:17:25.39: [ 9115]: --> [7:CONNECT]
> Jan 03 13:17:25.72: [ 9115]: --> HDLC<12:FF C8 01 04 77 1F 23 01 09 C0
> 28 4B>
> Jan 03 13:17:25.74: [ 9115]: --> [2:OK]
> Jan 03 13:17:25.74: [ 9115]: REMOTE best rate 14400 bit/s
> Jan 03 13:17:25.74: [ 9115]: REMOTE max page width 1728 pixels in 215
> mm
> Jan 03 13:17:25.74: [ 9115]: REMOTE max unlimited page length
> Jan 03 13:17:25.74: [ 9115]: REMOTE best vres 7.7 line/mm
> Jan 03 13:17:25.74: [ 9115]: REMOTE best format 2-D MMR
> Jan 03 13:17:25.74: [ 9115]: REMOTE supports T.30 Annex A, ECM
> Jan 03 13:17:25.74: [ 9115]: REMOTE best 0 ms/scanline
> Jan 03 13:17:25.74: [ 9115]: USE 14400 bit/s
> Jan 03 13:17:25.74: [ 9115]: USE 0 ms/scanline
> Jan 03 13:17:25.74: [ 9115]: SEND file "docq/doc4.cover;40"
> Jan 03 13:17:25.74: [ 9115]: USE page width 1728 pixels in 215 mm
> Jan 03 13:17:25.74: [ 9115]: USE unlimited page length
> Jan 03 13:17:25.74: [ 9115]: USE 3.85 line/mm
> Jan 03 13:17:25.74: [ 9115]: USE 2-D MR
> Jan 03 13:17:25.74: [ 9115]: SEND training at v.17 14400 bit/s

This is also important to notice, also.  We're sending @ 14400 bps, MR, 
low res, US letter.

> Jan 03 13:17:25.74: [ 9115]: <-- [9:AT+FTH=3\r]
> Jan 03 13:17:25.80: [ 9115]: --> [7:CONNECT]
> Jan 03 13:17:25.80: [ 9115]: <-- HDLC<23:FF C0 C2 B6 4E F6 66 36 36 A6
> C2 04 04 04 04 04 04 04 04 04 04 04 04>
> Jan 03 13:17:25.80: [ 9115]: <-- data [23]
> Jan 03 13:17:25.80: [ 9115]: <-- data [2]
> Jan 03 13:17:27.58: [ 9115]: --> [7:CONNECT]
> Jan 03 13:17:27.58: [ 9115]: <-- HDLC<6:FF C8 C1 00 45 1E>
> Jan 03 13:17:27.58: [ 9115]: <-- data [6]
> Jan 03 13:17:27.58: [ 9115]: <-- data [2]
> Jan 03 13:17:28.03: [ 9115]: --> [2:OK]
> Jan 03 13:17:28.03: [ 9115]: <-- [9:AT+FTS=7\r]
> Jan 03 13:17:28.14: [ 9115]: --> [2:OK]
> Jan 03 13:17:28.14: [ 9115]: <-- [11:AT+FTM=145\r]
> Jan 03 13:17:28.19: [ 9115]: --> [7:CONNECT]
> Jan 03 13:17:28.19: [ 9115]: <-- data [1024]
> Jan 03 13:17:28.19: [ 9115]: <-- data [1024]
> Jan 03 13:17:28.19: [ 9115]: <-- data [652]
> Jan 03 13:17:28.19: [ 9115]: <-- data [2]
> Jan 03 13:17:31.31: [ 9115]: --> [2:OK]
> Jan 03 13:17:31.31: [ 9115]: <-- [9:AT+FRH=3\r]
> Jan 03 13:17:32.13: [ 9115]: --> [7:CONNECT]
> Jan 03 13:17:32.96: [ 9115]: --> HDLC<5:FF C8 21 57 BE>
> Jan 03 13:17:32.98: [ 9115]: --> [2:OK]
> Jan 03 13:17:32.98: [ 9115]: TRAINING succeeded

Here's the last moment when we hear from the remote.  From here on we 
don't hear from the remote ever.

> Jan 03 13:17:32.98: [ 9115]: DELAY 75 ms
> Jan 03 13:17:33.06: [ 9115]: <-- [11:AT+FTM=146\r]
> Jan 03 13:17:33.11: [ 9115]: --> [7:CONNECT]
> Jan 03 13:17:33.11: [ 9115]: SEND begin page
> Jan 03 13:17:33.11: [ 9115]: <-- data [1045]
> Jan 03 13:17:33.11: [ 9115]: <-- data [1035]
> Jan 03 13:17:33.11: [ 9115]: <-- data [1027]
> Jan 03 13:17:33.11: [ 9115]: <-- data [1034]
> Jan 03 13:17:35.51: [ 9115]: <-- data [1029]
> Jan 03 13:17:35.51: [ 9115]: <-- data [915]
> Jan 03 13:17:35.51: [ 9115]: SENT 6027 bytes of data
> Jan 03 13:17:35.51: [ 9115]: SEND 2D RTC
> Jan 03 13:17:35.51: [ 9115]: <-- data [30]
> Jan 03 13:17:35.51: [ 9115]: <-- data [2]
> Jan 03 13:17:35.51: [ 9115]: SEND end page
> Jan 03 13:17:35.80: [ 9115]: --> [2:OK]

Page image data is sent.  Now we wait for requisite silence...

> Jan 03 13:17:35.80: [ 9115]: <-- [9:AT+FTS=7\r]
> Jan 03 13:17:37.08: [ 9115]: --> [2:OK]

Done waiting.  Now send the post-page-message, MPS (more pages to 
send)...

> Jan 03 13:17:37.08: [ 9115]: SEND send MPS (more pages, same document)
> Jan 03 13:17:37.08: [ 9115]: <-- [9:AT+FTH=3\r]
> Jan 03 13:17:37.15: [ 9115]: --> [7:CONNECT]
> Jan 03 13:17:37.15: [ 9115]: <-- HDLC<3:FF C8 F2>
> Jan 03 13:17:37.15: [ 9115]: <-- data [3]
> Jan 03 13:17:37.15: [ 9115]: <-- data [2]
> Jan 03 13:17:38.45: [ 9115]: --> [2:OK]

Message sent, now listen for the response (the first time we'll have 
heard from the remote since before page data was sent)...

> Jan 03 13:17:38.45: [ 9115]: <-- [9:AT+FRH=3\r]
> Jan 03 13:17:41.55: [ 9115]: --> [0:]
> Jan 03 13:17:41.55: [ 9115]: MODEM <Empty line>
> Jan 03 13:17:41.55: [ 9115]: MODEM TIMEOUT: waiting for v.21 carrier
> Jan 03 13:17:41.55: [ 9115]: <-- data [1]
> Jan 03 13:17:41.62: [ 9115]: --> [2:OK]

Nothing after 3 seconds of waiting for an answer.  Hrmm... try again, 
maybe it didn't hear us. (?)

> Jan 03 13:17:41.62: [ 9115]: SEND send MPS (more pages, same document)
> Jan 03 13:17:41.62: [ 9115]: <-- [9:AT+FTH=3\r]
> Jan 03 13:17:41.69: [ 9115]: --> [7:CONNECT]
> Jan 03 13:17:41.69: [ 9115]: <-- HDLC<3:FF C8 F2>
> Jan 03 13:17:41.69: [ 9115]: <-- data [3]
> Jan 03 13:17:41.69: [ 9115]: <-- data [2]
> Jan 03 13:17:43.00: [ 9115]: --> [2:OK]
> Jan 03 13:17:43.00: [ 9115]: <-- [9:AT+FRH=3\r]
> Jan 03 13:17:46.10: [ 9115]: --> [0:]
> Jan 03 13:17:46.10: [ 9115]: MODEM <Empty line>
> Jan 03 13:17:46.10: [ 9115]: MODEM TIMEOUT: waiting for v.21 carrier
> Jan 03 13:17:46.10: [ 9115]: <-- data [1]
> Jan 03 13:17:46.18: [ 9115]: --> [2:OK]

Again, nothing.  And so we give it one last try...

> Jan 03 13:17:46.18: [ 9115]: SEND send MPS (more pages, same document)
> Jan 03 13:17:46.18: [ 9115]: <-- [9:AT+FTH=3\r]
> Jan 03 13:17:46.24: [ 9115]: --> [7:CONNECT]
> Jan 03 13:17:46.24: [ 9115]: <-- HDLC<3:FF C8 F2>
> Jan 03 13:17:46.24: [ 9115]: <-- data [3]
> Jan 03 13:17:46.24: [ 9115]: <-- data [2]
> Jan 03 13:17:47.55: [ 9115]: --> [2:OK]
> Jan 03 13:17:47.55: [ 9115]: <-- [9:AT+FRH=3\r]
> Jan 03 13:17:50.65: [ 9115]: --> [0:]
> Jan 03 13:17:50.65: [ 9115]: MODEM <Empty line>
> Jan 03 13:17:50.65: [ 9115]: MODEM TIMEOUT: waiting for v.21 carrier
> Jan 03 13:17:50.65: [ 9115]: <-- data [1]
> Jan 03 13:17:50.74: [ 9115]: --> [2:OK]

Nope, either the remote has hung up, got disconnected, didn't see RTC 
(end of page), or we're dissynchronous somehow.

> Jan 03 13:17:50.74: [ 9115]: No response to MPS or EOP repeated 3
> tries

Yup, this is what it's called, but it could mean a million different 
problems.

> Jan 03 13:17:50.74: [ 9115]: <-- [9:AT+FTH=3\r]
> Jan 03 13:17:50.80: [ 9115]: --> [7:CONNECT]
> Jan 03 13:17:50.80: [ 9115]: <-- HDLC<3:FF C8 DF>
> Jan 03 13:17:50.80: [ 9115]: <-- data [3]
> Jan 03 13:17:50.80: [ 9115]: <-- data [2]
> Jan 03 13:17:52.11: [ 9115]: --> [2:OK]

We gracefully send DCN (disconnect) even though they may not be 
listening.

> Jan 03 13:17:52.11: [ 9115]: MODEM input buffering enabled
> Jan 03 13:17:52.11: [ 9115]: <-- [5:ATH0\r]
> Jan 03 13:17:52.82: [ 9115]: --> [2:OK]

Hang up.

Anyway, the point here is that we need to know if the remote even got 
the page image data completely (printed the fax page out).  Probably 
not, but it would be nice to know.  If it didn't, then most likely they 
don't understand our 2D-MR (this is a Panasonic, and from 
experience...), so you could use DestControls to send in MH (1D-MR) - 
or simply force MH in your client (sendfax ?).  Maybe send at 9600 bps, 
also.  Probably has to do with one of the session formats I mentioned 
above.

If, when you send in Class 2, you're sending in MH only - then this is 
a clue.  You can look at the session page formatting from your Class 2 
session logs.

If they did get page data, and printed out a page, then you'll need to 
upgrade and then work on post-page message timings which ain't fun, but 
it's not likely the case.

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@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*

Follow-Ups:
- Re: [hylafax-users] Class1 vs. Class2
  - From: John Darrington

References:
- [hylafax-users] Class1 vs. Class2
  - From: John Darrington
- Re: [hylafax-users] Class1 vs. Class2
  - From: Lee Howard
- Re: [hylafax-users] Class1 vs. Class2
  - From: John Darrington
- Re: [hylafax-users] Class1 vs. Class2
  - From: Lee Howard
- Re: [hylafax-users] Class1 vs. Class2
  - From: John Darrington
- Re: [hylafax-users] Class1 vs. Class2
  - From: Lee Howard
- Re: [hylafax-users] Class1 vs. Class2
  - From: John Darrington
- Re: [hylafax-users] Class1 vs. Class2
  - From: John Darrington

Prev by Date: [hylafax-users] Copy of send fax
Next by Date: Re: [hylafax-users] Class1 vs. Class2
Previous by thread: Re: [hylafax-users] Class1 vs. Class2
Next by thread: Re: [hylafax-users] Class1 vs. Class2
Index(es):
- Main
- Thread

Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services