A private number code allows telephone users and enterprise networks to suppress their outbound identity before establishing a voice session. While everyday mobile users rely on short prefix strings to preserve personal privacy, modern organisations require a deeper understanding of how these mechanisms interact with carrier networks, session border controllers, and automated spam filtering. This guide details how identity restriction operates across traditional telephony and modern voice platforms, helping IT leaders maintain security and high call-answer rates.
Key takeaways
- Dialling prefixes suppress public presentation via Calling Line Identification Restriction (CLIR) but do not hide identity from emergency services or upstream carriers.
- Global standards vary by transmission type, using GSM feature codes like #31# or North American Vertical Service Codes like *67.
- In enterprise VoIP environments, identity presentation is negotiated through SIP headers such as P-Asserted-Identity and Remote-Party-ID.
- Ad-hoc call suppression damages operational performance by triggering automated carrier spam blocks and drastically reducing answer rates.
- Modern PBX platforms replace blanket privacy codes with structured outbound caller ID masking tied to verifiable corporate direct dial numbers.
What Is a Private Number Code and How Does It Work?
A private number code is an operational prefix dialled ahead of a telephone number to withhold the caller’s transmission identity from the receiving handset. Historically termed a Vertical Service Code (VSC) in fixed networks and a supplementary service code within mobile networks, this sequence instructs the local telephone exchange to adjust the presentation flag of the voice circuit. When applied, the carrier alters the Calling Line Identification Presentation (CLIP) status to Calling Line Identification Restriction (CLIR).
Telephony routing splits caller data into two distinct components: the originating line identity and the display line identity. The network switching centre always retains the billing identification number to trace network usage, execute toll billing, and facilitate lawful interception. However, entering a private number code instructs the originating switch to alter the presentation indicator in the signalling payload. When the call passes through intermediate transit networks, downstream gateways read this restriction flag and replace the telephone number with a visual label such as “Private Number”, “Withheld”, or “Anonymous”.
Organisations deploying private number code controls across modern SIP infrastructure must recognise that identity suppression is merely a display preference. Upstream telecommunications providers always preserve session origination data to satisfy regulatory and billing requirements.
Global Code of Private Number Formats by Region
Different geographic regions and transmission standards govern how feature codes interact with public switched telephone networks (PSTN). Entering the correct code of private number syntax depends entirely on whether the endpoint communicates over GSM wireless protocols, North American signalling standards, or dedicated regional switches.
| Dialling Prefix | Primary Region / Standard | Applicable Networks | Signalling Mechanism |
|---|---|---|---|
| #31# | International / GSM Standard | Mobile networks worldwide | GSM Supplementary Service string (3GPP TS 22.081) |
| *67 | North America (NANP) | Fixed landline and North American mobile | North American Vertical Service Code (Telcordia) |
| 141 | United Kingdom and Republic of Ireland | BT, Virgin Media, UK mobile operators | Local exchange routing prefix (SIN 227) |
| 1831 | Australia | Telstra, Optus, domestic landline | ACMA regulatory carrier prefix |
| *31* | International (Selective) | Alternative European fixed/mobile | ETSI Supplementary Service control |
GSM mobile architectures utilise the #31# string natively, which is recognised globally by almost all cellular providers operating under 3GPP parameters. Conversely, regions adhering to the North American Numbering Plan (NANP) utilise *67 to toggle presentation status on landlines, though mobile carriers in the United States and Canada also interpret this code within their switching centres.
Step-by-Step: How to Dial Private Number Prefixes Across Devices
End users can apply number withholding manually for a single call or apply system-wide settings across their device operating systems. Managing these methods prevents internal staff from accidentally exposing personal or departmental direct inward dial (DID) lines.
Manual Prefix Dialling
To dial private number strings manually before a call, the user prefixes the destination number directly into the dialler:
- Open the native phone dialler on the mobile handset or desktop softphone.
- Enter the regional suppression code (for example, #31# for international GSM or *67 for North American carriers).
- Input the recipient’s full telephone number, including the country and area codes if calling internationally.
- Press call. The resulting string appears to the network as a single execution command (for example, #31#+442079460991).
Native Handset Configuration
Rather than entering a prefix for every transmission, users seeking how to hide caller id permanently can adjust the supplementary services menu on their handsets. This setting instructs the SIM card to request CLIR for every outgoing voice transmission by default.
- Apple iOS: Navigate to Settings > Phone > Show My Caller ID, then toggle the switch to off. If this option is greyed out, the network operator has restricted manual user overrides at the SIM profile level.
- Google Android: Open the Phone app > tap the three dots (menu) > Settings > Supplementary Services (or Calling Accounts) > Caller ID > select Hide Number.
Desktop Softphones and Unified Communications
When operating professional softphone applications, prefix commands often fail if the underlying PBX interprets characters like # or * as feature codes for internal transfers or voicemail access. Softphone users should utilise software-based privacy flags located within their client settings, or rely on PBX routing policies configured by system administrators.
Under the Hood: SIP Signaling, PAI, and SS7 Presentation Flags
In legacy SS7 (Signalling System No. 7) networks, an Initial Address Message (IAM) carries the Calling Party Number parameter. This field includes a two-bit value known as the Address Presentation Restricted Indicator (APRI). When set to “presentation restricted”, the terminating exchange suppresses the digit string from the callee’s display terminal while passing the data uninterrupted across network transit nodes.
Modern corporate telephony relies on Session Initiation Protocol (SIP). In an enterprise phone service architecture, withholding identity requires manipulation of specific RFC-compliant SIP headers managed by the PBX and carrier Session Border Controllers (SBCs):
- From Header: The public display field. When anonymity is requested, the PBX rewrites this header to sip:anonymous@anonymous.invalid, stripping visible names and extensions.
- P-Asserted-Identity (PAI): Defined under IETF RFC 3325, this trusted header carries the true, authenticated enterprise billing number. It travels securely between the corporate PBX and the SIP trunk provider.
- Remote-Party-ID (RPID): An earlier operational standard that performs an identical function to PAI, carrying internal extension data and privacy markers across older softswitches.
- Privacy Header: This header explicitly defines the requested restriction level (for example, Privacy: id or Privacy: full), directing the downstream carrier gateway to strip the authenticated identity before handing the invite off to the terminating carrier.
If an enterprise SIP trunk submits a call where the From header is stripped but the upstream carrier requires cryptographic identity assertion, misconfigured SBCs can drop the packet entirely. Enterprise networks managed by Call Experts maintain transparent PAI structures to ensure carrier compliance while shielding internal endpoints.
The Operational Risks of Using a GSM Private Call Code in Business
Deploying an ad-hoc gsm private call code across commercial teams introduces significant operational friction. While individual staff members may wish to obscure their direct lines, blanket anonymity harms external communication workflows and degrades corporate reputation.
Unidentified business communications encounter severe delivery barriers. Enterprise outreach conducted without clear caller presentation results in lower pick-up rates and immediate automated carrier filtering.
First, commercial answer rates collapse when displaying withheld IDs. Modern consumers routinely reject unidentified calls, and enterprise reception desks frequently configure automatic rejection rules for numbers with active CLIR flags. Research across telecommunications sectors confirms that calls displaying anonymous identities face pick-up rates far lower than those presenting verified local numbers.
Second, global regulatory bodies enforce aggressive anti-spoofing and anti-spam frameworks, most notably the STIR/SHAKEN framework governed by the International Telecommunication Union and regional telecom regulators. Under STIR/SHAKEN, originating service providers assign an attestation score (A, B, or C) based on their verification of the caller’s identity:
- Full Attestation (A): The provider verifies that the caller has a direct, certified right to use the presented telephone number.
- Partial Attestation (B): The provider verifies the call origin but cannot verify that the caller owns the specific display number.
- Gateway Attestation (C): The provider simply passes traffic from an unauthenticated international or third-party gateway.
Applying an unmanaged private code causes analytics algorithms on downstream mobile networks to flag the session as potential fraud. Handsets running iOS or Android increasingly route calls lacking high attestation directly to voicemail or display automated “Spam Likely” warnings to the recipient.
Implementing Outbound Caller ID Masking in Enterprise PBX Systems
To eliminate the operational risks of anonymous calls while protecting internal staff from unwanted inbound callbacks, organisations deploy managed outbound caller id masking. Rather than suppressing digits entirely, this method substitutes personal desk extensions or mobile lines with an authorised corporate presentation number.
Configuring 3CX Business Communications
In modern systems like 3CX business communications, identity presentation is managed centrally through outbound rules and trunk parameters:
- Access the 3CX Management Console and select SIP Trunks.
- Navigate to the Outbound Parameters tab to verify that the P-Asserted-Identity field passes the main trunk billing number.
- Select the targeted internal user or department via Users > General.
- Locate the Outbound Caller ID field and enter the primary departmental direct dial (for example, the central support switchboard number).
- Apply outbound rules that route domestic and international calls through this trunk, ensuring all staff calls display a verified, reachable corporate identity.
Configuring Yeastar P-Series Phone Systems
Similarly, deployment within Yeastar phone systems follows a structured routing process:
- Log in to the Yeastar PBX web interface and navigate to Extension and Trunk > Trunks.
- Edit the ITSP SIP Trunk and confirm that DOD (Direct Outward Dialling) is enabled.
- Navigate to the DOD tab, create a new entry, and map specific internal extension groups (such as outbound billing or patient outreach) to a shared corporate service number.
- In the trunk’s advanced signalling options, confirm that Send Remote Party ID or Send P-Asserted-Identity is checked.
This configuration maintains regulatory traceability between your PBX and the carrier, presents a familiar number on the customer’s display, and ensures incoming return calls route cleanly back to your automated switchboard or contact centre queue.
Establishing a Reliable Outbound Telephony Strategy
Relying on manual dialling prefixes or handset-level privacy toggles is an unscalable approach for expanding businesses. While a private number code remains useful for isolated, non-commercial calls, enterprise operations require transparent, policy-driven caller identification. Proper trunk configuration ensures that calls pass through carrier networks with full cryptographic verification, reaching customers reliably without triggering automated spam filters.
Modernising your voice infrastructure requires balancing end-user privacy, operational compliance, and call deliverability. Whether designing secure multi-site routing, integrating SIP trunks, or deploying resilient softphone environments, Call Experts delivers the structured engineering required to keep your business communications clear and compliant. To review your outbound calling architecture or upgrade your business telephony, contact our telephony specialists today.
Frequently asked questions
Does dialling a private number code hide my identity from everyone?
No. Dialling a suppression prefix only prevents your phone number from appearing on the recipient’s personal display. Upstream telecommunications carriers, billing engines, law enforcement agencies, and emergency service dispatch centres always receive and record your originating number through carrier-grade signalling parameters like P-Asserted-Identity.
Why do mobile carriers flag private number calls as spam?
Modern telecommunications providers use automated reputation engines and STIR/SHAKEN frameworks to combat fraud. Calls that suppress outbound numbers or carry incomplete identity verification cannot achieve full cryptographic attestation. As a result, carrier algorithms frequently mark these sessions as suspicious or route them directly to voicemail.
What is the difference between hiding caller ID and caller ID masking?
Hiding your caller ID strips your identity completely, displaying labels such as Anonymous or Withheld to the recipient. Caller ID masking replaces an internal line or personal mobile number with a verified corporate number, maintaining professional presentation, caller trust, and the ability for the recipient to call back.
Can an enterprise PBX system hide numbers for specific departments only?
Yes. Platforms such as 3CX and Yeastar allow administrators to define outbound rules per extension or department. For instance, customer support can display the central helpline, executive lines can display a switchboard number, and internal lines can maintain default trunk rules without using manual dialling prefixes.
