So had app for openreach to come put in FFTP, wired it all up and now not working, said there is a fault ? Said engineer would be out following day and low and behold no visit so had to contact BT who tell me it needs specialist engineer but that could take up until the 10th ?
After checking otther usual suppliers of broadband / fibre i see only 1 offering 1000mb's so is it even in my area ? Openreach site says it is but i am beggining to think they have not fully completed the work and are trying to sell it and play catch up without it being fully available ?
Just wondering if anyone else has this issue ?
I am very sceptical that they will be out before the 10th and feel like it will be another delay. If i changed suppliers to the other company i found would i still have the same issue as its still going to be openreach dealing with it ?
Any ISP who uses the openreach network will have same problem providing your connection. Changing ISP will just push you back in openreach queue
If there was no Openreach FTTP network availability then BT ( or anyone else using Openreach ) couldn’t order it for you , and the OR tech presumably wouldn’t have bothered fitting a CSP and ONT.
If you are the first connection on your CBT , or maybe the first connection on the splitter, it’s possible that OR have called the PON off as ready for service, but that’s not true , or it could be the physical path is OK , but some configuration issue .
If the tech fitted an ONT what lights are lit , and if the PON light is lit , is is steady or flashing ?
Its odd that your ONT would be initially flashing green PON , that means the ONT is receiving ‘light’ but the headend isn’t ‘talking’ to the ONT ( the ONT isn’t authenticated on the network ) that can be a relatively easy fix , the serial number of the ONT needs to be entered into the list of authorised ‘members’ of the network, a red PON light signifies that the ONT is not receiving light or it’s not of a sufficient level ( of power ) for the ONT to communicate with the headend, so if anything your connection is worse than it was.
There was a similar issue on another thread ( AFAIR ) which seemed to be down to the ONT manufacturer and headend manufacturer, the implication was that the ONT firmware wasn’t up-to date, so they were not ‘talking’ to each other.
Hopefully it won’t take too long to sort out
iniltous i appreciate your time to reply this was very helpful and gives me something to go off incase of further issues, lets hope they seem to know what the issue is and resolve it soon and if not i can at least try help them thanks to your help.