New BB FEC errors

Moving from LLU to BTw would be the same as doing a lift and shift but not the same as doing a pair change.

I suggested a pair change just so you can eliminate the physical line as the cause. I know the BT tests pass but they pass a lot of lines that are faulty in my experience.

May I suggest contacting somebody higher up at your ISP by email? That should get things moving.
 
When the engineer had reportedly been to clear the fault at the cabinet and exchange there was little to no noise on the line. Just out of curiosity I went and had a listen earlier and it was back to having some noise present again. However, latest stats from the last 14 hours shows much less errors than a similar recent period as per the post above, both of which are since the last engineer visit. SN Margin has dropped a bit too for down stream, lowest I've seen it I think since moving from Sky.

Link Information

Uptime: 0 days, 13:57:44

DSL Type: ITU-T G.992.5

Bandwidth (Up/Down) [kbps/kbps]: 961 / 7,424

Data Transferred (Sent/Received) [MB/GB]: 191.57 / 2.95

Output Power (Up/Down) [dBm]: 12.5 / 0.0

Line Attenuation (Up/Down) [dB]: 23.7 / 43.0

SN Margin (Up/Down) [dB]: 11.8 / 10.2

System Vendor ID (Local/Remote): TMMB / ----

Chipset Vendor ID (Local/Remote): BDCM / IFTN

Loss of Framing (Local/Remote): 0 / 0

Loss of Signal (Local/Remote): 0 / 0

Loss of Power (Local/Remote): 0 / 0

Loss of Link (Remote): -

Error Seconds (Local/Remote): 131 / 0

FEC Errors (Up/Down): 25 / 13,776

CRC Errors (Up/Down): 1 / 210

HEC Errors (Up/Down): 1 / 1,563
 
Last edited:
just ignore the FEC errors even though there ridiculously high DSLAM ignores them.

CRC / HEC are more important when it comes to DSLAM preventative. or i could be wrong lol, though something is definitely still wrong with your line, like people have said RAIN seems to be your main issue.
something is causing noise between your master socket and the exchange.
 
Last edited:
The FECs are a useful indication of an interference problem if they are very high.

I wouldn't say in the latest set of stats that they are hugely high but in previous sets they are.

OP, you need to raise the noisy phone line to your phone provider as this will be likely affecting your broadband.

The problem isn't just going to vanish.
 
Well everything behaved beautifully whilst OR engineer present so no fault found, line was quiet and very minimal CRC's occurred. Replaced connection in outside xnte box so their wire and ours are connected now without the original segmentation and fuse as he described it. New internal master socket and vdsl faceplate. Shortly after engineer visit we check phone and discover noisy line and router stats show CRC's climbing at a rate of aprox. 110'000 per half hour or aprox. 7000 per 1MB of data transferred downstream.

New router being dispatched by ISP and OR copper engineer job ticket raised.
 
Ah the old tests pass, bugger off routine. I know it well :rolleyes:

You're not going to like this but you're going to keep needing to get engineers until something gets done. Tell them you want a pair change done, even though the tests pass. Tell them about the high CRCs and error seconds, tell them about the noise on the line.

There are good engineers out there, trust me.
 
Well we've decided today to jump ship since the offer of fiber with someone else at no more cost than were currently paying was too tempting an offer to pass up on.

We will be going from LLU to BT Wholesale so I guess that will be a lift and shift.

I'm fairly sure the problem is at the exchange with our current adsl as I discovered a loose connection on our telephone handset so the OR engineer was right in not discovering any noise on the line with his equipment.

Anyway we hopefully will be sorted once the changeover to the new provider takes place, just takes a while, about 3 weeks until our phone moves over, then a couple of weeks without dsl until the fiber goes live. Have to make do with mobile broadband to tide us over the down time.
 
Back
Top Bottom