discrepancy in ringback doc/code

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

Paul Fox wrote:
> > the mgetty man page says:
> >  -R <t> Tells mgetty to go into "ringback" (aka "ring-
> >   twice") mode. That means: the first call is never
> >   answered, instead the caller has to hang up after
> >   the phone RINGs, wait 30 seconds, and then call
> >   again in the next <t> seconds for mgetty to pick
> >   up. If no call comes, mgetty will exit.
> 
> in addition to the timeout discrepancy (30 vs 17 in the code) i just noted,
> i'm wondering why there is an extra timeout value at all? why not just
> wait <t> seconds after the last RING is noted? 

How do you know that it was the *last* RING? This is what the 17 seconds
are for -- make sure that you know that the other end has hung up.

> as a potential user of
> this feature, it seems complicated to have to call back quickly, but not
> _too_ quickly.

This is done on purpose, to avoid false alerts if you get "normal" calls
on that line as well.

gert

-- 
USENET is *not* the non-clickable part of WWW!
           //www.muc.de/~gert/
Gert Doering - Munich, Germany      gert@greenie.muc.de
fax: +49-89-3545980     gert.doering@physik.tu-muenchen.de
.