[comp.dcom.modems] Answer while dialing

bill@carpet.WLK.COM (Bill Kennedy) (08/21/88)

I don't like cross posting either, but the problem seems initmately related
to the modem or to uucp.  I have seen it on the US Robotics, but it's most
aggravated on the brand new Trailblazer Plus.

The modem part of the problem is two fold.  Telling the TB+ to wait for
dial tone before dialing doesn't work on mine 80% of the time because
it gives up immediately with NO DIAL TONE.  I can hear dial tone for a
split second before it gives up.  I'm on an ancient Central Office, perhaps
that's the problem.  Is anyone aware of any adjustment that can be made to
lower the threshhold for sensing dial tone?

In particular what I'm asking about is a phenomenon where uucico is dialing
and the modem gives up on a BUSY.  During the time from when it goes back
on hook and before uucico times out, the modem will answer a call but nothing
can happen because of the lock file for the tty.  I have tried S0=0 and that
sure enough keeps the modem from answering but the DTR transition doesn't
always give it a good reset to recall the stored setup.

Related to this is the case where a call comes in and the modem answers before
uugetty or uucico can get a lock on the tty and both the uugetty and uucico
(uucico was just about to dial) fail.  Since ssbn is long distance from
almost every place in the free world it means that they pay for a call but
don't get through.  Statistically the odds of these collisions are very slim
but I guess my uucp and TB+ aren't much for statistics, it happens two to
three times per week.

Before I ask for help, ssbn is running AT&T 386 UNIX Vr3.1, HDB, nothing
fancy there.  The TB+ has the latest (not the Beta) ROM's and was set up
per Telebit's article on how to do it (except I turned off compression).
I'm sure that wait for dial tone would help but it doesn't seem to wait the
two seconds it's supposed to (most of the time) and when it does it doesn't
always "hear" it.  Now the questions -

Is anyone else experiencing answer/originate collisions?
Is there anything in the Trailblazer or uucp that can be done to minimize,
if not eliminate them?
If someone has experienced and conquered the same problem, may I have the
TB+ settings and uugetty arguments you used to whip it?

Many thanks, I'm not sure if it's the modem, uucp or both that are causing it.
-- 
Bill Kennedy  Internet:  bill@ssbn.WLK.COM
                Usenet:  { killer | att | rutgers | uunet!bigtex }!ssbn!bill