Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 2 [3] 4 5

Author Topic: Noisy Line  (Read 5300 times)

Black Sheep

  • Helpful
  • Kitizen
  • *
  • Posts: 4411
Re: Noisy Line
« Reply #30 on: April 20, 2017, 08:35:35 PM »

Hell, it sounds like you work in an untrustworthy patch, mate ....... do you have a 'Can I go to the toilet triage team' ??.  ;) ;D ;D

Where I work, if a CAL engineer has a UG issue, he will either just pass the task back for a UG engineer, or (through the managers say-so), have a UG engineer assist him on the task at hand, there and then.

Of course, we in the game know that different GM patches have different ways of working, but it seems you're 'triaged' to death !!  :)
Logged

Black Sheep

  • Helpful
  • Kitizen
  • *
  • Posts: 4411
Re: Noisy Line
« Reply #31 on: April 20, 2017, 08:39:36 PM »

Whoops ..... hit post too quickly.

It does indeed sound like he's a noobie, and mistaken the DSLAM beacon as a HR on his HHT.
Logged

burakkucat

  • Global Moderator
  • Senior Kitizen
  • *
  • Posts: 19341
  • Over the Rainbow
    • The ELRepo Project
Re: Noisy Line
« Reply #32 on: April 21, 2017, 02:20:16 AM »

. . . and mistaken the DSLAM beacon as a HR on his HHT.

That's interesting. Back in 2012 when my neighbour first took a G.993.2 service, I just had to "take a look". Now I'm sure you know me well enough to understand the implication of those three words . . .  ;)

When the arranged time arrived, I was invited in, carrying my basic tool-kit, a Tester 301C and a Hawk. (Before the latter item became an addition to Walter's Wheelbarrow.) So there I was, sitting on the floor in front of the NTE5, with a lolly-pop plugged into the "test" socket, first with the "mole" and then with the Hawk connected. My first reaction was "Huh?", to which my neighbour asked "Have you seen something interesting?" I suggested he take a look and then said "First you see it, then you don't. The DSLAM is effectively beaconing its location, waving a flag and saying here I am."

Until I read your words, above, I had never seen the word "beaconing" mentioned in any of the documentation that I have read, from that day to this.
« Last Edit: April 22, 2017, 03:46:19 PM by burakkucat »
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

mikeh

  • Member
  • **
  • Posts: 61
Re: Noisy Line
« Reply #33 on: April 21, 2017, 07:40:08 AM »

Thanks for the feedback, it's nice to know more information about yesterdays visit.

The engineer said he wasn't really qualified to tackle certain aspects of the job. He was unsure whether he was allowed to check the pole next to the crossing because of the rail line and phoned his manager about this.

The pole with the damaged outer cable at the start of the lane was seen to by a second engineer who came on the 7 April when the job was first investigated. He put a foot long plastic joint on the cable where the cable was damaged. I spoke to him at the time and he said it was going to be a difficult job. The first engineer who came earlier that morning and checked all the poles with the hoist had concluded that the problem maybe located underground from the drop pole and would need an underground team. Later OR said the fault was fixed and no underground work was done. I informed yesterday's engineer about this. I don't know if he had opened the joint at the first pole to check from there after he had been to the cabinet.

The main thing was that he reported the noise and as the first engineer had been up the poles and requested underground work he cancelled the hoist as unnecessary. Now that OR have confirmation of the problem maybe they will proceed with the underground work.
« Last Edit: April 21, 2017, 08:05:59 AM by mikeh »
Logged

mikeh

  • Member
  • **
  • Posts: 61
Re: Noisy Line
« Reply #34 on: April 21, 2017, 05:35:56 PM »

The internet lost connection later this morning and the phone was off so I checked outside for any work being done. There was an auger wagon near the farm and I could see they were replacing the pole which feeds the farm and carries my line to the pole with the damaged bottom cable which had the plastic joint fitted. I thought they would be replacing that pole as well but when I checked later they had gone.

Could they have replaced the wrong pole? I have had no further update from ISP.
Logged

anfield_92

  • Just arrived
  • *
  • Posts: 6
Re: Noisy Line
« Reply #35 on: April 21, 2017, 09:12:46 PM »

Hell, it sounds like you work in an untrustworthy patch, mate ....... do you have a 'Can I go to the toilet triage team' ??.  ;) ;D ;D

