Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: glennbtn on October 05, 2020, 02:53:24 PM
-
So been waiting years for BT to upgrade our cabinet to fibre. They have been saying it not financially viable, mainly because loads have gone to virgin as not other fibre service.
BT are meant to be rolling out FTTP over the 6 months or so have been keeping an eye on connection etc as have seen bt floating about a lot and I seriously need something quicker asap.
Now my cabinet is 5 doors up the road. I now can see that online with the bb checker and the openreach fibre checker that FTTC is now available. Now I am presuming BT have screwed the database as my cab has not been upgraded and no 2nd cabinet has appeared. Is it possible they are running fibre to another cabinet in some way or we think BT have screwed things up
-
If I go to https://www.telecom-tariffs.co.uk/codelook.htm
enter my postcode, I find FTTC has been available on cabinets P29 or P2 since 2015:
https://www.telecom-tariffs.co.uk/codelook.htm?xid=242447&postcodedet=NN13AX
-
If I use https://www.telecom-tariffs.co.uk/codelook.htm it says not available
But if I use https://www.broadbandchecker.btwholesale.com or https://www.openreach.com/fibre-broadband both say available
-
If I use https://www.telecom-tariffs.co.uk/codelook.htm it says not available
But if I use https://www.broadbandchecker.btwholesale.com or https://www.openreach.com/fibre-broadband both say available
Which cabinet, if you do not mind me asking?
-
Cabinet 32 IN worthing
-
When you enter your address in to https://www.broadbandchecker.btwholesale.com/ which cabinet does it say you are connected to.
It might not be the cabinet you think you are connected to.
There's also a few Worthing exchanges.
Worthing West, Worthing Central and Worthing Swandean.
The BT checker linked above will tell you the exchange name and cabinet number up the top of the page.
On 2 out of 3 of the exchanges cabinet 32 has fibre.
-
Yer would probably help if I gave you the exchange lol
Telephone Number 01903XXXXXX on Exchange WORTHING CENTRAL is served by Cabinet 32
-
That cabinet isn't FTTC enabled according to codelook but it's been wrong before.
Any new FTTC cabinet can be as much as 50-100m away from the cabinet (though 50m+ is in the very high end).
The newer VDSL Sidepods are just bolted on to the side of the PCP.
I'm not sure if the pods need an existing FTTC cabinet. I wouldn't think they do.
I've had a quick look oy Google maps and unfortunately none of the local cabinets seem to be numbered.
-
The newer VDSL Sidepods are just bolted on to the side of the PCP.
I'm not sure if the pods need an existing FTTC cabinet. I wouldn't think they do.
What about the optical link back to the head-end exchange? Taking that from an existing fibre cabinet would make the pod addition to the PCP an easy build.
Then there is, of course, the question of the power supply. My understanding is that the pods "piggy-back" their supply off the fibre cabinet.
Perhaps Black Sheep will be able to clarify the situation?
-
No Pod on the side just the thin old cabinet. All a bit odd but def no other cabinet
-
Looks like cabinet 32 and 33 do not have FTTC: https://www.telecom-tariffs.co.uk/codelook.htm?xid=242447&cabinets=15515
-
What about the optical link back to the head-end exchange? Taking that from an existing fibre cabinet would make the pod addition to the PCP an easy build.
Then there is, of course, the question of the power supply. My understanding is that the pods "piggy-back" their supply off the fibre cabinet.
Perhaps Black Sheep will be able to clarify the situation?
I'm aware they need power and fibre, and that pods currently source these from an existing DSLAM in situ.
I was more questioning whether a VDSL pod can be placed where no DSLAM exists already, with fibre and power being sourced specifically for the pod.
They can pull in fibre for a new stand alone DSLAM. No reason why not for a pod on its own.
They source local power for stand alone DSLAM... this is where I'm not so sure it can be done with a pod.
Is there enough space within the pod for its own power supply without piggy backing an existing DSLAM's power supply.
I haven't seen a single FTTC cabinet deployed near me in quite a while.
The VDSL pods are new(ish) and would be a cheaper and quicker deployment method than having to erect a plinth for a DSLAM/shell.
Edit: to answer my own question the power board is already there, it would just need a power supply sourced locally.
So it's very possible.
Not much space for backup batteries though.
-
No Pod on the side just the thin old cabinet. All a bit odd but def no other cabinet
I would contact OpenReach if i were you, just to double check.
Their Twitter team are often good at responding quickly.
Alternatively place an order. I wouldn't recommend a migration though as it may leave you without any current ADSL if the order fails.
-
Thanks All
I have tweated Openreach to see what they say.
-
@glennbtn I have checked some addresses in postcodes BN14 8NJ and 8LS and they have FTTC available from cabinet 32, the FTTC cab must be in the region of Harrison Road (8LS) as properties there get full speed FTTC estimates. Looks like codelook is wrong for that cabinet. :(
-
The main green cab is 5 doors away from me and there is no second cabinet anywhere to be seen. Bt have been here lots recently but running fibre ready for FTTP when it goes live, but not work has been done on the existing cab.
I checked with open reach who just said if it's on the website put in an order so I have placed an upgrade order with Zen and see what happens. Currently it still waiting for Open Reach to commit to a date.
-
@glennbtn If codelook is wrong maybe the FTTC has been enabled quite recently. This is google maps view in March 2019. I couldn't see another nearby cabinet.
https://www.google.co.uk/maps/@50.8261257,-0.3605926,3a,90y,286.81h,65.2t/data=!3m6!1e1!3m4!1sVqmgoG9AZHZXLUPWwEdy5Q!2e0!7i13312!8i6656 (https://www.google.co.uk/maps/@50.8261257,-0.3605926,3a,90y,286.81h,65.2t/data=!3m6!1e1!3m4!1sVqmgoG9AZHZXLUPWwEdy5Q!2e0!7i13312!8i6656)
If the cabinet has changed to a newer casing it could be an "all in one" where the old PCP and the FTTC cab are combined so only one cabinet is required. There are some pictures of the different cabs on this website somewhere. If it it still the old cab and there is no FTTC cab I am not sure what is going on. ???
-
Must say I've never seen a PCP replaced with an All In One.
I've only seen them used as an infill or for EO lines.
-
Def the really old style cab
Order still in waiting for Commit as I expected as that's usually done within an hour or so during the working day and been nearly 24 hours now. Guess someone is now scratching their head as to how it's been enabled for orders with no cab :lol:
-
Well funnily enough the upgrade is delayed
there is currently capacity issues on route
Might have something to do with no FTTC cab lol
-
I am about to give Zen a dig in the ribs regarding my order so hoping someone can tell me if I am correct.
If this is a capacity issue at a cab, I believe I should not be able to place an order but go on a waiting list. The https://www.broadbandchecker.btwholesale.com at the time of order did not show a capacity issue and still claims it's available. So in theory what Zen are telling me is incorrect?
Thanks
-
Are you using your address or landline telephone number when checking for a waiting list?
If you use your phone number and already have FTTC then it will always show available.
The waiting list only shows on an address check.
I know you don't have FTTC but I'd advise using the address check anyway.
Zen don't use the waiting list AFAIK.
Pretty much nobody does. It isn't a manual process and it's time consuming to manage.
After a set time period (i believe 3 months?) orders on the waiting list are automatically rejected and the whole process needs started again.
So ISP's just don't bother with it.
Any reported capacity issues aren't necessarily at the cabinet.
Although if there really is no cabinet I'm not surprised they can't find a free port on it ::)
I would nudge Zen all the same and request an update.