Constant "no number calls" since moving to IP Telephone from landline (Home) (Resolved)

[Chris_Myers]

My area has recently been migrated from landline to IP telephony which seems to work well with one exception.  My received calls report 10-20 daily calls from "no number".  There is no call made (no ringing) and no message left, just a report that "no number" called and a time.  OFCOM state it should be addressed to the provider and the Telephone preference service state they can do nothing with marketing or computer generated calls.  This did not happen until switched to IP telephony and has been daily since (coincidentally - I think not).  This appears to be a man-in-the-middle network attack and is therefore worrying (as well as filling my recent calls with rubbish).  Virgin media say they cannot see these calls, yet their system records it on my recent calls log. Anyone else having this problem or have a resolution?

[MOD EDIT: Please see post for an update ]

[Chris_Myers]

Let me guess - servers based outside UK and set to local time?

[MOD EDIT: [REMOVED]

[1malcolmgeorge]

That was my thought when the clocks went forward in spring. Unfortunately not all nations change their clocks on the same date. WHERE ARE THE  VIRGIN MEDIA SERVERS BASED???

[Chris_Myers]

my guess would be US-configured

[1malcolmgeorge]

👍

[Crystalgazer]

All,

The comments on the time issue have moved across to the 'Wrong Time on Handset since moving to Digital Voice' thread. New comments start from page 8. I can't seem to do a link to it unfortunately. 

[Chris_Myers]

Anyone know how to move a topic (Constant "no number calls" since moving to IP-Telephone) to "archive"

[ModTeam]

Hi, threads/topics are archived after 12 months of inactivity.

[adsinbath]

I have a Panasonic KX-TGJ424EB handset and since our upgrade to voip earlier this year. We’ve been receiving ghost calls. 
How many times must I restart my router for these to stop?? 
VM please can someone help? 
I already had my phones and if they were incompatible with voip surely it’s VM’s responsibility to rectify the issue? 
can someone at VM please confirm how we get this resolved? 

[Chris_Myers]

See Entry 92 in this thread - VM say it has been resolved and I, for one, have not had this issue since. VM are more than a little slow to respond.  Just look at the length of this thread and timelines going back to September 2022. You need weight of numbers and public shame on your side before VM will even admit there is an issue. Good luck.