Re: mdmCallProgressDetect
"Mark S. Lewis" <mlewis@telebit.com> Sat, 05 February 1994 08:41 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01698; 5 Feb 94 3:41 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa01694; 5 Feb 94 3:41 EST
Received: from apache.telebit.com by CNRI.Reston.VA.US id aa02353; 5 Feb 94 3:41 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 AA28269 to Kim_Ooi@3Mail.3Com.COM; Fri, 4 Feb 94 16:03:53 PST
Received: from yoyo.telebit.com by america.Sunnyvale.Telebit.COM (4.0/america.telebit.com-DBC-930718) id AA02638 to modemmgt@apache.Sunnyvale.Telebit.COM; Fri, 4 Feb 94 16:03:49 PST
Date: Fri, 04 Feb 1994 16:03:49 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Mark S. Lewis" <mlewis@telebit.com>
Message-Id: <9402050003.AA02638@america.Sunnyvale.Telebit.COM>
Received: by yoyo.telebit.com (4.1/SMI-4.1) id AA06714; Fri, 4 Feb 94 16:03:49 PST
To: waldbusser+@cmu.edu
Cc: modemmgt@telebit.com
In-Reply-To: <EhIIl2a00WAr1AGh5h@andrew.cmu.edu> (waldbusser+@CMU.EDU)
Subject: Re: mdmCallProgressDetect
Reply-To: Mark.S.Lewis@telebit.com
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
>>>>> On Thu, 3 Feb 1994 14:10:58 -0500 (EST), Steven Waldbusser <waldbusser+@CMU.EDU> said: > Finally: > Mark Lewis writes: >>Page 17: I think we should add a mdmCCCallProgressState (before >>mdmCCCallProgressDetect) like callProgressState from V.58. This >>should be a read-only variable. > Les Brown writes: >>5) On call progress state, this is a very transient condition, that is, >>each state is only active for a short period of time. > Mark Lewis writes: >>When things get stuck, this isn't a transient state. I think this >>would be a helpful debug object. > Do things ever get stuck? The modem will time out if there is no dial > tone detected in a short interval (5 seconds on a modem I tested). Then > it will time out if there is no carrier detected in a longer interval > (50 seconds on a modem I tested). The rest of the connection (99+%), it > is in the same state (as far as call progress is concerned). In order > to ever see the noDialTone state, you would have to poll every 2.5 > second on average. In order to ever see the noCarrier State you would > have to poll every 25 seconds on average. Why not just wait for the > timeout period to expire and check the failure reason? I agree with Les > - I don't see how this would be used. > Steve Ok. You argued me out of this. I officially withdraw my suggestion about mdmCCCallProgressState. :-} ... Mark ==========-------------- Mark S. Lewis ----------========== Mark.S.Lewis@Telebit.com Telebit Corp. Voice (408) 745-3232
- mdmCallProgressDetect Steven Waldbusser
- Re: mdmCallProgressDetect Mark S. Lewis