force-init-chat for ELSA 56 K

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

I'm running "mgetty: experimental test release 1.1.19-Nov24" on a FreeBSD 3.1
machine (modem is a ELSA Microlink 56 K). When building and configuring the
package from the FreeBSD-Port, the installation script didn't give me any
hints how to define the "force-init-chat"-String, so I assume it is left
empty in the current configuration. The complete chat-Lines in mgetty.config
are

init-chat "" ATS0=0Q0&D3&C1 OK
answer-chat "" ATA CONNECT \c \r
answer-chat-timeout 80

Now to my problem: Due to security considerations I switch off the modem 
twice a day (via a time-switch) for one minute some time after the dialout
connection to my UUCP-provider.
Problems occur when mgetty tries to talk to the modem during this period
(e.g. to find out if it's still alive). From mgetty's log

*----------------------------------------------------------------------------
04/07 04:30:10 aa1  WARNING: DSR is off - modem turned off or bad cable?
04/07 04:30:10 aa1  lowering DTR to reset Modem
04/07 04:30:10 aa1   tss: set speed to 115200 (341000)
04/07 04:30:10 aa1   tio_set_flow_control( HARD )
04/07 04:30:10 aa1   waiting for line to clear (VTIME), read: [ff]
04/07 04:30:10 aa1  send: ATS0=0Q0&D3&C1[0d]
04/07 04:30:10 aa1  waiting for ``OK''
04/07 04:30:10 aa1   got:
04/07 04:30:30 aa1  timeout in chat script, waiting for `OK'
04/07 04:30:30 aa1  init chat timed out, trying force-init-chat
04/07 04:30:30 aa1  send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
04/07 04:30:34 aa1  waiting for ``OK''
04/07 04:30:34 aa1   got:
04/07 04:30:54 aa1  timeout in chat script, waiting for `OK'
04/07 04:30:54 aa1  init chat failed, exiting...: Interrupted system call
04/07 04:30:54 ##### failed in mg_init_data, dev=cuaa1, pid=40745
04/07 04:30:54 aa1   removing lock file
*--
04/07 04:30:55 aa1  mgetty: experimental test release 1.1.19-Nov24
04/07 04:30:55 aa1   mgetty.c compiled at Mar  3 1999, 22:59:29
*----------------------------------------------------------------------------


The consequences of this "one minute switch off" are severe: No dialins
are successful afterwards (e.g. the two modems achieve no CONNECT) and even 
the following dialout call (from uucico) leads to a "timed out in chat script"
error (which is 
  chat    "" ATZ OK \dATV1E0Q0L0 OK \dATDT\D CONNECT
for the uucico-command).

The situation repairs itself after the following manual switch-off which is
made by the time switch. But this means that the modem has not been available
for dial-ins and dial-outs for more than half of a day!

Any suggestions for an appropriate "force-init-chat"-String for my ELSA
56 K? And what are the best AT-Commands for the other initialization 
strings (init-chat and post-init chat)?

Ciao, Peter