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 ]

[snozski]

Nice to hear they might have fixed it 🙂 i just rebooted , cleared phone log , lets see 

[Chris_Myers]

I rebooted at 10:30 this morning (having obtained permission from "she who must be obeyed").  So far no ghost calls.  It is looking promising, but does beg the question what was all the fuss about and why could this not have been fixed 12 months ago.  Perhaps at last there was someone in authority prepared to drive this to conclusion?  There will of course be no official statement on this - it never happened - Honest!

[Chris_Myers]

It was never really about compensation, just trying to light a fire under an organisation that refused to act responsibly and to value its customers.

[snozski]

I just wanna thank Chris Myers I feel like without all of his hard work making formal complaints and keep on at them this would never be fixed.   Thanks mate I appreciate it , and yes it seems fixed now 🙂

[fraserormston]

I second Snozski cheers Chris 

[TKD]

rebooted sat 11pm cleared logs off phone and looks like did the trick so far no (no number calls I too would like to thank Chris Myers for his hard work and free time he has wasted all because a massive company wouldn't admit they were wrong 99% of people would have gave in when given a load of cr*p from VM well done mate.

[Chris_Myers]

Thanks go to all of you for keeping me sane. I really cannot understand the corporate lack of care and responsibility to its user community. A very simple apology, direct contact, and regular updates would have gone a long way to addressing this.  There are some real lessons on internal communication, customer relations, and management oversight to be had (I still cannot believe statements that there was "no point taking it to management as a technical team was already on it" and that a "manager could do no more").  I would hope that VM consider a management review over this affair with feedback on lessons learned.  but somehow, I doubt it.

As has already been said, it would be nice to know what the issue was and how it was resolved, but again not holding my breath.

On another note, anyone know how we archive this thread now we seem to have come out of the end of this issue?

Finally, nice to have virtually met you all and well done one and all.

[lenworth]

Thanks to you, Chris, and everyone else who contributed to the thread. We got there in the end!

John

[Chris_Myers]

Credit where credit is due.  Someone at VM has investigated the issue, developed, and rolled out a solution. So on behalf of us all, please pass on our thanks to the team/individuals responsible. Whatever the solution was, seems to have resolved the ghost call issue. 

There has been a lot of conversation and it is important to say it was not about individuals, but a message of corporate policy/procedural failure as discussed previously.

[TAZMANUK]

I wouldn't archive this yet, as if you recall I found the 1 hour in front issue and we won't know if that's also fixed until clocks change again, and hoping it does not bring back the ghost calls