From: dawson@willard.UUCP
Newsgroups: comp.bbs.waffle
Subject: Re: Bug with Incoming Calls.
Keywords: dos waffle 165 beta 9
Date: 29 Jul 92 03:00:24 GMT
Organization: Willard's House BBS, Atlanta, GA -- +1 (404) 664 8814

frampton@vicuna.ocunix.on.ca (Steve Frampton) writes:

> I believe that once a 'Ring' is detected, Waffle should cool its jets for 
> awhile and make sure incoming calls are given a chance to succeed (if a 
> caller was calling long distance they would have to pay the minimum 
> charge because of this).

I believe that once a RING is detected, Waffle should provide an option...
to ignore or not.  AND, it already does, I think.  If you put uu.drops:RING
in the static file.  Actually, I believe the incoming call gets hung up
upon anyway (gh0d, isn't that horrible English!).  The uu.drops bit does
let Waffle realize the call has failed much sooner than it would ordinarily,
as otherwise Waffle must wait for the defined timeout period to determine
the call has failed.

Do I dare mention that I believe that Waffle's handling of uu.drops : RING
is broken!?  My modem has echos RRING on the remote ring detection.  If
I enable uu.drops:RING, the RRING causes Waffle to hang up!  Damn.  So,
I can't use the stinkin' uu.drops thingy.

> 
> I realize that the chances of this happening simultaneously aren't very 
> high, but they do increase depending on frequency of cron jobs run.

Actually, the chances of this happening simultaneously are EXTREMELY high.
Indeed, I seem to see it several times per day.  Wanna know something!?
I've got a Lynx RingDirector to control routing of my distinctive ringing.
I can hear incoming calls click through the RingDirector, then next I hear
the relays pop in the modem... then I see the Ring message on Waffle's
console.  I have on occasion seen a CONNECT 19200 message appear as my
site is dialing out, but just prior to executing the first instruction in
my DIALERS file.  The modem is connected with an incoming call.  My system
is in the midst of an outbound call, which of course never succeeds.  When
the timeout value is exceeded, the port is reset, which of course kills
the current connection... someone pays for potentially significant amounts
of 'minimum charge.'

It seems to me that Waffle gets a bit schizo.  (OH NO!  Not the old bbs-
newsreader-bbs-newsreader-etc. cascade!!!)  Perhaps, as Waffle is preparing
to call out, it should FIRST disable auto-answer.

It also seems to me that nobody's gonna get charged for anything, long
distance or not, if all they get is RING and no connect... for just a
few rings, anyway.  I believe AT&T charges, and possibly other carriers
also charge, for network usage if you try to let an attempted call ring
ad nauseum...

It seems to me that is the calling party's responsibility!  They should
definitely set their timeout value on outbound calls sufficiently low
(for ld calls, anyway) to avoid network usage fees.

> 
> Thanks.
> 
> ----------------------------------------------------
> frampton@vicuna.ocunix.on.ca (Steve Frampton)
> Vicuna Systems BBS - 613/547-5066 [9600 v.32/.42bis]


-- 
dawson@willard.UUCP (Willard Dawson)
Willard's House BBS, Atlanta, GA -- +1 (404) 664 8814