Troubleshooting wrong or missing caller name on outbound calls

See also

Sources

1. 1
   Bandwidth LIDB names are limited to 15 characters including spaces, allow only the special characters . , & - _ and ', and may not begin with a space, be a phone number, or contain words such as Unavailable or Blocked.

   How do I add LIDB to phone numbers? · LIDB name requirements · Checked 2026-10-02
2. 2
   CTIA's Branded Calling ID uses STIR/SHAKEN to convey Rich Call Data (name, logo and call reason) to smartphones, with numbers and display names vetted by audited Authorized Partners.

   Branded Calling ID home · home page: how it works / Authorized Partners · Checked 2026-10-02
3. 3
   On 2025-09-15 CTIA announced that Verizon had signed a contract to integrate Branded Calling ID on its wireless network.

   New Consumer Tool, Branded Calling ID to launch on Verizon's Network · opening paragraph · Checked 2026-10-02
4. 4
   AWS warns that some carriers do not support caller ID names and some do not use the Voice Connector CNAM database, so a called party may see no name or a different name from the one set.

   Setting outbound calling names - Amazon Chime SDK · Note under 'Setting outbound calling names' · Checked 2026-10-02
5. 5
   Amazon Chime SDK calling names can be updated once every seven days, accept up to 15 characters, apply only to toll-based numbers, and need 72 hours to be added or updated.

   Setting outbound calling names - Amazon Chime SDK · intro paragraph and 'To set an outbound calling name' steps 5-6 · Checked 2026-10-02
6. 6
   47 CFR 64.1601(a)(1) requires telecommunications carriers and interconnected VoIP providers to transmit, for all PSTN traffic, the telephone number received from or assigned to or otherwise associated with the calling party.

   47 CFR 64.1601 - Delivery requirements and privacy restrictions · 47 CFR 64.1601(a)(1) · Checked 2026-10-02
7. 7
   The Free Caller Registry run by First Orion, Hiya and TNS is for reducing spam labeling, and its operators state that registration data is not used to deliver Caller ID Name.

   Free Caller Registry · registry description / disclaimer · Checked 2026-10-02
8. 8
   FCC 25-76 was adopted 2025-10-28 and released 2025-10-29 in CG Dockets 17-59, 02-278 and 25-307 and WC Docket 17-97, with comments due 2026-01-05 and replies 2026-02-03.

   Advanced Methods To Target and Eliminate Robocalls (proposed rule; FCC 25-76), 90 FR 56101 · Federal Register 2025-22063 header (DATES and docket lines) · Checked 2026-10-02
9. 9
   FCC 25-76 proposes that the minimum caller identity information to be transmitted is a verified name, whether personal or business.

   Advanced Methods To Target and Eliminate Robocalls (proposed rule; FCC 25-76), 90 FR 56101 · FCC 25-76 FNPRM, para. 13 · Checked 2026-10-02
10. 10
    As of 2026-10-02 this research found no adopted order putting the FCC 25-76 verified-caller-name proposals into effect, so they should be treated as proposals rather than current obligations.inferred

    Advanced Methods To Target and Eliminate Robocalls (proposed rule; FCC 25-76), 90 FR 56101 · Document type: Proposed rule (FNPRM) · Checked 2026-10-02
11. 11
    FCC 25-76 proposes that originating providers transmitting caller identity information employ reasonable measures to verify its accuracy, and asks what measures should count as reasonable.

    Advanced Methods To Target and Eliminate Robocalls (proposed rule; FCC 25-76), 90 FR 56101 · FCC 25-76 FNPRM, paras. 21-22 · Checked 2026-10-02
12. 12
    FCC 25-76 describes Rich Call Data as placing caller identity into a digitally signed PASSporT, like STIR/SHAKEN authentication, allowing secure transmission of caller name plus optional logo and other information.

    Advanced Methods To Target and Eliminate Robocalls (proposed rule; FCC 25-76), 90 FR 56101 · FCC 25-76 FNPRM, para. 29 · Checked 2026-10-02
13. 13
    In FCC 25-76 the Commission proposed requiring terminating providers to transmit verified caller identity information to consumer handsets whenever they transmit an indication that the call received A-level attestation.

    Advanced Methods To Target and Eliminate Robocalls (proposed rule; FCC 25-76), 90 FR 56101 · FCC 25-76 FNPRM, para. 8 · Checked 2026-10-02
