Firstly apologies for this being my 1st post which is an obvious 'me too' problem., However, I've been bouncing off the walls on and off for the last couple of weeks to try to get this re-activated.
Simply, put Caller ID has stopped working on my parents Landline. At the beginning of the year it used to show all the proper incoming number, now, at some point in the intervening months, their Siemens phone just shows "external call" (aka no caller ID). Being somewhat elderly, they do rely on this to screen calls.
I have tried to reactivate it via *234#, resetting local phones and sockets, and by raising it several times with BT via online chat - of which I've never had any followup.
They do not have ADSL broadband (They get it via a village wireless mesh network) - indeed they have the BT 'non-broadband' line rental option. Historically, however, they DID have ADSL on the Landline. (3+ years ago)
I'm now at the the point of asking the Guru Mods on this board who seem to be able to Horse Whisper into the system and enable peoples Caller ID - whether I too could have some help/guidance/power from the Magical Staff of Ra to re-enable Caller ID back to their landline.
Welcome to this user forum.
Caller display would need to be added again to their landline account.
They can do this via MyBT.
There is no cost to do this.
There will be an option there to add BT Privacy and caller display.
I assume you can still contact them via landline, just in case they have a crossed line. If you can get through, then their line must be correct.
Thankyou so much for the quick reply. Jumping into that link, it unfortunately indicated that Caller ID was already enabled - but I've added a couple of privacy options anyway.
As you can see, below, although Caller ID is listed in the left hand panel as a selected option, the top right 'Setup' option shows only TPS and Privacy settings will actually be changed (added).
So, as a thought, should I wait 48hrs, and then DISABLE Caller ID, then 48hrs later RE-Enable it using this interface? Or is that an exercise in futility?
edit: ps. Yes, they can take and make calls without issue - no signs of crossed lines or other weirdness.
Yes, if you disable it, then wait 48 hours and enable it again, that normally fixes the problem, as the command is re-sent to the exchange.
What can happen is that the configuration that is stored in the exchange, can get reset to default, and needs to be refreshed.