Quiet Line Test?

Started by gyruss, Jun 04, 2010, 21:14:38

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Rik

The charge only applies if it's a 'no fault found' or something your side of the test socket.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

gyruss

Tonights BT speedtest is dire..

Download speedachieved during the test was - 267 Kbps
For your connection, the acceptable range of speedsis 400-2000 Kbps.
Additional Information:
Your DSL Connection Rate :448 Kbps(DOWN-STREAM), 128 Kbps(UP-STREAM)
IP Profile for your line is - 1371 Kbps
The throughput of Best Efforts (BE) classes achieved during the test is - 20.22:35.21:44.57 (SBE:NBE:PBE)
These figures represent the ratio while sententiously passing Sub BE, Normal BE and Priority BE marked traffic.

The results of this test will vary depending on the way your ISP has decided to use these traffic classes.


Ping test to www.idnet.net:
Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=53ms TTL=59
Reply from 212.69.36.10: bytes=32 time=52ms TTL=59
Reply from 212.69.36.10: bytes=32 time=51ms TTL=59
Reply from 212.69.36.10: bytes=32 time=50ms TTL=59
Reply from 212.69.36.10: bytes=32 time=53ms TTL=59
Reply from 212.69.36.10: bytes=32 time=52ms TTL=59
Reply from 212.69.36.10: bytes=32 time=51ms TTL=59
Reply from 212.69.36.10: bytes=32 time=54ms TTL=59
Reply from 212.69.36.10: bytes=32 time=53ms TTL=59
Reply from 212.69.36.10: bytes=32 time=52ms TTL=59
Reply from 212.69.36.10: bytes=32 time=55ms TTL=59
Request timed out.
Reply from 212.69.36.10: bytes=32 time=53ms TTL=59
Request timed out.
Reply from 212.69.36.10: bytes=32 time=49ms TTL=59
Reply from 212.69.36.10: bytes=32 time=52ms TTL=59
Request timed out.
Reply from 212.69.36.10: bytes=32 time=53ms TTL=59
Reply from 212.69.36.10: bytes=32 time=52ms TTL=59
Reply from 212.69.36.10: bytes=32 time=51ms TTL=59
Reply from 212.69.36.10: bytes=32 time=50ms TTL=59
Reply from 212.69.36.10: bytes=32 time=50ms TTL=59
Reply from 212.69.36.10: bytes=32 time=50ms TTL=59
Reply from 212.69.36.10: bytes=32 time=54ms TTL=59
Reply from 212.69.36.10: bytes=32 time=53ms TTL=59
Reply from 212.69.36.10: bytes=32 time=52ms TTL=59
Reply from 212.69.36.10: bytes=32 time=55ms TTL=59
Reply from 212.69.36.10: bytes=32 time=54ms TTL=59
Reply from 212.69.36.10: bytes=32 time=54ms TTL=59
Reply from 212.69.36.10: bytes=32 time=54ms TTL=59

and...

is this kind of finishing on BT boxes outside of ones property.. normal?  because this is what I can see on mine.

Wires visible are a white n green, a green and a black.  Its a good job i don't fix pc's and laptops for my customers like this :).. but heck.. this is shoddy work right? and considering all my trouble and the 'noise' on my line.. i'm looking for possible causes and is it likely however crazy that these wires 'could' be picking up interference and passing it through to my phone as noise?


Jase


gyruss

Jase


pctech

That looks quite old as it has the really old BT logo on it

Rik

It certainly doesn't appear to be wired to standard. Might be worth sending the pic to support and see if they think they can get BT out to fix it.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

gyruss

Sent pic.  This noise issue i'm getting seems to be a bit erratic as sometimes can have a clear line, and at other times, crackle and lots of, but tonight i'm on a 383k profile when i know my line is normally more than 20 times this.. sooo.........

Have also placed yet another order with adslnation for another xte2005 filtered plate and another run of twisted pair rj11>rj11 cable. (for the hell of it, £22)
Jase


Rik

Crackling is usually a corroded joint, if there's water ingress, that could well be your junction box.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

gyruss

James from IDNET replied along the lines of,   your contract for your line is with BT, therefore you should call BT to sort this out.

