Troubleshooting · Symptoms
Fast Busy Signal: The Call Was Rejected — Find Out Why
Fast busy — the rapid reorder tone — is the phone system's way of saying 'no, immediately, and not because the person is busy'. Unlike a normal busy signal (the callee is genuinely occupied), fast busy means the call was rejected during setup: a route refused it, a trunk had no capacity, the number wasn't recognized, or a policy blocked it. Something in the chain made a decision, and it wrote the reason down in a SIP response code.
This guide is short because the method is short: get the code, and the code names the culprit. Guessing without it is how fast-busy tickets wander.
The codes behind fast busy
| Code in the trace | Meaning | Typical fix |
|---|---|---|
| 404 Not Found | The dialed number isn't recognized on that route | Dial plan/format (missing prefix, country code), porting not complete, wrong trunk for that destination |
| 486 Busy Here | The endpoint itself is busy (genuine busy can also surface as fast busy on some systems) | Wait/retry; check the callee isn't stuck 'in use' — a phone with a stuck call appearance shows busy forever |
| 503 Service Unavailable | A server/trunk can't take the call: capacity exhausted or a route down | Check trunk channels (all busy = sizing), provider status, failover configuration |
| 603 Decline | A global refusal — policy or the user declined everywhere | Blocked destination lists, fraud-prevention blocks, account restrictions |
| 403 Forbidden | Refused for authorization reasons | Calling permissions/class of service, trunk credentials, destination not allowed on the plan |
| 480/408 | Endpoint unavailable or unreachable | Registration state (see the registration guide) |
Capacity fast-busy: the trunk variant
The version that generates office-wide complaints arrives at the busiest hour: outbound calls fail fast-busy while inbound works. That asymmetry is arithmetic — all trunk channels are occupied (or the hosted plan's concurrent-call limit is hit), and the platform rejects new attempts instantly rather than queueing them. Your trunk utilization report or a 503 in the trace confirms it. The remedies are sizing (channels matched to busy-hour Erlangs — see the channel guide) and honesty about call-path limits in the contract you bought.
Two-minute method
- Reproduce the call and capture it, or pull the call's record in the platform's trace tool. Find the final SIP response code on the failed INVITE.
- Map the code with the table above; identify whose element rejected the call (your PBX, your trunk, the far carrier, the endpoint).
- Fix that element: dial-plan prefix, class-of-service permission, channel count, registration, or a provider ticket carrying the code and Call-ID.
- Retest the exact number that failed — fast busy is destination-specific more often than users expect (one misformatted DID, one unported number).
- If the code is 503 at busy hours, pull a week of trunk utilization and right-size with the Erlang method before buying channels blindly.
Frequently asked questions
- Fast busy on one specific number only — what does that mean?
- The route to that destination is the problem: the number may have ported away, been disconnected, or your dial plan sends it to a trunk that doesn't serve it. The trace's 404/503 and the 'To' header tell the story; test the same number from a mobile to confirm it exists.
- We get fast busy and a 'all circuits are busy' announcement.
- That announcement is the recorded version of capacity exhaustion — trunk channels or plan call-paths fully occupied. It is a sizing and contract fact, answerable from utilization reports.
- Could fast busy be a fraud block?
- Yes — providers block destinations and patterns flagged as fraud (sudden international volume, premium numbers). A 403/603 appearing after a calling-pattern change is worth one direct question to the provider's fraud desk.