How To Call From A Restricted Number: Complete Protocol Guide

Masking outbound caller identity relies on Calling Line Identification Restriction (CLIR) protocols built directly into telecommunications networks and mobile operating systems. By prepending standardized vertical service codes like *67 or toggling native settings in iOS and Android, callers can override default Calling Line Identification (CLI) data to display as "Restricted," "Private," or "Blocked." This comprehensive technical guide details the precise steps needed to suppress outbound telephone numbers across mobile, landline, and Voice over IP (VoIP) channels while maintaining regulatory compliance.

Technical Prerequisites and Network Compatibility Requirements

Outbound Caller ID suppression operates at the interface between the originating user terminal and the serving telecommunications exchange. Modern voice networks use Signaling System No. 7 (SS7) or Session Initiation Protocol (SIP) signaling to transmit two distinct identity parameters: the Calling Line Identification (CLI), which is presented to the called party, and the Automatic Number Identification (ANI), which is utilized by billing systems and emergency services.

To restrict CLI successfully, your terminal equipment and carrier network must support standardized CLIR override protocols. While most consumer wireless and wireline subscriptions include per-call restriction at no additional charge, certain prepaid plans, enterprise PBX trunks, or regional carriers may restrict user-level CLI modification.

• Essential Hardware & Software:
  
  
  • Active smartphone running iOS 11.0+ or Android 8.0+ (for persistent operating system toggles).
  • Standard landline touch-tone telephone (for dual-tone multi-frequency/DTMF star-code execution).
  • SIP-compliant Voice over IP (VoIP) softphone or third-party virtual number application.
