Well, I hooked it up to the test socket overnight and when I awoke the connection up time was 30 minutes. So it certainly had several drops overnight.

No ring wire because no extensions

Yes if they can see the disconnects they will try and figure it out, but have you not noticed the exceptionally high sync the modem is trying...looks so much more like firmware is a bit foobar for long lines with that router, than any actual noise fault.

That exceptionally high sync can only be put to bed by using a diff router.

In reply to a post by brandscill:

So it certainly had several drops overnight.

What's router logs say about those discons?

but have you not noticed the exceptionally high sync the modem is trying...

Yes I had, hence my first reply to the OP. Could always be duff equipment in the exchange.

In reply to a post by XRaySpeX:

In reply to a post by brandscill:

So it certainly had several drops overnight.

What's router logs say about those discons?

7/26/2012 19:6:23> Configuration Change!
7/26/2012 19:6:23> netMakeChannDial: err=-3000 rn_p=8074451c
7/26/2012 19:6:24> Last errorlog repeat 2 Times
7/26/2012 19:6:29> Firewall: Filter no port UDP packet!
7/26/2012 19:6:31> Last errorlog repeat 5 Times
7/26/2012 19:6:31> netMakeChannDial: err=-3000 rn_p=8074451c
7/26/2012 19:6:32> Last errorlog repeat 5 Times
7/26/2012 19:6:41> netMakeChannDial: err=-3000 rn_p=8074451c
7/26/2012 19:6:41> Firewall: Filter no port UDP packet!
7/26/2012 19:6:41> netMakeChannDial: err=-3000 rn_p=8074451c
7/26/2012 19:6:41> Last errorlog repeat 1 Times
7/26/2012 19:6:42> netMakeChannDial: err=-3000 rn_p=8074451c
7/26/2012 19:6:43> Last errorlog repeat 5 Times
7/26/2012 19:6:47> Firewall: Filter no port UDP packet!
7/26/2012 19:6:49> Last errorlog repeat 1 Times
7/26/2012 19:6:51> netMakeChannDial: err=-3000 rn_p=8074451c


Those aren't from last night I know, this things keeps about 8 mins of logs if that. Useless!

In reply to a post by XRaySpeX:

That exceptionally high sync can only be put to bed by using a diff router.

In that case, will I be charged for the BT guy coming out? I did everything first line tech support asked, changed micro filter, tried another Zyxel router (they sent two for some unknown reason) and I also tried the test socket. All have countless drops

The Openreach engineer doesn't raise charges, just fills in a report which goes back to the ISP, it's them that decides where and what to do with any charges.

Things to check the engineer does;

Runs an end to end pair quality test, be nosy look over their shoulder, show interest and ask them to explain the results.
No more than 10 ohms difference in the legs, then closer the better.
Nice high AC balance at least 55db, but the higher the better.
Have them watch the error counter on their JDSU/Efo tester whilst using the phone at the same time. Should be little or none.
Look and see what thier kit syncs at, ask them what the average sync rate for the area might be.
Are there any better E-sides that your line might be on ?
They could ring up Wholesale and have them do comparative testing with both your and their kit sync, maybe ask what the RRTC history looks like.

Who knows, maybe it's a 'tickle' and they will just know the cause and sort it.

If it is your router, then you are back to plan A, arguing with the ISP that you did all the checks required by them, and were using kit recently supplied by them ....

I would ask all that but I won't be the one waiting in. It's my birthday and my girlfriend has taken the day of work to prepare some surprise whilst visiting me. She said as she'd need to be home in the morning she doesn't mind waiting in on my behalf.

I'll write down some things for her to ask and hopefully she will but she is the least technically minded person you'll come across really :/

Guess it's just a wait and see game

So far tonight we've had some decent uptime though!

Link Status: Up
WAN IP Address: *.*.*.*
Upstream Speed: 448 kbps
Downstream Speed: 5312 kbps
Node-Link Status TxPkts RxPkts Errors Tx B/s Rx B/s UpTime
1-PPPoA Up 5231093 8930905 0 26136 36568 2:33:23

DSL Line Status Diagnostics


relative capacity occupation: 62%
noise margin upstream: 17.0 db
output power downstream: 19.5 dbm
attenuation upstream: 29.5 db
carrier load: number of bits per symbol(tone)
tone 0- 31: 00 00 00 04 66 77 77 88 77 77 77 76 65 55 42 20
tone 32- 63: 00 44 67 99 ab bc dd ad dd dd ee dd dd ed dd dc
tone 64- 95: 0c dc cd dd cd dc a9 bb cb bb cb bb cb cb cc bb
tone 96-127: bc cb ba aa ba bb ba ab ab aa aa ba aa aa aa 88
tone 128-159: 77 89 99 99 99 99 99 98 49 98 78 86 45 36 66 76
tone 160-191: 52 46 52 74 75 74 62 56 76 65 56 65 26 46 66 66
tone 192-223: 56 35 44 22 22 22 22 22 33 20 32 33 30 32 32 22
tone 224-255: 33 00 23 00 00 00 00 00 00 00 00 00 00 00 00 00
relative capacity occupation: 113%
noise margin downstream: 3.5 db
output power upstream: 12.5 dbm
attenuation downstream: 61.0 db
carrier load: number of bits per symbol(tone)
tone 0- 31: 00 00 00 04 66 77 77 88 77 77 77 76 65 55 42 20
tone 32- 63: 00 44 67 99 ab bc dd ad dd dd ee dd dd ed dd dc
tone 64- 95: 0c dc cd dd cd dc a9 bb cb bb cb bb cb cb cc bb
tone 96-127: bc cb ba aa ba bb ba ab ab aa aa ba aa aa aa 88
tone 128-159: 77 89 99 99 99 99 99 98 49 98 78 86 45 36 66 76
tone 160-191: 52 46 52 74 75 74 62 56 76 65 56 65 26 46 66 66
tone 192-223: 56 35 44 22 22 22 22 22 33 20 32 33 30 32 32 22
tone 224-255: 33 00 23 00 00 00 00 00 00 00 00 00 00 00 00 00


I'm hoping that maybe over the next couple of days things really begin to improve and perhaps I can cancel the visit!