Hi G-H:
Many thanks for the message - I think I understand your
explanation. I've had another try - but with no luck at all.... Either the
modem is strange - or perhaps there is some small point that I am stupidly
missing!
I can get no response whatever from the modem using chat. If I do cat
somefile > /dev/modem I at least see the lights on the modem flash, but
when I use chat, no light flashes, and nothing happens until chat times-out.
I've seen and tried several chat scripts - all different - some use ""
others `` - some also add \n\r - and I've seen the item in the SDB
about putting in a delay \d
Here's the script I started with - and the result in /var/log/messages.....
(incidentally - I was logged-in as root)
#!/bin/sh
#
TELEPHONE=4011000
###################################################
exec chat -v \
TIMEOUT 3 \
ABORT "NO CARRIER" \
ABORT BUSY \
ABORT "NO ANSWER" \
"" +++ATZ OK \
TIMEOUT 30 \
ATDT"$TELEPHONE" \
CONNECT ""
Jan 4 22:42:39 kingr chat[459]: timeout set to 3 seconds
Jan 4 22:42:39 kingr chat[459]: abort on (NO CARRIER)
Jan 4 22:42:39 kingr chat[459]: abort on (BUSY)
Jan 4 22:42:39 kingr chat[459]: abort on (NO ANSWER)
Jan 4 22:42:39 kingr chat[459]: send (+++ATZ^M)
Jan 4 22:42:39 kingr chat[459]: expect (OK)
Jan 4 22:42:42 kingr chat[459]: alarm
Jan 4 22:42:42 kingr chat[459]: Failed
-----Original Message-----
From: Georges-Henry Portefait <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: 04 January 1999 12:26
Subject: Re: [SuSE Linux] Chat + USR Modem reaaaaally bugging me!
>Hi Rich,
>
>
>Ok, this has nothing to do with the modem, it is the chat script
>
>I ran accross similar problems , It was just hanging there !! and I had
>the same idea how does it know what device it will connect to.
>
>The thing is as minicom works the modem works. So now the chat script !!
>the problem is around the CR and the script, I solve this by :
>
>- Open an xterm and do tail -f /var/log /messages so I can see what
>diald says.
>- Then I trieed to write a script until I get an answer from the modem
>and good feedback in the /var/log/messages basically I did this by
>incrementally building the script
>start with
>ABORT BUSY
>"" +++ATZ OK
>
>Look at the messages you should get something like
>ABORT (BUSY)
>....expect (OK) --got it
>
>If you don't, play with the end of your lines in the shell
>
>like
>"" +++ATZ OK \
>ATDT 002211
>
>Ok the explantion are not very clear, but I hope you see the point.
>
>The script I have working now seems no diferent from the one which was
>NOT working, just because the CR character has moved to the right place
>( I don't know how to visualize it)
>
>So I had to play till it works, then I backed up the file just in case.
>
>I hope this will help you
>
-
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archiv at http://www.suse.com/Mailinglists/suse-linux-e/index.html
