We have an Ooma VOIP home phone. We have two mobile Android AT&T phones (one running Android version 9, the other version 14), both running Norton 360 version 5.76.0.231201002. Our home phone number is in our Android's phone contacts list. We have no phone numbers in our Android phone's call blocking list. When we make calls from our home VOIP phone to either of our two mobile phones, our calls go directly to voice mail (never rings -- symptoms similar to call blocking). Was wondering if Norton might be blocking the calls, and if so, how to correct the issue.
Thanks for posting back. But for our curiosity, it would be nice if you could post back if/when you get a solution.
I might add one more observation. My calls from my OOma home phone to my AT&T mobile phones only go directly to voice mail if I have "show caller-id" enabled on my home phone. Disabling showing caller-id allow the calls to ring, but they show only as "private" (which is expected). I uninstalled Norton on my AT&T mobile phones, and this did not resolve the issue. The only calls that go directly to voice mail are calls originating from my home phone and targeted to AT&T mobile phones. I had Ooma engaged, who ran call traces and verified the calls are leaving their servers correctly. I have now engaged AT&T and they are working the issue. Since removing Norton did not resolve the issue it appears Norton is not the problem, thus closing this ticket.
I would dial *80 to test whether call blocking numbers has been set by default. I have the same version Norton Mobile installed on Galaxy Z-Flip 5 with Android 14 ( Verizon ), I do not see this taking place my side.
SA
How long has this been going on? Any changes when it started?
Do you have any issues with other calls going directly to voicemail?
A quick way to test is to uninstall Norton from one of the phones and try calling your home phone number again.