SuSE Support Database

Title: PPP: Modem does not dial

Mainpage Searchform History Versions Categories Contents
Deutsch

PPP: Modem does not dial

Symptom:

ppp does not work, because the chat script does not dial.

Cause:

After a reset the modem needs a small delay before it reacts again on commands.

In Syslog (/var/log/messages) some messages like the following can be found (these are just examples) :

Dec 14 11:40:00 RMR kernel: PPP line discipline registered.
Dec 14 11:40:00 RMR kernel: registered device ppp0
Dec 14 11:40:00 RMR pppd[617]: pppd 2.2.0 started by root, uid 0
Dec 14 11:40:01 RMR chat[620]: timeout set to 45 seconds
Dec 14 11:40:01 RMR chat[620]: abort on (NO CARRIER)
Dec 14 11:40:01 RMR chat[620]: abort on (BUSY)
Dec 14 11:40:01 RMR chat[620]: abort on (NO DIALTONE)
Dec 14 11:40:01 RMR chat[620]: abort on (ERROR)
Dec 14 11:40:01 RMR chat[620]: send (+++ATZ^M)
Dec 14 11:40:01 RMR chat[620]: expect (OK)
Dec 14 11:40:02 RMR chat[620]: +++ATZ^M^M
Dec 14 11:40:02 RMR chat[620]: OK -- got it
Dec 14 11:40:02 RMR chat[620]: send (ATDT123456^M)
Dec 14 11:40:02 RMR chat[620]: expect (CONNECT)
Dec 14 11:40:02 RMR chat[620]: ^M
Dec 14 11:40:47 RMR chat[620]: ^M
Dec 14 11:40:47 RMR pppd[617]: Connect script failed
Dec 14 11:40:47 RMR pppd[617]: Exit.
Dec 14 11:40:47 RMR chat[620]: alarm
Dec 14 11:40:47 RMR chat[620]: Failed

Everything works fine until +++ATZ is reached. Then a message send (AT.... ) and expect (CO..) appears. Instead of this only ^M (carriage-return) is sent twice. No "beeping" of the modem can be heart even though normally it should dial in that moment.

Solution:

It will work if you insert a \d in front of the second AT.

...
ABORT "NO CARRIER"
ABORT BUSY
ABORT "NO DIALTONE"
ABORT ERROR
"" +++ATZ
OK \dATDT....

Sometimes even the initialization command ATZ is sent too early. This can be cured by a \d right after +++. Dialing is then possible without additional delay, e.g.

"" +++\dATZ
OK ATDT0191011

Credits: Detlef Postler (Detlef.Postler@t-online.de)

Similar error but completeley different cause

(Applies to S.u.S.E. Linux: Version 11/95)

Symptom:

ppp via CIS does not work because the chat-script doesn't dial.

Cause:

In the chat-script ppp-up delivered with the november 95 CD comments with a # are included by mistake.

This is not accepted by the chat-program or it waits until a #-sign is sent by the modem which doen't happen very often.

You will see something like this in /var/adm/sylog:

Feb 13 22:25:07 paddys pppd[1967]: pppd 2.1.2 started by root, uid 0
Feb 13 22:25:07 paddys pppd[1968]: Connecting with </usr/sbin/chat -v -f /etc/ppp/ppp.chat>
Feb 13 22:25:09 paddys chat[1969]: expect (#) 
Feb 13 22:26:54 paddys chat[1969]: alarm
Feb 13 22:26:54 paddys chat[1969]: Failed
Feb 13 22:26:54 paddys pppd[1968]: Exit.

Solution:

The correct script:

TIMEOUT 5
ABORT "NO CARRIER"
ABORT BUSY
ABORT "NO DIALTONE"
ABORT ERROR
"" +++ATZ
OK ATDTcistelefon
CONNECT \r\n
ame:--ame: CIS
"" cislogin/GO:PPPCONNECT
word: cispassword

See also:

Compuserve : Collection of dial-in scripts

Keywords: PPP, COMPUSERVE, CHAT, MODEM, CIS

Categories: PPP

Feedback welcome: Send Mail to kfr@suse.de (Please give the following subject: SDB-kfr_10)

Mainpage Searchform History Versions Categories Contents
Deutsch

SDB-kfr_10, Copyright SuSE GmbH, Nuremberg, Germany - Version: 18. Feb 1997
Impressum - Last generated: 24. Feb 1999 14:54:06 by maddin with sdb_gen 1.00.0