From: pclink@qus102.qld.tne.oz.au (Rick) Subject: Re: getty_ps - CONNECT keyword failing ? Date: Wed, 4 Aug 1993 08:00:18 GMT
grant@kcms.ipgis.co.za (Grant Smith) writes:
>I recompiled getty_ps (from /usr/src/getty_ps), as the Serial FAQ mentioned
>1.02 was using a different, older version. The I tried to setup a modem to
>answer on ringback. The physical part worked, ie phone once, hangup, phone
>again, modem answers. The CONNECT sequence found 9600 as the connect baud rate,
>which is correct, but the remote modem was just getting garbage, which I
>correctly suspected was as a result of an incorrect baud rate.
Try removing the "\A" from the CONNECT string. If that fixes it then
your problem is that uugetty is connecting to the serial port at a baud
rate other than 9600 (have a look at /etc/inittab), while your modem is
handling speed conversion internally. During the setup/answer
sequence, getty is talking to the modem at, say, 38400. When the modem
detects a carrier, it returns the speed of the link, but continues
talking at 38400. getty, on the other hand, sees the 9600 in the
connect string and downshifts, screwing up the connection. With most
modern modems, it pays to talk to the modem at the highest speed possible
and let it handle speed conversions internally. This allows the modem
to do on-the-fly compression (V42?) to effect a greater transfer rate
than you would get by setting the serial port to the speed you think
you should be getting.
Rick.