Re: mdmCConnectFailReason
"Mark S. Lewis" <mlewis@telebit.com> Thu, 17 March 1994 21:35 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13037; 17 Mar 94 16:35 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa13033; 17 Mar 94 16:35 EST
Received: from apache.telebit.com by CNRI.Reston.VA.US id aa23435; 17 Mar 94 16:35 EST
Received: from america.Sunnyvale.Telebit.CO (america-bb.sunnyvale.telebit.com) by apache.telebit.com (4.1/SMI-4.1/Telebit-Apache-Brent-930718) id AA14681 to ietf-archive@cnri.reston.va.us; Thu, 17 Mar 94 13:25:51 PST
Received: from yoyo.telebit.com by america.Sunnyvale.Telebit.COM (4.0/america.telebit.com-DBC-930718) id AA27836 to modemmgt@apache.Sunnyvale.Telebit.COM; Thu, 17 Mar 94 13:25:47 PST
Date: Thu, 17 Mar 1994 13:25:47 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Mark S. Lewis" <mlewis@telebit.com>
Message-Id: <9403172125.AA27836@america.Sunnyvale.Telebit.COM>
Received: by yoyo.telebit.com (4.1/SMI-4.1) id AA00974; Thu, 17 Mar 94 13:25:47 PST
To: modemmgt@telebit.com
In-Reply-To: <9402157637.AA763768176@robogate.usr.com> (rroyston@usr.com)
Subject: Re: mdmCConnectFailReason
Reply-To: Mark.S.Lewis@telebit.com
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
I have taken Rick's suggestion, V.58 callCleared, and the prior modemmgt mib versions and rehashed this object. The following is my suggestion. Unless anyone has a strenous objections, how about we include it in the mib and produce the I-D. We will have a final call period to make any last minute modification. If you have such objections, please speak up now so we can get the I-D done ASAP. Thanks. ... Mark ==========-------------- Mark S. Lewis ----------========== Mark.S.Lewis@Telebit.com Telebit Corp. Voice (408) 745-3232 mdmCCConnectionFailReason OBJECT-TYPE SYNTAX INTEGER { -- General unknown(1), other(2), managementCommand(3), inactivityTimeout(4), mnpIncompatibility(5), protocolError(6), -- DCE powerLoss(10), equipmentFailure(11), -- DTE Interface dtrDrop(20), -- Line Interface noDialTone(30), lineBusy(31), noAnswer(32), voiceDetected(33), -- Signal Converter carrierLost(40), trainingFailed(41), faxDetected(42) } MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the reason that the last connection or at- tempt failed. The meaning of each reason code is ex- plained below. unknown: This code means the failure reason is unknown or there has been no previous call. other: This code used when no other code is applicable. Additional vendor information may be available elsewhere. managementCommand: A management command terminated the call. These commands include escaping to command mode, initiating dialing, restoring lines, and disconnecting. inactivityTimeout: The call was terminated because it was inactive for at the minimum duration specified. mnpIncompatibility: The modems are unable to resolve MNP protocol differences. protocolError: An error occured in one of protocol in use. Further information is required to determine in which protocol the error occurred, and the exact nature of the error. powerLoss: The modem lost power and disconnected the call. equipmentFailure: The modem equipment failed. dtrDrop: DTR has been turned off while the modem is to disconnect on DTR drop. (Ref: V.58 cct108TurnedOff) noDialTone: If the modem is to monitor for call progress tones, but the modem has failed to detect dial tone while attempting to dial a number. lineBusy: Busy signal is detected while busy signal detection is enabled, or while the 'W' or '@' dial modifier is used. (Ref: V.58 engagedTone) noAnswer: The call was not answered. voiceDetected: A voice was detected on the call. carrierLost: Indicates that the modem has disconnected due to detection of loss of carrier. In TIA-602, the S10 register determines the time that loss of carrier must be detected before the modem disconnects. trainingFailed: Indicates that the modems did not successfully train and reach data mode on the previous connection. faxDetected: A fax was detected on the call. REFERENCE "V.58 callCleared" ::= { mdmCallControlEntry 6 }
- mdmCConnectFailReason Rick Royston
- Re: mdmCConnectFailReason Mark S. Lewis