In reply to a post by nredwood:

Have you requested a tie pair change as yet? If not, may be time to do so

No i havent, as per your post here...
http://forums.thinkbroadband.com/general/t/3980072-b...
I held off on that. If you are saying go ahead with that now though i will

Will check Bebox firmware version again, was pretty sure i had updated it. I know it came with 8.2.23.0 and pretty certain i updated to 8.2.7.7. Then again maybe i just downloaded it and never got round to the update. {shrug}

To be honest i dont think a firmware update will cure the issue considering the same disconnect issues with 4 other routers ive tried. But ill give that a go also. Though i cant see the Bebox or updates suddenly making it superior to 4 other devices

However one thing... If it does solve things how in future can i be sure if/when any new firmwares come out i wont be back to square one if i update it again and the disconnects return? I think the underlying issue is a line or BE issue in some manner, and id rather have that fixed than patching things up and hoping for the best in the future. I will do as you mention though and check/try that if needed.

Dunno if its any use but in the mean time my TP-Link gives figures for Maximum possible thruput/sync.......
Max: Upstream rate = 1218 Kbps, Downstream rate = 20619 Kbps
and actual figures sync figures on the TP-Link ...
Path: Upstream rate = 1213 Kbps, Downstream rate = 18547 Kbps

How accurate they are though i dunno, the MAX figures seem to change (upon initial sync they are lower but after a few hours the MAX figures increase, i spose that could be a bug of the router so this info may be useless)

Will mess around with the Bebox AGAIN to get that info if its truely necessary to diagnose something? I dont see firmware helping but as said im willing to try, anything half sensible like that at this point im willing to try

@RobertoS Thanks for that, good to know, looks possibly like its something else, rather than my dangly old BT line then Im still guessing Exchange end and probably BE equipment in it in some manner. If thats the case ive little chance getting it fixed.

In general and some of the complaints ive had with their product including my disconnects they wont admit to any faults which could be their fault.

Reporting various issues (not just the disconnects) they have previously denied possible equipment faults to me, LINX faults and so much more in tickets....... They "escalate" things which never get fixed in regards to all of those things.

Ive just recently had a ticket back stating the recent short LINX issue didnt affect everyone.
How that works though when every customer of BE goes through LINX in some manner though for many sites is anyones guess (thats the type of reponse i get to queries now... The whole, oh no sir its not our fault ethos, i guess broken peering and routing only affects selected unlucky few on the same network, reporting things to them is utterly pointless, they just demand tests and hope by the time you have messed around the issue vanishes until it occurs again a few days, weeks, months down the road).

I wonder if this is why they have always reported it as a voice fault, see BT dont poke about at BE equipment in my exchange and find the issue is with their gear? Or maybe im just being paranoid now.

Edited by deleted (Sun 20-Mar-11 02:57:40)

Looking at your SNR graphs, it looks like the router is losing power and then coming back on again.

This is apparent with the slope as the SNR margin rises after coming back on. the final curve is caused by the router coming up to operating temperature.

This would also explain why other routers you have tried have the same issue - and your recent power cut is also evidence of power supply problems.

If there is a loss of power, the modem will restart showing in the logs as either a 'kernel cold restart' or 'kernel warm restart', and the router's log information will be lost.

The most likely explanation is that the OP's line is being reset at BE's end. Are the upstream HEC Errors (bebox) being zeroed after a resync and the router's log information retained?

In reply to a post by Anonymous:

If there is a loss of power, the modem will restart showing in the logs as either a 'kernel cold restart' or 'kernel warm restart', and the router's log information will be lost.

The most likely explanation is that the OP's line is being reset at BE's end. Are the upstream HEC Errors (bebox) being zeroed after a resync and the router's log information retained?

Yep i dont think its power related, atleast not my home end of things, maybe exchange????

Though i didnt check the routers log the second time i plugged the thing in. If it was/is power related nothing else in the home is affected. The recent power cut i doubt is anything to do with the situation, as said its rare for the area to have power cut issues (the one the area had is the first in about 1.5 - 2 years and it only lasted a couple of hours, apparantely it was scheduled also according to a neighbour, which i didnt know).

Router doesnt power off or reset when it happens either (all lights stay green apart from the light which indicates sync, that goes out as expected, flashes and then it resyncs).

Problems holding sync started the very first day i joined BE (December), with UKonline things were fine i had several months worth of uptime with UKonline, day of migration to BE sync issues started. To begin with i thought it was purely down to an neighbours Xmas decoration as touched on earlier in the thread, that was causing issues for several people in my street. Once that was removed my resync issues went from several a day to 1 or 2 every 24-48 hours and its been that way ever since. So highly unlikely its power related, atleast my end.

I havent had chance to plug the Bebox back in my sister and her children visited today and messed around on the computer and playstation so i havent had chance to muck around switching hardware around again. Ill check its logs when i do though

Highly unlikely its power related though IMO router doesnt reset itself, nothing else in home is affected and there were no issues with the prior ISP, it all started very first day the connection migrated over to BE.

Well, try and get the tie-pairs changed, that may fix it

In reply to a post by BatBoy:

Well, try and get the tie-pairs changed, that may fix it

Yep thats definately something i will ask them about. Oh and thanks again for the recent sensible posts and suggestions BatBoy, appreciated

In reply to a post by nonBEliever:

In reply to a post by BatBoy:

Well, try and get the tie-pairs changed, that may fix it

Yep thats definately something i will ask them about. Oh and thanks again for the recent sensible posts and suggestions BatBoy, appreciated

Yeah well, I think the problem is your end, but I hope you get it fixed. I'm quite happy with my BE connection, you should be too.

Two things I would do:

1) Check the bebox's log after a resync to see if the historical events have been retained (I'm sure they are).
2) Monitor the upstream HEC errors before and after a resync to see if they have been zeroed. BE's dslam has a bug which accumulates upstream HEC errors after a resync and only a line reset can zero them.

I don't believe it is tie pairs as your line would probably be noisy, however a switch to a different port/line card may resolve your issues.

Chris Stening is the new MD at BE.

BE's Address: 62 Lancaster Mews, London W2 3QG

Registered Office: 260 Bath Road, Slough, Berkshire SL1 4DX

Company Number: 5262862.

I would put your complaint in writing - pen and paper not email - and mark it private and personal so that his secretary does not open it.

You should be able to find more company info. at Companies House but it will cost you.

Hope this helps.
Pantagoon

Thanks to all concerned, forwarding a complaint about all issues with their service to the relevant persons and organisations.