Where I work, if a CAL engineer has a UG issue, he will either just pass the task back for a UG engineer, or (through the managers say-so), have a UG engineer assist him on the task at hand, there and then.

Of course, we in the game know that different GM patches have different ways of working, but it seems you're 'triaged' to death !!  :)

No toilet triage yet but dont go giving them ideas ;) Every now and then we take part in these trials which normally last no more than a couple of months, it gives the next manager in waiting something to do until a job becomes avaliable, and then gives him something to talk about in the interview too :D

The internet lost connection later this morning and the phone was off so I checked outside for any work being done. There was an auger wagon near the farm and I could see they were replacing the pole which feeds the farm and carries my line to the pole with the damaged bottom cable which had the plastic joint fitted. I thought they would be replacing that pole as well but when I checked later they had gone.

Could they have replaced the wrong pole? I have had no further update from ISP.

I can only guess not knowing all the details but I suspect the pole renewal is unrelated to your fault, if a cable has been damaged and needs replacing then this would be done without changing the pole aswell (unless the pole was also damaged). Possibly the pole you saw being replaced was due to be changed for a seperate reason - each pole has a unique ID so its unlikely that the wrong one would be changed.
Logged

mikeh

  • Member
  • **
  • Posts: 61
Re: Noisy Line
« Reply #36 on: April 21, 2017, 09:26:23 PM »


I can only guess not knowing all the details but I suspect the pole renewal is unrelated to your fault, if a cable has been damaged and needs replacing then this would be done without changing the pole aswell (unless the pole was also damaged). Possibly the pole you saw being replaced was due to be changed for a seperate reason - each pole has a unique ID so its unlikely that the wrong one would be changed.


 Thank you for that.
Logged

mikeh

  • Member
  • **
  • Posts: 61
Re: Noisy Line
« Reply #37 on: April 22, 2017, 02:10:22 PM »

Further Update.

Plusnet, who have been very good regarding this problem, contacted me today to say their suppliers have completed the work on my line. However, a test by Plusnet detected another problem and asked me how the line was. I said the line noise has been quieter these last 2 days but is still there. The report they got back was as follows:-

Quote
I continued to progress to the end customer premises and performed a line test. The test failed with the fault located within the overhead network. There was a fault outside the end customer's curtilage and shown by general wear and tear and was fixed by re-terminating drop wire at DP/external block.

This is not what the engineer told me and he didn't go up the drop pole. He said it was underground between my pole and the pole at the lane entrance. I'm thinking yesterdays replacement of the farm's drop pole has something to do with the OR report. They did disconnect my wire at the farm pole which is 1 km away. Can anybody comment on this.

I am to have another engineer visit to be arranged.

[Moderator edited to fix the bbc tags.]
« Last Edit: May 02, 2017, 04:17:20 PM by mikeh »
Logged

mikeh

  • Member
  • **
  • Posts: 61
Re: Noisy Line
« Reply #38 on: April 23, 2017, 07:49:24 AM »

An engineer visit has been arranged for Wednesday afternoon. The noise became louder yesterday evening and it is at an annoying level again this morning. I have no doubt the engineer will hear the same noise as before but I have doubts whether their managers will authorize any digging work.

It is really bad now with loud crackles, the fibre broadband lost connection and has re-synced at 9.9mb instead of the usual 19.9mbs. Quiet line tests have constant loud crackling. The phone is unusable now.
« Last Edit: April 23, 2017, 09:04:54 AM by mikeh »
Logged

tickmike

  • Kitizen
  • ****
  • Posts: 3058
  • Yes Another Penguin !. :)
    • Free Download from.
Re: Noisy Line
« Reply #39 on: April 23, 2017, 11:53:37 AM »

