Read the forum guidelines
I am getting an increasing number of these malicious calls that seem to high-jack my Cox Telephone service. I am subjected to a very loud harassing alarm sound throughout my house from my answering machine and my three hand sets. This must be an FCC violation. Please use the following URL to listen to the last one I recorded from my answering machine.
Please advise on how I can stop this.
If you are currently subscribed to selective call rejection, you can block that call from getting in.
Allan - Cox Support Forums Moderator
I have tried to do so by using the *60 #01# on my telephone dial pad but since the call ID is unknown that does not work. Were you able to listen to the .mp4 recording of the call that I posted the link to? It sounds like something more than just the annoying sound is going on with these calls.
Not much you can do about "unknown" calls. AFAIK Cox has a feature called anomous call rejection, which blocks a call if the caller ID is set to "Private", as in blocked by the carrier, but it doesn't block phone calls of people/things calling in with NO caller ID or missing caller ID data. This is because some people (Doctors offices, governmental offices, correctional facilities, etc) don't have caller ID attached to their lines, so the feature would block them too. TBO other providers have newer systems that can block those types of calls, but Cox does not. Oddly enough, the Cox Business feature by the same name (anom. call rejection) CAN be configured to block "Unknown" callers, so there is hope Cox residential will get the feature too with the upgrades talked about coming. Fingers crossed
Thank you WiderMouthOpen - (What a moniker!) for the additional information and background. I would really like to see the ability to block "Unknown" ID callers. This brings me to another question. I receive some calls with the caller ID as "Private". Are "unknown" and "private" caller ID's handled the same? I ask because my nephew's caller ID shows as "private".
Inland said:(What a moniker!)
In case anyone is curious; was testing the new forum late and had to think of a new username fast when the database reset. I am a huge WKUK fan and this happened to be playing in the background so..
Ahhh... now I understand WiderMouthOpen : >O
Sounds like your answering machine didn't see a disconnect signal and stayed off-hook. That screeching sounds like Cox's "howler". Leave a phone open and you'll hear the voice telling you to hang up, followed shortly be the howler.
Thank you, dward
Yes, I believe you are correct. It didn't dawn on me that these are the "Cox Howler" one gets if they leave their phone off hook. What I can't figure out is how an incoming call can cause this. I don't lift my phone off hook to initiate a call nor do I pick up to answer the call. Incoming calls normally disconnect after the calling party hangs up. Why would a robo or telemarketer caller do this? They're not going to sell anything by doing this. This is why I feel like these calls are initiated by some malicious caller(s) who manage to hack the COX system to simply harass. How can they make it as though I initiated the call or I left the receiver off hook? Or, is this simply a Cox telephone system technical malfunction? BTW, I was sleeping in this morning and got another one of these at 9:30 AM.
It sounds like your answering machine answered the call and was waiting for a response. Maybe if you increased the number of rings for it to answer it might happen less, most robocallers don't wait more than a few rings. Also, most answering machines have a setting to detect when the caller has hung up.
dward is correct. they finally got a supervisor to our house who remembered from in the day when the phone segment of their business was here too that there's something called "c.o.d.?" or something similar (p.o.d.?)that is a standard setting. turning it off (they have to do this in their equipment) helped our situation a lot. it happens when someone triggers your machine, hands up, and their equipment doesn't release your line. now we get 4-5 seconds of busy beep. cox insists that's our phone & nothing they can do about it. not sure i buy it, but will get new phones someday & we'll see. ask cox to specifically check for this & if it's on your line ask them to turn it off & see if that works.
Thank you, socal transplant.
Maybe dward will chime in with more of an explanation of the p.o.d or c.o,d setting. How would the end user be able to know if there line is set to this or not?
Anyway, since I have brought this problem up and aired it here I have not been having the problem... so far.