[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
|
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
HI!
I have a customer who is using a USRobotics modem with his AlphaStation 250
and
Digital Unix 4.0. Everything appears to be configured properly, but the modem
will only respond to tip and not cu. The customer prefers cu and wants to get
it working. The modem was originally configured as a DecmodemV32 on ttyd0,
but
this wasn't working so we configured it as a hayes-compatible modem on ttyd1,
this is why you see an attempt to dial out through both in the following
output.
I had customer run cu -d to perform a diagnostics trace, but I'm not quite
sure
how to interpret it (I haven't worked with cu much), could anyone help??
Here is the output:
bam3% cu -d 428-3702
altconn called
Device Type ACU wanted
ttylock ttyd0 succeeded
Attempting to open /dev/ttyd0
fixline(4, 9600)
Changing tty c_cflags from 045415
Changing tty c_cflags to 0145415
Attempting to open /dev/ttyd0
gdial(DECmodemV32) called
expect: ("")
got it
sendthem (DELAY
^M)
expect: (Ready)
^Mtimed out
ttylock ttyd1 succeeded
Attempting to open /dev/ttyd1fixline(4, 9600)
Changing tty c_cflags from 045415
Changing tty c_cflags to 0145415
Attempting to open /dev/ttyd1
gdial(hayes) called
expect: ("")
got it
sendthem (DELAY
<NO CR>)
expect: (OK)
timed out
getto ret -1
Connect failed: CALLER SCRIPT FAILED
call cleanup(1)
call _mode(0)
bam3%
Any suggestions would be greatly appreciated, thanks!
Kim
[Posted by WWW Notes gateway]
| T.R | Title | User | Personal
Name | Date | Lines
|
|---|