You block your caller ID by dialing a carrier-specific prefix before the number (for example *67 on most US landlines and many mobile carriers, 141 in much of Europe) or by toggling a per-call or persistent setting in your phone or carrier account. The network then flags the call as "presentation restricted," and the recipient's handset shows "Private," "Anonymous," or "No Caller ID" instead of your number. That is the entire mechanism at the user level. What happens next depends on signaling standards, carrier configuration, and the receiving device, which is why blocking your number is more conditional than most guides admit.

How Caller ID Blocking Works in the Signaling Layer

Caller ID is not a single feature; it rides on two separate signaling channels that behave differently. The calling number travels in the Caller ID (CID) field of the initial setup message, typically as part of the ISDN User Part (ISUP) signaling or the SIP From/PAI headers in modern networks. A separate "presentation indicator" field tells the terminating network whether that number may be shown. Blocking your number does not delete it from the signaling path; it sets the presentation indicator to "restricted."

This distinction matters because the number usually still traverses the network. The recipient's carrier receives it even when the handset is instructed not to display it, which is why call-detail records and lawful intercept systems can still resolve the caller. The handset honors the restriction flag and renders "Private" or "Anonymous." On some networks, the originating carrier strips the number before handoff, but this is a policy choice, not a standard requirement.

The mechanism is also asymmetric across call types. PSTN-to-PSTN calls rely on ISUP signaling with mature, well-defined presentation semantics. VoIP and app-based calls may substitute SIP headers, and not every gateway maps the restriction flag faithfully. That gap between "flagged restricted" and "actually hidden" is where most confusion about how to block your number when calling originates.

Plain-language version: your phone or carrier marks the call as private, and the other side's phone decides whether to believe that mark.

Quantified Context: How Often Blocking Actually Works

Blocking reliability is high but not absolute, and the failure rate is concentrated in specific call paths. On traditional mobile-to-mobile calls within a single country, per-call blocking succeeds in the large majority of cases because both carriers implement the same ISUP presentation semantics. Cross-carrier and cross-border calls degrade: international gateways sometimes pass the number through despite the restriction flag, and some enterprise PBX systems ignore it entirely.

Caller ID spoofing is the dominant real-world failure mode, and it is widespread. The FCC has documented that spoofed calls number in the billions annually in the US, and the STIR/SHAKEN framework (mandated for IP-originated calls since June 2021) was introduced specifically because legacy signaling could not authenticate the number being presented. STIR/SHAKEN adds cryptographic attestation of the calling number, but it authenticates rather than hides: a call you flag as restricted is still a call whose originating number the carrier can see.

Two thresholds deserve explicit reconciliation. The FCC's spoofing rules prohibit transmitting misleading caller ID "with the intent to defraud, cause harm, or wrongfully obtain anything of value" (47 CFR 64.1601), which is a legal standard, not a technical one. STIR/SHAKEN attestation levels (A, B, C) describe how confident the originating carrier is that it knows the caller, not whether the caller is trustworthy. These are different things: a fully attested call can still be a scam, and a restricted call from you can still be fully attested. Do not conflate legal prohibition with technical prevention.

Edge Cases: Where Blocking Fails or Backfires

Several scenarios routinely defeat per-call blocking, and knowing them prevents false confidence:

Emergency calls. Dialing *67 before 911 (or the local emergency number) is either ignored or refused; dispatchers need your number. Never rely on blocking for emergency contact. Toll-free and some business lines. Many 800-number systems use automatic number identification (ANI), a separate signaling field from caller ID. ANI is generally not suppressed by presentation restriction, so businesses may still see your number. Enterprise PBX and call-center platforms. Some systems are configured to ignore presentation restrictions and display the number anyway, particularly for recording and compliance. International roaming and cross-border gateways. Restriction flags are inconsistently mapped between signaling variants; expect failures. App-based and VoIP calls. Behavior depends entirely on the app's gateway implementation. Text messages. Per-call blocking prefixes generally do not apply to SMS; you need carrier-level or app-level controls.

The counterintuitive professional caveat: blocking your number can reduce your own call completion rate. Many people and businesses now screen "Private" and "Anonymous" calls aggressively, and some carriers label them as suspected spam. A blocked number is not a neutral choice; it is a signal that recipients increasingly treat as a red flag. If your goal is to be reached, blocking may work against you.

Common Misconceptions About Hiding Your Number

Misconception one: blocking deletes your number from the network. It does not. It sets a display instruction. The number is transmitted, logged, and available to carriers, and often to the receiving party's carrier-side services even when the handset shows nothing.

Misconception two: *67 works everywhere. It is a North American carrier feature with wide but not universal support, and its behavior on mobile varies by carrier and plan. In much of Europe the equivalent is 141; other regions differ, and some carriers require account settings instead of prefixes.

Misconception three: blocking is permanent or per-call with one method. These are different tools. Per-call prefixes affect one call. Persistent settings (carrier account "anonymous calling" or phone settings) affect every call until changed. Choosing the wrong one produces the wrong outcome.

Misconception four: blocking protects your identity from the person you call. It hides your number, not your identity. Voicemail, call-back systems, and prior context can reveal you, and any recipient using a call-tracing feature can often recover the number. Privacy from a determined recipient is not what caller ID blocking provides.

Misconception five: STIR/SHAKEN hides or spoofs numbers. It does the opposite: it proves which carrier originated a call. It is not a privacy tool for callers.

Practical Actions: Choosing the Right Method and Verifying It

Pick the method that matches your goal, then test it before relying on it.

Per-call prefix: dial the carrier prefix, then wait for the prompt tone, then the number. On most US carriers this is *67. Confirm your carrier's prefix in your account documentation, because some require different codes or none at all.

Persistent setting via carrier: most major US carriers offer an "anonymous caller ID" toggle in the account portal or app. This applies to all outgoing calls until disabled. It is the right choice when you want blocking every time.

Device-level setting: iOS and Android expose caller ID settings that, depending on carrier, either request network-level blocking or only affect certain call types. Treat device toggles as convenience, not guarantee; verify with a test call to a second phone you control.

Threshold to apply: if the call is to a business, a government office, or anyone who may need to call you back, do not block. If it is a one-off call to a number you do not want to share with, block per-call and accept the screening risk. If you must be reachable and private, use a secondary number rather than blocking your primary.

Verification step: call a second device with caller ID display and confirm the display shows "Private" or "Anonymous," not your number. Repeat across carriers if the call crosses networks.

Caller ID blocking is a display instruction, not an anonymity service. It cannot prevent lawful access to the calling number by carriers, emergency services, or law enforcement acting under legal process. In the US, the Truth in Caller ID Act and FCC rules govern spoofing, but they do not create a right to conceal your number from the network. Separately, the FTC's guidance on caller ID and the FCC's robocall resources address spoofing and screening rather than concealment.

The practical ceiling is this: blocking reliably changes what a typical handset displays on a domestic call, and it unreliably changes anything else. It does not secure anonymity against a motivated recipient, a business using ANI, an enterprise PBX, or a cross-border gateway. Anyone selling guaranteed anonymity through caller ID blocking is describing a capability the signaling standards do not provide.

For calls involving safety, legal exposure, or financial transactions, do not rely on caller ID blocking as a protective measure. It is a display preference with known failure modes, not a security control.

This article is general educational information about call signaling and privacy, not legal advice or a security guarantee. Rules and carrier features vary by jurisdiction and change over time; consult your carrier and, for legal questions, a qualified local professional. If you are in immediate danger, contact local emergency services rather than attempting to conceal your number.