If it's been raised as a noise line fault, then don't expect a reset.

Line fault tasks don't provide the engineer with any informatiom about broadband connectivity.

Only if an engineer is booked specficially for a broadband fault, will they have the ability to reset DLM.

I told her I wanted both faults looked at and she said she's put it in the notes which I can view online so I'll check after work.

If not, I'll be back onto them as I'm fed up being fobbed off by them now. Don't care so much about the speed loss, it's more about the fact that I know it's capped but they insist it's not. I knew the fault was still there yesterday but they insisted it wasn't. I just want it sorted.

Edit: Just checked and they have updated the fault I reported that they cancelled the engineer for yesterday. It is a broadband fault so should be good - hopefully

Edited by WelshWArrior (Thu 13-Apr-17 14:20:35)

It still needs to be reported as a broadband fault, with a note about noise on the line, rather than as a noisy phone line fault with a note about broadband disconnections. Different people in Openreach are going to pick it up and assign their type of engineer.

The advice we gave for years about reporting a noisy line in order to get a broadband fault fixed quicker, (assuming there really was a noisy line), was never a guaranteed broadband fix. As has been frequently pointed out by more than one engineer on these forums. It simply worked in a high percentage of cases so was usually worth doing.

It also served the ancillary purpose that if there was no noise when the engineer tested, that no charge would be raised on "No fault found", unlike on a broadband "no fault found". That benefit went down the pan years ago when Openreach started charging for that on phone problems as well as broadband.

It did still work on ADSLx lines, but on FTTC is a dodgy approach. Particularly once banding has been applied! As you have found out a few times already with this fault.

With luck you may get the problem sorted. But luck is what it will be.

Edited by RobertoS (Thu 13-Apr-17 14:31:37)

The fault actually reads:

Reported Fault

Problem
Broadband - Slow Connection
Reference number
VOLXXX-XXXXXXXXXXXXX

So I'm hopeful!!

Stands a chance .

Time will tell I suppose but I hope so.

However, I best not hold my breath

Well the engineer has failed to turn up again - I'm fuming!

Been onto chat for 7th time since this saga began, to be told the engineer has been to my house this morning and marked the issue as fixed! I have been outside my house literally ALL morning fixing the car and at no point have BT been.

On top of this, she did another line test and confirmed the issue remains.

I'm really starting to lose confidence in BT as my ISP and will be writing a letter of complaint once it is finally resolved.

Also spoke to 4 of my neighbours this morning, specifically asking them about their broadband, to be told they are ALL having similar issues.

Trouble is it's Open Reach that didn't turn up, and unfortunately whatever ISP you use they still have to deal with Open Reach for FTTC, but some are better than others at getting OR to do their job.

My ISP is Bt so you'd think they'd have a little more input and power over Openreach but obviously not.

I'm still going to make a complaint as I've now missed 2 half days in work and a family Birthday today and the wife is barely speaking to me because of today (some might say that's a good thing mind )

I just really hope they turn up Tuesday now. Luckily I have the week off so won't need to take any more time off to be here!

Every ISP has the exact same "power".


Openreach cannot be seen to give preference to any ISP.