You block your number by activating a carrier-level calling feature—vertical service code *67 for a single call, or a permanent line setting—that instructs the network to withhold your calling party number from the recipient's display. The request travels as a privacy flag inside the call setup message, so the suppression happens before the phone rings, not on the receiving handset.

Caller ID is not a single switch on your phone. It is a negotiation between two networks, governed by signaling standards that date back to the 1960s and were formalized for digital networks in the 1990s. Understanding where in that negotiation the privacy instruction lives explains why some calls arrive as "Anonymous," some as "Restricted," some as a name with no number, and some with your number fully intact no matter what you pressed.

The signaling path of a withheld number

Every call begins with a setup message. In modern networks this is built on Signaling System 7 (SS7), the out-of-band protocol that carries call control between carrier switches. The calling party's number is encoded in a field called the Calling Party Number (CPN) parameter. Separately, a Calling Party Number Presentation indicator sits alongside it, and that single binary indicator is what does the actual blocking.

When you dial *67, your originating switch sets the presentation indicator to "presentation restricted." Downstream switches read that flag and instruct the terminating equipment to suppress the number from the display. The number itself often still travels through the network—it is the display instruction, not the data, that changes. This distinction matters later, because it is why certain institutional lines can still see through the block.

Signaling System 7 separates the voice path from the control path, which is why a privacy instruction can be honored even when the two carriers use different equipment generations. The flag rides in the control channel, gets translated at each network boundary, and is finally interpreted by the receiving switch. On a landline, the receiving central office formats the display data it sends to the phone. On mobile, the same instruction propagates through the visited network and the home network before reaching the handset.

The flag is binary in principle: present or restricted. In practice, carriers implement several intermediate states, which is why the display text varies. "Anonymous" typically means the network received no usable number at all. "Restricted" or "Private" usually means the number was sent but flagged as withheld. The wording is a carrier choice, not a standard.

Quantified context: why the block is less common than it looks

Caller ID display penetration in the United States is effectively universal on landlines and standard on mobile plans, which makes suppression a visible, deliberate act rather than a default. The feature itself is old: AT&T introduced *67 as a vertical service code in the 1980s, and the codes were standardized so that the same star-plus-two-digits pattern would work across competing carriers.

The practical asymmetry is large. A withheld call still consumes the same network resources as a normal call, but the recipient loses the ability to screen, block, or return the call. That is the entire point, and it is also why regulators have layered exceptions on top of the basic feature. Emergency calling is the most important: in the United States and most of Europe, a call to emergency services ignores the privacy flag and delivers the callback number and location data regardless of what the caller dialed.

Different carriers implement blocking across three broad layers, and the layer you use determines what the recipient sees:

Method Scope What the recipient sees Reversible per call
*67 prefix One call Restricted or Private Yes, automatically
Carrier privacy setting All calls on that line Restricted or Private Only by disabling it
Phone OS "hide number" toggle All calls from that device Depends on carrier support Yes
Third-party calling app App-routed calls only Varies by service Varies
VoIP provider admin setting All calls on the account Often Anonymous Account-level change

The table rows matter because people mix them up. A prefix applies to that call and expires when you hang up. A carrier setting persists until you change it. An app toggle only affects calls the app routes, which is why a hidden-number app can leave your normal cellular calls fully identified.

Edge cases: where blocking behaves unexpectedly

The flag is interpreted at the receiving end, which creates predictable failure modes. A private branch exchange (PBX) at a business can be configured to override display instructions and show the raw CPN parameter—the number that traveled through the network but was flagged for suppression. Many enterprise phone systems do exactly this for inbound call logging. Legitimate operators, fraud teams, and some call centers rely on it.

Toll-free routing adds another layer. Calls to 800-numbers often deliver the calling number to the business because the receiving party pays for the call and carriers contract for automatic number identification. In that path, *67 can be defeated by design.

