SIP 302 Moved Temporarily vs 483 Too Many Hops
SIP 302 (Moved Temporarily) is a 3xx Redirection response, while 483 (Too Many Hops) 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, 483 means that the Max-Forwards header has reached zero, indicating the request has passed through too many proxies.
説明
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 a user is temporarily reachable at a different location, such as when traveling or using a different device.
解決方法
Redirect the current call to the Contact URI provided, but keep the original URI for future requests.
説明
The Max-Forwards header has reached zero, indicating the request has passed through too many proxies.
このコードが表示される場合
When a request traverses more proxies than the Max-Forwards counter allows (default 70). Often indicates a routing loop.
解決方法
Check for routing loops. If the path is legitimately long, increase Max-Forwards. Usually indicates misconfigured routing.
主な違い
302 is a 3xx Redirection response, while 483 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 483: The Max-Forwards header has reached zero, indicating the request has passed through too many proxies.
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 483 when when a request traverses more proxies than the Max-Forwards counter allows (default 70). Often indicates a routing loop.
どちらをいつ使うか
For 302 (Moved Temporarily): Redirect the current call to the Contact URI provided, but keep the original URI for future requests. For 483 (Too Many Hops): Check for routing loops. If the path is legitimately long, increase Max-Forwards. Usually indicates misconfigured routing.