You can block your number when making a call by dialing a carrier feature code before the destination number, typically *67 on landlines and mobile phones in North America, or by enabling a per-line privacy setting in your phone or carrier account. On GSM networks the same request travels as a Calling Line Identification Restriction flag, and on VoIP systems it is a Privacy header. The block is a signal sent with the call setup, not a setting on the recipient's phone.

The signaling mechanism behind a hidden number

Caller ID is not transmitted by your phone directly to the recipient. It rides inside the call setup messages that establish the connection. On traditional telephone networks, the calling number travels in Signaling System 7 messages, a separate control channel that carries setup data before any voice path opens. Your handset asks the network to withhold that field, and the network decides whether to honor it.

On mobile networks the equivalent request is a CLIR, or Calling Line Identification Restriction, parameter inside the setup message. A phone can send two versions of the flag. One version applies only to that single call. The other version, set in the device or subscriber profile, applies to every call until switched off. That distinction explains why *67 and a phone menu toggle sometimes behave differently.

Voice-over-IP systems handle the same idea through a SIP header called Privacy. When the header reads "id," the originating provider strips the number before the invitation reaches the destination. Each hop in the path must respect the instruction. A single provider that ignores it can expose the number downstream.

The critical detail is that suppression is a request, not a guarantee. The originating network honors it by omitting or masking the number field. Nothing in the standard forces every downstream carrier, private branch exchange, or app to honor that omission. The plain-language version: your carrier hides the label, but it cannot control every machine that reads the package.

Quantified context: codes, flags, and coverage

The most common per-call code in North America is *67, dialed before the ten-digit number. On many business systems the same function is *82 to unblock a line that blocks by default. GSM handsets use a menu path, often under Call settings, with a line labeled "Hide my number" or "Caller ID." The network-side equivalent is a subscription service, sometimes free and sometimes billed monthly, that blocks all outgoing calls until deactivated.

Vertical service codes are standardized in the United States by the AT&T-owned code system that carriers share, and the major ones have been stable for decades. The Federal Communications Commission describes *67 as the standard per-call blocking method, and it notes that blocked calls still reach emergency services with location data in most cases. The FCC also documents that blocking is not absolute when the receiving party subscribes to a caller ID block override service.

Coverage varies by technology. A 2023-era survey of carrier documentation shows per-call codes supported on nearly all circuit-switched and VoLTE lines in the US, but support on some VoIP apps depends on the provider's configuration. Business phone systems often enforce policy at the PBX, overriding the handset request. International roaming can strip the flag at the visited network, so a *67 call placed abroad may arrive with the number visible.

Edge cases that change the outcome

Emergency calls are the largest exception. In the US and most of Europe, dialing 911 or 112 bypasses suppression so dispatchers can call back. The FCC states that emergency callers' numbers are transmitted for callback and location purposes regardless of blocking settings. Attempting to hide a number from emergency services is both futile and potentially dangerous.

Toll-free numbers and many business lines subscribe to automatic number identification, a service separate from caller ID. The receiving system may recover the number even when the display shows "anonymous." This is why a blocked call to a bank or insurer can still be matched to your account. The counterintuitive detail: the display you see and the data the recipient's system receives are two different streams, and suppression usually affects only the display.

Callbacks also reveal identity indirectly. A recipient who misses a blocked call and dials the number back through a carrier service can sometimes reach you, because the return path uses normal signaling. Voicemail systems sometimes record the originating number in metadata even when the display is masked. Conference bridges and call recording platforms may log the full number on the host's side.

Common misconceptions about hidden numbers

The first misconception is that blocking is permanent once set. Most per-call codes apply to a single call, and the next call shows your number again. The second is that a phone setting always overrides the network. A carrier subscription can override a handset toggle, and a PBX can override both. The third is that "anonymous" on the recipient's screen means no data exists. It means the display field was empty; other fields may still carry the number.

