0
Skip to content

FCC Call Blocking Redress: Final Compliance Deadline is March 25

FCCThe grace period for the FCC’s uniform call-blocking notification rule is ending. Review our compliance checklist to ensure your voice providers are correctly using SIP Code 603+ to identify and resolve erroneous blocks.

03/02/2026 12:00 P.M.

Final compliance with the Federal Communications Commission’s order on call blocking notifications and redress (PDF) from voice service providers is required effective March 25.

The order was published in the Federal Register about a year ago, and voice service providers have had the last 12 months to fully implement SIP Code 603+.

The order modifies the existing requirement for voice service providers to immediately notify callers when providers block calls based on reasonable analytics. Specifically, it now requires the use of Session Initiation Protocol (SIP) Code 603+.

The goal is to fulfill the requirements in the Telephone Robocall Abuse Criminal Enforcement and Deterrence (TRACED) Act for transparency and effective redress, ensuring legitimate callers know exactly when, why, and by whom their calls were blocked.

Key Technical Requirements

  • Mandatory Uniform Code: All voice service providers must now use SIP Code 603+ to notify originating providers and callers of analytics-based blocking.
  • Elimination of Old Codes: The use of SIP Codes 603, 607, and 608 for this purpose is being eliminated to prevent confusion.
  • “Network Blocked” Label: Unlike the standard SIP 603 code (which displays as “Decline”), the new 603+ code will read “Network Blocked.”
  • Integrated Redress Information: The code includes standardized text fields indicating the block was analytics-based and provides specific contact information for the caller to seek redress.
  • Do Not Originate (DNO) Blocking: The order also requires all providers in the call chain to block calls from numbers on a “reasonable do not originate” list.

Scope and Limitations

The order applies to voice calls blocked specifically due to reasonable analytics. It does not apply to text messages, call mislabeling (e.g., “Spam Likely” tags), or calls blocked for other reasons (such as being on a DNO list).

Action Items for Callers

ACA International suggests that businesses and members take the following steps to prepare:

  1. Consult Providers: Reach out to your voice service providers to ensure they are prepared to receive and pass along SIP Code 603+ notifications.
  2. Establish Redress Protocols: Work with your provider to determine how they will handle these notifications — specifically, whether they will notify you immediately or contact the blocking entity on your behalf.
  3. Review Contracts: Check service agreements to ensure your provider is obligated to facilitate the transparency and redress mechanisms mandated by the FCC.

ACA’s checklist for members, available on the Call Blocking and Labeling Resource Center webpage, has been updated to reflect the new call blocking and notification requirements approved by the FCC. It is designed to facilitate discussions with voice service provider(s) and platform providers.

As the final deadline approaches, it is a good time for ACA members to reach out to their voice service providers to confirm implementation and ensure that they know when a blocking notice has been sent.

Remember, subscribe to ACA Daily and Member Alerts under your My ACA Assistant profile when logged in to acainternational.org.

If you have executive leadership updates or other member news to share with ACA, contact our communications department at comm@acainternational.org. View our publications page for more information and our news submission guidelines here.

One moment please...

Share Profile

This site utilizes cookies as included in our Privacy Policy and User Agreement.