14. 14
    Since providers describe US mobile CNAM display as opt-in, generally unused, or a paid add-on, a correct CNAM record should not be expected to show on every mobile recipient's handset; branded calling over STIR/SHAKEN is the route aimed at mobile.inferred

    Brand your calls using CNAM · mobile phones note (compared with Telnyx mobile note, Verizon Call Filter FAQ, Twilio US Basic Branded Calling overview) · Checked 2026-10-02
15. 15
    The general transmission duty in 64.1601(a)(1) covers the calling number; the only name-specific duty found in 64.1601 is the conditional telemarketer clause, so a missing caller name on an ordinary business call does not by itself indicate a federal rule breach.inferred

    47 CFR 64.1601 - Delivery requirements and privacy restrictions · 47 CFR 64.1601(a)(1) and (e)(1) read together · Checked 2026-10-02
16. 16
    Published CNAM update times range from about 12 hours (Telnyx-owned numbers) to about three weeks (Zoom Phone), so no single industry-wide propagation time can be given.inferred

    Caller ID Outbound vs CNAM · CNAM listing timeline (compared with Zoom KB0064090, Twilio, Sangoma, AWS) · Checked 2026-10-02
17. 17
    RFC 9795 states that an authentication service typically determines the nam value of rcd from the display-name component of the SIP From header field.

    RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data · RFC 9795 section 12 (SIP usage) · Checked 2026-10-02
18. 18
    RFC 9795 (Standards Track, July 2025) defines the rcd PASSporT claim (section 5) with a nam key (section 5.1.1) that carries the caller's display name in signed form.

    RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data · RFC 9795 sections 5 and 5.1.1 · Checked 2026-10-02
19. 19
    Sangoma states that if a number is bought from or ported to a carrier that does not support outbound CNAM, the feature will not work, and porting to a supporting carrier is the remedy.

    Wholesale CNAM Services - Outbound CNAM (aka CNAM Storage) · Carrier support requirements · Checked 2026-10-02
20. 20
    Sangoma's troubleshooting path for a wrong name is to confirm the record in its vendor database and the CNAM dip vendor; if both are correct, the receiving phone company must be contacted because the originator cannot force a correction.

    Wholesale CNAM Services - Outbound CNAM (aka CNAM Storage) · Troubleshooting: incorrect display · Checked 2026-10-02
21. 21
    Sangoma enters a CNAM change in its internal database immediately, pushes it to vendors about once a day (typically nightly), and says it takes about 48 business hours after that for dips to return the new name.

    Wholesale CNAM Services - Outbound CNAM (aka CNAM Storage) · Propagation / timeline section · Checked 2026-10-02
22. 22
    Sangoma states that displaying caller ID name is the responsibility of the receiving phone company, which looks up the name in a database when the call arrives, so the originating carrier cannot guarantee display.

    Wholesale CNAM Services - Outbound CNAM (aka CNAM Storage) · How it works · Checked 2026-10-02
23. 23
    SignalWire states that Canadian carriers do not read from the national CNAM registry, so its CNAM will not display on calls to Canadian numbers.

    Caller ID & CNAM · Geographic restrictions > Canada · Checked 2026-10-02
24. 24
    SignalWire states that CNAM applies only to PSTN calls; on SIP-to-SIP calls the displayed identity comes from the caller ID set on the SIP endpoint.

    Caller ID & CNAM · How CNAM works / SIP note · Checked 2026-10-02
25. 25
    SignalWire disallows CNAM on toll-free numbers.

    Caller ID & CNAM · Geographic restrictions > Toll-free · Checked 2026-10-02
26. 26
    Under 47 CFR 64.1601(b), originating carriers treat *67 dialed as the first three digits of a call as the caller's request that the CPN not be passed on an interstate call.

    47 CFR 64.1601 - Delivery requirements and privacy restrictions · 47 CFR 64.1601(b) · Checked 2026-10-02
27. 27
    Microsoft does not support originating CNAM information for Teams Phone calls in countries or regions other than the United States.

    More about Calling Line ID and Calling Party Name - Microsoft Teams · final paragraph · Checked 2026-10-02
