SIP 302 Moved Temporarily vs 405 Method Not Allowed
SIP 302 (Moved Temporarily) is a 3xx Redirection response, while 405 (Method Not Allowed) 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, 405 means that the method specified in the Request-Line is not allowed for the address identified by the Request-URI.
描述
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 method specified in the Request-Line is not allowed for the address identified by the Request-URI.
何时出现
When sending a SIP method (e.g., MESSAGE, PUBLISH) that the server does not support for the target URI.
如何修复
Check the Allow header in the response to see which methods are supported. Use a supported method instead.
主要区别
302 is a 3xx Redirection response, while 405 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 405: The method specified in the Request-Line is not allowed for the address identified by the Request-URI.
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 405 when when sending a SIP method (e.g., MESSAGE, PUBLISH) that the server does not support for the target URI.
何时使用哪个
For 302 (Moved Temporarily): Redirect the current call to the Contact URI provided, but keep the original URI for future requests. For 405 (Method Not Allowed): Check the Allow header in the response to see which methods are supported. Use a supported method instead.