Telkom ADSL problem

[seriousrash]

Right where should i start....

*the dumber than dirt techies
*the poor service!

k this is my problem ever since the 6th of April iv had a constant latency of 170 to all local servers, i have swapped out all the variables so i know its the line. I first reported it online after about a week of struggling with the SO CALLED online adsl fault reporting ,i called there adsl support 0800 DSL DSL after about 45min of holding on, i logged the fault.
A week later the adsl techies "laurel and hardy" show up... believe me the names suit! OMF dumber than dirt , u try explain what latency is to a 2 year old.

They came to the conclusion that since theres an adsl signal theres nothing wrong with the line ,after seeing how pissed off i was the one tells me to call the " adsl support" again and get them to run a line test ..so i did and WTF the lady on phone says YES MR **** seems theres an analog fault on the line we will send out a technician. But there were two technicians at my house at that exact moment who cant/wont fix it cause they are "ADSL TECHNICIANS" and not normal telkom techies what ever that means!

To my surprise he showed up today.. asked me what the problem was so i tried to explain to him ,who seemed only slightly smarter than those other two. After telling him i basically only use it for ADSL he says : WELL WHATS THE PROBLEM THEN, YOU DONT NEED THE ANALOG PART ANYWAYS! Seeing the look in my face i guess he tried to seem abit interested and he tested the line with his little machine and said "the ADSL SUPPORT dont know WTF they talking about theres nothing wrong with the line" and left!

WTF DO I DO NOW TO GET THIS **** SORTED!???


Pinging www.myadsl.co.za [196.40.97.13] with 32 bytes of data:

Reply from 196.40.97.13: bytes=32 time=151ms TTL=245
Reply from 196.40.97.13: bytes=32 time=151ms TTL=245
Reply from 196.40.97.13: bytes=32 time=152ms TTL=245
Reply from 196.40.97.13: bytes=32 time=153ms TTL=245

Ping statistics for 196.40.97.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 151ms, Maximum = 153ms, Average = 151ms

Tracing route to 196.4.97.13 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 196.211.*.**
2 131 ms 130 ms 161 ms 196.211.***.**
3 129 ms 130 ms 130 ms cdsl1-rba-gi1-0-44.ip.isnet.net [196.36.80.209]

4 134 ms 131 ms 130 ms core1a-rba-gi0-2.ip.isnet.net [168.209.1.141]
5 130 ms 130 ms 151 ms 196.26.0.211
6 135 ms 142 ms 129 ms 196.23.136.35
7 130 ms 130 ms 132 ms ch3-rba-fa0-0.ip.isnet.net [196.26.0.88]
8 138 ms 136 ms 137 ms ch3-rba-se4-4-50-cpe.ip.isnet.net [168.209.86.82
]
9 * * * Request timed out.
10 * * * Request timed out.


*Sorry if i sound abit straight forward

 

[cavedog]

Im really sorry dude. But honestly you wont get it fixed. I had a similar problem but never got it sorted. it sorted it self after like 3 months. You cant say anything to telkom every thing you say just turns a blank stair in the tech's face.

 

[Leftfoot]

If ADSL support say theres a fault on the line ask "what type of faults is it?" Is it an EARTH, FOREIGN CONTACT, OR LOW INSULATION. In most cases the tech that comes out to work on this fault cant test it acurately without testing in tandem with the test desk. They use a system called LTS and there are very specific parameters for a "clear" line (technically called a condenser and clear condition). Chq out this post where I have mentioned some of the parameters.

http://mybroadband.co.za/vb/showthread.php?p=1648363#post1648363

Lazy faultsman listen if the line is working and move on......ask what faults condtions are found and for the detailed test result breakdown then you will know if its clear or not.