How To Call On Restricted: The Complete Technical Guide To Outbound Caller ID Masking
Placing a restricted call requires masking your outbound Caller ID using carrier-specific vertical service codes, device-level operating system configurations, or permanent line restrictions. To immediately mask your number on a single call within North America, dial *67 before the ten-digit telephone number, which triggers the Calling Line Identification Restriction (CLIR) protocol on both GSM and CDMA networks.
Pre-Dialing Configuration and Telecom Network Standards
Before initiating an outbound restricted call, you must understand how voice networks handle caller identity metadata. The Public Switched Telephone Network (PSTN) and modern Voice over Internet Protocol (VoIP) networks transmit two distinct sets of identity data: Calling Line Identification (CLI) and Automatic Number Identification (ANI). Caller ID masking tools modify the CLI data presented to the destination handset, but they do not alter the underlying ANI data, which remains visible to emergency services and toll-free service operators.
To successfully execute Caller ID masking, your equipment and network connection must meet the following baseline requirements:
- Essential Equipment and Hardware: An active analog landline, a digital VoIP terminal, or a mobile handset (iOS or Android) connected to a cellular network (GSM, LTE, or 5G).
- Prerequisite Network Knowledge: Understanding whether your cellular carrier utilizes GSM (such as T-Mobile and international networks) or legacy CDMA infrastructures (such as Verizon), as the protocol commands for temporary and permanent suppression can vary slightly between these architectures.
- Carrier Provisioning Permissions: Your cellular subscriber identity module (SIM) or landline billing plan must have Calling Line Identification Presentation (CLIP) and Calling Line Identification Restriction (CLIR) control enabled by default.
- Estimated Duration & Cost Benchmarks: Setup time is instantaneous (under 5 seconds for prefix dialing). Operating system configurations require under 2 minutes. Standard outbound caller masking is a free feature across major global telecom providers, though some enterprise PBX or SIP trunk operators may levy structural configurations fees.
Step-by-Step Protocol to Force Outbound Restricted Status
The following methods represent the authoritative technical pathways to suppress outbound caller identification across major mobile operating systems, analog landlines, and global carrier networks.
Step 1: Implementing Single-Call Masking via Vertical Service Codes (VSC)
Vertical Service Codes are special dial strings beginning with an asterisk or hash symbol that command the local telephone exchange or Mobile Switching Center (MSC) to alter call processing parameters.
- Retrieve your physical dialer interface (on mobile devices, launch the native Phone application; on landlines, lift the receiver and wait for a continuous dial tone).
- Input the standardized vertical service code corresponding to your geographical region and network type. In the United States, Canada, and parts of the Caribbean (the North American Numbering Plan area), input the prefix *67.
- Directly enter the destination telephone number, including the area code (e.g., *67-555-0199). Do not press the call key between the prefix and the phone number.
- Initiate the call by pressing the dial, call, or send key.
- The downstream carrier's signaling gateway will receive the call setup request with a signaling flag instructing the terminating switch to restrict CLI presentation. The recipient's display will render as "Restricted," "Private Number," "Blocked," or "Unknown."
Pro-Tip: If you are operating on a global GSM network or utilizing an international roaming profile, the standard code is #31#. Dialing this prefix before the complete country code and subscriber number forces immediate outbound restriction.
Step 2: Configuring Device-Level Caller ID Restrictions on iOS
If you need to make consecutive restricted calls without manually entering a prefix for every dial string, you can configure the iOS operating system to globally suppress outbound Caller ID at the SIP/VoIP signaling layer.
- Unlock your iPhone and launch the primary Settings application.
- Scroll down the system settings menu and tap on Phone.
- Within the Phone configuration panel, locate the sub-menu labeled Show My Caller ID and select it.
- Wait for the network query to complete. The system will query your carrier's Home Location Register (HLR) to fetch your current restriction status.
- Toggle the green switch next to Show My Caller ID to the Off position (the toggle will turn grey).
- Exit the Settings application. All subsequent voice calls placed through the native dialer will transmit a restricted header until this setting is manually restored.
Warning: Device-level toggles are subject to carrier override. If your network operator does not support user-controlled CLIR via the SIM card configuration profile, the "Show My Caller ID" menu option may appear greyed out, or the toggle will automatically snap back to the enabled state.
Step 3: Configuring Device-Level Caller ID Restrictions on Android
Android handles CLIR settings through its Supplementary Services engine. The exact menu paths can vary slightly depending on the device manufacturer's skin (such as Samsung One UI or Google Pixel Pixel UI), but the underlying signaling logic remains identical.
- Open the native Phone or dialer application on your Android device.
- Tap the More Options icon, represented by three vertical dots in the upper-right corner of the interface.
- Select Settings from the drop-down contextual menu to access Call Settings.
- Scroll down and tap on Supplementary Services (on some devices, this is located under Calling Accounts or More Settings).
- Tap on Show Caller ID or Show My Caller ID.
- A pop-up dialog box will present three distinct options: "Network default," "Never" (or "Hide number"), and "Always" (or "Show number").
- Select Never or Hide number to enforce persistent, global Caller ID suppression.
- Verify the setting updates successfully by watching for the loading wheel to disappear, confirming the command has registered with your network operator.
Step 4: Requesting Permanent Carrier-Level Line Blocking
For users who require absolute assurance that their outbound phone number will never display, mobile network operators can apply a permanent CLIR block directly to the billing account level.
- Contact your carrier's customer support or technical operations department (e.g., 611 on mobile networks).
- Request the provisioning of a "Permanent Outbound Caller ID Restriction" or "Line Blocking" feature on your specific line directory number.
- Once provisioned, every call placed from your SIM card will automatically transmit the restricted signal to all destination terminals, regardless of the phone hardware used.
- If you need to selectively reveal your caller identity for a specific call while permanent blocking is active, prefix the dialed number with *82 (in North America) or *31# (on global GSM networks). For example, dialing *82-555-0199 will temporarily unmask your identity to that recipient only.
How To Block Unwanted Calls | Consumer Advice
Global Telephony Standards and Caller ID Restriction Codes
The table below outlines the vertical service codes and technical protocols utilized across various geographical domains and network topologies to execute Caller ID masking and override procedures.
| Geographic Region / Network | Standard Protocol | Suppression Code (CLIR) | Presentation Code (CLIP Override) | Implementation Layer |
|---|---|---|---|---|
| North America (NANP) | SS7 / PSTN | *67 | *82 | Local Exchange / MSC |
| United Kingdom | BT / GSM | 141 | *31# | Core Switching Center |
| Global GSM Networks | ETSI / 3GPP | #31# | *31# | SIM Application / HLR |
| Australia | Telstra / Optus | 1831 | 1832 | Network Routing Tables |
| Japan | NTT / KDDI | 184 | 186 | Signaling Gateway |
| Enterprise VoIP (SIP) | RFC 3323 / RFC 3325 | Anonymous | Asserted-Identity | Session Border Controller |
Outbound Privacy Anomalies and Technical Resolutions
When configuring your phone to hide its caller identity, you may encounter system-level failures, call rejections, or unexpected exposure of your personal data. Below are the most common real-world failure scenarios and their technical resolutions.
Scenario 1: Outbound Caller ID remains visible when calling Toll-Free Numbers
- Root Cause: Toll-free numbers (specifically 800, 888, 877, 866, and 855 area codes) are paid for by the recipient. To prevent billing fraud, telecom routers bypass the user-facing Caller ID (CLI) field and query the Automatic Number Identification (ANI) database directly. The ANI record cannot be suppressed by consumer-facing vertical service codes or mobile OS toggles.
- Actionable Fix: To call a toll-free number anonymously, route the call through an intermediate digital service. Use a secure over-the-top (OTT) VoIP application, a secondary burn number, or a proxy bridging service that initiates the trunk call using an enterprise-registered ANI that does not link back to your personal subscription.
Scenario 2: The "Show My Caller ID" toggle is greyed out or completely missing
- Root Cause: This occurs when the carrier profile loaded onto your SIM card disables user access to supplementary network services. This is highly common with prepaid cellular plans (MVNOs) and corporate-managed enterprise mobile device management (MDM) profiles.
- Actionable Fix: Force the restriction on the network side by prefixing every manual dial string with *67 (or #31#). Alternatively, contact your system administrator or carrier help desk to request manual activation of the CLIR feature on your account provisioning file.
Scenario 3: Restricted outbound calls are instantly terminated or directed to a busy tone
- Root Cause: The destination party has activated a network feature known as Anonymous Call Rejection (ACR). When ACR is active, the terminating central office or carrier gateway automatically rejects any incoming call that carries an "Anonymous," "Restricted," or "Private" presentation indicator, preventing the recipient's phone from ringing.
- Actionable Fix: You must temporarily disclose your Caller ID to bypass this filter. Hang up, append *82 to the destination number (e.g., *82-555-0199), and place the call. This temporarily lifts the restriction for that single outbound connection, allowing the call to route successfully.
Scenario 4: Outbound masking fails during international roaming
- Root Cause: When routing voice traffic across international borders, local routing transit nodes use Signaling System No. 7 (SS7) or SIP trunking interconnections that may drop caller privacy headers due to divergent regional protocol configurations.
- Actionable Fix: Avoid placing calls via the cellular voice network. Use data-centric, end-to-end encrypted communication applications like Signal, WhatsApp, or proprietary VoIP clients that use web-based data packets to route audio, completely bypassing traditional carrier voice signaling protocols.
Frequently Asked Questions
Is it technically possible for a standard recipient to trace or unmask a restricted call?
No, a standard consumer recipient using a standard phone line cannot trace or unmask a restricted call. However, toll-free operators, emergency dispatch centers (such as 911/999/112), utility companies, and law enforcement agencies have specialized network access that queries the underlying Automatic Number Identification (ANI) metadata, bypassing your outbound restriction configuration entirely.
Will prefixing a text message with *67 mask my phone number?
No, vertical service codes like *67 and #31# are exclusively designed for voice signaling networks. Short Message Service (SMS) and Multimedia Message Service (MMS) rely on a completely different signaling protocol architecture where your 10-digit mobile directory number is hard-coded into the routing packet header; sending a text with these prefixes will simply cause the delivery to fail or display the code as plain text.
Is there a billing charge associated with making a restricted call?
For the vast majority of modern mobile carriers and residential landline providers, applying a vertical service code prefix or toggling device settings to hide your caller identity is completely free. However, a small number of regional legacy landline providers or enterprise PBX system operators may charge a minor monthly fee for permanent line blocking services.
Why does my masked call display as "Unknown" to some people and "Private" to others?
The specific nomenclature displayed on the recipient's screen is determined entirely by how their receiving carrier translates the Calling Line Identification Presentation (CLIP) privacy flags. When the signaling gateway receives a packet with the presentation-allowed flag set to "false," the recipient's local carrier translates this metadata based on their internal database terminology, outputting "Private," "Restricted," "Withheld," or "Unknown."
Can I block my number on a Wi-Fi call?
Yes, but the effectiveness depends on the operating system settings. If you use the native OS dialer with Wi-Fi calling enabled, turning off "Show My Caller ID" in your phone settings will still instruct the SIP gateway to strip your identifier. However, manual prefixes like *67 can occasionally fail on certain Wi-Fi calling networks if the carrier's gateway does not properly translate voice band tones; for absolute privacy, it is safer to temporarily disable Wi-Fi calling and use the standard cellular network when dialing vertical service codes.
Secure Your Digital Communications Strategy
Protecting your mobile identity is only the first step in maintaining complete operational security. To further shield your personal communication channels from unauthorized tracking, intercept, and digital intrusion, consult our comprehensive telecom security documentation to implement advanced data encryption standards today.