Is this a record?

[#1]

jelv, which modem/router are you using at the moment? Are you looking at Bits/Tone plots as well as SNRM?

[#2]

TG582
The bits tone graph looks pretty normal to me.
There's obviously something wrong with the line if it drops on an incoming call with no phone attached. I'll get that sorted first and then reassess the situation. If I can get a totally stable 6000 (fast enough for HD iPlayer) I'd be happy.
Current stats:
Link Information

Uptime: 0 days, 6:19:09
DSL Type: ITU-T G.992.1
Bandwidth (Up/Down) [kbps/kbps]: 832 / 7.616
Data Transferred (Sent/Received) [MB/MB]: 86,18 / 487,64
Output Power (Up/Down) [dBm]: 12,5 / 19,8
Line Attenuation (Up/Down) [dB]: 14,0 / 21,0
SN Margin (Up/Down) [dB]: 12,0 / 5,9
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / ????
Loss of Framing (Local/Remote): 34 / -
Loss of Signal (Local/Remote): 4 / -
Loss of Power (Local/Remote): 0 / -
Loss of Link (Remote): -
Error Seconds (Local/Remote): 59 / -
FEC Errors (Up/Down): 0 / 0
CRC Errors (Up/Down): 879 / 4
HEC Errors (Up/Down): - / 3

[#3]

I agree, there has to be something wrong with the line, as you say, plugged into the test socket it shouldn't drop with an incoming call, and with that attenuation you should be syncing at 8128 as your are on Fastpath (FECs=0).
Is that still with 10.2.2.9 firmware? Is there any significant bit swapping on the US?

[#4]

Still on 10.2.2.9
Nothing significant on the bitswaps/tone. It's pretty much flat right across all tones (up and down) with 2 swaps per tone.

[#5]

Let's hope the CLT shows a clear fault!

[#6]

Unfortunately we weren't able to get it to run, though that did enable us to raise the fault. It's been cleared with "15 - 556 - BTW cannot progress this fault as the root cause is the PSTN failure. Please report to your Copper Line Service Provider." so looks like it is a fault with the phone line - not sure we'll be able to progress this any further as a broadband fault now we've received that result.

[#7]

OK so if I ring up BT Retail to report a phone fault:
Me: When the phone rings for an incoming call the broadband drops
Them: Is the phone working OK?
Me: Yes
Them: Any noise on the line?
Me: No
No prizes for guessing what their response is likely to be!

[#8]

Quote from: Matt

Unfortunately we weren't able to get it to run, though that did enable us to raise the fault. It's been cleared with "15 - 556 - BTW cannot progress this fault as the root cause is the PSTN failure. Please report to your Copper Line Service Provider." so looks like it is a fault with the phone line - not sure we'll be able to progress this any further as a broadband fault now we've received that result.

There's nothing on my ticket about BTw clearing the fault - is that coming?
BTW: Only one incoming call so far today at 12:16
[quote=Router log]<173> Mar 21 12:16:56 xDSL linestate down
<173> Mar 21 12:17:10 xDSL linestate up (ITU-T G.992.1; downstream: 7584 kbit/s, upstream: 832 kbit/s; output Power Down: 19.8 dBm, Up: 12.5 dBm; line Attenuation Down: 21.0 dB, Up: 14.0 dB; snr Margin Down: 6.1 dB, Up: 12.0 dB)

The PPP did not drop.

[#9]

I've taken a look at it for you.
Our testing has failed at the Local Exchange. I've arranged for a Frames Engineer to go out to get that sorted for you.
Should all be sorted within 48 hours for you

[#10]

Brilliant
Thanks Chris

[#11]

Just had a call from the engineer at the exchange (which dropped the connection). Everything looks OK to him. He's going to report back that a broadband engineer is required.
What a surprise!

[#12]

Very friendly broadband engineer has been. Looked at what I'd done and agreed nothing more to be tested at my end, so off he went to the exchange. Disconnected my line and connected his test box inside the exchange, rang my number and his test box started logging CRC errors. He has arranged for the equipment in the exchange to be replaced which will take around 2-3 days.
At least it's progress - confirmed it's not my end and confirmed that it's not the wires from here to the exchange.

[#13]

Thanks for letting us know. At least we are seeing some progression with this.

[#14]

Given what I've posted above, does this response on the ticket sound appropriate?

Quote

Dear Mr xxx, Further to my message,  our suppliers are arranging the move to new pairs.  We'll continue to check for updates on a regular basis and pass information on as soon as it becomes  available.  Apologies for any inconvenience caused. Kind regards, <removed> --internal-- EC ref 197352799 I will go ahead and passed this to EM Assit team to provide the new tie pair and if required they will send out transmission engineer.

[#15]

Faulty Tie-pair seems quite a good possibility!