Re: Still looking for answers

Lars Poulsen <> Wed, 09 February 1994 19:16 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa14525; 9 Feb 94 14:16 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa14521; 9 Feb 94 14:16 EST
Received: from by CNRI.Reston.VA.US id aa14871; 9 Feb 94 14:16 EST
Received: from america.Sunnyvale.Telebit.CO ( by (4.1/SMI-4.1/Telebit-Apache-Brent-930718) id AA10965 to; Wed, 9 Feb 94 11:09:16 PST
Received: from by america.Sunnyvale.Telebit.COM (4.0/ id AA00375 to modemmgt@apache.Sunnyvale.Telebit.COM; Wed, 9 Feb 94 11:09:14 PST
Received: from eskimo.CPH.CMC.COM by (4.1/SMI-4.1/Telebit-Apache-Brent-930718) id AA10951 to modemmgt@Telebit.COM; Wed, 9 Feb 94 11:08:58 PST
Received: by eskimo.CPH.CMC.COM (4.1/SMI-4.1-eskimo) id AA12187; Wed, 9 Feb 94 15:39:26 +0100
Date: Wed, 9 Feb 94 15:39:26 +0100
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Lars Poulsen <>
Message-Id: <9402091439.AA12187@eskimo.CPH.CMC.COM>
Subject: Re: Still looking for answers

	Excerpts from modemmgt:
	29-Jan-94 MIB comments Steven Waldbusser@CMU.ED (11867)

	> >  13. mdmStatsIncomingAbnormalTerminations - how is this different  
	> >  from failed connection requests.  All connections abnormally 
	> >   terminate by loss of DCD, or some other means.

	> Your point about all connections terminating by loss of DCD is
	> interesting.  Is there a simple way to differentiate abnormal
	> terminations from normal terminations?  Or will
	> successfulConnections == abnormalTerminations?

For "dumb" modems (or error correction modems in "direct" mode)
all connections terminate either by a local HANGUP command or
by loss of carrier.

For error correcting modems, there is a disconnect line command
handshake defined. Several major brands of modems, however, do
not implement the handshake correctly. When interworking with such
a modem, all connections probably terminate abnormally.
Hopefully, these vendors will get it right in their next firmware
cycle (V.34/V.34bis ?)

/ Lars Poulsen