dgc@CS.UCLA.EDU (12/21/86)
Expires: References: Sender: Followup-To: I have a 2400 baud Bytcom modem. Frequently, when using it to call a vax also using a 2400 Bytcom modem, what appear to be a lengthy random sequence of bytes appears on my terminal screen and sometimes the modem disconnects. After two or three tries a useful connection is usually established. I have very few errors once a good connection is establshed. The telephone line is a Foreign Exchange (FX) line, operated by General Telephone, and is not of the best quality. I would guess that it is about 10 miles long while my local loop is about 3 miles long. The FX line is somewhat noisy and has lower gain than my other lines. I have no modem problems on my other lines (but I don't want to use them because of high charges). Does anyone know anything about this kind of problem? I have been told that this may be due to a bug in a Rockwell chip set. dgc
kaberline@ford-vax.UUCP.UUCP (03/15/87)
I'm sure this is a very simple problem for someone who, unlike me, knows what they are doing when it comes to modems/modular jacks/wiring. I have a HAYES-compatible modem at home, works just fine, I can call out and connect to the rest of the world, and the modem recognizes that the phone is ringing and can answer, also detects busy properly. When I move the same modem and computer to a friends house, I can still dial out anywhere and connect OK, but the modem no longer recognizes ring or busy?? I suspect that maybe a pair of wires in my modular jack are reversed, but which ones? HELP!? Suggestions?? ------
jerry@starfish.Convergent.COM (Gerald Hawkins) (10/25/88)
My company just provided me with a nice shiny new 2400 baud modem to use at home with my pcat clone. This is a Convergent DC-2400 model, which is an oem version of an expensive Japanese brand (which mfg I do not know). It is supposed to be 100% Hayes compatible. That is the good news. The bad news is that so far I've only been able to access bulletin boards and our computers at work at 1200 baud. That is rather frustrating. The machines I'm accessing are absolutely definitely 2400 baud. What happens when I access at 2400 is: Ringing, answer, carrier tones, squack, and silence. My (trial) procomm software reports CONNECT 2400/ARQ but no further communication takes place. My estimates of the possible causes of the problem are: 1. My telephone lines in my house are 30 years old and have many owner modifications, certainly not up to phone co. specs. The line is used for voice and data and has 1 old dial phone (wd50?) and a newer pushbutton model on it. 2. I could possibly be not initializing the modem correctly with the procomm package. Could someone who is using procomm and a hayes compatible modem please fill me in on what the command strings are best set to in the modem setup screen; and also the line setup screen? 3. Or lastly, the phone lines in my neighborhood may not be up to 2400 baud usage; or the modem isn't as good as specified--in either of these cases I have to surrender and accept 1200. Can anyone help? These opinions are mine. Jerry. (jerry@Starfish.Convergent.COM) -----
root@hawkmoon.MN.ORG (Admin) (01/23/89)
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 # <cr>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. Costainskrenta@eecs.nwu.edu (Richard Skrenta) (01/28/89)
I don't have a U.S. Robotics, but it's been my experience that sending data to a Hayes-type modem while it's waiting for a carrier causes it to quit and say NO CARRIER. I had a modem where the only character which would do with was "a". My new 2400 baud modem does this if it gets just about anything. My guess is that your modem sees the "+" and thinks you're cancelling the call... Rich Skrenta
news@brian386.UUCP (Wm. Brian McCane) (01/30/89)
In article <787@hawkmoon.MN.ORG> root@hawkmoon.MN.ORG (Admin) writes: >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: > > [ deleted ] > > 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" > >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 (:-)) > >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: I cut out most of the boring stuff. Anyway, your problems are many fold I believe. First, the modem at the other end, is most likely using your same ESCAPE code "+++". So it also enters command mode when it gets this message. So even if you do get most of the other rather involved instructions to work, he is now ignoring you. Second, I have had to put a \d between my escape characters for the necessary time out. My version of your dialup script would be: usrpwc24 =W-, "" \r\rATZ "" ATV1Q0E1S2=27 OK\r AT OK\r ATX6M0DTW6816634 CONNECT\s2400 \r "" \d\d\033\d\033\d\033 OK\r ATQ1V0E0S2=43O "" \010\010\010\r tion:--tion: \D\r\c Connected-\r\d\D\r\c-Connected--in:--in: Okay, so I cut out some of the embellishments, but you get the picture. I first set my escape code to something else, and then I dial the name and use my new escape code to get back to command mode. Then I reset it to the original. I hope this helps. (By the way, this is how I do it too. If my modem is not gagged, it picks up then phone and immediately hangs up again.) brian
leonard@bucket.UUCP (Leonard Erickson) (01/31/89)
Check the manual for the modem *carefully*. Many older Hayes clones use +++ as a hang-up sequence. My USR Password 1200 does this. My USR Courier 2400 has this as an option. I *think* it is switch selectable, but it may be an S register. -- Leonard Erickson ...!tektronix!reed!percival!bucket!leonard CIS: [70465,203] "I'm all in favor of keeping dangerous weapons out of the hands of fools. Let's start with typewriters." -- Solomon Short
pete@octopus.UUCP (Pete Holzmann) (02/01/89)
In article <787@hawkmoon.MN.ORG> root@hawkmoon.MN.ORG (Admin) writes: >..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" This is one of the USR 'features' :-( that made me give up early on the HST modems. It seems that for some of the modes of some of their modems (including high speed on the HST, and I guess on the Direct 2400 you are using), they can't both support AT commands and a data link simultaneously. So, if you go into command mode (+++ and all that), they just drop carrier. This was confirmed by USR tech support. If you never need to do this, you don't care. But let the buyer beware. Pete -- OOO __| ___ Peter Holzmann, Octopus Enterprises OOOOOOO___/ _______ USPS: 19611 La Mar Court, Cupertino, CA 95014 OOOOO \___/ UUCP: {hpda,pyramid}!octopus!pete ___| \_____ Phone: 408/996-7746
gpwrdcs@gp.govt.nz (Don Stokes, Govt Print, Wellington) (02/03/89)
In article <787@hawkmoon.MN.ORG>, root@hawkmoon.MN.ORG (Admin) writes: > > 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: Well, that certainly isn't normal behaviour for a Hayes compatoble modem... > ^M^J^M^JDSS::12T-37^M^J > WELCOME TO THE CORP. SQ. PWC NETWORK^M^J > ^M^JSelect Destination: +++^M^J > NO CARRIER^M^J^M > Conversation Complete: Status FAILED [newlines inserted for clarity] Ah ... all is revealed. When you send "+++", the modem forwards the +++ to the remote site. It does not interpret the +++ until it has completed. So (I can't be sure, as I never dialled into the site in question, but it could be that it is the remote site is dropping carrier on you after receiving "+++". Also, you should see "OK" when the +++ is acknowleged. Don Stokes Systems Programmer Government Printing Office, Wellington
patrick@chinet.chi.il.us (Patrick A. Townson) (02/05/89)
In article <277@gp.govt.nz> gpwrdcs@gp.govt.nz (Don Stokes, Govt Print, Wellington) writes: >In article <787@hawkmoon.MN.ORG>, root@hawkmoon.MN.ORG (Admin) writes: >> >> 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: > >Well, that certainly isn't normal behaviour for a Hayes compatoble modem... Some modems, such as my US Robotics Courier 2400 have a dip switch setting which allows +++ to be treated in one of two ways. With the dip switch set one way, the three plusses will retain the phone connection and return to command state. Set the other way, this causes the modem to hang up and send a NO CARRIER result code. In the US Robotics Courier 2400 instruction manual see page C-4, and refer to Switch 9. I don't personally know why anyone would want to use it in the mode where it immediatly disconnects the phone, but I guess some people must use it that way. -- Patrick Townson patrick@chinet.chi.il.us / US Mail: 60690-1570 (personal zip code) FIDO: 115/743 / AT&T Mail: 529-6378 (!ptownson) / MCI Mail: 222-4956
john@stiatl.UUCP (John DeArmond) (02/06/89)
>In article <787@hawkmoon.MN.ORG>, root@hawkmoon.MN.ORG (Admin) writes: > > 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 I did not see your original posting but if you are refering to the US Robotics original 1200 baud modem, this is a known bug. "+++" takes the modem offline instead of back to command mode like it should. I have no experience with their 2400 baud products but suspect this may be a similiar problem. john . -- John De Armond, WD4OQC | Manual? ... What manual ?!? Sales Technologies, Inc. Atlanta, GA | This is Unix, My son, You ...!gatech!stiatl!john | just GOTTA Know!!!
johnl@n3dmc.UU.NET (John Limpert) (02/06/89)
In article <7642@chinet.chi.il.us> patrick@chinet.chi.il.us (Patrick A. Townson) writes: >In the US Robotics Courier 2400 instruction manual see page C-4, and refer >to Switch 9. I don't personally know why anyone would want to use it in >the mode where it immediatly disconnects the phone, but I guess some people >must use it that way. It's a security feature. Many BBS systems used to have problems with people misconfiguring the system's modem. -- John A. Limpert UUCP: johnl@n3dmc.UUCP, johnl@n3dmc.UU.NET, uunet!n3dmc!johnl