Outbound Caller ID Not Showing: SIP Fixes
Caller ID missing, anonymous or wrong on outbound SIP calls? Check From vs P-Asserted-Identity, Privacy headers, number format and what the carrier accepts.
Réponse rapide
Outbound caller ID goes missing for five usual reasons: the carrier reads a different header than the one you send (From, P-Asserted-Identity or P-Preferred-Identity), a Privacy header hides the number, the number is in the wrong format, the number is not provisioned on that trunk, or the carrier overrides it. Capture the INVITE, check which header holds the number, then confirm format and provisioning with the carrier.
An agent dials a customer and the phone shows "Unknown", "Private" or the carrier's main number instead of the number you meant to present. The call itself works, so nothing looks broken, and it is easy to blame the handset or the receiving network. Most of the time the cause is in your own INVITE or in what the carrier does with it.
This guide explains which SIP header carries the number, why a carrier may ignore or overwrite it, how Privacy headers produce "anonymous" calls, and how to test with a trace. It is vendor-neutral and applies to any PBX or dialer. For reputation and spam labelling, which is a different problem, see réputation de l'identification de l'appelant pour les équipes sortantes.
Which header carries the number
On a SIP call, three headers can carry the calling identity. They are not interchangeable.
| Header | Who sets it | Ce que cela signifie |
|---|---|---|
| From | The sender (your PBX or dialer) | The identity the sender claims. Always present in a SIP request. |
| P-Preferred-Identity | The sender, to a trusted proxy | A hint about which of the sender's valid identities the network should assert (RFC 3325) |
| P-Asserted-Identity | A trusted network element | The identity the network asserts after authenticating the sender (RFC 3325) |
RFC 3325 defines P-Asserted-Identity and P-Preferred-Identity for use inside a trust domain, a set of nodes that trust each other to handle identity correctly. A proxy in the trust domain that receives a request from a node it does not trust, and wants to add a P-Asserted-Identity header, must first authenticate the sender (RFC 3325, section 5). If the request contains a P-Preferred-Identity, the proxy may use it as a hint for which identity to assert, and must remove the user-provided P-Preferred-Identity before forwarding (RFC 3325, section 6).
The practical consequence is that "which header does the carrier read" is a policy question with a different answer per carrier. Some read From, some read P-Asserted-Identity, and some read a Remote-Party-ID header, which RFC 3325 does not define. The carrier's setup sheet should say which.
Trust domains: why a carrier may ignore or overwrite your number
When you send a call into a carrier, you are normally outside their trust domain. That has two effects.
- Your P-Asserted-Identity is not trusted. RFC 3325 says that when a proxy receives a P-Asserted-Identity from an element it does not trust, it must replace that identity or remove the header (section 5). It also says a user agent only sends P-Preferred-Identity to proxies in a trust domain, and must not populate it in a message that is not sent directly to a proxy it trusts (section 6). So a carrier that does not regard you as trusted can drop an asserted identity you send, or replace it with the identity it has on file for your account.
- The hint may match nothing. If your P-Preferred-Identity does not correspond to any valid identity known for your account, RFC 3325 says the proxy can add a P-Asserted-Identity of its own construction, or can reject the request, for example with a 403 Forbidden (section 6). So a 403 on an outbound INVITE can mean "this number is not yours on this trunk".
This is why the same number can display correctly through one carrier and not another. It is usually the carrier's trust and provisioning rules at work rather than a fault in your dialer.
Privacy headers and calls that show as anonymous
RFC 3323 defines the Privacy header. The values it defines are header, session, user, none and critical, and further values can be added by other specifications. Two matter for caller ID:
- Privacy: id is defined in RFC 3325. If it is present, proxies must remove the P-Asserted-Identity headers before forwarding to elements that are not trusted. If the Privacy value is none, the proxy must not remove them (RFC 3325, section 7).
- An anonymous From. RFC 3323 gives
"Anonymous" <sip:anonymous@anonymous.invalid>as the recommended From for a user agent seeking anonymity, and says user agents should include a Privacy header when they need the network to provide privacy.
A call that shows as anonymous, withheld or private is therefore usually one of two things. Either your system sent a Privacy header or an anonymous From because a setting told it to, or an upstream element added one. Check the INVITE for any Privacy header and for a From user part of "anonymous". If your own platform has a privacy or presentation setting, confirm it is set to show the number, not hide it.
Number format in the user part
A correct number in the wrong shape can look invalid to a carrier. The global form of a telephone number begins with a plus sign followed by the country code (RFC 3966 says globally unique numbers are identified by the leading "+" and are composed of the country code and national number, section 5.1.4; the numbering plan itself is ITU-T E.164, with the 02/26 edition listed as in force). Visual separators such as hyphens, dots and brackets only aid readability and are not used for comparison or placing a call (RFC 3966, section 5.1.1).
Carriers differ on what they want in the From user part. Here are the shapes you will meet, using a made-up number with country code CC and subscriber digits NNNNNNNN:
| Shape | Example (illustrative) | Typical issue |
|---|---|---|
| E.164 with plus | +CCNNNNNNNN | Rejected if the carrier expects digits only |
| Digits with country code, no plus | CCNNNNNNNN | Read as a national number if the carrier expects a plus |
| National format | 0NNNNNNNN | Ambiguous across borders; often not dialable from abroad |
| Formatted with spaces or brackets | (0) NNNN NNNN | Fails strict matching against provisioned numbers |
Do not change the format on a guess. Ask the carrier which form they accept in From and in any identity header, and make a test call after each change. If you also manage contact lists, the same format discipline applies; see E.164 format for dialer lists.
The number must be provisioned on that trunk
Many carriers check the presented number against the numbers assigned to your account. A number you own elsewhere, a number from another carrier, or a mobile number you have no right to present, may be rejected, replaced with a default, or withheld. Check three things:
- The exact number is listed on the carrier account for this trunk, not just on the account in general.
- Any verification the carrier requires for presenting a number you do not hold from them has been completed.
- The trunk has a default caller ID configured as a fallback, so a rejected number does not become "unknown".
If calls fail outright with a caller ID error, see SIP error codes on outbound calls for how to read the response.
Regulators want a valid, dialable CLI
Caller ID is also a legal topic. As a worked example, the UK regulator Ofcom publishes guidance on calling line identification. It states that where CLI data is provided, it must include a valid, dialable telephone number which uniquely identifies the caller. Ofcom's page links two versions of the guidance: one applicable until 15 July 2027 (its file is labelled as the 2024 update), and a version published on 15 July 2026 that applies from 15 July 2027 (Ofcom, checked November 7, 2026).
The lesson is general even though the rule is national: a made-up, non-dialable or someone else's number is a compliance risk as well as a display problem. Rules differ by country, so check the regulator for each market you call. STIR/SHAKEN, where carriers use it, is a separate layer on top of the caller ID itself: the originating service provider signs the call and states a level of attestation (full, partial or gateway) for the calling identity (RFC 8588). Our STIR/SHAKEN explainer for outbound teams covers it.
A step-by-step test with a SIP trace
- Place a test call from the platform to a phone you control, presenting a number you are sure is provisioned. Note what the handset shows.
- Capture the outbound INVITE on your side. Find the From header, any P-Asserted-Identity, P-Preferred-Identity or Remote-Party-ID, and any Privacy header.
- Check the number in each header: format, plus sign, no spaces, the exact digits you intended.
- Check for privacy. A Privacy header or an anonymous From explains an anonymous display on its own.
- Change one thing at a time. Switch the header the platform populates, or the number format, then call again.
- Test a second number and a second destination network. If one number works and another does not, it is provisioning. If both fail to one destination only, it is downstream handling.
- Escalate with evidence. Send the carrier the INVITE, the time of the call and the number you expected to show.
An illustrative INVITE excerpt shows what you are looking for:
INVITE sip:+CCDESTINATION@carrier.example.com SIP/2.0
From: <sip:+CCNNNNNNNN@carrier.example.com>;tag=abc
P-Asserted-Identity: <sip:+CCNNNNNNNN@carrier.example.com>
Privacy: none Comment DialerBee s'intègre
On DialerBee's bring-your-own-carrier gateway form, the Caller ID tab has a Type d'identification de l'appelant that defaults to Auto-detect, with Remote-Party-ID, P-Asserted-Identity and From Header as the other choices. Mode de confidentialité defaults to "None - Caller ID visible", with a restricted mode and a full anonymous mode, and Remplacement de l'identification de l'appelant par défaut sets a fallback number for the gateway. Each gateway also has a Numéros DID et identification de l'appelant section where numbers are added with a jurisdiction and a Verify action.
Your carrier tells you which header they read, so set the type to match, and keep Privacy Mode on the visible setting unless you intend to withhold the number. The steps are in Comment connecter votre trunk SIP (configuration BYOC). For pools of numbers and local presence, see How to Configure Caller ID Groups et le renseignements sur l'identification de l'appelant page. The basics are in Qu'est-ce que l'identification de l'appelant ?.
Foire aux questions
Why does my outbound caller ID show as anonymous or unknown?
Either a Privacy header asked for the identity to be hidden, or the carrier received a number it would not accept and replaced or withheld it. Look at the INVITE for a Privacy header and an anonymous From, then compare the number you sent with the numbers provisioned on the trunk. If both look right, the next place to look is the carrier's own handling, which only they can confirm.
What is the difference between the From header and P-Asserted-Identity?
From is the identity the sender puts in the request. P-Asserted-Identity is an identity that a trusted network element asserts after it has authenticated the sender (RFC 3325). Which one a carrier displays is the carrier's policy, so the question to ask is which header your carrier reads and what format it expects.
Should I send P-Preferred-Identity to my carrier?
Only if the carrier asks for it. RFC 3325 says a user agent sends P-Preferred-Identity only to a proxy in a trust domain, and that the proxy removes it before forwarding. It is a hint about which of your valid identities to assert, not a command, and the proxy may add its own P-Asserted-Identity or reject the request if the hint matches nothing it knows.
Should the number be sent with a plus sign?
It depends on what the carrier expects, and the carrier's setup sheet is the authority. The global form of a number begins with a plus followed by the country code (RFC 3966, section 5.1.4, and ITU-T E.164). Some carriers want that, some want the digits only, and some want national format. A mismatch can make a number that is correctly provisioned look invalid.
Why does a number I own still not display?
Owning the number is not the same as being provisioned to present it on that trunk. The carrier normally checks the presented number against the numbers assigned to your account, and may override or reject others. Ask the carrier to confirm that the exact number, in the exact format you send, is allowed as caller ID on that trunk.
Do regulators care about the caller ID I present?
In many places, yes. As one worked example, Ofcom's guidance in the UK says that where CLI data is provided it must include a valid, dialable telephone number which uniquely identifies the caller. Other regulators have their own rules, so check the rules in each country you call. This article is general information, not legal advice.
Sources
- RFC 3325, Private Extensions to SIP for Asserted Identity within Trusted Networks, sections 5, 6 and 7. rfc-editor.org/rfc/rfc3325 (consulté le 7 novembre 2026)
- RFC 3323, A Privacy Mechanism for the Session Initiation Protocol (SIP). rfc-editor.org/rfc/rfc3323 (consulté le 7 novembre 2026)
- RFC 3966, The tel URI for Telephone Numbers, sections 5.1.1 and 5.1.4. rfc-editor.org/rfc/rfc3966 (consulté le 7 novembre 2026)
- ITU-T Recommendation E.164, The international public telecommunication numbering plan (02/26 listed as in force). itu.int/rec/T-REC-E.164 (consulté le 7 novembre 2026)
- RFC 8588, PASSporT Extension for SHAKEN (attestation levels). rfc-editor.org/rfc/rfc8588 (consulté le 7 novembre 2026)
- Ofcom, Calling line identification guidance. ofcom.org.uk (consulté le 7 novembre 2026)
Clause de non-responsabilité: This article is general information, not legal advice. DialerBee does not provide legal advice or guarantee regulatory compliance. The Ofcom guidance is a worked example checked on November 7, 2026, and rules differ by country and change over time. Confirm current requirements for each market you call with qualified counsel or the relevant regulator.
Lectures complémentaires
- How to Configure Caller ID Groups
- Explication de STIR/SHAKEN pour les équipes partantes
- Réputation du numéro appelant pour les équipes sortantes
- Qu'est-ce que l'identification de l'appelant ?
- Intelligence du numéro appelant
- SIP error codes on outbound calls
À lire aussi : Règles d'affichage du numéro appelant pour les appels commerciaux vers l'Allemagne
Articles connexes
SIP 488 Not Acceptable Here: Fixing Codec Mismatch
9 min de lecture
TechnologieSIP Error Codes on Outbound Calls: 403, 486, 503 and More
11 min de lecture
OpérationsQueue Callback (Virtual Hold): How to Set It Up
10 min de lecture
ConformitéSaudi SAMA Debt Collection Rules for Calling Teams
10 min de lecture
Prêt à voir DialerBee en action ?
Demandez une démo en direct de 15 minutes, ou démarrez un essai gratuit de 14 jours — sans diaporama, sans engagement. Les appels démarrent dès que votre propre trunk SIP ou PBX est connecté et approuvé.
Essai gratuit de 14 jours · crédit IA gratuit · sans carte · 11 langues · BYOC · contrôles qui contribuent à la conformité