In the last 25 hours, my phone has called itself.

Unless Nomo specifically and automatically blocks calls spoofed with your own number, you shouldn't report it to Nomo.  First, if your number is in the Nomo database, Nomo subscribers can't call you.  Second, Nomo limits the amount of telephone numbers on their list.  If you're the only one reporting your number, Nomo probably won't add it.

You should only block your number locally at your telephone or call-blocking device...or use Selective Call Rejection.

Locally, yes.  Why would you ever call yourself?

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.

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.

MSN home page URL, I do hope your question was answered.  Your original post seems to have taken a turn, but in the process, maybe we'll figure out a solution for you.😃

Bruce, I feel like your interpretation of what I said didn't sync up with my intended meaning.  My comments were a description of what I tested with my phone and an assessment of what I observed.  When I said calling my own number gets my voice mail messages and entering *298 does the same thing, it was to inform anyone who might not already know, that entering *298 gets the same results as keying in the phone number, i.e. voice mail messages.  (Other voice mail options are also available).  I didn't say, imply or in any way intend to convey the notion that keying *298 into a phone will initiate a phone call. 

Accessing voice mail by calling my own number on my own phone isn't anything new because it worked the same way on the old platform.  The one thing I noticed that is different is that calls to my own number were logged in "Voice Tools" call history on the old platform, but are not logged in the new one.

Calling my own Cox phone number from my own Cox phone does not get a busy signal.

Bruce, have you tried calling your own Cox phone number from your own Cox phone recently?

Other Cox phone customers, do you get a busy signal when you call your own Cox phone number from your own Cox phone?  (There may be something easier to test than this, but nothing comes to mind at the moment).  Please test it and post back.  If you don't mind, please indicate whether you have voice mail turned on.  Thanks.

Bruce, I wouldn't necessarily interpret not being able to block your own phone number with Selective Call Rejection as a discrepancy.  Cox may have done that intentionally so that customers don't inadvertently disable the ability to access their voice mail.  However, before accessing voice mail, Cox must determine that the phone number entered is the customer's own number and verify that it was entered from the customer's own phone.  So, if they're able to do that, theoretically, Cox should be able to identify when the sending number is the customer's number, determine when the call was not originated from the customer's phone and block it by default.  That would prevent scammers from being able to spoof the phone number of the call recipient.  Maybe someone at Cox could consider queueing this up for evaluation and if deemed to be an accurate assessment, move it through their program change process.

This is an interesting set of postings.  I have not had this Spam, but have heard others receiving this.

CurtB, I tried calling my own COX phone using my handset.  I get a message "for US English, press 1" but don't get any Busy signal....like something I remember from the past.  Not sure where the message was going to go...I entered 1, but left after that.

I find that under Voice Tools/Call History, there is a Voice Mail.  This is using COX, and not the Voice Mail recording that my landline uses to the phone directly.  Looking at the timestamps, I'm guessing that the COX Voice mail receives messages when I'm on the phone talking.  Since my phone is busy, people cannot leave a voice mail to it, and maybe it rolls over to the COX voice mail.  Not sure if this is the correct conclusion