SIP 200 OK vs 428 Use Identity Header
SIP 200 (OK) is a 2xx Success response, while 428 (Use Identity Header) is a 4xx Client Failure response. 200 indicates that the request has succeeded. For INVITE, the call has been answered. For other methods, the action has been completed successfully. 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 succeeded. For INVITE, the call has been answered. For other methods, the action has been completed successfully.
このコードが表示される場合
When a call is answered (INVITE 200 OK), a registration succeeds (REGISTER 200 OK), or a subscription is accepted (SUBSCRIBE 200 OK).
解決方法
No fix needed — this is a success response. The caller should send an ACK to complete the three-way handshake for INVITE transactions.
説明
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.
主な違い
200 is a 2xx Success response, while 428 is a 4xx Client Failure response.
SIP 200: The request has succeeded. For INVITE, the call has been answered. For other methods, the action has been completed successfully.
SIP 428: The server requires an Identity header to verify the caller's identity but it was not included in the request.
You encounter 200 when when a call is answered (INVITE 200 OK), a registration succeeds (REGISTER 200 OK), or a subscription is accepted (SUBSCRIBE 200 OK).
You encounter 428 when in environments that enforce SIP Identity (RFC 4474) for caller authentication and spam prevention (STIR/SHAKEN).
どちらをいつ使うか
For 200 (OK): No fix needed — this is a success response. The caller should send an ACK to complete the three-way handshake for INVITE transactions. For 428 (Use Identity Header): Add a valid Identity header signed by an authentication service. Ensure your STIR/SHAKEN infrastructure is properly configured.