What Is Outbound Id Suppression? (VoIP Masking)
Outbound caller-ID suppression asks a phone provider not to show your number on an ordinary recipient’s caller-ID display. It is a privacy request, not number spoofing or guaranteed anonymity. In the United States, federal rules set key limits; your carrier, SIP trunk, and call destination also affect what is hidden and what remains available.
A phone-system upgrade can add privacy controls without changing your published business number or replacing your PBX. The important detail is to separate the number shown to a recipient from identity information used by carriers to route, bill, secure, or return a call. I plan suppression as a provider feature with defined limits, then test the actual call paths.
Planning: Define the Privacy Requirement and Provider Support
Outbound caller-ID suppression is a request to withhold caller-ID information from ordinary recipient display. Before enabling it, identify whether you need privacy for selected calls or all outbound calls, and confirm that your provider supports the option on the lines and routes you use.
Start with a simple call-path map. Record the phone service, PBX or softswitch, SIP trunk, user devices, and the countries or regions you call. A setting on a desk phone may not control a PBX, and a PBX setting may be overridden by the trunk provider.
Per-call or account-wide suppression?
Per-call suppression applies to a specific call, often through a provider-supported prefix such as *67 in the United States. Availability and dialing rules can vary by provider and route, so verify the feature before relying on it.
Account-wide or per-line privacy applies more broadly. It may suit a line that should usually withhold caller ID, but can affect callbacks and how recipients handle calls. Ask whether the setting can be changed by user, extension, trunk, or account.
| Need | Possible approach | What to confirm |
|---|---|---|
| Hide caller ID on selected calls | Provider-supported per-call code or softphone option | Whether the code works through your PBX and on each route |
| Hide caller ID on most calls | Account, line, or PBX privacy setting | Whether emergency and special destinations override it |
| Set privacy on a SIP system | Provider-approved SIP privacy request | Whether the trunk accepts and passes the request |
| Send a different number | Not suppression | Use only a number you are authorized to present; do not substitute a false identity |
I document the provider’s exact feature name, the affected extensions, and the destinations tested. That prevents a local phone setting from being mistaken for an end-to-end privacy guarantee.
Access and Exceptions: Check Emergency, Toll-Free, and SIP-Trunk Handling
Suppression changes what an ordinary recipient may see; it does not promise that identity disappears from the network. U.S. rules include exceptions for 911 and specified toll-free services. Carriers and emergency systems may still receive or retain information needed to route, bill, address abuse, or support emergency callbacks.
Under 47 CFR § 64.1601(b), carriers must provide a way to request caller-ID blocking on a per-call basis. Section 64.1601(c) sets limits on honoring blocking for calls to 911 and specified toll-free services. Check the current rule and your provider’s terms for the route you use; do not assume every special destination behaves alike.
What the recipient may see
Depending on the network and device, a recipient may see “Private,” “Anonymous,” “Unknown,” or no number. A business phone system can also reject or route anonymous calls differently. Display behavior is not proof that no network element has the number.
For SIP systems, RFC 3323 describes privacy mechanisms, including the Privacy: id request. Support depends on the provider and the trust relationship between systems. The header is a request handled under network policy, not a command that guarantees every downstream network will erase identity.
RFC 3325 defines P-Asserted-Identity, which can carry an asserted identity inside trusted SIP networks. It is distinct from the recipient-facing From identity. Authorized network elements may still use asserted identity even when caller-ID presentation is restricted.
Suppression is not spoofing
Suppression asks that your caller-ID information not be presented in the ordinary way. Spoofing means transmitting caller-ID information that misleads about the caller’s identity. Under 47 CFR § 64.1604, knowingly transmitting misleading or inaccurate caller-ID information with intent to defraud, cause harm, or wrongfully obtain anything of value is prohibited.
Do not enter a fabricated, unassigned, or unauthorized number to imitate suppression. Ask your provider how to send a valid business number, or how to withhold presentation through its approved privacy control.
Execution: Apply Provider-Approved Caller-ID Suppression
A safe setup begins with the provider, not with an invented SIP header or a random dial-plan change. Confirm the supported method, apply it at the correct layer, and preserve any required identity for emergency routing and network operations.
Configure in a controlled order
- Survey the system. Identify the carrier, PBX or softswitch, SIP trunk, extensions, and jurisdictions. Decide whether privacy is needed per call or across a line or account.
- Ask the provider. Confirm supported feature codes, account settings, SIP privacy behavior, and any route-specific limits. Ask whether the provider honors
Privacy: idand how it handlesP-Asserted-Identity. - Choose one control point. Use the provider-approved per-call method, such as
*67where supported, or enable an account-level setting. Avoid duplicate controls until you know which layer governs presentation. - Keep valid identity fields. Do not replace a caller-ID number with a false number. Follow the provider’s guidance for
From, asserted identity, and privacy headers. - Record the change. Note the date, affected lines, feature settings, and test calls. This gives you a baseline if a software or trunk update changes behavior.
For a SIP PBX, have an administrator review the outbound route and trunk policy. A privacy header may be stripped, rewritten, or ignored when a call crosses a trust boundary. The provider’s written behavior is more useful than assuming a header will pass unchanged.
Verification: Test Recipient Display and Network-Side Identity
Verification means checking both the display seen by recipients and the provider’s handling of the call. Run controlled tests across more than one receiving network, since downstream systems can present privacy differently. Keep test results with the configuration record.
Use a repeatable test plan
Place a call from each affected line to consenting test phones on different carriers or services. Record the dialed method, date and time, outgoing line, destination network, and display result. Also check whether the recipient’s call log records a number or only a private-call label.
Then review the provider’s call records or support portal. A number appearing in a provider record does not mean caller-ID suppression failed; network-side records can be needed for billing, routing, and abuse handling. If the provider offers a privacy status field, ask what it means.
Use a separate, provider-approved test procedure for emergency and toll-free destinations. Do not place test calls to 911. For emergency behavior, ask the carrier or system administrator how caller identity and callback routing are handled.
| Test | Record | What it tells you |
|---|---|---|
| Per-call code on a normal destination | Display label and route | Whether the code is accepted on that path |
| Account-level privacy call | Display label by extension | Whether the account setting reaches each line |
| Calls to different recipient networks | Display and recipient call log | Whether downstream presentation varies |
| Provider call record | Available identity fields | What the provider retains for operations |
| Special-destination policy check | Provider guidance; no unnecessary test call | How exceptions and emergency routing apply |
If a number appears on a recipient display, do not immediately add a false number to “fix” it. Check whether the PBX sent the privacy request, whether the trunk accepted it, and whether the destination network honored it. Escalate with timestamps and call examples.
Practical Scenarios: What a Good Result Looks Like
These are illustrative test cases, not claims about a specific carrier. They show how I would define success before changing a live phone system: specify the path, expected display, provider-side behavior, and exceptions.
A household line with occasional privacy needs
A homeowner wants to withhold caller ID for selected calls but keep the usual display for family and service calls. I would confirm the provider’s per-call method, test it from the actual handset, and verify a normal call immediately afterward. The key result is predictable display behavior, not erasure of the number from carrier records.
A small office using a SIP PBX
An office administrator enables a privacy option in the PBX, but test calls still show the main business number. The likely diagnostic path is to inspect the PBX route, trunk requirements, and provider policy together. The team should ask whether the provider expects a specific privacy header and whether an asserted identity remains present inside its trusted network.
A system that uses account-wide privacy
A line is set to withhold caller ID for routine outbound calls. Before rollout, the owner checks how callers can receive callbacks and whether anonymous calls are rejected by key recipients. The provider should also clarify how emergency calls and special destinations are treated. The setting is acceptable only if those tradeoffs fit the use case.
Conclusion: Treat Suppression as a Controlled Privacy Setting
Outbound ID suppression can reduce what an ordinary recipient sees, but it cannot promise anonymity across the phone network. In the U.S., follow the limits in 47 CFR §§ 64.1601 and 64.1604, and use the provider’s approved controls. Document the setup, test multiple call paths, and never substitute a false number for a privacy request.
FAQ: Outbound Caller-ID Suppression
What is outbound caller-ID suppression?
It is a request to withhold your caller-ID information from ordinary recipient display. Carriers and other authorized network systems may still have identity information.
Is caller-ID suppression the same as spoofing?
No. Suppression asks not to present caller ID. Spoofing transmits caller-ID information that misleads about identity. Federal law prohibits specified deceptive transmissions made with the intent described in 47 CFR § 64.1604.
Does *67 always hide my number?
No. *67 is a common U.S. per-call method, but support depends on the provider and call route. Test it on your actual line and ask your provider about exceptions.
Does suppression hide my number from my carrier?
No. The provider may retain or use identity information for billing, routing, security, or other network functions.
Does caller-ID blocking work for 911?
Do not rely on ordinary blocking for 911. Federal rules provide an exception, and emergency routing and callback needs can take priority. Do not place a test call to 911.
Can I use suppression for toll-free calls?
Treatment can differ for specified toll-free services. Check the provider’s current policy and the applicable rules before assuming the number will be withheld.
What does Privacy: id do in SIP?
It is a SIP privacy request described in RFC 3323. Whether it is accepted and how it is handled depends on the provider and the network trust relationship.
What is P-Asserted-Identity?
It is an identity field defined by RFC 3325 for use within trusted SIP networks. It differs from recipient-facing caller-ID presentation and may remain available to authorized network elements.
Why does a recipient still see my number?
The PBX or trunk may not have sent the privacy request, the provider may not support it on that route, or a downstream network may handle presentation differently. Check the call path with your provider.
How should I verify suppression safely?
Use consenting test phones on multiple networks, record display results, and review provider documentation or call records. Ask the provider about emergency and special-destination behavior rather than making unnecessary test calls.
(This article was written by one of our staff writers, Garrett Vance. Visit our Meet the Team page.)






