Wrong or missing caller ID on outbound calls

See also

Sources

1. 1
   RFC 3323 gives the anonymous From header form "Anonymous" <sip:anonymous@anonymous.invalid> with a tag, using the reserved .invalid domain.

   RFC 3323: A Privacy Mechanism for the Session Initiation Protocol (SIP) · Section 4.1.1.3 (anonymous From example) · Checked 2026-09-25
2. 2
   47 CFR 64.1601(a) requires US carriers to transmit the calling party number received from, or associated with, the calling party through the call path, including the charge number in SS7 when it differs.

   47 CFR 64.1601 - Delivery requirements and privacy restrictions · Paragraph (a) · Checked 2026-09-25
3. 3
   47 CFR 64.1601(b) requires SS7 carriers to honor *67 as a per-call request to block CPN and *82 as a request to pass it, and bars carriers from overriding the privacy indicator.

   47 CFR 64.1601 - Delivery requirements and privacy restrictions · Paragraph (b) · Checked 2026-09-25
4. 4
   47 CFR 64.1601(e) requires telemarketers to transmit CPN or ANI and, when available, their name; they may substitute the seller's name and customer service number, and may not block caller ID.

   47 CFR 64.1601 - Delivery requirements and privacy restrictions · Paragraph (e) · Checked 2026-09-25
5. 5
   On CUBE, 'asserted-id pai' or 'asserted-id ppi' (globally under voice service voip sip, or per dial peer as 'voice-class sip asserted-id') makes outgoing SIP messages carry P-Asserted-Identity or P-Preferred-Identity.

   Cisco Unified Border Element SIP Support Configuration Guide, Cisco IOS Release 12.4T - Support for PAID PPID Privacy PCPID and PAURI Headers · P-Preferred Identity and P-Asserted Identity Headers section · Checked 2026-09-25
6. 6
   Cisco's IOS 12.4T CUBE guide states that translation to RPID headers is enabled by default, so PPID headers in incoming messages are translated to RPID in outgoing messages unless asserted-id is configured.

   Cisco Unified Border Element SIP Support Configuration Guide, Cisco IOS Release 12.4T - Support for PAID PPID Privacy PCPID and PAURI Headers · P-Preferred Identity and P-Asserted Identity Headers section, default-behavior sentence · Checked 2026-09-25
7. 7
   CUBE's 'privacy-policy passthru' (globally, or 'voice-class sip privacy-policy passthru' per dial peer) passes multiple Privacy header values through transparently, and CUBE can add a Privacy header with value none when forwarding.

   Cisco Unified Border Element SIP Support Configuration Guide, Cisco IOS Release 12.4T - Support for PAID PPID Privacy PCPID and PAURI Headers · Privacy section · Checked 2026-09-25
8. 8
   In Cisco's tech note 212649, a call forwarded from Unified CM to the PSTN failed with '604 Does Not Exist Anywhere' because the Diversion header held an internal extension instead of an E.164 number. The fix was a header-editor rule that rewrote Diversion to E.164.

   Troubleshoot CUBE SP Rejects Internal Call which is Fowarded to a PSTN Number · Problem / Solution sections · Checked 2026-09-25
9. 9
   With Unified CM's External Presentation Name and Number feature, the From header carries the configured presentation name and number for display only, while PAID (and Remote-Party-ID) carries the user's real identity, such as the DN or DDI, for billing.

   Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Separate Calling Party Number and Billing Number in SIP · Separate Calling Party Number and Billing Number in SIP > feature overview · Checked 2026-09-25
10. 10
    In Unified CM 15 the External Presentation Number accepts up to 32 digits, with trailing X characters replaced by directory-number digits from right to left, and the External Presentation Name accepts up to 50 characters.

    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Separate Calling Party Number and Billing Number in SIP · Configuration field descriptions for External Presentation Name and Number · Checked 2026-09-25
11. 11
    In Unified CM, SIP trunk external presentation settings override SIP Profile settings, which in turn override directory number settings.

    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Separate Calling Party Number and Billing Number in SIP · Configuration hierarchy / interactions section · Checked 2026-09-25
