Lower SNR extended to my cab?

I had been happily sync'd for about 12 days until shortly before 12pm today when there was a resync. I had a warning email about the resync so checked my stats. Seems I'm now connected at 66Mbps (3 more than usual) and SNR down is 5.3.

Does this mean that my cab is now using the new SNR profiles? I am tenbyboy2 on MDWS. My current stats:

adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 17188 Kbps, Downstream rate = 66214 Kbps
Bearer: 0, Upstream rate = 17188 Kbps, Downstream rate = 66249 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 5.3 6.0
Attn(dB): 18.9 0.0
Pwr(dBm): 12.6 7.5

VDSL2 framing
Bearer 0
MSGc: -6 21
B: 243 237
M: 1 1
T: 0 64
R: 10 16
S: 0.1173 0.4406
L: 17326 4612
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 72 0
TxQueue: 18 0
G.INP Framing: 18 0
G.INP lookback: 18 0
RRC bits: 0 24

It appears to be yes. It matches the criteria expected.

1st is that only the downstream is affected. Upstream will show the usual slight variation but should remain roughly the same.
2nd is that the line doesn't jump straight to 3dB. Every example I've seen show the line should drop in 1dB stages.
3rd is that the max attainable rises with the drop in target SNRM.

With a lower SNRM caused by a DSLAM reboot it usually affects both downstream/upstream. The max attainable usually drops back down after all your crosstalkers reconnect. It also doesn't go 1dB intervals.

You appear to be on a 5dB target. If DLM thinks the line is coping then in the next couple days it should drop to 4dB. Could you post back if it does indeed drop to 4dB?

Thanks for the reply - I was hoping that was the case. I've had a couple of disconnects over the past few months that I though was the trial but as you said - the upstream and downstream were affected but speed dropped back down within a few hrs.

I'll keep an eye in it over the next couple of days and yes I sure will post back if it drops to 4db.

Thanks! Please could you post the errors part of the adsl info --stats result, too? This will help us determine if your line is stable.

Here we go this is obviously just since the resync:

Since Link time = 11 hours 23 min 21 sec
FEC: 127272 35
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0

Over the last few days mine has went from:

DSLAM/MSAN type: BDCM
Modem/router firmware: Not reported
DSL mode: G.993.2 (VDSL2)
Status: Showtime
Uptime: 3 days, 4:19:55
Resyncs: 0 (since 02 Nov 2016 13:06:38)

Downstream Upstream
Line attenuation (dB): 14.8 5.9
Signal attenuation (dB): Not monitored
Connection speed (kbps): 35413 7139
SNR margin (dB): 6.2 6.2
Power (dBm): 13.9 7.2
Interleave depth: 8 0
INP: 49.00 0
G.INP: Enabled

RSCorr/RS (%):
RSUnCorr/RS (%):
ES/hour:

To:

Stats recorded 26 Mar 2017 09:28:56

DSLAM/MSAN type: BDCM
Modem/router firmware: Not reported
DSL mode: G.993.2 (VDSL2)
Status: Showtime
Uptime: 0 days, 23:34:49
Resyncs: 0 (since 22 Feb 2017 15:54:24)

Downstream Upstream
Line attenuation (dB): 14.9 6.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 39999 7622
SNR margin (dB): 4.6 6.0
Power (dBm): 14.0 7.5
Interleave depth: 4 0
INP: 52.00 0
G.INP: Enabled

RSCorr/RS (%):
RSUnCorr/RS (%):
ES/hour:

At one point it was at 5dB downstream and a D/S Sync of about 38.8Mb.

Nice!! Mine's still at 5.3 this morning but it's less than 24hrs since the resync so hopefully, as long as it stays stable enough, I'll see a further drop later this week

In reply to a post by j0hn83:

It appears to be yes. It matches the criteria expected.

Agreed.

Looking at MDWS, the line seems to be getting the same FEC and retransmission rates as before, and no CRC or ES.

Currently looking good to go for the next step.

That's good news! Fingers crossed then I see a further drop in SNR some time this week

Yes, not like mine! 28454402 downstream FEC's/hour in 23 hours, 5 minutes and 50 seconds on a downstream SNR margin of 3 dB!

Ouch!!

Ikr! People say I don't have a fault, but what's even more surprising is that there are no downstream errors!

