Old Outdated Congested Exchange Dslam Ports That Need to Be Upgraded In My Area!

Item: Telkom
Rating: 1
Author: Eric L

Hi my issue is simple the service i have been receiving since the begining of this year has been a disgrace. I have logged mutiple faults on 10210 which has lead to nothing as the same technician is dispatched to our area.

He has put me on a different port mutiple times and changed my line and says that there is nothing he can do now. Even the operations manager is our area which we manage to contact sent out the same technician. The technician said a upgrade is needed.

Our exchange is severely broken software, share linked or congestion to the point where i get high ping locally and packet loss from 8 am to 23 pm 6 months now everyday.

This Exchange is still running Dslam ports upgrade it to imax or what ever is required to fix it. My neighbour and many other customers have the same issue in our area.

Impossible to do anything constructive with current service provided during those hours. I am competitive gamer and this is affecting me in a big way.

The exchange is name is Mpenjati, Postal Code 4275 Trafalgar , San lameer. 039 313 ****

Model Name: DSL-2750U Time and Date: Mon Jul 18 02:39:36 2011 Firmware Version: AF_1.73_T10 INTERNET INFO Internet Connection: Internet Connection Status: Connected Default Gateway: ppp0.1 Preferred DNS Server: 196.43.54.190 Alternate DNS Server: 196.43.53.190 Connection Up Time: 00 day,02 hour,38 min,47 sec Downstream Line Rate (Kbps): 2048 Upstream Line Rate (Kbps): 512

Enabled WAN Connections: VPI/VCI Service Name Protocol IGMP QoS IPv4 Address 8/35 pppoe_0_8_35_1 PPPoE Disabled Enable 105.227.188.225

Mode: ADSL_G.dmt Type: ATM Status: Up Downstream Upstream Line Coding(Trellis): On On SNR Margin (0.1dB): 148 130 Attenuation (0.1dB): 520 315 Output Power (0.1dBm): 161 121 Attainable Rate (Kbps): 4352 808 Rate (Kbps): 2048 512 D (interleaver depth): 1 1 Delay (msec): 0.13 0.25 HEC Errors: 0 0 OCD Errors: 0 0 LCD Errors: 0 0 Total ES: 0 0 ADSL BER TestReset Statistics

C:\WINDOWS\system32>ping 155.133.238.63 -t

Pinging 155.133.238.63 with 32 bytes of data: Request timed out. Reply from 155.133.238.63: bytes=32 time=790ms TTL=55 Reply from 155.133.238.63: bytes=32 time=738ms TTL=55 Reply from 155.133.238.63: bytes=32 time=847ms TTL=55 Reply from 155.133.238.63: bytes=32 time=1084ms TTL=55 Reply from 155.133.238.63: bytes=32 time=1032ms TTL=55 Request timed out. Request timed out. Reply from 155.133.238.63: bytes=32 time=986ms TTL=55 Reply from 155.133.238.63: bytes=32 time=891ms TTL=55 Request timed out. Reply from 155.133.238.63: bytes=32 time=774ms TTL=55 Reply from 155.133.238.63: bytes=32 time=1037ms TTL=55 Reply from 155.133.238.63: bytes=32 time=1059ms TTL=55 Reply from 155.133.238.63: bytes=32 time=835ms TTL=55 Reply from 155.133.238.63: bytes=32 time=944ms TTL=55 Reply from 155.133.238.63: bytes=32 time=1051ms TTL=55 Reply from 155.133.238.63: bytes=32 time=1073ms TTL=55

Ping statistics for 155.133.238.63: Packets: Sent = 18, Received = 14, Lost = 4 (22% loss), Approximate round trip times in milli-seconds: Minimum = 738ms, Maximum = 1084ms, Average = 938ms Control-C ^C C:\WINDOWS\system32>

C:\WINDOWS\system32>tracert 155.133.238.63

Tracing route to 155.133.238.63 over a maximum of 30 hops

1 10 ms <1 ms <1 ms 10.0.0.2 2 890 ms 926 ms 935 ms ndn-ip-esr-3.east.dsl.telkomsa.net [105.224.12.1] 3 780 ms 786 ms 902 ms ***.ti-sen.telkomsa.net [105.187.252. 69] 4 960 ms 1047 ms 933 ms ipc-1-up.east.dsl.telkomsa.net [105.229.0.22] 5 * 784 ms 556 ms cust-aggr-2.east.telkomsa.net [105.229.0.13] 6 916 ms 1011 ms 916 ms ***.ti-sen.telkomsa.net [105.187.252 .181] 7 789 ms 883 ms * ***.ti-sen.telkomsa.net [105.187.252. 98] 8 * 833 ms 779 ms 196-60-9-22.ixp.joburg [196.60.9.22] 9 790 ms 842 ms 999 ms 192.168.210.39 10 * 787 ms 847 ms 155.133.238.63

Trace complete.

C:\WINDOWS\system32>

Helpful (0)

Replies (1)

Eric L's updateReviewer Update

19 May 2018, 20:23

Hi, This reponse might be late because i was not expecting a reponse after waiting for a reply at least one week. Yes i am still having the same issue. I don't think this funny anymore. Im paying for a service that used ot work fine since 2013 until beginging of 2017 The exchange ATM Trunk /Congestion breaks every 2 months and i always have to message Terrick from mybroadband forums. At this moment the Atm Trunk/Congestion started again from 2018/05/04 from 18:30pm to 23:00pm. Because of this poor service for the past year and a half i have not been able to stay in a csgo team or other games due my internet service bieng unstable your company does not want to upgrade our exhange but no one even checks it frequently since every 2-3months ATM trunk/ Congestion Exchange breaks and high pings occur locally and internationally. Im depressed and frustrated of always having to contact you guys. Get a real technician and your network devision to fix this please and frequently monitor the exchange since the technician dispatch has no knowledge of what to do. C:\WINDOWS\system32>tracert 155.133.238.18 Tracing route to 155.133.238.18 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 10.0.0.2 2 * * * Request timed out. 3 468 ms 349 ms 404 ms ***.telkomsa.net [105.187.232.129] 4 480 ms 420 ms 473 ms ***.telkomsa.net [105.187.232.130] 5 510 ms 532 ms 501 ms cust-aggr-2.east.telkomsa.net [105.229.0.13] 6 317 ms 241 ms 201 ms ***.ti-sen.telkomsa.net [105.187.252 .181] 7 277 ms 340 ms 349 ms ***.ti-sen.telkomsa.net [105.187.252. 98] 8 434 ms 424 ms 340 ms 196-60-9-22.ixp.joburg [196.60.9.22] 9 507 ms 495 ms 497 ms 192.168.210.35 10 436 ms 312 ms 311 ms 155.133.238.18 Trace complete. C:\WINDOWS\system32>tracert 155.133.238.17 Tracing route to 155.133.238.17 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 10.0.0.2 2 * * * Request timed out. 3 374 ms 346 ms 355 ms ***.telkomsa.net [105.187.232.129] 4 331 ms 308 ms 276 ms ***.ti-sen.telkomsa.net [105.187.252. 70] 5 385 ms 406 ms 430 ms cust-aggr-2.east.telkomsa.net [105.229.0.13] 6 478 ms 466 ms 418 ms ***.ti-sen.telkomsa.net [105.187.252 .181] 7 470 ms 425 ms 442 ms ***.ti-sen.telkomsa.net [105.187.252. 98] 8 534 ms 523 ms * 196-60-9-22.ixp.joburg [196.60.9.22] 9 409 ms 446 ms 389 ms 192.168.210.35 10 368 ms 400 ms 497 ms 155.133.238.17 Trace complete. C:\WINDOWS\system32>tracert 155.133.238.11 Tracing route to 155.133.238.11 over a maximum of 30 hops 1 <1 ms <1 ms 1 ms 10.0.0.2 2 * * * Request timed out. 3 377 ms 395 ms 375 ms ***.telkomsa.net [105.187.232.129] 4 383 ms 370 ms 385 ms ***.telkomsa.net [105.187.232.130] 5 492 ms 548 ms 533 ms cust-aggr-2.east.telkomsa.net [105.229.0.13] 6 634 ms 618 ms 612 ms ***.ti-sen.telkomsa.net [105.187.252 .181] 7 453 ms 330 ms 328 ms ***.ti-sen.telkomsa.net [105.187.252. 98] 8 401 ms 424 ms 360 ms 196-60-9-22.ixp.joburg [196.60.9.22] 9 425 ms 437 ms 382 ms 192.168.210.35 10 566 ms 495 ms 448 ms 155.133.238.11 Trace complete. C:\WINDOWS\system32>tracert 155.133.238.53 Tracing route to 155.133.238.53 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 10.0.0.2 2 * * * Request timed out. 3 723 ms 678 ms 579 ms ***.telkomsa.net [105.187.232.129] 4 305 ms 331 ms 387 ms ***.ti-sen.telkomsa.net [105.187.252. 70] 5 461 ms 504 ms 329 ms cust-aggr-2.east.telkomsa.net [105.229.0.13] 6 291 ms 277 ms 285 ms ***.ti-sen.telkomsa.net [105.187.252 .181] 7 328 ms 359 ms 383 ms ***.ti-sen.telkomsa.net [105.187.252. 98] 8 559 ms 486 ms 337 ms 196-60-9-22.ixp.joburg [196.60.9.22] 9 359 ms 386 ms 481 ms 192.168.210.35 10 421 ms 418 ms 437 ms 155.133.238.53 Trace complete.

Eric L's update19 May 2018, 20:23

Reviewer Update