12. 12
    RFC 5806, which documents the SIP Diversion header, is in the Historic category and was published for the historical record rather than as a standard.

    RFC 5806: Diversion Indication in SIP · Status of This Memo · Checked 2026-09-25
13. 13
    The Diversion header tells the receiving party from whom a request was diverted and why, carrying the pre-diversion Request-URI and a reason parameter.

    RFC 5806: Diversion Indication in SIP · Section 3 (Overview) · Checked 2026-09-25
14. 14
    RFC 5806 names RFC 4244 (request History-Info) as the standards solution the IETF chose instead of Diversion.

    RFC 5806: Diversion Indication in SIP · Abstract / Introduction reference to RFC 4244 · Checked 2026-09-25
15. 15
    The Federal Register publication of FCC 24-120 gives September 18, 2025 as the effective date of the third-party authentication rules.

    Call Authentication Trust Anchor (Federal Register 2025-15809; FCC 24-120) · DATES paragraph · Checked 2026-09-25
16. 16
    In the Federal Register text of FCC 24-120, A-level attestation requires the originating provider to have a direct authenticated relationship with the customer, be able to identify it, and have verified that the customer has a legitimate right to use the telephone number.

    Call Authentication Trust Anchor (Federal Register 2025-15809; FCC 24-120) · Supplementary Information Section I.A.2, FR pages 40244-40245 · Checked 2026-09-25
17. 17
    FCC 24-120 states that the attestation-level determination requires the originating provider's due diligence on its own customer and cannot be made by a third party with no relationship to that customer.

    Call Authentication Trust Anchor (Federal Register 2025-15809; FCC 24-120) · Supplementary Information Section I.A.2, FR page 40245 · Checked 2026-09-25
18. 18
    Under FCC 24-120, a provider with a STIR/SHAKEN obligation may use a third party to sign calls, but every call must be signed with the obligated provider's own certificate and the provider must make the attestation-level decisions.

    Call Authentication Trust Anchor (Federal Register 2025-15809; FCC 24-120) · Summary and Supplementary Information Section I.A.2, FR page 40244 · Checked 2026-09-25
19. 19
    RFC 7044 is the Standards Track History-Info specification and obsoletes RFC 4244.

    RFC 7044: An Extension to the Session Initiation Protocol (SIP) for Request History Information · Header block (Obsoletes: 4244; Category: Standards Track) · Checked 2026-09-25
20. 20
    RFC 7044 defines a Privacy priv-value 'history' that asks for History-Info entries to be anonymized, with a Privacy Service replacing un-anonymized targeted-to URIs with anonymous.invalid URIs at domain boundaries.

    RFC 7044: An Extension to the Session Initiation Protocol (SIP) for Request History Information · Section 10 (privacy processing) as returned by retrieval; subsection not confirmed · Checked 2026-09-25
21. 21
    When the far end sees a number other than the one configured, the first thing to check is whether From and P-Asserted-Identity in the outbound INVITE carry different numbers. All three platforms can deliberately split them (Teams substitution with ForwardPai, Unified CM external presentation, Webex Dual Identity), and at least one vendor documents carriers preferring PAI.inferred

    Issues with outbound calls - Microsoft Teams · Incorrect caller ID displayed to the recipient > Cause; combined with the Unified CM and Webex claims noted · Checked 2026-09-25
22. 22
    A US originating provider can give A-level attestation to a substituted or presentation number only if it has verified the customer's right to use that number. A number the enterprise does not hold with that provider, such as one ported elsewhere or belonging to a third party, is likely to be signed below A or to be screened.inferred

    Call Authentication Trust Anchor (Federal Register 2025-15809; FCC 24-120) · Section I.A.2 A-level criteria, applied to the substitution features documented by the vendors · Checked 2026-09-25
23. 23
    Under RFC 3325 a proxy inserts P-Asserted-Identity after it has authenticated the originating user, for example with Digest authentication.

    RFC 3325: Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks · Section 4 (P-Asserted-Identity description) as returned by retrieval · Checked 2026-09-25