Edited by deleted (Mon 27-Mar-17 12:29:05)

There is a BIG difference between a fault that an telecoms operator will dispatch staff to resolve and be able to fix and what the various error counters/handlers within the DSL stack will report.

Any Radio Frequency based medium has to tolerate errors, hence all the error correction systems, and while fibre optic may not be subject to RF interference many of the mathematical techniques are still employed.

In reply to a post by WilliamGrimsley:

Ikr! People say I don't have a fault,

I say you do have a fault.

But I also say you don't have a fault that's reportable. Or not last time I looked, anyway.

The trick is to realise is that there is no such thing as a perfect line. It just has to be "good enough" to carry the service being asked for.

In reply to a post by WilliamGrimsley:

what's even more surprising is that there are no downstream errors!

Many engineers and researchers have spent years, decades even, figuring out how to get lines to transfer data in noisy environments with as few errors as possible.

Should it be a surprise that so many of these solutions actually work?

People keep saying that copper is obsolete. The trouble is that the DSP chips controlling those copper lines are most certainly not obsolete. They employ the state of the art of what we can get signal processors to do. The improvements we see in speed and reliability is a direct consequence of Moore's law, and the amount of work we can ask of our hardware.

My line has suffered 2 resyncs in the last 30 mins, with the reason apparently being "Reason: 4 CReverb1Misdetection" - not a clue what that means!

Also, my attenuation has jumped up from 18.5ish to 29 and speeds have more than halved:

Current Downstream Sync Rate is now 28817kbps @ 5.1db SNRM
Current Upstream Sync Rate is now 8173kbps @ 6.2db SNRM

I haven't got access to my stats from modem at moment but I am tenbyboy2 on MDWS.

Need to check if you have dial tone, if so, run the quiet line test.

I literally work 2 mins away from home so I need to concoct a good story to have to pop home for 15 mins

This has happened before but it's a pain it's happening now just as my line got the lowered SNR yesterday as it may now think it's too unstable do you think?

Working that close then I would think the excuse of "I need the loo" would be good enough to get out of the office

It's worth a try

Nah, your noise margin is still 5.1, so something has caused the speed to drop. It's not like DLM has took a huff and increased the margin to 20.

but it's a pain it's happening now just as my line got the lowered SNR yesterday

....or maybe it's happening now because the lowered SNR happened yesterday ?

.. just a thought.

It was totally stable all day yesterday so I doubt very much it would suddenly go nuts today.

Fair enough ....

Then as someone else suggested, time to nip home and see if the line is noisy/dead.

Yep - I'm going to try and pop home in the next hour so I'll report back once I've checked.

Make a brew whilst you are there Murroughs is good !

Funny you should mention that - I have some Murroughs in the cupboard. Good call

Had some whilst in St.Davids a while back, now right up on my top five teas list.

p.s. White with one for me please.

Nice place St Davids - we camp there sometimes!!!

Just had another resync by looks of it and attenuation has dropped a little to 25.3 with speed now at:

Reason: 1 Remote Defect Indicator/DLM

Current Downstream Sync Rate is now 46192kbps @ 5.3db SNRM
Current Upstream Sync Rate is now 13331kbps @ 6.2db SNRM

Looks like I won't get home no until lunch about 1.25pm so I'll have to wait untl then to check phone etc.

Nice place St Davids - we camp there sometimes!!!

...if you ever fancy something a little more up-market try Ty-Boia B&B. Really top notch.

That place looks good!!!

Well I got home picked up the phone and didn't need to do a quiet line test as the background scratching-type noises are loud as heck. I will probably get onto them later.

However, on my drive back, I pass the cab and BT are working on it. I was unable to stop and talk to them as there are roadworks and traffic lights there. Just checked emails now and there has just been another resync and speeds are nearly back to normal even though they should be higher as the SNR is now 4.1.

