discrepancy in ringback doc/code

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

 > 
 > This is exactly the 17 seconds timeout. You *need* more than just 6
 > seconds to handle countries where RINGs can sometimes be up to 
 > 12-14 seconds apart.
 > 
 > > and anyway you could just tell mgetty
 > > to go into ringback mode when it receives say 3 rings (RINGS = 3) 
 > 
 > How do you know that it has rung *three* times on the receiving end? With
 > modern digitized telephone systems, RING on the receiving side and
 > the "ringing" sound on the dialing side are completely asynchronous -- so
 > when you hear three sounds, it's well possible that mgetty has only seen
 > two RINGs, or already four.

okay, as the original questioner, i now understand the design, and why
it works. :-)

so now the only suggestion is still with the docs -- i think the man page
should say 17 seconds, since the 17 is clearly manifested in the log files.
and it's important for the user to know exactly what that time is: for
instance, if i use -R 30, that 13 second discripenacy can chew up almost
half of the time i've allowed myself for calling back.

perhaps both timeouts should be specifiable, e.g. -R NN.MM, where NN is
the time after which the RING's are assumed stopped, and MM is the time
during which a call will subsequently be answered. or, maybe the initial
"no RING" timeout could be computed from the RING arrival interval? i
can imagine some RING patterns that might make that hard, though.

but i'm happy now that i understand the system. (as for getting a voice
capable modem, that's probably in the longer-term plans, but its a little
hard to justify a new modem simply for backup purposes...

paul
---------------------
 paul fox, pgf@foxharp.boston.ma.us (arlington, ma)
.