SIP 302 Moved Temporarily vs 428 Use Identity Header
SIP 302 (Moved Temporarily) is a 3xx Redirection response, while 428 (Use Identity Header) 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, 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 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 You See It
When a user is temporarily reachable at a different location, such as when traveling or using a different device.
How to Fix
Redirect the current call to the Contact URI provided, but keep the original URI for future requests.
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
302 is a 3xx Redirection response, while 428 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 428: The server requires an Identity header to verify the caller's identity but it was not included in the request.
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 428 when in environments that enforce SIP Identity (RFC 4474) for caller authentication and spam prevention (STIR/SHAKEN).
When to Use Which
For 302 (Moved Temporarily): Redirect the current call to the Contact URI provided, but keep the original URI for future requests. For 428 (Use Identity Header): Add a valid Identity header signed by an authentication service. Ensure your STIR/SHAKEN infrastructure is properly configured.