Latest stats:

Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 4.1 4.7
Attenuation (dB) 19.3 0.0
Output Power (dBm) 12.6 7.5
Attainable Rate (Kbps) 62017 16033
Rate (Kbps) 63977 16808
B (# of bytes in Mux Data Frame) 235 237
M (# of Mux Data Frames in an RS codeword) 1 1
T (# of Mux Data Frames in an OH sub-frame) 0 64
R (# of redundancy bytes in the RS codeword) 12 16
S (# of data symbols over which the RS code word spans) 0.1174 0.4506
L (# of bits transmitted in each data symbol) 16900 4510
D (interleaver depth) 8 1
I (interleaver block size in bytes) 248 127
N (RS codeword size) 248 254
Delay (msec) 0 0
INP (DMT symbol) 49.00 0.00

Line may have been disturbed when they're working on the cab.

If the line is still noisy when you get home, get it reported and it should be the end of your woes once it's fixed.

So it looks like they are doing cab uplift work maybe ?

They are building a mini-roundabout literally 30ft from the cab so they had to move all the lines/fibre a few weeks ago as it was buried way to shallow for them to continue with the work.

Not sure if what they are doing today is related but it could be.

It's off altogether now by looks of it as I can't even remote into my router remotely and my IP isn't updating on OpenDNS so I might get onto BT via online chat now.

Edited by WelshWArrior (Tue 28-Mar-17 14:34:06)

To be honest, I'd just wait until any works are finished today. If it's off and there's no one working at the cab when you go home, then I'd report the fault.

I agree with Lee .... except if they are still there when you get home, and the lines still dead, maybe nip and ask if they can fix it for you,

Murroughs may help here too.

Hahahaha sounds like good plan

I got home from work and surprise surprise BT had finished on the CAB.

Noise is still very much there though - it's a loud crackling/scratching sound. What could cause this? Nothing has changed with my house and it's only been there since BT were in the cab yesterday and my line started suffering resyncs.

The noise is obviously causing low speeds as my SNR is now 4 but sync is 56Mbps whereas before the probs started yesterday, it was 66Mbps with an SNR of 5.

I'm going to get onto BT about this this morning but wanted to make sure nothing within the house could cause this as I don't want the £129 charge they warn about on their website when reporting a fault. Also, their online line checker reports no faults on the line!

I'd suggest you go the route of reporting this as noisy, don't muddy the water and mention the FTTC.

Take your faceplate off the NTE and confirm that the line is audibly noisy in the test jack with a known working corded phone.

Ring and report, you will doubtless be warned about possible charges, but if you have taken the above steps, then it's Openreach's responsibility to repair for free.

I'll get on it this morning.

I suppose the Murroughs may come into play again

And if they don't want it, send it this way

I'd just add that there is little point telling CP CS about the cab work hoping it'll resolve things faster, that detail (useful to the engineer who actually visits) is almost never put on fault notes these days.

The most useful info will be a description of the fault, i.e. Crackle and a valid contact number for you.

If the CP insists on an appointment, no point in arguing the toss, just take the first going and ensure the CP puts 'please ring 0123 456 789 30 mins prior to visit' in their notes for Openreach.

If the engineer does visit, then is the point to mention all was well till the cab uplift started.

Cheers for that. Just booked for tomorrow between 8am and 1pm. Asked Engineer to ring my mobile 15mins before he visits.

Guess what? As they did the line test while I was talking to them, there was another resync. Attenutaion has gone down to 19.7 and speeds up to 63Mbps. The attenuation is still about 1db higher than before fault started yesterday morn and speed should be faster for my SNR of 5. Obviously I can't see if the noise is still on line from work but I'll check at lunchtime and cancel engineer if need be.

It wouldn't be surprising if someone else hasn't already reported a similar problem and remedial work/checks affecting several been carried out at the cabinet today.

Hopefully I've just got to remember to check my line for noise at lunch time and cancel the engineer by 2pm if noise has gone then!!

Well this is typical. I got home at lunch time, checked the phone (even brought one from work to rule out mine being dodgy) and the scratching noises are now gone from the phone so I cancelled the Engineer.

I guess RobertoS was correct this morning that the resync while I was on the phone to BT could have been BT at the cab again sorting it out.

Only thing is, my speed is still good bit lower due to the Att still being 1db higher than it was. Guess I'll just have to hope it settles down but I'm not holding out much hope

There was a recent thread with this symptom...
http://forums.thinkbroadband.com/fibre/t/4526275-re-...

It is, essentially a new sync because the training in the previous sync didn't work. It suggests a very garbled line or modem ... and your later experiences show this.

Myself, I'd have kept the appointment, to get the guy to check the joints in the cab at least.

The change in attenuation might be because you've been swapped over to the new cable. You might even be still T'd into both old and new lines together, and they'll be back to finish tomorrow. Zarjaz will know whether that's a possibility better than me.

It is indeed a possibility , and yes, I'd have kept the appointment too .... but suspect the voice CP might have just raised a CIDT task .... so unless the PQ test failed the engineer wouldn't have done too much.

Well it's all gone wrong again this eve with crackling back and 4 or 5 disconnects earlier by the looks if it whilst I was out.

I'll get back into BT in the morning. Will I get charged though if, as today the crackling goes before the Engineer gets here?

Is it worth saying about the resyncs when I book engineer so that they'll check that too?

I believe with BT, there's no charge if no fault found.

Especially if the agent can hear the noise when you call to report it.

Is it worth saying about the resyncs when I book engineer so that they'll check that too?

I doubt it, it'll just muddy the waters.

I'll get back into BT in the morning. Will I get charged though if, as today the crackling goes before the Engineer gets here?

That I honestly can't tell you, but at least a mention of the cab work to the visiting engineer should make them understand whats been going on.

AArrrggg - no crackling what so ever on line today. BUT several resyncs during night with the reason being loss of service and now just had 2 more within the space of 4 mins.

I can't understand what is causing it as there are no spikes of FECs before or after, no ES or SES.

Is it worth me ringing them and reporting the dropped connections? I am with BT for Internet anyhow and surely I should be able to report these dropped connections. Are they not able to see the resyncs?

Reason I'm being cautious about getting an engineer is that I can't afford the £129 if they don't find a fault.

Are they not able to see the resyncs?

They should be able to .....

Reason I'm being cautious about getting an engineer is that I can't afford the £129 if they don't find a fault.

I fully understand that.

See my reply from last night.

Sorry, missed that last night!!

I think I'm going to leave it a day or 2 to hopefully settle back down. FECs down to mid 50s and no restarts for couple of hrs now. No noise on line and neighbour texted me and said Openreach were back at cab earlier.

Speeds still down but I'm assuming it's because INP is still high at 52? It's usually 47-48.

Engineer re-booked.

Got home form work and crackling was so bad, I couldn't even ring BT so had to use online chat! Also, several more resyncs this afternoon.

Apparently, according to CS person I spoke to via chat, Engineer won't need to visit house but I made sure I gave my mobile number anyhow and asked them to ring me 15 mins before.

Going to keep this appointment no matter what this time. They say estimated fix by 01/04/2017.

Good luck.

Thanks I asked for a Saturday appointment and they said he probably won't visit the house so haven't been given a time. I'll post back here with verdict once engineer has been though.

Thinking about it tonight, the crackling on the line seems to be corresponding with the heavy rain we've been having over the past few days. Had the heaviest rain I ever seen about 20 mins ago and had another resync, this time with reason 20 20 - any ideas what that means?

any ideas what that means?

It could mean that your theory about the cab uplift is coincidental .... Is your house fed overhead ?

Nope all underground. I'm literally 150m from PCP but my attenuation has always been around 18db which I think means my line is about 350m?

There is an SCP up around the corner so I'm not sure if my line goes up to that first then back to my house.

Depends on the wire gauge - to an extent. However, 18dB is nearer 500m. At 440m, mine is 16 dB.

Right so even longer than I thought OR down to the gauge! I'm going to quiz the engineer if he does actually come to the house as the last one told me my line goes straight to the cab which, as I said above is about 150m.

Just did a quick measurement via Google Earth (I know this is only rough) but even if the line does go past the house, up to the scp and then back to me, the distance is only 320ish metres.

Line is terrible this morning - can't use phone due to crackling, G.inp is now enabled up and down and there have been 15 resyncs since this time yesterday.

I better get used to it as engineer isn't due to look at it until tomorrow!

Well having stayed in all day today and nothing apart from the now very regular resyncs happening on my line, I decided to get in touch with BT CS via online chat (as landline currently unusable due to noise).

Apparently, after speaking to Openreach, the 'work stack' was so full they couldn't look at my issue today.

The line is now so bad that the Internet is practically unusable, with pages timing out most of the time and BT TV so pixelated it's pointless trying to watch something.

Engineer now re-booked for Monday between 13:00 and 18:00. BT CS will call back after that to make sure the issue is resolved and to chat to me about reimbursement apparently!

Oh dear ....

worked myself today, was as quiet as you like round this way.

I think you should come and visit St David's and come to Tenby on your way there You'd probably sort this issue out in 2 mins!!

Edited by WelshWArrior (Sat 01-Apr-17 21:22:25)

It takes longer than that to fuel up on tea and Newton figs. Then two minutes afterwards for the job.

Hahahaha

Sadly it was my dear old Pa who lived in St.Davids, and he passed away in January. So won't be that way any time soon.

Good luck with your appointment, I hope you get a decent multi skilled engineer.

Sorry to hear about that.

Yeah hopefully I get an engineer who is both skilled and not on his way home at 17.45 and not in the mood!

I'll report be I once he's been.

Just had my 16th (I think - I'm losing count!) resync of the day

On top of that - just noticed that my line now seems to be banded as it connects at the same each time now - 55,000Kbps down and no more!

Will a DLM reset (assuming the engineer dues one Monday) remedy that?

Edited by WelshWArrior (Sat 01-Apr-17 23:23:03)

In reply to a post by WelshWArrior:

Engineer re-booked.
Apparently, according to CS person I spoke to via chat, Engineer won't need to visit house

The booking for to-day says Engineer will not need to visit your premises so how the heck can the or engineer run his/her line test from within your premises (Master Socket) sounds like a load of bull from your ISP

Yep, a DLM reset will sort that out.

It should be about the last thing the engineer does before a 5 minute close test on the sync.

Brill - that's what I was hoping - cheers

I'll post back here tomorrow after Engineer has been.

I've just received a text from BT ststing:

Hello, BT here. We're sending you an engineer on Monday 03/04/2017 between 1pm and 6pm. Our tests indicate an internal problem so we recommend a check on your equipment.

How can they say it's an internal problem if nobody has been? I've tried 3 different modems and another wired phone straight into master socket and the noise is still there. What elsr internally could cause cause this? There is no extension wiring in house - just master socket (Openreach Nte5 Mk3 type) with modem and phone plugged in .

They're mentioning the £129 charge again so that is making me double check myself!

I've tried 3 different modems and another wired phone straight into master socket and the noise is still there. What elsr internally could cause cause this? There is no extension wiring in house - just master socket (Openreach Nte5 Mk3 type) with modem and phone plugged in .

They are just covering their [censored], no hard fault detected on a remote test ..... You have done all that is required to prove it isn't an internal problem, therefore no charge to follow.

Go enjoy the sun.

Brill - cheers. I'm just being paranoid now.

I'm taking your advice and getting out of the house

Edited by WelshWArrior (Sun 02-Apr-17 11:20:37)

Good news - Engineer has just been.
Bad news - no fault found

What he did say is that he was talking to 2 other engineers at the exchange before he left to come to my house and they had just fixed a joint in front of my cab where they did the uplift work last week. He reckons this has also sorted my job out as the crackling has gone.

Only thing is - he can't request a DLM reset because he was booked for a line fault. I told him that the CS peeps were due to ring me back later to check on the progress and he said they can do the DLM reset for me. He did find a slight H(???) error but nothing that he could do anything about as it looks to be 490 meteres away - which is between the fibre cab and exchange.

He was a nice bloke and showed me the map of where my line goes after it leaves the cab - it actually goes the opposite direction which explains the higher than expected attenuation.

I also found out that one of the top fibre bosses in Openreach owns a holiday home a few doors down from me - I'll be introducing myself next time he's there

Hmmmmmm ......

What he did say is that he was talking to 2 other engineers at the exchange before he left to come to my house and they had just fixed a joint in front of my cab where they did the uplift work last week. He reckons this has also sorted my job out as the crackling has gone.

Plausible I guess.

he can't request a DLM reset because he was booked for a line fault. I told him that the CS peeps were due to ring me back later to check on the progress and he said they can do the DLM reset for me

He won't have been given the OGEA reference if it was (what sounds like a CIDT task) I bet they don't/won't/can't do the reset. When they ring make DAMN sure they WERE aware of the crackling previously hence THEM making the booking ...... get a note of whom you speak to and get them to confirm NO CHARGE.

He did find a slight H(???) error but nothing that he could do anything about as it looks to be 490 meteres away - which is between the fibre cab and exchange.

He sounds like a [censored] to me TBF...... He could see an HR on the E side and was unable to just go swap that out BS, an E side swap is a simple clear and well within the remit of any CA lightweight.

The 24 million dollar question is, has the noise gone, and what do the stats look like now ?

Noise definitely gone now - it was really bad at lunchtime when I came home but that was apparently before they repaired a joint.

BT have also just rung me to make sure issue is resolved and have performed the DLM reset after I asked them to! What they did say though is not to reboot router for 72hrs - is that correct?

As I can't reboot router, stats are still the same:

adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 18466 Kbps, Downstream rate = 61170 Kbps
Bearer: 0, Upstream rate = 17000 Kbps, Downstream rate = 55000 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 7.7 6.6
Attn(dB): 19.1 0.0
Pwr(dBm): 12.6 7.6

VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 227 163
M: 1 1
T: 0 0
R: 12 12
S: 0.1319 0.3047
L: 14562 4621
D: 4 2
I: 240 176
N: 240 176
Q: 4 2
V: 0 1
RxQueue: 130 115
TxQueue: 26 23
G.INP Framing: 18 18
G.INP lookback: 26 23
RRC bits: 24 24
Bearer 1

Can the DLM reset really take 72hrs and will it just drop on it's own in that time and remove the banding?

The BT rep just fobbed you off. They can't do DLM resets on fibre, only ADSL. A DLM reset would have triggered an immediate resync.

Just spoke to them again via online chat - they reckon it's been passed to another team to do the reset which will happen overnight. They still reiterated that I shouldn't disconnect router for 72hrs afterwards.

The don't reboot is done to avoid those who can't wait and keep rebooting to see if a change has happened, and this ends up triggering DLM to curtail you, so don't fiddle is best advice.

OK cheers. So have I been fobbed off by both Engineer and BT CS as J0hn83 suggested?

I'm pretty sure in my last house where I was also on FTTC, I definitely had a DLM reset.

Zarjaz - what's your take on this? Could the DLM reset have been set to trigger overnight?

+ 1

OK cheers. So have I been fobbed off by both Engineer and BT CS as J0hn83 suggested?

I'm pretty sure in my last house where I was also on FTTC, I definitely had a DLM reset.

Zarjaz - what's your take on this? Could the DLM reset have been set to trigger overnight?

The engineer didn't lie ..... he doubtless had a voice fault so the OGEA ref wouldn't have been in his job notes. Can't say the same for BT CS ..... never known them able to do a DLM reset on FTTC, if you trigger one it happens inside of a couple of minutes or not at all.

Oh great - more fun and games ahead then! I best leave it the full 72hrs before making a complaint if it hasn't been done then.

Not much else I can do is there?

I have just spent ages speaking to BT CS to try and get the DLM reset. After a long drawn out convo, the gist of it was:

MY estimated line speed is up to 54Mbps (I've been connected at 61Mbps-ish for over a year)
She did another line reset (nothing after 15 mins so asked her to try again)
Then she told me she has requested another reset but said it might take 5-6 hrs, after which time, I need to reset the hub using the reset button!!

At that point, I asked her to make a not of what she said she'd done as I know I'll be back onto her later. She sent me a text to reply to and she will ring me back later if need be.

I can see this becoming a looooong drawn out affair

My guess is they aren't deliberately lying but just poorly trained. No ISP has the ability to perform a DLM reset on fibre, not even BT. They must be getting confused with ADSL, where they can perform some resets. Only a booked OpenReach engineer can perform a DLM reset on fibre, either via their smartphone app or by calling the DCoe.

So does that mean that unless I'm extremely lucky and develop a broadband issue, then I'm likely to be stuck on a banded profile??

Is there anyone I can ring?

Hi WelshWArrior,

Yes, you'll need to ask for a broadband boost engineer. I had my telephony fault fixed yesterday and got a broadband boost engineer coming today to fix the banding it caused.

Edited by deleted (Tue 04-Apr-17 11:32:53)

How did you go about organising that? The CS reps (3 of them so far) do not seem to have a clue what is going on!

I had a telephony fault which caused my line to become banded. Luckily, the telephony fault was fixed yesterday, but unfortunately the telephony engineer was unable to do a DLM reset. So, I had to organise a broadband boost engineer appointment which is booked for today. If you go to BT live chat and enforce that you need a broadband boost engineer they'll book it for you.

Edited by deleted (Tue 04-Apr-17 11:42:46)

Thanks for that - I'll get onto them later today. Hope your's gets sorted soon.

Thanks. I don't have a lot of confidence that it will, as I just rang BT and they said "Someone is looking into it today, but I don't have a time written here."

Edited by deleted (Tue 04-Apr-17 11:50:23)

Yeah, all done here. NTE5 and MK3 replaced with a master socket 5c and MK4, DLM reset done and back on the bog standard interleaved profile atm. The engineer said they cannot do full DLM resets (downstream reset to fastpath) anymore. Hopefully, G.INP will be back soon.

Edited by deleted (Tue 04-Apr-17 13:47:19)

Glad you got yours' sorted. Wish me luck for later. Doubt they'll even send me an engineer!!

You've got to be assertive and keep checking that they've got it right, otherwise you could get a telephony engineer! Good luck!

Yeah, Downstream FEC is working very hard right now!

xDSL
Mode VDSL2
Traffic Type PTM
Status Up
Link Power State L0
Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 6.3 5.9
Attenuation (dB) 23.9 0.0
Output Power (dBm) 12.2 6.2
Attainable Rate (Kbps) 41586 7900
Rate (Kbps) 35133 7900
B (# of bytes in Mux Data Frame) 51 239
M (# of Mux Data Frames in an RS codeword) 1 1
T (# of Mux Data Frames in an OH sub-frame) 64 42
R (# of redundancy bytes in the RS codeword) 12 0
S (# of data symbols over which the RS code word spans) 0.0471 0.9653
L (# of bits transmitted in each data symbol) 10872 1989
D (interleaver depth) 687 1
I (interleaver block size in bytes) 64 120
N (RS codeword size) 64 240
Delay (msec) 8 0
INP (DMT symbol) 3.00 0.00
OH Frames 1080388 320361
OH Frame Errors 2 7
RS Words 276495685 660868
RS Correctable Errors 1500783 0
RS Uncorrectable Errors 5 0
HEC Errors 0 0
OCD Errors 0 0
LCD Errors 0 0
Total Cells 220864699 0
Data Cells 4941722 0
Bit Errors 0 0
Total ES 1 6
Total SES 0 0
Total UAS 30 30

Edited by deleted (Tue 04-Apr-17 14:31:06)

What were you banded at?

I know you'll think I'm mad, but 35000/7200. With G.INP and 3/6 dB I got nearly 48000/8700.

Surprised that my copper pair is "perfect" to say how many downstream FEC's there are! Believe it or not, though, the engineer said the minimum downstream rate for my line was 20.6 Mbps! Seems extremely low to me!

Edited by deleted (Tue 04-Apr-17 19:29:17)

Current line stats:

xDSL
Mode VDSL2
Traffic Type PTM
Status Up
Link Power State L0
Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 6.1 6.1
Attenuation (dB) 23.9 0.0
Output Power (dBm) 12.2 6.2
Attainable Rate (Kbps) 41571 7900
Rate (Kbps) 35133 7900
B (# of bytes in Mux Data Frame) 51 239
M (# of Mux Data Frames in an RS codeword) 1 1
T (# of Mux Data Frames in an OH sub-frame) 64 42
R (# of redundancy bytes in the RS codeword) 12 0
S (# of data symbols over which the RS code word spans) 0.0471 0.9653
L (# of bits transmitted in each data symbol) 10872 1989
D (interleaver depth) 687 1
I (interleaver block size in bytes) 64 120
N (RS codeword size) 64 240
Delay (msec) 8 0
INP (DMT symbol) 3.00 0.00
OH Frames 26865695 7966321
OH Frame Errors 26 156
RS Words 2582566834 1823637
RS Correctable Errors 30649852 0
RS Uncorrectable Errors 70 0
HEC Errors 7 0
OCD Errors 0 0
LCD Errors 0 0
Total Cells 1197206865 0
Data Cells 116300710 0
Bit Errors 0 0
Total ES 13 131
Total SES 0 1
Total UAS 30 30

Would dread to think about the stability on fastpath...

Edited by deleted (Wed 05-Apr-17 16:49:32)

Any update on the broadband boost engineer appointment?