How SIP Response Codes (603, 607, 486) Reveal If Your Toll-Free Number Is Being Flagged as Spam

TL;DR: Every phone call ends with a SIP response code — a number that tells your system why the call ended. Most businesses never see these codes. But buried in those codes is critical intelligence: SIP 607 means a consumer reported your call as unwanted, SIP 603 means a carrier explicitly refused to complete the call, and SIP 486 spikes can indicate carrier-side filtering. Monitoring these codes per toll-free number is the earliest possible warning that a number is being flagged — before your answer rates collapse and before you know you have a problem.

---

What Is SIP and Why Do the Response Codes Matter?

SIP stands for Session Initiation Protocol. It is the signaling protocol that modern telephony uses to set up, maintain, and terminate phone calls. When you dial a number, SIP messages travel between servers negotiating the call. When the call ends — for any reason — a final SIP response code is sent back indicating why the call ended.

You may be familiar with HTTP response codes: 200 OK, 404 Not Found, 500 Internal Server Error. SIP response codes work on the same principle — a three-digit number from the carrier network communicating what happened.

For businesses routing calls, these codes have always been visible in raw call logs. But until recently, nobody built a system that turned those raw codes into per-number intelligence. Most platforms simply logged the code and moved on. CallFlow uses these codes to calculate a live spam health score per number — and understanding what each code means is essential for interpreting that score.

---

The Three Codes That Matter Most for Spam Detection

SIP 607 — Unwanted

What it means: The called party (or their carrier) has signaled that this call was unwanted.

SIP 607 was formally introduced by the IETF (Internet Engineering Task Force) in RFC 8197 and pushed into widespread use by the FCC starting around 2020 as part of the STIR/SHAKEN framework rollout. The FCC specifically created this code to give consumers and carriers a standardized mechanism for reporting unwanted calls.

When a 607 response is returned:

• A consumer used a carrier-provided "report spam" feature on their phone
• A consumer app (like Hiya, Robokiller, or YouMail) automatically flagged the call based on its database
• The carrier itself determined the call was from a known spam source and rejected it on the consumer's behalf

The severity: 607 is the highest-severity signal for spam detection. It represents direct feedback — either from a real person or a system acting on that person's behalf — that the call was unwanted. Carrier analytics engines (TNS, Hiya, First Orion) weight 607 responses heavily in their spam scoring models. Even a handful of 607 responses from the same number triggers attention.

In CallFlow's spam score: 607 responses carry the highest weight in the score formula — 50 points per call at a 100% 607 rate. A number receiving even 5% of its calls as 607s would score meaningfully above zero on this signal alone.

---

SIP 603 — Decline

What it means: The call was explicitly refused — without ever reaching or ringing the called party.

Unlike a no-answer (where the call rings and nobody picks up) or a busy signal (where the line is occupied), 603 is an active rejection. The carrier network — not the end user — decided this call should not be completed and sent back 603 before the phone ever rang.

603 responses come from:

• Carrier-side blocklists — the number has been added to a known spam list
• Call blocking apps operating at the carrier level that pre-block specific numbers
• Enterprise business policies that block all inbound toll-free calls
• STIR/SHAKEN failed attestation rules — carriers that refuse calls with failed attestation

The severity: High. A 603 response means the carrier either already knows your number is a problem, or the destination has policies that reject your number category. High 603 rates suggest your number is already on carrier-side blocklists or that your caller ID type (toll-free, international, low-attestation SIP) is being systemically filtered by recipients.

In CallFlow's spam score: 603 responses carry the second-highest weight — 25 points per call at a 100% 603 rate.

---

SIP 486 — Busy Here (in Spikes)

What it means in isolation: The called number is currently busy — in use on another call.

What it means in spikes: When 486 responses arrive at abnormally high rates from a specific number or to a specific campaign number, they often indicate artificial busy signals being generated by the carrier or by call blocking apps — not genuine busy lines.

Carriers can generate artificial 486 responses as a quiet form of call rejection. Rather than sending an explicit 603 rejection (which would be logged and potentially disputed), some carrier-side filtering sends 486 — a response that looks like a normal busy signal but actually means "we are not completing this call."

Identifying 486 spikes vs. normal busy: Normal 486 rates for inbound marketing campaigns are typically 3–8%. A rate above 15–20% consistently suggests something beyond normal busy signals. A sudden jump — where 486 rate doubles or triples in a day with no corresponding change in call volume or destination capacity — strongly suggests carrier-side filtering.

In CallFlow's spam score: 486 spike rates carry a moderate weight — 12 points per call at a 100% rate. The score formula evaluates 486 in context with other signals to distinguish genuine busy signals from filtering patterns.

---

The Supporting Signals

Beyond the three primary SIP codes, two additional behavioral signals complete the spam score:

No-Answer Rate (SIP 480 or timeout)

A call that rings but receives no answer returns a 480 Temporarily Unavailable or simply times out. Normal no-answer rates for inbound marketing campaigns are 25–40%. Rates above 60–70% are concerning.

