Getting a 603 Error? Here's What Changed
Recently, 603 errors have become more important due to the FCC changes on how providers must handle certain types of call blocking. Here is what you need to know.
July 09, 2026 | 5 min read
Getting a 603 Error? Here’s What Changed and What You Can Do About It
If your outbound calls are suddenly failing with no ring, no answer, and no clear explanation, there’s a good chance you’ve run into a 603 error. If it’s been happening more frequently lately, that’s not a coincidence. The FCC has been quietly reshaping the rules around call blocking, and the industry hit a major milestone in early 2025 that every voice provider and their customers need to understand.
First, What Is a 603, and Why Does It Happen?
A 603 is a SIP response code that has historically meant “Decline”, the far-end network chose not to complete the call. Simple enough on paper, but the reality is messier. For years, carriers have been allowed to use a 603 (along with codes 607 and 608) as a catch-all signal when their analytics programs decided to block a call. The problem? A generic 603 tells you almost nothing. It doesn’t tell you who blocked it, why it was flagged, or how to fix it.
That ambiguity has been frustrating businesses and carriers alike. Legitimate calls from doctors’ offices, financial institutions, contact centers, have been getting caught in the net right alongside actual robocall traffic, with no straightforward path to dispute the block.
What the FCC Did and Why It’s a Big Deal:
In February 2025, the FCC adopted its Eighth Report and Order (FCC 25-15), published in the Federal Register on March 24, 2025.
The two headline requirements:
- SIP code 603+ is now the exclusive code for analytics-based blocking on IP networks. All voice service providers must use 603+ and only 603+ when a call is blocked by an analytics program. The old 603, 607, and 608 codes are being retired for this purpose. The deadline for full compliance was March 25, 2026.
- Every provider in the call path is now on the hook. The DNO (Do-Not-Originate) blocking requirement has been expanded from gateway providers to all U.S.-based voice service providers in the call path. That means originating, intermediate, and terminating carriers all share responsibility for blocking calls from invalid, unallocated, or flagged numbers.
So What Actually Makes 603+ Different?
This is where it gets useful. Unlike the standard 603 “Decline,” the new 603+ status line reads “Network Blocked” an immediate, standardized signal that an analytics-based decision was made. More importantly, the ATIS standard for 603+ requires mandatory fields in the reason header that identify the blocking provider and provide contact information for filing a dispute.
That’s the shift that matters. Before, getting a 603 meant you were left guessing which carrier in the chain made the call — no pun intended. With 603+, the blocking provider is identified, and you have a direct line to dispute erroneous blocks. The FCC’s whole point here is transparency and effective redress, which is what the TRACED Act has required all along.
And it must travel the full path. Any provider that receives a 603+ is required to pass it upstream to the originating point — all the way back to you. For calls that cross between IP and legacy TDM networks, the equivalent is ISUP code 21, and carriers are required to map between the two, so the notification isn’t lost in translation.
What Could Be Triggering Your Blocks?
The 603+ framework addresses notification — but it doesn’t change the underlying reasons calls get blocked in the first place. If your calls are getting declined, the analytics programs making those decisions are typically looking at things like:
- STIR/SHAKEN attestation level. Calls with no attestation are more likely to be flagged.
- Caller ID reputation. Whether your number appears on third-party spam databases like Hiya or First Orion.
- Call volume patterns. High simultaneous or sequential call volume that resembles automated dialing.
- Number validity. Whether your outbound number is properly allocated and assigned in NANPA records.
- Upstream carrier reputation. If your originating carrier has a poor standing with downstream networks, it can affect your traffic regardless of what your own numbers look like.
What Should You Do If Your Calls Are Being Blocked?
Start with your call detail records. Pull the specific call that was blocked, date, time, originating number, destination, and bring that to your carrier. Once 603+ is fully deployed, the reason header on a blocked call should identify the provider that made the decision and give you contact information to file a dispute directly.
In parallel, get ahead of the root cause. Confirm your STIR/SHAKEN implementation is in order and that your outbound numbers carry A-level attestation where possible. Check your numbers against major reputation databases. If you’re a high-volume caller, review your traffic patterns to make sure they don’t look like robocall behavior to an automated system.
Conclusion
The 603+ framework isn’t just a regulatory checkbox, it’s the first time the industry has had a standardized, mandatory mechanism for identifying who blocked a call and giving callers a real path to contest it. That’s meaningful progress, and knowing how to use it is now part of doing business on the PSTN. If you are experiencing 603 connectivity issues on your calls, contact QuestBlue today and speak to an experienced team member about your options at sales@questblue.com or 877.686.4784 to learn how QuestBlue can support your communication needs.