----- Original Message -----
From: "Jim" <mlist@budget.co.nz>
To: <adsl@unixathome.org>
Sent: Thursday, March 01, 2001 5:11 PM
Subject: Re: Re: HUGE WARNING ON JETSTREAM BILLING!

> > 3. It is possible for a ISP to 'push' the limit attribute into your
> > database. currently correct - will be plugged in the near future
>
> *COUGH* So in theory an ISP could set the limit up higher than 128, if
you'd
> told them how to, but you haven't, and won't? Or is the limit attribute a
> logical yes/no type value?

The token in question, "RedbackRateLimit = 128" could be passed to Telecom's
RAN by the ISP, however Telecom has more credit than you give them brains
for and drops/ignore's this token from ISP's.

After all, they'd have to be insane to allow ISP's who are using Telecom's
bandwidth to provide jetstart access to this token - or else I'd be sitting
on my flat rate 8.6Mbit/s jetstart right now :)

>
> > 4. The limit attribute can only be changed when a update runs on the
> > database at 4 in the morning. correct (for now)
>
> Did you have Microsoft custom build this database?
> "Listen Bill, your SQL server just isn't, to be blunt, fucked up enough
for
> us. Think you can work on something a little more... twisted?"
>
>
> > 5. If the rate is NOT capped when you have JetStart, it is the ISP's
> > fault because it's their job to 'push' this information into Telecom's
> > database. in-correct - may be the ISP's fault for pushing back (or ours
> > for accepting the attribute) but there are other possibilities (faults)
>
> I'd say it can't be the ISP's fault if you haven't told them about this
> feature (based on comment from Voyager employee on list).

<snip useless footers>

--geoff/Nem

This message is part of the NZ ADSL mailing list.
see http://unixathome.org/adsl/ for archives, FAQ,
and various documents.
To unsubscribe: send mail to majordomo@unixathome.org
with "unsubscribe adsl" in the body of the message
Received on Thu Mar 1 20:38:00 2001