Faxpoll server with USR Courier V34+

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

On Thu, 18 Jan 1996, Gert Doering wrote:

>=20
> > 01/17 16:50:46 yS1  fax_wait_for: string '+IS:1,3,0,2,0,0,0,4'
>=20
> This seems as if your host has lost an "F" somewhere.
After I recompiled mgetty the 'F' was not lost anymore. (Can you explain?,=
=20
I can't)

> > 01/17 16:50:56 yS1  fax_get_page_data: wait for EOL, got: [0a]P=E2![ff]=
[ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff=
][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][ff][f=
f][ff][ff][ff][ff][ff][ff][ff][ff][f
>=20
> Seems the leading EOL required on each page is missing -- bad timing in
> the USR?
This is also happening when normal receiving a fax (no poll). The=20
received facsimiles look good to me. Could it be that the first line always=
=20
is lost??
=20
> This is the next ugly thing: the standard demands hexadecimal responses,
> the courier sends decimal numbers. *sigh*.
>=20
Is it not possible to implement decimal responses and select between hex=20
and dec in the policy.h file ?
Or doesn't USR want to give you the decimal responses ?

> > 01/17 16:51:29 ##### failed: polling failed, +FHS:-5, time=3D60s
>=20
> This might be related to #define FAX_SEND_IGNORE_CARRIER. Please try this
> -- the USR lowers the DCD line between pages, and this will lead to
> "strange" errors.
>=20
> I'm not sure, though, whether this will be sufficient to get poll
> receiving to work.

When using #define FAX_SEND_IGNORE_CARRIER poll receiving is going fine.=20
However this option has one big disadvantage. When the connection is=20
broken (lost carrier), MGETTY doesn't detect it. The faxfile which is=20
sent, is echoed by the modem and written in the logfile..

Is it not possible to discard the carrier only when a page is completely=20
sent ??

Gerhard.