Re: Re MIB Comments 11

["Mark S. Lewis" <[e-mail]>]

>>>>> On Tue, 1 Feb 94 00:39:42 -0600, [e-mail] said:


> Concerning 'blind dialing' and the need for a wait before dial timer, Mark Lewis 
> writes:

> I don't follow you here. mdmCCCallProgressDetect controls the
> detection and messaging of dial & busy tones.  It does not specify any
> action (eg. 'blind dialing').

> It doesn't sound to me like we need mdmPauseBeforeBlindDialingTime
> because of mdmCCCallProgressDetect.  Is there some other reason?
> _______________________________________________________

> First, the normal dialing procedure is to issue an ATD command with a number to 
> call. The phone goes off hook but the modem does not dial the number until it 
> detects dial tone. Now, suppose you disable dial tone detection. The modem would 
> never dial the number would it? So, you can configure the modem to ignore dial 
> tone so that when the ATD command is issued with a number to dial, the phone 
> goes off hook and dials the number after a predetermined time. This is blind 
> dialing. It is necessary to wait after going off hook before dialing however, 
> since the dial tone is not present immediately. If the number is dialed without 
> waiting for dial tone to be present, the connection attempt would not be 
> successful.

> The object that I propose allows this predetermined wait time to be set. The 
> default should probably be about 2 or 3 seconds. Without this object, we would 
> have one object that can configure the modem into a state that may not work 
> because we don't have the associated object to set the wait time to make it work 
> properly.

Thanks for the clarification of blind dialing.  However, it still is
not clear to me how mdmCCCallProgressDetect requires
mdmPauseBeforeBlindDialingTime.

Do others think mdmPauseBeforeBlindDialingTime is useful?  Thanks.

... Mark

==========--------------       Mark S. Lewis      ----------==========
[e-mail]       Telebit Corp.      Voice [phone]