Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!uunet!swlabs!jack From: jack@swlabs.UUCP (Jack Bonn) Newsgroups: comp.unix.questions Subject: Re: cu Message-ID: <237@swlabs.UUCP> Date: Sun, 7-Jun-87 12:45:38 EDT Article-I.D.: swlabs.237 Posted: Sun Jun 7 12:45:38 1987 Date-Received: Thu, 11-Jun-87 01:13:19 EDT References: <7708@brl-adm.ARPA> Organization: Software Labs, Ltd. Easton CT USA Lines: 41 Summary: How to fix cu for long distance delays. In article <7708@brl-adm.ARPA>, hugh@BRL.ARPA (USAFAS | Howard) writes: > I am trying to use cu for telecommunications with an Intel 310 > running xenix 3.0. Whenever I try to make a long distance call through > my FTS line, the process times out, "DN timeout". What does this mean? > Is there a way that I can change the timeout setting to allow a longer > time to make the connection? Sorry for the delay in replying. I have been trying to send you e-mail, but have been unsuccessful. I really don't know what an FTS line is, but I have a few things you can try. 1) I assume that you are doing the dialing from the L.sys file. In this file, locate the send/expect strings where the number is dialed. Insert "\r\d\c" immediately after the dial string. This is the string that starts out with ATDT if you have a Hayes compatible dialer. The \r means to send a carriage return. The \d indicates to delay here. The \c says not to send a carriage return at the end of the string (we already sent one). If needed, add more \d's. Each causes a two second delay. The example send field would be: ATDT12125551212\r\d\c. This should fix the problem. 2) You might try putting a "#" after the number that you are dialing, if it is sent via touch tone. This indicates that you have no more digits to send to the CO (central office). It is actually sent via two tones, just like the digits, and it prevents the CO from using timing to determine if you are done sending. It also saves you time. I use it all the time even when manually dialing. It is especially useful on international calls, where the local phone company doesn't know how many digits to expect. An example of this would be: ATDT12125551212#\r\d\c. I have a question for you. Is 3.0 the latest version of Xenix running on a 310? I have the task of helping my agent get his 310 system running and he is running Xenix v1.0! It is really a pain. Does 3.0 have a getty? Is there a call to IOCTL(2) in section 2 of the manual? I am trying to have him use the same modem for originating and terminating calls. I have a program here to do it, but it relies on running under System V (I think). I am having him order the upgrade, but I don't know if it will help. Maybe you can make use of this program, when I get it working. Let me know. -- Jack Bonn, <> Software Labs, Ltd, Box 451, Easton CT 06612 seismo!uunet!swlabs!jack