24. 24
    A P-Asserted-Identity header carries at most two values, and if there are two, one must be a sip or sips URI and the other a tel URI.

    RFC 3325: Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks · Section 9.1 (P-Asserted-Identity syntax) · Checked 2026-09-25
25. 25
    RFC 3325 limits P-Asserted-Identity to use inside a Trust Domain of SIP servers that are explicitly trusted to assert identity under shared policy.

    RFC 3325: Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks · Section 1 (Introduction) applicability statement on Trust Domains · Checked 2026-09-25
26. 26
    A user agent may send P-Preferred-Identity to a trusted proxy as a hint about which identity to assert, and the proxy must remove that header from any message it forwards.

    RFC 3325: Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks · Section 6 (P-Preferred-Identity / hints for multiple identities) as returned by retrieval · Checked 2026-09-25
27. 27
    The RFC 3323 priv-value 'critical' asserts that the requested privacy is critical and that the request should be rejected if the network cannot provide it.

    RFC 3323: A Privacy Mechanism for the Session Initiation Protocol (SIP) · Section 4.2, definition of 'critical' · Checked 2026-09-25
28. 28
    When the Privacy header contains the 'id' token, RFC 3325 requires proxies to remove all P-Asserted-Identity header fields before forwarding to elements that are not trusted.

    RFC 3325: Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks · Privacy 'id' handling text; retrieval placed it in Section 7 with the priv-value registered in Section 9.3; section number unconfirmed · Checked 2026-09-25
29. 29
    RFC 3323 defines the Privacy header priv-values header, session, user, none and critical; the 'id' value comes from RFC 3325, not RFC 3323.

    RFC 3323: A Privacy Mechanism for the Session Initiation Protocol (SIP) · Section 4.2 (Privacy header values) · Checked 2026-09-25
30. 30
    The SHAKEN PASSporT 'attest' claim takes the values A, B or C, meaning Full, Partial and Gateway Attestation respectively.

    RFC 8588: Personal Assertion Token (PaSSporT) Extension for Signature-based Handling of Asserted information using toKENs (SHAKEN) · Section 4 (PASSporT 'attest' claim) · Checked 2026-09-25
31. 31
    The SHAKEN PASSporT 'origid' claim is a UUID (RFC 4122) identifying the call's origination point to support traceback.

    RFC 8588: Personal Assertion Token (PaSSporT) Extension for Signature-based Handling of Asserted information using toKENs (SHAKEN) · Section 5 (PASSporT 'origid' claim) · Checked 2026-09-25
32. 32
    RFC 8224 authentication services take the originator's identity typically from the From header, and its guidance also applies to taking it from P-Asserted-Identity where local policy in a trusted environment dictates.

    RFC 8224: Authenticated Identity Management in the Session Initiation Protocol (SIP) · Text on identity sources and P-Asserted-Identity; section number not returned by retrieval · Checked 2026-09-25
33. 33
    For STIR signing, RFC 8224 canonicalizes telephone numbers by dropping '+', dashes, parentheses and other non-digits except '#' and '*', and says implementations SHOULD convert the number to E.164 form, adding a country code if necessary.

    RFC 8224: Authenticated Identity Management in the Session Initiation Protocol (SIP) · Section 8.3 (canonicalization of telephone numbers) · Checked 2026-09-25
34. 34
    Microsoft states that CLID values it originates may be changed, omitted or truncated by intermediary or terminating carriers, and that it has little to no recourse in correcting this in the PSTN.

    More about Calling Line ID and Calling Party Name - Microsoft Teams · Second paragraph of body · Checked 2026-09-25
35. 35
    Microsoft attributes inconsistent CNAM to intermediate or terminating carriers delaying refresh of authoritative CNAM databases, as in the United States, and to individual carrier practice where no such database exists.

    More about Calling Line ID and Calling Party Name - Microsoft Teams · Final paragraph of body · Checked 2026-09-25
