SIP 300 Multiple Choices vs 428 Use Identity Header
SIP 300 (Multiple Choices) is a 3xx Redirection response, while 428 (Use Identity Header) is a 4xx Client Failure response. 300 indicates that the address in the request resolved to several choices, each with its own location. The user or UA can select a preferred communication endpoint. 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 address in the request resolved to several choices, each with its own location. The user or UA can select a preferred communication endpoint.
このコードが表示される場合
When a user has multiple registered devices or contact addresses and the server cannot determine which one to use.
解決方法
Select one of the provided Contact addresses and resend the request to that specific URI.
説明
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.
主な違い
300 is a 3xx Redirection response, while 428 is a 4xx Client Failure response.
SIP 300: The address in the request resolved to several choices, each with its own location. The user or UA can select a preferred communication endpoint.
SIP 428: The server requires an Identity header to verify the caller's identity but it was not included in the request.
You encounter 300 when when a user has multiple registered devices or contact addresses and the server cannot determine which one to use.
You encounter 428 when in environments that enforce SIP Identity (RFC 4474) for caller authentication and spam prevention (STIR/SHAKEN).
どちらをいつ使うか
For 300 (Multiple Choices): Select one of the provided Contact addresses and resend the request to that specific URI. For 428 (Use Identity Header): Add a valid Identity header signed by an authentication service. Ensure your STIR/SHAKEN infrastructure is properly configured.