SIP Redirect ResponsesAdded by IBM on November 30, 2011 | Version 1 (Original)
|The 3xx responses give information about the user's new location, or about alternative services that might be able to satisfy the call.
The 3xx responses give information about the user's new location, or about alternative services that might be able to satisfy the call.
Table 1. Redirect Responses
Parent topic: SIP Overview
|Response Code ||Response||Comment|
|300||Multiple Choices ||The address in the request resolved to several choices, each with its own specific location, and the user (or UA (User Agent)) can select a preferred communication end point and redirect its request to that location.|
|301||Moved Permanently||The address in the request resolved to several choices, each with its own specific location, and the user (or UA) can select a preferred communication end point and redirect its request to that location.|
|302||Moved Temporarily||The requesting client should retry the request at the new address(es) given by the Contact header field (Section 20.10). The Request-URI of the new request uses the value of the Contact header field in the response. The duration of the validity of the Contact URI can be indicated through an Expires (Section 20.19) header field or an expires parameter in the Contact header field. Both proxies and UAs MAY cache this URI for the duration of the expiration time. If there is no explicit expiration time, the address is only valid once for repeating, and must not be cached for future transactions. If the URI cached from the Contact header field fails, the Request- URI from the redirected request MAY be tried again a single time. The temporary URI may have become out-of-date sooner than the expiration time, and a new temporary URI may be available.|
|305||Use Proxy||The requested resource must be accessed through the proxy given by the Contact field. The Contact field gives the URI of the proxy. The recipient is expected to repeat this single request via the proxy. 305 (Use Proxy) responses must only be generated by User Agent Servers.|
|380||Alternative Service||The call was not successful, but alternative services are possible. The alternative services are described in the message body of the response. Formats for such bodies are not defined here, and may be the subject of future standardization.|