Fact-checked by Grok 2 weeks ago

Calling Name Presentation

Calling Name Presentation (CNAP) is a supplementary that enables the called party to receive and display the name information associated with the calling party's telephone number during call setup for incoming calls. Standardized by the 3rd Generation Partnership Project () in TS 22.096, it applies to all circuit-switched bearer services except Short Message Service (SMS), and is invoked automatically by the network when name data is available. The service supports names up to 80 characters in length and includes presentation indicators, such as "presentation restricted" if the caller has invoked Calling Line Identification Restriction (CLIR) or "name not available" otherwise. In practice, CNAP operates by querying centralized databases maintained by network operators to retrieve the caller's registered name, which is then transmitted via signaling protocols like SS7 or in modern networks. It interacts with related services, including CLIR (which takes precedence to withhold the name) and (where the original caller's name is preserved unless restricted). While the core functionality is defined internationally, implementations vary by region; in , it is commonly known as Caller Name Delivery (CNAM) and relies on a shared national database for landline and mobile numbers. Globally, CNAP has been deployed in various countries to improve call security and reduce , with recent expansions in regions like the and . For instance, in , the (TRAI) approved its nationwide rollout in October 2025, mandating verified names linked to SIM registration documents to combat fraudulent calls, with pilots underway and full implementation expected by March 2026. The service requires subscription by the called party for automatic activation and display on compatible devices, with callers able to restrict name presentation via CLIR.

Definition and Functionality

Core Concept

Calling Name Presentation (CNAP) is a that retrieves and displays the name associated with the calling party's number on the recipient's device during an incoming call. Standardized by the 3rd Generation Project (3GPP) in TS 22.096, this functionality operates within networks to provide alphanumeric caller identification, typically appearing alongside or in lieu of the phone number in the field. By associating names with numbers through centralized databases, CNAP extends beyond traditional numeric-only displays to offer more contextual information about the caller. CNAP represents the broad international term for this name delivery capability, while , the equivalent service is termed Caller Name Delivery (CNAM), a standardized variant embedded in the country's . Both terms describe the same core objective of name-based caller presentation, though implementations may vary by region due to differing network architectures. The service aims to combat , scams, and unwanted calls by presenting names tied to identities from telecom operator databases, thereby empowering recipients to assess call legitimacy before answering. This enhances overall user protection and call management, as names foster greater in incoming communications compared to or spoofed numbers. A practical example involves a call from a : instead of showing only a generic number like (555) 123-4567, the recipient's screen might indicate "ABC Customer ," enabling quick of legitimate entities.

Operational Mechanism

Calling Name Presentation (CNAP), also known as Caller Name Delivery (CNAM) in some regions, operates through a lookup mechanism triggered by incoming calls in networks. When a call is placed, the caller's phone number, known as the Calling Line (CLID), is transmitted through to the recipient's . The terminating carrier's switch then initiates a query to a centralized Line Information Database (LIDB) or equivalent name database to retrieve the associated caller's name, which is pulled rather than pushed by the originating . The operational flow proceeds as follows:
  1. Call Initiation: The caller dials the recipient's number, and the call is routed via the originating carrier's network, including the CLID in signaling messages.
  2. Query Trigger: Upon reaching the terminating carrier's switch, a "dip" is performed using the CLID to search the LIDB for the registered name. In CNAP implementations, names can be up to 80 characters per 3GPP TS 22.096, while in CNAM, they are typically limited to 15 alphanumeric characters. This query occurs in milliseconds to avoid call setup delays.
  3. Response Retrieval: If a match is found, the LIDB returns the name; otherwise, no name or a default indicator is provided. The response is integrated into the call signaling.
  4. Name Transmission and Delivery: The retrieved name is forwarded to the recipient's alongside the CLID, enabling during the ringing phase.
In traditional (PSTN) environments, Signaling System No. 7 (SS7) facilitates the CNAP process by routing query messages over the Common Channel Signaling () network to the appropriate LIDB, ensuring secure and reliable database access between switches. For (VoIP) calls, (SIP) plays a key role, where the display name can be embedded in SIP headers (e.g., the From field) during call setup, though interworking with PSTN often still requires LIDB queries for accurate name resolution. Anonymous or blocked calls are handled by suppressing the CLID and name transmission at the originating end, typically via user-activated features like *67 in the United States. In such cases, the terminating carrier does not perform a name query, and the recipient's device displays "Private," "Unknown," or "Anonymous" as a default, prioritizing caller privacy over identification. On smartphones, CNAP integration occurs at the network-device interface, where the carrier delivers the name via signaling protocols to the (e.g., or ). The device's telephony stack parses the incoming call , rendering the name prominently on the incoming call screen or notification, often overriding or supplementing local contact lookups if the carrier supports the feature. This ensures seamless presentation without requiring third-party apps, though mobile carriers may impose opt-in requirements or additional fees for full functionality.

Historical Development

Origins in Caller ID Systems

The development of in the laid the groundwork for Calling Name Presentation (CNAP) by establishing the infrastructure for transmitting caller information over telephone networks. , part of the , had earlier invented () in the 1940s as a means to automatically capture calling line details for long-distance billing purposes, using electromechanical equipment in central offices. This ANI technology provided the core capability to route and identify calls internally, but it was not initially designed for consumer access. By the early , as electronic switching systems proliferated, regional Bell Operating Companies adapted ANI principles to enable the external delivery of calling numbers, transforming it into the basis for public services. The first commercial trial of took place in January 1984, when conducted a market test in , allowing select customers to view incoming telephone numbers on specialized display devices. Key milestones in the late 1980s and early 1990s solidified 's role while highlighting privacy tensions that shaped its evolution. Services expanded commercially in the late 1980s, with Bell pioneering deployments in 1987 through field trials and making it available to customers in December 1988. The (FCC) addressed regulatory hurdles by adopting its first rules on in 1991, mandating that telephone companies offer free per-call and per-line blocking options to protect caller anonymity. These rules responded to widespread privacy concerns from groups, who argued that unblocked number transmission could enable , , or unwanted commercial targeting; as a result, early implementations strictly limited displays to numbers only, avoiding any personal identifiers like names to mitigate these risks. Technologically, Caller ID's precursors relied on in-band signaling techniques suited to analog telephone lines, which were the dominant infrastructure at the time. Data transmission occurred via (FSK) modulation at a rate of 1200 bits per second, embedded within the voice frequency band (typically between 1200 Hz and 2200 Hz) during a brief "" (Caller ID Alert Signal) tone played between the first and second rings. This method allowed central office equipment to send the calling number as a series of ASCII-encoded bytes without requiring separate data channels, leveraging existing (POTS) lines for compatibility. Such in-band approaches were essential for cost-effective rollout but were vulnerable to noise and line conditions, often necessitating robust error-checking in receiving devices. Despite these advances, early Caller ID systems suffered from significant limitations, particularly the lack of name presentation, which underscored the need for future enhancements like CNAP. Without integrated databases to map numbers to names, services could only provide numeric identifiers, leaving users to manually look up contacts and limiting utility for recognizing unknown callers. objections further delayed name inclusion, as advocates feared it would exacerbate risks beyond mere numbers; this number-only focus thus positioned CNAP as a critical evolution, introducing name resolution through external lookups while building on the established signaling framework.

Evolution and Standardization

The evolution of Calling Name Presentation (CNAP) in the marked a significant advancement beyond basic phone number delivery in systems, with U.S. companies introducing centralized Calling Name (CNAM) databases to link subscriber names to phone numbers for display on receiving devices. These databases enabled the first widespread deployment of name presentation services, becoming available to consumers around as part of enhanced caller identification features in networks. The (TIA), through its standards development efforts under the (ANSI), formalized the technical requirements for CNAM in the late ; specifically, ANSI T1.401.03-1998 defined the signaling protocols and data transmission interfaces for delivering caller names using analog equipment, ensuring across networks. The first specified CNAP as a supplementary service in TS 22.096 in Release (), providing an international framework that complemented CNAM implementations. During the 2000s, CNAP expanded to wireless environments through enhancements to the IS-41 protocol, the standard for cellular network signaling in , which incorporated SS7-based queries to CNAM databases for mobile-to-landline and mobile-to-mobile calls. This integration allowed name presentation in and handoff scenarios, broadening CNAP's applicability as mobile usage surged. For (VoIP) systems, the (IETF) supported CNAP via the (SIP) outlined in RFC (), where caller identity details, including names, could be conveyed in SIP headers to enable presentation in packet-switched networks. In more recent years, standardization has focused on next-generation networks, with the 3rd Generation Partnership Project (3GPP) incorporating CNAP support within the IP Multimedia Subsystem (IMS) framework for 4G LTE and 5G deployments; for instance, ETSI TS 123 231 (adopted from 3GPP specifications) describes CNAP as a supplementary service in IMS, allowing name delivery over IP-based mobile architectures. The Alliance for Telecommunications Industry Solutions (ATIS, successor to certain TIA functions) further advanced this with ATIS-1000067.2015, defining enhanced CNAM (eCNAM) for IP next-generation networks (NGN), improving accuracy and compatibility in hybrid circuit- and packet-switched systems. Globally, the European Telecommunications Standards Institute (ETSI) has contributed through harmonized supplementary services protocols, aligning CNAP-like features with international SS7 and IMS standards to facilitate cross-border interoperability. Notable recent efforts include pilots in emerging markets; for example, in October 2025, India's Telecom Regulatory Authority (TRAI) released recommendations for introducing CNAP across its telecommunication networks, initiating trials in select regions to combat while leveraging existing IMS . These developments underscore the ongoing role of bodies like TIA/ATIS and in refining protocols for secure, reliable name presentation amid the shift to all-IP networks.

Technical Implementation

Database and Network Integration

The Calling Name Presentation (CNAP) service relies on databases that store mappings between telephone numbers and associated alphanumeric names, with structures varying by and region. In many implementations, operators maintain centralized databases within their public land mobile networks (PLMNs) to retrieve caller name information during call setup. In , the related Caller Name Delivery (CNAM) system uses a of regional , often referred to as Line Information Databases (LIDB), which are decentralized and maintained by individual carriers, allowing each to operate its own repository of caller data. This structure supports efficient local management but requires coordination across providers for consistency. Telecommunications companies update and these databases through subscription-based s, where carriers pay per query to retrieve name information during call setup. In the United States, query costs typically range from $0.002 to $0.003 per lookup (as of 2025), enabling real-time name while incentivizing accurate by providers. Integration with telecom networks occurs primarily through signaling . In traditional circuit-switched networks, queries are routed via service control points that interface with the name database. For mobile networks, CNAP is invoked automatically during call setup using supplementary protocols. Carriers must connect to the appropriate signaling to these points, ensuring seamless retrieval. In , for number portability, periodic database updates are synchronized with the Number Portability Administration Center (NPAC); this central hub, administered by , directs queries to the appropriate regional LIDB by identifying the current carrier for a ported number. The names themselves originate from registrations at the time of activation, where subscribers provide details to be linked to their line information. CNAM databases in face significant scalability challenges due to the high volume of daily telephone traffic, with hundreds of millions of calls triggering name lookups. Vendors like , through their NPAC oversight, help mitigate these by optimizing portability data flows, while carriers employ caching and load balancing to handle query loads without issues. This infrastructure ensures reliable performance across regional databases, supporting the system's role in caller identification.

Protocol and Transmission Details

Calling Name Presentation (CNAP) relies on appropriate signaling protocols depending on the network type. In traditional circuit-switched networks using Signaling System No. 7 (SS7), the Transaction Capabilities Application Part (TCAP) facilitates database queries to retrieve caller name information. In SS7, a Service Switching Point (SSP) initiates a CNAP query by sending a TCAP Invoke component embedded within an SCCP Unitdata message to a Signal Control Point (SCP) hosting the name database. The Invoke component specifies the operation code for the CNAP query, including the calling party number as the key parameter, prompting the SCP to perform the lookup. In 3GPP mobile networks, similar queries use the Mobile Application Part (MAP) over TCAP for supplementary services in GSM/UMTS. Upon successful retrieval, the SCP responds with a TCAP Return Result (Last) component containing the name data, which is routed back via SS7 to the terminating switch for display before the call rings. For (VoIP) environments, including (IMS), the (SIP) handles name presentation through extensions in the P-Asserted-Identity header, as defined in RFC 3325 for trusted networks. This header carries the caller's verified identity, including the display name derived from a name database query, in the format of a SIP URI with a "display-name" (e.g., "John Doe" sip:[email protected]). To ensure privacy and security during transmission, SIP implementations typically encrypt the P-Asserted-Identity header using (TLS), preventing interception in untrusted segments of the network. Application servers or proxies query the name database and populate or update the header before forwarding the INVITE message to the recipient. Transmission of CNAP data faces challenges related to and cross-network , particularly in ensuring the name appears on the recipient's before the first , ideally within under 2 seconds from query initiation. In SS7 networks, this requires efficient to minimize delays in TCAP exchanges, while international calls leverage Translation (GTT) in the SCCP layer to resolve the destination across national boundaries by translating the caller's (e.g., number) into a routing point code. GTT enables seamless query handling in multinational scenarios, such as , by directing the Invoke message to the appropriate regional name service without requiring direct point code knowledge. Error handling in CNAP transmission prioritizes call completion, with fallback mechanisms to display only the calling number if the name query fails, such as due to network congestion or database unavailability. In SS7, a TCAP Reject component may be returned for protocol errors or timeouts, triggering the switch to proceed with number-only presentation via the Initial Address Message (IAM). Similarly, in SIP, if the CNAP lookup yields no result or encounters a failure, the P-Asserted-Identity header defaults to an empty display name, ensuring the phone number remains visible to the recipient. This approach maintains service reliability without interrupting the call setup process.

Global Adoption and Variations

Implementation in the United States

In the United States, Calling Name Presentation (CNAP), commonly referred to as Caller Name (CNAM), operates through a distributed of databases maintained by carriers, with no single centralized national repository for all phone numbers. Carriers query these databases, including regional Line Information Databases (LIDB), to retrieve and display the associated name during incoming calls. For toll-free numbers, has managed the TFNIdentity database since 2017, providing a dedicated repository for CNAM records to ensure consistent name delivery across networks. Users can of CNAM transmission on a per-call basis by dialing the *67 before the phone number, which blocks both the caller ID number and name from appearing on the recipient's . CNAM enjoys widespread adoption in the , with major carriers supporting name delivery for the vast majority of landline and calls, enabling integration with services. For instance, Verizon's Call Filter Plus service incorporates CNAM to display caller names alongside spam screening and blocking features, enhancing user trust in legitimate calls. Key regulatory milestones have shaped CNAM's deployment. In 1993, the (FCC) mandated that telephone carriers offer services including name delivery, establishing CNAM as an essential component of call identification under rules adopted in CC Docket No. 91-281. More recently, following the 2019 FCC order, (VoIP) providers have been required to implement protocols to authenticate caller identities, which verifies the legitimacy of CNAM data and reduces spoofing risks in IP-based networks. Despite its prevalence, CNAM suffers from accuracy challenges due to unverified and outdated entries in carrier databases, leading to frequent mismatches between displayed names and actual callers. The FCC has noted that these databases are "incomplete and unreliable," prompting ongoing efforts to improve verification through integration.

Recent Developments in India

In September 2025, the (DoT) sent a back-reference to the (TRAI) regarding its February 2024 recommendations on introducing Calling Name Presentation (CNAP) in Indian telecommunication networks, prompting TRAI to issue a detailed response on October 28, 2025, affirming the path for implementation. This response aligned with DoT's views on enabling CNAP by default, with pilots commencing shortly thereafter by major telecom operators including , , and in select circles. The pilots, initiated in October 2025 in northern regions such as the circle, focus on testing the service's functionality for and networks, excluding users initially, with live trials aimed at verifying seamless name display during calls. As of November 2025, trials have expanded to involving Airtel, alongside ongoing pilots in Haryana by , , and . A full pan-India rollout is targeted for completion by March 31, 2026, covering approximately 1.1 billion mobile subscribers to enhance call transparency and combat and . The verification process for caller names under CNAP relies on linking the registered name to the subscriber's (KYC) details, authenticated through official identification documents such as during SIM issuance or updates, ensuring authenticity without requiring real-time checks. Telecom service providers maintain centralized Calling Name (CNAM) databases populated with these verified details, which the terminating network queries in real-time via signaling protocols to display the name on the recipient's . While not directly integrated with the (DLT) platform used for SMS regulation, the system draws on similar KYC principles to prevent misuse, with names for or telemarketer numbers required to reflect the entity registered with the TRAI-D7 platform. During the pilot phase, testing is confined to specific areas like and to evaluate network integration and user experience, with operators reporting successful trials in displaying verified names for incoming calls across networks. Upon nationwide deployment, CNAP will be activated by default for all users, offering an option, and provided free of charge to consumers, with telecom operators bearing the implementation and operational costs. For businesses, participation is mandatory, requiring them to register accurate entity names to facilitate identification and reduce fraudulent calls disguised as legitimate promotions. This approach positions CNAP as a key tool in India's anti-spam ecosystem, complementing existing measures like the .

Usage in Other Regions

In the , Calling Name Presentation (CNAP) has been mandated by the Telecommunications and Digital Government Regulatory Authority (TDRA) since June 2021, requiring all mobile devices operating on UAE networks to support the service for displaying the caller's registered name during incoming calls. Major providers du and have implemented CNAP nationwide, achieving 100% coverage across , , , VoLTE, and networks, primarily for commercial entities to combat by showing names as registered on trade licenses or establishment cards. The service supports names, aligning with local trade documentation, and limits displayed names to up to 25 characters for clarity on recipient screens. In , CNAP implementations adhere to EU (GDPR) requirements through GSMA-endorsed standards, ensuring privacy safeguards like consent for data processing in supplementary services. In the , BT's Caller Display service provides name presentation alongside numbers for incoming calls, integrated into and digital voice systems to help users identify callers, though names rely on network databases or user-linked directories. In , Telefónica's network supports caller name display as part of its caller ID features, allowing verified business names to appear on compatible devices while complying with data protection rules that restrict unverified personal information sharing. Across the region, introduced caller ID services in 2003, with name display features for government and entities developing in subsequent years through centralized databases managed by operators like and . In , CNAP remains a limited opt-in service offered by providers such as and , where users must activate name display features on compatible devices, often drawing from listings or verified registrations, but without mandatory nationwide coverage due to privacy preferences. Globally, CNAP aligns with specifications (e.g., TS 23.096) to facilitate cross-border calls by standardizing name transmission in SS7 and IMS protocols, allowing interoperability where networks support the supplementary service. However, in developing regions, adoption faces challenges from inadequate infrastructure, such as limited SS7 upgrades or inconsistent database integration, hindering reliable name delivery and exacerbating risks in areas with fragmented networks.

Regulatory and Privacy Aspects

In the United States, the regulates Calling Name Presentation (CNAP), also known as Caller Name (CNAM), under 47 CFR Part 64, which outlines miscellaneous rules for common carriers including requirements for accurate transmission of caller identification information by voice service providers. These rules mandate that providers offering services support CNAM to ensure reliable name delivery, with recent 2025 proposals aiming to require terminating providers to transmit verified caller name data alongside . Additionally, the Truth in Caller ID Act of 2009 prohibits the transmission of misleading or inaccurate caller identification, including names, with intent to defraud, cause harm, or obtain value wrongfully, applying to both voice and VoIP services. In , the (TRAI) issued guidelines in 2024, with government responses in October 2025, mandating the introduction of CNAP as a supplementary service to display verified caller names, integrated with the Customer Preference Registry (NCPR) for control and customer verification. CNAP must be enabled by default on and networks, with originating providers responsible for supplying accurate name data from centralized databases, and a phased rollout starting with circuit-switched networks before transitioning to signaling-based delivery. Non-compliance with these TRAI directives, including failure to implement CNAP or report progress, incurs penalties under Section 29 of the Telecom Regulatory Authority of India Act, 1997, with fines up to ₹1 and an additional ₹1 for every day of continuing contravention. Internationally, the - Telecommunication Standardization Sector () provides recommendations for CNAP through Recommendation I.251.9 (1996), which defines calling name identification presentation as a supplementary service allowing the called party to receive the caller's name at call setup, alongside number identification, using standardized signaling procedures. In the , adaptations of the (2002/58/) govern CNAP by requiring member states to ensure caller line identification services, including names derived from telephone numbers, are offered with safeguards, prohibiting unconsented disclosure of like names in communications . Opt-out provisions for suppressing caller name display vary by to protect . In the , subscribers have a free legal right to request suppression of their name in CNAM databases through their carrier, enforced under FCC privacy rules without additional charges. In contrast, some EU nations implement opt-out options under the to suppress name display, typically provided free of charge, depending on national regulations, to balance service provision with data protection.

Privacy Implications and Protections

The revelation of a caller's name through Calling Name Presentation (CNAP) can enable doxxing or by exposing personal identities to unwanted parties, potentially exacerbating risks for vulnerable individuals such as of who rely on for safety. CNAM databases, which store linked phone numbers and names, hold sensitive that makes them attractive targets for cyberattacks, with privacy experts highlighting the potential for unauthorized access leading to identity theft or targeted abuse if breached. Although no large-scale public CNAM-specific breaches have been widely reported, the decentralized nature of these databases amplifies vulnerability, as inconsistent security practices across providers could expose millions of records in a single incident. To mitigate these risks, several built-in protections exist within CNAP systems. , callers can activate per-call blocking using the *67 , which prevents transmission of both phone number and name to the recipient, thereby preserving without additional fees or permanent settings. For data transmission, modern implementations employ encryption protocols such as (TLS) for signaling queries that retrieve CNAM information over IP networks, ensuring that name data remains protected during transit from potential interception. In Europe, compliance with the General Data Protection Regulation (GDPR) mandates explicit consent for processing like caller names, treating such information as identifiable that requires lawful basis, data minimization, and user rights to access or erasure. Ethical debates surrounding CNAP center on balancing benefits against erosion, with proponents arguing it empowers recipients to avoid unknown callers while critics contend it infringes on the caller's right to communication, potentially chilling expression. Studies indicate that enhanced caller reduces unwanted calls by improving in displayed and deterring spoofing, with U.S. consumers reporting higher answer rates for verified names, yet this comes at the cost of heightened perceptions that may discourage legitimate calls from -conscious users. Research from the early 1990s highlighted these tensions, finding that while CNAP aids in curbing for some, it disproportionately burdens those seeking , such as informants or activists, without adequate safeguards. Telecommunications providers implement mitigation strategies like regular audits of CNAM databases to ensure with standards, including reviews of data access logs and vulnerability assessments under frameworks like (CPNI) rules. Additionally, controls allow individuals to or correct their associated names in CNAM records through provider portals, enabling proactive management of displayed information to prevent outdated or erroneous from circulating. These measures, combined with options under legal frameworks, help address gaps while maintaining CNAP's utility.

Benefits and Limitations

Advantages for Users

Calling Name Presentation (CNAP) offers substantial advantages for users by reducing calls through the display of verified caller names, which deters fraudulent activities and enables recipients to screen incoming calls more effectively. In regions like , where and calls have proliferated, ongoing CNAP pilots conducted by operators aim to curb this issue by providing transparent caller , with a nationwide rollout targeted for 2026. This process, tied to customer records, minimizes the success of impersonation tactics commonly used in s, such as fake or alerts. The service enhances user safety by simplifying the identification of legitimate callers, including essential contacts like healthcare providers or delivery personnel, thereby lowering the risks associated with unknown numbers. By presenting authenticated names in , CNAP reduces incidents of where callers pose as authorities, allowing users to make secure choices without additional verification steps. This is particularly beneficial in high-risk scenarios, such as avoiding attempts that exploit caller anonymity. CNAP improves convenience for everyday call management, as users can quickly decide whether to answer based on the displayed name, streamlining interactions and reducing interruptions from unwanted calls. This feature integrates seamlessly with modern devices, including smart home systems, to provide contextual alerts that enhance overall user experience without relying on external applications. From an economic perspective, CNAP benefits users indirectly by fostering trusted communications that lower the societal costs of , while businesses experience reduced outreach expenses due to higher engagement rates from verified calls. This leads to more efficient customer interactions, potentially decreasing the need for follow-up attempts and supporting broader in .

Challenges and Criticisms

One major challenge with Calling Name Presentation (CNAP) systems lies in their accuracy, as Caller Name Identification (CNAM) databases often contain outdated or incorrect information, leading to misleading displays for recipients. For instance, when telephone numbers are ported between carriers, the associated name in the CNAM database may not update promptly, resulting in the wrong name appearing on incoming calls. This issue contributes to low consumer trust, with a 2024 Numeracle study finding that 85% of U.S. consumers rarely trust information due to such inaccuracies. Implementation barriers further hinder widespread adoption, particularly in developing regions where challenges for operators pose significant obstacles. Additionally, network latency in rural areas exacerbates these problems, as CNAP relies on rapid database lookups that can be delayed by poor connectivity, leading to incomplete or slow name displays. CNAP is applicable only to and networks, excluding users and limiting its effectiveness in areas with legacy infrastructure. Criticisms of CNAP often center on implications, as the service can involuntarily reveal personal information to recipients, even for non-spam callers who prefer . operators in have raised concerns that default CNAP disclosure, which raises concerns as it shares KYC-verified names unless opted out, potentially exposing individuals to unwanted tracking or . In regions with weaker data protection laws, such as some authoritarian regimes, there is potential for abuse, where governments could leverage CNAP data for or to suppress by monitoring call patterns and identities. Looking ahead, CNAP faces hurdles in adapting to emerging technologies like , which requires enhanced security to prevent cross-slice attacks that could compromise name verification integrity. The rise of AI-generated calls, which use synthetic voices to mimic legitimate callers, further challenges CNAP's effectiveness, as traditional name displays may not distinguish between human and automated origins. Industry and regulatory bodies have called for improved verification standards, such as mandatory authenticated caller names under frameworks like , to address these gaps and ensure reliability.

References

  1. [1]
    TS 22.096 (3Q25/12 p.) – CNAP: Calling Name Presentation
    Provides for the ability to indicate the name information of the calling party to the called party at call set-up time for all incoming calls.
  2. [2]
    [PDF] TECHNICAL SPECIFICATION Calling Name Presentation
    May 26, 2021 · Calling Name Presentation (CNAP). The CNAP supplementary service provides for the ability to indicate the name information of the calling party.
  3. [3]
    Decoding Caller ID, CNAM, or RCD - Numeracle
    Mar 15, 2022 · CNAM stands for “Caller Name,” also known as “Caller Name Presentation (CNAP).” It is a feature used in US-based telephone networks to display ...
  4. [4]
    [PDF] Recommendations on Introduction of Calling Name Presentation ...
    Oct 28, 2025 · This supplementary service provides the ability to indicate the name information of the calling party to the called party at call set-up time.
  5. [5]
    India could get official caller ID by March 2026: What is CNAP and ...
    Oct 31, 2025 · India's telecom regulator has approved Calling Name Presentation (CNAP) - a verified caller ID system that will show the names from the caller's ...
  6. [6]
    The Caller Name Presentation - CNAP
    Implementation Phases: Phase 1: CNAP will be enabled for all corporate fixed-line numbers across public, private, and non-profit sectors. Phase 2: CNAP will ...
  7. [7]
    What is CNAP Feature in Telecom? - Ziwo
    Nov 17, 2021 · Calling Name Presentation (CNAP) is used in telephone networks to identify the caller's name and it's commonly displayed in the Caller ID section whenever ...Cnap In Simple Words · What's The Impact Of This On... · How Can I Set Up My Cnap?<|control11|><|separator|>
  8. [8]
    Caller Name Delivery (CNAM) - DIDWW Documentation!
    Caller Name Delivery (CNAM) is a telecommunication feature that provides the calling party's name information to the recipient.
  9. [9]
    What Is CNAM? Caller ID Name & Lookup - Bandwidth
    CNAM means Caller ID Name, and is the name associated with an incoming phone number. This is also called Caller Name Presentation (CNAP).Missing: Delivery | Show results with:Delivery
  10. [10]
    CNAM (Caller Name Delivery) — Everything You Need to Know
    Rating 4.3 (2,225) May 26, 2025 · CNAM stands for Caller Name Delivery. It's also known as Caller Name Presentation or CNAP. CNAM is a service that links a caller's name to their ...What Does Cnam Mean? · Cnam Best Practices · Setting Up A Cnam With...Missing: telecommunications | Show results with:telecommunications
  11. [11]
    What is CNAP, TRAI's proposed Caller ID service to reduce spam calls
    Mar 12, 2024 · Caller Name Presentation, abbreviated as CNAP, is a service similar to Truecaller that will show the caller's name.Missing: definition | Show results with:definition
  12. [12]
    What is Calling Name Presentation (CNAP)? - Cupola Teleservices
    Oct 15, 2022 · The introduction of CNAP means that your company name will show up on any outbound calls made from your business phone lines to mobile phones.Missing: definition | Show results with:definition
  13. [13]
    How Caller Name Delivery Works + Requirements - NobelBiz
    Jun 26, 2020 · The following is an overview of caller name delivery (CNAM), also known as caller name presentation (CNAP). We're going to go over how it works and what the ...
  14. [14]
    How to Setup Your CNAM for Maximum Deliverability - Kixie
    Rating 4.7 (428) · Free · Business/ProductivityNov 3, 2025 · How It Works (The "CNAM Dip"): Your name is not sent with the call. The recipient's carrier performs a database lookup (a "dip") to find the ...
  15. [15]
    [PDF] OpenSS7 CNAM Query Platform High-Level Design
    Oct 25, 2014 · The traditional architecture for providing CNAM database access is to provide SS7 network con- nectivity between SSPs (local and terminating ...
  16. [16]
    More about Calling Line ID and Calling Party Name - Microsoft Teams
    Apr 8, 2025 · Calling Line ID (CLID) is a phone number, and Calling Party Name (CNAM) is a name. CLID is routed to the destination's carrier, but CNAM may ...
  17. [17]
    Caller ID Name (CNAM) Frequently Asked Questions
    Handling multiple calls in queues · Managing call handling ... If the outbound caller ID is set to. Blocked. , the call recipient will see. UNKNOWN. or. ANONYMOUS.
  18. [18]
    [PDF] Bell-Labs-50th-Anniversary.pdf - World Radio History
    ister- senders and Automatic Number Identi- fication (ANI) -was developed and placed in service in 1943. The close working relationship at Bell Labs between ...
  19. [19]
    Did caller ID get its start in N.J.? We picked up the mystery.
    Dec 18, 2022 · New Jersey Bell, which was then headquartered in Newark, was dabbling in a caller ID-like service as early as 1985. John W. Seazholtz, Bell's ...
  20. [20]
    'Caller ID' Stirs Debate on Phone Privacy - The New York Times
    Feb 11, 1990 · The service, known as Caller ID, was pioneered by New Jersey Bell in 1987. It was made available to customers in New Jersey in December 1988 and ...<|control11|><|separator|>
  21. [21]
    [PDF] CALLER IDENTIFICATION INFORMATION IN SUCCESSOR OR ...
    Jun 22, 2011 · The history of today's Caller ID service goes back to the early 1980s. ... Caller ID Order); Second Caller ID Order, 10 FCC Rcd 11700. 12 47 ...Missing: approval | Show results with:approval
  22. [22]
    [PDF] TAN-008 - MaxLinear
    INTRODUCTION TO CALLER ID. The Caller ID feature is an on-hook capability that provides the user information about the caller before.
  23. [23]
    Is Branded Calling using CNAM Really Dead? - Number Sentry
    Aug 8, 2024 · CNAM is a telephone feature that displays a 15-character name or other information about the originating caller in the caller ID display of the ...Missing: history | Show results with:history
  24. [24]
  25. [25]
    RFC 3261 - SIP: Session Initiation Protocol - IETF Datatracker
    This document describes Session Initiation Protocol (SIP), an application-layer control (signaling) protocol for creating, modifying, and terminating sessions ...
  26. [26]
    [PDF] ETSI TS 123 231 V11.1.1 (2012-11)
    Calling Name Presentation (CNAP) ... [15]. IETF RFC 3261: "SIP: Session Initiation Protocol". [16]. IETF RFC 4028: "Session Timers in the Session Initiation ...
  27. [27]
  28. [28]
    The Basics of Caller ID - RDI Intuitive Technical
    The loose-knit system of CNAM databases used in the U.S. can take days to completely update. ... Instead, you use your local provider to update the CNAM value ...2. Caller Id -- The Basics · 2.2 - The Cnam (caller Id... · 3.2 - Caller Id Mobile...
  29. [29]
  30. [30]
    EZCNAM: CNAM Data Provider | Affordable CNAM API & Caller ID ...
    Your Choice for CNAM is EZ. Lowest pricing around: $0.003 (3/10 penny) each! Carrier-grade data - highly accurate, never cached. No minimum volume commitments ...
  31. [31]
    CNAM, E911 & RoboCall Solutions | Bulk Solutions, LLC
    CNAM. $0.002. per query ; OUTBOUND CALLS. $0.004. per minute ; MESSAGING (SMS). $0.003. as low as per message.
  32. [32]
    [PDF] Attachment 2 Exhibit B, Page 1 of 3 Pages KY 7/25/00 CALLING ...
    Jul 25, 2000 · If the customer queries the BellSouth CNAM SCP via a third party national. SS7 transport provider, the third party SS7 provider shall ...
  33. [33]
    Why Traditional Network CNAM Does Not Work Anymore - Trestle
    Oct 21, 2024 · Now, anyone using the CNAM data knows that the typical coverage for actual non-junk (i.e., real/valid) data is around 50%, with an accuracy of ...
  34. [34]
    NPAC - Number Portability Administration Center - iconectiv
    Find out which companies can access the country's Number Portability Administration Center (NPAC) database and for what purposes. Download. Complying with ...Missing: CNAM | Show results with:CNAM
  35. [35]
    What is CNAM? Everything You Need to Know About Caller Name
    CNAM, short for Caller ID Name, is the service that displays the name of a caller alongside their phone number when they make a call.
  36. [36]
    Three Issues with CNAM Data and How They Impact Businesses
    Jun 7, 2023 · According to this blog, people in the U.S. make about 2.9 billion calls per day, but only about 42% of the CNAM data is usable, while 58% of the ...Missing: volume | Show results with:volume
  37. [37]
  38. [38]
  39. [39]
    Wholesale | InterNetwork Calling Name - CenturyLink
    Jan 30, 2017 · The ANSI On Line web site allows you to search for an ANSI Standards documents. There may be charges associated with acquiring ANSI ...
  40. [40]
  41. [41]
    draft-ietf-enum-cnam-00
    The CNAM ENUMservice defined in this document is assumed to be used in an ... [2] ITU-T, "The International Public Telecommunication Number Plan ...
  42. [42]
  43. [43]
  44. [44]
    Global Title Translation (GTT) Overview - Oracle Help Center
    The Global Title Translation (GTT) feature is designed for the signaling connection control part (SCCP) of the SS7 protocol. The EAGLE uses this feature to ...
  45. [45]
    All about Global Title Translation & SCCP Routing
    Oct 25, 2024 · This is how the international SS7 Network used for roaming is structured and addressed – All using Global Title rather than Point Codes.
  46. [46]
    Know Who's Calling Each and Every Time - Somos
    TFNIdentity is a standalone database provided by Somos, storing CNAM records specifically for Toll-Free Numbers. CNAM data is constantly updated and ...Missing: 2017 | Show results with:2017
  47. [47]
    TFNRegistry: A History of Toll-Free Numbers - Somos
    Jan 27, 2025 · Responsible Organizations can access TFNIdentity to store Caller Name information (frequently referred to as CNAM) so that it can be displayed ...
  48. [48]
    Caller ID Blocking (*67) for home phone - AT&T
    Apr 9, 2025 · Block your number when making a call · At the dial tone, push *67. · Listen for a series of tones, followed by a dial tone for blocking to be ...
  49. [49]
    Verizon Call Filter
    Screen and automatically block spam calls and report unwanted numbers. Upgrade to Call Filter Plus for enhanced protection with features like Caller Name ID, a ...Missing: CNAM | Show results with:CNAM
  50. [50]
    Verizon Call Filter - Apps on Google Play
    Rating 4.7 (518,164) · Free · AndroidWith Call Filter, you can screen incoming calls, auto-block spam and report any unwanted numbers. Or, upgrade to Call Filter Plus with Caller ID for added ...Missing: integration | Show results with:integration
  51. [51]
    [PDF] Federal Communications Commission Record
    On September 23, 1993, we adopted a Notice of Pro posed Rule Making (Notice)1 in which we proposed, inter alia, to establish a procedure by which private land ...<|separator|>
  52. [52]
    Combating Spoofed Robocalls with Caller ID Authentication
    In 2020, the FCC adopted rules requiring voice service providers to implement STIR/SHAKEN in the IP portions of their voice networks by June 30, 2021. Since ...
  53. [53]
    [PDF] October 7, 2025 FCC FACT SHEET* Call Branding FNPRM ...
    Oct 7, 2025 · What the Notice of Proposed Rulemaking Would Do: • Propose to define “caller identity information”. • Propose to require terminating voice ...
  54. [54]
    Avoid unwanted calls with Verizon Call Filter FAQs | Verizon Support
    Call Filter screens incoming callers to alert you if a number may be spam, a robocall or fraud. Call Filter detects spam and blocks high-risk spam calls by ...Using Call Filter & Call Filter... · Call Filter · How to get and use Verizon...Missing: CNAM integration
  55. [55]
    DoT sets March 2026 deadline for pan-India rollout of CNAP service
    Oct 29, 2025 · Carriers including Vodafone Idea, Bharti Airtel, and Reliance Jio are conducting pilots in some northern circles, with live tests expected soon.
  56. [56]
  57. [57]
    Telcos begin pilot runs of 'calling name presentation' feature in one ...
    Oct 30, 2025 · Telecom operators are piloting a new feature called Calling Name Presentation. This will allow users to see a caller's name on incoming calls.
  58. [58]
    No more spam calls? Govt plans verified caller ID rollout ... - Mint
    Oct 29, 2025 · Govt plans verified caller ID rollout across India by 2026. The DoT has initiated a pilot for Calling Name Presentation (CNAP), allowing users ...
  59. [59]
    Access Alert: TRAI recommends the Introduction of Calling Name ...
    Under TRAI's recommendations, number series allocated for businesses or telemarketers making calls to subscribers must display the name of calling entity.
  60. [60]
    Haryana: Jio, Vi begin caller name pilot, nationwide rollout expected ...
    Oct 30, 2025 · Haryana: Jio, Vi begin caller name pilot, nationwide rollout expected by March 2026. The pilot will display the caller's verified name from ...
  61. [61]
    TRAI Approves CNAP - Verified Caller ID Coming Soon | SCC Times
    Nov 1, 2025 · Calling Name Presentation ('CNAP') is a supplementary telecom service that enables the called party to see the verified name of the caller, ...Missing: history | Show results with:history
  62. [62]
    CNAP - PIB
    Oct 28, 2025 · The Telecom Regulatory Authority of India (TRAI) has today issued its response to the back-reference dated 26.09.2025, received from the ...
  63. [63]
  64. [64]
    Caller Identification Feature "Kashif" (CNAP/Caller ID) - Etisalat
    CNAP/Kashif is a mandatory caller ID for commercial entities in the UAE, displaying their name to combat spam and fraud. It is not for consumers.Missing: du 2022 Arabic<|separator|>
  65. [65]
    What is Caller Name Presentation (CNAP)? - Mobile Services - Du
    CNAP is a Caller Presentation feature, mandated by TDRA for commercial entities in UAE to display the registered entity's name, as appears on their trade ...Missing: Etisalat 2022 Arabic
  66. [66]
    [PDF] ETSI TS 123 096 V15.0.0 (2018-07)
    Calling Name Presentation (CNAP) ... The present document describes name identification supplementary services (stage 2) within the 3GPP system.
  67. [67]
    All about Caller Display | BT Help
    Caller Display shows you the number of the person calling, so you can decide whether to pick up the phone or leave it to your answering service.Missing: presentation GSMA
  68. [68]
    Caller ID | O₂ Community
    Jan 11, 2021 · According to your wish, I have now changed the settings so that when you call another person, your Caller ID will be shown to the other person.
  69. [69]
    Method and system for displaying calling area name in identification ...
    Provides the calling area name display service system in the integrated environment of identification number. 본 발명의 제 4 목적에 의하면, 이동통신 식별번호를 ...
  70. [70]
    Manage caller ID on my mobile service - Telstra.com
    Learn how caller ID works and choose when you hide your number with Telstra's step-by-step instructions.
  71. [71]
    Manage mobile phone number display settings (Caller ID) - Optus
    In this article, we'll show you how to turn your Caller ID settings on and off. This includes: See who's calling: Making the phone number of incoming calls ...
  72. [72]
    Calling name display - Optus - Whirlpool Forums
    Nov 10, 2020 · Noticed recently on Optus that incoming calls sometimes display caller's name or Company name. This must be sent from network as these are ...Caller name ID? - TelstraCNAM - Caller ID Name in Australia????More results from forums.whirlpool.net.au
  73. [73]
    [PDF] sp-99479.pdf - 3GPP
    Oct 13, 1999 · TS 22.096: "Calling Name Presentation (CNAP) - Stage 1". [194]. GSM ... precautions to ensure that cross border coverage is minimized in adjacent ...
  74. [74]
    Inter-PLMN Mobility Management Challenges for Supporting Cross ...
    Jun 8, 2021 · The work presented in this study attempts to analyse the requirements for cross-border CAM operation for the five main CAM use cases selected by 3GPP.Missing: CNAP | Show results with:CNAP
  75. [75]
    Non-Terrestrial Networks - Opportunities and Challenges - GSMA
    Jun 11, 2025 · This paper explores the transformative potential of Non-Terrestrial Networks (NTN) as a vital complement to terrestrial mobile infrastructure.
  76. [76]
    47 CFR Part 64 -- Miscellaneous Rules Relating to Common Carriers
    § 64.401 Policies and procedures for provisioning and restoring certain telecommunications services in emergencies.Missing: CNAM | Show results with:CNAM
  77. [77]
    Trai aligns with DoT on CNAP, makes caller ID service default with ...
    Oct 28, 2025 · Trai aligns with DoT on CNAP, makes caller ID service default with opt-out. Trai's backing clears path for nationwide CNAP rollout; feature to ...Missing: consumers | Show results with:consumers
  78. [78]
    Trai proposes steeper fines for telcos that don't report new plans and ...
    Oct 16, 2025 · Currently, if any service provider fails to comply with the reporting requirement, they are liable to pay ₹5,000 for every day of delay, up to a ...
  79. [79]
    I.251.9 : Number identification supplementary services - ITU
    Recently posted - Search Recommendations. I.251.9 : Number identification supplementary services : Calling name identification presentation. Recommendation I.
  80. [80]
    Stop Unwanted Robocalls and Texts | Federal Communications ...
    Mar 3, 2025 · To block telemarketing calls, register your number on the Do Not Call List. Legitimate telemarketers consult the list to avoid calling both ...Caller ID Authentication · FCC Expands Use of Tool to... · Do-not-call
  81. [81]
    EUROPE STARTS TO TACKLE CALLER ID - Tech Monitor
    Feb 28, 1991 · In the meantime legislation is up to member states. The systems are banned in France and Germany, but in UK the situation is described as vague ...
  82. [82]
    Abuse Using Technology: Spoofing | WomensLaw.org
    This law prohibits falsifying or spoofing caller ID to do any of the following: to cheat or trick someone out of something (defraud);; to cause harm; or; to ...
  83. [83]
    [PDF] Preserving Privacy in Caller ID Applications - Hal-Inria
    In this paper we investigate two Caller ID applications,. Truecaller and Everybody, and compliance of their privacy policies with the data privacy laws, ...Missing: adaptations | Show results with:adaptations
  84. [84]
    Protecting Your Privacy: Phone and Cable Records
    Dec 30, 2019 · FCC rules require telemarketers to display on caller ID either their phone numbers and, if possible, their names, or the name of the company ...
  85. [85]
    Cisco Preferred Architecture for Enterprise Collaboration 11.6, CVD
    Feb 6, 2017 · TLS is mainly used to encrypt call control signaling; for example, with SIP signaling between endpoints and Unified CM servers or in SIP trunks.
  86. [86]
    Personal Data - General Data Protection Regulation (GDPR)
    Rating 4.6 (10,111) Personal data are any information which are related to an identified or identifiable natural person. The data subjects are identifiable if they can be directly ...
  87. [87]
    Caller ID and the meaning of privacy - Taylor & Francis Online
    This article explores privacy in the context of the Caller ID debate from a social science perspective. It examines motives for seeking and preserving privacy.Missing: impact | Show results with:impact
  88. [88]
    An inquiry into the privacy aspects of caller-ID - ScienceDirect
    A study was conducted to determine the balance between the advantages and disadvantages of caller-ID from a user perspective. A questionnaire exploring the ...
  89. [89]
    Why Telecommunications Companies Must Strengthen Data Privacy ...
    Oct 10, 2025 · Our services include: CPNI compliance audits; Privacy and breach reporting protocol development; Vendor and partner data-sharing assessments
  90. [90]
    CNAM Services | Caller ID Management - Bandwidth
    When you receive a call, your carrier queries a CNAM database to retrieve the associated name. However, not all carriers support CNAM and mobile networks are ...Missing: SS7 | Show results with:SS7
  91. [91]
    India's Verified Caller ID: A New Dawn in the Fight Against Spam ...
    Oct 29, 2025 · Compared to previous digital milestones, CNAP is a significant step towards a government-regulated, standardized approach to caller ...
  92. [92]
  93. [93]
    2G users to miss out as caller ID to curb spam calls nears rollout - Mint
    Oct 28, 2025 · The caller ID feature, which the DoT will notify, aims to help users identify unidentified callers, make an informed decision about whether ...
  94. [94]
    CRA Launches Caller Name Presentation Initiative to Enhance Trust ...
    Oct 15, 2025 · The new service enables call recipients to identify the official, verified name of the calling entity before answering, allowing them to ...Missing: Korea 2010 Australia
  95. [95]
    Key Benefits of Calling Name Presentation Service - Oxyvin
    The Calling Name Presentation Service is designed to let users see the name of a caller before answering the phone, much like a caller ID service but with a ...Missing: definition | Show results with:definition
  96. [96]
    [PDF] Federal Communications Commission FCC 25-76
    Oct 29, 2025 · In this Notice, we propose to require that providers give consumers accurate caller name and other information that enables them to regain ...
  97. [97]
    Fix Incorrect Caller ID Name - Numeracle
    May 15, 2025 · Free or very low cost to update, CNAM is rudimentary and doesn't give enterprises any real control over how business names appear on Caller ID.
  98. [98]
    US Consumers Want More Accurate Caller ID - Numeracle
    Sep 12, 2024 · A recent study by Numeracle reveals that 85% of U.S. consumers rarely trust caller ID, with 69% missing important calls due to unverified ...Missing: error FTC
  99. [99]
    CNAP: A Comprehensive Overview of India's Caller Name ...
    Aug 16, 2025 · ... Calling Name Presentation (CNAP). This initiative aims to address ... Cost of Implementation: The cost of implementing and maintaining ...
  100. [100]
    TRAI, DoT clear default CNAP rollout for 4G, 5G users
    Oct 29, 2025 · ... Calling Name Presentation (CNAP) feature by default for subscribers, starting with 4G and 5G networks. This move is designed to combat fraud ...
  101. [101]
    Telecom operators flag privacy issues with TRAI's caller ID proposal
    Jan 18, 2023 · Telecom operators have expressed concerns over user privacy on the Telecom Regulatory Authority of India's Calling Name Presentation (CNAP) ...
  102. [102]
    TRAI-caller? We tell TRAI why a central registry is a bad idea.
    Jan 9, 2023 · Given the privacy concerns with the CNAP service, the use of it can potentially violate an individual's privacy by disclosing their name to the ...
  103. [103]
    5G Network Slicing: Security Challenges, Attack Vectors, and ... - MDPI
    This paper examines the vulnerabilities of network slicing and proposes mitigation strategies to strengthen its protection in 5G networks.
  104. [104]
    What Is An AI-Generated Call? - Klein Moynihan Turco
    Apr 10, 2025 · The FCC proposes to define an “AI generated call” as “a call that uses any technology or tool to generate an artificial or prerecorded voice or a text.
  105. [105]
    FCC Proposes Tougher Standards for Call Labeling and Foreign ...
    Nov 4, 2025 · The FNPRM proposes to require terminating providers to display caller identity information (at minimum, a verified personal or business name if ...