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.
Description
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 You See It
When a user has permanently changed their SIP address. All future calls should be directed to the new URI.
How to Fix
Update your address book or routing tables to use the new Contact URI provided in the response.
Description
The server requires an Identity header to verify the caller's identity but it was not included in the request.
When You See It
In environments that enforce SIP Identity (RFC 4474) for caller authentication and spam prevention (STIR/SHAKEN).
How to Fix
Add a valid Identity header signed by an authentication service. Ensure your STIR/SHAKEN infrastructure is properly configured.
Key Differences
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).
When to Use Which
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.