Peer hangup after <DLE><ETX>

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

Hi,

Joseph Kwok wrote:
> > I'm afraid to say that -- your vendor is right, your modem *CANNOT* do
> > class 2 fax.
[..]
> > > 03/26 15:35:02 yS0   fax_wait_for: string '+FPTS:1'
> > > 03/26 15:35:02 yS0  page status: +FPTS:1
> >
> > Completely unsolicited message!!!  It is supposed to be sent *AFTER* the
> > AT+FET=x command, not before it!!
> >
> > > 03/26 15:35:03 yS0   fax_wait_for: string '+FHNG:0'
> > > 03/26 15:35:03 yS0  connection hangup: '+FHNG:0'
> > > 03/26 15:35:03 yS0   (Normal and proper end of connection)
> >
> > And the modem just hangs up - claiming that the connection is "over".
[..]
> > This modem is completely broken.
> 
> But if I send the same 2 pages to a real FAX machine, it works!  Here is the
> successfully log:

Well, maybe "just" the part for 14.400 fax is broken, or "just" sending
faxes with no delay between successive scan lines, or whatever.  In any
case, the behaviour logged above is very much in violation of the fax
class 2 standard -- this should NEVER happen.

> But this is the real FAX machine that cannot send fax to my mgetty.  
> mgetty can only receive 1504 bytes everytime and then get an error 91.  

I've seen your e-mail regarding this, but I don't have an answer either --
basically, if the modem sends those error codes, there is nothing mgetty
can do about it.  In class 2, all the brains are in the modem firmware,
and if they don't work, that's it :-(

> But I really doubt that whether my modem is really 100% class 2 or not.

Yup.  Since even the vendor denies it...

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