General Discussion
  >> Fibre Broadband


Register (or login) on our website and you will not see this ad.


  Print Thread
Standard User Nightglow
(learned) Tue 09-Jun-15 11:39:20
Print Post

Numerous Resyncs/Restarts


[link to this post]
 
Been having problems with my connection due to 300 metre of rotten aluminum cable, which is killing my speed, getting between 24-31Mb,my neighbour 80Mb, she only 60' away & on same DP & cable down lane to High Street where we connect to dodgy cable & which BTOR will not replace, depite it being the cause of all my problems & Ofcom can do nothing, despite me having a 'deadlock letter' & BT admitting my speed is well below what was quoted.
Fortnight ago, we had OR poking around clearing out blocked ducts where this cable is located.
Since then I have been getting numerous resync/restart, 2nd to 5th June a few, 6th to 8th June, had 7 in on day, a total of 13 for those dates.
Today 9th June, had 6 so far, it's getting beyond a joke now, & I'm at a loss as what to do.

It's all on DSLWebStats under KIAB.

Edited by Nightglow (Tue 09-Jun-15 11:49:12)

Standard User Nightglow
(learned) Tue 09-Jun-15 21:20:13
Print Post

Re: Numerous Resyncs/Restarts


[re: Nightglow] [link to this post]
 
Still getting these resyncs, same error listed on DSLWebStat, 'RDI: Remote Defect Indicator/DLM'.

Edited by Nightglow (Tue 09-Jun-15 21:21:01)

Standard User David_W
(fountain of knowledge) Tue 09-Jun-15 22:07:22
Print Post

Re: Numerous Resyncs/Restarts


[re: Nightglow] [link to this post]
 
The speed you were quoted is an estimate and nothing more.

All forms of DSL - be it ADSL or FTTC - are."best effort" services. The modest monthly income Openreach get from providing wholesale FTTC does not justify costly engineering work unless they are unable to deliver the universal service obligation. Unless the line condition issues are affecting voice telephony and there are no unused pairs remaining to swap your service to that are in better condition, there is little chance of the cable being replaced. This, of course, presumes that all the joints have been remade already and that the issue is definitely with the cable.

If you push too hard, it's possible that your ISP will terminate service on the grounds that they are prevented by the condition of the available line plant from delivering an acceptable standard of service. It's also possible Openreach will disconnect FTTC and mark your line as unsuitable for FTTC.


Ultimately you might face a difficult decision - is a slow and flaky FTTC service better than losing FTTC altogether and potentially be prevented from ordering FTTC again in the future?


If the problem doesn't affect a nearby neighbour, you could do a deal with that neighbour to order FTTC service at their address and connect to it using point to point wireless equipment. It's not an ideal solution, but self help might be the only way ahead here.


Register (or login) on our website and you will not see this ad.

Standard User Nightglow
(learned) Tue 09-Jun-15 22:22:29
Print Post

Re: Numerous Resyncs/Restarts


[re: David_W] [link to this post]
 
Before OR engineers started poking around & clearing ducts, connection was slow, but reliable to a degree, & seldom resynced.
When line was moved last December to rear pole, I got 49Mb, it's gradually it's fallen down to 24-31Mb,occasionally lower, & it will get worse according to engineer.
Since June 2nd there been about 25 resyncs, not every day, some days you have could have a couple, other days like today there been 7 resyncs.
There are no spare pairs, & I'm only about 450-500mtrs from the cabinet.
Have had numerous BTOR engineers sorting faults & they have all reported to have aluminum section replaced.

Edited by Nightglow (Tue 09-Jun-15 22:26:54)

Standard User shinerweb
(regular) Wed 10-Jun-15 06:38:41
Print Post

Re: Numerous Resyncs/Restarts


[re: Nightglow] [link to this post]
 
It's not likely to be the aluminium cabling itself causing the high number of dropouts. I too had a long run of aluminium cabling which did have an impact on my line performance but it should be a constant.
Your fault conditions are indicative of another fault although, it could still be related to the aluminium itself. For example, when copper meets aluminum or when the aluminium cabling meets any other metal in a connector, those joints may suffer with corrosion due to dissimilar metals which would be impacted further if moisture is present.
My point being, rather than using the fact that aluminium is present in your line, it's poor performing, please change it approach, try the "my line keeps disconnecting, a particular junction box/underground duct has suffered with bad connections in the past and is likely to be the fault - by the way, the fact it has aluminium cabling coming into that junction/duct is a probable point of failure" - or words to that effect.

That's not too far from the problem I had where my drop wire from our over head lines terminated in an underground chamber about 100m from my property. The 100 pair cable in that junction box was aluminium going to a junction box a further 200m down the road. The 100 pair connector unit was a type used on Poles and not ideally suited to being underground and often spent 90% of the year under 3ft of water. If it were not for the fact that any time an engineer lifted the 100 pair cable out of the water you could pretty much guarantee a few lines would lose their phone lines/broadband due to the joints breaking when moved, BTOR wouldn't have touched our cabling either.
Whilst they didn't remove the aluminum, they did re-wire the whole 100 pair and enclose it in a more suitably water resistant junction box. That at least made the 'mean time to failures' go out to 3-4 years instead of 3-4 months !! When ever it failed, the local engineers would always go check that junction box first and 9/10 it was inside that box.

So push for line is noisy, poorly functions on voice at times and oh by the way, broadband keeps dropping out too. eg. don't push too much on the "it's got aluminum in it, that's the fault"

--
About Me | PlusNet ADSL2
Standard User David_W
(fountain of knowledge) Wed 10-Jun-15 11:43:46
Print Post

Re: Numerous Resyncs/Restarts


[re: shinerweb] [link to this post]
 
In reply to a post by shinerweb:
So push for line is noisy, poorly functions on voice at times and oh by the way, broadband keeps dropping out too. eg. don't push too much on the "it's got aluminum in it, that's the fault"
That's a great summary of what I was saying.

If there are voice faults, report those as they have to be fixed. That said, don't report a fake voice fault, because that creates a high risk of an engineer visit charge when the fault cannot be replicated.

If all the joints on the problematic cable haven't been remade, it's worth trying to get that done. Joints can often be the source of faults, and they are often relatively simple to remake, especially if all that is needed is remaking the connection for your particular line rather than replacing an entire multi-pair joint.

The chance of cable being replaced for DSL only faults is low, unfortunately. Openreach will often take the view that the cost involved cannot be justified considering that there is no regulatory requirement being breached and the income they receive from the affected services is low. The risk is that Openreach will take the alternative approach of removing FTTC and marking the line(s) and address(es) as unable to receive FTTC in the availability database.


It is important that you don't offer your own diagnosis, as you are not in the position to diagnose the fault. As shinerweb indicates, you could say something along the lines of "Openreach engineers have indicated that part of the cable run is aluminium, which makes it prone to faults", but you really shouldn't be saying "part of the cable run is aluminium, which needs replacing".

Unfortunately, your room for manoeuvre with your current ISP is limited as you already have a deadlock letter. It might be worth your while porting out to one of the ISPs that specialises in chasing Openreach over faults, though you will have to pay for their service with no guarantee of a fix.

  Print Thread

Jump to