The noise became louder yesterday evening and it is at an annoying level again this morning.
It is really bad now with loud crackles,
You should think about recording it while it's bad, I used a app on my mobile phone or on our 'Dect' phones to record it when my line was bad. you may need it as evidence.
Logged
I RECOMMEND TRYING / USING PCLinuxOS (www.pclinuxos.com) .
I have a set of 8 fixed IP's From my Eclipse isp.
BT ADSL2 line>HG612 set as a Modem, Bridge, WAN not Bound to LAN1 or 2 >Smoothwall (Hardware Firewall and routing) > Ethernet LAN, DMZ,WiFI LAN and Spare LAN .
DSLstats LAN2  linked Ethernet

mikeh

  • Member
  • **
  • Posts: 61
Re: Noisy Line
« Reply #40 on: April 23, 2017, 04:43:44 PM »

I am using a friends internet connection as the landline is now unusable. The phone is unusable and will ring showing an external call and then stop. The line is very crackly. I have switched off my router, which could not stay connected.

I don't need to record anything now, the line is kaput now. This will be my last post till they fix this line.
Logged

Black Sheep

  • Helpful
  • Kitizen
  • *
  • Posts: 4411
Re: Noisy Line
« Reply #41 on: April 23, 2017, 05:47:27 PM »

Your pain is an engineers joy ...... something to definitely fault !!  :)
Logged

mikeh

  • Member
  • **
  • Posts: 61
Re: Noisy Line
« Reply #42 on: April 26, 2017, 07:37:58 PM »

The saga continues. I thought we had a proper "engineer's joy" but the line recovered somewhat by Sunday evening. It was not ready to meet its' maker unfortunately. I was able to phone out again but the noise was so loud with crackling and buzzing I couldn't hear a conversation, so still unusable. All good for the engineer visit today pm.

Monday, check phone constant crackling and buzzing. Unpleasant using phone.

Tuesday - same again.
 
Today - crackling more intermittent now. Waiting for engineer visit this afternoon. By 2.00pm I had had no text alerts from Open Reach and so phoned Plus Net to confirm the appointment. Which they duly did. Waited in all afternoon but no engineer arrived. I therefore phoned Plus Net back. They informed me the visit had been rejected by Open Reach. I am very disappointed that customers are not informed of cancelled appointments. Plus Net have now arranged a visit for PM Friday. But I notice on their line test "no fault found". I have received a text message from Plus Net informing me that, should an internal fault be found, I could incur a charge of 65 (which is also levied if the customer misses the appointment - how ironic!).

After each engineer's visit I have a feeling of hopeful anticipation - but end up with disappointment and frustration.

One last comment - I have yet to reconnect my modem due to continued and obtrusive interference on the line.   
Logged

mikeh

  • Member
  • **
  • Posts: 61
Re: Noisy Line
« Reply #43 on: April 29, 2017, 07:47:00 PM »

Yet another no show from BTOR engineer on Friday. I knew by 2pm as I had had no text alerts from OR that inform you of a visit. I phoned Plusnet and they said that they could not do anything and could not inform me if they knew OR would be coming even though they had we had agreed I would be at home on Friday afternoon. I am frustrated by this situation but I will see what Plusnet do next.

I'm back online again despite the line noise. So far I've had a few re-syncs with a lot of errors showing, at least Plusnet can see how unstable the line is. As far as the noise goes there is a pattern of constant background buzzing which is quite loud and occasional crackling with short loud bursts which can drown out a callers voice. I am not expecting anything to happen till after the bank holiday.

I've been using the excellent Dslstats to monitor the line stats.  G.INP was enabled for a while on the upstream with the line noise.

Code: [Select]
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    1
Last initialization procedure status:   0
Max:    Upstream rate = 1145 Kbps, Downstream rate = 21823 Kbps
Bearer: 0, Upstream rate = 1145 Kbps, Downstream rate = 17998 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State:       L0
Mode:                   VDSL2 Annex B
VDSL2 Profile:          Profile 17a
TPS-TC:                 PTM Mode(0x0)
Trellis:                U:ON /D:ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):        7.7             6.6
Attn(dB):        30.9            0.0
Pwr(dBm):        10.7            10.5

                        VDSL2 framing
                        Bearer 0
