Path: utzoo!attcan!uunet!wuarchive!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!mips!daver!kcdev!gentry
From: gentry@kcdev.UUCP (Art Gentry)
Newsgroups: comp.sys.hp
Subject: Re: Modems
Message-ID: <1131@kcdev.UUCP>
Date: 2 Jul 90 21:35:18 GMT
References: <1990Jun13.153719.17110@groucho> <560012@hpqtdla.HP.COM> <1990Jul02.173100.10477@groucho>
Reply-To: gentry@kcdev. (Art Gentry)
Followup-To: comp.sys.hp
Organization: AT&T Kansas City, Mo.
Lines: 29

In article <1990Jul02.173100.10477@groucho> edwards@neon.UUCP (Daniel Edwards) writes:
=The problem does not seem to be with the modem, which behaves quite
=normally.  I connect to the modem from the console using 
=cu -s1200 -l tty01 -m dir
=ATDT dials numbers, ATH hangs up the phone line, and
=all internal switches seem normal.  If I exit from cu (tilde period)
=I get the normal disconnected message and the normal ksh prompt.  
=If I then call the modem from a remote terminal, I get connected, 
=and nothing happens; no login prompt, no response.  If I again try 
=cu from the console, I get a normal connection and then a 
=listing of ringings and garbage that I typed from the remote terminal.
=The system stays in this state until I reboot.  Any suggestions will
=be welcomed.  

I missed the original discussion, so this may have already been discussed,
but it sounds suspiciously like you have 'getty' instead of 'uugetty'
spawned on the port.  getty does not know how to handle 2 way traffic
gracefully.

your /etc/inittab entry should look something like this:

01:2:respawn:/usr/lib/uucp/uugetty -r -t 60 tty01 2400


-- 
| R. Arthur Gentry     AT&T Communications     Kansas City, MO     64106 |
| Email: gentry@kcdev.uucp          ATTMail: attmail!kc4rtm!gentry       |
| The UNIX BBS: 816-221-0475        The Bedroom BBS: 816-637-4183        |
| $include {std_disclaimer.h}       "I will make a guess" - Spock - STIV |