cancel
Showing results for 
Search instead for 
Did you mean: 

Something wrong

pvmb
Aspiring Pro
Posts: 579
Thanks: 70
Fixes: 2
Registered: ‎12-02-2014

Re: Something wrong

OK, will do. Thanks.
Chris
Legend
Posts: 17,724
Thanks: 600
Fixes: 169
Registered: ‎05-04-2007

Re: Something wrong

The test on the phone line isn't showing any issues. Can you confirm that you've been able to test the phone in the master socket?
Former Plusnet Staff member. Posts after 31st Jan 2020 are not on behalf of Plusnet.
pvmb
Aspiring Pro
Posts: 579
Thanks: 70
Fixes: 2
Registered: ‎12-02-2014

Re: Something wrong

The phone line problems are intermittent - they are only there when they are there, so using the test socket doesn't help.
The broadband is still at a DS noise margin of 9.5dB, it has always previously been a long term steady 6dB. Is there anything that can be done about this?
Chris
Legend
Posts: 17,724
Thanks: 600
Fixes: 169
Registered: ‎05-04-2007

Re: Something wrong

I could reset the SNR, but if there are periods of noise on the line it's very likely that the SNR will head back up. Let me know if you'd like me to try an SNR reset, keeping in mind that we can't do another for 10 days/.
Former Plusnet Staff member. Posts after 31st Jan 2020 are not on behalf of Plusnet.
pvmb
Aspiring Pro
Posts: 579
Thanks: 70
Fixes: 2
Registered: ‎12-02-2014

Re: Something wrong

OK try a reset and I will monitor what happens. Thanks.
Chris
Legend
Posts: 17,724
Thanks: 600
Fixes: 169
Registered: ‎05-04-2007

Re: Something wrong

Ah-ha.
The target SNR was actually 6db already, so I was a little suspicious of why it was currently at 9.5db. It turns out your line had been banded to ensure stability, you were syncing at the top end of the band and therefore the increased SNR was expected. I've requested the banding get removed which should happen in the next hour or so.
Former Plusnet Staff member. Posts after 31st Jan 2020 are not on behalf of Plusnet.
Chris
Legend
Posts: 17,724
Thanks: 600
Fixes: 169
Registered: ‎05-04-2007

Re: Something wrong

Well that's worked, you're now synced at 16674 - this gives a profile of 14700.
Former Plusnet Staff member. Posts after 31st Jan 2020 are not on behalf of Plusnet.
pvmb
Aspiring Pro
Posts: 579
Thanks: 70
Fixes: 2
Registered: ‎12-02-2014

Re: Something wrong

OK, returned to normal this end. Thanks.
What would have caused the banding?
Chris
Legend
Posts: 17,724
Thanks: 600
Fixes: 169
Registered: ‎05-04-2007

Re: Something wrong

It's normally due to a period of disconnections or noise on the line, the banding increases the stability so tries to keep the connection working by possibly sacrificing some speed.
Former Plusnet Staff member. Posts after 31st Jan 2020 are not on behalf of Plusnet.
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: Something wrong

As mentioned here - if you can post the TG582n Full DSL stats we can take it from there.
pvmb
Aspiring Pro
Posts: 579
Thanks: 70
Fixes: 2
Registered: ‎12-02-2014

Re: Something wrong

Hello,
Slightly faster today. I have been trying to disconnect broadband via the router before I turn power off at night.
Here are stats. I wondered if the FEC seemed rather high.
[tt]Physical Layer Statistics:       
  Modem state:                  up
  Up time (Days hh:mm:ss):      0 days, 11:12:15
  xDSL Standard:                ITU-T G.992.5
  xDSL Annex:                    Annex A
  Channel Mode:                  Interleaved
  Number of reset:              0

  Bearers generic info            DS        US     
    Payload rate [Kbps]:       16263    1227 
    Attenuation [dB]:          28.5        14.5         
    Margins [dB]:              5.9          5.9           
    Output power [dBm]:      0.0            12.7         
   
G.997.1 Statistics (Current):       
  Failures:
    Line failures                Near end
      Loss of signal (LOS):    0     
      Loss of frame (LOF):      0     
      Loss of power (LPR):    0     
  Performance monitoring:
    Line PM:            Near end
      Error second (ES):    173   
    Channel PM:          Near end Far end
      Bearer 0:
        Code Violation (CV):    297      237   
        FEC:                    211655  704   
    ATM data path PM:            Near end Far end
      Bearer 0:
        HEC violation count (HEC):        6118    N/A[/tt]
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: Something wrong

Yes the FECs are high, but although the CV(CRC) & ES errors are a touch higher than one would like, the HECs are rather more of a concern.
Do you still have this intermittent noise on the line? Try the Quiet Line Test 17070 option 2 if need be.
pvmb
Aspiring Pro
Posts: 579
Thanks: 70
Fixes: 2
Registered: ‎12-02-2014

Re: Something wrong

Yes. I still do get noises on line on incoming calls. I had a call this evening with some noise on it. But again, testing using Quiet Line doesn't show up anything.
Here are stats. from about one and a half hours after previous ones:
[tt]Physical Layer Statistics:        
 Modem state:                   up
 Up time (Days hh:mm:ss):       0 days, 12:45:56

G.997.1 Statistics (Current):        
 Failures:
   Line failures                Near end
     Loss of signal (LOS):    0      
     Loss of frame (LOF):      0      
     Loss of power (LPR):        0      
 Performance monitoring:
   Line PM:              Near end
     Error second (ES):     223    
   Channel PM:            Near end   Far end
     Bearer 0:
       Code Violation (CV):     364      257    
       FEC:                     228000   787    
   ATM data path PM:            Near end   Far end
     Bearer 0:
       HEC violation count (HEC):   7312     N/A
[/tt]
pvmb
Aspiring Pro
Posts: 579
Thanks: 70
Fixes: 2
Registered: ‎12-02-2014

Re: Something wrong

Just had another incoming call from same source. Once again, noisy incoming line. Again, no call no noise.
Townman
Superuser
Superuser
Posts: 23,016
Thanks: 9,605
Fixes: 160
Registered: ‎22-08-2007

Re: Something wrong

Is the noise just on incoming calls from that source or from several sources?
If just that source, then it is likely that the problem is on their line.

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.