Re: Expire date

Josh Hillman ( (no email) )
Wed, 14 May 1997 10:49:00 -0400

Mark,
I don't work for IEA or anything, but what problem or problems are you
running into when it comes to billing? The MBR's Extend and Limit
fields/values have nothing to do with billing. They just simply allow the
customer to still access his/her services for the specified number of days
past their expiration date. The billing is based on that expiration date,
payperiod, charges, etc. While the Extend (one-time extension) or the
Limit (permanent grace-period) may be used, they have no effect on billing
cycles or the invoice's "Due Date" (MasterAccounts.MaExpireDate).

I, too would like to use the Limit field as a grace period, but have to
wait until the new version of RadiusNT comes out (and Emerald as far as
putting the number in there automatically is concerned), but I've been
handling billing with no problems at all for quite a few months. Right
now, I'm using Emerald 2.1.11 and RadiusNT .60.

Until the new version of Emerald comes out, that automatically reads in the
Limit value properly, you can run the following script to update any
EXISTING MBRs:

update MasterAccounts
set OverDue = 7
where OverDue = 0
and Active = 1

Of course you can modify it as necessary, but that's what I did when
testing Radius .90 (which I can't use, due to an unrelated problem). The
above script worked just fine.

Josh Hillman
hillman@talstar.com

----------
> From: Marc Elbirt <marc@cpol.com>
> To: emerald@emerald.iea.com
> Subject: Re: Expire date
> Date: Wednesday, May 14, 1997 10:18 AM
>
> I think everyone on this list has been waiting for the ability to perform
> billing from Day 1. It is not satisfactory that we are required to do
this
> manually. There is too much room for error. We need a fix for this
> problem NOW. I don't care what version you call it. Just take the code
> for 2.1.8 or 2.1.11, fix the "bug where the extend was not being read
from
> the DB" and call it 2.1.8.1. I paid for this feature six months ago.
>
> On Sun, 4 May 1997, Dale E. Reed Jr. wrote:
> > 2.1.11 had a bug where the extend was not being read from the DB, and
so
> > the default extend was always 0. The admin was fine. The next version
> > will fix this.
>
> Dale, as far as everybody but you is concerned, 2.1.11 STILL HAS a bug.
I
> can't wait for the next version, for christ's sake. For the last time,
> get the hint: We need software that works.
>
>
> ------------------------------------------------------------------------
> Marc Elbirt Computer Pages Inc.
> Systems Administrator 253 Sheppard Ave. West
> marc@cpol.com Toronto, Canada M2N 1N2
> WWW - http://www.cpol.com Ph: +1 416 225 3030 Fax: +1 416 225 6737
>
> ----------------------------------------------------------
> Emerald Mailing List listserver@emerald.iea.com