|
|
If you cease the line first then the new order will not require an engineer to visit - it will use the deactivated circuit. If you order before the cease then an enginner visit will be required to fit a new master socket and possibly install new cabling from you distribution point or cabinet.No idea how likely this is to rectify the situation.
Ordering a whole new line seems like a possible solution. I don't care about the cost at the moment, I just want it sorted.
Can anyone suggest if leaving the talk talk account as it is for the time being, and ordering a brand new service from another provider, i.e. new phone line, new number and then a broadband service would work?
|
|
|
Answer - the phone no longer routes from the exchange to 4, but to 19. Shifting the FTTC provision from 4 to 19 (FTTC cab) was for some reason not done.
That's kinda what I'd figured all along [smug] The OP said as much in his first post.
My guess is the D-side cable which originally fed from cab 4 has some major issues, and the cheapest option to fix these is to reroute via cab 19. (maybe a major road crossing on the original route meaning huge costs to replace cable)
In doing this Openreach have still got an FTTC port provisioned for this line in cab 4 ..... records clearly haven't been updated, and the chances of the FTTC being made live on cab 19 to clear this issue as a fault seem slim to none.
I stick with my original diagnosis. Cease both existing line and FTTC, then have reprovided ......
On the plus side, once complete, the OP is going to have much faster FTTC speeds !
|
|
|
I stick with my original diagnosis. Cease both existing line and FTTC, then have reprovided ......
On the plus side, once complete, the OP is going to have much faster FTTC speeds !
Order new line & FTTC and then cease TT line and FTTC just to negate any chance of the existing Frankenstein line being reused
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
|
Can anyone confirm if an fttc ip profile can have an upstream rate of 0.45 Mbps?
|
|
|
It cannot.
The downstream IP Profile on FTTC is the sync x 0.9679. The upstream IP Profile on FTTC is always exactly 20Mbps, 10Mbps or 2Mbps depending on the Openreach product in use, and quite independent of the sync speed.
0.45 will be the 448kbps upstream of ADSLx. Either ADSL Max (G.DMT) or ADSL2+ with a cap which some ISPs impose.
My broadband basic info/help site - www.robertos.me.uk | Domains,site and mail hosting - Tsohost.
Connection - Plusnet UnLim Fibre (FTTC). Sync ~ 57.2/15.0Mbps @ 600m. - IPv4 BQM IPv6 BQM
"Angels can fly because they can take themselves lightly." - G K Chesterton.
|
|
|
Ok, thanks for that.
I have a theory, I believe the OP was the only line meeting both the following-
Receiving a fttc service from cab 4 AND is now being served by cab 19.
Edited by deleted (Wed 21-Jan-15 19:50:41)
|
|
|
Answer - the phone no longer routes from the exchange to 4, but to 19. Shifting the FTTC provision from 4 to 19 (FTTC cab) was for some reason not done.
That's kinda what I'd figured all along [smug] The OP said as much in his first post.
My guess is the D-side cable which originally fed from cab 4 has some major issues, and the cheapest option to fix these is to reroute via cab 19. (maybe a major road crossing on the original route meaning huge costs to replace cable)
In doing this Openreach have still got an FTTC port provisioned for this line in cab 4 ..... records clearly haven't been updated, and the chances of the FTTC being made live on cab 19 to clear this issue as a fault seem slim to none.
I stick with my original diagnosis. Cease both existing line and FTTC, then have reprovided ......
On the plus side, once complete, the OP is going to have much faster FTTC speeds !
Yes, if it works!  Theres always the possibility that the cabling path already used will be used again, but it is certainly an option to be explored if and when I have exhausted the TT channels. I will push with them still until they say they are at a stalemate, at least then I can request a deadlock letter, and escalate the complaint thought the ADR scheme and onto the Communications Ombudsman Service which TT have signed up to. That will be at the same time as a complaint being channelled into Openreach and possibly up the food chain in BT as well.
I think a structured approach may be best, although may string thing out for a while yet.
|
|
|
|
It sounds like you have more stamina than I, by the sounds of it, I might have given up on TT by this stage.
Although the "problematic" cable route may be re-used, I find it highly unlikely a fttc engineer will connect a new provisioned line to the "incorrect" cabinet.
On that note, make sure you order a 76Mbps FTTC service which requires an engineer visit!
|
|
|
You certainly seem to be between a rock and a hard place.
Whilst your problem should be dealt with by TT but they have failed, before you either cancel and re-order, or order a new line then cancel, why not try contacting the CEO of Openreach.
I know that you have no contract with OR, but nothing to loose.
His email is [email protected]
Keep your email concise and explain the problem as you have done in your posts here and hopefully you will get a result.
Good luck.
Cheers!
Clive
Andrews & Arnold FTTC
DrayTek Vigor 2920Vn
Andrews & Arnold Data SIM
HUAWEI E5776
|
|
|
Edit: ^ that is the sort of Email address I was thinking of in my previous post. My opinion is: Do that.
What I wrote, pre-edit:
If you're comfortable with the financial side of things, I suppose you could take both routes - order a new 80/20 service right now, AND don't give up on the existing problem. I wouldn't do it, but if you've got the money and patience, then maybe it couldn't do any harm? Also, the non-ceasing of your TT line would ensure that the "Frankenstein line" wouldn't physically be touched (i.e., used as your new line). So then once you have a new, working FTTC service you can decide exactly what to do with the horrible existing mess.
I want a photo of the 6 lines into your house, from the outside, if you go for that, though
Edited by deleted (Wed 21-Jan-15 22:26:41)
|