I recently noticed that our Premium Phones all have the "Line cord error, please check" message and no dial tone. I don't know how long this has been for, since we don't use the landline all that much. I've seen some old posts regarding this and have tried the unplugging for a short while, resetting and re-registering that have been offered as possible solutions, but nothing has helped. I do not have another phone to check the line with, but the BT service checker says there's no problems in my area.
Can anyone suggest anything else please?
Many thanks
Solved! Go to Solution.
Assuming your current phone is plugged into the master NTE phone wall socket?
Have you changed your broadband and phone package? Have you been moved onto Digital Voice?
Hi @jac_95
Thanks for a prompt response.
Nothing has changed. The phone is plugged into the master socket as it always has, and we have not changed our package. And I would hope that we haven't been changed to Digital Voice without our knowledge 😲
Obviously trying another phone would be first priority. Can you not borrow one from a friend/neighbour? If not you could probably pick one up for peanuts from the likes of Facebook Marketplace.
Assuming that you've already checked the cable at both ends, try removing the faceplate from the master socket & plugging into the test socket.
If there was a fault on your line, it would normally affect your broadband speed.
That tends to indicate an issue in the exchange, but you do need to try the test socket, as its possible that the master socket is faulty.
What does your master phone socket look like?
That socket is the most recent, but it does have some reported issues.
As mentioned https://community.bt.com/t5/Landline/2019-Master-Socket-kit-loose/m-p/1985566#M6775
The filtered faceplate may have a fault within the phone filtering circuitry. Using the test socket, or connecting things up as shown below, would prove it.
@Keith_Beddoe thank you for your help. I have obtained a corded phone and tried the test socket - still nothing 😟
I've reported it via the BT troubleshooter, so we'll see what happens 🤞