International calls introduce translation points. A privacy flag set in one country's signaling may be mapped, dropped, or reinterpreted at the gateway between networks. The result is that a call blocked on your end can arrive identified abroad, and vice versa.

There are red-flag behaviors worth recognizing:

A caller who insists on staying anonymous while asking for payment, credentials, or personal data is using the feature as cover, and legitimate institutions rarely do this. A withheld number combined with urgency and a threat of account closure is a common impersonation pattern. Calls that display "Anonymous" but claim to be from a government agency should be verified through a published number you look up yourself. Blocking your own number does not make you untraceable to law enforcement or to the carrier, which retains call detail records.

Misconceptions that survive because the mechanism is invisible

The most durable myth is that *67 makes you anonymous. It does not. It withholds the display. The carrier still logs the originating number, the time, and the duration in call detail records, which are retained under legal and regulatory requirements and are available to subpoena. The feature changes what the recipient sees, not what the network knows.

A second misconception is that blocking works identically on every phone. It does not, because the handset only formats what the network sends. Updating your phone's software cannot add a privacy capability your carrier has not provisioned.

A third is that *67 is universal. The star codes are standardized within North America, but the exact sequence and availability vary by country and by carrier. Some VoIP services implement blocking as an account preference rather than a dialed prefix, and some prepaid lines disable the feature entirely.

The counterintuitive professional caveat is that a withheld number can sometimes make a call look more suspicious to automated screening systems than an identified one. Modern spam analytics score calls partly on presentation consistency. A number that is normally presented and suddenly arrives restricted can trip a higher-risk classification, so the block can work against the caller who is trying to sound legitimate.

Practical actions: how to block and how to verify

The reliable method depends on which layer you control. For a one-off call, dial the prefix before the number on a landline or mobile line in North America. For a persistent block, change the setting in your carrier account portal or call support, because the permanent privacy option is a line feature, not a phone feature.

On a smartphone, the operating system toggle labeled something like "hide my number" or "show my caller ID" simply requests the same network instruction. Verify it with a test call to a second phone you control, not to a business, because a PBX may override the display and give you a false result.

For VoIP and business lines, the setting usually lives in the account's outbound caller ID configuration, often as a per-extension or per-trunk option. Change it there, then confirm by calling a phone that displays raw network data rather than a curated contact name.

A workable verification sequence:

Call your own second line and note exactly what appears. Repeat with the block enabled, then disabled, to confirm the toggle is the variable. Test a call to a toll-free number, where the block may be overridden. Record the display text your carrier uses, because "Private" and "Anonymous" mean different network states. For business lines, confirm with the PBX administrator whether inbound logging ignores the flag.

Thresholds to reconcile: there is no single national rule for how long carriers retain call detail records, and retention periods vary by jurisdiction and carrier type. Do not assume a fixed number. What is consistent is that the record exists independently of the display flag.

Limitations and what blocking cannot do

Blocking your number changes one field in one signaling message. It does not encrypt the call, mask your location from the network, prevent the carrier from logging the call, or stop a receiving PBX from overriding the display. It also does not protect against callback tracing through voicemail or through the content of the call itself.

Availability is not guaranteed. Emergency calls bypass the feature by regulatory design. Some carriers restrict permanent blocking on certain plan types. International gateways may strip or reinterpret the flag. And because the recipient's equipment controls the final display, no setting on your side can force a specific result on the other end.

The honest summary is that number blocking is a display-privacy instruction with a narrow, well-defined scope. It works reliably within North America for ordinary person-to-person calls and fails predictably at the edges: emergency services, enterprise phone systems, toll-free routing, and cross-border gateways. Knowing which edge you are standing on is the difference between a feature that works and one that quietly does not.

This article is general educational information about telecommunications signaling, not legal advice or a guarantee of privacy outcomes. Laws governing caller identification, call recording, and data retention vary by jurisdiction. Consult a qualified local professional for guidance specific to your situation.