28. 28
    In Teams PowerShell the calling party name of a caller ID policy is set with the -CompanyName parameter of New-CsCallingLineIdentity or Set-CsCallingLineIdentity.

    Manage caller ID for users - Microsoft Teams · Use PowerShell > New custom caller ID policy · Checked 2026-10-02
29. 29
    Microsoft attributes CNAM inconsistencies to intermediate or terminating carriers delaying refresh of CNAM information in authoritative databases, as in the United States.

    More about Calling Line ID and Calling Party Name - Microsoft Teams · final paragraph · Checked 2026-10-02
30. 30
    For Teams Direct Routing, the substituted number and the CNAM are sent to the SBC in the SIP From header; with -ForwardPai $true the P-Asserted-Identity carries the real calling user.

    Manage caller ID for users - Microsoft Teams · Outbound caller ID behavior > Outbound calling line ID · Checked 2026-10-02
31. 31
    On inbound PSTN calls Teams shows, in order of precedence, the called user's People contact, then Outlook and Entra ID contacts, then the call's calling party name, then the calling line ID.

    Manage caller ID for users - Microsoft Teams · Inbound caller ID behavior (hierarchy list) · Checked 2026-10-02
32. 32
    The Teams calling party name in a caller ID policy can be up to 200 characters, but Microsoft notes downstream systems might support fewer.

    Manage caller ID for users - Microsoft Teams · Outbound caller ID behavior > Outbound calling party name · Checked 2026-10-02
33. 33
    Teams sends the configured calling party name only when the caller ID is the user's own number or a resource account's number and the caller is a Teams user.

    Manage caller ID for users - Microsoft Teams · Outbound caller ID behavior > Outbound calling party name · Checked 2026-10-02
34. 34
    Teams caller ID policies using CallingIDSubstitute = Service are deprecated and no longer honored; CallingIDSubstitute = Resource must be used instead.

    Manage caller ID for users - Microsoft Teams · Use PowerShell > final Note · Checked 2026-10-02
35. 35
    Microsoft states that CLID and CNAM delivery is the responsibility of the terminating carrier, which must support CNAM and keep the records up to date, and that Microsoft has little recourse if an intermediary or terminating carrier alters the values.

    More about Calling Line ID and Calling Party Name - Microsoft Teams · second paragraph after the CLID/CNAM definitions · Checked 2026-10-02
36. 36
    Under 47 CFR 64.1601(e)(1), a telemarketer's caller identification must include either CPN or ANI and, when made available by the telemarketer's carrier, the name of the telemarketer.

    47 CFR 64.1601 - Delivery requirements and privacy restrictions · 47 CFR 64.1601(e)(1) · Checked 2026-10-02
37. 37
    47 CFR 64.1601(e)(2) prohibits any person or entity engaged in telemarketing from blocking the transmission of caller identification information.

    47 CFR 64.1601 - Delivery requirements and privacy restrictions · 47 CFR 64.1601(e)(2) · Checked 2026-10-02
38. 38
    Telnyx states that Canada has no national CNAM database and that Canadian caller name information is instead passed in SIP headers.

    Caller ID Outbound vs CNAM · How CNAM works > Canada · Checked 2026-10-02
39. 39
    Telnyx says CNAM values on Telnyx-owned numbers usually reach the database within 12 to 24 hours but can take up to 72 hours, while numbers on underlying carriers take 3 to 5 working days to process.

    Caller ID Outbound vs CNAM · CNAM listing timeline · Checked 2026-10-02
40. 40
    Telnyx notes a customer can put their own display name in the SIP From or P-Asserted-Identity header, but it may or may not be passed all the way through to the called party.

    Caller ID Outbound vs CNAM · Outbound caller ID vs CNAM · Checked 2026-10-02
41. 41
    Telnyx states that the industry-wide CNAM service is not generally used by wireless carriers.

    Caller ID Outbound vs CNAM · mobile carriers note · Checked 2026-10-02
42. 42
    Twilio CNAM display names can be at most 15 characters, should begin with a letter, and may contain only letters, numbers, periods, commas and spaces.

    Brand your calls using CNAM · CNAM requirements section · Checked 2026-10-02
