SIP 301 Moved Permanently vs 428 Use Identity Header
SIP 301 (Moved Permanently) is a 3xx Redirection response, while 428 (Use Identity Header) 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, 428 means that the server requires an Identity header to verify the caller's identity but it was not included in the request.
설명
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 server requires an Identity header to verify the caller's identity but it was not included in the request.
이 코드를 보게 되는 경우
In environments that enforce SIP Identity (RFC 4474) for caller authentication and spam prevention (STIR/SHAKEN).
해결 방법
Add a valid Identity header signed by an authentication service. Ensure your STIR/SHAKEN infrastructure is properly configured.
주요 차이점
301 is a 3xx Redirection response, while 428 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 428: The server requires an Identity header to verify the caller's identity but it was not included in the request.
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 428 when in environments that enforce SIP Identity (RFC 4474) for caller authentication and spam prevention (STIR/SHAKEN).
언제 어떤 것을 사용할지
For 301 (Moved Permanently): Update your address book or routing tables to use the new Contact URI provided in the response. For 428 (Use Identity Header): Add a valid Identity header signed by an authentication service. Ensure your STIR/SHAKEN infrastructure is properly configured.