Locate the response family
- 1xx ProvisionalRequest is progressing
- 2xx SuccessRequest succeeded
- 3xx RedirectionAnother destination301 belongs here
- 4xx Request failureInterpret this request
- 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 requested address has a new permanent location represented by the redirect information. This is a routing instruction, not ordinary ringing.
Read it in context
A service can redirect requests when an identity or destination has moved. Client and intermediary behavior depends on policy; your PBX may not automatically follow every supplied contact.
Administrator checks
Inspect the Contact destination and whether it is expected for the called identity. Check route policy, address normalization and whether following it would create an unauthorized external call. Compare the intended number-management change with the observed redirect.
Next action and common mistake
Do not blindly make a supplied contact a permanent trusted trunk or paid route. Validate ownership and carrier guidance, then test the new destination and the old published address. Keep the redirect distinct from a temporary 302.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.