43. 43
    Twilio bills US Basic Branded Calling only when brand information is successfully delivered on a call.

    US Basic Branded Calling · billing note · Checked 2026-10-02
44. 44
    Twilio US Basic Branded Calling is a Public Beta product, and its documentation lists T-Mobile and Verizon as the networks that display it.

    US Basic Branded Calling · supported carriers and status notes · Checked 2026-10-02
45. 45
    Twilio's US Basic Branded Calling display name is limited to 15 characters on Verizon and 32 characters on T-Mobile and must relate to the business name.

    US Basic Branded Calling · display requirements · Checked 2026-10-02
46. 46
    Twilio positions US Basic Branded Calling for display on mobile phones and directs customers to CNAM for landlines.

    US Basic Branded Calling · overview · Checked 2026-10-02
47. 47
    Only US standard long code numbers assigned to a Twilio Business Profile are eligible for Twilio CNAM; Canadian numbers and US or Canadian toll-free numbers cannot be assigned to CNAM profiles.

    Brand your calls using CNAM · eligibility section · Checked 2026-10-02
48. 48
    Twilio states that most US mobile carriers offer CNAM as an opt-in feature, and if the recipient has not enabled it the name is not shown even when CNAM is set correctly.

    Brand your calls using CNAM · mobile phones note · Checked 2026-10-02
49. 49
    Twilio requires a CNAM value to be a unique name and not a generic value such as a city or state.

    Brand your calls using CNAM · CNAM requirements section · Checked 2026-10-02
50. 50
    Twilio states it keeps its CNAM LIDB records current but not all carriers subscribe to every CNAM database.

    Brand your calls using CNAM · CNAM overview / limitations · Checked 2026-10-02
51. 51
    Twilio says that after a CNAM Trust Product is approved the display name may take 48 to 72 hours to propagate to all US carriers.

    Brand your calls using CNAM · propagation note after approval steps · Checked 2026-10-02
52. 52
    Verizon lists Caller ID (name display for unknown numbers) as a Call Filter Plus feature rather than part of free Call Filter, priced at $3.99 per month per line.

    Avoid unwanted calls with Verizon Call Filter FAQs · FAQ: upgrade to Call Filter Plus · Checked 2026-10-02
53. 53
    Verizon states its Call Filter Caller ID is not available for restricted or unlisted numbers.

    Avoid unwanted calls with Verizon Call Filter FAQs · FAQ: Caller ID limitations · Checked 2026-10-02
54. 54
    With Webex Calling Cloud Connected PSTN, setting the External Caller ID Name in Control Hub does not update the public CNAM database; the admin must contact the PSTN provider.

    Specify caller ID for users and workspaces · Configure a caller ID for a location · Checked 2026-10-02
55. 55
    Webex Calling offers three external caller ID name choices for users and workspaces: Direct Line (the user or workspace name), the location's external caller ID name, or an Other name entered by the admin.

    Specify caller ID for users and workspaces · Configure caller ID for a user; Configure caller ID for a workspace · Checked 2026-10-02
56. 56
    Cisco states that some PSTN providers may not honor the caller ID name setting sent by Webex Calling.

    Specify caller ID for users and workspaces · Configure caller ID for a user · Checked 2026-10-02
57. 57
    Zoom Phone caller ID names apply only to US and Canada numbers, are limited to 15 characters with no special characters, and display in uppercase regardless of how they are entered.

    Managing the main company number and caller ID · caller ID name restrictions · Checked 2026-10-02
58. 58
    Zoom Phone caller ID names are set per organization or per site, not per user; individual users' caller ID names cannot be changed.

    Managing the main company number and caller ID · configuration level / multi-site note · Checked 2026-10-02
59. 59
    Zoom says a changed Zoom Phone caller ID name can take around three weeks to be updated by external carriers.

    Managing the main company number and caller ID · caller ID name notes · Checked 2026-10-02

Documents

Cite this page

WarmTransfer. (2026, October 2). Troubleshooting wrong or missing caller name on outbound calls. WarmTransfer. https://warmtransfer.net/knowledge/cnam-display-troubleshooting

@misc{warmtransfer-cnam-display-troubleshooting,
  title  = {Troubleshooting wrong or missing caller name on outbound calls},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/cnam-display-troubleshooting},
  note   = {Verified 2026-10-02}
}