SIP 301 Moved Permanently vs 405 Method Not Allowed
SIP 301 (Moved Permanently) is a 3xx Redirection response, while 405 (Method Not Allowed) is a 4xx Client Failure response. 301 indicates that the user can no longer be found at the address in the Request-URI. The client should direct future requests to the new address in the Contact header. In contrast, 405 means that the method specified in the Request-Line is not allowed for the address identified by the Request-URI.
설명
The user can no longer be found at the address in the Request-URI. The client should direct future requests to the new address in the Contact header.
이 코드를 보게 되는 경우
When a user has permanently changed their SIP address. All future calls should be directed to the new URI.
해결 방법
Update your address book or routing tables to use the new Contact URI provided in the response.
설명
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.
주요 차이점
301 is a 3xx Redirection response, while 405 is a 4xx Client Failure response.
SIP 301: The user can no longer be found at the address in the Request-URI. The client should direct future requests to the new address in the Contact header.
SIP 405: The method specified in the Request-Line is not allowed for the address identified by the Request-URI.
You encounter 301 when when a user has permanently changed their SIP address. All future calls should be directed to the new URI.
You encounter 405 when when sending a SIP method (e.g., MESSAGE, PUBLISH) that the server does not support for the target URI.
언제 어떤 것을 사용할지
For 301 (Moved Permanently): Update your address book or routing tables to use the new Contact URI provided in the response. For 405 (Method Not Allowed): Check the Allow header in the response to see which methods are supported. Use a supported method instead.