• Mandatory Network Standards & Knowledge:
  
  
  • Knowledge of local vertical service codes (*67 in North America, #31# for global GSM networks, 141 in the United Kingdom).
  • Carrier SIM card provisioned with active voice capabilities (VoLTE, VoNR, or standard 3G/2G PSTN).
  • Awareness of regulatory limits (e.g., US FCC rules permitting emergency services and toll-free lines to override CLI restriction).
• Performance Benchmarks:
  
  
  • Configuration Time: 10 to 30 seconds for menu toggles; instant for prefix codes.
  • Implementation Cost: $0.00 (standard feature supported across public telecommunication networks).

Step-by-Step Outbound Caller ID Masking Workflows

Step 1: Applying Temporary Network Prefixes (*67, #31#, 141)

Per-call masking is the most reliable method for suppressing your number on an individual call basis without modifying global device settings. When you dial a vertical service code before entering the destination phone number, the local telephone exchange intercepts the sequence and alters the SS7 "Address Presentation Restricted Indicator" flag to "Presentation Restricted" for that specific session call setup message.

1. Open the native dialer app on your mobile phone or pick up the receiver of your landline handset.
2. Key in the designated vertical service code corresponding to your geographic region or network type:
   
   
   • North America (US, Canada) & NANP Regions: Dial *67
   • Global GSM Networks (Default International Standard): Dial #31#
   • United Kingdom & Ireland: Dial 141
   • Australia: Dial 1831 (or 1832 for landlines)
3. Enter the full destination phone number, including the area code, immediately after the code without entering spaces, pauses, or hyphens. For example, in North America, dial *671234567890.
4. Press the Send or Call button. The destination device will receive the incoming call signaling packet stripped of personal CLI data, displaying "Restricted," "Private," or "Anonymous."

Pro-Tip: When traveling internationally or using a roaming SIM card, use the GSM standard #31# before the international phone number formatted with the plus (+) sign (e.g., #31#+1234567890). This ensures proper packet routing across international transit gateways.

Step 2: Configuring Hardware-Level Restrictions on iOS

Apple iOS provides a native setting that modifies the outgoing SIP headers or signaling requests generated by the device baseband processor, requesting the carrier to permanently restrict CLI on all outgoing calls.

1. Launch the Settings application on your iPhone.
2. Scroll down and tap Phone.
3. Locate and tap the Show My Caller ID submenu.
4. Toggle the Show My Caller ID switch to the Off position (gray background).
5. Exit the menu. Every outgoing call placed from the native Phone app will now automatically transmit a CLIR restriction request to your cellular operator.

Warning: Certain carrier bundle configurations (such as specific prepaid or MVNO profile settings) automatically lock this software toggle. If the "Show My Caller ID" toggle is grayed out or non-interactive, your network carrier requires manual service provisioning or reliance on prefix codes.

Step 3: Modifying Supplementary Service Settings on Android

Android handles Calling Line Identification through supplementary service menus linked directly to the SIM card application interface. Depending on your Android distribution (e.g., Samsung One UI, Stock Android, or Xiaomi MIUI), the exact menu depth may vary slightly.

1. Open the primary Phone dialer app.
2. Tap the More Options icon (three vertical dots) located in the upper-right corner of the screen and select Settings.
3. Scroll down and select Supplementary Services (on Samsung devices) or Calling Accounts > Advanced Settings (on Stock Android/Pixel devices).
4. Tap Show Caller ID or Outbound Caller ID.
5. Select Never or Hide Number from the pop-up options menu.
6. Confirm the selection. The SIM protocol will update its outgoing caller profile state with the network register.

Step 4: Managing Caller ID Suppression in VoIP and Virtual Number Applications

Voice over IP systems utilize SIP protocols where caller metadata is stored within specific SIP packet headers, primarily From, Contact, and P-Asserted-Identity (PAI). To hide your main line or virtual number when using VoIP applications like Google Voice, Skype, or specialized SIP clients:

1. Open the settings dashboard of your chosen VoIP client or virtual phone provider.
2. Navigate to the Calls, Outbound Calling, or Telephony Privacy section.
3. Enable options designated as Anonymous Caller ID, Hide Outbound Number, or Custom Outbound CLI.
4. If using a custom PBX or enterprise SIP trunk (such as Asterisk or FreePBX), update your dialplan configuration to strip the primary identity and inject privacy headers:
   
   
   • Set Privacy: id in the SIP header.
   • Modify the outbound header field to From: "Anonymous" .

Protocol Specifications and Masking Method Matrix

The selection of a masking method dictates system persistence, network behavior, and security handling across different calling destinations.

Telecommunication Network Failures and Remediation Protocols

Failure Scenario 1: Call Fails or Instantly Drops with Error Tone

• Root Cause: The call recipient's local network or device has enabled Anonymous Call Rejection (ACR). When the receiving exchange identifies the "Presentation Restricted" flag on an incoming SS7 call setup message, it automatically rejects the session with a SIP 480/603 error or an automated recording.
• Actionable Fix: Temporarily disable number masking by dialing the recipient without the prefix code. Alternatively, send a preliminary text message (if using a virtual number) asking the recipient to temporarily disable ACR on their line.

Failure Scenario 2: Real Phone Number Displayed on Toll-Free (800/888/877) Dialing

• Root Cause: Toll-free numbers operate on a reverse-charge mechanism governed by Automatic Number Identification (ANI) rather than standard Caller ID (CLI). ANI is a billing protocol managed at the carrier trunk layer that cannot be masked using consumer CLIR tools like *67 or iOS toggles.
• Actionable Fix: If absolute privacy is required when contacting toll-free destinations, avoid placing calls through the PSTN altogether. Place the call using a secondary VoIP service, a burner application, or a web-based calling service configured with a disposable virtual phone number.

Failure Scenario 3: "Show My Caller ID" Toggle Greyed Out on Smartphone

• Root Cause: The Subscriber Identity Module (SIM) profile pushed by your Mobile Network Operator (MNO) or Mobile Virtual Network Operator (MVNO) has explicitly disabled local handset modification of the CLIR parameter.
• Actionable Fix: Fall back to the manual vertical service code method (*67 or #31#) before dialing. If manual codes are also rejected, contact your carrier's technical support department to request "Outbound Line Identification Restriction" provisioning directly on your cellular account line.

Failure Scenario 4: Wi-Fi Calling Bypasses Dialed Vertical Service Codes

• Root Cause: Voice over Wi-Fi (VoWiFi) encapsulates voice traffic into IPsec tunnels directly to the operator's ePDG (Evolved Packet Data Gateway). Certain device firmware implementations fail to translate legacy DTMF star codes like *67 into the corresponding SIP URI parameters when routing calls over Wi-Fi networks.
• Actionable Fix: Disconnect from Wi-Fi to force your smartphone onto native cellular infrastructure (5G/LTE) before dialing the code, or configure outbound privacy globally through the Android/iOS settings menu instead of relying on dialer prefixes.

Frequently Asked Questions

Can a restricted call be unmasked or traced by the receiver?

Standard call recipients using consumer telephone equipment cannot unmask a properly restricted CLI call. However, law enforcement agencies executing valid legal warrants, emergency services (911/999/112 gateways), and operators of toll-free 800-numbers receive raw ANI metadata, which completely bypasses standard Caller ID masking.

Does dialing *67 work for SMS and MMS text messages?

No. Vertical service codes like *67 are strictly designed for circuit-switched or packet-switched voice sessions. Prepending *67 to a text message will cause the SMS routing process to fail, generating an "Invalid Destination Address" error. To send anonymous text messages, you must use a dedicated VoIP or virtual number application.

Why does my phone display "Unknown" instead of "Restricted"?

The distinction between "Unknown" and "Restricted" depends on how the receiving carrier interprets the incoming SS7/SIP metadata. "Restricted" or "Private" means the caller intentionally activated CLIR to suppress their information. "Unknown" indicates that the originating network failed to pass identification data altogether due to technical routing errors or legacy network interconnects.

How do emergency services (911) see restricted numbers?

Emergency services rely on specialized public safety answering point (PSAP) trunks that process Automatic Number Identification (ANI) and Enhanced 911 (E911) location databases. Telecommunications laws mandate that CLIR privacy flags must be ignored during emergency calls to ensure operator dispatchers can identify and locate callers in distress.

Elevate Your Digital Privacy Infrastructure

Maintaining personal privacy over voice communications requires selecting the right network mechanisms for your specific hardware and carrier framework. By combining hardware toggles, vertical service codes, and dedicated virtual number services, you can effectively manage your outbound caller identity across all calling channels.