BT and more line problems

Called my isp today to find out what was going on with my hard cap by bt.
They told me i had over 140000 retransmission in a 14 day period, think that's crc errors then
So they told me they going to run a test and see what's going on and i should call back in an hour.
One hour later and they tell me they could not carry out the test as something was already running a test and they had no idea what.
They have now logged a fault with bt, and just to make sure on my end i will now be using four different routers over a four day period from the test socket to test results with my isp
So tonight its a netgear dg834gt then 24 hours later its a dg384 v2 then a belkin F6D4630-4 V1 and then a Linksys WAG54GS
this has been a problem since November that i was sure that BT had fixed
my 1st fault in November was that my line would only work if i used my phone, so a bt engineer came out and swapped my line from the house to the cab and that sorted that problem but introduced a new one, that every time i used the phone the adsl would drop.
So after 2 more engineers my line from the cab to the exchange was changed and that fixed that problem and had great connection for 6 days at 4.5mb profile
i turned of the router to move it to the face plate to go wireless and my snr was raised from 6 to 12
So i contacted my isp and have done so for the last month about this and my line is now hard capped at 3070
So contacted my isp yesterday and they said they would request my snr be reset and i should call back today about that.
i call back today and have been told i have over 140000 retransmissions and they want to do a line test and i should call back in one hour again .
after one hour i call back and have been told they could not do a test as some one was already doing a test on my line and they had no idea who. so they have now logged a fault with BT
I am just so @@@@@ off with it all now

Edited by deleted (Fri 28-Jan-11 23:51:24)

Swapping routers while they are trying to sort out the problem is going to help how?

Isp would like to be sure its not my router that is causing the problems
So they can look at each day and make sure its the same and that it must be BTs fault

ok so i have been told that the errors are on the upstream side of things
this is upstream graph when a phone call is made upstream errors burst

and this is my ping on a good day

ping and jitter

done all the master socket test once again and still the same
no phones are plugged in and i called my number from my mobile

Just cant seem to get this sorted even after they stuck me on a new pair twice now
Bt have told my ISP that and engineer visit would be needed but had all this the last time and took 3 before they found the fault and the call out fee was cancelled

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 23 | 23 | 0 | 0 | 1 | 0 |
| lns18.the.dsl.enta.net - 9 | 23 | 21 | 25 | 25 | 33 | 25 |
| gi1-8.the.dist.dsl.enta.net - 0 | 23 | 23 | 25 | 25 | 28 | 25 |
| te2-2.telehouse-east3.dsl.enta.net - 9 | 23 | 21 | 25 | 26 | 50 | 25 |
| te5-2.telehouse-east.core.enta.net - 9 | 23 | 21 | 25 | 25 | 29 | 25 |
| te5-1.telehouse-east2.core.enta.net - 18 | 23 | 19 | 25 | 26 | 38 | 26 |
| 212.58.238.177 - 18 | 23 | 19 | 25 | 25 | 27 | 25 |
| 212.58.238.153 - 5 | 23 | 22 | 25 | 26 | 37 | 29 |
| 212.58.239.62 - 9 | 23 | 21 | 25 | 25 | 26 | 26 |
| 212.58.251.44 - 5 | 23 | 22 | 25 | 26 | 31 | 26 |
| bbc-vip115.telhc.bbc.co.uk - 5 | 23 | 22 | 25 | 25 | 26 | 26 |
|________________________________________________|______|______|______|______|______|______|

In reply to a post by iwish:

Looks better and easier to read like this :-

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |   23 |   23 |    0 |    0 |    1 |    0 |
|                  lns18.the.dsl.enta.net -    9 |   23 |   21 |   25 |   25 |   33 |   25 |
|             gi1-8.the.dist.dsl.enta.net -    0 |   23 |   23 |   25 |   25 |   28 |   25 |
|      te2-2.telehouse-east3.dsl.enta.net -    9 |   23 |   21 |   25 |   26 |   50 |   25 |
|      te5-2.telehouse-east.core.enta.net -    9 |   23 |   21 |   25 |   25 |   29 |   25 |
|     te5-1.telehouse-east2.core.enta.net -   18 |   23 |   19 |   25 |   26 |   38 |   26 |
|                          212.58.238.177 -   18 |   23 |   19 |   25 |   25 |   27 |   25 |
|                          212.58.238.153 -    5 |   23 |   22 |   25 |   26 |   37 |   29 |
|                           212.58.239.62 -    9 |   23 |   21 |   25 |   25 |   26 |   26 |
|                           212.58.251.44 -    5 |   23 |   22 |   25 |   26 |   31 |   26 |
|              bbc-vip115.telhc.bbc.co.uk -    5 |   23 |   22 |   25 |   25 |   26 |   26 |
|________________________________________________|______|______|______|______|______|______|

(See the added line feed).

Edited by RobertoS (Tue 01-Feb-11 07:54:12)

Thanks

If you click the Quote button against my post where I have aligned things you will see at the start of the table the letters pre in square brackets, and the corresponding /pre at the end of the table. I've just edited to add a line space as well, but it auto-adds one at the end - see the edited version (in Quote) as well.

Works well for most sets of line stats as well, though occasional slight problems that need spaces adding or taking out. Or sometimes in a table you need to copy/paste the gap between two items to add to or replace the gap between two others, as that copies the tab characters in there which of course you cannot type.

Abandon the quote once you have seen it .

Edited by RobertoS (Tue 01-Feb-11 07:58:01)

does the code tag make a decent job ? :-

Text

1 23 45 67 89

Host                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev  1. home                                                      0.0% 58343    1.8   1.1   0.9 126.0   9.0 2. anchor-hg-1-lo100.router.demon.net                        0.9% 58343   37.8  32.4  31.8 519.5  13.5  3. anchor-access-3-s2004.router.demon.net                    1.0% 58343   35.1  33.3  31.8 446.7  17.4 4. anchor-inside-4-g1-0-3.router.demon.net                   0.2% 58343   34.9  32.8  31.8 538.0  11.1  5. anchor-border-2-g4-0-0.router.demon.net                   0.9% 58343   37.6  33.1  31.9 500.2  13.9 6. 195.11.50.25                                              0.8% 58343   34.1  34.3  31.8 619.0  30.3  7. vlan821.sw1.c16.iph.lon.as5587.net                        0.3% 58342   34.2  34.2  32.0 539.3  12.4 8. demon-web-1.dvs.demon.net                                 1.1% 58342   36.7  34.1  31.9 478.9  15.5

note the decent sample size

Bursty noise is something ADSL has to accept sometimes, e.g. it can be as simple as a train going by on an electric line every 30 minutes.

14,000 CRC errors a day (if that is them) is not that bad. Is it affecting throughput?

If these are just upstream it is more complex, since upstream has no DLM, and upstream is more likely to be affected by telephony issues e.g. filters/wiring/joints