Faxpoll server with USR Courier V34+

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

Hi,

Gerhard Ahuis wrote:
> > > When I serve a faxpoll from my Linux box running MGETTY, the first page is 
> > > going fine, but the second one not. The page is completely sent into my 
> > > logfile and the connection is broken. I know USR's fax implemation is not 
> > > fine, but this looks to me like a little problem.
> > > Is there a solution (patch) to this ?
> > 
> > Logfile? 
> > 
> 
> All right here it is:

I'm sorry, it was not necessary in this case (I didn't look closely, just
saw "no log file there").

The USR faxmodems can't do fax poll serving in class 2.0 mode. USR tech
support says "it's optional" (I have the mail somewhere!!!), and they don't
think it's a bug. After all, it's optional.

> Doing a faxpoll is also going wrong. The pages are sent correctly by the 
> remote fax machine and also received correctly except the last part.

Last time I tried, fax polling as a client didn't work either, but let's
look at your log file...

[..]
> 01/17 16:50:46 yS1  fax_wait_for: string '+FCI:"      +XX XXX XXXXXX"'
> 01/17 16:50:46 yS1  fax_id: '+FCI:"      +XX XXX XXXXXX"'

Good so far.

> 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.

> 01/17 16:50:46 yS1  fax_wait_for: string '+FPO'
> 01/17 16:50:46 yS1  got +FPO -> will do polling
> 01/17 16:50:46 yS1  fax_wait_for: string 'OK'** found **
> 01/17 16:50:46 yS1  fax_send: 'AT+FBO=1'
> 01/17 16:50:46 yS1  mdm_command: string 'AT+FBO=1'
> 01/17 16:50:46 yS1  mdm_command: string 'OK' -> OK
> 01/17 16:50:46 yS1  tio_set_flow_control( XON_IN )
> 01/17 16:50:46 yS1  fax_send: 'AT+FDR'
> 01/17 16:50:46 yS1  fax_wait_for(CONNECT)

OK so far.

> 01/17 16:50:51 yS1  fax_id: '+FTI:"      +XX XXX XXXXXX"'
> 01/17 16:50:52 yS1  fax_wait_for: string '+FCS:1,3,0,2,0,0,0,3'
> 01/17 16:50:52 yS1  transmission par.: '+FCS:1,3,0,2,0,0,0,3'
> 01/17 16:50:56 yS1  fax_wait_for: string 'CONNECT'** found **
> 01/17 16:50:56 yS1  sending DC2
> 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?

> 01/17 16:50:56 yS1  fax_get_page_data: receiving ./ff0fd1ac5S1-+XX-XXX-XXXXXX.01...
> 01/17 16:51:25 yS1  fax_get_page_data: page end, bytes received: 34290

How does the page look? When I tried, it was *always* completely corrupt.

> 01/17 16:51:25 yS1  fax_wait_for(OK)
> 01/17 16:51:25 yS1  fax_wait_for: string '+FPS:1,2288,0,0,0'
> 01/17 16:51:25 yS1  page status: +FPS:1,2288,0,0,0
> 01/17 16:51:25 yS1  8840 lines received, 0 lines bad, 0 bytes lost

This is the next ugly thing: the standard demands hexadecimal responses,
the courier sends decimal numbers. *sigh*.

> 01/17 16:51:26 yS1  fax_wait_for: string '+FET:2'
> 01/17 16:51:26 yS1  fax_wait_for: string 'OK'** found **
> 01/17 16:51:26 yS1  fax_send: 'AT+FDR'
> 01/17 16:51:26 yS1  fax_wait_for(CONNECT)
> 01/17 16:51:26 yS1  fax_wait_for: string 'AT+FDR'
> 01/17 16:51:29 yS1  fax_read_byte: read returned 0: Unknown error
> 01/17 16:51:29 yS1  fax_get_line: cannot read byte, return: Unknown error
> 01/17 16:51:29 ##### failed: polling failed, +FHS:-5, time=60s

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.

I'm not sure, though, whether this will be sufficient to get poll
receiving to work.

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