Why high no-answer is a spam signal: When carrier analytics engines or consumer apps flag a number, they often do not block it outright — they let the call ring but show "Potential Spam" on the caller ID. Consumers see "Potential Spam" and decline to answer. The result: a spike in no-answer rates without any change in call volume.

High no-answer rates that appear without an obvious operational explanation (seasonal, time-of-day) are often an early warning that the number is already being labeled on recipient devices.

Short Completed Call Rate

Calls that connect but last under 10 seconds. The call technically completed — it was answered — but the recipient hung up almost immediately.

Short calls happen for legitimate reasons (wrong number, quick inquiry resolved in seconds). The signal becomes meaningful when:

• The short call rate rises sharply without explanation
• Short calls cluster at unusual times
• Short calls come disproportionately from numbers or area codes associated with fraud

Short calls in context with 607 responses are particularly telling: consumers who pick up a suspected spam call, realize it is spam, and hang up — then report it. The sequence produces a completed call (answered), a very short duration, and a 607 response all from the same call event.

---

How Carriers Use These Signals

The major carrier analytics engines — TNS Call Guardian (Verizon), Hiya (AT&T), and First Orion (T-Mobile) — aggregate SIP response signals across their entire network. They see billions of calls daily, across hundreds of carriers and call-terminating networks.

Their spam scoring models use machine learning to combine:

• Raw 607, 603, 486 signal rates for a specific number
• The velocity of those signals (sudden spikes vs. gradual accumulation)
• Historical behavior of the number over months and years
• Cross-carrier consistency (is the same number generating 607s on AT&T and Verizon simultaneously?)
• STIR/SHAKEN attestation level (A, B, or C — higher attestation means more trusted origination)
• CNAM database matches (does the registered name match a known business?)
• Honeypot signals (did the number ever call an unlisted "trap" number?)

When a number reaches a threshold in their model, the carrier applies a label:

• "Potential Spam" — shown on recipient phones before they answer
• "Scam Likely" — stronger label used for numbers with high-confidence fraud scores
• Silent block — calls from the number are rejected without ringing at all

Your CallFlow spam score does not have access to cross-carrier data or honeypot signals — that is carrier-proprietary information. But your own SIP response data is the earliest possible signal you can access, because it is generated in real time on your own traffic. Carrier-side flagging happens after signals accumulate. Your own data shows the accumulation as it happens.

---

The Timeline of a Number Getting Flagged

Understanding the typical progression helps you catch problems early:

Stage 1: Clean (Months 0–3 of heavy use)

New number, clean history. No 607s. Low 603 rate (normal carrier rejections for disconnected numbers). Normal no-answer rate. Score: Healthy (0–25).

Stage 2: Early Signals (Weeks 1–4 after traffic quality degrades)

A traffic source introduces lower-quality calls. Callers who feel pestered file occasional 607 reports. 603 rate ticks up slightly as some carrier apps begin recognizing the number. Score: Caution (26–50).

Stage 3: Growing Concern (Weeks 4–8)

More 607 accumulation. TNS or Hiya may now be applying "Potential Spam" label to outgoing calls from this number — but you cannot see this directly. Answer rates on calls from this number start declining (because consumers see the label and decline). No-answer rate rises. More 607s from the calls that do get answered. Score: Warning (51–75).

Stage 4: Flagged (Month 2–3)

Number is now labeled across most major carriers. Answer rate has dropped 40–60%. Some carriers are sending silent blocks (603 without ringing). Buyers in your campaign notice call quality has dropped and inquiry rate has fallen. Score: High Risk (76–100).

Stage 5: Unusable (Month 3+)

The number is effectively dead for marketing use. Calls are blocked or labeled on every major carrier. Answer rate is under 15%. Remediation is possible but takes weeks and is not guaranteed. Number replacement is faster.

The window for intervention: Between Stage 2 and Stage 3 — when the score is in Caution range — is when action is most effective. Identify the traffic source generating 607s, clean it up or remove it, and the 30-day window gradually purges the bad data. Score improves. Number recovers.

Waiting until Stage 4 means fighting an uphill remediation battle. Waiting until Stage 5 means replacing the number entirely.

---

How to Read the Spam Score Breakdown in CallFlow

Hover over any number's spam score badge in the Numbers page. The breakdown shows:

Signal	What You See	What It Means
607 rate	X% of calls	X% of calls ended with carrier unwanted signal
603 rate	X% of calls	X% of calls were explicitly declined before ringing
486 spike	X% of calls	X% unusually high busy responses
Failed rate	X% of calls	X% failed to complete for non-607/603 reasons
No-answer rate	X% of calls	X% rang but were not answered
Short call rate	X%	X% connected but lasted under 10 seconds

Reading the breakdown in context:

• High 607 + high short call rate + normal no-answer → Traffic quality problem. Real callers are answering, getting annoyed, hanging up, and reporting. Clean your traffic source.
• High no-answer + rising 603 → Number is getting labeled. Callers see "Potential Spam" and decline. Some carriers are now blocking. Begin remediation.
• High 486 spike + normal 607 and 603 → Possible carrier-side filtering or genuine capacity problem at destination. Check if destination numbers are consistently busy at certain times.
• High 603 + low 607 → Destination-side blocking (enterprise blocklist, call blocking app policy) rather than reputation-based spam flagging. Different problem requiring different response.

