Michael, at 12:42 on Aug 15 1996, you wrote to Bill Grimsley...

BG> Exactly, so there's no point slagging off at your modem for 
BG> something which is quite obviously beyond its control, is there?

MR> True however I'm not sure phone lines are the problem.  If the stats I 
MR> posted bring this out then fair enough. 

That's EXACTLY what your stats show.  Your lines are terrible.

MR> BTW which ones do I look for and what are acceptable ranges.

The S/N ratio should be 38db or better for a start, and yours isn't.

BG> You have shitty lines, and the best modem in the world is 
BG> not going to change that fact.  It's bad luck, but you're 
BG> basically stuck with it.

MR> True but it still alter the fact my Dynalink will not negotiate _any_ sort 
MR> of connection with at least two BBS' and ISP' using an init string of 
MR> AT&F1&HI&R2X1 or including &K0.  It just squeals
during negotiation but 
MR> does not connect. 

It could just as easily be the remote modem at fault.
 
MR> I can then  hang up and use an init string of
AT&F1&k0X1S32=12S33=32 and 
MR> get a 14400 connect with those same BBS' and ISP _every_ time. Why won't my 
MR> Dynalink negotiate down without having to be set at 14400 (before you ask I
MR> have checked and they _all_ have 28800 modems but I don't know what sort). 
MR> Shitty lines should not cause that.

Sure, but I've already told you to try disabling the 3429 symbol rate and
the V.42 detect phase, both of which are workarounds for problems inherent
in others modems, not necessarily yours.

MR> BTW on each of these calls I was using Dynalinks 
MR> recommended init string of AT&F1&H1&R2X1.

BG> They wouldn't know a decent init$ if it bit them on the arse.  The
&H1&R2 
BG> are defaults for the &F1 template anyway. You DO have a manual, dont you?

MR> Yes I do have a manual and I know those settings are the defaults however
MR> Dynalink acknowledge that those settings are required because the modem
MR> sometimes forgets the defaults.

As usual, I suspect that Askey are talking crap.

MR> Dynalink don't agree and my ISP reckons that I _have_ to have V.42 enabled 
MR> for their modems (still trying to find out what sort they are)

BG> For Christ's sake Mike, &K0 only disables V.42bis data compression.  V.42 
BG> (LAPM with MNP4 fallback) is enabled by default with the &F1 template.

MR> I know that however you suggested disabling the V42 detection stage. I 
MR> wasn't sure how that would work with a provider that _required_ V42. I know 
MR> it has nothing to do with V42bis.

Disabling the V.42 detect phase does NOT prevent the modems from connecting
with V.42, it just stops them from negotiating it themselves.  The whole
point is to FORCE V.42 without the possiblitly of the modems objecting to
it.

MR> Is there any manual/publication/file which sets out how to compare the 
MR> stats produced by ATI6 ATI11 and ATY11 with perfect/ideal ones and what to 
MR> do.

No, but linking into the USR_Modems echo will help, I'd imagine.

MR> I've thought about it lately with this one anyway. There is one thing you 
MR> may be able to add.  On one particular BBS I connect then about 20 seconds 
MR> later it drops carrier.  ATI6 displays the reason for the disconnect as 
MR> GSTN  cleardown. I can't find anything on GSTN cleardown.  Can you shed any 
MR> light on it?

  GSTN (General Switch Telephone Network) Clear Down:  

     The connection was non-ARQ and DTR was dropped from one side 
     of the connection, or the DISC frame was corrupted due to noise.

Sounds to me like the original connect was made without error correction,
something which disabling the V.42 detect phase is supposed to prevent.

Regards, Bill
@EOT:

--- MsgedSQ/2 3.50