[net.dcom] Using uucp with Hayes Smartmodem

johnm@houxd.UUCP (11/10/83)

We uucp through Ven-Tels using a method suggested to us by qusavx!allan.
The idea is to set up the L-devices entry for a direct line, rather than
an ACU, and then use the L.sys file to define a dialogue which dials.

Example:

system Any cul0 1200 cul0 "" ^M  $-^M-$ k^M call:-k^M-call: 0000000^M line!^G-r^M-line!^G-r^M-line!^G-r^M-line!^G ^M ogin:-^M-ogin: uucp ssword: xxxxxx

What happens:

uucp sends			uucp expects

				""(nothing)
^M(carriage return)		$(dialer prompt)
k^M				call:(end of "Number to call:")
00000000^M(phone number)	line!^G(end of "Carrier detected...On-line!^G")
^M				ogin:(login: prompt from UNIX)
uucp				ssword:(Password: prmpt from UNIX)
xxxxxx(password)

There is also some provision for retries.  This should work with the Hayes
if the dialogue above is altered a bit.  Note some versions of uucp allow
escaped characters in the L.sys entry - \r for CR, \d for a delay, etc.
Mine didn't, so I had to embed control characters in the file.  Something
like this ought to bring up uucp for you in a hurry.

	John Montgomery
	ihnp4!houxd!johnm

mark@cbosgd.UUCP (11/11/83)

I don't know about your Ventel 212+, but mine requires 2 CR's to
wake up at 1200 baud.  They must be less than 1 second apart, but
cannot be right next to each other at 1200 baud either - at least
3 chars worth of nothing must be between them.  This is very hard
to deal with in hard code (sleep(1) takes > 1 second about half
the time), much less in an L.sys file.  Our solution tries three
times - usually the second one works if the first fails.  Since
we stopped using a Ventel, I have heard that setting a CR delay
in the tty driver works better.

johnm@houxd.UUCP (#J.MONTGOMERY) (11/15/83)

Mark's right, it takes two CR's to wake up the Ven-tel MD212 +2 modem.
My L.sys entry should have read:

system Any cul0 1200 cul0 "" ^M^M  $-^M-$ k^M call:-k^M-call: 0000000^M line!^G-r^M-line!^G-r^M-line!^G-r^M-line!^G ^M ogin:-^M-ogin: uucp ssword: xxxxxx

Mine almost always wakes up without retries, but I have noticed that the
first attempt at dialing ALWAYS terminates in "...Operator Abort", meaning
that a garbage character had gotten to the modem before it can come on line.
It usually takes two more attempts to get through (the second usually gives
"..Busy", and the third completes).  This is all a bit kludgey, but in practice
it has worked pretty well for us.  In fact, the machine I use this with (a
Plexus P/25) doesn't have any source code on it, so this saved my having
to port over a copy and hack a dialer into it.

	John Montgomery
	ihnp4!houxd!johnm