> 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?

> 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).

-----------------------------------------------
This message is confidential. If you are not the intended recipient you must not read or do anything else with this message.
If you have received this message in error please notify us immediately by return email and destroy this email. Thank you.

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 17:10:48 2001