Locate the response family
- 1xx ProvisionalRequest is progressing
- 2xx SuccessRequest succeeded
- 3xx RedirectionAnother destination
- 4xx Request failureInterpret this request486 belongs here
- 5xx Server failureServer could not fulfil
- 6xx Global failureFailure across destinations
Read the status with its request method and call leg. For example, 200 after REGISTER confirms a binding; it does not prove an INVITE succeeded.
What this response means
The called endpoint is busy at this location. This is a normal possible call outcome and does not assert that every possible destination is unavailable.
Read it in context
The endpoint or PBX may apply call waiting, capacity or busy-state policy. A user declining a call can also be mapped by an implementation into a response the caller hears as busy.
Administrator checks
Check current calls, call-waiting settings and the actual responding endpoint. Compare direct extension dialing with a ring-group or queue route. Verify whether another contact or fallback is intended to be tried under the business design.
Next action and common mistake
Do not disable capacity or permission controls merely to avoid busy responses. Confirm the expected busy treatment, voicemail and overflow path. Distinguish 486’s local busy outcome from the broader refusal semantics of a 603 response.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.