Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[notaclue]

After a few more calls, I have this reported as a fault and it's in the first stage? (ie they are going to watch my line and then do nothing, as there is apparently nothing wrong with it according to their tests, no mention of an engineer.)

Also boost, why the sad face?

[konrado5]

Could you attach your Hlog, QLN and other graphs after removing of fault?

Best regards
konrado5

[boost]

After a few more calls, I have this reported as a fault and it's in the first stage? (ie they are going to watch my line and then do nothing, as there is apparently nothing wrong with it according to their tests, no mention of an engineer.)

Also boost, why the sad face?

http://forum.kitz.co.uk/index.php?topic=13794.msg259895#msg259895

Could be coincidence I suppose or they are just the most widely deployed but the alarming majority of my faults have been based off these DSLAMs.

TalkTalk use a very similar IFTN 71C6 but BT/non-LLU use 71C8.

I'd do wonder what make/model this DSLAM is tbh.

[kitz]

Boost I'd keep at BT and if necessary ask to speak to the technical team or 2nd line support.   If you got the Indian call centre, unfortunately these people are unlikely to have a clue how things work.   

You need to stress how your upstream was previously 2Mb, but you can now only get circa 400Kbps.  If you can get through to second line support, they are more likely to understand SNR Margin and the impact it can have on the line.  It wont harm either posting on their forums as well.  One of their tech team may see your graphs. 

Good luck

[boost]

Boost I'd keep at BT and if necessary ask to speak to the technical team or 2nd line support.   If you got the Indian call centre, unfortunately these people are unlikely to have a clue how things work.   

You need to stress how your upstream was previously 2Mb, but you can now only get circa 400Kbps.  If you can get through to second line support, they are more likely to understand SNR Margin and the impact it can have on the line.  It wont harm either posting on their forums as well.  One of their tech team may see your graphs. 

Good luck

We go via another (very poor) CP for the bulk of our ADSL stuff. I feel too far removed to start shouting about something I can't quite prove as yet.

Getting closer though, with help from this excellent forum

[AdriHD]

Can the OP do us a favour and let us know what exchange he/she is on?

http://www.samknows.com/exchange_search

On that website, cuse your postcode, NOT your number. It gets the nearest available exchange. Can you pop the code of the exchange back? it'll be something like NDSIT (is what mines called)

Usually all capital letters in that form

Cheers,
A

[burakkucat]

it'll be something like NDSIT (is what mines called)

b*cat's sleepy eye recognises that as "North Downs Sittingbourne", Kent. 

[notaclue]

Engineer just left my property. (Like 10 mins ago)

My HLog and QLN are a bit different.

I also managed to snap some pics of the engineers device while it was testing my adsl, if anyone wants pics i will gladly oblige.

[konrado5]

You have ADSL2 or G.DMT instead ADSL2+. Why?

I also managed to snap some pics of the engineers device while it was testing my adsl, if anyone wants pics i will gladly oblige.

Could you attach pics of the engineers device?
Could you attach SNR margin graph and general router stats?

[notaclue]

You have ADSL2 or G.DMT instead ADSL2+. Why?

I also managed to snap some pics of the engineers device while it was testing my adsl, if anyone wants pics i will gladly oblige.

Could you attach pics of the engineers device?
Could you attach SNR margin graph and general router stats?

This should answer your questions. (I don't know why it's G rather than 2+, probably because of the crappy line and the dslam has to retrain?)

Code: [Select]

Stats recorded 29 Jul 2014 13:41:41

DSLAM/MSAN type:        IFTN:0x71c8 / v0x71c8
Modem/router firmware:  AnnexA version - A2pD030g.d22j
DSL mode:                G
Status:                  Showtime
Uptime:                  1 hours 38 min 29 sec
Resyncs:                0 (since 29 Jul 2014 12:06:08)

Downstream Upstream
Line attenuation (dB):  9.5 5.5
Signal attenuation (dB): 9.5 4.6
Connection speed (kbps): 4544 448
SNR margin (dB):        26.4 29.0
Power (dBm):            19.8 8.6
Interleave depth:        32 4
INP:                    1.42 1.88

RSCorr/RS (%):          0.0000 0.0000
RSUnCorr/RS (%):        0.0000 0.0000
ES/hour:                0 0

(I need to upload the other pictures via another site.)

[notaclue]

[Black Sheep]

Haven't read this thread at all, it's only because of the pictures that I'm commenting so apologies if it's been covered ?

I would suggest you have a small HR fault there, as the WB Noise is low (not critical but enough for concern) and the REIN counter has clocked up almost 100 counts. This doesn't mean it is REIN, it just means its picking up interference of some kind.
The problem here is that the 'Test Summary' of this PQT shows as a pass, but I'll bet a pound to a pinch of …………. that the individual leg-balances are out by quite a few ohms ??

It would appear you're quite near to the Exchange, has the engineer gone to carry out any further work or did he just say his goodbyes ??

[notaclue]

Engineer has left, he just replaced the cable running down the side of the house. (It was a phone eng rather than BB). It stopped the very audible crackling going on the line though.
I'll wait the 3 days then phone again.

[Black Sheep]

Hold on a mo ...... were the photo's of the tester done after the cable renewal, or before ?? If it was before, he's most likely cured the problem and those obscure meter readings ?

[boost]

Line techs get JDSUs?