SIP 202 Accepted vs 428 Use Identity Header
SIP 202 (Accepted) is a 2xx Success response, while 428 (Use Identity Header) is a 4xx Client Failure response. 202 indicates that the request has been accepted for processing but the processing has not been completed. Used primarily for REFER 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.
説明
The request has been accepted for processing but the processing has not been completed. Used primarily for REFER requests.
このコードが表示される場合
After sending a REFER request for call transfer. The transfer target acknowledges receipt but hasn't completed the transfer yet.
解決方法
Wait for a NOTIFY to learn the outcome of the referred action. If no NOTIFY arrives, check subscription state and network connectivity.
説明
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.
主な違い
202 is a 2xx Success response, while 428 is a 4xx Client Failure response.
SIP 202: The request has been accepted for processing but the processing has not been completed. Used primarily for REFER 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 202 when after sending a REFER request for call transfer. The transfer target acknowledges receipt but hasn't completed the transfer yet.
You encounter 428 when in environments that enforce SIP Identity (RFC 4474) for caller authentication and spam prevention (STIR/SHAKEN).
どちらをいつ使うか
For 202 (Accepted): Wait for a NOTIFY to learn the outcome of the referred action. If no NOTIFY arrives, check subscription state and network connectivity. For 428 (Use Identity Header): Add a valid Identity header signed by an authentication service. Ensure your STIR/SHAKEN infrastructure is properly configured.