Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!cuae2!ltuxa!ttrdc!levy From: levy@ttrdc.UUCP Newsgroups: comp.unix.questions Subject: Re: call back software Message-ID: <1529@ttrdc.UUCP> Date: Mon, 23-Feb-87 18:48:03 EST Article-I.D.: ttrdc.1529 Posted: Mon Feb 23 18:48:03 1987 Date-Received: Thu, 26-Feb-87 21:41:32 EST References: <4403@brl-adm.ARPA> <288@desoto.UUCP> <2695@ecsvax.UUCP> Organization: AT&T, Computer Systems Division, Skokie, IL Lines: 31 In article <2695@ecsvax.UUCP>, emigh@ecsvax.UUCP writes: >In article <288@desoto.UUCP> attc@desoto.UUCP (ATT Communications) writes: >>Try the ct command! > >Quote from AT&T 3B2 System V Release 3.0, page 34 > > The ct command is not compatible with the Basic Networking Utilities. >Do not use this command. >-- >Ted H. Emigh Genetics and Statistics, North Carolina State U, Raleigh NC The original message is gone from my system and I can't remember whether the original requestor said he had SVR3 or SVR2. I _have_ gotten ct to work, after a fashion, on a SVR2 3B2 system with at least one dial-in port which is different from a free dial-out port. How I kludged it was to dial in, then "exec ct -s 'speed' -v 'your_number'". (Note, the "exec" is needed, else the original dial in port will be tied up by the shell even after the "ct" finishes.) ct will acquire the acu and then hang you up, at which point it will (try to) call you back using the acu. I do not know if this kludge would work on SVR3 (do not have it handy to try). It might fail on SVR3 for different reasons than on SVR2. -- ------------------------------- Disclaimer: The views contained herein are | dan levy | my own and are not at all those of my em- | an engihacker @ | ployer or the administrator of any computer | at&t computer systems division | upon which I may hack. | skokie, illinois | -------------------------------- Path: ..!{akgua,homxb,ihnp4,ltuxa,mvuxa, allegra,ulysses,vax135}!ttrdc!levy