PCMCIA, ECO II 56K Fax/Modem: Fax/Data distinguishing does not work
Gert Doering (gert@greenie.muc.de)
Wed, 11 Aug 1999 22:36:21 +0200
Hi,
On Wed, Aug 11, 1999 at 12:32:14AM +0200, Thomas Ziegler wrote:
> Error: Dialin with fax does not work (see log-faxin-error)
> But: Dialin with /etc/answer set to 'fax' works (see log-faxin-faxonly)
Hmmm, what is /etc/answer? Mgetty doesn't use this (vgetty might, but
you're not using that). So I'd consider this "random failure, random
luck".
> Error: Fax-Polling works neither as a server (see log-poll-server)
> nor as a client (see log-poll-client)
> But: The german dealer says he's sure, that polling is supported
The dealer has no idea what he's talking about. This is very explicit
from the log file:
> 08/10 17:17:11 yS1 got: ATA[0d]
> 08/10 17:17:11 yS1 CND: OKATA[0d][0a]CONNECT ** found **
> 08/10 17:17:30 yS1 send:
> 08/10 17:17:30 yS1 waiting for ``_''
> 08/10 17:17:30 yS1 got: 19200 NoEC[0d]
> 08/10 17:17:30 yS1 CND: CONNECT 19200 NoEC
... the modem has "identified" the call as 19200 bps (?? must be the
serial port speed) and No Error Control - most likely, the 300bps fax
negotiation carrier, or something like this. Stoopid thing.
Second try:
> 08/10 15:53:00 yS1 got:[0d][0a]OK[0d]
> 08/10 15:53:00 yS1 mdm_command: string 'OK' -> OK
> 08/10 15:53:00 yS1 mdm_send: 'AT+FAA=1;+FCR=1'
> 08/10 15:53:00 yS1 got:[0a]AT+FAA=1;+FCR=1[0d]
> 08/10 15:53:00 yS1 mdm_command: string 'AT+FAA=1;+FCR=1'
the modem is initialized as before - adaptive answer (fax and data) = on.
> 08/10 15:54:35 yS1 connection hangup: '+FHNG:0'
> 08/10 15:54:35 yS1 (Normal and proper end of connection)** found **
... and this time it works. Stoopid indeed.
[..]
> --- log-poll-server ---
[..]
> 08/10 19:19:03 yS1 mdm_command: string 'OK' -> OK
> 08/10 19:19:04 yS1 mdm_send: 'AT+FLPL=1'
> 08/10 19:19:04 yS1 got:[0a][0d][0a]ERROR[0d]
> 08/10 19:19:04 yS1 mdm_command: string 'ERROR' -> ERROR
> 08/10 19:19:04 yS1 faxpoll_server_init: no polling available
If the modem doesn't understand this command, it can't do polling
(server-side), at least not in class 2 mode. Period, no discussion.
> --- log-poll-client ---
[..]
> 08/10 19:24:16 yS1 mdm_send: 'AT+FCIG="987654321"'
> 08/10 19:24:16 yS1 got:[0a][0d][0a]ERROR[0d]
> 08/10 19:24:16 yS1 mdm_command: string 'ERROR' -> ERROR
> 08/10 19:24:16 yS1 cannot enable polling
... same for this: AT+FCIG is a prerequisite for polling (client) in class
2 mode, if that doesn't work, polling won't work.
As for a good recommendation: hard to say, I haven't any yet.
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