Courier I-Modem, losing data link layer

Courier I-Modem, losing data link layer

Post by AIDAN INTERNET SOLUTION » Sat, 12 Sep 1998 04:00:00



I'm using an Internal USR Courier I-Modem to connect to my ISP.  I'm using Linux 2.0.34 and pppd version 2.2 patch level 0.  I
am using the following configuration of pppd.

ppp-on.sh calls this:

#!/bin/sh
pppd -d +ua /etc/ppp/pap-secrets connect "chat -v -f /etc/ppp/chatscript" /dev/ttyS3 persist &

The chatscript is as follows:

ABORT           BUSY
ABORT           "NO CARRIER"
ABORT           VOICE
ABORT           "NO DIALTONE"
"" ATZ! OK AT&F1*V2=5&K1 OK ATDT4857460 CONNECT

I've found this to be little if any more reliable in preventing this upon a disconnection from the ISP:

Sep 10 20:26:10 server chat[500]: abort on (BUSY)
Sep 10 20:26:10 server chat[500]: abort on (NO CARRIER)
Sep 10 20:26:10 server chat[500]: abort on (VOICE)
Sep 10 20:26:10 server chat[500]: abort on (NO DIALTONE)
Sep 10 20:26:10 server chat[500]: send (ATZ!^M)
Sep 10 20:26:10 server chat[500]: expect (OK)
Sep 10 20:26:10 server chat[500]: ATZ!^M^M
Sep 10 20:26:10 server chat[500]: OK -- got it
Sep 10 20:26:10 server chat[500]: send (AT&F1*V2=5&K1^M)
Sep 10 20:26:10 server chat[500]: expect (OK)
Sep 10 20:26:10 server chat[500]: ^M
Sep 10 20:26:11 server chat[500]: AT&F1*V2=5&K1^M^M
Sep 10 20:26:11 server chat[500]: OK -- got it
Sep 10 20:26:11 server chat[500]: send (ATDT4857460^M)
Sep 10 20:26:11 server chat[500]: expect (CONNECT)
Sep 10 20:26:11 server chat[500]: ^M
Sep 10 20:26:11 server chat[500]: ATDT4857460^M^M
Sep 10 20:26:11 server chat[500]: NO DIAL TONE^M
Sep 10 20:26:56 server chat[500]: alarm
Sep 10 20:26:56 server chat[500]: Failed

And it's more than a nusance once or twice.

Sep 10 13:19:54 server chat[1451]: NO DIAL TONE^M
Sep 10 13:20:51 server chat[1458]: NO DIAL TONE^M
Sep 10 13:21:48 server chat[1459]: NO DIAL TONE^M
Sep 10 20:18:35 server chat[484]: NO DIAL TONE^M
Sep 10 20:19:32 server chat[485]: NO DIAL TONE^M
Sep 10 20:20:29 server chat[492]: NO DIAL TONE^M
Sep 10 20:21:26 server chat[493]: NO DIAL TONE^M
Sep 10 20:22:23 server chat[494]: NO DIAL TONE^M
Sep 10 20:23:20 server chat[495]: NO DIAL TONE^M
Sep 10 20:24:17 server chat[496]: NO DIAL TONE^M
Sep 10 20:25:14 server chat[499]: NO DIAL TONE^M
Sep 10 20:26:11 server chat[500]: NO DIAL TONE^M

It keeps me down for a looong time, for a LAN in use.

I've noticed a typo now, for the ABORT NO DIAL TONE in the chatscript and am changing that as we speak.
However, I need to induce a wait state of about 20 seconds after the ATZ! typically, as it takes at least that long to
re-stablish the data link layer.  When I get the NO DIAL TONE message, I can fire up minicom, and do an ATI12, and notice the
data link layer is inactive.  Once I get it re-active, ie, atz!, it comes back alive, and dials out fine.  Sometimes, it's
required me to shutdown and reboot the machine.  Sad really, this Imodem is not my friend.  Ideas?

Taylor