ok no problem, i had heard sometimes that ISP's help by providing assists in this way if their customers are affected, but will call them anyway.  I believe in fact that an isp can request the openreach special faults call for 'broadband' for the customers too.  I'll likely request that.


Today the XTE2005 adslnation faceplate + Pro+ RJ11 > RJ11 cable has arrived that i ordered, so tonight and tomorrow will fit that.    Running it along a slightly longer route, but this time fitting the router nearer to the inside support walls and acoustic wise, even more solid than previously.    I already have the xte2005 and twisted pair carefully fitted and radio test done

Once i've done this test with new cable and new xte2005, and left it to see how it affects my profile, i am going to ring BT and restate my case.    Only this time i will tell them that i understand about the charge they would apply if found to be internal cabling, but once i provide their engineer with my evidence to prove its not my wiring (or router which was replaced twice due to this resync constant issue)

384k profile is a joke, and i've suffered this long enough despite best efforts. :/
Jase


pctech

The trick I gather is to report a voice fault and not to mention broadband otherwise they will send you back in the direction of your ISP.

Rik

Very much so, Mitch. IDNet are trying to save you  money, Gyruss. If they call out an engineer, a charge is quite likely.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Adam

BT may seem impossible to deal with, but you really just need to say the right things and persevere. I had a fault a few years ago which was sorted right away (they replaced the wire to the telegraph pole). As previously said, just don't mention broadband and keep it as a voice fault.
Adam

gyruss

Tonight, since changng my cable and faceplate for the same like-for-like.. getting this:





I'lll see how this shapes up, but if this holds, i'll tack the rest of the cable (the last 8 meters) into place.

Jase


Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

gyruss

After yet more resyncs at various points yesterday (saturday):

bought and installed a Netgear DG834Gv5 so that i've got something other than a cisco/linksys for testing this awful internet connection i am cursed with here.

Its connected at 5888 kbps down / 928 kbps up  (slightly less downstream than previous router)  i've seen this house connection peak at 7k approx


So this week i have replaced

the faceplate to another ADSLnation XTE-2005,
the twisted pair cabling to more pro+ (RJ11 to RJ11)
the router from a Cisco/Linksys 320N to a cheaper Netgear DG834Gv5



Surely.. SURELY after doing all this, we can rule out my internal wiring?    I do desktop support for a very large company, so cabling is a routine thing for me.   I just get the feeling that I'm going to end up getting my line fully tested now and even though my cabling is fine, will have one of the more unhelpful engineers who will make every attempt to make it a chargeable call out anyway :/
Jase


Rik

Remind me, have you tried using the test socket?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

gyruss

Yes had the setup on the test socket for 3 days.. only drawback of the test socket is having to use the 'soap-on-a-rope' filter instead.  was pretty much same resync scenario alot
Jase


gyruss

Download speed achieved during the test was - 1524 Kbps
For your connection, the acceptable range of speeds is 400-1920 Kbps.
Additional Information:
Assured Rate IP profile on your line is - 1920 Kbps

profile down again which is good evidence of a constant resyncing connection.
Jase


gyruss

anyone else got a netgear dg834gv5 router? and if so, have you got any 3rd party router stat monitoring tools working with it?   (eg. dmt tool or similar)
Jase


Steve

Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

gyruss

ahh found it on that page, ta,.. seems i need the plug n play cut down version according to that link will dl now.  thx.
Jase


gyruss

The resyncs continue, with complete change of cabling, faceplate and router now.

The following screen suggests a high noise issue?



also just come off a phone call with my mother and the call quality was absolutely horrendous too, lots of 'noise' on the line.  same fault as always .
Jase


Rik

Contact aupport and point them at this thread. I don't think there's anything else you can try and that margin suggests a banded profile to me.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

gyruss

have got routerstats lite working now, the noise margin has been a steady 14.5 for a while now.

I don't know if idnet support will even be interested in this thread or my problem however as i've tried that avenue before during the course of this fault diagnosis.
Jase


Rik

What's the router report for the noise margin? If it's swinging by 14db that's a very noisy line.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.