msc@qubix.UUCP (Mark Callow) (06/03/83)
I too have noticed systems calling us and not waiting long enough for an answer. I have modified conn.c so that the timeout is calculated based on the length of the number. (10 digits is assumned to be long distance and gets a big timeout.) I then program the dialer with this value (a Hayes Smartmodem 1200) and add 10 secnds and use the new value for the alarm call. I have used timeouts as long as 75 seconds because I was trying to call the East Coast via Sprint/MCI. These calls never worked and I abandoned the attempt. I now use a 50 second timeout on long distance calls via Ma Bell. [The reason Sprint/MCI is NBG (I believe) is because they use half duplex statistical multiplexers in their networks which obviously don't allow full duplex 212a modems to work over the same lines.] Mark Callow
smh@mit-eddi.UUCP (06/04/83)
Not to mention, some supposedly clever autodial modems feature automatic call abort if carrier is not returned within, say, 24 seconds. This is definitely not long enough for some calls. In the modems with which I am familiar, this feature can be disabled by cutting jumpers.
darrelj@sdcrdcf.UUCP (06/09/83)
On my ancient Vadic ACU, there is a potentiometer which sets the time before the dialer hardware raises the signal "Abandon Call and Retry". This timer is started when the dialer receives an End of Number code, and trips from 5 to 60 seconds later.