I was interested to see the topic, as I noticed a number of recent disconnections (ticket 86089411) and rang an hour or two after one happened yesterday lunchtime (I was out of the house at the time, and most of my computer gear was off).
Spoke to someone in Tech Support who did some line test, then said he was going to get interleaving enabled on the line and it would take up to 48 hours for it to happen and then may take a while more for the line to settle down.
Had an e-mail which I only glanced at today (I had been busy for some 30 hours solid on a job and only made the phone call after returning home, and then slept for a good while). E-mail suggests I was questioning speed whereas I was specific about disconnections and the chap had looked and said that yes, there had been a number of disconnections in previous 7 days (without being very specific as to number - ie I have no idea whether it was once or twice a day, or more often... I had noticed several instances of things being sluggish - put it down to my iMac being overworked with 100-150 tabs open at once!)
Anyway, seeing the thread, just got some stats off the Thomson TG585 v7 (incidentally, is there some easy way to get line stats - I went into the Telnet interface as the browser UI didn't seem to display much useful detail, but then again, I was up from 0300 today and might have overlooked an option or 'link'....
I've copied an extract, to give similar info to that from swervinc
{xxxxxx}=> xdsl info expand=enabled
Physical Layer Statistics:
Modem state: . . . . . . . up
Up time (Days hh:mm:ss): 0 days, 10:17:30
xDSL Standard: . . . . . . . ITU-T G.992.5
xDSL Annex: . . . . . . . Annex A
Number of reset: 46
Bearers generic info . . . . . . . DS US
Payload rate [kbps]: . . . . 11479 1091
Attenuation [dB]: . . . . . . . 33.5 17.5
Margins [dB]: . . . . . . . . . . 3.5 6.5
Output power [dBm]: . . . . 0.0 12.0
G.997.1 Statistics (Current):
Failures:
Line failures Near end
Loss of signal (LOS): 95
Loss of frame (LOF): 55
Loss of power (LPR): 0
Performance monitoring:
Line PM: Near end
Error second (ES): 2038
Channel PM: Near end Far end
Bearer 0:
Code Violation (CV): 1944
FEC: 0
ATM data path PM: Near end Far end
Bearer 0:
HEC violation count (HEC): 936 0
Would appreciate any comments...
In particular, (a) whether it was a 'standard explanation' used in the e-mail response (ie if interleaving to be enabled, then report as if customer complained of speed problems), and (b) whether this has any similarities concerning the S/N margin