A fourth misconception is that blocking protects against spam filtering. Modern call-filtering apps use reputation databases and call-pattern analysis, not just the caller ID field, so a blocked number can still be flagged. A fifth is that the recipient cannot tell a blocked call from a private line. Some phones label both as "Unknown," while others distinguish "Anonymous" from "Private," depending on the signaling code used.

Comparison of blocking methods

Method Scope Where set Typical cost Reliability Notes
*67 prefix Single call Handset dial string Free High on US carriers Must dial before every call; lost on some VoIP apps
Phone menu toggle Device-wide Handset settings Free Medium Carrier or PBX can override
Carrier subscription All calls Account or customer service Often free, sometimes billed monthly High Persists across devices and reboots
VoIP Privacy header Per call or account Provider portal Varies Medium to high Depends on downstream carriers
Business PBX policy All lines System administrator Business cost High Usually enforced regardless of handset
Third-party app Per app App settings Free to paid Low to medium Must route calls through the app

Timeline of what happens during and after a blocked call

Stage Timing What occurs Who sees what
Dial and code entry Instant Handset sends CLIR flag with setup message Carrier sees request
Network processing Milliseconds Originating switch honors or rejects the flag Carrier logs request
Delivery to recipient Under 1 second Number field stripped or masked Recipient display shows anonymous
Connection Call duration Voice path proceeds normally Both parties hear audio
Voicemail metadata At recording System logs may retain originating data Host or operator may see number
Callback attempt Minutes to hours Recipient dials back via carrier service Number may resolve normally
Billing records Days to months Carrier retains call detail records Carrier and authorized parties

Practical actions and thresholds

Start with the cheapest method. Dial *67 before the full number and place the call. Confirm the recipient sees "anonymous" or "private" on a test call to a trusted line. If the display still shows your number, your carrier or PBX is overriding the request.

For persistent blocking, log into your carrier account and look for a privacy or caller ID section. If the option is absent, call customer service and ask for a per-line block subscription. Record the date and representative name. Test again after 24 hours, which is typically the provisioning window for account changes.

On a smartphone, open the phone app settings and locate the caller ID or additional settings menu. Toggle "Hide my number" and place a test call. On dual-SIM devices, set the toggle per SIM, because the default SIM determines which network carries the flag.

For business lines, submit a written request to your PBX administrator specifying whether the block applies to all extensions or selected ones. Confirm the policy in writing, because the administrator's setting will override any handset toggle.

Red-flag warnings: Do not assume *67 blocks emergency calls; it does not, and dispatchers see your number. Do not rely on a phone toggle alone when calling from a business PBX; the system can override it. Do not expect blocking to defeat toll-free number identification or bank verification systems. Do not use blocking to conceal identity during harassment or fraud; carriers retain records and can disclose them under legal process. Do not assume international roaming preserves the flag; many visited networks strip it.

Limitations and what blocking cannot do

Suppression hides the display field, not the underlying call record. Your carrier retains call detail records that include the originating number, duration, and destination. Law enforcement can obtain these records with legal process, and carriers can disclose them under subpoena. The block is not anonymity; it is display privacy.

Recipients with caller ID block override subscriptions, common on business and emergency lines, see the number anyway. Call-filtering apps may identify you through call-pattern and reputation databases even when the number is masked. Voicemail and conference systems may log the number on the host side. And some networks in the path may ignore the flag entirely, especially during roaming or when a VoIP provider is configured to strip privacy headers.

The practical threshold is this: blocking works best for casual calls to ordinary phones on the same carrier ecosystem. It degrades with each network boundary crossed. If your goal is genuine anonymity, suppression alone cannot deliver it, and no consumer method available today fully substitutes for a dedicated privacy service with a disposable number.

This article is general educational information about call signaling and privacy features, not legal or safety advice. Caller ID suppression does not protect against lawful records requests, and it never applies to emergency calls. For legal questions about anonymity or harassment, consult a qualified attorney in your jurisdiction.