Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!easy!lron Newsgroups: comp.sys.amiga Subject: Re: UUCP Incomming calls Message-ID: <18727f3a.ARN090a@easy.hiam> Date: 31 Dec 90 03:27:38 GMT References: <6620@crash.cts.com> Reply-To: uunet!easy!lron Followup-To: comp.sys.amiga Organization: You must be talking about someone else. Lines: 41 Expires: Keywords: Distribution: In article <6620@crash.cts.com>, Bob Lindabury writes: > I'm having some problems with incomming calls via UUCP1.06D. I am running > a Hayes Ultra 96 modem and have no problems dialing out. I have been > receiving incomming calls but there seems to be a problem when the calling > system has a lower baud than my first -B setting when running GETTY. > > I have getty running thusly: > > run nil: Getty -B38400 -B19200 -B9600 -B4800 -B2400 -B1200 -Mh -7 ATS11=45 > Now, when a 2400 baud system dials my system, do they have to send breaks > or something so the speed will drop on the port? My GETTY:logfile states > that I'm getting 2400 baud connects but then the guy on the other end says > that his system is waiting for ogin: but that all he sees is garbage that > looks to be speed problems (-X9). His system never sees the ogin: and hence > never connects fully. When I dial out to his system we connect without a > problem. Well, I don't know of any 9600 modems that don't support locked baud rates, so the trick is to do it like this: run < nil: >nil: Getty -B19200 -Mh -7 -A ATS11=45 The -A will lock the comm port at 19.2K and the modem will handle adjusting to the actual speed the other modem is connecting at. If you don't do this your modem is likely going to be sending the info into your serial port at the rate it was set at when it sent the RING message indicating an incomming call, but Getty will change the rate to whatever the connect message is (CONNECT 2400) which will cause problems as Getty will be reading the serial port at 2400 while the modem sends at 19.2Kbps. This is the line I use with my USR dual standard and it has worked with connects at 1200, 2400, and 9600 (V.32) without problems: run >nil: