Re: New Modem frustration

["AfterBurn" <afterburn crashdot com>]

Actually, it does look familiar, adn im not pointing to the script, but to
the error messages. I had the same for an external isdn modem and a 56k
analog modem. Bear with me, ill have to dig for something for you to maybe
give you a solution.

-AB-

>Hi all;
> I'm in the process of pulling out my old internal modem, and replacing
>it with a new - faster external model. (The new one is a 3com/USR 56k
External
>FAX Modem). I've been using the 33.6 internal version of this for years
with no
>trouble. No such luck with the 56k model... (oh.. setting it up on a
>AlphaStation 200/233, running RedHat 5.1).
>
> Here's what's up:
> If I open minicom, I can dial, and establish a connection. Then with a
>flip of alt-q it's out of there, and a quick pppd command, and the ppp link
is
>up and running. Fair enough. The modem works.
> Now I'm trying to get the scripts to work, and there's no joy at all.
>(I also tried netcfg, and kppp with similar results as the following).
> Using a script to call chat, nothing happens! It doesn't dial. Looking
>at the /var/log/messages, I get the following:
>
> ...send (rAT^M)
> ...expect (OK)
> ...alarm
> ...send (+++)
> ...expect (OK)
> ...alarm
> ...connect script failed
>
> The chat script looks like:
>
>/usr/sbin/chat -v
> TIMEOUT 3 \
> ABORT '\nBUSY\r' \
> ABORT '\nNO ANSWER\r' \
> ABORT '\rRINGING\r\n\rRINGING\r' \
> '' \rAT \
> 'OK-+++\c-OK' ATH0 \
> TIMEOUT 30 \
> OK ATDT$TELEPHONE \
> CONNECT '' \
> ogin:--ogin: $ACCOUNT \
> assword: $PASSWORD
>
>(Look familiar?)
>
> Obviously, it's not getting the "expects" it should. But all looks
>normal in minicom...
>
> Any light will be greatly appreciated!
>
> Thanks!
>
> Ric
>
>--
>To unsubscribe: send e-mail to axp-list-request@redhat.com with
>'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com
>