THANK YOU!!!!

You wouldn't happen to want to make a (very informed) guess as to what the problem might be and possible timescale for a fix?

MM

I wouldnt take a guess, any of the usual suspects, card, harness, splitters, strips etc.
Issue should be identified and resolved within the next few days.

Thank you. Can I assume the problem was detected remotely as no-one's been near the cab since the original activation date of 26 Sept, although perhaps the problem was known about before then. Fortunately the rest of us with FTTC connections via that cab aren't having problems, or rather mine's OK and none of my neighbours have complained!

Perhaps you are now asking for TMI? Risking the goose that lays the golden eggs?

It would have been found when the openreach tech or contractor attempted to activate the line at the AIO.

Update.
Engineer visited WRVAUX 54 this morning, the first time anyone has been near it for two weeks or more (we had put a telltale on the doors) and my neighbour's installation is now due for tomorrow. Why of why couldn't PlusNet, BT Wholesale or Openreach been honest and given a proper honest answer when asked for the cause of the delay.

Edit: BT Retail corrected to BT Wholesale

Edited by deleted (Wed 09-Oct-19 22:30:01)

Could simply have been miscommunication as often happens when messages are passed between OpenReach, BT Wholesale then the ISP.

The problem is stated as not being at the cabinet, ports are available, but rather at the exchange and that no port is available

The response is often about ports at the exchange when they actually mean the street DSLAM.

Could have been something as simple as a line card fault meaning no free working ports were available.
The original reason given might have been correct, just the location of the ports in question being wrong.

I'm with you on wishing the initial info given should be more accurate.

MCM

Try the scenario below that may exist elsewhere where AIOs were provided for small clusters (eg less than the AIO capacity). Saves a fortune on remote truck rolls, but is usually rural unlike yours!

As your AIO was a community funded one they may have wired all the premises covered straight into the VDSL cards, Thus customers could be configured remotely, When they tried to do your neighbour the port had a fault on so had to have a visit that would not normally be needed!

The ISP would not know this and would just be told there was a faulty port. Front office people tend to think this is exchange rather than Cab and you know no-one has been to the cab so think no-one would know there was a faulty port.

I've never known OpenReach to connect tie cables to every line just because the PCP has less capacity than the serving DSLAM.

Don't see why a CFP would be any different.

I'm no engineer and happy to be educated further on this but I was under the impression an ADSL line can't be jumpered to the line card in the FTTC cabinet anyway.

If I cease my line tomorrow it's done remotely, left jumpered to the FTTC cabinet so it can be reprovisioned without a cabinet visit.

If I downgrade to ADSL then my line is disconnected from the tie cables on the cabinet.

An upgrade to FTTC would need a further visit to the cabinet.

It was the advise given to my by OpenReach to get my line changed from the ECI DSLAM to the Huawei DSLAM on my PCP.

A downgrade to ADSL would be needed to have my line disconnected from the ECI tie pair, a cease wouldn't make a difference unless that port was recycled at a later date.

Has that changed or was that never the case?