MSGc:           -6              26
B:              40              31
M:              1               1
T:              0               52
R:              6               0
S:              0.0719          0.8737
L:              5226            293
D:              8               1
I:              47              32
N:              47              32
Q:              8               0
V:              1               0
RxQueue:                120             0
TxQueue:                30              0
G.INP Framing:          18              0
G.INP lookback:         30              0
RRC bits:               0               24
                        Bearer 1
MSGc:           90              -6
B:              0               0
M:              2               0
T:              2               0
R:              16              0
S:              10.6667         0.0000
L:              24              0
D:              1               0
I:              32              0
N:              32              0
Q:              0               0
V:              0               0
RxQueue:                0               0
TxQueue:                0               0
G.INP Framing:          0               0
G.INP lookback:         0               0
RRC bits:               0               0

                        Counters
                        Bearer 0
OHF:            0               642333
OHFErr:         835             327
RS:             1332761096              2823830
RSCorr:         727285          0
RSUnCorr:       0               0
                        Bearer 1
OHF:            1498334         0
OHFErr:         171             0
RS:             8989635         0
RSCorr:         11742           0
RSUnCorr:       265             0

                        Retransmit Counters
rtx_tx:         17318154                17195
rtx_c:          1583509         15005
rtx_uc:         1044371         13749

                        G.INP Counters
LEFTRS:         1671            541
minEFTR:        17998           1088
errFreeBits:    381828219               3109827

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    831061592               0
Data Cells:     2266071         0
Drop Cells:     0
Bit Errors:     0               0

                        Bearer 1
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    0               0
Data Cells:     0               0
Drop Cells:     0
Bit Errors:     0               0

ES:             1168            249
SES:            272             20
UAS:            392             252
AS:             24072

                        Bearer 0
INP:            51.00           0.00
INPRein:        1.00            0.00
delay:          0               0
PER:            0.00            11.40
OR:             0.01            22.45
AgR:            18164.44        1167.43

                        Bearer 1
INP:            2.50            0.00
INPRein:        2.50            0.00
delay:          0               0
PER:            16.06           0.01
OR:             47.81           0.01
AgR:            47.81   0.01

Bitswap:        8481/8482               7/7

Total time = 2 days 12 hours 47 min 0 sec
FEC:            10964213                1532
CRC:            15256           595
ES:             1168            249
SES:            272             20
UAS:            392             252
LOS:            7               0
LOF:            45              0
LOM:            70              0
Latest 15 minutes time = 2 min 0 sec
FEC:            4450            0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Previous 15 minutes time = 15 min 0 sec
FEC:            15410           0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 1 day time = 12 hours 47 min 0 sec
FEC:            1178777         815
CRC:            10065           494
ES:             626             203
SES:            184             8
UAS:            274             170
LOS:            5               0
LOF:            33              0
LOM:            60              0
Previous 1 day time = 24 hours 0 sec
FEC:            4743128         472
CRC:            3613            87
ES:             295             36
SES:            65              12
UAS:            90              54
LOS:            2               0
LOF:            12              0
LOM:            5               0
Since Link time = 6 hours 41 min 11 sec
FEC:            727285          0
CRC:            835             327
ES:             180             146
SES:            9               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
 >
Logged

NEXUS2345

  • Reg Member
  • ***
  • Posts: 226
Re: Noisy Line
« Reply #44 on: April 29, 2017, 09:22:46 PM »

If it continues much longer I would get in touch with the Openreach CEO. Everytime somebody has done so, the issue has been resolved within days. Considering you have had 2 no shows, if you have a third, I would suggest doing this. PSTN faults are meant to have a repair time of usually no more than 2 days I believe.
Logged
Zen ADSL2+ | HG612 + TP-Link C2600 | Awaiting FTTC (build in progress)
Pages: 1 2 [3] 4 5
 

anything