How to Block Phone Number When Calling: The Signaling, Routing, and Detection Layers Explained

You block a phone number when calling by sending a calling-line-identification restriction code that tells the network to withhold your number, typically by prefixing the call with *67 on landlines and many mobile carriers, or by enabling a permanent "hide my number" setting in your phone's call settings. The network then delivers the call without your number, or with an anonymous placeholder, depending on the receiving carrier's handling of restricted caller ID. The specific prefix, menu path, and even whether the block survives depends on a stack of technologies most users never see.

This explainer goes one level deeper than the usual tip sheet. It covers how the signaling actually works, where blocks leak, which thresholds matter, and what you can and cannot control from the handset.

Mechanism: how a number gets hidden in the signaling path

Every call begins with a setup message that travels separately from your voice. In the traditional telephone network, and in most modern interconnects, that setup message carries fields for calling party number (the number itself) and presentation indicator, a flag that tells the receiving side whether to display, restrict, or suppress the number. The presentation indicator is the switch that matters. When you dial a prefix or toggle a setting, you are asking your originating network to set that flag to "presentation restricted" before the call leaves your carrier.

The receiving network reads the flag and decides what to do. If the flag says restricted, the terminating switch will typically either omit the number entirely or replace it with an anonymous marker such as "Private" or "Restricted." The call still connects. The number simply does not travel in a displayable form.

Here is the counterintuitive detail most articles miss: in many network configurations the calling number is still transmitted in the raw signaling, even when the presentation flag tells the handset not to display it. The restriction is a display instruction, not always a cryptographic erasure. That distinction matters for anyone who assumes a blocked call is untraceable. Protocol-level metadata can persist through interconnects and be visible to carriers, lawful-intercept systems, and some enterprise telephony platforms even when your contact's screen shows nothing.

Prefix codes exploit this architecture. In the United States, *67 is a common per-call vertical service code for calling-line-identification restriction on landline and some mobile networks. The exact behavior varies by carrier, and some mobile carriers ignore or override the prefix depending on account settings and the destination network. Plain-language version: the prefix is a request, and the network decides whether to honor it.

Quantified context: how common blocking is and where it fails

Caller ID spoofing and unwanted calls are large enough that regulators track them. The Federal Communications Commission has reported that unwanted calls generate hundreds of thousands of complaints each year, and the agency has pushed carriers to deploy STIR/SHAKEN, an authentication framework that cryptographically signs the calling number at the originating network. That framework addresses a different problem (whether the displayed number is genuine) but it interacts directly with blocking, because an authenticated number can be labeled and filtered more reliably than an anonymous one.

The practical numbers are less tidy. Per-call prefixes like *67 generally work on plain voice calls but are routinely dropped when the call traverses certain VoIP gateways, when the destination is an emergency line, or when the receiving carrier's policy forces number delivery. Emergency calling is the clearest example: in the US and many other jurisdictions, calling-line identification is presented to emergency services regardless of your restriction request, because dispatchers need a callback path. That is not a bug. It is a deliberate policy override built into the routing rules.

Another number that matters: permanent versus per-call settings often diverge. A per-call prefix applies to one dialed call. A line-level setting applies to every call until you change it, and it may be stored on the carrier's switch rather than the handset. Users routinely set one, forget it, and then wonder why their number stopped appearing to everyone.

Timeline: what happens between dialing and display

Each stage is a potential leak. The timeline also explains why testing your block from two different phones, on two different carriers, can produce two different results.

Edge cases: emergency services, enterprises, and international calls

Emergency calling is the most consequential edge case. When you dial an emergency number, the presentation restriction is typically ignored so dispatch can reach you. Relying on *67 during an emergency is not a safety strategy.

Enterprise phone systems add another layer. A company private branch exchange can override the handset's presentation setting and force a main switchboard number onto outbound calls. That is often a compliance or branding decision, not a user preference. If your work phone shows the company's number instead of yours, the cause is usually the PBX configuration, not your handset.

International routing introduces flag-translation problems. A restriction set on one carrier's network may be translated, dropped, or reinterpreted at an international gateway. Some countries have stricter or looser policies about honoring foreign presentation flags, and the result is unpredictable from the caller's side. VoIP and app-based calling add a third variable: the app's own privacy setting may control what the receiving party sees, independent of the underlying carrier.

Misconceptions: what blocking does and does not do

The most persistent misconception is that *67 makes you anonymous. It does not. It requests display suppression. Carriers, lawful-intercept systems, and some platforms can still see the signaling metadata. A second misconception is that blocking your number prevents the recipient from calling you back or finding you. It does neither. It only affects display on that call.

A third misconception is that a permanent setting is universal. A carrier-level restriction may not follow you to a different network, a different country, or a VoIP app. A fourth is that caller ID blocking and call blocking are the same tool. They are opposites: caller ID blocking hides your number from others, while call blocking (using your phone's block list or carrier-level blocking) stops others' numbers from reaching you. These are easy to conflate, and the confusion leads to wrong expectations.

Red-flag warnings to keep in mind:

Do not assume a hidden number protects you from a callback or from carrier records. Do not rely on *67 for emergency calls; dispatch usually sees your number regardless. Do not expect a per-call prefix to work identically across carriers and countries. Do not confuse hiding your number with blocking incoming calls. Do not assume a work phone's displayed number reflects your handset setting; the PBX may override it.

Comparison: methods for hiding your number when calling

The table shows why no single answer fits every situation. The method you choose should match the scope you need and the network you are on.

Practical actions: concrete steps and thresholds

The steps below are general and carrier-dependent. Exact menu names vary, and the safest approach is to verify with your carrier's own documentation rather than a third-party tip.

Decide the scope. For a single call, use the per-call prefix your carrier supports. For every call, change the line-level setting. Test before you rely on it. Call a second phone on a different carrier and confirm what the screen shows. Check the handset menu under call settings for a "hide number" or "caller ID" toggle, and note whether it is per-call or permanent. Confirm with your carrier whether the setting is stored on the switch or the device, since the two can disagree after a SIM swap or device change. For work lines, ask your telephony administrator whether the PBX forces a main number onto outbound calls. For emergency readiness, keep in mind that restriction requests are generally overridden for emergency calls, so plan accordingly.

Thresholds worth remembering: per-call prefixes apply to exactly one call; line-level settings persist until changed; emergency overrides apply regardless of your setting. Reconciling these: a per-call prefix is the lowest-commitment option and the most likely to be ignored at a gateway, while a line-level setting is more consistent but harder to reverse if you forget it.

Limitations: what no setting can guarantee

No handset setting can guarantee full anonymity across every network, and none can prevent carrier-level logging. The presentation indicator is a request that networks may honor, translate, or override depending on policy, jurisdiction, and routing. STIR/SHAKEN improves trust in displayed numbers but does not make restricted numbers invisible to carriers. Verification is the only reliable path: test from the actual device and network you will use, and confirm with your carrier what their switch actually does.

This article is general educational information about telephony signaling and privacy settings, not legal, safety, or telecommunications advice for your specific situation. It does not promise anonymity or any specific outcome, and carrier behavior varies. For emergencies, contact local emergency services directly and assume your number is visible to dispatchers.