failure notice (fwd)

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

On Thu, Feb 11, 1999 at 07:25:51AM -0800, Clayton Valley wrote:
>    I'm forwarding this message which bounced.  I'm not at all sure that
> the message got through to you.  

Got through to me, but maybe it didn't reach the remainder of the list.
I'm not really sure what's going on - Russell is already looking after
it (I hope).

As to your original question:

> > 	Linux 2.0.34
> > 	Modem: Compaq/Microcom 4000 modem bank (23 modems connected to
> > 		a pri circuit. The "server" end of 56k v.90)
> > 	Serial Ports: Cyclades, Cyclom Y
> > 
> > Mgetty does receive a file of approximately the correct size but I can't 
> > tell what it looks like.  Any attempt to convert it to pbm reports an error.
> > 
> > 02/10 06:16:57 yC8   checking lockfiles, locking the line
[..]
> > 02/10 06:17:15 yC8   fax_wait_for: string 'CONNECT'** found **
> > 02/10 06:17:15 yC8   sending DC2
> > 02/10 06:17:15 yC8   fax_get_page_data: wait for EOL, got: [0a][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][c0][05]6j[00]
> > 02/10 06:17:15 yC8  fax_get_page_data: receiving /var/spool/fax/incoming/ff6c194d9C8-805-984-1241.01...
> > 02/10 06:17:55 yC8  fax_get_page_data: page end, bytes received: 71055
> > 02/10 06:17:55 yC8  fax_wait_for(OK)

Up to this point, everything looks pretty reasonable.

> > 02/10 06:17:56 yC8   fax_wait_for: string '+FPS:1,0,0,0,0'
> > 02/10 06:17:56 yC8  page status: +FPS:1,0,0,0,0
> > 02/10 06:17:56 yC8   0 lines received, 0 lines bad, 0 bytes lost

This is certainly fishy.  The modem reports in the +FPS: line that the
page was OK, but did contain 0 lines of data - and 0 lines of errors.  
How to make out 71 Kbytes out of 0+0 lines of data, I don't know.

> > 02/10 06:17:56 yC8   fax_wait_for: string '+FET:2'
> > 02/10 06:17:56 yC8   fax_wait_for: string 'OK'** found **
> > 02/10 06:17:56 yC8  Page doesn't look good, request retrain (MPS)

... mgetty doesn't like the smell of it, so it tries to get the sender to
re-send the page.

> > 02/10 06:17:56 yC8  fax_send: 'AT+FPS=2'
> > 02/10 06:17:56 yC8  fax_wait_for(OK)
> > 02/10 06:17:56 yC8   fax_wait_for: string 'ERROR'
> > 02/10 06:17:56 yC8  ABORTING: line='ERROR'

... which the modem doesn't handle.  Now this problem is a fairly
well-known misfeature of some USR Sportster and Rockwell modems, the
failure to implement AT+FPS=2 (part of the standard, btw!).

As a workaround for this, you can set "modem-quirks 0x04" in
mgetty.config, which will make mgetty ignore bad +FPS:... lines, and not
send +FPS=2.

Unfortunately, this problem is not related to the kaput G3 file - it 
won't change the contents of what was received.  You might want to try 
"viewfax -r ff...", maybe the modem reversed the bits inside each byte
(common problem), but I really doubt that's the problem.

I'm afraid that you won't have much choice besides going to the modem
vendor, showing them the log file (especially the +FPS:1,0,0,0 line and
the broken G3 file) and ask them for a firmware update to repair class 2.0
faxing.

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de