36. 36
    The Teams caller ID policy Calling Party Name can be up to 200 characters, but Microsoft warns that downstream systems might support fewer.

    Manage caller ID for users - Microsoft Teams · Outbound caller ID behavior > Outbound calling party name · Checked 2026-09-25
37. 37
    Microsoft states it does not currently support originating CNAM for Teams calls in countries or regions other than the United States.

    More about Calling Line ID and Calling Party Name - Microsoft Teams · Final paragraph of body · Checked 2026-09-25
38. 38
    For Direct Routing, Teams sends the substitute number and CNAM in the From header, and if the SBC's OnlinePstnGateway has ForwardPai set to true, P-Asserted-Identity carries the real calling user.

    Manage caller ID for users - Microsoft Teams · Outbound caller ID behavior > Outbound calling line ID (Direct Routing paragraph) · Checked 2026-09-25
39. 39
    In Direct Routing, Microsoft's troubleshooting article says the From header holds the caller's number (or 'anonymous'), a substitute number from CsCallingLineIdentity, or the original caller's number on a forwarded call, while P-Asserted-Identity holds the number of the user billed for the call.

    Issues with outbound calls - Microsoft Teams · Incorrect caller ID displayed to the recipient (intro paragraphs) · Checked 2026-09-25
40. 40
    Microsoft attributes a wrong caller ID on Direct Routing calls to From and P-Asserted-Identity differing while the PSTN prioritizes PAI, and recommends configuring the SBC to remove or modify the PAI header.

    Issues with outbound calls - Microsoft Teams · Incorrect caller ID displayed to the recipient > Cause / Resolution · Checked 2026-09-25
41. 41
    Teams emergency calls always send the user's own calling line ID to the PSAP, whatever the caller ID policy says.

    Manage caller ID for users - Microsoft Teams · Outbound caller ID behavior > Important note · Checked 2026-09-25
42. 42
    The Set-CsOnlinePSTNGateway ForwardCallHistory parameter makes Direct Routing send History-Info and Referred-By headers to the SBC, and it defaults to $false.

    Set-CsOnlinePSTNGateway (MicrosoftTeams) · Parameters > -ForwardCallHistory · Checked 2026-09-25
43. 43
    The ForwardPai parameter of Set-CsOnlinePSTNGateway controls whether Direct Routing forwards the P-Asserted-Identity header to the SBC, and it defaults to $false.

    Set-CsOnlinePSTNGateway (MicrosoftTeams) · Parameters > -ForwardPai · Checked 2026-09-25
44. 44
    Microsoft's disputed statement: according to the Set-CsOnlinePSTNGateway reference, setting ForwardPai to $true 'will render the from header anonymous', citing RFC 5379 and RFC 3325, whereas the Teams caller ID article says that with ForwardPai true the From header still carries the substitute number and CNAM. Neither page says which behavior applies to which calls.disputed

    Set-CsOnlinePSTNGateway (MicrosoftTeams) · Parameters > -ForwardPai (last sentence) · Checked 2026-09-25
45. 45
    When a Teams user calls on behalf of another account (a delegator, a call queue or shared calling), the caller ID configured for that account replaces the user's caller ID.

    Manage caller ID for users - Microsoft Teams · Outbound caller ID behavior > Outbound calling line ID (calling on behalf of another account) · Checked 2026-09-25
46. 46
    A Teams caller ID policy can send the user's assigned number (the default), Anonymous, or a substitute number assigned to a resource account used by an auto attendant or call queue.

    Manage caller ID for users - Microsoft Teams · Outbound caller ID behavior > Outbound calling line ID · Checked 2026-09-25
47. 47
    The Teams caller ID policy value CallingIDSubstitute = Service is deprecated: new policies cannot use it, existing ones are not honored, and Resource should be used instead.

    Manage caller ID for users - Microsoft Teams · Configure caller ID policies > Use PowerShell > closing Note · Checked 2026-09-25
