When will my cabinet be upgraded to FTTC

My exchange is upgraded to fibre but my cabinet is not. Does anyone know how I find out when my cabinet is being upgraded? I've been on 2.5mbit for the last 5 years and cannot wait until I can get FTTC.

Thanks for any advice that you can provide.

Hi Anonymous,

BT does not publicly share its cabinet-level plans, but if you post your full postcode someone here may be able to find the details for you.

Does the BT Wholesale Checker provide any indication for your telephone number?

Our number does not show up on that checker as we are with Sky.

Our post code is BL3 1ST

Thank you in advance.

In reply to a post by Anonymous:

Our number does not show up on that checker as we are with Sky.

Our post code is BL3 1ST

Thank you in advance.

You can input your postcode/address and it would come back with a GOOD idea if it was available to you, or even better ask a next door neighbour to input their telephone number.

I'm afraid it looks like bad news.

- 90% of the properties in BL31ST have direct lines to the exchange; these are excluded from FTTC because BT is not permitted to run VDSL2 directly from the exchange

- 9% are connected to PCP128 which has been excluded from the upgrade

I don't know what happened to the other 1%: I suspect a rounding error!

In reply to a post by DougM:

I'm afraid it looks like bad news.

- 90% of the properties in BL31ST have direct lines to the exchange; these are excluded from FTTC because BT is not permitted to run VDSL2 directly from the exchange

- 9% are connected to PCP128 which has been excluded from the upgrade

I don't know what happened to the other 1%: I suspect a rounding error!

That sucks. That 9% don't get FTTC and don't get FTTP either it seems.

In reply to a post by DougM:

- 90% of the properties in BL31ST have direct lines to the exchange; these are excluded from FTTC because BT is not permitted to run VDSL2 directly from the exchange!

Why are they not permitted to do this

In reply to a post by Andrue:

In reply to a post by DougM:

I'm afraid it looks like bad news.

- 90% of the properties in BL31ST have direct lines to the exchange; these are excluded from FTTC because BT is not permitted to run VDSL2 directly from the exchange

- 9% are connected to PCP128 which has been excluded from the upgrade

I don't know what happened to the other 1%: I suspect a rounding error!

That sucks. That 9% don't get FTTC and don't get FTTP either it seems.

Thanks for the detailed information. That absolutely sucks. Guess I best get saving up for a 100meg leased line.

I believe the current version of the Ofcom Access Network Frequency Plan (ANFP) prevents the full frequency range of VDSL2 profiles 8c (legacy) and 17a (current) to be used within exchanges.

The goal of the ANFP is to minimize interference between the various transmission systems. I understand from reading other posts on this forum that the restrictions on VDSL2 are there to prevent interference ADSL2+ services served from the same exchange.

I also read about some practical issues. If the line is too long there will be no throughput benefit over ADSL2+ (VDSL2 effectively falls-back to ADSL2+ on long runs), and the line length from the VDSL2 DSLAM to the edge of the exchange can easily be 200m.

Does this mean I'm stuck on 2.5mb until something else gets invented that works for us?

In reply to a post by Anonymous:

Does this mean I'm stuck on 2.5mb until something else gets invented that works for us?

You might be able to get a bit more by messing around. Step 1 is to see if you can find your router stats and post those. See here for help.

In reply to a post by DougM:

I believe the current version of the Ofcom Access Network Frequency Plan (ANFP) prevents the full frequency range of VDSL2 profiles 8c (legacy) and 17a (current) to be used within exchanges.

The goal of the ANFP is to minimize interference between the various transmission systems. I understand from reading other posts on this forum that the restrictions on VDSL2 are there to prevent interference ADSL2+ services served from the same exchange.

I also read about some practical issues. If the line is too long there will be no throughput benefit over ADSL2+ (VDSL2 effectively falls-back to ADSL2+ on long runs), and the line length from the VDSL2 DSLAM to the edge of the exchange can easily be 200m.

Fiber runs across the Atlantic and this is a problem for a puny country?

EO lines aren't running on fibre, they're pure copper - hence the issue with line length.

FTTP will resolve the issue for EO lines.

In reply to a post by DougM:

I also read about some practical issues. If the line is too long there will be no throughput benefit over ADSL2+ (VDSL2 effectively falls-back to ADSL2+ on long runs), and the line length from the VDSL2 DSLAM to the edge of the exchange can easily be 200m.

The VDSL2 is only from the cabinet to the premises. 600 metres is good for 40Mbps connection in most cases.

200m anyway? Cab to exchange? What does the "m" stand for? .

You may want to re-read in threaded-mode.

I was responding to the question about why exchange-only lines are being excluded, explaining that under current regulations VDSL2 cannot be run from the exchange to directly-connected premises (those without PCPs).

But if it were permitted, according to the BT research paper, 200 metres is a typical line length within the exchange from MSAN/DSLAM to edge. So VDSL2 would not offer the same uplift for exchange-only because every line is effectively 200m longer than if it were connected to a DSLAM in a cabinet directly outside the exchange.

In that case you are right - 200 metres would indeed be quite a penalty to add before the line goes anywhere.

On the other hand, good speeds are possible out to over 600 metres, so the real question is: What proportion of the direct-exchange lines are direct because they are short, and close to the exchange? And what proportion are direct because they've gone out (a long distance) to a sparse location?

It could well be that the short lines wouldn't suffer from the penalty. But the solution for those might well be to add a cabinet very close to the exchange (which wouldn't have the 200m penalty), or an FTTP-based solution.

Adding a cabinet (or ten) might be the solution for the longer lines, but the sparseness is likely to work against this case. This would definitely require use of smaller DSLAM/MSANs (16 or 32 lines).

BT know the answer to this...

In reply to a post by DougM:

You may want to re-read in threaded-mode.

No need. I was fully aware of what you were answering, but given that most of us know there are no VDSL2 DSALMs in the exchange it never occurred to me that was your train of thought. Your answer just seemed odd.

Hence my questions, that you possibly didn't reach before hitting the Reply button .

In reply to a post by Stoo:

EO lines aren't running on fibre, they're pure copper - hence the issue with line length.

FTTP will resolve the issue for EO lines.

I guess FTTP will be something I would have to enquire about rather than assuming that's going to ever happen for free?

i have been on the bt wholesale site and inputted my phone number and the date keeps changine when it gets to it ... 3 times now its very annoying can you look up to see when my cabinett will be enabled please?
gu9 9be