Line test (phone troubleshooter failed)
FIXED- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Home Phone
- :
- Line test (phone troubleshooter failed)
11-04-2020 4:32 PM - edited 11-04-2020 4:43 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I did a line noise test on my master and test socket, I did this with multiple filters and no filter at around 11am and again 11pm yesterday. During the test I hear a light static noise, as I've never done this test before I'm unsure if this is expected, or if even the slightest static points to a fault. I have a cordless phone and unfortunately I'm unable to retrieve a corded phone for testing purposes. I tried to run trhough the troubleshooter but I just get the oops message, so I was hoping someone here could do a line test for me. Just to clarify, I'm not having any problems actually using my phones, this is about a fault potentially slowing my broadband.
Fixed! Go to the fix.
11-04-2020 4:45 PM - edited 11-04-2020 4:45 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
@phirani Welcome to the forum. 🙂
The troubleshooter will often return the 'Oops' message even though it has actually raised a ticket and the fault has been passed to Openreach.
You can log into your account and check tickets here - https://www.plus.net/wizard/?p=search
Zen FTTC 40/10 + Digital Voice FRITZ!Box 7530
BT technician (Retired)
Re: Line test (phone troubleshooter failed)
13-04-2020 11:18 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Home Phone
- :
- Line test (phone troubleshooter failed)