SIP 100 Trying vs 428 Use Identity Header
SIP 100 (Trying) is a 1xx Provisional response, while 428 (Use Identity Header) is a 4xx Client Failure response. 100 indicates that the request has been received by the next-hop server and an unspecified action is being taken to process it. The UAC should expect additional responses. 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 received by the next-hop server and an unspecified action is being taken to process it. The UAC should expect additional responses.
何时出现
Immediately after sending an INVITE. The proxy has received the call and is searching for the callee. This is the SIP equivalent of a dial tone.
如何修复
No fix needed — this is normal call setup behavior. If stuck on 100 Trying for too long, check network connectivity and proxy configuration.
描述
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.
主要区别
100 is a 1xx Provisional response, while 428 is a 4xx Client Failure response.
SIP 100: The request has been received by the next-hop server and an unspecified action is being taken to process it. The UAC should expect additional responses.
SIP 428: The server requires an Identity header to verify the caller's identity but it was not included in the request.
You encounter 100 when immediately after sending an INVITE. The proxy has received the call and is searching for the callee. This is the SIP equivalent of a dial tone.
You encounter 428 when in environments that enforce SIP Identity (RFC 4474) for caller authentication and spam prevention (STIR/SHAKEN).
何时使用哪个
For 100 (Trying): No fix needed — this is normal call setup behavior. If stuck on 100 Trying for too long, check network connectivity and proxy configuration. For 428 (Use Identity Header): Add a valid Identity header signed by an authentication service. Ensure your STIR/SHAKEN infrastructure is properly configured.