Forum Discussion
I'm having the same issue - It's a scammer claiming to be a Microsoft representative. The caller ID is MY land-line number so I can't block it (...or CAN I?)
- Bruce6 years agoHonored Contributor III
Locally, yes. Why would you ever call yourself?
- CurtB6 years agoValued Contributor III
You might want to call yourself to hear your voice mail messages (*298 will do the same thing). However, while I can add numbers to call screening (*60), adding my own number didn't prevent me from calling myself. So, it would appear you can't block your own number, at least not from calling it from your own phone. I can't say what happens if it's a scammer calling from another phone.
- Bruce6 years agoHonored Contributor III
I disagree. If you prefix a call with an asterisk, (Star Code (*298)), you're initiating a telephone-service feature...not a telephone call.
If your local exchange "hears" the tone for an asterisk, it moves your call "upward" into the telephone hierarchy as opposed to "outward" towards another exchange or another telephone connected to the same exchange.
This upward connection is into the telephone-service-feature system of your provider and ultimately, in this case, to the Cox Voice Mail server or gateway. When you include your telephone number with the Star Code, it's just informing the server or gateway which account to check.
This upward direction...as opposed to outward...is why Star Codes are technically called Vertical Service Codes (up vs. out).
Perhaps entering your own telephone number into Selective Call Rejection confuses the Cox terminating switching-system. Cox should fix this discrepancy. However, you can't "call yourself" because at most you'd get a busy signal.
Related Content
- 8 months ago
- 9 years ago
- 31 days ago
- 2 months ago
- 5 years ago