mgetty works fine , vgetty doesn't receive fax.

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

Hi,

Marc Eberhard wrote:
> > Here is the vgetty.ttyS1 log-file.
> Looks like it is Gerts problem:

Let's see...

> > 06/03 18:10:30 yS1  vgetty: experimental test release 0.7.4 / 21Jan98
> > 06/03 18:10:30 yS1  mgetty: experimental test release 1.1.12-Jan27
> [...]
> > 06/03 18:12:38 yS1  send: ATA[0d]
> > 06/03 18:12:38 yS1  waiting for ``CONNECT''
> > 06/03 18:12:38 yS1   got: ATA[0d]
> > 06/03 18:12:38 yS1    CND: RING3ATA[0d][0a]+FCON
> 
> Looks a bit strange...

This is just the logging stuff, I think (CND: logging messes up the
character-by-character logging of do_chat).

> > 06/03 18:12:47 yS1  found action string: ``+FCON''
> > 06/03 18:12:47 yS1  start fax receiver...
> > 06/03 18:12:47 yS1   fax receiver: entry
> > 06/03 18:12:47 yS1   tss: set speed to 19200 (016)
> > 06/03 18:12:47 yS1  fax_wait_for(OK)
> > 06/03 18:12:47 yS1    got:[0a][0d][0a][0d][0a]+FHNG: 0[0d]
> > 06/03 18:12:48 yS1   fax_wait_for: string '+FHNG: 0'
> > 06/03 18:12:48 yS1  connection hangup: '+FHNG: 0'
> > 06/03 18:12:48 yS1   (Normal and proper end of connection)

Well, this is what I wrote before.  The modem says "everything done, no
problem here, goodbye".

This *is* possible, if the calling side requested to *poll* a document, 
and you don't have anything - both sides negotiate that nobody wants to
send anything, and thus they both hang up and are happy about it.

*If* the other side wanted to send something, this is a bad firmware bug
in your modem (if it isn't able to start the fax protocol, it MUST NOT
report +FHNG: 0, but some other error code!).  There is nothing you can
do in mgetty/vgetty to work around this.

gert
-- 
Gert Doering
Mobile communications ... right now writing from *AWAY* :-)) 
... mobile phone: +49 177 2160221 ... or mail me:  gert@greenie.muc.de