SIP 302 Moved Temporarily vs 485 Ambiguous
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://statuscodefyi.com/iframe/entity//" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://statuscodefyi.com/entity//Add a dynamic SVG badge to your README or docs.
[](https://statuscodefyi.com/entity//)Use the native HTML custom element.
SIP 302 (Moved Temporarily) is a 3xx Redirection response, while 485 (Ambiguous) is a 4xx Client Failure response. 302 indicates that the callee has temporarily moved to a different address. The client should retry the request at the Contact address but continue using the original URI for future requests. In contrast, 485 means that the Request-URI was ambiguous. The response body may contain a list of possible unambiguous addresses.
Description
The callee has temporarily moved to a different address. The client should retry the request at the Contact address but continue using the original URI for future requests.
When You See It
When a user is temporarily reachable at a different location, such as when traveling or using a different device.
How to Fix
Redirect the current call to the Contact URI provided, but keep the original URI for future requests.
Description
The Request-URI was ambiguous. The response body may contain a list of possible unambiguous addresses.
When You See It
When the destination address matches multiple users and the server cannot determine which one is intended.
How to Fix
Use a more specific SIP URI. Check the response body for a list of possible matches and select the correct one.
Key Differences
302 is a 3xx Redirection response, while 485 is a 4xx Client Failure response.
SIP 302: The callee has temporarily moved to a different address. The client should retry the request at the Contact address but continue using the original URI for future requests.
SIP 485: The Request-URI was ambiguous. The response body may contain a list of possible unambiguous addresses.
You encounter 302 when when a user is temporarily reachable at a different location, such as when traveling or using a different device.
You encounter 485 when when the destination address matches multiple users and the server cannot determine which one is intended.
When to Use Which
For 302 (Moved Temporarily): Redirect the current call to the Contact URI provided, but keep the original URI for future requests. For 485 (Ambiguous): Use a more specific SIP URI. Check the response body for a list of possible matches and select the correct one.