Advanced Methods To Target and Eliminate Unlawful Robocalls (final rule; FCC 25-15), 90 FR 13416

Publisher

Office of the Federal Register / Federal Communications Commission

URL

https://www.govinfo.gov/content/pkg/FR-2025-03-24/html/2025-04811.htm

Published

2025-03-24

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

US government work (public domain); public domain; short excerpts and locators used anyway

Source notes citing this source

• The rule defines SIP 603+ by reference to ATIS-1000099, adopted 16 August 2022. in context
• FCC 25-15 required providers to implement SIP 603+ no later than 12 months after the order's Federal Register publication (24 March 2025). in context
• Under amended 64.1200(k)(9), the appropriate response code is SIP 603+ as defined in ATIS-1000099 for calls terminating on an IP network, and ISUP cause code 21 with cause location 'user' for calls terminating on a non-IP network. in context
• SIP 603+ differs from a standard 603 by using the reason phrase 'Network Blocked' instead of 'Decline', together with a Reason header that indicates analytics-based blocking and gives redress contact information. in context
• FCC 25-15 directs providers to stop using SIP 603, 607 and 608 for analytics-based blocking once they implement 603+, and in no case later than 12 months after Federal Register publication. in context
• The DNO list categories in FCC 25-15 are inbound-only government numbers at the government's request, inbound-only private numbers used in imposter scams at the entity's request, invalid NANP numbers, unallocated NANP numbers, and unused allocated numbers. in context
• FCC 25-15 requires every voice service provider to block calls purporting to originate from numbers on a reasonable do-not-originate list, and warns that a list omitting obvious numbers that could be added with little effort may be deemed unreasonable. in context
• The FCC 25-15 Federal Register document is dated effective 25 March 2026, except the amendment to 47 CFR 64.1200(o), which was delayed indefinitely pending a further Federal Register notice announcing information-collection approval. in context
• FCC 25-15, the order requiring SIP 603+ for analytics-based blocking, was adopted 27 February 2025, released 28 February 2025 in CG Docket No. 17-59, and published at 90 FR 13416 on 24 March 2025. in context
• When the blocking code crosses from an IP to a non-IP network, SIP 603+ must map to ISUP code 21; from non-IP to IP, ISUP code 21 with cause location 'user' must map to SIP 603 or 603+. in context
• FCC 25-15 allows a standard SIP 603 to continue where ISUP code 21 has been translated into a standard 603 that cannot be distinguished as a 603+. in context
• In FCC 25-15 the Commission declined to require display of caller name information when a provider displays an indication that caller ID was authenticated, and urged industry to keep developing Rich Call Data and branded calling. in context
• When a blocked call's response crosses a TDM segment, the caller is likely to receive a plain 603 without the 603+ redress contact, because ISUP cause 21 carries no Reason-header text; the caller then has to identify the blocking provider some other way. inferred in context

Cite this source record

APA

WarmTransfer. (2025, March 24). Advanced Methods To Target and Eliminate Unlawful Robocalls (final rule; FCC 25-15), 90 FR 13416. WarmTransfer. https://warmtransfer.net/knowledge/sources/govinfo-fr-2025-04811-fcc-25-15

BibTeX

@misc{warmtransfer-govinfo-fr-2025-04811-fcc-25-15,
  title  = {Advanced Methods To Target and Eliminate Unlawful Robocalls (final rule; FCC 25-15), 90 FR 13416},
  author = {{WarmTransfer}},
  year   = {2025},
  url    = {https://warmtransfer.net/knowledge/sources/govinfo-fr-2025-04811-fcc-25-15},
  note   = {Office of the Federal Register / Federal Communications Commission, accessed 2026-09-24}
}