SIP

SIP 100 Trying vs 505 Version Not Supported

SIP 100 (Trying) is a 1xx Provisional response, while 505 (Version Not Supported) 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, 505 means that the server does not support the SIP protocol version that was used in the request. Currently only SIP/2.0 is standardized.

描述

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 does not support the SIP protocol version that was used in the request. Currently only SIP/2.0 is standardized.

何时出现

Extremely rare. Would occur if a client sends a request with a SIP version other than 2.0.

如何修复

Ensure your UA uses SIP/2.0 in the request line. This is the only standardized version.

主要区别

1.

100 is a 1xx Provisional response, while 505 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 505: The server does not support the SIP protocol version that was used in the request. Currently only SIP/2.0 is standardized.

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 505 when extremely rare. Would occur if a client sends a request with a SIP version other than 2.0.

何时使用哪个

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 505 (Version Not Supported): Ensure your UA uses SIP/2.0 in the request line. This is the only standardized version.

了解更多