{"description":"Documents matching 'correct notify callers when calls'","count":533,"total_pages":27,"next_page_url":"https://www.federalregister.gov/api/v1/documents?conditions%5Bterm%5D=correct+notify+callers+when+calls&format=json&page=2","results":[{"title":"Enhancing Know-Your-Upstream-Provider Requirements and Strengthening STIR/SHAKEN (Call Authentication Trust Anchor; Advanced Methods To Target and Eliminate Unlawful Robocalls)","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) proposes steps to strengthen its robocall mitigation framework by enhancing Know-Your-Upstream-Provider (KYUP) requirements, improving oversight of voice service providers by the STIR/SHAKEN Governance Authority, raising caller ID attestation standards, and closing implementation gaps in STIR/SHAKEN implementation. Specifically, the Commission proposes establishing baseline KYUP information-collection, compliance review, verification, monitoring, and responsive-action requirements to ensure providers can identify and cut off bad-actor upstream providers. The Commission also proposes measures to expand the Governance Authority's vetting, enforcement, and reporting responsibilities to prevent misuse of STIR/SHAKEN certificates and to remove noncompliant providers from the authentication ecosystem. The Commission further proposes clarifying and strengthening STIR/SHAKEN attestation rules, including codifying attestation levels, defining improper attestations, and specifying permissible mechanisms for verifying number-to-customer associations. Additionally, the Commission proposes and seeks comment on additional steps to close caller ID authentication gaps, such as refining provider definitions, reconsidering exemptions, requiring providers serving end users to assign STIR/SHAKEN attestations, and ensuring calls maintain authentication information. The Commission also seeks comment on special circumstances, including addressing issues with foreign- originated calls.","document_number":"2026-13874","html_url":"https://www.federalregister.gov/documents/2026/07/09/2026-13874/enhancing-know-your-upstream-provider-requirements-and-strengthening-stirshaken-call-authentication","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-07-09/pdf/2026-13874.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-13874.pdf?1783514714","publication_date":"2026-07-09","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"“full”) attestation <span class=\"match\">when</span> it (1) is responsible for the origination of the <span class=\"match\">call</span> onto the IP network, (2) has a direct authenticated relationship with its customer and can identify the customer, and (3) has established a verified association between its customer and the telephone number used for the <span class=\"match\">call</span>. It may assert B-level (or “partial”) attestation <span class=\"match\">when</span> it can satisfy elements (1) and (2), but not (3). It must assert C-level (or “gateway”) attestation <span class=\"match\">when</span> the provider has no relationship with the originator of a <span class=\"match\">call</span>, such as <span class=\"match\">when</span> a provider is acting"},{"title":"Location-Based Routing for Wireless 911 Calls","type":"Rule","abstract":"The Federal Communications Commission (the FCC or Commission) adopted a Report and Order in PS Docket No. 18-64, FCC 24-4, on January 25, 2024, and released on January 26, 2024. This document is a summary of the Commission's Report and Order. The Report and Order adopted rules to more precisely route wireless 911 calls and Real-Time Texts (RTT) to Public Safety Answering Points (PSAPs), which can result in faster response times during emergencies. Wireless 911 calls have historically been routed to PSAPs based on the location of the cell tower that handles the call. Sometimes, however, the 911 call is routed to the wrong PSAP because the cell tower is not in the same jurisdiction as the 911 caller. This can happen, for instance, when an emergency call is placed near a county border. These misrouted 911 calls must be transferred from one PSAP to another, which consumes time and resources and can cause confusion and delay in emergency response. The Report and Order requires wireless providers to deploy technology that supports location-based routing, a method that relies on precise information about the location of the wireless caller's device, on their internet Protocol (IP)-based networks and to use location-based routing to route 911 voice calls and RTT communications to 911 originating on those networks when caller location is accurate and timely. The Report and Order provides six months for nationwide wireless providers to implement location-based routing for wireless 911 voice calls and provides 24 months for non-nationwide wireless providers to implement location-based routing of wireless 911 voice calls. The Report and Order provides 24 months for all wireless providers to implement location-based routing for RTT communications to 911.","document_number":"2024-03157","html_url":"https://www.federalregister.gov/documents/2024/03/13/2024-03157/location-based-routing-for-wireless-911-calls","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-03-13/pdf/2024-03157.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-03157.pdf?1709932520","publication_date":"2024-03-13","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"precisely route wireless 911 <span class=\"match\">calls</span> and Real-Time Texts (RTT) to Public Safety Answering Points (PSAPs), which can result in faster response times during emergencies. Wireless 911 <span class=\"match\">calls</span> have historically been routed to PSAPs based on the location of the cell tower that handles the <span class=\"match\">call</span>. Sometimes, however, the 911 <span class=\"match\">call</span> is routed to the wrong PSAP because the cell tower is not in the same jurisdiction as the 911 <span class=\"match\">caller</span>. This can happen, for instance, <span class=\"match\">when</span> an emergency <span class=\"match\">call</span> is placed near a county border. These misrouted 911 <span class=\"match\">calls</span> must be transferred from"},{"title":"Advanced Methods To Target and Eliminate Unlawful Robocalls","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) modifies its existing call blocking rules. Specifically, the Commission requires all domestic voice service providers to block based on a reasonable do-not-originate (DNO) list. Second, it requires voice service providers to return Session Initiation Protocol (SIP) code 603+ when calls are blocked based on reasonable analytics.","document_number":"2025-04811","html_url":"https://www.federalregister.gov/documents/2025/03/24/2025-04811/advanced-methods-to-target-and-eliminate-unlawful-robocalls","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-03-24/pdf/2025-04811.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-04811.pdf?1742561117","publication_date":"2025-03-24","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"notification to <span class=\"match\">callers</span> <span class=\"match\">when</span> <span class=\"match\">calls</span> are blocked based on reasonable analytics. The Commission now requires the exclusive use of SIP code 603+ for this purpose on IP networks. The Commissions directs providers that block based on reasonable analytics to return SIP code 603+. This will ensure that <span class=\"match\">callers</span> learn <span class=\"match\">when</span> and why their <span class=\"match\">calls</span> are blocked based on reasonable analytics, which in turn will allow these <span class=\"match\">callers</span> to access redress <span class=\"match\">when</span> blocking errors occur. The Commission clarifies that this requirement only applies <span class=\"match\">when</span> providers block <span class=\"match\">calls</span> based on"},{"title":"Internet-Based Telecommunications Relay Service Modernization","type":"Proposed Rule","abstract":"The Federal Communications Commission (Commission) proposes to modernize its telecommunications relay services (TRS) rules and seeks comment on the use of automatic speech recognition (ASR) for speech-to- text conversion and advanced text-to-speech technologies for Internet Protocol (IP) Relay Service; the need for metrics for IP Relay quality; the compatibility of IP Relay with Real-Time Text (RTT) technology; adding captioning functionality to Video Relay Service (VRS) platforms; amending VRS calling rules for calls to U.S. embassies and consulates by U.S. residents while traveling abroad; adjusting VRS call center requirements; streamlining TRS provider certification and user registration processes; updating or eliminating obsolete rules; and closing outdated dockets. With these proposals, the Commission presents targeted reforms that align internet-based TRS with twenty-first century technological advancements in relay services that can better serve the needs of persons with disabilities while securing the viability and enhancing the effectiveness and functional equivalency of internet-based TRS.","document_number":"2026-05213","html_url":"https://www.federalregister.gov/documents/2026/03/17/2026-05213/internet-based-telecommunications-relay-service-modernization","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-03-17/pdf/2026-05213.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-05213.pdf?1773665121","publication_date":"2026-03-17","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"U.S. residents who are VRS users frequently need to make telephone <span class=\"match\">calls</span> while traveling abroad. The Commission's current rules allow TRS Fund support (after notice to the user's default VRS provider) <span class=\"match\">when</span> such users place <span class=\"match\">calls</span> to the United States, but they do not address compensation for <span class=\"match\">calls</span> placed to other endpoints. Recently, the United States Department of State (State Department) asked the Commission to permit TRS Fund support <span class=\"match\">when</span> VRS users traveling abroad make <span class=\"match\">calls</span> to U.S. embassies and consulates, which have telephone numbers local"},{"title":"Facilitating Implementation of Next Generation 911 Services (NG911); Location-Based Routing for Wireless 911 Calls","type":"Rule","abstract":"In this document, the Federal Communications Commission (the FCC or Commission) adopted a Report and Order to advance the nationwide Next Generation 911 (NG911) transition rules that define the responsibilities and set deadlines for originating service providers (OSPs) to implement NG911 capabilities on their networks and deliver 911 calls to NG911 systems established by 911 authorities. In addition, the rules preserve the authority of state, territorial, regional, Tribal, and local government to adopt alternative approaches to the configuration, timing, and cost responsibility for NG911 implementation within their jurisdictions.","document_number":"2024-18603","html_url":"https://www.federalregister.gov/documents/2024/09/24/2024-18603/facilitating-implementation-of-next-generation-911-services-ng911-location-based-routing-for","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-09-24/pdf/2024-18603.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-18603.pdf?1727095514","publication_date":"2024-09-24","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"Law/RAY BAUM'S Act Order), <span class=\"match\">corrected</span> by Erratum, 34 FCC Rcd 11073 (PSHSB 2019), 85 FR 9390 (Feb. 19, 2020), \n also <span class=\"match\">corrected</span> by \n Second Erratum, 37 FCC Rcd 10274 (PSHSB 2022), 87 FR 60104 (Oct. 4, 2022); \n see \n 47 CFR 9.4, 9.5.\n \n \n \n Legacy 911 <span class=\"match\">Call</span> Routing. \n In legacy E911 systems, 911 <span class=\"match\">calls</span> are typically routed through the use of a wireline network element—<span class=\"match\">called</span> a selective router—to a geographically appropriate PSAP based on the <span class=\"match\">caller's</span> location.\n 18 \n \n The selective router serves as the entry point for wireline 911 <span class=\"match\">calls</span> originated from competitive"},{"title":"Advanced Methods To Target and Eliminate Unlawful Robocalls","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) proposes and seeks comment on a number of actions aimed protecting consumers from illegal calls, restore faith in caller ID, and hold voice service providers responsible for the calls on their networks. Specifically, the notice of proposed rulemaking proposes and seeks comment on several options to combat illegal calls, including: specific call blocking requirements; the correct way to notify callers when calls are blocked based on reasonable analytics; requiring the display of caller name information in certain instances and; a base forfeiture for failure to adopt affirmative, effective measures to prevent new or renewing customers from originating illegal calls. Additionally, the Notice of Inquiry seeks broad comment on tools used by voice service providers to combat illegal calls, such as honeypots, as well as on the status and use of call labeling.","document_number":"2023-13032","html_url":"https://www.federalregister.gov/documents/2023/07/10/2023-13032/advanced-methods-to-target-and-eliminate-unlawful-robocalls","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2023-07-10/pdf/2023-13032.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2023-13032.pdf?1688733914","publication_date":"2023-07-10","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"seeks comment on a number of actions aimed protecting consumers from illegal <span class=\"match\">calls</span>, restore faith in <span class=\"match\">caller</span> ID, and hold voice service providers responsible for the <span class=\"match\">calls</span> on their networks. Specifically, the notice of proposed rulemaking proposes and seeks comment on several options to combat illegal <span class=\"match\">calls</span>, including: \n \n specific <span class=\"match\">call</span> blocking requirements; the <span class=\"match\">correct</span> way to <span class=\"match\">notify</span> <span class=\"match\">callers</span> <span class=\"match\">when</span> <span class=\"match\">calls</span> are blocked based on reasonable analytics; requiring the display of <span class=\"match\">caller</span> name information in certain instances and; a base forfeiture for failure to"},{"title":"Facilitating Implementation of Next Generation 911 Services (NG911); Improving 911 Reliability","type":"Rule","abstract":"In this document, the Federal Communications Commission (the FCC or Commission) adopts rules to ensure that emerging Next Generation 911 (NG911) networks are reliable and interoperable. NG911 is replacing legacy 911 technology across the country with internet Protocol (IP)- based infrastructure that will support new 911 capabilities, including text, video, and data. However, for NG911 to be fully effective, NG911 networks must be designed to safeguard the reliability of critical components and support the interoperability needed to seamlessly transfer 911 calls and data from one network to another. The rules require entities essential to delivering emergency calls in the NG911 environment to implement common sense measures to safeguard the reliability of NG911 networks and reduce the risk of 911 outages, and require certain entities to report on their support for NG911 interoperability. The rules also eliminate unnecessary and burdensome legacy rules to increase flexibility and encourage technical innovation to make NG911 services reliable, interoperable, and accessible to all.","document_number":"2026-13998","html_url":"https://www.federalregister.gov/documents/2026/07/10/2026-13998/facilitating-implementation-of-next-generation-911-services-ng911-improving-911-reliability","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-07-10/pdf/2026-13998.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-13998.pdf?1783601118","publication_date":"2026-07-10","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"\n \n \n Legacy 911 Networks \n \n In 2013, <span class=\"match\">when</span> the Commission adopted the \n 911 Reliability Order, \n the legacy networks of incumbent wireline providers typically connected PSAPs to those seeking help, whether the <span class=\"match\">call</span> for assistance originated on a landline or a wireless phone.\n 37 \n \n In these <span class=\"match\">call</span> flows, OSPs originate and transmit 911 <span class=\"match\">calls</span> placed by their customers, together with information about the <span class=\"match\">callers</span>' locations, to legacy 911 networks, where the <span class=\"match\">calls</span> are collected at an aggregation point <span class=\"match\">called</span> a selective router.\n 38 \n \n The selective"},{"title":"Facilitating Implementation of Next Generation 911 Services (NG911); Improving 911 Reliability","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (the FCC or Commission) proposes rules that would help ensure that emerging Next Generation 911 (NG911) networks are reliable and interoperable. NG911 is replacing legacy 911 technology across the country with Internet Protocol (IP)-based infrastructure that will support new 911 capabilities, including text, video, and data. However, for NG911 to be fully effective, NG911 networks must safeguard the reliability of critical components and support the interoperability needed to seamlessly transfer 911 calls and data from one network to another. When the Commission first adopted 911 reliability rules in 2013, the transition to NG911 was in its very early stages. Since then, many state and local 911 Authorities have made significant progress in deploying NG911 capabilities in their jurisdictions. This Further Notice of Proposed Rulemaking (FNPRM) is the next step in fulfilling the Commission's commitment to facilitate the NG911 transition and to ensure that the transition does not inadvertently create vulnerabilities in the nation's critical public safety networks. The FNPRM proposes to update the definition of \"covered 911 service provider\" in the Commission's existing 911 reliability rules to ensure that the rules apply to service providers that control or operate critical pathways and components in NG911 networks. It also proposes to update the reliability standards for providers of critical NG911 functions to ensure the reliable delivery of 911 traffic to NG911 delivery points, and proposes to establish NG911 interoperability requirements for interstate transfer of 911 traffic between Emergency Services IP Networks (ESInets). In addition, the FNPRM proposes to modify the certification and oversight mechanisms in the current 911 reliability rules to improve reliability and interoperability in NG911 systems while minimizing burdens on service providers, and proposes to empower state and local 911 Authorities to obtain reliability and interoperability certifications directly from covered 911 service providers.","document_number":"2025-09279","html_url":"https://www.federalregister.gov/documents/2025/06/04/2025-09279/facilitating-implementation-of-next-generation-911-services-ng911-improving-911-reliability","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-06-04/pdf/2025-09279.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-09279.pdf?1748954707","publication_date":"2025-06-04","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"Reliability Order \n that the routing of a legacy 911 <span class=\"match\">call</span> is accomplished via an aggregation point <span class=\"match\">called</span> a selective router, which identifies the PSAP that should receive the <span class=\"match\">call</span> based on the <span class=\"match\">caller's</span> phone number and address.\n 69 \n \n The selective router then determines the <span class=\"match\">correct</span> routing path for the <span class=\"match\">call</span> and transmits the <span class=\"match\">call</span>, together with the <span class=\"match\">caller's</span> location and telephone number, to the central office serving the PSAP. Finally, the central office transmits the 911 <span class=\"match\">call</span> and associated <span class=\"match\">caller</span> information to the PSAP, typically along dedicated"},{"title":"Call Authentication Trust Anchor","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) takes further steps to combat illegally spoofed robocalls by strengthening and expanding caller ID authentication and robocall mitigation obligations and creating new mechanisms to hold providers accountable for violations of the Commission's rules.","document_number":"2023-12142","html_url":"https://www.federalregister.gov/documents/2023/06/21/2023-12142/call-authentication-trust-anchor","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2023-06-21/pdf/2023-12142.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2023-12142.pdf?1687265121","publication_date":"2023-06-21","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"relied on in prior <span class=\"match\">caller</span> ID authentication and <span class=\"match\">call</span> blocking orders. \n \n 80. \n <span class=\"match\">Caller</span> ID Authentication. \n The Commission concludes that the same authority through which it imposed <span class=\"match\">caller</span> ID authentication obligations on gateway providers—a subset of intermediate providers—applies equally to its rules that impose <span class=\"match\">caller</span> ID authentication obligations on non-gateway intermediate providers. Specifically, the Commission finds authority to impose <span class=\"match\">caller</span> ID authentication obligations on the first intermediate providers in the <span class=\"match\">call</span> chain under section"},{"title":"Location-Based Routing for Wireless 911 Calls","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (the FCC or Commission) proposes rules to more precisely route wireless 911 calls and texts to Public Safety Answering Points (PSAPs), which can result in faster response times during emergencies. Wireless 911 calls have historically been routed to PSAPs based on the location of the cell tower that handles the call. Sometimes, however, the 911 call is routed to the wrong PSAP because the cell tower is not in the same jurisdiction as the 911 caller. This can happen, for instance, when an emergency call is placed near a county border. These misrouted 911 calls must be transferred from one PSAP to another, which consumes time and resources and can cause confusion and delay in emergency response. The Notice of Proposed Rulemaking (NPRM) proposes to require wireless and covered text providers to deploy technology that supports location- based routing, a method that relies on precise information about the location of the wireless caller's device, on some networks and to use location-based routing to route 911 voice calls and texts originating on those networks when caller location is accurate and timely. In addition, the NPRM proposes to require CMRS and covered text providers to deliver 911 calls, texts, and associated routing information in internet Protocol (IP) format upon request of certain 911 authorities.","document_number":"2023-00519","html_url":"https://www.federalregister.gov/documents/2023/01/17/2023-00519/location-based-routing-for-wireless-911-calls","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2023-01-17/pdf/2023-00519.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2023-00519.pdf?1673617522","publication_date":"2023-01-17","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"more precisely route wireless 911 <span class=\"match\">calls</span> and texts to Public Safety Answering Points (PSAPs), which can result in faster response times during emergencies. Wireless 911 <span class=\"match\">calls</span> have historically been routed to PSAPs based on the location of the cell tower that handles the <span class=\"match\">call</span>. Sometimes, however, the 911 <span class=\"match\">call</span> is routed to the wrong PSAP because the cell tower is not in the same jurisdiction as the 911 <span class=\"match\">caller</span>. This can happen, for instance, <span class=\"match\">when</span> an emergency <span class=\"match\">call</span> is placed near a county border. These misrouted 911 <span class=\"match\">calls</span> must be transferred from one PSAP"},{"title":"Advanced Methods To Target and Eliminate Unlawful Robocalls, Call Authentication Trust Anchor","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) expands several rules previously adopted for gateway providers to other categories of voice service providers and modifies or removes existing rules consistent with these changes. Specifically, the Commission requires all domestic voice service providers to respond to traceback requests from the Commission, civil and criminal law enforcement, and the industry traceback consortium within 24 hours of the receipt of the request. Second, it requires originating providers to block substantially similar traffic when the Commission notifies the provider of illegal traffic or risk the Commission requiring all providers immediately downstream to block all of that provider's traffic. This rule is consistent with the rule for gateway providers, and requires non-gateway intermediate or terminating providers that receive such a notice to promptly inform the Commission that it is not the originating or gateway provider for the identified traffic, identify the upstream provider(s) from which it received the traffic, and, if possible, take lawful step to mitigate the traffic. Third it requires all voice service providers to take reasonable and effective steps to ensure that the immediate upstream provider is not using it to carry or process a high volume of illegal traffic. Finally, it updates the Commission's Robocall Mitigation Database certification requirements to reflect the 24-hour traceback requirement.","document_number":"2023-13035","html_url":"https://www.federalregister.gov/documents/2023/07/10/2023-13035/advanced-methods-to-target-and-eliminate-unlawful-robocalls-call-authentication-trust-anchor","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2023-07-10/pdf/2023-13035.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2023-13035.pdf?1688733914","publication_date":"2023-07-10","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"illegal <span class=\"match\">calls</span> including, but not limited to: <span class=\"match\">call</span> duration; <span class=\"match\">call</span> completion ratios; large bursts of <span class=\"match\">calls</span> in a short time frame; neighbor spoofing patterns; and sequential dialing patterns. If the <span class=\"match\">notified</span> provider is an originating provider, the identity of the <span class=\"match\">caller</span> may be a material factor in identifying whether the traffic is substantially similar. However, an originating provider may not assume, without evidence, that the <span class=\"match\">caller</span> only has one subscriber line from which it is placing <span class=\"match\">calls</span> and must maintain vigilance to ensure that the <span class=\"match\">caller</span> does"},{"title":"Improving the Effectiveness of the Robocall Mitigation Database; CORES Registration System","type":"Rule","abstract":"In this document, the Federal Communications Commission (FCC or Commission) adopts rules requiring Robocall Mitigation Database (RMD or Database) filers to take additional steps to ensure the accuracy, completeness, and currentness of submitted information. The rules also establish a base forfeiture of $10,000 for each violation for filers that submit false or inaccurate information to the Database, as well as a base forfeiture of $1,000 for failure to update information that has changed in the Database within 10 days. Further, the Wireline Competition Bureau is directed to establish a dedicated reporting mechanism for deficient filings in the Database, as well as to issue additional guidance and \"best practices\" for filers. Additionally, the Wireline Competition Bureau and Office of the Managing Director are directed to develop a two-factor (or more) authentication solution for accessing the Database.","document_number":"2026-00010","html_url":"https://www.federalregister.gov/documents/2026/01/06/2026-00010/improving-the-effectiveness-of-the-robocall-mitigation-database-cores-registration-system","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-01-06/pdf/2026-00010.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-00010.pdf?1767620708","publication_date":"2026-01-06","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"II. Legal Authority \n \n Consistent with our proposal, we adopt the foregoing revisions to the Robocall Mitigation Database requirements pursuant to the legal authorities that the Commission relied on in its <span class=\"match\">caller</span> ID authentication and <span class=\"match\">call</span> blocking orders, namely sections 201(b), 202(a), and 251(e) of the Communications Act, the Truth in <span class=\"match\">Caller</span> ID Act, and our ancillary authority. We conclude that the Commission has authority under 31 U.S.C. 3512(b) and Part 1, Subpart O of the Commission's rules to make administrative enhancements pertaining to"},{"title":"Wireless E911 Location Accuracy Requirements","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (the FCC or Commission) proposes rules to strengthen wireless 911 location accuracy rules and to put more actionable location information in the hands of Public Safety Answering Points (PSAPs) and first responders.","document_number":"2025-06865","html_url":"https://www.federalregister.gov/documents/2025/05/07/2025-06865/wireless-e911-location-accuracy-requirements","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-05-07/pdf/2025-06865.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-06865.pdf?1746535509","publication_date":"2025-05-07","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"accuracy level <span class=\"match\">when</span> used with 911 <span class=\"match\">calls</span> in each of the four morphologies. We also propose to exclude the use of live <span class=\"match\">call</span> data in the validation of vertical location technologies. Live <span class=\"match\">call</span> data does not demonstrate performance, either on a per-technology or a per-morphology basis. In addition, live <span class=\"match\">call</span> data does not distinguish between indoor and outdoor <span class=\"match\">calls</span>, and thus does not provide a basis for determining compliance with indoor vertical location requirements.\n 73 \n \n \n \n \n 73 \n  The 2015 \n Fourth Report and Order \n stated that live <span class=\"match\">call</span> data, when"},{"title":"Transwestern Pipeline Company, LLC; Notice of Scoping Period Requesting Comments on Environmental Issues for the Planned Desert Southwest Expansion Project, and Notice of Public Scoping Sessions","type":"Notice","abstract":null,"document_number":"2026-13880","html_url":"https://www.federalregister.gov/documents/2026/07/09/2026-13880/transwestern-pipeline-company-llc-notice-of-scoping-period-requesting-comments-on-environmental","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-07-09/pdf/2026-13880.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-13880.pdf?1783514715","publication_date":"2026-07-09","agencies":[{"raw_name":"DEPARTMENT OF ENERGY","name":"Energy Department","id":136,"url":"https://www.federalregister.gov/agencies/energy-department","json_url":"https://www.federalregister.gov/api/v1/agencies/136","parent_id":null,"slug":"energy-department"},{"raw_name":"Federal Energy Regulatory Commission","name":"Federal Energy Regulatory Commission","id":167,"url":"https://www.federalregister.gov/agencies/federal-energy-regulatory-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/167","parent_id":136,"slug":"federal-energy-regulatory-commission"}],"excerpts":"be a formal presentation by Commission staff <span class=\"match\">when</span> the session opens. You may <span class=\"match\">call</span> at any time after the session begins, at which time you will be placed on hold. <span class=\"match\">Calls</span> will be answered in the order they are received. Once answered, you will have the opportunity to provide your comment directly to a court reporter with FERC staff or representative present on the line. A time limit of 3 minutes may be implemented for each commentor. Please note that your hold times may vary based on the number of <span class=\"match\">callers</span> at any given time. \n Your oral comments will"},{"title":"Information Collections Being Submitted for Review and Approval to Office of Management and Budget","type":"Notice","abstract":"As part of its continuing effort to reduce paperwork burdens, as required by the Paperwork Reduction Act (PRA) of 1995, the Federal Communications Commission (FCC or the Commission) invites the general public and other Federal Agencies to take this opportunity to comment on the following information collection. Pursuant to the Small Business Paperwork Relief Act of 2002, the FCC seeks specific comment on how it can further reduce the information collection burden for small business concerns with fewer than 25 employees.","document_number":"2026-12197","html_url":"https://www.federalregister.gov/documents/2026/06/17/2026-12197/information-collections-being-submitted-for-review-and-approval-to-office-of-management-and-budget","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-06-17/pdf/2026-12197.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-12197.pdf?1781613916","publication_date":"2026-06-17","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"automated dispatchable location. For non-fixed devices, <span class=\"match\">when</span> dispatchable location is not technically feasible, internet-based TRS providers may fall back to Registered Location or provide alternative location information. As a last resort, internet-based providers may route <span class=\"match\">calls</span> to Emergency Relay Calling Centers after making a good faith effort to obtain location data from all available alternative location sources. Dispatchable location means a location delivered to the PSAP with a 911 <span class=\"match\">call</span> that consists of the validated street address of the calling"},{"title":"Analog Telecommunications Relay Service Modernization","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) proposes to modernize its telecommunications relay services (TRS) rules and seeks comment on phasing out the mandatory status of traditional TTY-based relay services (TTY Relay) under state TRS programs; recognizing additional forms of internet-based TRS, such as internet Protocol Speech-to-Speech (IP STS) and real-time text (RTT)-based relay as compensable forms of TRS; establishing a temporary, national certification process for analog relay providers and user registration and verification requirements; and updating or eliminating obsolete rules to all forms of TRS. Through these proposals, the Commission aims to align TRS with today's communications landscape, better serve the needs of relay users, ensure the continued availability of TRS through the transition from legacy communications network, to modern, IP-based networks, and continue to protect the integrity of the TRS program through the prevention of waste, fraud, and abuse.","document_number":"2025-24210","html_url":"https://www.federalregister.gov/documents/2026/01/02/2025-24210/analog-telecommunications-relay-service-modernization","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-01-02/pdf/2025-24210.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-24210.pdf?1767188718","publication_date":"2026-01-02","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"Relay, STS, and CTS) to be capable of handling pay-per-<span class=\"match\">call</span> <span class=\"match\">calls</span>. The Commission proposes to delete this rule. The Commission believes the use of pay-per-<span class=\"match\">call</span> (900) <span class=\"match\">calls</span> is no longer sufficiently prevalent in the United States to warrant an explicit rule requiring TRS providers to support that type of <span class=\"match\">call</span>. The Commission also notes that, with or without a specific pay-per-<span class=\"match\">call</span> provision, TRS providers remain subject to the general requirement that they “be capable of handling any type of <span class=\"match\">call</span> normally provided by telecommunications carriers unless"},{"title":"Improving the Effectiveness of the Robocall Mitigation Database; Amendment of CORES Registration System","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) proposes and seeks comment on procedural measures that would require Robocall Mitigation Database filers to take additional steps to ensure the accuracy of submitted information, potential technical solutions for validating data, accountability measures to ensure and improve the overall quality of submissions in the Robocall Mitigation Database, and generally invites comment on any other procedural steps the Commission could require to increase the effectiveness of the Robocall Mitigation Database as a compliance and consumer protection tool.","document_number":"2024-20176","html_url":"https://www.federalregister.gov/documents/2024/09/12/2024-20176/improving-the-effectiveness-of-the-robocall-mitigation-database-amendment-of-cores-registration","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-09-12/pdf/2024-20176.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-20176.pdf?1726058722","publication_date":"2024-09-12","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"Commission that they intend to do so. \n We view this process to be similar to that authorized <span class=\"match\">when</span> the Commission sends cease-and-desist letters pursuant to § 64.1200(k)(4) of our rules, which states that a provider may, without liability, block voice <span class=\"match\">calls</span> or traffic from an originating or intermediate provider that has been <span class=\"match\">notified</span> by the Commission but fails to take steps to mitigate or prevent its network from being used to originate illegal <span class=\"match\">calls</span>. Under this rule, a provider must, prior to initiating blocking, provide the Commission with notice"},{"title":"Ensuring the Reliability and Resiliency of the 988 Suicide & Crisis Lifeline; Rules Concerning Disruptions to Communications; Implementation of the National Suicide Hotline Improvement Act of 2018","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) requires covered 988 service providers (a new category of service provider) and cable, satellite, wireless, wireline, and interconnected voice over internet protocol (VoIP) providers (originating service providers) to report outages that potentially affect the 988 Suicide and Crisis Lifeline in the Commission's Network Outage Reporting System (NORS). The rules also require these entities to directly notify Substance Abuse and Mental Health Services Administration (SAMHSA), the Department of Veterans Affairs (VA), and the 988 Lifeline administrator about outages that potentially affect a 988 special facility, and exercise special diligence to maintain accurate, up-to-date contact information for 988 special facilities, just as the Commission's rules require for 911 special facilities. The rules also allow SAMHSA and the VA to have direct read-only access to NORS consistent with the Commission's existing NORS outage information sharing procedures. These rules are adopted with the goal of ensuring that the Commission and those parties that provide life-saving crisis intervention services to people calling the 988 Lifeline receive timely and actionable information about 988 service outages that potentially affect those services' ability to meet the immediate health needs of people in suicidal crisis and mental health distress.","document_number":"2024-00428","html_url":"https://www.federalregister.gov/documents/2024/01/16/2024-00428/ensuring-the-reliability-and-resiliency-of-the-988-suicide-and-crisis-lifeline-rules-concerning","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-01-16/pdf/2024-00428.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-00428.pdf?1705067114","publication_date":"2024-01-16","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"help 988 <span class=\"match\">callers</span> successfully reach the Lifeline. In any event, the Commission believes the potential negative impacts on the effectiveness of outage notifications outweigh these possible benefits. \n 23. The Commission also declines to require that PSAPs be <span class=\"match\">notified</span> about 988 outages. While some commenters argue that 988 outage notifications would prepare PSAPs for potential <span class=\"match\">call</span> volume increases and give them the necessary situational awareness to handle those <span class=\"match\">calls</span> in an appropriate manner, our rules already require PSAPs to be <span class=\"match\">notified</span> about outages"},{"title":"Agency Information Collection Activities: Proposed Request and Comment Request","type":"Notice","abstract":null,"document_number":"2026-05600","html_url":"https://www.federalregister.gov/documents/2026/03/23/2026-05600/agency-information-collection-activities-proposed-request-and-comment-request","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-03-23/pdf/2026-05600.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-05600.pdf?1774010715","publication_date":"2026-03-23","agencies":[{"raw_name":"Social Security Administration","name":"Social Security Administration","id":470,"url":"https://www.federalregister.gov/agencies/social-security-administration","json_url":"https://www.federalregister.gov/api/v1/agencies/470","parent_id":null,"slug":"social-security-administration"}],"excerpts":"representative payees to report changes <span class=\"match\">when</span> beneficiaries return to work, <span class=\"match\">when</span> their amount of work increases, or <span class=\"match\">when</span> their earnings increase. Similarly, SSA requires recipients of SSI, their deemors, and representative payees to report changes in work and monthly wages. SSA allows SSDI beneficiaries, SSI recipients, deemors, and representative payees to report earnings via electronic means, though the methods available depend on the type of benefits received. SSDI users may report wages using an internet reporting system <span class=\"match\">called</span> myWageReport. myWageReport"},{"title":"Controlled Substances Ordering System (CSOS) Modernization","type":"Rule","abstract":"This rule is amending the Drug Enforcement Administration's (DEA) regulations to conform to the Controlled Substances Ordering System (CSOS) modernization effort by requiring all CSOS enrollment applications and supporting materials to be submitted through the Diversion Control Division secure online portal. These amendments improve the enrollment process by aligning it with DEA's current requirements for other online form submissions. The online submission of enrollment applications and supporting material through the secure online portal increases the efficiency of the enrollment, modification, and revocation processes, and ensures DEA's receipt of accurate documentation in a more timely and organized manner.","document_number":"2025-19325","html_url":"https://www.federalregister.gov/documents/2025/10/02/2025-19325/controlled-substances-ordering-system-csos-modernization","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-10-02/pdf/2025-19325.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-19325.pdf?1759322726","publication_date":"2025-10-02","agencies":[{"raw_name":"DEPARTMENT OF JUSTICE","name":"Justice Department","id":268,"url":"https://www.federalregister.gov/agencies/justice-department","json_url":"https://www.federalregister.gov/api/v1/agencies/268","parent_id":null,"slug":"justice-department"},{"raw_name":"Drug Enforcement Administration","name":"Drug Enforcement Administration","id":116,"url":"https://www.federalregister.gov/agencies/drug-enforcement-administration","json_url":"https://www.federalregister.gov/api/v1/agencies/116","parent_id":268,"slug":"drug-enforcement-administration"}],"excerpts":"$109,138 \n 32 \n \n will be eliminated <span class=\"match\">when</span> this final rule is implemented.\n \n \n \n 32 \n  Source: DEA.\n \n \n \n 5. \n <span class=\"match\">Call</span> Center Support Cost: \n DEA operates a CSOS <span class=\"match\">call</span> center to service questions, or provide assistance, regarding CSOS enrollment and certificate management. The estimated total current annual cost as $1,749,946.\n 33 \n \n While DEA anticipates a reduction in the number of <span class=\"match\">calls</span> and duration of each <span class=\"match\">call</span>, DEA anticipates this reduction will result in lower wait-times for <span class=\"match\">callers</span> rather than reduced <span class=\"match\">call</span> center resources. Therefore, DEA estimates"}]}