Date: Thu, 18 Nov 1999 00:14:32 -0800 From: Kent Stewart <kstewart@3-cities.com> To: Annelise Anderson <andrsn@andrsn.stanford.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: USR 56k Profesional Message Modem Message-ID: <3833B568.A49E8F3D@3-cities.com> References: <Pine.BSF.4.10.9911172334380.87059-100000@andrsn.stanford.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Your comment about B0 rang a bell because that is where it chooses ITU or US answering tones. B1 is US tones. I was really thinking of &H1 and &R2 instead of &F1. I don't know about your stty command because I was always on the PC end when we tested the lines. With user-ppp, I set the line to 115.2 kb and tell it to dial. No one dials into this system. Your initialization on the one that is answering at 9600 needs to be pre-established at 38.4 kb or 57.6 kb. If the link between the computer and the modem is established at 9600 the modem will not select a higher baud rate. Kent Annelise Anderson wrote: > > On Wed, 17 Nov 1999, Kent Stewart wrote: > > > Annelise Anderson wrote: > > > > > > On Wed, 17 Nov 1999, Kent Stewart wrote: > > > > > > > Annelise Anderson wrote: > > > > > > > > > > This interests me quite a lot, because I have external 56K Sportster > > > > > Robotics modems at home and at the office (on a regular phone > > > > > line); I can dial out just fine and make connections, but I can't > > > > > get the modem at the office to answer and establish a connection > > > > > at better than 9600. This is v.90; maybe I should turn that off? > > > > > > > > The v.90 should be a choice. For example, I occasionally get 28.8kb > > > > and I know I have a bad line but the handshaking also has a different > > > > tone and I was told that was leaving v.90. > > > > > > > > Your two user modems should not be able to connect are more than 33.6 > > > > because each considers the other an upload and settle for 33.6 kb max. > > > > The modems that support 53kb are different from the ones a user can > > > > purchase. > > > > > > > > I don't have any idea why they wouldn't connect at 33.6kb other than a > > > > mismatch or line quality between them. That is terrible and I would > > > > expect a configuration problem. They are supposed to argue until they > > > > come up with something they both support. In your case, it is 9.6 kb > > > > > > > > You can set them up to tell what the connection is and I would log > > > > that and see if it provides any clues. > > > > > > > > Kent > > > > > > The problem is that unless I have std.9600 in /etc/ttys, I can't > > > connect at all; I either get continual garbage on the screen or a > > > login that responds but doesn't allow the ppp (or pppd) connection > > > to come up. These failure don't log. For a while I had some sort > > > of a rotary thing set up in gettytab, but this doesn't work either. > > > > Have you tried locking the DTE rate and let the modem buffer the > > connection. I use &F1 and &B1. That locks the serial rate between the > > computer and the modem and specifies Hardware Flow control. You fix > > the serial port at some rate such a 57.6kb or 115.2kb and let the > > modem connect at what ever speed it wants to. You have to use Hardware > > flow control (RTS/CTS) to block when one of the pieces is getting > > ahead of the other. > > > > Kent > > Yes, I have a definition in gettytab that looks like this: > > # AA's VHS modem > vm|VH300|VHS at 300,8-bit:\ > :nx=VH57600:tc=std.300: > vn|VH1200|VHS at 1200,8-bit:\ > :nx=VH300:tc=std.1200: > vo|VH2400|VHS at 2400,8-bit:\ > :nx=VH1200:tc=std.2400: > vp|VH9600|VHS at 9600,8-bit:\ > :nx=VH2400:tc=std.9600: > vq|VH14400|VHS at 14400,8-bit:\ > :nx=VH9600:tc=std.14400: > vs|VH19200|VHS at 19200,8-bit:\ > :nx=VH14400:tc=std.19200: > vt|VH28800|VHS at 28800,8-bit:\ > :nx=VH19200:tc=std.28800: > vu|VH38400|VHS at 38400,8-bit:\ > :nx=VH28800:tc=std.38400: > vv|VH57600|VHS at 57600,8-bit:\ > :nx=VH38400:tc=std.57600: > > that I use with VH38400 in ttys instead of std.9600, in the ttyd0 entry: > > ttyd0 "/usr/libexec/getty VH38400" dialup on secure > > The modem output looks like this: (Maybe it needs to be B1 in the > first line?) > > Script started on Wed Nov 17 23:20:10 1999 > Connected. > ATATE1Q0 > OK > ATI4 > U.S. Robotics 56K FAX EXT Settings... > > B0 E1 F1 M1 Q0 V1 X4 Y0 > BAUD=9600 PARITY=N WORDLEN=8 > DIAL=TONE ON HOOK CID=0 > > &A3 &B1 &C1 &D2 &G0 &H1 &I0 &K1 > &M4 &N0 &P0 &R2 &S1 &T5 &U0 &Y1 > > S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 > S07=060 S08=002 S09=006 S10=014 S11=070 S12=050 S13=000 > S15=000 S16=000 S18=000 S19=000 S21=010 S22=017 S23=019 > S25=005 S27=000 S28=008 S29=020 S30=000 S31=128 S32=002 > S33=000 S34=000 S35=000 S36=014 S38=000 S39=000 S40=001 > S41=000 S42=000 > > LAST DIALED #: T > > OK > ATI5 > U.S. Robotics 56K FAX EXT NVRAM Settings... > > Template Y0 > > DIAL=TONE B0 F1 M1 X4 > BAUD=9600 PARITY=N WORDLEN=8 > > &A3 &B1 &G0 &H1 &I0 &K1 &M4 &N0 > &P0 &R2 &S1 &T5 &U0 &Y1 > > S00=001 S02=043 S03=013 S04=010 S05=008 S06=002 S07=060 > S08=002 S09=006 S10=014 S11=070 S12=050 S13=000 S15=000 > S19=000 S21=010 S22=017 S23=019 S25=005 S27=000 S28=008 > S29=020 S30=000 S31=128 S32=002 S33=000 S34=000 S35=000 > S36=014 S38=000 S39=000 S40=001 S41=000 S42=000 > > > Strike a key when ready . . . > > Template Y1 > > DIAL=TONE B0 F1 M1 X4 > BAUD=9600 PARITY=N WORDLEN=8 > > &A3 &B1 &G0 &H1 &I0 &K1 &M4 &N0 > &P0 &R2 &S1 &T5 &U0 &Y1 > > S00=001 S02=043 S03=013 S04=010 S05=008 S06=002 S07=060 > S08=002 S09=006 S10=014 S11=070 S12=050 S13=000 S15=000 > S19=000 S21=010 S22=017 S23=019 S25=005 S27=000 S28=008 > S29=020 S30=000 S31=128 S32=002 S33=000 S34=000 S35=000 > S36=014 S38=000 S39=000 S40=001 S41=000 S42=000 > > OK > ATE0Q1&W1W0 > Script done on Wed Nov 17 23:26:37 1999 > > I've struggled a lot with this without success, so I appreciate > your efforts to help. I hope I'm doing something wrong, however > stupid. I even sent a modem back to U.S. Robotics for "repair." > > The output of stty -a -f /dev/ttyd0 shows it (I'm not sure if it's > the rate at which it is connecting to the computer or the line) > as: > > speed 9600 baud; 0 rows; 0 columns; > lflags: -icanon -isig -iexten -echo -echoe -echok -echoke -echonl > -echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin > -nokerninfo -extproc > iflags: -istrip -icrnl -inlcr -igncr -ixon -ixoff -ixany -imaxbel -ignbrk > -brkint -inpck -ignpar -parmrk > oflags: -opost -onlcr -oxtabs > cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow > -dtrflow -mdmbuf > cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>; > eol2 = <undef>; erase = ^?; intr = ^C; kill = ^U; lnext = ^V; > min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T; > stop = ^S; susp = ^Z; time = 0; werase = ^W; > > Annelise > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3833B568.A49E8F3D>