---

What to Do Based on Your Score

Healthy (0–25): Maintenance Mode

• Review score monthly
• No action required
• Keep traffic sources clean and IVR qualification active

Caution (26–50): Active Investigation

• Check traffic sources in the last 30 days for quality changes
• Review call recordings from short calls and 607-generating calls if identifiable
• Tighten IVR qualification to filter lower-quality callers
• Consider whether the call timing is generating complaints (late evening calls)

Warning (51–75): Urgent Action

• Pause new campaign traffic through this number
• Route existing traffic to a clean backup number
• Review all active publishers or traffic sources sending calls through this number
• Check call recording samples from the highest-complaint periods
• Begin remediation registration with Free Caller Registry

High Risk (76–100): Emergency Response

• Immediately stop campaign traffic on this number
• Replace with a new number for active campaigns
• Pull call recordings from the number's last 30 days
• Submit remediation requests to:
  • Free Caller Registry (freecallerregistry.com) — covers AT&T, T-Mobile, Verizon simultaneously
  • Numeracle — professional number reputation management
  • Hiya Business — direct remediation with AT&T's engine
  • TNS Call Guardian — Verizon's analytics engine
• Document legitimate business purpose and call volume for your dispute

---

Remediation: Does It Work?

Yes, but it is slow and not guaranteed.

The process:

1. Register at Free Caller Registry (free, covers all three major carriers)
2. Provide business name, caller ID information, call use case
3. Wait 2–6 weeks for the carrier analytics engines to process and update their databases
4. Monitor your score — 607 and 603 rates should begin declining as the new traffic patterns (cleaner) replace the old ones in the 30-day window

Simultaneous with registration, the most important step is stopping the traffic that generated the complaints. If the 607s are still accumulating, registration will not overcome the ongoing damage.

For numbers with significant brand value (printed on marketing materials, in long-running ad campaigns), the remediation effort is worth it. For numbers that are interchangeable, replacement is faster.

---

Preventing the Problem: Best Practices

Use IVR qualification on all campaign numbers. A digit-press requirement filters automated traffic. Randomized digits defeat sophisticated autodialers.

Monitor spam scores weekly for active campaign numbers. The earlier you see movement toward Caution, the more options you have.

Assign dedicated numbers per traffic source. If Publisher A's traffic is generating complaints, you see it in Publisher A's number — not mixed in with all your traffic.

Set minimum call duration thresholds. Only count calls above 60 seconds as valid. This creates a natural incentive structure against incentivized short-duration fraud.

Audit your traffic sources regularly. Where are your calls coming from? Are those sources sending legitimate traffic? A clean traffic source is the best long-term spam prevention.

Do not recycle numbers immediately. When you release a number, there is a period where carrier databases still associate old call behavior with that number. New assignment inherits the reputation. Allow a cooling period before reassigning released numbers.

---

Frequently Asked Questions

Can I see the exact SIP response codes for individual calls in CallFlow? The spam score aggregates SIP codes across all calls per number for the last 30 days. Individual call records show call status (completed, failed, no-answer, busy) which maps to SIP response categories.

Is SIP 486 always a spam signal? No. Normal 486 responses (3–8% rate) are genuine busy signals — the destination number is in use. 486 becomes a spam signal when the rate is abnormally elevated or when it spikes suddenly without explanation. Context matters.

How long until a cleaned-up number recovers its score? The score is a rolling 30-day calculation. Once you stop the traffic generating bad signals, the score improves as the 30-day window rolls forward. Significant improvement is usually visible in 2–4 weeks; full recovery to Healthy (0–25) typically takes 4–6 weeks of clean traffic.

Are toll-free numbers more vulnerable to spam flagging than local numbers? Both can be flagged. Toll-free numbers are specifically not covered by STIR/SHAKEN attestation in the same way as 10-digit numbers (which can receive A-level attestation from the originating carrier). This means toll-free numbers rely more heavily on their behavioral track record — 607s, 603s, call patterns — for carrier reputation scoring.

What if my 607 rate is high but I am not doing anything wrong? This happens. Aggressive but legitimate marketing (high call volume, broad targeting) can generate enough complaints to push a score upward even without intentional fraud. In this case, IVR qualification is the best tool — filtering callers who are less aligned with your offer reduces complaint rates. You may also need to register with carrier analytics engines to establish your legitimate business identity.

---

Conclusion: The Intelligence Is in the SIP Codes

Carrier networks have been generating SIP 607, 603, and 486 responses for years. The information has always been there — embedded in call termination data that most platforms discard or ignore.

CallFlow built the first per-number spam score system in the call forwarding market specifically because this data is too valuable to ignore. Every number on your account generates a continuous stream of SIP feedback from the carrier network. That feedback tells you, in real time, whether carriers are beginning to flag your number — before the answer rates collapse, before the buyers complain, before you have to replace the number.

The SIP codes are the earliest warning system you have. Reading them correctly is the difference between proactive number management and expensive emergency response.

See your numbers' spam scores at callflow.solutions.