ok the way to deal with this is like this assuming your test results are reliably repeatable..

Report voice not bb fault.

Part of their diagnosis is doing a quiet line test.

When they start a test, ring one of those 25 properties from your mobile.

If the ringing is audible and the engineer then walks claiming no fault to fix, they breached contract.

Okey doke, had 2 vans and a cherry picker here all day yesterday.

So they started off swapping pairs on the main road UG run (5.8km ish) and managed to turn 2700kbps into 3500kbps at that point. However after that there is a further 1.5km of bundled pairs up a side road, then 400m from the junction into the property.

Anyway, after switching pairs on the main road to get 3500 they came to test at the house, but the speed here had not improved (JDSU syncing just under 1000). they then decided to swap the 400m of two pair (I think?) into the property. this improved things a lot and the homehub then synced at 1400kbps.

now 24 hours on the SNR has started to drift down again and the usability of the internet is getting worse.

Stats after 24 hours:
Connection Information

Line state: Connected
Connection time: 1 days, 00:00:29
Downstream: 1.406 Mbps
Upstream: 448 Kbps

ADSL Settings

VPI/VCI: 0/38
Type: PPPoA
Modulation: G.992.1 Annex A
Latency type: Interleaved
Noise margin (Down/Up): 5.3 dB / 13.0 dB
Line attenuation (Down/Up): 70.9 dB / 31.5 dB
Output power (Down/Up): 16.7 dBm / 12.4 dBm
FEC Events (Down/Up): 86840064 / 56084
CRC Events (Down/Up): 4197 / 622
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
HEC Events (Down/Up): 26942 / 411
Error Seconds (Local/Remote): 1821 / 323

IP profile still at 0.75, and I don't really want to reconnect just now, but I will if you think I should to show fresh line stats.

Tried the ringing pulse noise thing, but it is pretty faint now, and they guy said it was likely just induction.

Any thoughts welcome. Thanks, JF.

I seem to remember posts about marginal performance being improved by getting interleaving switched off (by the ISP). Something about fewer bad packets at the expense of higher latency. I'm no expert so what do others think?

Turning off interleaving is likely to make the line very unstable (and would reduce latency rather than increase). It is interleaving that normally helps a long line.

yep that CRC/FEC count he has, bad idea to turn of interleaving without a massive snrm bump The low sync doesnt give much room for a snrm bump either.

Thinking about it, the guy who was advised to switch it off had a rock-solid connection and wanted lower latency for gaming so, yes, not recommended in this instance. Thanks.

Some observations:

A) The downstream power is a bit low (17 dBm rather than 20 dBm). The extra 3 dB are desperately needed. But this may be beyond your control.
B) Replacing the wire improved the attenuation by 3 dB, which improved your line from 1 to 1.4 Mbps, with reduced error seconds. A decent step. Did they replace 0.4 mm wire by 0.5 mm wire?
C) Noise can vary throughout time. Try to resink when the noise is bad. The bandwidth will be lower, but you will get less errors. Alternatively try to change the snr margin settings from 6 db to 8 db or so, if you can.
D) At this snr margin level you should not get so many errors. Could be a modem issue.

Edited by deleted (Sat 27-Sep-14 07:28:24)

OK, so I went out and got a hold of a 2700HGV modem to try out, and the speed is fantastic! synced at 1888 with a noise margin of 6db on Friday, and errors much lower than the homehub. Also where the homehub needed reset every 12hours or so, the business hub just keeps chugging away!

I also downloaded linestats to run on the pc for a few days to keep track of things...

STarted off Friday afternoon 1888 and 6db, then on Sunday at 0715 it jumped to 1400 and 10db. Now, during the 1888 running it had a total of 9 tiny dropouts, but was generally pretty solid although I am now considering that there may have been other dropouts but linestats didnt pick them up. anyway, as of 0720 Tuesday morning its dropped again to 1184 and 12db! Not sure where to go from here, errors are no better than when it was at 1888.

A) How do I get the extra 3db?
B) Not sure, but sound like that could be right.

The Chairmans office are really keen to close this fault and give us £50 to go away, but I put her off till Thursday to see how it goes.

Thanks, JF.

EDIT: Router Stats

Since Reset Current 24-Hour Interval Current 15-Minute Interval Time Since Last Event
ATM Cell Header Errors: 12414 12414 9 0:00:08
ATM Loss of Cell Delineation: 1841 1841 3 0:00:08
DSL Link Retrains: 1 1 0 2:52:42
DSL Training Errors: 0 0 0 0:00:00
DSL Training Timeouts: 0 0 0 0:00:00
DSL Loss of Framing Failures: 2 2 0 2:52:42
DSL Loss of Signal Failures: 2 2 0 2:52:42
DSL Loss of Power Failures: 0 0 0 0:00:00
DSL Loss of Margin Failures: 2 2 0 2:52:42
DSL Cumulative Errored Seconds: 4604 4604 5 0:00:08
DSL Severely Errored Seconds: 159 159 0 0:47:07
DSL Corrected Blocks: 159605 159605 406 0:00:01
DSL Uncorrected Blocks: 15049 15049 9 0:00:08
ISP Connection Establishment: 2 2 2 12:00:25

Edited by deleted (Tue 07-Oct-14 10:18:28)

You probably need to set your linestats sampling interval to 5 or 7 seconds, the minimum such tools normally have, rather than the default.

That usually lets you see the margin degrade rather than just drop out, and I always found that more useful.

Also getting it to save the graphs (give those a nice short timespan as well so the graph gives more detail) and a CSV file are good ideas.

(Edit - the light suddenly dawned as to where your nick comes from! It has been worrying me for a while, as I recognised it but couldn't place it).

Edited by RobertoS (Tue 07-Oct-14 14:29:26)