In reply to a post by MrSaffron:

I have lots of faith and believe me, that will not be cabinet E_1 once its live.

Agreed, I have seen a block of EO Lines, say EO Block 7 consisting of several post codes get moved over to either an all in one or two separate cabinets, they are temporary assigned a Node ID of E_7 to match the EO Block number and when they get to connecting them up and then testing it was assigned a permanent Node ID.

This was what I have seen several times now, twice on my exchange as well as part of LEP.

*** update ***
In WWWombat example Cabinet E_1 is catering for postcodes on EO Block 1 shown below:

[EO Block 1]
SG2 7JD
SG2 7JE

So I assume it will be a small cabinet or maybe other EO Blocks will be moved over to it later.

But I am thinking that cabinet will be assigned a Node ID of P2 later on.
Lets hope they are smart where they locate the cabinet or else nobody on it will be able to get fibre.

BTW the exchange is here which is smaller than my shed BTW , so going by the two postcodes which are far from it and the route to join them would be long.


Paul

Edited by PaulKirby (Fri 16-Dec-16 23:39:21)

So is it going to be a cabinet? Is it going to be a separate cabinet from P1?

If so, then we're talking about a cabinet with an unknown identity that, for the sake of argument, we might as well call *something* for now. What better to call it the same name than Codelook is using?

In reply to a post by PaulKirby:

So I assume it will be a small cabinet or maybe other EO Blocks will be moved over to it later.

Yeah, that's what I assume.

But there's no point in discussing a cabinet listed on Codelook and using a name that is different from the name used there. Not until it gets a proper name.

In reply to a post by WWWombat:

In reply to a post by PaulKirby:

So I assume it will be a small cabinet or maybe other EO Blocks will be moved over to it later.

Yeah, that's what I assume.

But there's no point in discussing a cabinet listed on Codelook and using a name that is different from the name used there. Not until it gets a proper name.

Agreed, else it would lead to confusion.

Paul

Separate cabinet from P1 otherwise would be called P1 already

As to what another site calls it, down to them, maybe unknown new cabinet

I just did a quick bit of searching and found cabinet P1. I had assumed all lines on this exchange were EO - I was wrong. I guess it also explains why this was done first!

I'm guessing enabling a cab that already exists is a lot easier than rearranging a bunch of EO lines.

If they are only putting 1 cabinet in I would assume they would try and include as many EO lines as possible - the logical conclusion there would be a cabinet right outside the exchange?

If that is the case here then there is going to be a lot of sub 24Mbps lines on it.

Or I guess they might just place it so that some EO lines get maximum benefit and sod the rest?

My bet is one at exchange, and ideally one more in Clay End and another in Wood End but all depends on targets of the project

In reply to a post by MrSaffron:

Separate cabinet from P1 otherwise would be called P1 already

I guess if the only *known* proposition is that the EO line is going to be bundled into a cabinet, then we don't know that until we do know of a separate cabinet identity.

If, as you argue, the "E_1" nomenclature indicates merely that it is an EO bundle being subsumed into a cabinet, then we cannot be sure it is a separate, new cabinet, unless, well we get something out of the next answer...

In reply to a post by MrSaffron:

As to what another site calls it, down to them, maybe unknown new cabinet

I only know of two places to look up all cabinet identities, especially without searching all postcodes on the OR or BTW websites: The Openreach "secret" list (sometimes leaked), and the Codelook website. Without access to the former, there's only the latter to go on.

We can get past that limitation iff someone publishes a postcode and some OR/BTW lookup information.

Unless, of course, TBB are about to publish some of their secret postcode/cabinet data?

Unless and until that happens, we're left with grubbing at whatever sources we can use. As I'm talking to people with access to nothing more than the same tools I have (ie *not* the secret list), then the best point of contact is to use the same naming convention.

Snide comments to people who have no choice but to converse this way aren't helpful.

Edit:
I did have a scraper that could run from a set of postcodes to a set of cabinets, much like Paul Kirby's tool. BT's mechanisms to bar it made it relatively useless without a rewrite (or a pool of outbound IPs). I've yet found sufficient impetus to work around BT's blocking ... so, for now, work with the rather limited tools where BT choose to hide their network (that is, admittedly, of critical national importance).

Edited by deleted (Sun 18-Dec-16 01:55:20)

Only reason for highlighting that cabinet would NOT be called is E_1 is because others will find E_2 etc mentioned and may mean that they are going to get a cabinet...

No snide intentions

In the last few days my postcode has gone from "Exploring Solutions", which I read to mean not happening to "In Scope".

Hopefully this either means they will be siting that cabinet somewhere useful or they have decided to put more cabinets out.

Codelook doesn't seem have been updated.

Hopefully I'm not reading too much in to this but I assume that means that I should now get Fibre Broadband at somepoint in the not to distant future?

I'm guessing this has nothing to do with the clawback money just announced (re-announced)

https://s27.postimg.org/p0csh07ab/connected.png

Edited by deleted (Thu 22-Dec-16 10:28:34)