Faxpoll server with USR Courier V34+

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

Hi,

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

I think this was an unique byte loss -- bad serial cable, whatever ;)

> > > 01/17 16:50:56 yS1  fax_get_page_data: wait for EOL, got: [0a]Pâ![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][ff][ff][ff][ff][ff][ff][ff][ff][ff][f
> > 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 
> received facsimiles look good to me. Could it be that the first line always 
> is lost??

Yup. Timing at the start of the page is fairly critical. Some modems do
this very well (Multitech, ZyXEL), some worse (USR).

> > This is the next ugly thing: the standard demands hexadecimal responses,
> > the courier sends decimal numbers. *sigh*.
> Is it not possible to implement decimal responses and select between hex 
> and dec in the policy.h file ?

Mgetty *does* distinguish between dec and hex responses (because in class
2, the responses are decimal), but I do *not* implement workarounds for 
modems firmware flaws, unless it's critical for operation (which this is
not).

> Or doesn't USR want to give you the decimal responses ?

They apparently read the standard differently than I do.

> > > 01/17 16:51:29 ##### failed: polling failed, +FHS:-5, time=60s
> > 
> > -- the USR lowers the DCD line between pages, and this will lead to
> > "strange" errors.
> > 
> > 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. 

poll receiving or poll sending?

> However this option has one big disadvantage. When the connection is 
> broken (lost carrier), MGETTY doesn't detect it. The faxfile which is 
                         ^^^^^ mgetty doesn't do "poll receiving"?!?
> sent, is echoed by the modem and written in the logfile..

FAX_SEND_IGNORE_CARRIER isn't used in mgetty. This is a bug of the USR
modem, it doesn't always give proper error responses upon hangup.

(BTW: in fax mode the connection can never be "broken" in the middle of a
page [unless you're using ECM which mgetty doesn't do] because fax is
half-duplex, the modem won't notice until the end of the page that the
receiver has gone away. And *if* it notices, it *MUST* send a proper
+FHS:xx status code).

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

see above.

gert

-- 
                                                            //www.muc.de/~gert
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-3545980 <---new!!!              gert.doering@physik.tu-muenchen.de