TIP: Click on subject to list as thread! ANSI
echo: aust_modem
to: Michael Raiteri
from: Ian Smith
date: 1996-08-23 19:05:36
subject: DYnalinks V34+ modems

MR> cleardown.  Can you shed any light on it?

BG>  GSTN (General Switch Telephone Network) Clear Down:

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

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

Not directly - bypassing the detect phase to a modem known to support LAPM
can solve some problems, with some modems, but disabling V.42 detect phase
(thus going straight into LAPM protocol negotiation) by itself needn't be
directly related to whether you're demanding an EC connection or not; well
on my modem it's optional. anyway.

 MR> with and without compression.  Dynalink support haven't a

We already know that BTLZ compression is broken on these, don't we?

 MR> clue why in one case I
 MR> cannot get a connect other than at 14400 fixed and on a BBS
 MR> a connect then drop
 MR> carrier with the disconnect message GSTN cleardown. As I
 MR> mentioned previously,
 MR> Dynalink don't even know what the hell GSTN is.

As Arthur's mentioned, this might be a problem more related to training too
'aggressively'; the symptoms are similar to those experienced with Arthur's
Motorola or my Dataplex DPX596 when told (or configured by default) to
demand, in effect, too high a signal quality reading for any given
negotiated speed.

This effect has been seen consistently calling various modems, lately
around here a rack of Netcomm V.34 modems which are likely set too
insensitive, maybe again from poor defaults to best cope with locally
non-optimal lines.  I found this earlier to be a problem with some older
Maestros, on problematic lines.

It may be a matter of finding out what can you set in the Dynalink /
Sportster to have it train less aggressively, that is, to fallback or
negotiate a lower speed connect, with a given determined line quality?  It
seems to be the extra negotiation time that makes others (esp. the
Netcomms) assume / demand a non-EC connect.  You need particularly good
lines to support non-EC connects at any rate much above 14400 (hence the
cleardown disconnects later).

Ian

--- MaltEd 1.0.b5

* Origin: Magic Puddin' BBS Nimbin 066-89-1843 V.32bis/V.42 (3:626/660)
SEEN-BY: 50/99 620/243 623/630 625/100 626/660 661 664 666 667 668 670
SEEN-BY: 711/401 409 410 413 430 501 808 809 899 932 934 712/515 713/888
SEEN-BY: 714/906 800/1
@PATH: 626/660 711/401 808 934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.