48. 48
    Teams will not accept as a substitute caller ID any Calling Plan or Operator Connect number whose usage type is User, any Direct Routing number assigned to a user, or any Skype for Business Server on-premises number.

    Manage caller ID for users - Microsoft Teams · Outbound caller ID behavior > Outbound calling line ID (list of numbers you can't assign) · Checked 2026-09-25
49. 49
    If a Teams caller ID policy has EnableUserOverride on, the user's own hide-my-number setting takes precedence over the other policy settings, in either direction.

    Manage caller ID for users - Microsoft Teams · Outbound caller ID behavior > End user control that overrides the caller ID policy · Checked 2026-09-25
50. 50
    In a tel URI a global number is identified by a leading '+' and must consist of the E.164 country code and national number.

    RFC 3966: The tel URI for Telephone Numbers · Section 5.1.4 (global numbers) · Checked 2026-09-25
51. 51
    A local number in a tel URI must carry a phone-context parameter identifying the scope in which it is valid.

    RFC 3966: The tel URI for Telephone Numbers · Section 5.1.5 (local numbers) · Checked 2026-09-25
52. 52
    In Control Hub, a Webex Calling user, workspace or virtual line can present its direct line, its location's main number, or another number from the organization as the outbound caller ID number.

    Specify caller ID for users and workspaces · Configure caller ID for a user (and workspace / virtual line sections) · Checked 2026-09-25
53. 53
    The Webex Calling trunk setting Dual Identity Support decides the From and P-Asserted-Identity headers on outbound INVITEs to the trunk: when enabled the two can differ, and when disabled they are identical.

    Configure trunks, route groups, and dial plans for Webex Calling · Add a trunk for your location > Dual Identity Support · Checked 2026-09-25
54. 54
    Cisco notes that some PSTN providers may not honor the caller ID name set through Webex Calling.

    Specify caller ID for users and workspaces · Caller ID name options note · Checked 2026-09-25
55. 55
    A Webex Calling 'other number' caller ID must come from the same PSTN provider, country and zone as the user or workspace, and can be assigned or unassigned.

    Specify caller ID for users and workspaces · Configure caller ID for a user > caller ID number options · Checked 2026-09-25
56. 56
    The Webex Calling trunk option P-Charge-Info Support adds a P-Charge-Info header to outbound PSTN calls. It is disabled by default, and its policy options are the primary or location main number, or a charge number customized on the location page.

    Configure trunks, route groups, and dial plans for Webex Calling · Add a trunk for your location > P-Charge-Info Support · Checked 2026-09-25
57. 57
    Cisco positions P-Charge-Info as letting the PSTN provider identify the chargeable number from one header, without relying on PAI for normal originations and Diversion for redirected calls.

    Configure trunks, route groups, and dial plans for Webex Calling · Add a trunk for your location > P-Charge-Info Support · Checked 2026-09-25
58. 58
    Cisco warns that if an unassigned number is chosen as a Webex Calling caller ID, callbacks to that number are not answered.

    Specify caller ID for users and workspaces · Configure caller ID for a user > note on unassigned numbers · Checked 2026-09-25
59. 59
    When an administrator has enabled it, a Webex App user can choose the outbound caller ID for external calls from direct line, location, call queue, hunt group (Webex Calling only) or other organization numbers.

    Webex App | Change your caller ID · Article body, desktop and mobile procedures · Checked 2026-09-25
60. 60
    The calling number a carrier receives from a globalized Unified CM dial plan can be shaped in two places, Unified CM calling party transformation CSSs and IOS voice translation rules on the gateway, so both must be checked when the carrier sees an unexpected caller ID.inferred

    Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control · Dial Plan, Outbound Calls: Called and Calling Number Localization; combined with Configure Call Routing chapter, Transformation Patterns · Checked 2026-09-25

Documents

Cite this page

WarmTransfer. (2026, September 25). Wrong or missing caller ID on outbound calls. WarmTransfer. https://warmtransfer.net/knowledge/caller-id-presentation-problems

@misc{warmtransfer-caller-id-presentation-problems,
  title  = {Wrong or missing caller ID on outbound calls},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/caller-id-presentation-problems},
  note   = {Verified 2026-09-25}
}