Pair has been swapped, lift and shift also done.

It's going to be one of those odd ones, remote interference or some such.

In reply to a post by Zarjaz:

The lift and shift the OP says has been done should rule that out.

Ah, ok, I thought the lift and shift was just the cables from home to the cabinet and maybe from the cabinet to the exchange, I wasn't sure if that also included the line card in the exchange.

If that's all been done and hasn't fixed it and they are the only one on his trunk of cables then it would possibly point to something in their building, unless there is a noise source someplace between the exchange and their address, I am no BT Engineer but twisted pairs (balanced line) should reduce that interference.

Paul

In reply to a post by PaulKirby:

In reply to a post by Zarjaz:

The lift and shift the OP says has been done should rule that out.

Ah, ok, I thought the lift and shift was just the cables from home to the cabinet and maybe from the cabinet to the exchange, I wasn't sure if that also included the line card in the exchange.

If that's all been done and hasn't fixed it and they are the only one on his trunk of cables then it would possibly point to something in their building, unless there is a noise source someplace between the exchange and their address, I am no BT Engineer but twisted pairs (balanced line) should reduce that interference.

Paul

For the FTTC the E side wouldn't be of relevance as it isn't actually needed for the vdsl to function normally , but isp's rely on a working E side to run their remote tests

In reply to a post by tommy45:

For the FTTC the E side wouldn't be of relevance as it isn't actually needed for the vdsl to function normally , but isp's rely on a working E side to run their remote tests

Ah, that will teach me from not reading the whole thread

Paul

Ah, that will teach me from not reading the whole thread

Or possibly the title of this section of the forum ?

In reply to a post by Zarjaz:

Ah, that will teach me from not reading the whole thread

Or possibly the title of this section of the forum ?

Well you can never go by that, ADSL stuff always seems to pop up in this section .

Paul

You're lucky not to get billed for those nine engineers' visits. Openreach can charge, and often does charge £130 for each call-out where "no fault found". Since they haven't charged you (or have they?) they presumably recognise there's a fault, even if they can't isolate it, or rectify it. Poor show.

We're in the same boat with an intermittent line fault. But we're leaving it to get much worse, until it hopefully fails altogether on both voice and broadband. That way Openreach can't deny the fault's existence, and bill us for calling them out. Don't let Openreach turn a fault into a cash cow.

Ours is a high-resistance joint somewhere, probably at the pole distribution point, where the line is most exposed to the elements. The CRCs tend to soar in bad weather, when gusts of wind cause the drop-wire to lash about, causing repeated loss of broadband service. When the weather is bad, there's also an audible crackle and a clear 'uptick' in attenuation on resync, as the HR joint takes its toll on the broadband signal.

Since you've had nine engineers visit now, all without merit, maybe it's time to diagnose the fault yourself?

Pinpointing a failure point is usually done using the time-domain reflectometry (TDR) function of the JDSU. Since the engineers can't even give you an accurate estimate of your line length - variously guessing at 700 to 800 metres - it sounds like they don't know how to use TDR properly. Which doesn't bode well as both loop-length estimation and fault location are based on time-domain reflectometry.

Maybe it would be quicker, in the long run, to borrow or hire a time-domain reflectometer to locate the problem yourself? The impedance mismatch of a HR joint will cause a clear and visible reflection in the TDR signal, showing on the screen plot. That's how a well-trained engineer should be able to pinpoint an HR fault within minutes, and to an accuracy of a metre or so.

Good luck arobertson545. With Openreach on the job, you'll need it!

Can't be a line card fault if they're on FTTC

In reply to a post by edwincluck:

Maybe it would be quicker, in the long run, to borrow or hire a time-domain reflectometer to locate the problem yourself? The impedance mismatch of a HR joint will cause a clear and visible reflection in the TDR signal, showing on the screen plot. That's how a well-trained engineer should be able to pinpoint an HR fault within minutes, and to an accuracy of a metre or so.

Good luck arobertson545. With Openreach on the job, you'll need it!

One of the first thing Openreach engineers are taught when they go onto faults is how to read a TDR, they all know how to do it. Broadband trained engineers have this reinforced and then obviously are taught how to read all the other tests on their Exfos or JDSUs.

Edited by deleted (Thu 01-Oct-15 20:08:34)

He already has a JDSU. How does that help exactly?

In reply to a post by Icaras:

Can't be a line card fault if they're on FTTC

Like I said I should of read the whole thread before replying, heh.

Paul