On Fri, 16 Apr 1999 11:07:27 +0200, hai scritto:
>connecting procedure is about 30 sec, but when speed is degraded to 216000,
>connecting procedure is almost 1 minute.
>
> OK, in our country is this tarif (first impulse is added (and payed)
>when my modem call's to on IPS, not when this two modems are correcty
So in Italy.
>connected etc..:-() (Yes, 1 impulse is added (and payed), when this two
>modems don't connect together corectly:-():
>Work day (monday - friday) 7:00 - 19:00, impulse by 2 minutes ,
>Work day (monday - friday) 19:00 - 7:00, impulse by 4 minutes
>Weekend days (sunday, saturday) all 24 hours impulse by 4 minutes...
>
> Yes, we don't have cheap life..;-)
Well, it depends on how much you are billed for an impulse :-)
>restrict 7:00:00 19:00:00 * * *
>impulse 60,120,30
>restrict 19:00:00 * * * *
>or-restrict * * 0 * *
>or-restrict * * 6 * *
>impulse 180,240,30
I don't think the 3 args to impulse are right for your situation.
In order to make diald to count for the initial seconds (connection time) you
can upgrade to diald 0.98.x
- Call duration is now measured from the moment we try and start
the link rather than when the link actually becomes up for
network traffic. This makes more sense because chargable
duration is from the moment the physical layer (modem etc.)
is connected and not from when the network layer is connected.
For the impulse rules.
When a slot lasts 3min40sec=220sec I use:
impulse 180,40
but I could even use
impulse 190,30
I understand that the sum of the 2 arguments is to be equal to the time your
telephone company gives you for an impulse.
Diald stays up for 180 and in the last seconds of the impulse (220 -180 = 40)
is allowed to bring the link down.
Ciao.
--
Giulio
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
