Cable Forum - View Single Post

RichardCoulter · 12-04-2019, 15:56

I think that's what must have happened. I'm not FTTP, so they will be copper then.

When it was first announced that NTL would be using fibre optic, I assumed that this was throughout as nobody mentioned that the last bit would be copper. I really don't know why they didn't just make all installations FTTP instead of penny pinching for the last tiny part of the network.

The cables have been down for nearly nineteen years, do they degrade over time? My internet seems to be a lot faster since they were replaced!

I remember when cable first started here and it was TV only. Then, phone lines were introduced. Surely they must have futureproofed their system and didn't have to pull a new cable throughout all their system?!

IIRC, cable had to wait for permission to be granted to be able to offer telephony, so maybe they took a gamble on it being granted and laid all the cables at the same time (which paid off).

12-04-2019, 15:56	#17
RichardCoulter cf.mega poster Join Date: Jan 2008 Posts: 10,061	Re: Will VM charge for damaged cable? I think that's what must have happened. I'm not FTTP, so they will be copper then. When it was first announced that NTL would be using fibre optic, I assumed that this was throughout as nobody mentioned that the last bit would be copper. I really don't know why they didn't just make all installations FTTP instead of penny pinching for the last tiny part of the network. The cables have been down for nearly nineteen years, do they degrade over time? My internet seems to be a lot faster since they were replaced! I remember when cable first started here and it was TV only. Then, phone lines were introduced. Surely they must have futureproofed their system and didn't have to pull a new cable throughout all their system?! IIRC, cable had to wait for permission to be granted to be able to offer telephony, so maybe they took a gamble on it being granted and laid all the cables at the same time (which paid off). Last edited by RichardCoulter; 12-04-2019 at 16:00. Reason: Typo.