I am only 7 months into an 18 month contract, with cessation charges if I changed ISP.
IMO, connection problems really rest with BT though, as they are resposible for the infrastructure.
My ISP has been quite supportive, organising numerous engineer visits whenever I have been able to prove
further faults etc.
BT just won't respond though if a connection "appears" stable & it exceeds their own conservative speed estimates, falling within their "acceptable" performance limits.
Faults are all so much harder to prove with ISPs not having access to full diagnosis tools for VDSL2 connections & users having to use "locked" modems with no "official" means of monitoring their own connection statistics etc.
I have an unlocked HG612 modem & have developed Windows versions of the linux scripts & tools to monitor ALL
my connection's stats, either on demand whenever I wish to generate snapshot stats/graphs and my ongoing/changing stats 24/7 via data logs that are harvested every minute (a little like RouterStats).
It is only being able to provide these stats/graphs that has enabled my ISP to keep pushing BT to rectify the faults (a bit at a time) on my connection.
The tools currently available to ISPs simply do not record most of our connection re-syncs, changes in SNRM levels, excessive corrected & uncorrected error counts, connection time between re-syncs at varying speeds etc. as these type of re-syncs are so quick from disconnection to reconnection (less than 20 seconds) & don't drop the PPP session or change the dynamically allocated IP address.
ISPs can/do blissfully & genuinely believe that connections are perfectly stable, when in reality the complete opposite may be the case.
If anyone wishes to try out the Windows only versions of the scripts I mentioned above, they can be downloaded via this link:-
Huawei HG612 graphing scripts
graph.sh is the Linux version that can also be used via a Linux scripting shell such as Cygwin on a Windows machine.
The Windows only version is hg612_wingraphs.zip (no need to install any Linux shells).
Prior to downloading or using the Windows versions I advise reading the summary of what the scripts actually do (hg612_wingraphs_SUMMARY.TXT).
The Windows only scripts have been fully tested on Windows 7 & Vista machines, & will probably work (a bit slower) on XP machines.
A tiny edit of one batch file is required to ensure that fonts are displayed at the correct style/size for Vista (& presumably XP).
If anyone tries these out, I would appreciate some feedback on the setting up process & general use of them.
It would also be good to see a few example graphs, for different connection comparison purposes
Full setting up instructions & links to various other required program downloads are included in the zip file.
Once set up, a simple double-click on the relevant batch file icon will generate the graphs from the ongoing log or harvest current stats & generate the snapshot graphs, storing the output in dated subfolders for future reference.
There is also an easy method of generating graphs from previous log files (preferably but not essentially PuTTy.log), although some of the graphs/text data will be absent if not all the relevant data was included in the previous log file.
Due to how the Windows scripts operate, there is no longer a requirement to manually login to a Telnet session, or the modem itself.
Snapshot Example Graphs
Ongoing Example Graphs
Edited by Bald_Eagle1 (Wed 18-Jan-12 08:53:50)