Xref: utzoo comp.unix.microport:2717 comp.dcom.modems:3283 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!ncar!ames!xanth!nic.MR.NET!shamash!com50!mscunx!hawkmoon!root From: root@hawkmoon.MN.ORG (Admin) Newsgroups: comp.unix.microport,comp.dcom.modems Subject: modem problem Keywords: +++, command mode, USR Direct 2400, uugetty, 3.0e, HDB Message-ID: <787@hawkmoon.MN.ORG> Date: 23 Jan 89 08:02:25 GMT Organization: One of the Eternal Champions - Richfield, MN, 554232523, USA Lines: 84 Ok -- here's the scoop. I'm calling the site "elric" (with Uutry) and i'm doing it over a bidirectional serial port, /dev/cul0, using uugetty: Everything works fine (in a relative fashion) if i gag the modem by turning off verbose mode. But this causes unnecessary delays while i time out waiting for the login: prompt instead of looking for "CONNECT". It *does* work however. But, what i wanted to do is (silly me) speed this process up somewhat. The problem is to have the modem in verbose mode whilst calling OUT, but in "gag" mode while otherwise idle. So, i concieved of the somewhat-short-of- brilliant idea of initializing the modem to be in verbose mode; then waiting until i get CONNECT and going temporarily into the modem's command mode with "+++", issuing the gag order and finally returning on-line with ATO and preceding apace from there on as if nothing had happened. At most, just a few seconds delay would have occurred between the CONNECT and my initial CR to the called site's getty. Certainly no worse than the current situation. But nooo.. As soon as i issue the +++, the carrier drops the carrier like a hot potato. What the heck am i doing wrong here? The USR manual mentions nothing like: "As soon as the +++ is entered the modem not only enters the command state, but also immediatly drops the carrier like a hot potato" (my severe embellishment, a hacker's inalieanable rite (sic)) Has anyone else run into this or is this just yet another fundamental mis- understanding of the way the modem/uugetty is supposed to work (not a terribly unusual situation, i might add (:-)) The hopefully relevant data follows, in my quite imitable, verbose fashion: $ grep cul0 /etc/inittab ug:23:respawn:/usr/lib/uucp/uugetty -r -t 30 cul0 2400 # connect bidirectional $ ls -li /dev/tty*1 /dev/cu* 38 crw--w--w- 2 uucp uucp 3, 1 Jan 23 01:40 /dev/cul0 40 crw-rw-rw- 1 root sys 16, 0 Dec 30 22:49 /dev/tty 38 crw--w--w- 2 uucp uucp 3, 1 Jan 23 01:40 /dev/tty01 279 crw-rw-rw- 1 root sys 3,193 Jul 18 1988 /dev/ttyM01 281 crw-rw-rw- 1 root sys 3,129 Jul 18 1988 /dev/ttym01 $ grep usrpwc24 ~uucp/Dialers.cico # s inserted for the easing of # tired eyes usrpwc24 =W-, "" \r\r\r\r\dATZ "" ATV1Q0E1 "" AT OK-\d\d+++\d\dATH\r\dATV1Q0E1-OK ATX6M0DTW6816634 CONNECT\s2400 \r "" \d\d+++\d\d OK ATQ1V0E0 "" ATO "" \r tion:--tion: \D\r\c Connected-\r\d\D\r\c-Connected--in:--in: $ cat /tmp/elric conn(elric) Device Type PWC wanted expect: ("") got it sendthem (^M^M^M^MDELAY ATZ^M) expect: ("") got it sendthem (ATV1Q0E1^M) expect: ("") got it sendthem (AT^M) expect: (OK) ^M^M^MATZ^M^M^JOKgot it sendthem (ATX6M0DTW6816634^M) expect: (CONNECT 2400) ^M^JATV1Q0E1^M^M^JOK^M^JAT^M^M^JOK^M^JATX6M0DTW6816634^M^M^JRINGING^M^J^M^JCONNECT 2400got it sendthem (^M^M) expect: ("") got it sendthem (DELAY DELAY +++DELAY DELAY ^M) expect: (OK) ^M^J^M^JDSS::12T-37^M^JWELCOME TO THE CORP. SQ. PWC NETWORK^M^J^M^JSelect Destination: +++^M^JNO CARRIER^M^J^MConversation Complete: Status FAILED derek -- Derek Terveer root@hawkmoon.MN.ORG || ..!uunet!rosevax!elric!hawkmoon!root w(612)681-6986 h(612)688-0667 "A proper king is crowned" -- Thomas B. Costain