sullivan@aqdata.uucp (Michael T. Sullivan) (06/07/90)
The subject says it all. I haven't tried using it before since I've always been told "it's broken" (without an explanation). Now, somebody wants me to use ct and and "it's broken". I try to ct a number and I get back: No 2400 dialers on this system even though uucp, cu and the rest of the gang can find 2400 lines just fine. -- Michael Sullivan uunet!jarthur!aqdata!sullivan aQdata, Inc. sullivan@aqdata.uucp San Dimas, CA +1 714 599 9992
dold@mitisft.Convergent.COM (Clarence Dold) (06/08/90)
in article <1990Jun6.202530.8038@aqdata.uucp>, sullivan@aqdata.uucp (Michael T. Sullivan) says: > I try to ct a number and I get back: > No 2400 dialers on this system > even though uucp, cu and the rest of the gang can find 2400 lines just fine. This might not the case, since your description makes it sound like you are forcing a dial-out, but... If you call in on the only 2400 line that you have, and try to invoke a 'ct' expecting it to call you back, it won't work. altcon() (I think) looks for a free 2400 device, finds yours, finds a lock file, and hangs. try 'ct -x9 phone_no' to see what's happening. If this is the problem, create another Devices entry at 2400 baud, tied to a /dev/ttyNNN that has no real device. In my case, I used a higher dev number than I have ports on my system. ct allocates the other dialer, hangs up your connection, fails on the other port, looks for another, and finds yours free, dials you back... -- --- Clarence A Dold - dold@tsmiti.Convergent.COM (408) 435-5293 ...pyramid!ctnews!tsmiti!dold FAX (408) 435-3105 P.O.Box 6685, San Jose, CA 95150-6685 MS#10-007
shwake@raysnec.UUCP (Ray Shwake) (06/09/90)
In article <1990Jun6.202530.8038@aqdata.uucp> sullivan@aqdata.uucp (Michael T. Sullivan) writes: >The subject says it all. I haven't tried using it before since I've always >been told "it's broken" (without an explanation). Now, somebody wants me >to use ct and and "it's broken". I try to ct a number and I get back: > > No 2400 dialers on this system Yes, ct is broken on a number of systems. I seem to recall one manual page (either for a Zilog 8000 or an early release ATT 3B2) which said something like "This program has not been shown to work"! But recently (yesterday) I got it working on a Computer Consoles (CCI) 6/32 MP. You don't say what system/environment you're trying to run it on, or what command you tried. Here, I simply used "ct [-h] [-v] -s2400 phone_no". I used the -h and -v options if I wished to force a callout to a tty line other than the current line. Also, note that ACU dialing must be supported. Cu and uucp can live with direct lines, but not ct. I did have a bit of trouble dealing with hangups to the current tty (most of our modems interface to mux ports), and finally resorted to a simple "at" command, viz: % at now +1 min ct -s2400 phone_no <Ctrl>-D % logout