On Sun, 2008-01-06 at 01:07 -0600, Robert Citek wrote:
> Hello all,
>
> We're getting more and more people going the DSL route for Internet
> connectivity. What should our Standard Operating Procedure (SOP) be
> for dealing with AT&T's DSL? Connecting the computer isn't hard: plug
> one end of the ethernet cable into the modem and the other in the
> computer. However, registering on AT&T's website and then configuring
> the modem to deal with PPPoE has become a real pain and a real time
> drain.
>
> Today was just one example. Before the holidays another student had
> an issue with configuring the modem. It worked in the shop, but
> didn't work at home. That ticket is still unresolved.
>
> Anyone have any solutions? For example, should we charge to make
> house calls to configure DSL? Should we have folks bring in their
> entire setup and we use our DSL line to configure their system?
> Something else?
If AT&T does the install for a customer, they charge $150-$200 for the
service call. I think that cost would effectively put the service out
of the price range for most of our students and their families.
That being said, the amount of time Robert spent on getting a used modem
with no documentation configured, IMHO, should have been charged for,
not free.
One thing Doc pointed out is that our instructions on the wiki
(installing/configuring AT&T DSL under Debian) are hard to find.
A bigger question is, where would we find the volunteer resources to
make house calls to configure DSL?
If a student brings in their entire setup, *can* we use our DSL line to
configure everything? Or are there settings that must be done at the
line where the service is to be provided?
One possible (partial) solution -- have a DSL Demo on Week 7, or after
graduation on Week 6. Have printed handouts ready to go home with any
student going for the DSL option.
Just my two-bits.
t.
--
*** Propositions arrived at purely by logical
means are completely empty as regards
reality. - Albert Einstein ***
