DH> Sigh.  I've now got another episode of the one-way-only disconnect
DH> blues, so I've gone to work on trying to identify the trigger mechanism.

DH> My theory re V8 appears to be full of the proverbial - I managed to
DH> produce a solid case of the fault under the USR v32Terbo protocol. No
DH> V8, no calling tones, no fancy negotiations.  ??????  What the _blazes_...

Do you actually have any evidence for anything other than just a
USR problem, albeit one that is only seen in SOME circumstances ?

DH> Scratch one theory, IMHO.   Wonder what to try next?

You could try sacrificing some chickens |-)

DH> Same shitstorm is still on - I now have a Microcom Deskporte Fast
DH> on the same line, with an occasional retry.  (Two retries so far, in
DH> 1.4Mb.) Holds dead solid in VFC, at 26.4k.   Yet in
"normal" conditions,
DH> the USR craps all over the Microcom for line holding ability and speed.

Sure, but all that shows is that the USRs are sensitive to something.

DH> Now if I just knew what "normal" meant, and
DH> what the #{at}#{at}# is sour at the moment...:-(

Are you still getting the audible ticking in that fault situation ?

DH> Neither USR I have is capable of holding that line at the moment
DH> for longer than 2 minutes maximum.  _However_ both negotiate happily
DH> up to 28.8, and report s/n at over 35db, until the fault hits.

Corse you dont actually KNOW that the S/N is valid in the fault
situation, just that thats what the USR claims is the S/N.

DH> The fault is in severe mode, and as soon as
DH> it's initiated, lock into retrain, and disconnect.

DH>I think I'm gonna take up golf. Easier, cheaper, and more likely profits..:-

Life wasnt meant to be easy boy |-)
@EOT:

---