SIP 100 Trying vs 401 Unauthorized
SIP 100 (Trying) is a 1xx Provisional response, while 401 (Unauthorized) 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, 401 means that the request requires user authentication. The response includes a WWW-Authenticate header with a challenge for the realm.
描述
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 request requires user authentication. The response includes a WWW-Authenticate header with a challenge for the realm.
何时出现
When making a request that requires Digest authentication. Common for REGISTER and INVITE requests to authenticated SIP trunks.
如何修复
Resend the request with proper Authorization header containing valid credentials (Digest authentication).
主要区别
100 is a 1xx Provisional response, while 401 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 401: The request requires user authentication. The response includes a WWW-Authenticate header with a challenge for the realm.
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 401 when when making a request that requires Digest authentication. Common for REGISTER and INVITE requests to authenticated SIP trunks.
何时使用哪个
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 401 (Unauthorized): Resend the request with proper Authorization header containing valid credentials (Digest authentication).