Plusnet tech support procedures

[#1]

Hey guys

After the last few months and multiple phone calls its fairly clear to me that the tech support procedures are somewhat lacking within plusnet. 

im not here to complain about the service recieved (which has been fairly sub par) but i would like to suggest perhaps additional procedures for when the current ones fail. 

The backdrop - i have been having multiple disconnection issues over more than 3 months (that i have noticed) - speeds are good when working. but would frequently have 5 or 6 or more network disconnections in a day (yesterday it was 15 or so)  then periods of it working as it should. i would call plusnet tech support and be on an endless loop of a ticket being opened, no line faults found (with their tests) and no further action. still having the issue - call again - no fault found - me getting aggrivated. ask for an engineer to come out, they do, find a fault and fix it. - issue persists - call again - no fault found again - ask for another engineer.

i was told there wasnt a fault many, many times and there wasnt a way for them to request an engineer without me accepting the liability for the engineers fee. - this really isnt acceptable as there was clearly a fault. this showed in the connection logs. it appaeared to me that there isnt a way for a plusnet employee to get any further with my issue without potentially being subject to a bit of grief from whomever above them.  

I have just had the second of 2 engineers this week alone to diagnose and hopefully sort the issue. after me mentioning the 1970's era cable from the pole to my house and the state of corrosion on parts of it, it was all finally replaced, and the engineer showed me the multiple areas of corrosion, bare cable, actually split cable. he was supprised it was working at all. I told at least 3 different plusnet employee's about the state of the cable leading to my house. - and there doesnt seem to be a way for them to relay this information. 

i understand that the infrastructure is openreach's responsibility. and if the first enginner came did the job correctly it would not have gone this far. 

once again, this isnt a complaint against any employee i have spoken too, they have all been mostly ok. but its very apparent that the scripts they follow only cover basic issues - This is me mearly pointing out that these procedures do not cover all the issues that may be faced by some customers. and perhaps additional ones should be added to cover issues like mine, when the normal ones fail. For instance if an issues continues after an openreach engineer has already attended. 

its been a long 3 months. and very irritating. im happy to explain further, or if im not clear at any point let me know. 

[#2]

Hi,

A warm welcome to the forum. You post illustrates well the difficulty in diagnosing a marginal line which is not a total failure.

The line condition you describe would be very susceptible to variable behaviour as weather varies. The state of the cable you described could even right itself (for a short period) by the act of testing it. Similar and inbound call could clear the fault. Circuit test signals and ring current applied to the line can dry out iffy joints. Consequently on testing no fault is found.

Under SOP an ISP can only call out an engineer if the test systems identify a fault from the exchange test head. Therein lays one issue that some faults will only appear if tested from the user’s premises.

Whenever an engineer visit is arranged there is the warning that the user might be charged if no fault is found in BT’s infrastructure.

Even when an engineer does attend and the find and fix one fault they do not going looking for others. Though as I hint above, a cable defect might not exhibit a fault all if the time.

Hope the problem is now fully fixed for you. Did you do a quiet line test with a handset at anytime along your journey?

[#3]

---

@Townman wrote:

The line condition you describe would be very susceptible to variable behaviour as weather varies. The state of the cable you described could even right itself (for a short period) by the act of testing it. Similar and inbound call could clear the fault. Circuit test signals and ring current applied to the line can dry out iffy joints. Consequently on testing no fault is found.

Under SOP an ISP can only call out an engineer if the test systems identify a fault from the exchange test head. Therein lays one issue that some faults will only appear if tested from the user’s premises.

---

This is my point. the standard operating procedures do not cover issue faced by me. and probably by others. so they either need to be changed, or new ones put in place to cover them. hiding behind an SOP is the reason im unhappy with the service. 

Whenever an engineer visit is arranged there is the warning that the user might be charged if no fault is found in BT’s infrastructure.

Even when an engineer does attend and the find and fix one fault they do not going looking for others. Though as I hint above, a cable defect might not exhibit a fault all if the time.

---

This is what bugs me the most. i have applied everything plusnet asked me to do. yet was still having issues. clear issues that were recorded on their system. 

how can they say there is no fault, when this is happening? how is this a fault that is not exibited?  

- the Openreach engineer said to me that the property should have been checked on connection of the service. and that checks should have been done every time an engineer went to look at the issue. 

Yet i STILL have a connection dropping issue. 

[#4]

SOP for line faults is set by BT Openreach not Plusnet.

You've responded to most of the points I made, except the most important one - have you done (did you do) a QLT?

Broadband is not going to work well if the "phone" line is not working properly.

Please perform a quiet line test - dial 17070 select option 2 using a corded phone plugged into the test socket behind the face plate of the master socket. It should be silent. A noisy phone line (or no dial tone) will have a marked adverse impact on the performance of broadband.

If the line is noisy or there is no dial tone, then a PHONE LINE fault needs to be raised with your phone provider. If this is PlusNet, you can report a fault on line using the button below.  From the Q&A list, choose the one which matches the problem, 'open' the 'section' and click the trouble-shooter link.  NB: If you receive a failure message (rather than a log-in prompt) then log-in to the user portal in a different browser tab and attempt to use the trouble-shooter again.

• Phone Faults

Given the faults you mentioned, one would expect a lot of audible noise on the phone line.  Checking for line noise is the first line of SOP, however many users do not have telephone handsets claiming they have no use of the phone and refuse to obtain one to help diagnose the problems.  Not having a handset connected also results in an inability to see if any of the faults experienced are connected to a call being placed on the line.

In certain conditions what seems like just a piece of wire can act like a complex electrical circuit of capacitors and resistors to the high frequency signals used for xDSL.  Sometimes (not often) the characteristics of a circuit can look different if tested from the exchange to that tested from the premises.  Similarly the effect of ring (or test) currents / voltage on a line can alter defects cause by corrosion.

I have experienced a line which tested fine from the premises but the automated exit test (from the exchange test head) still reported a fault.  The BT Engineer claimed his tests were fine so the exchange test head must be faulty.  Some two or three repeated visits later, a different engineer went and tested the circuit back from the exchange and found that there was indeed a fault on the line … quite close to the exchange.  IIRC that ADSL line was only delivering 15Mbps just outside the exchange, where it should have been close to 24Mbps.

Network diagnosis is more art than science, for invariably for intermittent issues, they are not manifest when testing is performed,  Totally broken connections are far easier to fault locate than ones which fail some of the time.  Such unfortunately is a fact of life!

[#5]

Hi  @JJmcneil,

I'm very sorry for the inconvenience that the dropping connection fault has caused you and for the length of time that this has been ongoing. As @Townman has mentioned, diagnosing the cause of the fault can be difficult when it comes to intermittent issues but I will pass on your feedback regarding our operating procedures.

Having checked your connection today, things look to have been much more stable since the engineer visit last Thursday:

Please keep an eye on your connection. If the drops become frequent again, I would recommend that you run through a quite line test ,as per @Townman's comment, to check whether there is noise on the line. If you get back in touch on here and let us know the result of the quiet line test, we will be able to investigate this further for you.

[#6]

@EmilyD 

Thank you for the radius log plot - very helpful.

@JJmcneil 

I note a very regular disconnection between 00:45 and 02:00 on most days, except last Sunday when the clocks changed.  Are you aware of any electrical system in the vicinity which has an on / off event around that time?  ERM from switching events can give rise to connection failures of the characteristic shown on your connection plot.

Degraded lines such as the one you have described are more susceptible to such events.

[#7]

thanks for the replies folks. i will check as soon as a phone arrives from ebay (dont even own a home phone anymore) 

---

I note a very regular disconnection between 00:45 and 02:00 on most days, except last Sunday when the clocks changed.  Are you aware of any electrical system in the vicinity which has an on / off event around that time?  ERM from switching events can give rise to connection failures of the characteristic shown on your connection plot.

Degraded lines such as the one you have described are more susceptible to such events.

---

thanks for pointing that out. i hadnt noticed. i have a ton of radio recieving gear in a cuboard that i could maybe have a look with (no transmit and also not powered up so its not that) thanks for that point. 

It does seem better. but has still dropped. im leaving it for a while to see if there is a proper improvement, as this is the faults M.O. - i shall report back if i find anything.  

[#8]

right.

im still having the same issue. after 3 1/2 months (at least).  3 engineers visits. multiple calls to plusnet support. i have done everything i have been asked to do. - im not a telecoms engineer. you guys have them. 

i have added a reply to the email i recieved yesterday. im trying to stay level headed about this, but this is a massive failure from plusnet, and im not happy with the overall service i have recieved so far. 

the email states that the engineer visited and the problem should be solved (more than a week after the visit) - but if anyone had looked at the line data - or the original problem i was having, they would have seen that it is NOT sorted. 

I dont care that openreach look after the network. i know that. but i have no recourse with them. only with plusnet. i also dont care that its an intemittant fault. Plusnet is a telecoms company, and along with openreach (Both BT subsidiaries) should have the qualified staff and equipment to be able to handle an issue like this after many years or operating.

how many attempts does it take the average customer to sort a problem out?  well, a quick google search of this forum would indicate quite a few, if the problem is similar to mine. - surely Plusnet would/could have learned from this? - it does not appear that way to me.

[#9]

Hello guys,  

I posted a reply to a technical issues i have been having, also, as part of the technical issue i posted about the level of service i have recieved from plusnet over the last few months. i posted this in this feedback section of the forum. 

Original post https://community.plus.net/t5/Plusnet-Feedback/Plusnet-tech-support-procedures/m-p/1724300#M86078

I posted there as a reply to previous request, and after 48 hrs have received no reply from a plusnet staff member. - fine, i guess they cant trawl this forum day and night waiting for replies. 

However, i also replied to a support ticket on my account more than 48hrs ago and have received no reply there either. 

is it normal to take this long? i know that staffing is an issue at the moment, from a previous phone call to the support team. but the issue im having has dragged on since january without resolution. 

Is there any specific procedures or hoops that i have to jump through in order to start a complaint?  

[#10]

With regard to my Loooong ongoing disconnection issues, does anyone have any idea what

"PPP LCP Send termination request (user request)"   is?  

Every time my router disconnects the router log shows that message, then the follow up reconnection until the next disconnection. 

I googled it, as im not a telecoms engineer. the only results i found on the first 4 pages of google were with regard to Plusnet and BT, and customers using the Plusnet hub one, and the BT HH5 (both identical hardware, with a different skin and cosmetic firmware tweaks) 

From what i gather, the router is reqesting the line to be dropped as a certain number of echo packets have not been recieved. - i did read the entire document, but it start to go above my head at a point. most of the info and more experienced folks seem to point to a fault in the copper network possibly combined with a firmware/hardware issue with the router. - again, im not a telecoms engineer.  

i kept reading some of them, and i could have sworn that i had written some of those posts, as they sounded identical to the issues im facing. along with the very same calls to help desks, engineers visits and support tickets being opened and closed, line tests showing nothing - all without resolution of the fault. 

 a lot of people have had this mysterious fault resolved with a new router. but was wondering if anyone else had any experience of this? 

I have multiple calls to plusnet and engineers visits since january. and am currently waiting for them to replt to messages sent 2 days ago.

[#11]

My apologies, please can this be moved into Feedback, or the appropriate heading. as i misplaced it

Thanks!

John

[#12]

Moderators Note

Several topics from same poster merged to keep all info in one place and to help staff

[#13]

Right now things are tough everywhere. Plusnet support is stretched with staff needing to self isolate, call centre hours have been restricted - see the banner. There you will also find that BT Openreach have restrictions on the engineering services they can provide.

As advised before intermittent issues are hard to find. There is every possibly that your particular issue might not be a line fault but one caused by external interference.

You might have a journey to follow to bottom this out ... though you’ve not yet reported in the first step of doing a quiet line test. In the past I’ve had the experience of having 18+ engineer visits over 8 months to improve a line from 2.4 Mbps to 5 Mbps ... which in the end still dropped when certain West Coast trains passed nearby.

That journey included elimination of RFI caused by a CCTV system, fixing Star wired internal extensions and multiple changes to the d-side circuit you eliminate problematic (aluminium) cable segments. Add to that the performance was better in dry weather than wet weather it was rather hard to fix.

Like it or not, all ISPs are in the dead hand of BT Openreach, who tend to go fix the symptom identified by the ISP and nothing more.

So what is the result of the QLT please?

You mention the you have a lot of radio receiving equipment - such would be useful for detecting REIN. IIRC the critical band is 600kHz

[#14]

i was told by the latest openreach engineer that the line sounded fine. so i didnt buy a phone to test it. i dont own one.

I know things are tough, tough for a large amount of people. but like i said, this has dragged on since january. 

The REIN thing you mentioned, i do indeed have radio gear that would pick that up, and i have looked, at the times of the disconnection it doesnt show anything out of the ordinary, certainly no burst events, but then i havent walked down to the cabinet and tried there - i tried unpluging everything else in the house, to the great annoyance of my partner, execpt the PC that runs a web server, and its frequent disconnection that is getting me so annoyed with this. even with the faily sizeable antenna sat right next to it it doesnt show any spurious RF (the benefit of buying quality parts)  - also the street lights turning on and off dont correspond with any disconnection. or visable interferance. 

You might have a journey to follow to bottom this out ... 

I already have had a journey. and i dont want this journey to continue any longer. i want plusnet to stop quoting me the SOP, investigate the issue, and sort it. i have said it before, im not a telecoms engineer - they are an internet service provider, with telecoms engineers. - and i also know that Openreach are responsible for the network, but i cant contact them, i MUST go through my supplier. 

[#15]

Edited for duplication.