Locate the response family
- 1xx ProvisionalRequest is progressing
- 2xx SuccessRequest succeeded
- 3xx RedirectionAnother destination302 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 request should be retried at a temporary alternate location indicated by the response. It does not permanently redefine the called identity.
Read it in context
Call forwarding or routing policy can produce a redirect. A PBX may follow it, reject it or implement forwarding using a separate call leg. Those behaviors can have different permission and charging consequences.
Administrator checks
Inspect the proposed contact, the source of the redirect and the PBX’s policy for external destinations. Verify whether the resulting call consumes additional trunk capacity and which caller identity is presented.
Next action and common mistake
Do not bypass destination restrictions to make redirection work. Test approved forwarding and a prohibited destination, then confirm normal routing when the temporary condition ends. Distinguish a redirect from a PBX bridging two legs itself.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.