General Discussion
  >> General Broadband Chatter


Register (or login) on our website and you will not see this ad.


Pages in this thread: 1 | 2 | >> (show all)   Print Thread
Standard User marcusjclifford
(committed) Thu 12-Nov-15 19:39:38
Print Post

Example of BT Openreach making phone lines worse.


[link to this post]
 
A few years ago BT did lots of work on the main A road that my phoneline comes along. Replacing the "old" wiring.

When this was all done my ADSL sync had gone from 8128 to 3776. BT claim no fault and say the line is perfect.

I know what they did... they didn't use correct pairs (twisted) and connected the wiring just to random wires in the bundle.

The proof of this is tonight we had a power cut, but I am on UPS. Everyone else's connection will have dropped. Hence the crosstalk (the cause of all the problems) is gone. Power failed at 18:12 returned at 18:48

Here is the log.

12.11.2015 18:00:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:01:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:02:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:03:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:04:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:05:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:06:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:07:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:08:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:09:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:10:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:11:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:12:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:13:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:14:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.0 dB
12.11.2015 18:15:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:16:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:17:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:18:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:19:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:20:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:21:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 28.0 dB
12.11.2015 18:22:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:23:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:24:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:25:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.0 dB
12.11.2015 18:26:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.0 dB
12.11.2015 18:27:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:28:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:29:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:30:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:31:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.0 dB
12.11.2015 18:32:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:33:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.0 dB
12.11.2015 18:34:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.0 dB
12.11.2015 18:35:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.0 dB
12.11.2015 18:36:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:37:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.0 dB
12.11.2015 18:38:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.0 dB
12.11.2015 18:39:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:40:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.0 dB
12.11.2015 18:41:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.0 dB
12.11.2015 18:42:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.0 dB
12.11.2015 18:43:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.0 dB
12.11.2015 18:44:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.5 dB
12.11.2015 18:45:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.0 dB
12.11.2015 18:46:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 27.0 dB
12.11.2015 18:47:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 26.5 dB
12.11.2015 18:48:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 12.5 dB
12.11.2015 18:49:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.5 dB
12.11.2015 18:50:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.5 dB
12.11.2015 18:51:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.5 dB
12.11.2015 18:52:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:53:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:54:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB
12.11.2015 18:55:00 - C1L1D1T01 | BitrateDN: 3776 kbit/s | BitrateUP: 448 kbit/s | SNRM: 7.0 dB

You can clearly see the rise in SNR, and then when power returns back it goes down again.

So frustrating, but BT refuse to do anything, and charged me the ~£120 call out fee for one of their visits.

Aquiss Home 30
On Exchange ESSTC - via edinbugh-ipsc
Speedtouch 585v6 on BT Filtered Faceplate
Administrator MrSaffron
(staff) Thu 12-Nov-15 21:19:31
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: marcusjclifford] [link to this post]
 
And your downstream attenuation is what?

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Standard User Zarjaz
(eat-sleep-adslguide) Thu 12-Nov-15 22:03:50
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: marcusjclifford] [link to this post]
 
Use of split pairs would provide other symptoms, does your line show any of these ?


Register (or login) on our website and you will not see this ad.

Standard User marcusjclifford
(committed) Fri 13-Nov-15 10:10:44
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: MrSaffron] [link to this post]
 
38db - It was before and after.

The SNR graph of the tones shows a nice gentle curve so no specific frequencies are suffering, it's just a general large increase in signal noise caused by the crosstalk.

Aquiss Home 30
On Exchange ESSTC - via edinbugh-ipsc
Speedtouch 585v6 on BT Filtered Faceplate
Standard User marcusjclifford
(committed) Fri 13-Nov-15 10:11:24
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: Zarjaz] [link to this post]
 
What other symptoms should I be looking for?

Thanks

Aquiss Home 30
On Exchange ESSTC - via edinbugh-ipsc
Speedtouch 585v6 on BT Filtered Faceplate
Administrator MrSaffron
(staff) Fri 13-Nov-15 10:30:10
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: marcusjclifford] [link to this post]
 
The lack of noise rejection can impact on the voice side, so you should be hearing issues too I believe, hence why twisted pair was common decades before xDSL was considered.

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Standard User ian72
(eat-sleep-adslguide) Fri 13-Nov-15 11:01:07
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: MrSaffron] [link to this post]
 
In addition, given there was a power cut, there could be some serious noise coming from an electrical device somewhere that would not be operating whilst the power was down.

As a start, if I was the OP, I would flip the main breaker in the house (as the router is on UPS) and see if it makes any difference to the noise margin.
Administrator MrSaffron
(staff) Fri 13-Nov-15 11:04:13
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: ian72] [link to this post]
 
And if the noise margin flies up at that point to do a resync and see if the modem is happy to make use of the spare margin.

Possibly worth saying twisted pairs while good are NOT perfect at making xDSL services immune to noise. Some noise sources can still cause problems and that even applies if you go all out and use CAT5E

(edit as phone rang, and pressed post before reading to see if I made sense)

Edited by MrSaffron (Fri 13-Nov-15 13:04:30)

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Standard User ian72
(eat-sleep-adslguide) Fri 13-Nov-15 11:12:58
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: MrSaffron] [link to this post]
 
I am either very tired or your second sentence doesn't make much sense?

I think you mean that whilst good at reducing noise they aren't perfect and noise.
Standard User MHC
(sensei) Fri 13-Nov-15 12:43:46
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: marcusjclifford] [link to this post]
 
Why would they randomly connect to individual wires rather than a specific pair? If they did, then at the other end of the cable the job would be ten times worse trying to locate the two wires used.

And, if a BT tech was found to be working in that way, he would certainly have been dealt with and the terminations remade.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

M H C


taurus excreta cerebrum vincit
Administrator MrSaffron
(staff) Fri 13-Nov-15 13:05:02
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: ian72] [link to this post]
 
The joy of answering phone, and pressing post thinking you had typed something else smile

Edit may make some sense.

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Standard User ian72
(eat-sleep-adslguide) Fri 13-Nov-15 13:24:15
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: MrSaffron] [link to this post]
 
smile
Standard User RobertoS
(elder) Fri 13-Nov-15 14:02:24
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: ian72] [link to this post]
 
In reply to a post by ian72:
I am either very tired or your second sentence doesn't make much sense?

I think you mean that whilst good at reducing noise they aren't perfect and noise.
Ditto?

The indispensable man or woman passes from the scene, and what happens next is more or less the same thing as was happening before.
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 59997/15142kbps @ 600m. - BQM
Standard User ian72
(eat-sleep-adslguide) Fri 13-Nov-15 14:32:32
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: RobertoS] [link to this post]
 
LOL. Indeed. I had written more than that but deleted a load - obviously I should have deleted another 2 words... I said maybe I was tired wink
Standard User deleted
(deleted) Fri 13-Nov-15 15:10:24
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: ian72] [link to this post]
 
In reply to a post by ian72:
In addition, given there was a power cut, there could be some serious noise coming from an electrical device somewhere that would not be operating whilst the power was down.

As a start, if I was the OP, I would flip the main breaker in the house (as the router is on UPS) and see if it makes any difference to the noise margin.


Certainly a good start. My 3 local interference generating incidents were all faulty switched mode power supply units. The most ironic one was the plug-in wall wart PSU for an ADSL broadband router - the supply degraded over a couple of months to the point where sync was unobtainable for its owner. I replaced the PSU with a non faulty equivalent and problem solved for owner and me (living a street away - I'd seen 10dB or so of margin/equivalent speed lost) In all cases they produced a broad band (ha!) radio frequency spectrum of noise which had the consequence of decreasing the signal to noise ratio of the wanted broad band radio frequency carriers used for ADSL (&VDSL) - in other words all 'tones' were similarly affected.

It's not unheard of that UPS produce produce nasty mains waveforms (and harmonics)
Standard User deleted
(deleted) Sat 14-Nov-15 14:24:27
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: marcusjclifford] [link to this post]
 
"I know what they did... they didn't use correct pairs (twisted) and connected the wiring just to random wires in the bundle."

How would you know ? have you seen the joints close up ? if not how can you know for a fact ? Very unlikey to be spilt pairs but could well be "random jointing" but that does no harm.
Standard User Gadget
(committed) Sun 15-Nov-15 17:15:55
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: marcusjclifford] [link to this post]
 
possibly also worth asking the question if your UPS is a sine-wave or a filtered square-wave output - some (more expensive) UPS try to mimic the mains sine-wave output for exactly the reason of minimising noise.
Standard User MHC
(sensei) Sun 15-Nov-15 19:30:10
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: Gadget] [link to this post]
 
It would not be the UPS output causing problems as the OP says he saw a significant SNR improvement when power failed.

Any pointing at the UPS should be at the input side where the incoming 230v is converted down to a 12v DC (niminal) to charge the batteries - that power supply could be a good . That will be operational when powered up but quiet when there is a power cut.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

M H C


taurus excreta cerebrum vincit
Standard User Zarjaz
(eat-sleep-adslguide) Sun 15-Nov-15 21:49:42
Print Post

Re: Example of BT Openreach making phone lines worse.


[re: MrSaffron] [link to this post]
 
That's the one, overhearing.

Pages in this thread: 1 | 2 | >> (show all)   Print Thread

Jump to