discrepancy in ringback doc/code

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

Hi,

Russell King wrote:
> What happens? Person A's phone rings within possibly as little as 10
> seconds of the first call. If it happens to have an mgetty with ringback
> on the line, it'll incorrectly answer the second call.
> 
> I don't think that the current mgetty behaviour is correct for this
> situation, and some improvement along the lines above would be most
> welcome to cover this situation if you wish to use this facility.
> 

Well, the current (!) mgetty behaviour is perfectly OK for that case -- as
it waits 17 seconds for RINGing to stop.

If I change it as proposed yesterday, it will fail in that case...

[..]
> Also, it isn't a good idea to specify a set number of rings - if you call
> though a PABX, then you simply can't tell how many rings the remote end
> will ring, since the clear-down time of the PABX is indeterminent.

My wording :)

> What I suggest is to keep the current behaviour and to allow the
> 17 seconds to be a configuration option. This will then allow you to
> specify all timeouts for ringback, and will minimise the changes to
> mgetty.

I think I'll do that, yes.

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
.