US Telco Support > AT&T > AT&T U-verse > What wrong with my line?

What wrong with my line?

Your bit loading graph appears it would indicate a bridge tap on the line somewhere.

I doubt its a bridge tap. My house was built in '01. I've had Uverse since mid 2008 with no problems until now.

Could be Am radio interference? Post those screen shots and your issues in the Direct forums and Tier 2 can look into for you? When is the last time you re-booted the RG?

»AT&T Direct

reply to ineel
Reseat all the connectors from the nid to the RG. One may have developed some resistance. Then reboot the RG. If it is coax you may need new connectors.

Ok i took various steps to see if i can resolve this issue. I currently have a cat5e from the NID to the 3801HGV then RG-6 to the DVR/STB. So i went to the NID this morning to study which pairs are used for what. From my understanding how everythings set up is that the Blue/blue-white pair is Phone Line 1, Orange/orange-white is Phone line 2 and the Green/green-white pair is the one that goes to the RG. So i took out the blue and orange pairs since i no longer use at&t POTS service. I took out the green pair for Uverse and inspected the copper ends and they seemed rusty copper brown so i cut a few cm off and stripped it with 24 awg strippers and reconnected the green pair into the Balun/DSL splitter they use. I went to the junction box in the master closet and all connections are tight there and i re seated the phone line connection coming the from wall to the RG. I went ahead to the gateway/ page in my browser and restarted the RG. Hopefully this will fix my problems. I usually see the high amounts of corrected and uncorrected blocks during the evening and almost none during the day. I'm wondering if there is crosstalk between my pair and all my neighbors pairs that go the VRAD. Is that possible? Or does crosstalk only happen on pair-bonded lines. Im hoping that line vectoring somebody posted is deployed soon. Anyways everything seems good for now. I will check the UV realtime app again in the evening to see if anything is happening. Looks like my Max sync has gone up from 49mbps to 53mbps.

reply to ineel
I am 1300-1400 feet from my Vrad and sync at 53,000ish.

I have had 0 uncorrected blocks in the last 94 days and only about 10 corrected blocks a day, everything else reads 0's.

So you being 1000 feet closer should def not have all that.

I also DO have AM bleed into my line and it causes no issues other than a dead spot on my bits graph. Yours does look like a bad wire or connector though.

I had similar issues a few months after I first got HSI and the wire running from the port outside into the house had cracks all over them so I replaced with a new Cat5e and its been happy from that point on.

Oh I also hooked the ground up to the shielding on the main wire from the ped they didn't hook up and the wires from ped to my house are new, but rest of the wire from ped to vrad are 25+ year old lol

Not 1000 feet closer, I mean 100 (doh!)

Be careful of connecting the shield. The shield should only be connected at the source end. Connecting both ends will create a ground loop and generate noise in the line.

reply to ineel
You certainly don't have a bridge tap. If your errors keep piling up after your repairs (you made your max rate go up, hats off), then the next problem areas would be a failing RG, or crosstalk before the NID like you conjectured. It's just jargon for anything bleeding over into the VDSL frequencies on your pair, not limited to pair bonding, usually caused by bad grounding/shielding or poor twists.

reply to ineel

Unfortunately it can happen anytime. In the old days spring connections were a lot more reliable as they were gold plated. Today as the connectors age they build up some corrosion around the contact area. If the cable is moved the contact point slips on the corroded area and you have errors. I had the problem recently after I was making some changes in my A/V cabinet which also houses the RG. I later noticed the correctable errors going out of site. A quick reseat of the cable to the RG fixed it.