Thought I would relay my last 2 weeks of "fun" having my dry loop DSL connected.
I had home phone and DSL service with SNET/SBC now ATT for 10 years. Service was flawless @ 6Mbs. I decided to transfer my home phone # to cell service (Verizon) Two weeks ago my DSL service was terminated as part of the home phone transfer. I called to have "dry loop" service install. After I was told it was installed, it did not work. I spent about 2 hours on tech support stepping thru their checklists even tho I knew it was not my setup. I was told the standard "we don't support linux or linksys routers" even tho having hooked up my work laptop to create a broadband connection, all they had me do was to create a PPPoe connection (the same thing linux or a linksys would do. I also inform them that I am talking to tech support on the phone line THEY WERE SUPPOSED TO DISABLE.
After all this work, I was informed I had not enabled my new account (which requires the web). So I drive down to the library and use their open Wifi to enable my account.
Still nothing works, except the phone line they hadn't disconnected. Another hour and I'm told I am supposed to remove the DSL filters that were installed as part of the old installation. Filters removed, nothing works, except the phone they were supposed to disconnect.
Finally I get transferred to Tier 2 support and a nice lady in Dallas says "definitely a wiring issue" and tells me to call back to schedule a on site tech. I was leaving the state the next day so I let it slide.
Call back when I got back in state and no one will transfer me to Tier 2. Insisting they can solve 99% of connection issues @ tier 1. At this point I am sorry I even transferred my service. I also inform them I am talking to them on the line they were supposed to disconnect. I calmly inform the help desk person and his supervisor that I would not be going thru the checklist of connection steps. e.g. What OS, what modem etc. etc. etc. That I was still talking to them on the phone line I wasn't supposed to have. "This stuff all worked for 10 years, it isn't the house wiring, the computer, the ethernet (aka the "yellow" cable), the modem, the OS, the striped shirt(ok I am exaggerating)" It all worked until they tried to convert my service and then nothing.
Over to tier 2 and they schedule a on site person, ok, i will diverge here to point out that now AT&T answers the help desk with "This is Manny in San Francisco or This is Annabelle in Little Rock" The HD translation is "you are not talking to a guy in India" The guy shows up and after 10 minutes of checking stuff figures out no one actually moved any cables back @ the CO; this is why my phone still worked and DSL didn't. He apologizes and says "this really isn't good for the customer" 10 minutes later DSL is working
I plan to put in a good word for him since he was cordial and apologetic. I don't really blame any Tier 1 people, I guess the moral is to document each call and the steps you have already done. Also have a case # assigned to constantly refer to it. I work in IT so I should know this. But sometimes the littlest things turn into monstrosities and the wisdom to document the issue arrives too late.
-T
I had home phone and DSL service with SNET/SBC now ATT for 10 years. Service was flawless @ 6Mbs. I decided to transfer my home phone # to cell service (Verizon) Two weeks ago my DSL service was terminated as part of the home phone transfer. I called to have "dry loop" service install. After I was told it was installed, it did not work. I spent about 2 hours on tech support stepping thru their checklists even tho I knew it was not my setup. I was told the standard "we don't support linux or linksys routers" even tho having hooked up my work laptop to create a broadband connection, all they had me do was to create a PPPoe connection (the same thing linux or a linksys would do. I also inform them that I am talking to tech support on the phone line THEY WERE SUPPOSED TO DISABLE.
After all this work, I was informed I had not enabled my new account (which requires the web). So I drive down to the library and use their open Wifi to enable my account.
Still nothing works, except the phone line they hadn't disconnected. Another hour and I'm told I am supposed to remove the DSL filters that were installed as part of the old installation. Filters removed, nothing works, except the phone they were supposed to disconnect.
Finally I get transferred to Tier 2 support and a nice lady in Dallas says "definitely a wiring issue" and tells me to call back to schedule a on site tech. I was leaving the state the next day so I let it slide.
Call back when I got back in state and no one will transfer me to Tier 2. Insisting they can solve 99% of connection issues @ tier 1. At this point I am sorry I even transferred my service. I also inform them I am talking to them on the line they were supposed to disconnect. I calmly inform the help desk person and his supervisor that I would not be going thru the checklist of connection steps. e.g. What OS, what modem etc. etc. etc. That I was still talking to them on the phone line I wasn't supposed to have. "This stuff all worked for 10 years, it isn't the house wiring, the computer, the ethernet (aka the "yellow" cable), the modem, the OS, the striped shirt(ok I am exaggerating)" It all worked until they tried to convert my service and then nothing.
Over to tier 2 and they schedule a on site person, ok, i will diverge here to point out that now AT&T answers the help desk with "This is Manny in San Francisco or This is Annabelle in Little Rock" The HD translation is "you are not talking to a guy in India" The guy shows up and after 10 minutes of checking stuff figures out no one actually moved any cables back @ the CO; this is why my phone still worked and DSL didn't. He apologizes and says "this really isn't good for the customer" 10 minutes later DSL is working
I plan to put in a good word for him since he was cordial and apologetic. I don't really blame any Tier 1 people, I guess the moral is to document each call and the steps you have already done. Also have a case # assigned to constantly refer to it. I work in IT so I should know this. But sometimes the littlest things turn into monstrosities and the wisdom to document the issue arrives too late.
-T
Last edited: