Terebinthia wrote on Sep 14
th, 2014 at 10:41am:
So, I've worked out how to access my ADSL stats:
Line state Connected
Connection time 3 days, 18:10:37
Downstream 1,280 Kbps
Upstream 448 Kbps
ADSL settings
VPI/VCI 0/38
Type PPPoA
Modulation ITU-T G.992.1
Latency type Interleaved
Noise margin (Down/Up) 6.4 dB / 11.0 dB
Line attenuation (Down/Up) 63.5 dB / 31.5 dB
Output power (Down/Up) 16.2 dBm / 12.3 dBm
Loss of Framing (Local) 0
Loss of Signal (Local) 0
Loss of Power (Local) 0
FEC Errors (Down/Up) 624473 / 480
CRC Errors (Down/Up) 7128 / N/A
HEC Errors (Down/Up) N/A / 236
Error Seconds (Local) 5316
And read up a little bit on Line attenuation - and the kitz tool at
http://www.kitz.co.uk/adsl/max_speed_calc.php gives an approximate line length of 4.6 kn when the actual distance to the exchange as double-checked is 7.9. So, that suggests the physical phone lines aren't in too bad condition, am I right?
I suppose I need to gird my loins and talk to the Hell Desk, but am not looking forward to it, as they basically will try to fob me off. Hate BT customer support
Yup, they don't look that bad... 8 klicks for 1Mb down is actually quite good. 63dB is in line with 1Mb bandwidth, so there's nothing strange here.
( it's not in like with 8 klicks though... 8 klicks shoud be in the 70/80 dB attenuation, so the physical line is quite nice, probably something relatively new, laid to dispose of the DACS box. ) FEC errors don't matter since your line is in interleaved setting.
I'm surprised by the PPPoA ( that's point to point protocol over ATM ) since it's a mostly deprecated system most DSLAMs nowadays uses PPPoE ( that's the same
over Ethernet ), so you're probably connected to a first generation DSLAM, which might explain why it has issues with it's backend link. ( depending on the technology [ Ericsson, Alcatel, Nortel, Siemens, ... ] the uplink after the DSLAM might be limited to one to four 2Mb links... for 128 Subscribers )
Hell Desk Drone will probably be unable to help you... if they are like here... I usually end up talking to supervisors as the drones have no clue beyond following the page on their screen... At lesat supervisors listen when I tell them that DNS server at IP X.Y.Z.A stopped answering queries, or that the RADIUS server W.X.Y.Z is down... and they check the thing. ( while the drone keeps telling me to restart my box ( despite the fact that I told him/her 4 times that I do not have a box, but that I have a router with full control over it ).
At least you might be able to get them to check the DSLAM health and see if there's anything wrong there.