Caller ID not working

[#1]

Well, it maybe rules out the storm as the culprit, but I'll tag @MatthewWheeler and see if it gets you any more traction. Not much else I can do, sorry.

[#2]

Ok and thank you for trying.

We’ll have to see what happens next.

[#3]

Hi @Humbug,

I'm very sorry to hear that we've not been able to fix this issue yet. I've had a look over the account this morning and I can see that your case has been assigned to a case handler, with an update having been logged yesterday. For reference, you can view this here. Once an update is available, your case handler will be back in touch to discuss things further.

[#4]

The usual culprits for this issue are...

1. The user's filter / face plate - could have been damaged in the storm - easy for the user to change
2. The line card in the exchange - if that was damaged, one might expect many to have been damaged
3. A fault on the line - one would expect line tests to show this - though some line faults are not detectable from the exchange
4. The ADSL pair left in in the exchange - this is generally seen only immediately following an upgrade from ADSL to FTTC
5. The CLI settings have not been applied cleanly - there are known issues were the Plusnet portal will report that CLI is active ... but it is not active on BTOR's systems

@198kHz - does anything else come to mind?

[#5]

@Townman I think you've covered all the possibilities there.

As Caller ID has been working for several years before the storm, and the OP has replaced the phone, then items 4 and 5 in your list can probably be discounted.

If I've read the thread correctly, we're not totally certain whether the kitchen socket is actually a master, and if it is, whether it's one with a filtered faceplate, or the old type using a dangly microfilter.

If the former, then it would be advisable to connect the phone directly to the test socket to eliminate a problem within the property.

Once that's proved, then hopefully the case handler mentioned above will ensure that PN get OR on the case again and not accept a 'clear' until it's really fixed.