SIP

SIP 100 Trying vs 500 Server Internal Error

SIP 100 (Trying) is a 1xx Provisional response, while 500 (Server Internal Error) is a 5xx Server 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, 500 means that the server encountered an unexpected condition that prevented it from fulfilling 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 encountered an unexpected condition that prevented it from fulfilling the request.

何时出现

When the SIP server has an internal error — database failure, unhandled exception, or resource exhaustion.

如何修复

Check server logs for the specific error. Common causes include database connectivity issues, configuration errors, or memory exhaustion.

主要区别

1.

100 is a 1xx Provisional response, while 500 is a 5xx Server Failure response.

2.

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.

3.

SIP 500: The server encountered an unexpected condition that prevented it from fulfilling the request.

4.

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.

5.

You encounter 500 when when the SIP server has an internal error — database failure, unhandled exception, or resource exhaustion.

何时使用哪个

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 500 (Server Internal Error): Check server logs for the specific error. Common causes include database connectivity issues, configuration errors, or memory exhaustion.

了解更多