7300 - Decserver chat script

[James C. Benz]

Sender: 
Reply-To: jcbst3 at unix.cis.pittsburgh.edu (James C. Benz)
Followup-To: 
Distribution: 
Organization: Univ. of Pittsburgh, Comp & Info Sys
Keywords: 

The University here has their campus network set up so that the phones are
answered by a Decserver 500.  I have 3 3B2's connected to the network, and
a 7300 PC at home.  I have been trying for some time without success to set
up a uucp chat script on the 7300 so that it can call and extablish mail links
etc. with the 3B's.  I have yet to find a way to get the 7300's uucico through
the Decserver.  Specifically, I can not get the server's Local> prompt.  I can
call up the server via cu, with not special options, and by hitting a few
returns, get the prompt every time with no problem.  Uucico, however, can send
all the \r's and \d's I can put on a line with absolutely no response.  Please,
if anyone knows the answers to the following two questions, or has any light
to shed on this, email me so I can get some sleep.  Transferring big files
by cu's ~%take during off peak hours (11PM to 5AM) is no fun, and it would be
so nice to have email at home.

Question 1) Has anyone gotten a 7300 to call through a decserver, and how did
	you do it?
Question 2) Does anyone have a complete list of the chat script tokens that
	the 7300's uucico understands?  A friend has a Berkeley Unix script
	that he uses on another machine, but some of the tokens he uses mean
	nothing to the 7300.  Specifically, he uses ~5 to mean "wait only
	five seconds for the expect string before sending the next send
	string".  I think the Decserver will respond if I can say something
	like "ocal>-~5\r\d-ocal>" or "expect ocal>, if you don't get it in
	five seconds, send \r\d and expect ocal>, repeat until you get it".
	I have had some limited success with long strings of \r\d's 
	interspersed with ""'s but when the Decserver responds early, (It does
	occasionally respond to this, but not reliably) the extra \r's are
	then transmitted to the prompt, producing only error messages that
	cause the chat script to fail.  The script "ocal>--ocal>" waits
	indefinitely for the ocal> prompt, at least long enough for the 
	server to time out and drop the line.

Thanks for any help you might offer.


-- 
Disclaimer: All opinions expressed herein are mine alone.  I wear an 
	asbestos suit to work, so flame away.  Pitt doesn't care *what*
	I do, so long as I appear to be working behind this terminal.
Jim Benz, University of Pittsburgh, UCIR